Send & Receive Issues

Troubleshoot Slow Office 365 SMTP Attachment Delivery

Adam DavisAdam Davis Nov 20, 2026 868 views

Question details

Identify why an application takes several minutes to send Microsoft 365 SMTP messages with attachments.

How to Troubleshoot Slow Office 365 SMTP Attachment Delivery
Product
Microsoft 365 SMTP and Outlook
Device & OS
not provided
Scenario
An application sends messages through smtp.office365.com on port 587 with TLS and a 600,000-millisecond timeout.
Observed behavior
Messages with small attachments can take several minutes to send; one reported message took about 10 minutes.
Before you start

Record the send start and end times, recipient address, attachment size, and time zone for a delayed message. Confirm that you can test the same account in Outlook and access application logs or ask an administrator for a Microsoft 365 message trace.

Solution 1Recommended

Compare SMTP delivery with an Outlook Exchange test

Use the same account in Outlook to determine whether the delay is specific to the application or its SMTP path.

1
Add the account to Outlook

In Outlook, open account settings and add the same Microsoft 365 account using Exchange, rather than configuring it as an SMTP-only account.

2
Send a test attachment

Compose a message to a test recipient, attach a file larger than 50 KB, such as a 5 MB file, and click Send. Record when you send it and when it arrives.

3
Compare the results

Send a comparable message from the application to the same recipient and compare the timings. A quick Outlook test and a slow application test point toward the application's SMTP configuration or network path, although they use different protocols.

4
Trace the delayed message

Ask a Microsoft 365 administrator to open the Exchange admin center and run a message trace using the sender, recipient, and time range. Compare the trace with the application timestamps to see whether the delay occurred before or after Microsoft 365 accepted the message.

Compare SMTP delivery with an Outlook Exchange test
Interpret the comparison: A successful Outlook test does not by itself rule out an SMTP-specific Microsoft 365 or network issue. Continue with the SMTP and network checks if the application remains slow.
Free Microsoft Office alternative

Prepare Office Attachments with WPS Office

WPS Office is a free, lightweight alternative for creating and editing documents you need to send. Its familiar interface and Microsoft Office format compatibility make it easy to move existing files into your workflow. It does not fix Microsoft 365 SMTP delivery delays.

Create and edit files before attaching them to emailCompatible with Microsoft Office formats such as DOCX, XLSX, and PPTXFamiliar interface for working with existing Office filesFree and lightweight office suite
microsoft office alternative - wps office

Frequently Asked Questions

Should port 587 use SSL or STARTTLS?

For Microsoft 365 SMTP client submission, configure smtp.office365.com on port 587 and use STARTTLS. Check the application's SMTP settings to ensure it does not expect implicit SSL immediately upon connection.

How can I tell whether Microsoft 365 caused the delay?

Ask an administrator to run a message trace in the Exchange admin center using the sender, recipient, and time range. Compare the trace timestamps with the application's send logs to identify whether the delay occurred before or after Microsoft 365 accepted the message.

Why test the same account in Outlook?

Adding the account in Outlook using Exchange mode provides a comparison with the application's SMTP path. If Outlook sends a similar attachment quickly, investigate the application, SMTP configuration, and network path; the test does not conclusively rule out an SMTP-specific service issue.

Does a 600,000-millisecond timeout cause a 10-minute delay?

It permits the send operation to wait up to that timeout; it does not identify the cause of the wait. Add timestamps around connection, authentication, and client.Send(msg), and check retry and network logs.