Kris Deugau skrev den 2014-03-28 20:51:
(PBL entries in particular are submitted in part by the netblock
owner/operators themselves, as "IP ranges which should not be
generating
direct-to-MX email traffic". Most other DNSBLs list data in a similar
context; they should not be used for deep inspection of the Received:
chain, just the IP that relayed the message to your server/network.)
PBL is managed by spamhaus and isp owners, with 127.0.0.10 and
127.0.0.11 it can be seperaly tested, i wish all dynamicly ips was
listed in PBL, then spam problems would be gone, since idealy all mail
users would use sasl auth to there mailprovider, with will then not care
of origin ips is listed in PBL or not
here i just use postfix with postscreen rbl testing, thus also dnswl
keeps the most good servers into be tested with content later in
spamassassin, while only a few mails that could be spam are tested,
while postfix reject all the rest via rbl/dmarc/spf here
to the OP: start dkim sign your mails and see if you can be listed in
dnswl.org as a good sender if you have a static server ip, this is the
begin to be not listed as spaming ip
i had for around a year ago a spamhaus pbl listning where my isp could
see it was there need to make that not happend when i paid for static
ip, listed seperate in ripe.net, so i could not at that point send mails
to one more of there custommers with a isp hosted email addr, called
them and got them to agree this was something thay either resolve or get
less money from my so called static ip :=)
btw dhcp in a hostname does not say its dynamic, seperate listning is
best prove to its a static, when my ripe listning is gone, its will be
static pool, where there could be silly or not silly, dynamic clients in
:(
