I thinks it's a good starting point, Steve. And it's much better than doing it manually as I did :-)
Anyway... I rapidly tested delivery time from my office365 account: - WL disabled: 15 hours - WL enabled: just a few minutes postgrey enabled. Thanks! a. Il 25/11/15 04:45, Steve Jenkins ha scritto:
On Tue, Nov 24, 2015 at 10:32 AM, proto <alessan...@protodigital.net <mailto:alessan...@protodigital.net>> wrote: Thank you Steve. I did something similar some weeks ago because I had to get in contact with MS Support urgently. I remember I had to get outbound gateways IPs from <spf.protection.outlook.com <http://spf.protection.outlook.com>>, but I didn't use <ns1.msft.net <http://ns1.msft.net>>. Actually in your script this NS return no SPF records (IP and includes). I think this WL could be completed with records from: spfa.protection.outlook.com <http://spfa.protection.outlook.com> spfb.protection.outlook.com <http://spfb.protection.outlook.com> a. Alessandro: I've updated the script to also query spf.protection.outlook.com <http://spf.protection.outlook.com>, spfa.protection.outlook.com <http://spfa.protection.outlook.com>, and spfb.protection.outlook.com <http://spfb.protection.outlook.com>: https://gist.github.com/stevejenkins/b8898f3632561f9999f4 My scripting and sed skills are NOT that strong, so I'm certain there are many more elegant ways to do that I'm trying to do... including better automation of parsing through the original SPF record and figuring out the right thing to do. But whatever it's worth, the script now grabs more IPs from Microsoft. I also think it's crazy that MSFT's primary name server's aren't updated, so that I have to use two different nameservers in the script. I've half a mind just to query Google's 8.8.8.8 nameserver for the correct MS values... because it got them all right in my tests. LOL SJ
