Few things are more frustrating than discovering that Microsoft Outlook is receiving emails perfectly—but refusing to send them. For professionals and businesses that rely on seamless communication, this issue can cause delays, missed opportunities, and unnecessary stress. Fortunately, the problem is usually tied to a handful of common causes, most of which can be resolved quickly with the right approach.
TL;DR: When Outlook receives but does not send emails, the issue is usually caused by incorrect SMTP settings, authentication errors, a corrupted Outlook profile, oversized attachments, antivirus interference, or a damaged data file. Checking outgoing server settings and verifying credentials solve the problem most often. Restarting Outlook in safe mode or repairing the data file can also restore normal functionality. With the right troubleshooting steps, most sending errors can be fixed in under 30 minutes.
Below are six proven fixes that work, along with practical guidance on how to apply them.
1. Check Outgoing (SMTP) Server Settings
The most common reason Outlook cannot send emails—while still receiving them—is incorrect Simple Mail Transfer Protocol (SMTP) settings. Receiving emails uses incoming servers (IMAP or POP3), while sending requires SMTP. If SMTP settings are wrong or incomplete, outgoing emails will fail.

Users should verify the following:
- SMTP server address (e.g., smtp.yourprovider.com)
- Port number (typically 587 for TLS or 465 for SSL)
- Encryption method (SSL/TLS)
- Authentication required checkbox enabled
To check these settings:
- Go to File > Account Settings > Account Settings.
- Select the affected email account.
- Click Change and then More Settings.
- Open the Outgoing Server tab.
Ensure that “My outgoing server (SMTP) requires authentication” is checked and that it uses the same login credentials as the incoming server.
This fix alone resolves a large percentage of sending failures.
2. Verify Username and Password
Incorrect login credentials can prevent Outlook from sending emails—even if it appears to be receiving them. Sometimes, incoming mail continues to work temporarily due to cached credentials, while outgoing mail fails immediately.
Common scenarios include:
- Password recently changed
- Two-factor authentication enabled
- App-specific password required
- Account temporarily locked by provider
Users should log directly into their email provider’s webmail portal to confirm that their password works. If two-factor authentication is enabled, an app-specific password may need to be generated and entered into Outlook.
After updating credentials in Outlook:
- Restart Outlook.
- Try sending a test message.
If the problem persists, continue with the next fix.
3. Disable Antivirus Email Scanning Temporarily
Antivirus software can sometimes block outgoing emails—especially if it detects large attachments or scans outgoing SMTP traffic.
Overprotective security settings may:
- Block SMTP ports
- Quarantine outgoing messages
- Interrupt secure outgoing connections
To test whether antivirus software is the culprit:
- Temporarily disable email scanning (not full protection).
- Send a test email.
If sending works, the solution may involve:
- Changing SMTP ports
- Updating antivirus software
- Adding Outlook as an allowed application
Important: Users should re-enable protection immediately after testing.
4. Check Attachment Size Limits
Oversized attachments can silently block outgoing mail. Many providers impose strict sending limits, typically between 20MB and 35MB.
Even if the message appears to send, it may remain stuck in the Outbox if it exceeds size limits.
Signs this is the issue:
- Email stuck in Outbox
- Sending progress bar never completes
- Error message referencing message size
Solutions include:
- Compressing files into a ZIP folder
- Uploading files to cloud storage and sharing a link
- Splitting large attachments into multiple emails
After reducing attachment size, the user should delete the stuck message, restart Outlook, and resend it.
5. Repair the Outlook Data File (PST or OST)
Corrupted Outlook data files can disrupt sending functionality while leaving incoming mail unaffected.
Outlook uses two primary file types:
- PST (Personal Storage Table)
- OST (Offline Storage Table)
If these files become corrupted due to improper shutdown, power outages, or disk issues, sending errors may occur.
Microsoft provides a built-in repair tool called ScanPST.exe.
Steps to repair:
- Close Outlook.
- Locate ScanPST.exe (usually in the Office installation folder).
- Run the tool and browse for the PST file.
- Click Repair.
For OST files, deleting the file and restarting Outlook may trigger automatic recreation and synchronization from the mail server.
This fix is particularly effective when Outlook crashes frequently in addition to sending issues.
6. Create a New Outlook Profile
When all else fails, creating a new Outlook profile often resolves sending problems caused by deep configuration errors.
Profiles store account settings, preferences, and configuration data. Corruption or conflicts within the profile can prevent SMTP from functioning properly.
To create a new profile:
- Close Outlook.
- Go to Control Panel > Mail.
- Select Show Profiles.
- Click Add to create a new profile.
- Set the new profile as default.
After setup, test sending a message. If successful, the issue was profile-related.
This method resolves stubborn issues that do not respond to simpler fixes.
Additional Troubleshooting Tips
If the six primary fixes do not solve the issue, users may also consider:
- Starting Outlook in Safe Mode to disable add-ins
- Updating Outlook to the latest version
- Checking firewall permissions
- Contacting the email service provider to confirm server status
Safe Mode can be launched by pressing Windows + R and typing outlook.exe /safe.
Why Outlook Can Receive but Not Send
Understanding why this happens helps prevent recurrence. Outlook separates incoming and outgoing communication into two distinct processes:
- Receiving → IMAP or POP3
- Sending → SMTP
This separation means one side may function normally while the other experiences authentication, port, or encryption errors. Because SMTP typically requires stricter authentication, it fails more frequently.
By focusing troubleshooting on outgoing server configuration first, users can save significant time.
Conclusion
When Outlook receives but refuses to send emails, the issue is rarely catastrophic. In most cases, it stems from incorrect SMTP settings, authentication problems, oversized attachments, antivirus interference, corrupted data files, or profile conflicts. Methodically applying the six proven fixes outlined above resolves the vast majority of cases.
Rather than reinstalling Outlook immediately, users should start with SMTP verification and credential checks, then move toward data repair and profile recreation if necessary. With systematic troubleshooting, email functionality can typically be restored quickly and efficiently.
Frequently Asked Questions (FAQ)
-
Why can Outlook receive emails but not send them?
This usually happens because of incorrect SMTP server settings, authentication errors, or blocked outgoing ports. Receiving and sending use different protocols, so one can work while the other fails. -
What SMTP port should be used in Outlook?
Most providers use port 587 with TLS encryption or port 465 with SSL. It is best to confirm directly with the email provider. -
How do users fix Outlook emails stuck in the Outbox?
They should check attachment size, delete the stuck message, restart Outlook, and verify outgoing server settings. -
Can antivirus software block outgoing emails?
Yes. Email scanning features in antivirus programs can interfere with SMTP connections. Temporarily disabling email scanning can help identify the issue. -
Will creating a new profile delete emails?
Creating a new profile does not delete emails stored on the server. However, users should back up PST files before making major changes. -
When should someone contact their email provider?
If all local troubleshooting fails, the provider may be experiencing server issues or may have blocked the account due to suspicious activity.
