If you want to block all ‘.info’ domains on a server running netqmail-1.06<\/p>\n
I can confirm the badmailfrom wildcard functionality is not included in netqmail-1.06<\/p>\n
Use the badmailfrom-wildcard patch http:\/\/tomclegg.net\/qmail-bmf-wildcard
\neven though it makes no mention of netqmail-1.06, it works.<\/p>\n
Saved below for posterity;<\/p>\n
If (like me) you’re getting lots of unreturnable spam from addresses like “opt-in@mtsopt21.email-info.net”, you want “.email-info.net” in controls\/badmailfrom.<\/p>\n
Without this patch, you would have to list “@mtsopt21.email-info.net”, “@mtsopt22.email-info.net”, etc. separately.<\/p>\n
To install:<\/p>\n
cd \/src\/qmail-1.03
\nwget http:\/\/www.omniweb.com\/wordpress\/wp-content\/uploads\/patch-qmail-badmailfrom-wildcard
\npatch < patch-qmail-badmailfrom-wildcard\nmake qmail-smtpd\ninstall -m 755 qmail-smtpd \/var\/qmail\/bin\/qmail-smtpd\nTo refuse mail from any sender which ends with \".example.com\":\n\necho \".example.com\" >>\/var\/qmail\/control\/badmailfrom
\nYou will still accept mail from foo@example.com unless you add “@example.com” as well:<\/p>\n
echo “@example.com” >>\/var\/qmail\/control\/badmailfrom
\nThe wildcard does not apply to the sender’s local part. “.spam@example.com” will not block mail from example-spam@example.com. It will only block “.spam@example.com” which is probably not what you want.<\/p>\n","protected":false},"excerpt":{"rendered":"
If you want to block all ‘.info’ domains on a server running netqmail-1.06 I can confirm the badmailfrom wildcard functionality is not included in netqmail-1.06 Use the badmailfrom-wildcard patch http:\/\/tomclegg.net\/qmail-bmf-wildcard even though it makes no mention of netqmail-1.06, it works. … Continue reading