Guy writes:
Hi,
We've intentionally introduced a mail loop within a maildrop filter
file. The logs show that the message has been bounced, but the bounce
message doesn't seem to go anywhere.
maildrop doesn't send bounces. If mail delivery fails, it terminates with
the error code, and the mail server is responsible for creating and sending
the bounce. When maildrop terminates with a non-zero exit code, its job is
done. Your mail server is completely responsible for creating and sending
the non-delivery report.
The log shows this:
Aug 26 13:01:24 stoat postfix/pickup[14030]: 99AD5A4037: uid=1510 from=<>
Aug 26 13:01:24 stoat postfix/cleanup[22073]: 99AD5A4037:
message-id=<4a04...@mail.gmail.com>
You'll need to ask this on the Postfix list. I would guess that if Postfix
detects a bouncing mail loop, it would simply discard the message.
I'm running maildrop 2.0.4 and postfix 2.5.1 on Ubuntu 8.04. Do I need
to explicitly list the sender with the -f option when piping to
maildrop or is there likely some other problem with my config?
Setting -f has no effect as far as bounces are concerned. When maildrop, or
any mail delivery agent, terminates with an error code, the -f option has no
effect.
3 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] No bounce message fro...
