On 2015-02-22, Markus Kolb <open...@tower-net.de> wrote:
> Why you'd like to whitelist yahoo.com or gmail.com or any other
> non-related smtp?
> I think whitelisting makes only sense for smtps you control or are
> somehow in relation to your network.
Because some of these large senders send mail from multiple servers,
either with a shared mail queue, or behind a NAT where the source
address can change for different retries.
It is fairly common for graylisting implementations to mask on a
/24 network boundary, and many senders seem to take advantage of this
by keeping within a /24. Some of the published "greylisting whitelists"
were refusing to accept submitted /24's.
spamd doesn't do this, it does a full match on the IP address,
so this type of sender configuration introduces bigger delays
(and sometimes total failures) with spamd, especially on smaller
receiving sites. (Bigger sites usually have enough volume of mail
from these larger senders that they stay whitelisted anyway).
Anyway for yahoo, to avoid this sort of delay, perhaps it makes
sense to exempt all of their bgp-announced nets.
$ peval AS5779
({206.190.32.0/19, 206.190.48.0/20, 206.190.60.0/22, 206.190.58.0/23,
206.190.57.0/24, 206.190.49.0/24, 205.172.212.0/22, 205.172.214.0/24,
205.172.215.0/24, 205.172.213.0/24, 170.118.0.0/16, 63.250.192.0/19,
63.250.192.0/20, 63.250.208.0/20})
