Sunil Shetye <shetye(_at_)bombay(_dot_)retortsoft(_dot_)com> writes:
Received: ... by mailserver ... [no for <address>]
Received: ... by server1.domain ... for <user(_at_)domain>
Such a situation might occur with one mailserver and one domain being
shared by servers, each handling a subset of users. Of course, I am
not sure if such contrived headers will actually occur.
And I'm not sure if I'd trust Received any further than I can spit.
There's far too much magic (read: complexity) in fetchmail that makes
the whole address finding process difficult to track. OK, fetchmail -vv
will do, but fixing the configuration from seeing what fetchmail -vv
writes takes an expert (or two). All this address-finding stuff is gory.
I've never seen a Received: header that carried more than one envelope
recipient, instead, the envelope address is dropped when the mail has
more than one recipient.
What I mean is: we cannot expect reliable multidrop delivery without
envelope addresses. And we cannot expect reliable multidrop when we have
only one piece of mail for more than one recipient. Multidrop will only
work if the server drops one mail per recipient into the POP3 box. Of
course, that will make people scream about duplicate downloads, but hey,
POP3 was never meant for that. Neither was IMAP. It's time for UUCP and
ODMR.
--
Matthias Andree