Postfix Forwarder package won't start
-
I was on pfSense version 2.1.2 and only had the Postfix package installed. It was working fine. Suddenly, it stopped receiving mail so I began checking things and noticed the service wasn't started. I attempted to start the service but it wouldn't start. I then uninstalled the package, updated pfSense to 2.1.3, then reinstalled the package. I'm still not able to get the service started however.
Is there anything I can check, or is this a known issue?
-
I did the same;
My postfix forwarder was OK.
I upgraded pfsense (installing 2.1.3).
Postfix forwarder doesn't start anymore.
I re-install the postfix forwarder package, doesn't work.
I can start it by hand (sh /usr/local/etc/rc.d/postfix.sh start), but I have errors forwarding :
postfix/error[6539]: 89FB01CD84: to=xxxxx@xxxxxxxx, relay=none, delay=13628, delays=13597/30/0/0.4, dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to 192.168.25.151[192.168.25.151]:25: Operation timed out)/xxxxx@xxxxxxxxMy internal postfix is OK, accessible from the machine running pfsense (by telneting on the smtp port, I can send mails)
Is there an incompatibility between the new pfsense and postfix forwarder ? something to modify ? -
I later activate the log in /var/log/maillog, and then got this message :
Jun 20 21:57:33 pfsense postfix/postfix-script[61892]: starting the Postfix mail system
Jun 20 21:57:33 pfsense postfix/master[62539]: fatal: /usr/pbi/postfix-amd64/etc/postfix/master.cf: line 3: no valid IP address found: smtp
Jun 20 21:57:34 pfsense postfix/master[62204]: fatal: daemon initialization failureThe pfsense machine is directly on the internet, it has my public address on one ethernet (78.236.X.Y),
and a local address on another ethernet (192.168.25.250)my master.cf is :
/usr/pbi/postfix-amd64/etc/postfix/master.cf
smtp inet n - n - 1 postscreen
-o user=postfix
-o soft_bounce=yes
smtpd pass - - n - - smtpd
dnsblog unix - - n - 0 dnsblog
tlsproxy unix - - n - 0 tlsproxy
pickup fifo n - n 60 1 pickup
cleanup unix n - n - 0 cleanup
qmgr fifo n - n 300 1 qmgr
tlsmgr unix - - n 1000? 1 tlsmgr
rewrite unix - - n - - trivial-rewrite
bounce unix - - n - 0 bounce
defer unix - - n - 0 bounce
trace unix - - n - 0 bounce
verify unix - - n - 1 verify
flush unix n - n 1000? 0 flush
proxymap unix - - n - - proxymap
proxywrite unix - - n - 1 proxymap
smtp unix - - n - - smtp
relay unix - - n - - smtp
-o smtp_fallback_relay=
showq unix n - n - - showq
error unix - - n - - error
retry unix - - n - - error
discard unix - - n - - discard
local unix - n n - - local
virtual unix - n n - - virtual
lmtp unix - - n - - lmtp
scache unix - - n - 1 scache
anvil unix - - n - 1 anvilAny idea ?
-
Check your configs against this.
-
hello
thank you for your post and details of configuration :)
What is correcting the problem is :- have postfix forwarder listening to LAN instead of WAN
- write a NAT rule to redirect smtp traffic to LAN address of pfsense
I think it's the same you recommend having postfix forwarder listening to loopback ?
I don't understand why it works, why it suddenly didn't work anymore, and why this trick solves the problem.
Can you explain that to me ?thank you again :)
-
hello
thank you for your post and details of configuration :)
What is correcting the problem is :- have postfix forwarder listening to LAN instead of WAN
- write a NAT rule to redirect smtp traffic to LAN address of pfsense
I think it's the same you recommend having postfix forwarder listening to loopback ?
I don't understand why it works, why it suddenly didn't work anymore, and why this trick solves the problem.
Can you explain that to me ?thank you again :)
It isn't the same as having the forwarder listening on loopback. Did you mean to say "listen on WAN instead of LAN"?
Are you relaying from an internal mail server to the outside world? That might explain it but I don't know how you would get emails from outside if you're listening on LAN.