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

    Postfix - antispam and relay package

    Scheduled Pinned Locked Moved pfSense Packages
    855 Posts 136 Posters 1.1m 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.
    • B
      biggsy
      last edited by

      @trinidadrancheria:

      1: I see no way of using DNS block lists like dbl.spamhaus.org (which only accept domain names, not IP addresses).
      I have tried adding the option smtpd_client_restrictions=reject_rhsbl_client dbl.spamhaus.org on the general page under custom main.cf options. When I add it, I get a lot of log entries about it replacing existing smtpd_client_restrictions=reject_rhsbl_client lines.
      Does not seem to work.

      Have you tried using zen.spamhaus.org in the RBL server list?  That seems to work well with IP addresses:

      postfix/postscreen[83574]: CONNECT from [193.189.117.147]:29103 to [127.0.0.1]:25
postfix/dnsblog[84018]: addr 193.189.117.147 listed by domain zen.spamhaus.org as 127.0.0.4
postfix/dnsblog[84018]: addr 193.189.117.147 listed by domain zen.spamhaus.org as 127.0.0.2
postfix/postscreen[83574]: DNSBL rank 2 for [193.189.117.147]:29103
postfix/postscreen[83574]: HANGUP after 1.1 from [193.189.117.147]:29103 in tests after SMTP handshake
postfix/postscreen[83574]: DISCONNECT [193.189.117.147]:29103
      1 Reply Last reply Reply Quote 0
      • T
        trinidadrancheria
        last edited by

        @biggsy:

        @trinidadrancheria:

        1: I see no way of using DNS block lists like dbl.spamhaus.org (which only accept domain names, not IP addresses).
        I have tried adding the option smtpd_client_restrictions=reject_rhsbl_client dbl.spamhaus.org on the general page under custom main.cf options. When I add it, I get a lot of log entries about it replacing existing smtpd_client_restrictions=reject_rhsbl_client lines.
        Does not seem to work.

        Have you tried using zen.spamhaus.org in the RBL server list?  That seems to work well with IP addresses:

        postfix/postscreen[83574]: CONNECT from [193.189.117.147]:29103 to [127.0.0.1]:25
