Viktor Dukhovni wrote: > > > - You may want to "preserve the envelope", by generating a > > > recipient-specific bcc address. Just "always_bcc" fails > > > to record "bcc" recipients, and may record header recipients > > > who weren't actually (envelope) recipients of the message. > > > > could you please elaborate on that (off-list is okay with me), because I > > don't seem > > to understand your point here. > > This copies only the message headers and body, but fails to capture the > message envelope, which contains the true recipient list. With > per-recipient addressing in "recipient_bcc_maps", and provided the > archive system captures the message envelope, you don't lose that (IMHO > essential) information. > > MAIL FROM:<[email protected]> > RCPT TO:<[email protected]> > RCPT TO:<[email protected]> > DATA > From:<[email protected]> > To: <[email protected]> > Subject: Let's commit fraud > > ... > . > > With "always_bcc" one might assume that the message went to > "fake-recipient", where in real-life it was sent to "bcc1" and "bcc2". > With per-recipient bcc addresses that are captured by the archive, > this is not the case.
MailStore only states the "always_bcc" approach in their manual https://help.mailstore.com/en/server/index.php?title=Archiving_Emails_from_Linux-based_Email_Servers#Archiving_Incoming_and_Outgoing_Emails_Directly AFAIK, Mailstore only support this "basic mode" where it uses the header information when importing from generic servers or the specific Exchange/Office365 Journaling format. Additionally, I have only a single destination email address available to import into the archive, as each email address specifies which (customer) archive this mail should be imported as this is a multi tenant software. With your approach, I would need a catchall at the archive software if I understand correctly. We could however try to implement the Exchange Journal format. This creates a new email, adds the envelope from and to address to the body, and then attaches the actual email as an eml attachment. So I could either write a script as a milter or use a service in master.cf that calls a script and passes the envelope and mail data to the script and the script then builds a new email in Exchange Journal format and transfers it directly to the archive gateway server without going through postfix again. If you're bored feel free to send in suggestions for the script :) ^^ Otherwise I'll use always_bcc for now and try to figure out the script in a few weeks when I have more time. Thanks! Cheers, Simon
signature.asc
Description: PGP signature
_______________________________________________ Postfix-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
