Hi Janos: 2015-06-01 18:12 GMT+08:00 Janos SUTO <[email protected]>: > fix the hostname for hostid in piler.conf, and fix the always_bcc address as > well. > Then restart piler, and if new emails are displayed properly, then remove > archive@[10.1.1.200] > from the rcpt table.
your advice works fine :) I also found some missing steps after postinstall. maybe you want to fix the postinstall script or document. at the file config-site.php I need to add: $config['PILER_HOST'] = '127.0.0.1'; (default is 1.2.3.4 in config.php, I think 127.0.0.1 is a reasonable default?) without this health monitor always show piler error. $config['DECRYPT_BINARY'] = '/usr/bin/pilerget'; (default /usr/local/bin) $config['DECRYPT_ATTACHMENT_BINARY'] = '/usr/bin/pileraget'; (default /usr/local/bin) $config['PILERIMPORT_IMAP_COMMAND'] = '/usr/bin/pilerimport -d /var/piler/imap -q -r'; (default /usr/local/bin) and I have other questions now. check the mail-list archive, I found your advice to enable postfix at another port to co-exist with piler. I have done that, and I can send out normal mails (like cron report or other system administration mails) at the piler host. I wonder if I didn't enable postfix, can these mails be sent out correctly? because I found both postfix and piler will log to /var/log/maillog, so the log looks a little complicated. or I want to use another log file for piler if possible. also I found many workarround and discussions about "x-add-envelope-to". could you advice the best method now we can use with postfix? I would like to test dev version if there are new thought about these. thanks again for your kindly help!! Regards, tbskyd