postfix/dnsblog[84018]: addr 193.189.117.147 listed by domain zen.spamhaus.org as 127.0.0.4
postfix/dnsblog[84018]: addr 193.189.117.147 listed by domain zen.spamhaus.org as 127.0.0.2
postfix/postscreen[83574]: DNSBL rank 2 for [193.189.117.147]:29103
postfix/postscreen[83574]: HANGUP after 1.1 from [193.189.117.147]:29103 in tests after SMTP handshake
postfix/postscreen[83574]: DISCONNECT [193.189.117.147]:29103

        Yes, I am using Zen. It is an IP address based list. It only accepts IP addresses as it should, and works fine. The Evil Nasty spammers and malware sites like to move around a lot to try and beat the ip based block lists.
        The lists that I want to use are based on their domains. They only accept domain names not IP addresses. Many of the best lists are switching to domain based for better blocking.

        1 Reply Last reply Reply Quote 0
        • B
          biggsy
          last edited by

          Sorry, I completely misread that first line in your post. :-[

          I think you'll have to modify your [i]main.cf and restart postfix manually to make that work.  Unfortunately, the change will be over-written next time you save your config from the GUI.

          1 Reply Last reply Reply Quote 0
          • BismarckB
            Bismarck
            last edited by

            @trinidadrancheria

            1. You need to manually edit /usr/local/pkg/postfix.inc this will keep your changes after a postfix reload but needs to be re edited after a package update. eg.:

            …
            smtpd_helo_restrictions = check_helo_access pcre:{$pf_dir}/etc/postfix/helo_check,
            reject_unknown_helo_hostname,
            reject_invalid_helo_hostname,
            reject_non_fqdn_helo_hostname,
            reject_rhsbl_helo hostkarma.junkemailfilter.com=127.0.0.2,
            **        reject_rhsbl_helo dbl.spamhaus.org,**
            permit
            …
            ...
            smtpd_sender_restrictions = reject_non_fqdn_sender,
            reject_unknown_sender_domain,
            reject_unauth_pipelining,
            reject_multi_recipient_bounce,
            **        reject_rhsbl_sender dbl.spamhaus.org, **
            permit
            …
            ...
            smtpd_client_restrictions = permit_mynetworks,
            reject_unauth_destination,
            check_client_access pcre:{$pf_dir}/etc/postfix/cal_pcre,
            check_client_access cidr:{$pf_dir}/etc/postfix/cal_cidr,
            reject_unknown_client_hostname,
            reject_unauth_pipelining,
            reject_multi_recipient_bounce,
            reject_rhsbl_reverse_client hostkarma.junkemailfilter.com=127.0.0.2,
            reject_rhsbl_reverse_client dbl.spamhaus.org,
            permit
            …

            And I guess this is highly ineffective, since Postscreen and RBL server List already reject almost everything and its safer, because you can combine as many rbl lists you like.

            http://www.postfix.org/SMTPD_ACCESS_README.html

            http://www.postfix.org/POSTSCREEN_README.html

            2. You missing a dot before the asterisk and add always a comment to the REJECT, easier to identify false/positives:

            /^From:.@__.__.download/ REJECT Spam Rule #20191

            3. see 1. & 2.

            Here a few commands to check your postfix rules if they match:

            postmap -q - regexp:/usr/pbi/postfix-amd64/etc/postfix/body_check < /root/mail.txt

            postmap -q - regexp:/usr/pbi/postfix-amd64/etc/postfix/header_check < /root/mail.txt

            postmap -q - regexp:/usr/pbi/postfix-amd64/etc/postfix/mime_check < /root/mail.txt

            postmap -q - regexp:/usr/pbi/postfix-amd64/etc/postfix/helo_check < /root/mail.txt

            Just copy the full mail with the header etc. into mail.txt file before execute.

            Usefull: http://www.regexr.com/

            Best practice is a well configurated Postfix + Mailscanner + sa-updater-custom-channels.sh + clamav-unofficial-sigs.sh = Spam > 1%.

            Cheers! ;)

            1 Reply Last reply Reply Quote 0
            • T
              trinidadrancheria
              last edited by

              I tried your format
              /^From:.@..eu/ REJECT Spam Rule #20191
              and is KINDA works…

              It does block the .eu TLD, but also hits on addresses like From:bill@mail.eugene.ca.gov
              This behavior is expected, since we are starting at the front of the screen. When I do it the right way:  /^From:.@..eu$/ (with the $ to match the end for .eu), the PCRE simulators all work fine. It catches only the .eu TLD.
              But when I put it in Postfix with the $ in it, it blocks nothing :P
              Am I missing something?

              And thanks for the other guides. I am looking at them now :)

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

                So, for anyone here who's not given up yet and is having issues with https://redmine.pfsense.org/issues/4420 - there's v2.4.5 out. If someone's wiling to undo the manual hacks (stuff like cyrus-sasl2/libspf2 installed via pkg, symlinks etc.) and report back, it'd be appreciated.

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

                  Hi, guys!

                  I have a problem.

                  I installed pfsense 2.2.4 x64 with postfix. And of course had issue with sqlite. I reinstall postfix using marcelloc instruction:

                  fetch -o /usr/local/www/postfix.php http://e-sac.siteseguro.ws/px22/postfix.txt
                  fetch -o /usr/local/www/widgets/widgets/postfix.widget.php http://e-sac.siteseguro.ws/px22/postfix.widget.txt
                  pbi_delete postfix-2.11.3_2-amd64
                  rm -f /usr/pbi/bin/libexec/postfix
                  rm -f /usr/local/etc/postfix
                  rm -f /var/spool/postfix
                  rm -f /var/mail/postfix
                  rm -f /var/db/postfix
                  pkg install postfix
                  etc…

                  now it work. BUT it reject all mails.
                  Here is a part of log:

                  Nov 11 10:35:13 pfSense postfix/postscreen[96424]: CONNECT from [209.85.223.170]:33179 to [127.0.0.1]:25
