[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Fetchmail trouble with mailing lists



In message <33K9C-8se-25@gated-at.bofh.it>, Erik Dörnbach <doernbach@elge.de> writes
Hello people,

I'm having a Debian Sarge box here running fetchmail, sendmail, spamass-milter. Mail retrieved by fetchmail from 2 multidrop POP accounts is delivered to local sendmail (for spam check) and then forwarded via mailertable to an Exchange server. Everything on the
Debian box are official (well, testing) debs.

When any user on the Exchange is subscribed to a mailing list just like this, mail will be delivered localy on the Debian box to the account set as postmaster in the global fetchmailrc (running daemon mode btw). The original reciever's address is neither seen in any logfiles or in the postmaster mbox, just the ml address (which can ofcourse not be
delivered).


What did I miss here?

As another poster has said, you may be able to fix this. You may not. The SMTP protocol passes email between servers until it reaches its destination, which is specified in the SMTP 'envelope'. This is not part of the email header set and is discarded when the mail reaches its final destination. As far as SMTP is concerned, an ISP which offers collection by POP3 is the final destination. Most POP3 mailboxes are single-user, so there is usually no problem in identifying the recipient. Multiple-user mailboxes may cause problems.

For normal and CC: recipients, this is not an issue because they will be listed in the appropriate header, and fetchmail will identify them. As you say, the recipient of a mailing list message is the list itself, and 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:.

If this is the case with yours, then fetchmail can be taught to check for this header. If not, then you will need to keep records of mailing list users, and alias messages sent to the mailing list to these users. 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.
--
Joe



Reply to: