Do not use an IP address for the Microsoft 365 or Office 365 server, as IP Addresses are not supported.įor information about TLS, see How Exchange Online uses TLS to secure email connections and for detailed technical information about how Exchange Online uses TLS with cipher suite ordering, see Enhancing mail flow security for Exchange Online. Some network firewalls or ISPs block ports, especially port 25, because that's the port that email servers use to send mail. Port: Port 587 (recommended) or port 25 is required and must be unblocked on your network.Transport Layer Security (TLS): Your device must be able to use TLS version 1.2 and above.Mailbox: You must have a licensed Microsoft 365 or Office 365 mailbox to send email from.If SMTP AUTH is intentionally disabled for the organization or the mailbox being used, you must use Option 2 or 3 below. To find out more about OAuth, see Authenticate an IMAP, POP, or SMTP connection using OAuth. Otherwise, you'll need to use Basic Authentication (which is simply a username and password) to send email from the device or application. Authentication: If possible, we recommend using Modern Authentication in the form of OAuth.Requirements for SMTP AUTH client submission With this method, you can send email from any location or IP address, including your (on-premises) organization's network, or a third-party cloud hosting service, like Microsoft Azure.This bypass can help protect your company IP addresses from being blocked by a spam list. This method bypasses most spam checks for email sent to people in your organization.SMTP AUTH client submission allows you to send email to people in your organization and outside your company.The following diagram gives you a conceptual overview of what your environment will look like. If your device recommends or defaults to port 465, it doesn't support SMTP AUTH client submission. To find out more about configuring your own email server to send mail to Microsoft 365 or Office 365, see Set up connectors to route mail between Microsoft 365 or Office 365 and your own email servers. In fact, you might find it easier to configure and manage an on-premises SMTP server to relay messages from your devices and applications, especially if you have many devices and applications that send email. Use an on-premises email server (Exchange Server or any other SMTP server) to relay mail if your device is unable to meet the previous requirements for connecting to Microsoft 365 or Office 365.Depending on your requirements, use direct send (Option 2) or Microsoft 365 or Office 365 SMTP relay (Option 3) instead.If your device or application doesn't support TLS 1.2 or above, you have the following alternatives: As long as your scenario meets the requirements for SMTP AUTH client submission, the following settings will enable you to send email from your device or application.Įnter the sign-in credentials of the hosted mailbox being usedĭetermine what version of TLS your device supports by checking the device guide or with the vendor. How to set up SMTP AUTH client submissionĮnter the following settings directly on your device or in the application as their guide instructs (it might use different terminology than this article). The email address of the account that's used to authenticate with Microsoft 365 or Office 365 will appear as the sender of messages from the device or application. To configure your device or application, connect directly to Microsoft 365 or Office 365 using the SMTP AUTH client submission endpoint .Įach device or application must be able to authenticate with Microsoft 365 or Office 365. You want to send email to people inside and outside your organization.You want to send email from a third-party hosted application, service, or device.This option supports most usage scenarios and is the easiest to set up. For more information, see Enable or disable authenticated client SMTP submission (SMTP AUTH) in Exchange Online. SMTP AUTH is disabled for organizations created after January 2020 but can be enabled per-mailbox. You must also verify that SMTP AUTH is enabled for the mailbox being used. To find out more about OAuth, see Authenticate an IMAP, POP or SMTP connection using OAuth. As a result, there are no plans to disable Basic Authentication for SMTP AUTH clients at this time. Although SMTP AUTH now supports OAuth, most devices and clients have not been designed to use OAuth with SMTP AUTH. We recommend using Modern Authentication when connecting with our service. This option is not compatible with Microsoft Security Defaults.
0 kommentar(er)
