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.
    • R
      Redtooth
      last edited by

      Hi

      I've just installed postfix, everything is working fine except an error keeps feeling my logs..

      Jan 17 19:20:26
      postfix/smtpd[25463]: D17FD62D47C: client=addmail.nu[212.247.84.186]
      Jan 17 19:20:26
      postfix/cleanup[28013]: D17FD62D47C: message-id=729443A7-32CE-41B4-A908-11E46BA2CBD9@site.se
      Jan 17 19:20:26
      postfix/qmgr[46843]: D17FD62D47C: from=firstname.lastname@site.se, size=1225, nrcpt=1 (queue active)
      Jan 17 19:20:27
      postfix/smtp[28014]: D17FD62D47C: to=myname@mydomain.org, relay=10.10.1.100[10.10.1.100]:25, delay=0.2, delays=0.03/0.01/0.02/0.13, dsn=2.0.0, status=sent (250 Queued (0.016 seconds))
      Jan 17 19:20:27
      postfix/qmgr[46843]: D17FD62D47C: removed
      Jan 17 19:20:31
      postfix/smtpd[25463]: warning: connect to private/anvil: Connection refused
      Jan 17 19:20:31
      postfix/smtpd[25463]: warning: problem talking to server private/anvil: Connection refused
      Jan 17 19:20:32
      postfix/smtpd[25463]: warning: connect to private/anvil: Connection refused
      Jan 17 19:20:32
      postfix/smtpd[25463]: warning: problem talking to server private/anvil: Connection refused
      Jan 17 19:20:32
      postfix/smtpd[25463]: disconnect from addmail.nu[212.247.84.186]

      Any clue how to fix this?

      ** SOLVED **
      Had to have Anvil Daemon enabled in Postfix Forwarder under AntiSpam for the problem to go away./myname@mydomain.org/firstname.lastname@site.se

      1 Reply Last reply Reply Quote 0
      • R
        RChadwick
        last edited by

        Can you tell me if this can forward to a port besides 25? I have pfsense at work, and I run an email server at home, but Comcast just decided to block port 25. Was hoping to configure the mx records to point to my office, and it would forward all mail to my home email server.

        1 Reply Last reply Reply Quote 0
        • marcellocM
          marcelloc
          last edited by

          @RChadwick:

          Can you tell me if this can forward to a port besides 25? I have pfsense at work, and I run an email server at home, but Comcast just decided to block port 25. Was hoping to configure the mx records to point to my office, and it would forward all mail to my home email server.

          It will not filter based ou source ip as all your mail will have your comany address as source.

          Treinamentos de Elite: http://sys-squad.com

          Help a community developer! ;D

          1 Reply Last reply Reply Quote 0
          • V
            vbela
            last edited by

            @mrfairsquare:

            ISSUE:
            –-----
            The postfix log db file is empty, and postfix does not or can not write to the db file.

            Location i'm looking at:  /var/db/postfix

            I have the same problem.

            Loggin is turned on
            Destination /var/log/maillog
            Update Sqlite Every minute
            /^Subject:/ WARN is in the right place

            But mail search is not working. DB is created, but it's empty ((

            Pfsense ver 2.0.2 i386

            1 Reply Last reply Reply Quote 0
            • marcellocM
              marcelloc
              last edited by

              @vbela:

              But mail search is not working. DB is created, but it's empty ((

              What you get on postfix logs? Can you see the subject warn message on logs and postfix database script on cron?

              Treinamentos de Elite: http://sys-squad.com

              Help a community developer! ;D

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

                I've set up a new VM to try and test Postfix and some other packages.

                2.1-BETA1 (amd64) built on Tue Apr 2 16:21:22 EDT 2013  +  Postfix 2.8.7,1 pkg v.2.3.4_1

                Two things noticed so far:

                • Still need to copy files as per this post: http://forum.pfsense.org/index.php/topic,50519.msg270803.html#msg270803

                • When restarting the ESXi host and pfSense VM, Postfix doesn't pick up a change of WAN IP address.  Given error is: postfix/master[32735]: fatal: bind <old wan="" ip="">port 25: Can't assign requested address.  Probably because master.cf is being updated in /usr/local/etc/postfix/ not /usr/pbi/postfix-amd64/etc/postfix</old>

                Edit: one more thing at start of package:

                • postfix/postfix-script[55357]: warning: not owned by root: /var/spool/postfix
                1 Reply Last reply Reply Quote 0
                • B
                  biggsy
                  last edited by

                  The two main problems noted above now seem to be fixed with the latest version for pfSense 2.1 (amd64). 
                  Thank you marcelloc.

                  The last point, about /var/spool/postfix is still there but never caused any problems.

                  Just as an aside, I also discovered that I could copy the /var/db/postfix/postscreen_cache.db file from the existing 32-bit 2.0.2 install to the new 64-bit 2.1 Beta1 install.

                  To avoid delayed delivery of all those "once every few weeks emails", I have a custom main.cf entry:```
                  postscreen_cache_retention_time = 30d

                  
Copying the postscreen_cache file saves having the new install re-learn all the whitelisted SMTP client IPs that the existing install knew about.
                  1 Reply Last reply Reply Quote 0
                  • marcellocM
                    marcelloc
                    last edited by

                    biggsy,

                    Thanks for your feedback  :)

                    Treinamentos de Elite: http://sys-squad.com

                    Help a community developer! ;D

                    1 Reply Last reply Reply Quote 0
                    • I
                      ics
                      last edited by

                      Hi All,

                      I've just updated package mailscanner-dev to v4.84.5_3 and upgraded pFsense to v2.0.3.
                      Now memory usage is very high. I don't know if it's due to package or pfsense update.
                      Postfix processes take very high memory  (screen captures of sys activity in old and new version attached).

                      Do have an idea ?

                      Thanks

                      new_sys.png
                      new_sys.png_thumb
                      old_sys.png
                      old_sys.png_thumb

                      1 Reply Last reply Reply Quote 0
                      • marcellocM
                        marcelloc
                        last edited by

                        It's a normal behavior. You have low memory machines.

                        Treinamentos de Elite: http://sys-squad.com

                        Help a community developer! ;D

                        1 Reply Last reply Reply Quote 0
                        • I
                          ics
                          last edited by

                          Thank you Marcelloc

                          Indeed I have 1024MB.
                          But why processes use so much memory now ?
                          This is a huge difference !

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

                            A strange new problem today with postfix forwarder on 2.1BETA amd64 test system.  Config hadn't changed.

                            Received the following error:

                            
postfix/smtpd[1783]: error: open /usr/local/etc/postfix/helo_check: No such file or directory
postfix/smtpd[1783]: connect from [i]mailserver.myisp[/i].com[[i]x.y.z.231]
postfix/smtpd[1783]: warning: pcre:/usr/local/etc/postfix/helo_check is unavailable. open /usr/local/etc/postfix/helo_check: No such file or directory
postfix/smtpd[1783]: warning: pcre:/usr/local/etc/postfix/helo_check: table lookup problem

                            EDIT:  looks like it should be "helo_check_s_"

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

                              Is the per process memory usage of 200M+ normal ?

                              I haven't used mailscanner before (just visited their website and they list some impressive installations), but for the past 6-7 years I have been running several Postfix systems using amavis to interface with antispam (spamassassin) and antiviruses (e.g. clamav) and postgrey and the overall memory usage is nowhere near those numbers …

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

                                Regarding my post above about /usr/local/etc/postfix/helo_check

                                I created a plain text file with one line similar to this:

                                /^my.domain.com/ REJECT

                                The error has gone away and postfix is forwarding mail again.  I have no idea why this file was suddenly wanted by postfix but it almost certainly happened after an upgrade to the latest 2.1 snap and the subsequent re-install of postfix.

                                I also suspect the file should probably have been looked for in: /usr/pbi/postfix-amd64/etc/postfix/

                                (The code above also stops remote SMTP clients from trying to claim they are part of my own domain.)

                                1 Reply Last reply Reply Quote 0
                                • marcellocM
                                  marcelloc
                                  last edited by

                                  @biggsy:

                                  Regarding my post above about /usr/local/etc/postfix/helo_check
                                  The error has gone away and postfix is forwarding mail again.  I have no idea why this file was suddenly wanted by postfix but it almost certainly happened after an upgrade to the latest 2.1 snap and the subsequent re-install of postfix.

                                  I also suspect the file should probably have been looked for in: /usr/pbi/postfix-amd64/etc/postfix/

                                  (The code above also stops remote SMTP clients from trying to claim they are part of my own domain.)

                                  I've included this helo check on latest version, but forgot to include folder check on it.

                                  It's fixed now.

                                  Thanks for your feedback. :)

                                  Treinamentos de Elite: http://sys-squad.com

                                  Help a community developer! ;D

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

                                    It's fixed now.

                                    Indeed it is.

                                    Thank you once again marcelloc  :)

                                    1 Reply Last reply Reply Quote 0
                                    • R
                                      r00tm4n
                                      last edited by

                                      Hello Marcello,

                                      Very nice work (um trabalho extraordinario!), congrats!

                                      I would like to migrate my smtp proxy to something that
                                      is able to count emails per user per minutes or hours and
                                      be able to limit that.
                                      Can pfSense do that?

                                      1 Reply Last reply Reply Quote 0
                                      • marcellocM
                                        marcelloc
                                        last edited by

                                        @r00tm4n:

                                        Very nice work (um trabalho extraordinario!), congrats!

                                        Thanks!:)

                                        @r00tm4n:

                                        I would like to migrate my smtp proxy to something that
                                        is able to count emails per user per minutes or hours and
                                        be able to limit that.
                                        Can pfSense do that?

                                        Not on current version, but postfwd can do that.

                                        http://www.postfix.org/SMTPD_POLICY_README.html
                                        http://postfwd.org/

                                        Treinamentos de Elite: http://sys-squad.com

                                        Help a community developer! ;D

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

                                          Here's another one for you marcelloc:

                                          I just noticed that postfix forwarder on 2.1 BETA 1 amd64 does not pick up descriptive names (e.g., "DMZ") for OPT interfaces. It does on my 2.0.2 install.

                                          Also, the package description is "Not available" under Status > Services.

                                          Both of the above are only cosmetic changes but you may not have noticed them.  :)

                                          ![2013-05-16 19-51-31.png](/public/imported_attachments/1/2013-05-16 19-51-31.png)
                                          ![2013-05-16 19-51-31.png_thumb](/public/imported_attachments/1/2013-05-16 19-51-31.png_thumb)

                                          1 Reply Last reply Reply Quote 0
                                          • I
                                            ics
                                            last edited by

                                            I have an Exchange Server that sends outgoing emails through pfSense.
                                            The recipient can see the local hostname and private IP address of the Exchange server in the header of the email.
                                            Is there a way to hide this ?

                                            Thanks

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