Yup, Burt got it right.
Unfortunately, using X-Original-To: as the envelope address exposes another
hazard of using fetchmail.
Now what happens is that if someone addresses mail To: howard@sci1.com,
test@sci1.com some of the time only the first recipient gets the mail. It
depends upon how ISPs up the line process the message.
If the message arrives with two different sequence numbers then it is
handled properly. If it arrives as two messages, with two different
X-Original-To: headers but the same sequence number then fetchmail discards
the second one assuming it's a duplicate. Unfortunately, I can't find a
fetchmail switch to disable that behavior. I may go and try to hack the code.
Any other ideas?
Thanks,
Howard
At 10:00 AM 9/13/2003 -0400, Burt Juda wrote:
>It looks like the ISP is putting the envelope-recipient info into the
>"X-Original-To" header.
>You need to tell fetchmail to use that for the recipient.
>
>Use the 'envelope X-Original-To:" parameter when fetching the multi-user
>mailbox.
>I do exactly the same thing but with the "Envelope-to:" header that my ISP
>adds.
>
> - Burt
>
>
>Howard Spindel wrote:
>
>>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.
>>
>>-------------------------------------------
>>
>>Return-Path: <gdjmsp@qwest.net>
>>Received: from localhost (IDENT:root@localhost.localdomain [127.0.0.1])
>>by server.sci1.com (8.9.3/8.9.3) with ESMTP id QAA31572;
>>Thu, 11 Sep 2003 16:50:44 -0700
>>X-Original-To: test@sci1.com
>>
>>-----------------------------------------------------------------------------------------------------
>>
>>
>>Return-Path: <gdjmsp@qwest.net>
>>Received: from localhost (IDENT:root@localhost.localdomain [127.0.0.1])
>>by server.sci1.com (8.9.3/8.9.3) with ESMTP id QAA31564;
>>Thu, 11 Sep 2003 16:50:43 -0700
>>X-Original-To: howard@sci1.com
Follow-Ups:
References:
|
|
