On 2/5/2010 5:36 PM, der Mouse wrote:
One of the benefits of the suggestion to use the regular posting
mechanism is that it means that the MUA already knows how to post a
message. It does not need the IP Address of a server to post two.
However, it assumes that the path for outgoing mail is related to the
path for incoming mail.
Well, before I sent my first post on this, I considered that question, and I
could argue it either way. If the requirement is a trusted channel from MUA to
the reporting mailbox, then yeah, an asymmetry is a problem. Otherwise, it's ok.
If the two paths are not related, then sending something to the
outgoing mail path won't have any effect on incoming mail handling.
Not quite. The outgoing mail path is a posting agent, not a delivery agent.
The /address/ specifies the delivery agent. That's why this is an issue of
trust, not routing. Since the domain name or possibly full email address of the
reporting destination is taken from the pickup host, there's no question that it
points to the right place. Hence, any valid posting server ought to be able to
get the report there. The problem is whether the reporting server /believes/
that the report is valid.
If there is a configuration asymmetry, then the report will come from outside
the trust boundary.
Also, everyone's talking about POP and IMAP as if they were all there
is. What about cases where the user's mailbox is accessed other ways?
I think the latest round of discussion has eliminated any interest in the
message retrieval mechanism.
--
Dave Crocker
Brandenburg InternetWorking
bbiw.net
_______________________________________________
Asrg mailing list
Asrg(_at_)irtf(_dot_)org
http://www.irtf.org/mailman/listinfo/asrg