On 2015-06-01 14:22, d tbsky wrote:
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.
well, the localhost is definitely a good idea, unless you put
exim/postfix/...
to 127.0.0.1
$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.
the syslog stuff (facility, ...) is pretty hard coded, and I believe
that
a mail related application (ie. both postfix and piler) should syslog to
the mail log. Anyway it's easy to filter out piler related stuff, and
make sure that postfix is actually running.
also I found many workarround and discussions about
"x-add-envelope-to". could you advice the best method now we can use
what do you want to achieve?
with postfix? I would like to test dev version if there are new
thought about these.
to get the dev version, download the master branch (see the download
section on bitbucket)
Janos
