OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Postfix Archives: Re: Correct way of rerouting bounce messages

Re: Correct way of rerouting bounce messages

Subject: Re: Correct way of rerouting bounce messages
From: Wietse Venema (wietseporcupine.org)
Date: Mon Jan 24 2000 - 19:40:41 CST

Richard Adams:
>
> > That is too bad. Mail systems are as strong as the weakest link.
> > If one link loses, then the entire mail system loses with it.
>
> Agreed
>
> > What is the problem with this filter that it refuses valid MAIL
> > FROM or RCPT TO addresses?
>
> To the filter the MAIL FROM and RCPT TO addresses are invalid due to a
> variety of possible reasons. Sadily I have very little influence over what
> the filter can do and cannot do.
>
> >
> > > What I would like to achieve is that ALL messages go to the
> > inhouse filter
> > > relay host irrespective of sender and reciever but that any
> > mail generated
> > > by bounce can be sent via a different transport thus bypassing
> > any potential
> > > problems caused by the filter.
> > >
> > > Advice on this would be greatly appreciated.
> >
> > As far as Postfix is concerned, a bounce message is like any message,
> > the difference being that it has an empty sender address. However,
> > the sender address does not matter. Like most mailers, Postfix has
> > no support for sender-dependent routing.
> >
> > If you want bounces to be sent via a different path, then you have
> > to hack up the bounce server code and add an address transformation
> > to the recipient address.
> >
> > However, it makes a lot more sense to spend the energy fixing the
> > application that rejects valid MAIL FROM or RCPT TO addresses,
> > because the problem is there, not with Postfix.
>
> Agreed but pretty unlikely in the near future. The mail systems are very
> closed systems so I am not too worried about modifying the bounce daemon and
> updating our documentation to reflect this.
>
> It looks like what I would like to do is append a ".bounce" to the
> reciepient of the bounce message. It appears the best place may be in
> bounce.c->bounce_notify_proto().
>
> There appears to be several macros surrounding the parsing of sender that I
> am little confused as to the best way of modifying it safely. I tried
> looking for some domain part modification functions in global and util but
> did not have much luck. Since I am only a casual C programmer I would
> appreciate any guidance in this matter to make these mods safely.
>
> Thanks

In bounce_notify_proto(), see if the sender is a non-empty address
in userdomain form. If so, vstring_strcat() your glop to the end
of the sender. Otherwise the sender address must not be changed,
or disasters happen.

That will be all. I'm standing on my toes all the time and prefer
to spend my energy on solutions that benefit many, rather than
working around problems that should not exist in the first place.

        Wietse

This archive was generated by hypermail 2b27 : Mon Jan 24 2000 - 19:42:36 CST