SMTP Email notifications fail in 4 out of 27 pfSenses

bmeeks

@pfrickroll said in SMTP Email notifications fail in 4 out of 27 pfSenses:

@bmeeks All firewalls have same configuration for SMTP but only 4 receive that particular error as shown in my screenshot. I have correct time on firewalls.

I am kind of new to Office365, I looked around in admin center in message center, mail flow and alerts but didn't find anything unusual and no trace of emails from those 4 firewalls. Where do I have to look specifically?

Did you see the other replies in this thread? I failed to notice that you have misspelled the email server name. You typed "smpt" instead of "smtp" in the email host. Fix that and see if it then works.

johnpoz

@pfrickroll said in SMTP Email notifications fail in 4 out of 27 pfSenses:

Where do I have to look specifically?

No your never going to connect there.. Because its not smpt is its SMTP..

You have the wrong address..

Which is why its DOH!!

bmeeks

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.

johnpoz

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 ;)

pfrickroll

Oh my goodness, my eyes. Such a dumb mistake

johnpoz

ie the whole DOH joke ;)

pfrickroll

@johnpoz I think forums needs emoji reactions :)

bmeeks

@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.

pfrickroll

@bmeeks

Serbus even wrote it out for me, i read it like "doh" i know. Tell me something else, i feed dumb

johnpoz

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

SteveITS

@johnpoz said in SMTP Email notifications fail in 4 out of 27 pfSenses:

prob register smpt.office356.com

https://www.bleepingcomputer.com/news/security/hijacking-traffic-to-microsoft-s-windowscom-with-bitflipping/

"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)."

johnpoz

@steveits

Yeah had seen the bitflipping and ntp article - somewhat relatable sure to such typo domains ;)