Raja asked John, and then John asked us, about this:
| >X-Actual-Recipient: rfc822; |IFS=' ' && exec /usr/local/bin/procmail -f- ||
| >exit 75 #kanagala(_at_)mailhub(_dot_)Cadence(_dot_)COM
MTAs like sendmail or postfix (qmail is in a universe of its own and writes
different error messages, which a user can control with its "bouncesaying"
utility) will do that: if you bounce a message by returning from a pipe in
.forward with a non-zero exit status, it will air the contents of your
.forward, although they won't all stick the domain on the end like that as if
the pipe were an unqualified local address.
| What do we have set up incorrectly below
| to get the .forward included accidentally as
| part of the spam-bounced email?
Unless you have other reasons to switch to qmail, you're doing nothing wrong
at all. The workaround I use is to disguise the call in .forward. Procmail
can be invoked under any name, but unless the first eight characters of the
basename are "procmail" there's an implicit -d option. So on one system, for
example, I have a symlink in ~/.invalid to the procmail binary and this in
.forward:
"|exec $HOME/.invalid -f- dattier"
If my .forward is displayed in a bounce message, the recipient isn't sure what
to make of it. It seems that the ISP has left my home directory around with a
marker that the account is invalid. (I could have called it ".canceled" or
".closed" instead.)
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail