On Sat, 28 Mar 2009, fl...@pbartels.info wrote: > I'm not sure what I should do with bounce messages from aliased addresses. > > If X is the sender of a message to A what is an alias for B and my MTA > can't deliver the message to B for some reason, my MTA creates a bounce > messages and sends it to X. > > The bounce message contains informations like: > <B> (expanded from <A>): host HostB [IP] said: ....
This is done in src/bounce/bounce_notify_util.c and AFAIK not "configurable" in main.cf. > I, or rather the user, don't want that X can see the address B or other > informations, like HostB, it's IP or whatever. > > So what is common to do, how did you solve this problem? > (I think I'm not the first with this problem.) > - I can't send it to A/B because there are some problems. > - I can't send it to X because X must not see the alias A > B. > - I'm not going to send it to the postmaster. > > I could filter all bounces, extract the address B or the alias A > B and > find out this way if it is a bounce for an alias. Then I could send a new > bounce to X with less informations. What do you think about this? Backscatter concerns aside, if you really want to bounce mail after accepting it, edit the section of the code that calls bounce_print_wrap() to reveal the alias expansion. This is NOT recommended and likely to void the warranty. :-) -- Sahil Tandon <sa...@tandon.net>
