After three days of troubleshooting i finally figured it out.
Office 365 smtp relay stopped working.
Before you get started testing first ensure you know what.
I also tried using the smtp server ip address instead of the domain name and tried using port 25 as well.
The easiest way to do that is to use powershell.
A common reason for issues with microsoft 365 or office 365 smtp relay is a blocked ip address.
I also tried setting the dns domain name field with office 365 domain name as recommended is some reddit page but the problem still persists.
This can be caused by a number of issues.
The queue folder quickly filled up with over a hundred e mails so what could have caused this problem.
August 2017 office 365 exchange online.
Relaying email via office 365 suddenly stopped working.
Senders are not bound by the 30 messages per minute or 10 000 recipients per day limits.
Had a client whose smtp server suddenly stopped sending scan to e mails to their domain cloud office 365 e mail from their on premise smtp server.
In this section we ll create some powershell scripts to allow you to easily ensure the connector is working properly.
After creating the connector prepare to test it out.
I took about 45 minutes after submitting the form for office 365 to start accepting emails relayed from this ip address.
Microsoft 365 or office 365 smtp relay has higher sending limits than smtp client submission.
Testing the office 365 smtp relay connector with powershell.
I set up my printer for microsoft 365 or office 365 smtp relay but it s not sending email or my device was sending email using smtp relay but it stopped working.
We have not changed any tls settings or enabled disabled any ciphers in the past few months.
Microsoft 365 or office 365 smtp relay does not require the use of a licensed microsoft 365 or office 365 mailbox to send emails.
Relay via office 365 stopped working client host blocked using spamhaus.
Office 365 smtp relay quit working.
Thank them all for helping but it s not you.
