Most of the big providers will simply not deliver an email to a user's inbox unless it meets at least one of these criteria, instead, sending it to a Junk Mail folder, quarantining it, or junking it. DKIM signs email headers, where as SPF is used to indicate which systems are expect (permitted) to send mail on your behalf. SPF and it's slightly more complicated cousin, DKIM, are becoming more and more essential as everyone tries to get a handle on spam. So, not sure if I need to focus on my Exchange server, my firewall, my DNS maybe missing something, or something completely different. The other changes were in the Exchange server and minor updates. The DNS has been updated to reflect the new firewall name, tied to its own IP address, .129. ![]() We changed the firewall name during this process, which is the time-frame when we started having issues. One of those changes was implementing a security certificate from a CA. The issue I'm struggling with is that their firewall is sending back an IP address that is not tied to our mail server DNS entries, it's one digit off, .130 is the IP address they have in their firewall logs when ours is .131.Ī bit of history, we recently made some changes in our own firewall security in order to pass our penetration test. ![]() ![]() The first member I'm working with says their firewall is stopping our messages because of an error around SPF and the "domain of transitioning". We've recently had some issues sending email to some of our members.
0 Comments
Leave a Reply. |