Am 20.10.2014 um 14:18 schrieb Robert Moskowitz:
SInce this is about mail and spam, I thought this might be a good place
to ask about nolisting:

http://en.wikipedia.org/wiki/Nolisting

I get ~ 7000 messages/day on my server, with ~70% getting tagged as spam.

This is really private mailserver for my side consulting business and
for all the standards and support lists I am on.

I am in the process of building a new server that I hope to launch
tonight: Redsleeve6 (on
armv7/Cubietruck)/postfix/dovecot/spamassassin/clamav/amavis-new.

I a friend recommended I use nolisting to reduce the amount of spam
messages to scan for spam.  I tried the single fake MX record as
discussed in the wiki. Port 25 is blocked on the first MX entry. No
changes in spam received.

that may be the mistake, just reject temporary there

many bots don't retry but if there is no connect the may fall
back on the primary MX in the same second, the other benefit of the temp reject is that the bot may think this is greylisting and come back on the primary 10 or 15 minutes later

well, within that 10 minutes they chances to be in RBLs is high

So I was told that this simple single MX record may not work.  To have
TWO fake low value MX records and one high value like:

MX 10 bad.foo.com
MX 20 bad2.foo.com
MX 30 me.foo.com
MX 40 bad3.foo.com

And this did not make any difference in % of spam.  I seem to be
receiving the same amount.  So either the spammers that know about me
use realy MTAs or have updated their SMTP to process MX records right.

So is there any experience here with nolisting?

* postscreen
* two ip-addressess
* backup MX for the second
* postscreen_whitelist_interfaces = !<backup-mx-ip>, static:all

the stats below are unique IP's

most bots starting on the backup-MX never come back
the ones which come back are mostly catched by RBL's

some big legit senders start also on the backup, hence temp-reject because they come back with proper behavior later on the primary

Default-MX:         31400
Honeypot-MX:        16906
Honeypot-Only:      14062

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to