i do love greylisting, but:
is there a way to bypass greylisting for some hosts/networks?
the obvious problem is with large providers (outlook, googlemail, gmx,...) that keep resending from different IPs, thus keeping the mail in the greylisting for ages.
i know i can whitelist hosts, but afaiu, that means that these whitelisted hosts will completely bypass all anti-spam measures. this is not what i want to do.
so I would like to do any or all of the following, but it should only effect greylisting:
esp. if we could establish (by other means) that the IP is from a static range?
is there a way to bypass greylisting for some hosts/networks?
the obvious problem is with large providers (outlook, googlemail, gmx,...) that keep resending from different IPs, thus keeping the mail in the greylisting for ages.
i know i can whitelist hosts, but afaiu, that means that these whitelisted hosts will completely bypass all anti-spam measures. this is not what i want to do.
so I would like to do any or all of the following, but it should only effect greylisting:
- manually maintain a whitelist of hosts/networks
- use a DNS-based realtime whitelists instead of a manually maintained static one
- use the SPF-entry of a domain (or similar) to exclude an sender from being greylisted
(IP, sender1, receiver2)
tuple), why is it greylisted again when the sender resp receiver address changes (that is: a new (IP, sender3, receiver4)
)? we obviously need such a tuple to establish that the given IP is pertinacious enough when doing delivery attempts; but isn't it safe to assume that once we know that that IP is pertinacious it will stay so for some time?esp. if we could establish (by other means) that the IP is from a static range?