Postfix forwarder - modify SMTP banner?
-
With postfix running just stop your mail server and run the test with mxtoolbox. If you receive a reply it is configured correctly if you do not receive a reply it is not. Let me know the results.
With my mail server shut down, I got a timeout from mxtoolbox. The firewall rule I used on the WAN interface after I re-read your posts was:
TCP * * 127.0.0.1 25 (SMTP) * none
And I changed Listen interface(s) in postfix forwarder to loopback.
I must be doing something wrong with the firewall rules because it appears postfix forwarder IS running, just not answering.
I have tried having the rule above enabled both with my previous rule for my internal server enabled and disabled, but either way postfix forwarder doesn't answer on port 25.
Update:
I've been reading through http://forum.pfsense.org/index.php/topic,40622.msg217539.html#msg217539, particularly:
"remove nat from port 25
create a wan rule to permit smtp traffic to wan address
check enable postfix option
choose at least wan loopback interfaces
fill your domain/internal smtp info"I follow this except for the "at least" part… maybe I need to try using the WAN interface instead of loopback.
-
With postfix running just stop your mail server and run the test with mxtoolbox. If you receive a reply it is configured correctly if you do not receive a reply it is not. Let me know the results.
With my mail server shut down, I got a timeout from mxtoolbox. The firewall rule I used on the WAN interface after I re-read your posts was:
TCP * * 127.0.0.1 25 (SMTP) * none
And I changed Listen interface(s) in postfix forwarder to loopback.
I must be doing something wrong with the firewall rules because it appears postfix forwarder IS running, just not answering.
I have tried having the rule above enabled both with my previous rule for my internal server enabled and disabled, but either way postfix forwarder doesn't answer on port 25.
Update:
I've been reading through http://forum.pfsense.org/index.php/topic,40622.msg217539.html#msg217539, particularly:
"remove nat from port 25
create a wan rule to permit smtp traffic to wan address
check enable postfix option
choose at least wan loopback interfaces
fill your domain/internal smtp info"I follow this except for the "at least" part… maybe I need to try using the WAN interface instead of loopback.
You can do it as above. However do not use the rule I gave you. Instead use the rule above and change the listening interface to the wan and loopback. Just use the control key to select both. Then save the configuration. Then rerun the mxtoolbox test with your smtp server stopped but postfix enabled and running. you should get a responce.
-
I follow this except for the "at least" part… maybe I need to try using the WAN interface instead of loopback.
That seems to have worked… I changed the rule to:
TCP * * WAN address 25 (SMTP) * none
And now postfix forwarder is answering... and emails are getting to my internal mail server.
-
Good. :)
You still should go to /var/log/maillog
And take a look and see what postfix is doing and see if there are any other problems.
-
I follow this except for the "at least" part… maybe I need to try using the WAN interface instead of loopback.
That seems to have worked… I changed the rule to:
TCP * * WAN address 25 (SMTP) * none
And now postfix forwarder is answering... and emails are getting to my internal mail server.
It should be answering now with whatever you put in smtpd_banner = $myhostname
-
Good. :)
You still should go to /var/log/maillog
And take a look and see what postfix is doing and see if there are any other problems.
I thought I replied to this but don't see it… anyway, I changed the postfix forwarder logging option to /var/log/maillog. This file is 0 bytes when I download it from the pfsense GUI. The Postfix dashboard widget is also just a blue bar that says Postfix. This was the case before and after my changing the logging from System logs to /var/log/maillog. Confused! It appears email is being processed fine as I'm receiving it from my internal mail server and the headers mention my pfsense.domain.com.
-
Try rebooting the box. Then take a look at the log and see if it is logging properly.
-
Try rebooting the box. Then take a look at the log and see if it is logging properly.
When all else fails… yeah, that worked. After rebooting I can now download and view /var/log/maillog and there are stats in the Postfix dashboard widget.
It will be nice not having any more spam from Dr. Oz. Not that you guys would know about that, because you've been blocking his mail. And now I am too. ;)
-
Good. :)
You still should go to /var/log/maillog
And take a look and see what postfix is doing and see if there are any other problems.
I thought I replied to this but don't see it… anyway, I changed the postfix forwarder logging option to /var/log/maillog. This file is 0 bytes when I download it from the pfsense GUI. The Postfix dashboard widget is also just a blue bar that says Postfix. This was the case before and after my changing the logging from System logs to /var/log/maillog. Confused! It appears email is being processed fine as I'm receiving it from my internal mail server and the headers mention my pfsense.domain.com.
Also did you configure the tabs in postfix "access lists" and "antispam"
-
Also did you configure the tabs in postfix "access lists" and "antispam"
Antispam yes… access lists no. In terms of the "Client Access List", I force users to connect to the LAN via VPN to send mail. So I don't think I need to let postfix forwarder know about clients allowed to relay, because no one is?
-
Any idea where the Postfix dashboard widget gets its data? It currently shows:
Postfix
2013-08-16
Sent
2But I can see from /var/log/maillog (and from my inbox) that a lot more stuff has happened… e.g. rejections.
-
Also did you configure the tabs in postfix "access lists" and "antispam"
Antispam yes… access lists no. In terms of the "Client Access List", I force users to connect to the LAN via VPN to send mail. So I don't think I need to let postfix forwarder know about clients allowed to relay, because no one is?
You are thinking the wrong direction. the ACL is what postfix uses to process the email. The key word being accept as in "INBOUND" mail. Not outbound as it does not have any thing to do with outbound mail.
What you are seeing in the dashboard is correct. The Sent actually refers to received. So it received 2 emails from x and forwarded it to you smtp server.
Are you using mailscanner?
-
Also did you configure the tabs in postfix "access lists" and "antispam"
Antispam yes… access lists no. In terms of the "Client Access List", I force users to connect to the LAN via VPN to send mail. So I don't think I need to let postfix forwarder know about clients allowed to relay, because no one is?
You are thinking the wrong direction. the ACL is what postfix uses to process the email. The key word being accept as in "INBOUND" mail. Not outbound as it does not have any thing to do with outbound mail.
What you are seeing in the dashboard is correct. The Sent actually refers to received. So it received 2 emails from x and forwarded it to you smtp server.
Are you using mailscanner?
Oh… I think I get it now. So the ACL is to whitelist my computers in case they send spammy-looking email, they won't be blocked by postfix forwarder? I think I'll leave the entire set of options in that tab empty for now.
I thought the dashboard would show rejections, but it looks like it does not... I just have #s for sent and bounced, but I know many more messages are being rejected from looking at /var/log/maillog.
-
you are correct.