E-Commerce Times Talkback
|
|
|
See Full Story
America Online, the largest Internet service provider, said it would stop using Microsoft's Sender ID technology to filter unwanted e-mail being sent to its millions of members, and instead embrace an open-source friendly alternative. AOL's decision came just days after a subgroup of the Internet Engineering Task Force (IETF) said it was unable reach consensus on how Sender ID, which is widely viewed as a strong antispam technology, could be integrated with other tools. A major stumbling block for the Task Force was the fact that Microsoft has laid patent claims on Sender ID.
Posted by: perpeta 2004-09-28 16:07:46 In reply to: Keith Regan
SMTP should not continue to live...it has outlived its geeky usefulness.
Private email networks, using a simple web browser with the HTTP protocol and web services behind the scenes connecting all of the private networks together. It's like a P2P system, but has some central control to coordinate who is who.
That is the future.
Private email networks, using a simple web browser with the HTTP protocol and web services behind the scenes connecting all of the private networks together. It's like a P2P system, but has some central control to coordinate who is who.
That is the future.
Posted by: aloaha 2004-09-18 14:36:26 In reply to: Keith Regan
Yes,
but people are makeing the Story to political.
SPF is simply the better choice on your SMTP Server since it really reduced the traffic since
it checks the envelope (which cannot be forged).
Sender ID uses the same mechanism but uses the Mime Header. That means that Sender ID doesnt make
sense to use it on a Server to reduce Traffic.
Thats why Sender ID suits more as Plugins for
Mail Clients.....
We are supporting SPF fully in our Aloaha.
Sender ID we are using as well but only to
check the published records. From that point
onwards we treat them as SPF1 since we want
to reduce the SPAM Traffic on your Server...
FH
but people are makeing the Story to political.
SPF is simply the better choice on your SMTP Server since it really reduced the traffic since
it checks the envelope (which cannot be forged).
Sender ID uses the same mechanism but uses the Mime Header. That means that Sender ID doesnt make
sense to use it on a Server to reduce Traffic.
Thats why Sender ID suits more as Plugins for
Mail Clients.....
We are supporting SPF fully in our Aloaha.
Sender ID we are using as well but only to
check the published records. From that point
onwards we treat them as SPF1 since we want
to reduce the SPAM Traffic on your Server...
FH
Posted by: jenfromthelou 2004-10-20 17:17:54 In reply to: aloaha
I think it is being made out to be more political that it should be as well. But I cannot stand the presence of SPAM!







Headline Feeds