Nov 11 10:35:19 pfSense postfix/postscreen[96424]: PASS NEW [209.85.223.170]:33179
Nov 11 10:35:19 pfSense postfix/smtpd[48617]: connect from mail-io0-f170.google.com[209.85.223.170]
Nov 11 10:35:19 pfSense postfix/smtpd[48617]: warning: unknown smtpd restriction: "reject_spf_invalid_sender"
Nov 11 10:35:19 pfSense postfix/verify[51147]: cache btree:/var/db/postfix/verify_cache full cleanup: retained=5 dropped=0 entries
Nov 11 10:35:19 pfSense postfix/smtpd[48617]: NOQUEUE: reject: RCPT from mail-io0-f170.google.com[209.85.223.170]: 451 4.3.5 Server configuration error; from= <mymail@gmail.com>to= <mymail@mydomain.ru>proto=ESMTP helo= <mail-io0-f170.google.com>Nov 11 10:35:20 pfSense postfix/cleanup[59443]: 1E0D61138ADC: message-id=<20151111083520.1E0D61138ADC@pfSense.localdomain>
Nov 11 10:35:20 pfSense postfix/smtpd[48617]: disconnect from mail-io0-f170.google.com[209.85.223.170]
Nov 11 10:35:20 pfSense postfix/qmgr[57167]: 1E0D61138ADC: from=<double-bounce@pfsense.localdomain>, size=981, nrcpt=1 (queue active)
Nov 11 10:35:20 pfSense postfix/smtp[60115]: 1E0D61138ADC: to=<postmaster@pfsense.localdomain>, orig_to=<postmaster>, relay=none, delay=0.17, delays=0.01/0.01/0.16/0, dsn=5.4.4, status=bounced (Host or domain name not found. Name service error for name=pfSense.localdomain type=A: Host not found)
Nov 11 10:35:20 pfSense postfix/bounce[68723]: warning: 1E0D61138ADC: undeliverable postmaster notification discarded
Nov 11 10:35:20 pfSense postfix/qmgr[57167]: 1E0D61138ADC: removed</postmaster></postmaster@pfsense.localdomain></double-bounce@pfsense.localdomain></mail-io0-f170.google.com></mymail@mydomain.ru></mymail@gmail.com>

                  I added in Access Lists -> MyNetworks:
                  127.0.0.1
                  192.168.0.247 Exchange IP
                  192.168.0.250 Pfsense LAN IP
                  192.168.0.0/24

                  I found this advise for Postfix forwarder on 2.1_x64

                  1. Copied /usr/local/etc/postfix to /usr/pbi/postfix-amd64/etc/postfix
                  2. Once I put 2,6s into the greet wait time under antispam, it seemed to work

                  but it doesn't work for me(((

                  It's seem something wrong with postscreen….

                  pease help me

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

                    I've solved my problem. :)
                    Thanks for awesome package

                    1 Reply Last reply Reply Quote 0
                    • T
                      trinidadrancheria
                      last edited by

                      Tried this… First time I did only the helo lines, did not work, even after reboot. Nothing changed in main.cf
                      Did the other lines, rebooted, then it reverted with ownership errors on the database files :P
                      Ideas?

                      @Bismarck:

                      @trinidadrancheria

                      1. You need to manually edit /usr/local/pkg/postfix.inc this will keep your changes after a postfix reload but needs to be re edited after a package update. eg.:

                      …
                      smtpd_helo_restrictions = check_helo_access pcre:{$pf_dir}/etc/postfix/helo_check,
                      reject_unknown_helo_hostname,
                      reject_invalid_helo_hostname,
                      reject_non_fqdn_helo_hostname,
                      reject_rhsbl_helo hostkarma.junkemailfilter.com=127.0.0.2,
                      **        reject_rhsbl_helo dbl.spamhaus.org,**
                      permit
                      …
                      ...
                      smtpd_sender_restrictions = reject_non_fqdn_sender,
                      reject_unknown_sender_domain,
                      reject_unauth_pipelining,
                      reject_multi_recipient_bounce,
                      **        reject_rhsbl_sender dbl.spamhaus.org, **
                      permit
                      …
                      ...
                      smtpd_client_restrictions = permit_mynetworks,
                      reject_unauth_destination,
                      check_client_access pcre:{$pf_dir}/etc/postfix/cal_pcre,
                      check_client_access cidr:{$pf_dir}/etc/postfix/cal_cidr,
                      reject_unknown_client_hostname,
                      reject_unauth_pipelining,
                      reject_multi_recipient_bounce,
                      reject_rhsbl_reverse_client hostkarma.junkemailfilter.com=127.0.0.2,
                      reject_rhsbl_reverse_client dbl.spamhaus.org,
                      permit
                      …

                      And I guess this is highly ineffective, since Postscreen and RBL server List already reject almost everything and its safer, because you can combine as many rbl lists you like.

                      http://www.postfix.org/SMTPD_ACCESS_README.html

                      http://www.postfix.org/POSTSCREEN_README.html

                      2. You missing a dot before the asterisk and add always a comment to the REJECT, easier to identify false/positives:

                      /^From:.@__.__.download/ REJECT Spam Rule #20191

                      3. see 1. & 2.

                      Here a few commands to check your postfix rules if they match:

                      postmap -q - regexp:/usr/pbi/postfix-amd64/etc/postfix/body_check < /root/mail.txt

                      postmap -q - regexp:/usr/pbi/postfix-amd64/etc/postfix/header_check < /root/mail.txt

                      postmap -q - regexp:/usr/pbi/postfix-amd64/etc/postfix/mime_check < /root/mail.txt

                      postmap -q - regexp:/usr/pbi/postfix-amd64/etc/postfix/helo_check < /root/mail.txt

                      Just copy the full mail with the header etc. into mail.txt file before execute.

                      Usefull: http://www.regexr.com/

                      Best practice is a well configurated Postfix + Mailscanner + sa-updater-custom-channels.sh + clamav-unofficial-sigs.sh = Spam > 1%.

                      Cheers! ;)

                      1 Reply Last reply Reply Quote 0
                      • T
                        trinidadrancheria
                        last edited by

                        I ma wondering if I did not have the right section, since I have the header verification box set to basic? After stepping through the PHP should I be putting it here?

                        Original:

                        Don't talk to mail systems that don't know their own hostname.

                        smtpd_helo_required = yes
                        {$reject_unknown_helo_hostname}

                        smtpd_sender_restrictions = reject_unknown_sender_domain,
                        RBLRBLRBL

                        Allow connections from specified local clients and rbl check everybody else if rbl check are set.

                        smtpd_client_restrictions = permit_mynetworks,
                        reject_unauth_destination,
                        check_sender_access hash:{$pf_dir}/etc/postfix/sender_access,
                        check_client_access pcre:{$pf_dir}/etc/postfix/cal_pcre,
                        check_client_access cidr:{$pf_dir}/etc/postfix/cal_cidr
                        RBLRBLRBL

                        Whitelisting: local clients may specify any destination domain.

                        #,
                        smtpd_recipient_restrictions = permit_mynetworks,
                        reject_unauth_destination,
                        check_sender_access hash:{$pf_dir}/etc/postfix/sender_access,
                        check_client_access pcre:{$pf_dir}/etc/postfix/cal_pcre,
                        check_client_access cidr:{$pf_dir}/etc/postfix/cal_cidr,
                        SPFSPFSPFRBLRBLRBL

                        Modified:

                        Don't talk to mail systems that don't know their own hostname.

                        smtpd_helo_required = yes
                        {$reject_unknown_helo_hostname}

                        smtpd_sender_restrictions = reject_unknown_sender_domain,
                                                        reject_rhsbl_reverse_client dbl.spamhaus.org,
                        RBLRBLRBL

                        Allow connections from specified local clients and rbl check everybody else if rbl check are set.

                        smtpd_client_restrictions = permit_mynetworks,
                        reject_unauth_destination,
                        check_sender_access hash:{$pf_dir}/etc/postfix/sender_access,
                        check_client_access pcre:{$pf_dir}/etc/postfix/cal_pcre,
                        check_client_access cidr:{$pf_dir}/etc/postfix/cal_cidr <–------- I see a missing , in the INC, put it in?
                        RBLRBLRBL

                        Whitelisting: local clients may specify any destination domain.

                        #,
                        smtpd_recipient_restrictions = permit_mynetworks,
                        reject_unauth_destination,
                        check_sender_access hash:{$pf_dir}/etc/postfix/sender_access,
                        check_client_access pcre:{$pf_dir}/etc/postfix/cal_pcre,
                        check_client_access cidr:{$pf_dir}/etc/postfix/cal_cidr,
                                                        reject_rhsbl_reverse_client dbl.spamhaus.org,
                                                        reject_rhsbl_sender dbl.spamhaus.org,
                                                        reject_rhsbl_client dbl.spamhaus.org,
                        SPFSPFSPFRBLRBLRBL

                        I would be using MailScanner, but I am running PFSense 2.2.4 and they say mailscanner does not work, or there is something we need to do to install it right, but my other thread went unanswered to see if it is working :P

                        1 Reply Last reply Reply Quote 0
                        • T
                          trinidadrancheria
                          last edited by

                          @trinidadrancheria:

                          I tried your format
                          /^From:.@..eu/ REJECT Spam Rule #20191
                          and is KINDA works…

                          It does block the .eu TLD, but also hits on addresses like From:bill@mail.eugene.ca.gov
                          This behavior is expected, since we are starting at the front of the screen. When I do it the right way:  /^From:.@..eu$/ (with the $ to match the end for .eu), the PCRE simulators all work fine. It catches only the .eu TLD.
                          But when I put it in Postfix with the $ in it, it blocks nothing :P
                          Am I missing something?

                          And thanks for the other guides. I am looking at them now :)

                          In case someone else was having the same issue, I found a work around for PostFix not recognizing both the ^ (begin) and the $ (end) for an entry in the access list.
                          Instead of
                          /^From:.@..eu/ which would hit on things like bill@ci.eureka.ca.gov as well as bill@sample.eu, which is NOT what we want.
                          New way using word boundary
                          /^From:.@..eu\b/ only hits on bill.sample.eu
                          Now we can reject senders from certain TLDs properly :D
                          (The reason I did not use HELO is A: It never worked for me, and B: (BIG one) spammers are using US servers to spoof .eu in the from address so the HELO does not match).
                          :)

                          1 Reply Last reply Reply Quote 0
                          • T
                            trinidadrancheria
                            last edited by

                            Marceloc are you the one I talk to about patches for PF sense postfix?
                            I am working on a patch to implement the DNS blacklist to the package through a patch with its own list section, but it would be nice if we can add it right to the next version.
                            Once tested, can I send the patch to you to see what you think?

                            Also is there a official place to get full documentation on how the patchfile syntax?

                            1 Reply Last reply Reply Quote 0
                            • S
                              Sherby
                              last edited by

                              @doktornotor:

                              So, for anyone here who's not given up yet and is having issues with https://redmine.pfsense.org/issues/4420 - there's v2.4.5 out. If someone's wiling to undo the manual hacks (stuff like cyrus-sasl2/libspf2 installed via pkg, symlinks etc.) and report back, it'd be appreciated.

                              Hi,
                              I did uninstall the postfix package and undo any manual fixes and patches.
                              Then I did firmware upgrade from 2.2.4 to 2.2.5 and postfix package reinstall.
                              This time, things look better but I still had to do some tweak to the postfix.inc file to make it work.

                              1. had to do the following procedure, except for the 2 first line "fetch…" because I believe those file are now obsolete and will break things, since the package has been updated.

                              @marcelloc:

                              Reposting update guide for pfsense 2.2.x only:

                              Install package via gui
                              execute code below via console/ssh

                              fetch -o /usr/local/www/postfix.php http://e-sac.siteseguro.ws/px22/postfix.txt
