POSTFIX and General
Hello,
I must say Piler is a nice software for archive I've tested it on a test machine works perfect there was some hick ups but i did managed to work around it to get it working.
anyhow I've decided to install this software on a live system wanted to see how stable it will run with lots of email going out and in.
So i did the installation everything went smooth no problems expect when i start piler on the mail piler gives me and error of 8:19:32 mail piler[30948]: reloaded config: /usr/local/etc/piler.conf Oct 1 08:19:32 mail piler[30948]: ERR: cannot bind to port Oct 1 08:19:32 mail piler[30948]: piler has been terminated
So i know you have to set in postfix in the master.cf something like this 127.0.0.1:**** inet n - - - - smtpd
but i am using a Ubuntu server with Postfix and got a virtual host setup with all my domains we don't use smart host on our postfix but i did change a few things to get smart host with internet site working on the configuration of postfix and the thing is that i use port 25 of all my clients to sent email and i don't want to change that.
Thanks
Comments (8)
-
repo owner -
reporter Let me put the big picture we host a couple of 100+ domains on our server running Virtualmin and use postfix i want piler to pull all domain emails going out and in the client sent and archive via piler, so we can search any email accounts on our server via piler. I know its not recommended to run piler on the same host.
So what our problem is as soon as i change my postfix master.cf to this and the example #smtp inet n - - - - smtpd -o smtpd_sasl_auth_enable=yes 127.0.0.1:**** inet n - - - - smtpd -o smtpd_sasl_auth_enable=yes
Then what happened is that u cannot send email via port 25. I would like if there is a work around it please
Thanks
-
repo owner OK, I start to understand your situation. If you put postfix to 127.0.0.1, and let piler occupy 0.0.0.0:25, you surely won't send an email, since piler is not an smtp relay. The easiest way to fix it to assign a secondary IP-address (ip2) to the host, and let postfix use the primary ip (ip1), and piler the secondary ip (ip2).
Another possible option: put piler to localhost, and let postfix use the public ip address.
-
reporter Thank ill give it a go and will let you know if it works
-
reporter Ok i did managed to fix the problem after 3 hours but thanks for your help ill let you know for any other problems.
-
reporter - changed status to resolved
-
reporter i just had small error on on sphinx searchd i had to add a small line compat_sphinxql_magics=0 to be able to search and made some changes asswell of php versions change
-
repo owner Roger that.
- Log in to comment
Hello Chris, I'm glad that you like piler. The cannot bind to port is a common error (message) if you put piler and your MTA to the same host. I'm not sure if you have your mailboxes and piler on the same host (this is not recommended, though you can make it work) or you just have postfix installed with piler. In the latter case a workaround like what you mentioned might work. Anyway please clarify the task you want me to solve or fix.