I meant SMTP AUTH for Sender only no the target SMTP server. It was
from the user point of view. And yes SPFand other techniques do help in MTA
to MTA transaction.
Again, you're ignoring things like discussion group/mailing lists,
message digests, and so forth. Anybody who makes the mistake of
supporting SPF later finds that they can't send mail using their
business E-mail address when they are (say) on a cruise ship
vacation or at an Internet cafe in some other country.
mobileSender(_at_)myDomain--AUTH--> myDomain SMTP--SPF,MTAMark etc---target
SMTP
|__________________________________________|
I truly don't understand why the types that keep hawking SMTP AUTH as the
solution JUST DON'T GET IT... how many times do we have to say this?
THE FACT IS THAT IF YOU ARE ON A CRUISE SHIP AT THEIR INTERNET CAFE, OR AT AN
AIRPORT WAITING LOUNGE INTERNET ACCESS KIOSK, (and many other public-access
situations) YOU MOST LIKELY HAVE *NO* CONTROL ABOUT WHAT SMTP MAIL SERVER IS
GOING TO BE SENDING YOUR OUTGOING E-MAIL MESSAGE. That notwithstanding,
OBVIOUSLY you would STILL want to use "your" own E-mail address as the sender!
SMTP AUTH does NOT help, and generally IS NOT (currently, at least) POSSIBLE,
for such situations!
Gordon Peterson http://personal.terabites.com/
1977-2002 Twenty-fifth anniversary year of Local Area Networking!
Support free and fair US elections! http://stickers.defend-democracy.org
12/19/98: Partisan Republicans scornfully ignore the voters they "represent".
12/09/00: the date the Republican Party took down democracy in America.
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg