OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Re: After upgrading from 2.4.6 to 2.5.3..

From: Wietse Venema (wietseporcupine.org)
Date: Thu Aug 21 2008 - 06:08:33 CDT


Bj?rn T Johansen:
> On Wed, 20 Aug 2008 14:16:22 -0400 (EDT)
> wietseporcupine.org (Wietse Venema) wrote:
>
> > Bj?rn T Johansen:
> > > On Wed, 20 Aug 2008 07:08:32 -0400 (EDT)
> > > wietseporcupine.org (Wietse Venema) wrote:
> > >
> > > > Bj?rn T Johansen:
> > > > > Aug 20 12:36:44 web postfix/pipe[2802]: 88AC71FA25F: to=<btjhavleik.no>, relay=dovecot, delay=0.09,
> > > > > delays=0.07/0/0/0.02, dsn=5.4.6, status=bounced (mail forwarding loop for btjhavleik.no)
> > > >
> > > > You are sending mail with
> > > >
> > > > Delivered-To: btjhavleik.no
> > > >
> > > > into the pipe daemon.
> > > >
> > > > See:
> > > > The RELEASE_NOTES file
> > > > man 8 pipe
> > > >
> > > > Wietse
> > >
> > > Yes, in my master.cf file I have this..:
> > >
> > > dovecot unix - n n - - pipe
> > > flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -d ${recipient}
> > >
> > >
> > > I can't use this anymore with version 2.5.x?
> >
> > Please read the documents that I referred you to.
> >
> > Wietse
>
>
> Yes, I did but I am not sure what the solution is? I see that the D flag adds a Delivered-To header and that
> it checks the mail to see if it already has a Delivered-To header and the message is returned as undeliverable if so,
> as of version 2.5.x...
> But is the solution to this to remove the D flag from the pipe transport? Or should I increase
> dovecot_destination_recipient_limit from 1 to 2?

Given this description:

              D Prepend a "Delivered-To: recipient" message header with
                     the envelope recipient address. Note: for this to work,
                     the transport_destination_recipient_limit must be 1 (see
                     SINGLE-RECIPIENT DELIVERY above for details).

                     The D flag also enforces loop detection (Postfix 2.5 and
                     later): if a message already contains a Delivered-To:
                     header with the same recipient address, then the message
                     is returned as undeliverable. The address comparison is
                     case insensitive.

                     This feature is available as of Postfix 2.0.

Which solution would you pick when mail is returned as undeliverable
because a "mail forwarding loop" was detected?

You will have to use your own brain cycles.

        Wietse