Greylisting mystery
Posted: 2017-01-07 20:41
Some (considerable) time ago, I was experimenting with greylisting. At the time I determined that it wasn't a good fit for my circumstances, and disabled it - or so I thought.
Today I was looking for something else and happened to click on Greylisting in the Admin console. Lo and behold, Greylisting is enabled. I thought, cool, it's working so transparently, I didn't even know it was on. But then I got to thinking, that can't be.
I searched over a year's worth of logs, and there' s not a single instance of "SENT: 451" in any of them. (I always have SMTP logging on.) I fired up MSSQL and issuedand it came up with zero.
Greylisting settings are:Bypass on SPF and Bypass on A or MX record are both checked (but I know I get plenty of incoming connects that fail SPF and don't have DNS records).
The greylist's whitelist appears to be the default config; there's not like a universal wildcard entry that would bypass everything.
I've checked the IP ranges, and they have the Anti-Spam check box checked.
Is there some other setting somewhere that overrides greylisting?
Today I was looking for something else and happened to click on Greylisting in the Admin console. Lo and behold, Greylisting is enabled. I thought, cool, it's working so transparently, I didn't even know it was on. But then I got to thinking, that can't be.
I searched over a year's worth of logs, and there' s not a single instance of "SENT: 451" in any of them. (I always have SMTP logging on.) I fired up MSSQL and issued
Code: Select all
select count(*) from hm_greylisting_triplets;Greylisting settings are:
Code: Select all
Minutes to defer delivery attempts: 4
Days before removing unused records: 2
Days before removing used records: 65The greylist's whitelist appears to be the default config; there's not like a universal wildcard entry that would bypass everything.
I've checked the IP ranges, and they have the Anti-Spam check box checked.
Is there some other setting somewhere that overrides greylisting?
