Alan,
AD> What's important for me is that RMX allows the receiving MTA to
AD> trivially discover that the originating domain has consented to send
AD> mail from that MTA. Right now, we have *no* way of verifying the
AD> originators consent.
if you find the rmx record, and then you know the posting is through an
authorized MTA.
if you do NOT find the rmx record, you do not know anything.
so, what is the real utility of the rmx record?
that is, what can you safely do, versus not do?
For a variety of reasons -- notably for some mobile users -- the
originating MTA may well be unable to know the set of valid domains
sending from it. That is, some mobile users must be able to
spontaneously post through different MTAs.
AD> I've heard this before, and I have no idea why it's true.
firewall blockage of outbound port 25. relatively common.
it means that mobile users often must re-configure their outbound MTA to
be something new and transient.
AD> Are there NO other methods which a mobile user may use to send mail?
no.
AD> SMTP is only one of many protocols used to send/receive email.
interesting. i believe there are no others. ("submit" is simply smtp on
another port.) which ones are you referring to?
I also believe that if there were others, it would not solve this
problem.
d/
--
Dave Crocker <mailto:dcrocker(_at_)brandenburg(_dot_)com>
Brandenburg InternetWorking <http://www.brandenburg.com>
Sunnyvale, CA USA <tel:+1.408.246.8253>, <fax:+1.866.358.5301>
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg