Mail server forwards/copies all incoming and outgoing after processing to [email protected]
Archive@ is stored on the mail server, piler fetches the mails off the mail server. Sent from my iPhone > On 04 Sep 2014, at 10:55 AM, Janos SUTO <[email protected]> wrote: > > >> On 2014-09-04 10:46, [email protected] wrote: >> for completeness , what would one do if the archiving address is >> [email protected] > > the archive address should be on a different host, other than an > MX server. I'm not sure how [email protected] should work. > > Janos > > > >>> On 04 Sep 2014, at 9:52 AM, Janos SUTO <[email protected]> wrote: >>> Dear piler users, >>> I'd like to clarify how the hostid parameter in piler.conf and the >>> archiving address are related. >>> Let's say you copy all emails to [email protected]. >>> In this case set hostid=piler.yourdomain.com in piler.conf. >>> Piler from 1.1.0 checks the rcpt to field, and if it's not >>> an address on piler.yourdomain.com, then it also stores it >>> as extra recipient. >>> This is the reason why some of you can see the archive@ address >>> in the gui. >>> How to fix it: >>> #1: Fix the hostid parameter in piler.conf, then reload or restart >>> the piler daemon >>> #2: execute the following mysql query to remove the unwanted extra >>> rcpt address from the database: >>> delete from rcpt where `to`='[email protected]'; >>> (be sure to use the archive address for your own site!) >>> Janos >
