On Mon, Jun 16, 2003 at 01:04:50AM -0500, Tim Legant wrote: > Guy Middleton <[EMAIL PROTECTED]> writes: > > > From [EMAIL PROTECTED] Sun Jun 15 23:54:34 2003 > > Return-Path: <[EMAIL PROTECTED]> > > X-Original-To: [EMAIL PROTECTED] > > Delivered-To: [EMAIL PROTECTED] > > Received: from localhost (localhost [127.0.0.1]) > > by chaos.obstruction.com (Postfix) with ESMTP id BBC6C5C55 > > for <[EMAIL PROTECTED]>; Sun, 15 Jun 2003 23:54:34 -0400 (EDT) > > X-Original-To: [EMAIL PROTECTED] > > Delivered-To: [EMAIL PROTECTED] > > This looks suspiciously like Postfix is adding the second > X-Original-To ([EMAIL PROTECTED]), perhaps because it appended > '.obstruction.com' to the address for delivery (noted in > Delivered-To).
I don't think it can be avoided having two of these, due to the trip through fetchmail. In the case of a confirmation message, the two headers would be like this: X-Original-To: [EMAIL PROTECTED] X-Original-To: [EMAIL PROTECTED] The second is by the ISP to the confirmation addresss, the first is by my local Postfix, because fetchmail collapses addresses to the real mailbox. The interesting one is the first one (in chronological order). If mail transports prepend header lines, then it should be safe using the last (in textual order). _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
