Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: Sahil Tandon (sahiltandon.net)
Date: Sat Mar 28 2009 - 17:42:17 CDT
On Sat, 28 Mar 2009, flosspBartels.info wrote:
[please keep this thread on-list]
> Zitat von Sahil Tandon <sahiltandon.net>:
>> On Sat, 28 Mar 2009, flosspBartels.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. :-)
> As I said I'm not familiar with the RFC's about DSN messages. But if
> they allow it, wouldn't it be nice if a config option exists that allows
> not attaching the received DSN and just sending a bounce back to the
> sender (X), like defined in $bounce_template_file ?
You can modify $bounce_template_file as explained in bounce(5), but this
does not change what appears below the template. It would be useless to send
a bounce without specifying the recipients to whom it applies or without
providing reasons for the non-delivery. And from the RFC: "A single
notification listing all of the failed recipients or separate notification
messages MUST be sent for each failed recipient."
Sahil Tandon <sahiltandon.net>