Doug Clements writes:
Greetings,
I'm having an issue where users are setting up filters with sqwebmail that
forward all mail destined for them to another address. This is all fine and
dandy until that address has a problem, and bounces. The bounce then comes
back to the mailbox, and gets forwarded (and bounced) again. This basically
starts an infinite loop of forward/bounce, and chews up disk space rather
rapidly.
sqwebmail seems to be setting up a normal 'to' or 'cc' forwarding in the
mailfilter file.
I was wondering if there was some sort of bounce detection I could set in the
filters (or in sqwebmail), as a maildrop default, or even with qmail (even
though that's a little off-topic).
Thanks for any input..
There are a couple of possibilities.
1) Enter an explicit rule via sqwebmail looking for the From: header on
a bounce that appears to be a postmaster bounce. Or, perhaps, key off
the subject being the subject on a bounce. If the rule matches,
deliver the message to INBOX, with this being the first rule.
2) Alternatively, maildrop reads /etc/maildroprc first, before reading
.mailfilter. Enter the same kind of rules, by hand, into /etc/maildroprc
and have it deliver to $HOME/Maildir explicitly, then terminate without
even reading the .mailfilter, in the event of a bounce.
5 messages in net.sourceforge.lists.courier-maildrop[maildropl] Re: Detecting and not for...
