Re: spamd greylisting, masking on /24
You really do not need to do this in spamd. Do it in pf. i.e: table nospamd persist file /etc/mail/nogreylist ... no rdr $ext_if proto tcp from nospamd to $mailserver port smtp * Stuart Henderson [EMAIL PROTECTED] [2005-07-26 04:23]: I seem to remember seeing a patch to spamd that makes greylisting only look at the first /24 of the address, but I can't find it after fairly extensive searching with google/marc. Does anyone have a copy they could point me at? The whitelists on puremagic.com (on which greylisting.org's lists are based) don't list networks with a common spool unless more than a /24 is involved (there are some /24 listed with other factors requiring whitelisting, e.g. unique sender addresses per delivery attempt). -- Bob Beck Computing and Network Services [EMAIL PROTECTED] University of Alberta True Evil hides its real intentions in its street address.
Re: spamd greylisting, masking on /24
--On 27 July 2005 13:50 -0600, Bob Beck wrote: You really do not need to do this in spamd. Do it in pf. table nospamd persist file /etc/mail/nogreylist Been doing that for months, but it takes quite a while to add enough networks to be useful, and there's always another round the corner. I don't think I've seen any up-to-date 'greylisting whitelists' that include common-spool senders from /24 and smaller, but those are responsible for most excessive delays I've seen. (The other delays I see are usually shorter [2-4h or so], mostly from ISPs using Exim shunting delayed mail off to another host to shorten queues on their primary relays and not bothering to retry for a while).
Re: spamd greylisting, masking on /24
Practically, I've never found any need to use anything beyond the greylisting.org whitelist in that manner, as well as ensuring I'm running spamlogd correctly so that outbound servers get whitelisted.. At least with our 70,000 lusers worth of mailboxes. -Bob * Stuart Henderson [EMAIL PROTECTED] [2005-07-27 18:12]: --On 27 July 2005 13:50 -0600, Bob Beck wrote: You really do not need to do this in spamd. Do it in pf. table nospamd persist file /etc/mail/nogreylist Been doing that for months, but it takes quite a while to add enough networks to be useful, and there's always another round the corner. I don't think I've seen any up-to-date 'greylisting whitelists' that include common-spool senders from /24 and smaller, but those are responsible for most excessive delays I've seen. (The other delays I see are usually shorter [2-4h or so], mostly from ISPs using Exim shunting delayed mail off to another host to shorten queues on their primary relays and not bothering to retry for a while). -- Bob Beck Computing and Network Services [EMAIL PROTECTED] University of Alberta True Evil hides its real intentions in its street address.
spamd greylisting, masking on /24
I seem to remember seeing a patch to spamd that makes greylisting only look at the first /24 of the address, but I can't find it after fairly extensive searching with google/marc. Does anyone have a copy they could point me at? The whitelists on puremagic.com (on which greylisting.org's lists are based) don't list networks with a common spool unless more than a /24 is involved (there are some /24 listed with other factors requiring whitelisting, e.g. unique sender addresses per delivery attempt).
