OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: *_bcc_maps bounce behavior

From: Victor Duchovni (Victor.DuchovniMorganStanley.com)
Date: Thu Aug 11 2005 - 07:49:56 CDT


On Thu, Aug 11, 2005 at 08:34:55AM -0400, Joel Nimety wrote:

>
>
> Victor Duchovni wrote:
> > On Wed, Aug 10, 2005 at 08:55:18PM -0400, Joel Nimety wrote:
> >
> >
> >>I'm curious, how does postfix know when it is forwarding to another
> >>postfix instance?
> >>
> >
> >
> > Wrong question, the issue is that not all MTAs implement DSN, so once
> > Postfix relinquishes the mail to another MTA (which may forward it furter)
> > all bets are off. Note also that auto-responders may ignore DSN requests...
> >
> > So basically you get deterministic behaviour while Postfix 2.3 owns the
> > message, and no guarantees after that.
> >
>
> Thanks to both for answering my questions. I'll wait for postfix 2.3 BCC
> behavior to move to an official release.
>

Past releases have been issued in the Dec-Mar timeframe..., expect 2.3
official some time in early 2007. In the interim if you arrange for
local processing by a suitable delivery agent, bounces should be
highly improbable. Such processing is in any case necessary in order
to inject the message envelope into the content of the message for
archiving:

        Return-Path: (really envelope sender) archive-senderexample.com
        From: archive-noreplyexample.com
        To: archiveexample.com
        Subject: message
        Content-Type: multipart/mixed; boundary = "strong-random-hex"

        --strong-random-hex
        Content-Type: text/plain

        MAIL FROM:<alleged-envelope-senderexample.org>
        RCPT TO:<first-envelope-rcptexample.net>
        RCPT TO:<second-envelope-rcptexample.net>
        ...
        RCPT TO:<last-envelope-rcptexample.net>

        --strong-random-hex
        Content-Type: message/rfc822

        Return-Path: <alleged-envelope-senderexample.org>
        Received: ...
        From: <alleged-authorexample.org>
        To: <plausible-recipientsexample.net>
        Subject: Yet another junk message

        buy fraudulent overpriced junk

        --strong-random-hex--

In the above format the archive captures both the message content
and the message envelope.

--
        Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majordomopostfix.org?body=unsubscribe%20postfix-users>

If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.