![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Links
Active Entries
- 1: sometimes, I think of ponies
- 2: Careless People
- 3: let’s all go to the EXIT
- 4: alt text issues
- 5: the delicate art of text replacement
- 6: thinking about someone I should not bother thinking about
- 7: the media may not care, but ICE is still running roughshod over LA this July 4th
- 8: Call your Republican Senators RIGHT NOW.
- 9: Yes, establishment Democrats of New York, “vote blue no matter who” still applies
- 10: as a treat
Thoughts & Ideas
Date: 2016-01-26 11:47 pm (UTC)Starting with the most obvious: Was milter-greylist one of the things updated? If so, I'd be investigating the changes.
Does your DNS still work? Is there anything blocking DNS requests on either UDP or TCP? (Recent DKIM keys are often big enough to require TCP for the DNS, but sometimes TCP DNS is broken while UDP DNS works.) Can you do the DKIM request yourself with dig? (e.g. "dig -t txt 20120113._domainkey.gmail.com" works for me.)
It may be worthwhile to grab the Debian source of milter-greylist, find where the DKIM checking happens, disable it in the code, then do your own build. ("debuild -us -uc", if I remember right.)
Or maybe it would be easier/better just to find a different greylist tool that doesn't try to act outside its scope. (I see one called "gross" that looks like it should work for all mail servers, but I don't know more than the package description.)