You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allowing incoming emails to this SMTP server by means of an upstream server.
This eliminates gaps when using IMAP and POP3 where the polling interval could be more than the time that messages have been received into the mailbox and been deleted or modified manually or with users filters.
A popular tool piler uses something similar to this request.
Proposed Solution
Postfix and other upstream mailservers can utilize something similar to always_bccsender_bcc_maps or recipient_bcc_maps, which could map user@realdomain.com -> user@mailarchiver.realdomain.com, or be able to determine the to, cc, bcc from the headers via a global bcc email address and route the messages accordingly to users either auto provisioned or manual users.
This server shouldn't obviously send mail outbound and should fail silently should there be NDRs or loops. Bonus would be ability to add listening controls as to what interface, port to listen on, and TLS support.
This discussion was converted from issue #285 on February 05, 2026 09:44.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Feature Description
Allowing incoming emails to this SMTP server by means of an upstream server.
This eliminates gaps when using IMAP and POP3 where the polling interval could be more than the time that messages have been received into the mailbox and been deleted or modified manually or with users filters.
A popular tool piler uses something similar to this request.
Proposed Solution
Postfix and other upstream mailservers can utilize something similar to
always_bccsender_bcc_mapsorrecipient_bcc_maps, which could map user@realdomain.com -> user@mailarchiver.realdomain.com, or be able to determine the to, cc, bcc from the headers via a global bcc email address and route the messages accordingly to users either auto provisioned or manual users.This server shouldn't obviously send mail outbound and should fail silently should there be NDRs or loops. Bonus would be ability to add listening controls as to what interface, port to listen on, and TLS support.
All reactions