On Fri, Apr 21, 2017 at 11:25:14AM +0200, Markus Rosjat wrote: > > so if you have spamd in place in greylisting mode and you have customers > that work with people who use Office365 as a service you will get calls that > emails are delayed for a freaking long time and if you check the ip range > that outlook.com could send from you get scared.
start with $ host -ttxt outlook.com and follow the includes to the very end. Then weep. TL;DR: last time I looked that expanded to eighty-some *networks* of varying sizes. https://github.com/akpoff/spf_fetch fed the relevant domains is one solution, and in addition you will find my collection of manually maintained SPF sedimentation is available at https://home.nuug.no/~peter/nospamd The problem is that the 'architects' behind outlook.com and their ilk are really not on board with the idea that having some tiny bit of control over where your mail comes from is a good idea, but they were made to comply with the SPF/DKIM/DMARC scheme (straight out of the Rube Goldberg school of engineering), which is one of those endless and endlessly tiresome artifacts of the "something has to be done", "this is something" 'system architect' responses. -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.
