X-Envelope-To Receipient is always Pilerhost fake Mailaddress

[Karsten Bandlow]

I archive Mails from an external Mailserver. All Mails are forwarded to another Mailserver with always bcc to [e-mail] MX entry is mailhost.example.com

Mailhost.example.com is a regular Mailserver to forward Mails with transportmaps to the internal pilerhost.

All mails in Piler from this external Mailserver have [e-mail] as receipient, the Mailheader contains X-Envelope-To: [e-mail] two times. The original receipient is like [e-mail]

Mails from local Mailserver are ok.

[Janos SUTO]

I think you may fix the problem by setting the X-Envelope-To: header only on the external mail server.

[Janos SUTO]

Any update on the matter?

[Karsten Bandlow]

Its not possible, because the internal Mailserver forward Mails from other adresses to piler too. And it would be nice to forward only mails from goggle or so on, with a filter to a fixed archiveaddress. So there is no possibility to add an extra header. Do you have a solution?

[Former user]

This is rather about postfix than it is about piler. Can you setup a transport map on the external server for [e-mail] pointing directly to your pilerhost (e.g. opening a port in the firewall and allowing only connections from the external mail server on that port)

Otherwise recipient_bcc_maps could be an alternative for you as you could rewrite the bcc address depending on the recipients domain (or sender_bcc_maps for that matter if rewriting on the sender's domain).

[Janos SUTO]

Unfortunately Piper can't really help preventing the occurrence of the 2 identical mail headers.

[Karsten Bandlow]

Hi Janos, the only Problem is the piler email address in the to field. If I use the SAAS Feature, it would be helpful to set a destination emailadress like [e-mail] wich Piler have to ignore.