fetch -o /usr/local/www/widgets/widgets/postfix.widget.php http://e-sac.siteseguro.ws/px22/postfix.widget.txt
pbi_delete postfix-2.11.3_2-amd64
rm -f /usr/pbi/bin/libexec/postfix
rm -f /usr/local/etc/postfix
rm -f /var/spool/postfix
rm -f /var/mail/postfix
rm -f /var/db/postfix
pkg install postfix

                              fix postfix.inc file with this patch via system patcher package

                              add this patch via package system patcher

                              **description:**postfix_inc
                              patch:

                              --- postfix.orig.inc 2015-08-18 08:15:00.000000000 +0000
+++ postfix.inc  2015-08-18 08:18:10.000000000 +0000
@@ -36,11 +36,11 @@
 require_once("globals.inc");

 $pfs_version = substr(trim(file_get_contents("/etc/version")),0,3);
-if ($pfs_version == "2.1" || $pfs_version == "2.2") {
-       define('POSTFIX_LOCALBASE', '/usr/pbi/postfix-' . php_uname("m"));
-} else {
+//if ($pfs_version == "2.1" || $pfs_version == "2.2") {
+//     define('POSTFIX_LOCALBASE', '/usr/pbi/postfix-' . php_uname("m"));
+//} else {
        define('POSTFIX_LOCALBASE','/usr/local');
-}
+//}

 $uname=posix_uname();
 if ($uname['machine']=='amd64')

                              directory:/usr/local/pkg/

                              1. had to manually patch the file /usr/local/www/postfix_view_config.php, to fix the path for config files to allow displaying  the config file correctly under the "view config" tab.

                              Guys, you did a great job to make that package work on pfsense 2.2.x !

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

                                Any ETA on a "Install and Go" fix without needing to manually edit things?

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

                                  @MadCatZA:

                                  Any ETA on a "Install and Go" fix without needing to manually edit things?

                                  ETA = never. The package is gone from pfSense 2.3.

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

                                    @doktornotor:

                                    @MadCatZA:

                                    Any ETA on a "Install and Go" fix without needing to manually edit things?

                                    ETA = never. The package is gone from pfSense 2.3.

                                    Mmm… Then I must ask what mail forwarder is pfsense going to replace it with? Surely many people make use of pfsense for dual web and mail filtering and other general firewall purpouses. Scrapping postfix without a replacement would force people to look at other next generation firewalls.

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

                                      @MadCatZA:

                                      Mmm… Then I must ask what mail forwarder is pfsense going to replace it with?

                                      I don't believe any replacement is planned for this. https://redmine.pfsense.org/issues/5374

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

                                        @doktornotor:

                                        @MadCatZA:

                                        Mmm… Then I must ask what mail forwarder is pfsense going to replace it with?

                                        I don't believe any replacement is planned for this. https://redmine.pfsense.org/issues/5374

                                        Does that also mean all the other mail apps like mailscanner, spamassasin, clamav ect will be falling away? Last I checked the Postfix was a MTA that sent all emails to 127.0.0.1 on the pfsense box were they were then scanned and filtered accordingly, PostFix would then send them on there way when they were done. Unless I am understanding wrong, how would I filter my mail now without PostFix?

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

                                          @MadCatZA:

                                          Unless I am understanding wrong, how would I filter my mail now without PostFix?

                                          On your mailserver perhaps? I don't get the idea of running postfix, spam filters and co. on a firewall… Regardless, take this with pfSense developers, I'm not one.

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

                                            @doktornotor:

                                            @MadCatZA:

                                            Unless I am understanding wrong, how would I filter my mail now without PostFix?

                                            On your mailserver perhaps? I don't get the idea of running postfix, spam filters and co. on a firewall… Regardless, take this with pfSense developers, I'm not one.

                                            Meant how would I filter my mail without PostFix "On pfSense", but I appreciate your honest replies. What a pity I liked pfSense. Cheers.

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