Your scripts look like they have a good deal of qmail sophistication.
Some years ago I ran qmail 1.0.3, after each major system crash, I would
revisit whether to use qmail, and eventually decided to switch to
qpsmtp+postfix because both seem to have better support. And in fact,
the reason I included /etc/alias was to replace the very useful alias
mechanism in qmail. I really didn't need much, so that was sufficient
for me.
So it seems that among these collections of scripts there are
backscatter solutions for qmail sites and qpsmtp sites. Perhaps one of
the developers can fold these into a contrib folder?
Todd
On 2/5/2011 6:23 AM, Tim Meadowcroft wrote:
On Saturday 05 February 2011 08:38:12 Todd Brunhoff wrote:
I have a small email server that is just for my wife and I. The
biggest problem I have is backscatter (mail received with invalid local
address that bounces to an invalid sender address). So the following
script blocks all of this at the point of receipt, inside qpsmtpd. Could
not find it anywhere else so I wrote this. Comments welcome.
I did a similar thing but seeing how I'd started off using qmail before
discovering qpsmtpd, mine reads the qmail config files /var/qmail/users/assign
including reading alias files configured in there - this way I have a standard
qmail setup with partial wildcards addresses and have aliases for postmaster,
abuse (and qmail handles things like forwarding email on to other addresses
etc).
So I then hand out different email addresses to different people ("tim_XYZ" to
company XYZ etc) knowing that the prefix rule will accept any such email that I
invent, but if any one address leaks or otherwise becomes too spammy then I
block that explicit address with another plugin that runs BEFORE this one
which checks a specific list and refuses anything from its own config list. I'm
not sure if the check_badrcptto is a "standard" plugin or one I simply cobbled
from elsewhere, so it's attached too.
Of course if you don't use qmail for final delivery, then this may not be so
useful but it seemed better than coming up with my own user list and wildcards
and alias mechanisms :)
Cheers
--
Tim
