Closed aberkvam closed 2 years ago
The outlook.com (port 25) changes are kind of superfluous as there is already blanket whitelisting of outlook.com clients on lines 241-242. That, and the stale outbound.protection.outlook.com (line 253) reference would also need to be removed, or updated to mail.protection.outlook.com for this update to be meaningful. Personally I'm quite happy to just leave outlook.com as a catchall and not have to worry about MS changing their outgoing IP address ranges.
I can't find anything in my mail logs that wouldn't be covered by outlook.com so it looks like lines 241-242 would work. But that brings up a few other questions.
Removes old IP ranges for Microsoft and adds the latest published ranges from https://docs.microsoft.com/en-us/microsoft-365/enterprise/urls-and-ip-address-ranges?view=o365-worldwide