Hi,
I would like to suggest an optional feature for mailcow.
When an external application, website, CRM, ERP system, etc. sends an email through mailcow using authenticated SMTP, the message is delivered correctly, but no copy is stored in the sender’s Sent folder.
For example:
website → authenticated SMTP → mailcow → recipient
If the website authenticates as info@example.com, I would like mailcow to automatically store a copy of the outgoing message in the Sent folder of info@example.com.
Of course, mail clients and webmail normally save their own copy through IMAP. But many external applications only support SMTP, which means these sent messages are currently missing from the mailbox history.
It would be very useful to have an optional server-wide setting, for example:
“Store authenticated SMTP submissions in the sender’s Sent folder”
Ideally, this would:
work automatically for all existing and future mailboxes;
use the authenticated SMTP username to determine the mailbox;
work regardless of the IP address or application sending the message;
store the message directly in the normal Sent folder;
optionally be configurable globally, per domain or per mailbox.
I know this can probably be achieved manually using Postfix/BCC/Sieve rules, but having this as a native mailcow feature would be much cleaner and easier to maintain.
Microsoft 365, for example, can provide similar server-side sent-item behaviour, and I think this would be especially useful for mailcow installations that are also used as SMTP servers for websites and business applications.
Would this be something that could be considered for a future version of mailcow?
Thanks!