Thanks for your replies,
citing Joe here:
> a BCC: recipient will not be named in a header either, for obvious
> reasons. POP3 does not work well in these cases where multiple users
> share a mailbox. Many ISPs do in fact keep the SMTP envelope,
> converting
> it to a non-standard header, such as X-EnvelopeTo:.
I checked the ISP side, there's sendmail running as MTA and the particular
multidrop box is created with an "@domain.com dropbox" entry in the
virtusertable there. Looking at the mail before I'm fetching it shows there'
s a "Recieved: from ... for <[EMAIL PROTECTED]>; date" (There is
more stuff in the Recieved line I cut out here).
So I put an "envelope Received" in my fetchmailrc (isn't this default
anyway?)- to no avail, ml mails still get delivered to the postmaster.
I'm just pasting the poll-part of my fetchmailrc here, maybe the position is
wrong (though I don't get syntax error when running):
<snip>
poll mailserver.somewhere.com with proto POP3 and options no dns
localdomains domain.com
envelope Received
user 'dropbox' there with password 'topsecret' to * here options
fetchall
</snip>
> Probably the easiest way is to create distribution groups in
> Exchange,
> and use the Linux mail server to reroute mail addressed to
> the lists to
> the appropriate group.
Ey, nice idea also. Though too much trouble at this time, I hope to get away
from POP3 with an MX record in about 2 weeks time and fetchmail will be
history then.
Thanks for more input.
Erik
