My outgoing Mails are not saved over IMAP in the Sent Folder and i cant see them in my Inbox the normal Inbox works fine and Trash too, what can I do?
I don’t think this works. All you can do is send and see your inbox.
Hello @henneberg
there are two “popular” workaround that I use in my projects:
Send every email to a bcc address, so at least you can check there what went out
Build a custom communication module which stores records and the communication is send out from there.
But both mostly workarounds and the standard Sent folder is not being used.
Yeah, I’m not sure if this functionality was just left out, or it’s a bug and it’s supposed to work. It worked in the old sugarCE and you could even get subfolders, but since the re-design of the email, I’m not sure if this is a bug or just not developed. It seems silly you have to connect a sent and trash folder, but there are no ways to view them in SuiteCRM.
That’s really an issue for multiple customers.
I’ve added a bug report:
opened 04:00AM - 22 Jan 26 UTC
Type: Bug
### Issue
See this topic:
https://community.suitecrm.com/t/suite-crm-dosent-sa… ve-outgoing-mails-in-sent-folder-with-imap/93558/2
When I sent out an email from the CRM, there is no evidence in the sent folder of that.
I expected that I'm out to select a sent folder so that I can see the sent mails there.
(I'm using traditional IMAP / SMTP connections)
That seemed to have been working on SugarCE before but now now anymore.
It's holding multiple customers back from using E-Mail in the CRM (and/or they have to employ workarounds).
### Possible Fix
_No response_
### Steps to Reproduce the Issue
```bash
1. Send an email from the CRM
2. Check your sent folder in Thunderbird or similar
```
### Context
_No response_
### Version
8.9.2
### What browser are you currently using?
Chrome
### Browser Version
_No response_
### Environment Information
MariaDB, PHP 8.3
### Operating System and Version
Ubuntu 24 LTS
1 Like
tapio
19 February 2026 13:29
6
I have proposed a solution for this Issue.
develop ← eleknader:fix/imap-sent-append-minimal-pr
Kind Regards,
Tapio
2 Likes
rsp
19 February 2026 14:37
7
Thank a lot! @tapio
All committers have signed the CLA.
develop ← eleknader:fix/imap-sent-append-minimal-pr
opened 01:17PM - 19 Feb 26 UTC
## Summary
This PR fixes **SuiteCRM-Core #839** by ensuring that emails sent … via outbound account flows are appended to the configured IMAP **Sent** folder.
The scope is intentionally minimal and limited to:
- `core/backend/Emails/LegacyHandler/Mailers/LegacyMailer.php`
- `public/legacy/modules/Emails/Email.php`
## Root Cause
SuiteCRM had two outbound send paths that could successfully send email but still miss IMAP Sent append:
- Backend legacy mailer flow (`LegacyMailer`)
- Legacy outbound flow (`Email::sendFromOutbound`)
As a result, users could see successful delivery to recipients, but no copy in the IMAP Sent folder.
## What Changed
### 1) Backend legacy mailer path (`LegacyMailer.php`)
- `LegacyMailer::sendEmail()` now resolves the outbound account id and performs a best-effort IMAP Sent append after successful send.
- Added a focused inbound account resolver based on `inbound_email.outbound_email_id`, with user-preferred lookup first and a safe fallback.
- Ensured `$mail->oe` is set in `setMailer()` so `NonGmailSentFolderHandler` behaves consistently.
### 2) Legacy outbound send path (`Email.php`)
- `Email::sendFromOutbound()` now calls a dedicated helper to append to IMAP Sent after successful send.
- Extracted clear helper methods:
- `storeSentMessageInSentFolder()`
- `resolveInboundEmailIdForSentFolder()`
- Kept logic defensive and readable without changing feature scope.
## Behavior
- Email send remains authoritative: if Sent append fails, send still succeeds.
- IMAP Sent append is best-effort and non-blocking.
- No changes to Graph transport logic.
- No database schema changes.
## Why This PR Is Minimal
- No cross-module refactors.
- No UI changes.
- No unrelated email processing changes.
- Only the two files needed for the IMAP Sent append gap.
## Validation
- `php -l core/backend/Emails/LegacyHandler/Mailers/LegacyMailer.php`
- `php -l public/legacy/modules/Emails/Email.php`
## Description
## Motivation and Context
## How To Test This
## Types of changes
- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to change)
### Final checklist
- [ ] My code follows the code style of this project found [here](https://docs.suitecrm.com/community/contributing-code/coding-standards/).
- [ ] My change requires a change to the documentation.
- [ ] I have read the [**How to Contribute**](https://docs.suitecrm.com/community/contributing-code/) guidelines.
1 Like