> From: majordomo-users-owner@greatcircle.com
> [mailto:majordomo-users-owner@greatcircle.com] On Behalf Of
> Howard Spindel
> Sent: Friday, September 12, 2003 12:30 PM
> To: majordomo-users@greatcircle.com
> Subject: Re: duplicate messages
>
>
> Okay, I'll try not to get you started on how broken outlook is. :(
>
> I've done some more tracing through logs, and I'm pretty
> confident that
> this is not actually a Majordomo problem.
>
> I have my list configured so that if users hit "reply" it goes to the
> original message sender, and "reply all" goes to the original
> sender and
> the list.
>
> What I'm seeing, at least in one of the two cases, is the following:
> 1. Outlook user hits reply-all to message I posted, message
> gets sent To:
> test@sci1.com, howard@sci1.com
> 2. Message hits Outlook user's ISP. Qmail on ISP sends the
> message twice
> to my ISP, once for test@sci1.com, once for
> howard@sci1.com. Unfortunately, both messages continue to have both
> addresses in the To: line.
> 3. When my system fetches the messages from my ISP, it fetches two
> messages. Since both of them are destined for both
> addresses, I see four
> messages when Majordomo and Sendmail are done processing them.
>
> I don't know why Qmail is sending two messages, and whether
> or not this is
> related to something broken in Outlook's headers.
> Any ideas?
>
> The message headers are reproduced below, in case it's helpful.
It's not Qmail OR Outlook that are doing the wrong thing.
It's fetchmail.
Outlook is sending a message as follows:
RCPT TO: <howard@sci1.com>
RCPT TO: <test@sci1.com>
To: howard@sci1.com, test@sci1.com
...which is reasonable.
Qmail always splits envelopes, so it queues these in your
single-POP-mailbox-per-domain as two messages:
Received: ...for <howard@sci1.com>...
To: howard@sci1.com, test@sci1.com
...and...
Received: ...for <test@sci1.com>...
To: howard@sci1.com, test@sci1.com
...which is also kosher.
Then fetchmail ignores the Received: data or other headers that might
indicate each copy is for a different recipient and parses the To: header on
each, and sends each user a copy of each message.
That's what you get when you try to take shortcuts rather than (a) giving
each end-user a POP mailbox upstream, or (b) running SMTP with ETRN rather
than running POP/fetchmail.
References:
|
|
