SMTP Email notifications fail in 4 out of 27 pfSenses
-
Like @johnpoz is saying, the error is on your pfSense firewalls (likely all 4 of them that are not working). Notice in your screen shot you posted in your original message that you have the Email Server name spelled wrong. You have "smpt.office365.com" and it should instead read "smtp.office365.com". You have the "t" and "p" backwards in the name.
-
I blame it on MS, they should clearly allow for both smtp and smpt ;) to account for their userbase ;) hehehehe
Are not fqdn like nukes - you should just have to be close is all ;)
-
Oh my goodness, my eyes. Such a dumb mistake
-
ie the whole DOH joke ;)
-
@johnpoz I think forums needs emoji reactions :)
-
@pfrickroll said in SMTP Email notifications fail in 4 out of 27 pfSenses:
Oh my goodness, my eyes. Such a dumb mistake
Don't feel too bad. I didn't notice the typo either when I replied initially.
-
Serbus even wrote it out for me, i read it like "doh" i know. Tell me something else, i feed dumb
-
We should submit a bug request to MS about it ;)
they should prob register smpt.office356.com etc.. and all the other possible typo scenarios ;) hehehe
-
@johnpoz said in SMTP Email notifications fail in 4 out of 27 pfSenses:
prob register smpt.office356.com
"However, what if one of these bits got automatically flipped due to a solar flare, cosmic rays, or a hardware error? That is one of the 0's becomes a 1 and vice versa.
...
as soon as Remy squatted the aforementioned domains and setup sinkholes to record any traffic, the researcher noticed an uptick in legitimate traffic coming his way.In addition to the traffic destined to windows.com, the researcher was also able to captured UDP traffic destined for Microsoft's time server, time.windows.com, and TCP traffic meant to reach Microsoft's services such as Windows Push Notification Services (WNS) and SkyDrive (former name of OneDrive)."
-
Yeah had seen the bitflipping and ntp article - somewhat relatable sure to such typo domains ;)