+ [EMAIL PROTECTED]:
| Qmail use the address #@[] as the envelope sender address for double
| bounces. The messages with this sender address are rejected by
| Microsoft Exchange IMS with this error (from qmail logs):
|
| Connected_to_NNN.NNN.NNN.NNN_but_sender_was_rejected.
| /Remote_host_said:_553_malformed_address:_<#@[]>/
|
| I have read the RFC821 (SMTP) and it seems to me that this address
| is ilegal. [...]
I am no RFC lawyer myself, but it looks like you're right. In fact,
if memory serves, that address was chosen because practically all
servers will accept it as a sender address, but at the same time it is
guaranteed to be unreplyable, which puts an effective stop to bounce
loops.
[I skipped the part about patching qmail to use a different double
bounce sender, since you already discovered that an external solution
works just as well.]
| Furthermore I tried another solution. I forward double bounces but
| changing the envelope sender with this .qmail file:
|
| | qmail-inject -f"<>" postmaster@exchange-server
|
| However, if this forwarding fails, this configuration could produce
| a mail loop. Any suggestions?
First, doesn't that make qmail-remote say "mail from:<<>>"?
Second, you're right about the loop. I would rather do something like
|NEWSENDER=triplebounce forward postmaster@exchange-server
and have .qmail-triplebounce contain
|echo 'Aaack! Pfhht! Triple bounce!'
which will just put that message in the log and discard the mail.
- Harald
