Forwarding emails to Piler archive server

Hey folks,

I was wondering if someone uses Piler and already set up the mail forwarding to a Piler archive server. It would be awesome to have a plugin for setting the Piler server address in order to archive incoming and outgoing messages.

The Piler documentation on configuring the mail server offers this:

Quote from http://www.mailpiler.org/wiki/current:installation

Configure your mail server to forward a copy of each email it receives or sends to piler

To archive emails, piler must receive them somehow. So you have to configure your mail server to send a copy of each received emails to piler via smtp. Since piler is actually an SMTP server, you should not put postfix, exim, … on the archive itself. If you need it for some reason, then put it to 127.0.0.1:25/tcp, and set the listen_addr variable in piler.conf to listen on eth0 or similar.

If you have MS Exchange, then turn on journaling.

If you have postfix (including zimbra), then add the following to main.cf:

Code: /etc/postfix/main.cf

1. smtpd_recipient_restrictions = reject_non_fqdn_recipient, ..., \ check_recipient_access pcre:$config_directory/x-add-envelope-to, ... always_bcc = archive@piler.yourdomain.com

Code

1. /(.*)/ prepend X-Envelope-To: $1

Display More

Since I don't want to use the "X-Envelope-To" function I would leave that part out.
This is a configuration from an installation guide I found (in german):

Quote from https://www.debinux.de/2015/03/sichere-e-mail-archivierung-mit-piler/

Beispiel-Konfiguration (ohne „X-Envelope-To“):

Code: /etc/postfix/main.cf

1. # In allen drei Parametern darf "piler.domain.tld" NICHT auftauchen!
2. # Das verhindert externe Zustellung an das Archiv.
3. mydestination = domain.tld
4. virtual_mailbox_domains = domain.tld
5. relay_domains =
6. mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 IP.MAIL.PILER.SERVER
7. always_bcc = archive@piler.domain.tld
8. transport_maps = hash:/etc/postfix/transport
9. smtpd_recipient_restrictions = permit_mynetworks,
10. ...
11. ...

Display More

I'm not sure, if the "always_bcc" is sufficient for both sending AND receiving. I couldn't really check the relaying under imscp because I didn't want to break the working mail server and I don't have another system to test it on at the moment. I would appreciate any help or pointers.

Nonetheless, a "forward all incoming and outgoing mail AFTER spam and virus cleanup to archive@archiveserver.tld" would be a nice feature.

Cheers,

J