<P>Looks like it will work if I set it to deliver to a special header only! </P> <P> Thanks!</P>

<P>We are running Mercury/32 4.01b.  Mercury connects to our ISP using MercuryC (SMTP) & MercuryD (POP3).  We are NDS aware.</P> <P mce_keep="true"> </P> <P>All users email at our ISP is forwarded to a single email account (<A href="mailto:mickey.mouse@wcaslab.com">mickey.mouse@wcaslab.com</A>) , Mercury connects to this box and downloads all email.</P> <P>The problem (?) is that there is an alias web server in the middle (before it hits our ISP) that aliases from <<A href="mailto:user@waltdisney.com">user>@waltdisney.com</A> to <user>@wcaslab.com </P> <P>When does Mercury add the X-Envelope-To: header?  </P> <P>It seems like that if Mercury doesn't like the original To: header (it's not seeing the aliased address) it doesn't know who to deliver it to, it sets the X-Envelope-To: recipient to the 'default user' field in the Mercury setup (mmouse.WCAS, who gets it) and not the original To: header recipient.  If the email is originally addressed to <A href="mailto:daffy.duck@wcaslab.com">daffy.duck@wcaslab.com</A> the X-Envelope-To: recipient would read <A href="mailto:daffy.duck@wcaslab.com">daffy.duck@wcaslab.com</A> and be delivered to Daffy.</P> <P>Mercury delivers the mail to the X-Envelope-To: recipient?</P> <P>See below for an example:</P> <P>==================================</P><FONT size=2> <P align=left>Received: from spooler by wcaslab.com (Mercury/32 v4.01b); 26 Jul 2007 12:30:56 -0700</P> <P align=left>X-Envelope-To: mmouse.WCAS</P> <P align=left>Return-Path: <minnie.mouse@webmail.com></P> <P align=left>Delivered-To: <A href="mailto:mickey.mouse@wcaslab.com">mickey.mouse@wcaslab.com</A></P> <P align=left>Received: (qmail 1813 invoked by uid 508); 26 Jul 2007 19:30:16 -0000</P> <P align=left>X-Mail-Scanner: (n/a)</P> <P align=left>Delivered-To: <A href="mailto:daffy.duck@wcaslab.com">daffy.duck@wcaslab.com</A></P> <P align=left>...edited.....</P> <P align=left>Date: Thu, 26 Jul 2007 12:29:43 -0700 (PDT)</P> <P align=left>From: Minnie Mouse <minnie.mouse@webmail.com></P> <P align=left>Subject: test for delivery</P> <P>To: <A href="mailto:daffy.duck@waltdisney.com">daffy.duck@waltdisney.com</A></P></FONT> <P mce_keep="true"> </P>

[quote user="gregrshaw"]<p>We are running Mercury/32 4.01b.  Mercury connects to our ISP using MercuryC (SMTP) & MercuryD (POP3).  We are NDS aware.</p> <p mce_keep="true"> </p> <p>All users email at our ISP is forwarded to a single email account (<a href="mailto:mickey.mouse@wcaslab.com" mce_href="mailto:mickey.mouse@wcaslab.com">mickey.mouse@wcaslab.com</a>) , Mercury connects to this box and downloads all email.</p> <p>The problem (?) is that there is an alias web server in the middle (before it hits our ISP) that aliases from <<a href="mailto:user@waltdisney.com" mce_href="mailto:user@waltdisney.com">user>@waltdisney.com</a> to <user>@wcaslab.com </p> <p>When does Mercury add the X-Envelope-To: header? </p><p> </p><p>When writing the *.CNM file to the users new mail directory.</p><p>  </p> <p>It seems like that if Mercury doesn't like the original To: header (it's not seeing the aliased address) it doesn't know who to deliver it to, it sets the X-Envelope-To: recipient to the 'default user' field in the Mercury setup (mmouse.WCAS, who gets it) and not the original To: header recipient.  If the email is originally addressed to <a href="mailto:daffy.duck@wcaslab.com" mce_href="mailto:daffy.duck@wcaslab.com">daffy.duck@wcaslab.com</a> the X-Envelope-To: recipient would read <a href="mailto:daffy.duck@wcaslab.com" mce_href="mailto:daffy.duck@wcaslab.com">daffy.duck@wcaslab.com</a> and be delivered to Daffy.</p> <p>Mercury delivers the mail to the X-Envelope-To: recipient?</p> <p>See below for an example:</p> <p>==================================</p><font size="2"> <p align="left">Received: from spooler by wcaslab.com (Mercury/32 v4.01b); 26 Jul 2007 12:30:56 -0700</p> <p align="left">X-Envelope-To: mmouse.WCAS</p> <p align="left">Return-Path: <minnie.mouse@webmail.com></p> <p align="left">Delivered-To: <a href="mailto:mickey.mouse@wcaslab.com" mce_href="mailto:mickey.mouse@wcaslab.com">mickey.mouse@wcaslab.com</a></p> <p align="left">Received: (qmail 1813 invoked by uid 508); 26 Jul 2007 19:30:16 -0000</p> <p align="left">X-Mail-Scanner: (n/a)</p> <p align="left">Delivered-To: <a href="mailto:daffy.duck@wcaslab.com" mce_href="mailto:daffy.duck@wcaslab.com">daffy.duck@wcaslab.com</a></p><p align="left"> </p><p align="left">Here's a header to work with.  Tell MercuryD to use this for delivery only in the MercuryD setup, level the user name blank  and set the default user to the postmasters address.  I believe that this will be properly delivered to the correct user.  The only problem I can see is that there is two Delivered-To: lines and this will be a problem if these are actual headers.  </p><p align="left"> </p><p align="left"> </p> <p align="left">...edited.....</p> <p align="left">Date: Thu, 26 Jul 2007 12:29:43 -0700 (PDT)</p> <p align="left">From: Minnie Mouse <minnie.mouse@webmail.com></p> <p align="left">Subject: test for delivery</p> <p>To: <a href="mailto:daffy.duck@waltdisney.com" mce_href="mailto:daffy.duck@waltdisney.com">daffy.duck@waltdisney.com</a></p></font> <p mce_keep="true"> </p>[/quote]

<P>Yes there are two Delivered-To Headers, the one closest to the top is always mickey.mouse - this is the email box that ALL email is forwarded to at the ISP and where Mercury connects for downloading.</P> <P>The only time there is one instance is when the email is originaly addressed to mickey.mouse (doesn't need to be forwarded).</P> <P mce_keep="true"> </P>