-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2005-10-24 at 18:19 +0800, Peter Sutter wrote:
SuSE V8.2 sendmail on the sending side SuSE V9.2 sendmail on the receiving side fetchmail release 6.2.5+POP2+RPA+NTLM+SDPS+SSL+OPIE+NLS
I am sending out one email with 3 recipients on the from line, cheryl@domain.topleveldomain, julie@domain.topleveldomain, sue@domain.topleveldomain,
I assume you meant "To:" line.
The mail is received by the SMTP server of an ISP, which buffers it in mailbox@isp.com. There are 3 messages in the pop mailbox, one for cheryl, one for julie and 1 for sue. All messages have the same message header and the same message ID.
First problem: is it a) _one_ pop mailbox with three copies, or is it b) three mailboxes, with one email each? I assume it is "a".
Fetchmail retrieves the 3 emails from mailbox@isp.com. The first mail ist distributed to all 3 recipients, so is the second and the third.
Only one message left the sending smtp server, it had a unique message ID and 3 recipients. Received at the destination were 9 messages.
Ok, I'll try to explain a bit. The three initial copies are generated on the sending side. The ISP box thus receives three emails: cheryl, julie, and sue. Fetchmail fetchs them, and forwards them to sendmail. Being a multidrop box (a) fetchmail probably doesn't know who is the "main" destination of each; it hands them over to sendmail, who sees in the destination three addresses... thus sends each one to all three destinations. A peek at the log would serve to check if my hypothesis is correct (perhaps calling fetchmail in verbose mode (-v)). Please read the fetchmail manual, paying attention at "multidrop mail boxes". Look: | Note that | fetchmail's reconstruction of MAIL FROM and RCPT TO | lines is not guaranteed correct; the caveats discussed | under THE USE AND ABUSE OF MULTIDROP MAILBOXES below | apply. This is what is happening... (IMO). Check if your ISP puts a "Delivered-To" line, you can use it to clarify things in fetchmail. Mmmm...: | Also, note that in multidrop mode duplicate mails are sup- | pressed. A piece of mail is considered duplicate if it has | the same message-ID as the message immediately preceding and | more than one addressee. Such runs of messages may be gener- | ated when copies of a message addressed to multiple users are | delivered to a multidrop box. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDXMFLtTMYHG2NR9URAoJoAJ97YCWolNmHXRcEY3onzhmfdtxdgQCdGzRd lMcWZtkS1SdsCkOZDx5zTCg= =hqfA -----END PGP SIGNATURE-----