Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Postfix forwarder - modify SMTP banner?

    Scheduled Pinned Locked Moved pfSense Packages
    40 Posts 3 Posters 12.1k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • D
      doktornotor Banned
      last edited by

      I am asking about your pfsense box hostname (forget postfix)… Is it domain.com?  ???

      1 Reply Last reply Reply Quote 0
      • D
        dreadnought
        last edited by

        @doktornotor:

        I am asking about your pfsense box hostname (forget postfix)… Is it domain.com?  ???

        Yes.

        I just got a spam and found that its IP address is blocked by both RBLs (zen.spamhaus.org, b.barracudacentral.org) I have configured under "RBL Server List."  Apparently my RBL functionality is not working.  Maybe the GUI is broken or I'm being stupid.  I'm sure postfix forwarder is running because if I telnet from the outside in on port 25 I'm getting a banner served up by postfix forwarder, not the banner I get from the mail server I actually get my mail from which I have postfix forwarder forwarding to.

        I checked main.cf using "View Postfix configuration files" and it appears its being modified properly by the GUI… I see these lines in there:

        smtpd_banner = $myhostname host.domain.com (with my host and domain)
        postscreen_dnsbl_sites=zen.spamhaus.org, b.barracudacentral.org
        postscreen_dnsbl_threshold=1

        I'll reboot the appliance again, but that hasn't seemed to work and as far as I understand it's not necessary.

        1 Reply Last reply Reply Quote 0
        • D
          doktornotor Banned
          last edited by

          Huh? Why is your hostname empty??? Did you set myhostname = domain.com somewhere or what? That is the whole problem, there is absolutely no need to mess with anything normally; postfix uses gethostname() by default; and smtpd_banner is $myhostname ESMTP $mail_name by default.

          1 Reply Last reply Reply Quote 0
          • D
            dreadnought
            last edited by

            @doktornotor:

            Huh? Why is your hostname empty??? Did you set myhostname = domain.com somewhere or what? That is the whole problem, there is absolutely no need to mess with anything normally; postfix uses gethostname() by default; and smtpd_banner is $myhostname ESMTP $mail_name by default.

            My pfsense "General Setup" is set for hostname = "pfsense" and domain = "domain.com".

            Maybe I should start over.  I'm not sure where postfix forwarder is getting the host/domain (well, in my case, just domain) it's serving up in the SMTP banner. The SMTP banner simply says "domain.com" and I would like it to say "host.domain.com" which would match my MX record.

            1 Reply Last reply Reply Quote 0
            • D
              doktornotor Banned
              last edited by

              As said, it should use gethostname(). What's the output of

              postconf -n
              hostname
              
              

              ???

              1 Reply Last reply Reply Quote 0
              • D
                dreadnought
                last edited by

                @doktornotor:

                As said, it should use gethostname(). What's the output of

                postconf -n
                hostname
                
                

                ???

                In () are my redactions/comments:

                $ postconf -n
                access_map_defer_code = 451
                access_map_reject_code = 554
                config_directory = /usr/local/etc/postfix
                default_process_limit = 100
                disable_vrfy_command = yes
                local_recipient_maps =
                message_size_limit = 25600000
                mydestination =
                mynetworks = /usr/local/etc/postfix/mynetwork_table
                mynetworks_style = host
                postscreen_access_list = permit_mynetworks, cidr:/usr/local/etc/postfix/cal_cidr
                postscreen_blacklist_action = enforce
                postscreen_dnsbl_action = enforce
                postscreen_dnsbl_sites = zen.spamhaus.org, b.barracudacentral.org
                postscreen_dnsbl_threshold = 1
                relay_domains = (My first email domain) (My second email domain)
                smtpd_banner = $myhostname (My host.domain.com)
                smtpd_client_restrictions = permit_mynetworks, reject_unauth_destination, check_client_access pcre:/usr/local/etc/postfix/cal_pcre, check_client_access cidr:/usr/local/etc/postfix/cal_cidr, reject_unknown_client_hostname, reject_unauth_pipelining, reject_multi_recipient_bounce, permit
                smtpd_delay_reject = yes
                smtpd_helo_required = yes
                smtpd_recipient_restrictions = permit_mynetworks, reject_unauth_destination, reject_unauth_pipelining, check_client_access pcre:/usr/local/etc/postfix/cal_pcre, check_client_access cidr:/usr/local/etc/postfix/cal_cidr, check_sender_access hash:/usr/local/etc/postfix/sender_access, reject_non_fqdn_helo_hostname, reject_unknown_recipient_domain, reject_non_fqdn_recipient, reject_multi_recipient_bounce, reject_unverified_recipient, reject_spf_invalid_sender, permit
                smtpd_sender_restrictions = reject_non_fqdn_sender, reject_unknown_sender_domain, reject_unauth_pipelining, reject_multi_recipient_bounce, permit
                strict_rfc821_envelopes = yes
                transport_maps = hash:/usr/local/etc/postfix/transport
                unknown_client_reject_code = 550
                unknown_hostname_reject_code = 550
                unverified_recipient_reject_code = 550

                $ hostname
                pfsense.domain.com (My domain)

                1 Reply Last reply Reply Quote 0
                • D
                  doktornotor Banned
                  last edited by

                  Afraid the postfix package is broken - gethostname() not working. Otherwise, you'd get "pfsense.domain.com" in the smtpd_banner. You can try to add

                  
                  myhostname = host.domain.com
                  
                  

                  to custom configuration and see if it helps.

                  1 Reply Last reply Reply Quote 0
                  • D
                    dreadnought
                    last edited by

                    @doktornotor:

                    Afraid the postfix package is broken - gethostname() not working. Otherwise, you'd get "pfsense.domain.com" in the smtpd_banner. You can try to add

                    
                    myhostname = host.domain.com
                    
                    

                    to custom configuration and see if it helps.

                    Is it possible the RBL lookups are broken as well?  I think postfix forwarder is reducing the volume of spam (though this is just anecdotal, I don't see any useful logs in the GUI), but the first spam I received this morning came from an IP address that should have been blocked by the postfix forwarder RBL lookup.

                    1 Reply Last reply Reply Quote 0
                    • D
                      doktornotor Banned
                      last edited by

                      Well, if basic things like resolution of local hostname are broken, then obviously yes, DNSBLs which rely on DNS records may be broken as well. Would need the whole postconf output (without -n) to see what's really configured in the end.

                      1 Reply Last reply Reply Quote 0
                      • M
                        mschiek01
                        last edited by

                        @dreadnought:

                        @doktornotor:

                        Afraid the postfix package is broken - gethostname() not working. Otherwise, you'd get "pfsense.domain.com" in the smtpd_banner. You can try to add

                        
                        myhostname = host.domain.com
                        
                        

                        to custom configuration and see if it helps.

                        Is it possible the RBL lookups are broken as well?  I think postfix forwarder is reducing the volume of spam (though this is just anecdotal, I don't see any useful logs in the GUI), but the first spam I received this morning came from an IP address that should have been blocked by the postfix forwarder RBL lookup.

                        I have been running it for months on multiple boxes. As far as I know nothing is broken as long as it intstalled correctly.

                        First you NEED to look at the log.

                        1. Do this, go into the first page general configuration, second heading "Logging"  it should say "/var/log/maillog"  if not use the down arrow and select it and save the configuration.

                        2. Go into services and restart postfix.

                        3. you can do this anyway you want.  You said you tried to use edit file which is fine, use it browse to var/log/maillog and open it what does it say?  Post the log here

                        Again I do not think postfix is actually receiving your mail.  It needs to be in the middle between pfsense and your smtp server.  If you see it running in services then it probably is.

                        Were you running an smtp server without it before? If so did you modify your firewall route to pass the mail to postfix first.  Just installing it will not do this.

                        This is very easy to test.  
                        1. Stop your SMTP server NOT postfix.
                        2. Run a test with mxtoolbox
                        3. Do you get a responce
                        3a No -> postfix is not in the middle and IS not processing mail for you.
                        3b Yes -> postfix is in the middle.

                        1 Reply Last reply Reply Quote 0
                        • D
                          dreadnought
                          last edited by

                          I have been running it for months on multiple boxes. As far as I know nothing is broken as long as it intstalled correctly.

                          First you NEED to look at the log.

                          1. Do this, go into the first page general configuration, second heading "Logging"  it should say "/var/log/maillog"  if not use the down arrow and select it and save the configuration.

                          2. Go into services and restart postfix.

                          3. you can do this anyway you want.  You said you tried to use edit file which is fine, use it browse to var/log/maillog and open it what does it say?  Post the log here

                          Again I do not think postfix is actually receiving your mail.  It needs to be in the middle between pfsense and your smtp server.  If you see it running in services then it probably is.

                          Were you running an smtp server without it before? If so did you modify your firewall route to pass the mail to postfix first.  Just installing it will not do this.

                          This is very easy to test.  
                          1. Stop your SMTP server NOT postfix.
                          2. Run a test with mxtoolbox
                          3. Do you get a responce
                          3a No -> postfix is not in the middle and IS not processing mail for you.
                          3b Yes -> postfix is in the middle.

                          Ok, logging was set for "System log" - I changed it to "/var/log/maillog".

                          I don't see a way to restart Postfix, so I went into Services/Postfix Forwarder, unchecked "Enable Postfix" then saved and then rechecked it then saved.

                          From the command prompt on the Netgate firewall I tried "cat /var/log/maillog" but nothing happened.

                          If I go to "System Activity" I see:

                          42792 postfix    64   20 87216K 50644K nanslp  2   0:02  0.00% perl5.12.4
                          32099 postfix    64   20 87216K 50520K nanslp  1   0:02  0.00% perl5.12.4
                          51351 postfix    64   20 87216K 50644K nanslp  1   0:02  0.00% perl5.12.4
                          59513 postfix    64   20 87216K 50644K nanslp  2   0:02  0.00% perl5.12.4
                          2313 postfix    64   20 87216K 50644K nanslp  2   0:02  0.00% perl5.12.4

                          Regarding the firewall rule… there is a postfix forwarder option for "Domains to Forward" and I put my mail server's IP in there along with the domains.  If this didn't create a firewall rule, then it sounds like that's where I screwed up and I may have misinterpreted the mxtoolbox results.

                          Actually, I'm still getting email from my mail server... so that doesn't make sense.  I'll go back and read your posts again.

                          Edit: Now I see none of my NAT or firewall rules related to SMTP were updated by the installation of postfix forwarder.  Combination of misinterpreting mxtoolbox output and a slow spam night doomed me while I was troubleshooting.  Fixing the rules now.  Thanks for the help!

                          1 Reply Last reply Reply Quote 0
                          • M
                            mschiek01
                            last edited by

                            @dreadnought:

                            I have been running it for months on multiple boxes. As far as I know nothing is broken as long as it intstalled correctly.

                            First you NEED to look at the log.

                            1. Do this, go into the first page general configuration, second heading "Logging"  it should say "/var/log/maillog"  if not use the down arrow and select it and save the configuration.

                            2. Go into services and restart postfix.

                            3. you can do this anyway you want.  You said you tried to use edit file which is fine, use it browse to var/log/maillog and open it what does it say?  Post the log here

                            Again I do not think postfix is actually receiving your mail.  It needs to be in the middle between pfsense and your smtp server.  If you see it running in services then it probably is.

                            Were you running an smtp server without it before? If so did you modify your firewall route to pass the mail to postfix first.  Just installing it will not do this.

                            This is very easy to test.  
                            1. Stop your SMTP server NOT postfix.
                            2. Run a test with mxtoolbox
                            3. Do you get a responce
                            3a No -> postfix is not in the middle and IS not processing mail for you.
                            3b Yes -> postfix is in the middle.

                            Ok, logging was set for "System log" - I changed it to "/var/log/maillog".

                            I don't see a way to restart Postfix, so I went into Services/Postfix Forwarder, unchecked "Enable Postfix" then saved and then rechecked it then saved.

                            From the command prompt on the Netgate firewall I tried "cat /var/log/maillog" but nothing happened.

                            If I go to "System Activity" I see:

                            42792 postfix    64   20 87216K 50644K nanslp  2   0:02  0.00% perl5.12.4
                            32099 postfix    64   20 87216K 50520K nanslp  1   0:02  0.00% perl5.12.4
                            51351 postfix    64   20 87216K 50644K nanslp  1   0:02  0.00% perl5.12.4
                            59513 postfix    64   20 87216K 50644K nanslp  2   0:02  0.00% perl5.12.4
                            2313 postfix    64   20 87216K 50644K nanslp  2   0:02  0.00% perl5.12.4

                            Regarding the firewall rule… there is a postfix forwarder option for "Domains to Forward" and I put my mail server's IP in there along with the domains.  If this didn't create a firewall rule, then it sounds like that's where I screwed up and I may have misinterpreted the mxtoolbox results.

                            Actually, I'm still getting email from my mail server... so that doesn't make sense.  I'll go back and read your posts again.

                            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.

                            1 Reply Last reply Reply Quote 0
                            • D
                              dreadnought
                              last edited by

                              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.

                              1 Reply Last reply Reply Quote 0
                              • M
                                mschiek01
                                last edited by

                                @dreadnought:

                                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.

                                1 Reply Last reply Reply Quote 0
                                • D
                                  dreadnought
                                  last edited by

                                  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.

                                  1 Reply Last reply Reply Quote 0
                                  • M
                                    mschiek01
                                    last edited by

                                    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.

                                    1 Reply Last reply Reply Quote 0
                                    • M
                                      mschiek01
                                      last edited by

                                      @dreadnought:

                                      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

                                      1 Reply Last reply Reply Quote 0
                                      • D
                                        dreadnought
                                        last edited by

                                        @mschiek01:

                                        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.

                                        1 Reply Last reply Reply Quote 0
                                        • M
                                          mschiek01
                                          last edited by

                                          Try rebooting the box.  Then take a look at the log and see if it is logging properly.

                                          1 Reply Last reply Reply Quote 0
                                          • D
                                            dreadnought
                                            last edited by

                                            @mschiek01:

                                            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.  ;)

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.