> > It appears you assume that there is mail received
> > to attach headers to.
>
> There is mail, if you use rblcheck instead (which is what I suggested).
Ahh, but I would like to stop the spammers before they
even get the mail through and chew up resources (memory,
disk, etc.).
> > rblsmtpd uses the lists which contain IP addresses
> > of SMTP servers. It rejects them before *anything*
> > happens. This is the intended behaviour of most
> > of this spam prevention, to limit the amount of
> > resources used.
>
> I use it -- I know how it works. However, I only block RBL hosts this
> way -- I allow the other messages through because of poor listings on
> the RSS, etc. and would appreciate a tool that just added such a mail
> header as I suggested.
I agree. Most if not all of my users don't know
or want to know about putting in filters. Its typically
a yes/no thing, either they want all mail or have it filtered.
> > I was only thinking of allowing a recipient check
> > also to see if a user and/or virtual domain would
> > like to allow SPAM to be recieved also. If not,
> > drop the connection right then & there.
>
> This requires maintaining the list of virtual domains / users that want
> specific options.
Exactly. For me, I just wanted to set a default, and list
the exceptions to the rule. More complicated rules can
be setup, but I don't need it.
Thanks,
Brian
