I would expect to not be able to use the SMTP relay from anywhere except the IP address nominated in the connector record. Surely this is a vulnerability that needs to be closed. So, at this point, I can relay an e-mail from any smtp client, on any computer, with no authentication, not using TLS, to anyone as long as both organisations use office 365. I was only blocked from relaying an e-mail if the address I'm sending to is not an office 365 address. I tested further andįound that I could also relay e-mails from any IP address, not just the one I nominated in the connector setup. I added the public ip address of our server in the connector setup.Īs part of the setup, I used telnet to connect to the SMTP endpoint and was surprised that I could connect to this endpoint not only from our nominated IP address, but from any IP address. I followed the instructions in the article, setting up a connector in our office 365 portal exchangeĪdmin page. We need to send e-mails to addresses outside the organisation, so option 2 (direct send) was not an option, so we tried option 3 (Office 365 SMTP relay). It takes 15-20 seconds to send each e-mail. Im trying to get scan to email working again (it was setup previously via their old Exchange server) and I was able to get it working by setting up a virtual SMTP server in their new 2012 Essentials server but its problematic and I want to get away from using any server if possible and. This option works, but does not perform well. I have a client with an iR-ADV C2030 who just migrated to Office 365 and no longer have an Exchange server. How to set up a multifunction device or application to send email using Office 365 We started using option 1 (SMTP client submission) in the We've been using the Office 365 SMTP service from our server for a few months now.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |