On Fri, 5 Feb 2010, Chris Lewis wrote:
Daniel Feenberg wrote:
On Fri, 5 Feb 2010, John Levine wrote:
I haven't been following this thread very closely, but why not just
establish a standard role account on the MUAs designated POP or IMAP
server? Such as arf(_at_)pop(_dot_)example(_dot_)com? It effectively
"preconfigures" the
MUA since "arf" is standard and "example.com" is already known to the
MUA.
The less configuration the better, I think.
Sorry, wouldn't work. The name of the POP or IMAP server need not
bear any relationship to any email address. For example, on my
system, the server is named imap.iecc.com (yes, even for POP, it
deters the clueless) but there are not imap.iecc.com addresses at all.
I don't understand why this is relevant. If the MTA operator doesn't want
to support this feature, he doesn't have to. But if he does wish to support
the feature he needs to supply an MX record or accept mail on the POP or
IMAP server. Is that such a great burden? Compared to the other suggestions
here?
Yes. Why tie the ARF path to the mailboxes by naming convention? Don't need
to.
Use arf(_at_)arf(_dot_)domain(_dot_)com(_dot_) If they're the same machine, fine, make
arf.domain.com alias to imap.domain.com. If they're not, you don't have to
rename your mail infrastructure or screw around with forwarding on the imap
machine that you may have no control over.
Fine with me. But you really should learn about MX records - they are very
useful and have been standardized for many years now.
Daniel Feenberg
_______________________________________________
Asrg mailing list
Asrg(_at_)irtf(_dot_)org
http://www.irtf.org/mailman/listinfo/asrg
_______________________________________________
Asrg mailing list
Asrg(_at_)irtf(_dot_)org
http://www.irtf.org/mailman/listinfo/asrg