Postfix - antispam and relay package
-
After upgrade to pfSense 2.3.3 Postfix does not start any more. The error message is "shared library libicuuc.so.57 not found".
Any help? -
After upgrade to pfSense 2.3.3 Postfix does not start any more. The error message is "shared library libicuuc.so.57 not found".
Any help?Which version of Postfix do you run? It looks like you need to update the postfix/icu pkg.
https://www.freshports.org/mail/postfix/
search for other commits by this committer
devel/icu: update to 58.1
Changes: http://site.icu-project.org/download/58
PR: 214384
Exp-run by: antoine
Approved by: office (bapt)Try: pkg install postfix icu pcre
-
How many people does still need antispam and dkim outgoing mail signing feature running on pfSense?
I know Netgate does not want or need it as a package on current pfSense versions but I'm updating postfix package to 2.3.x as a manual procedure in the user at your own risk way.
-
…
How many people does still need this running on pfSense?I know netgate does not want or need it as a package on current versions(I've asked a lot of times), but I can try to update it to 2.3.x or 2.4 as a manual procedure in the user at your own risk state.
I will say this is a must if you want to be sure that at least pfsense notification will be emailed to you.
If wan ( or lan ) go down and you don't use this package, you will lose all notification and is a good chance that logs will be overwritten until connection is fixed.
And in my case I am using it also as a backup (mx2) for primary mail server (mx1) that is on another location… -
Install process and search mail tab is almost done. Will take a look on widgets, view config and queue tab.
The process will be simple as execute a script on console/ssh. ;)
-
That are great news! Thank YOU! :)
-
Hello!
Does somebody have a modified system.inc for PFsenese 2.3.3 ? ( It doesn't work with system.inc from attached pfSense-2.3-Postfix.zip…. PFsense doesn't load saved configuration... ) :( :( :(
-
Hello!
Does somebody have a modified system.inc for PFsenese 2.3.3 ? ( It doesn't work with system.inc from attached pfSense-2.3-Postfix.zip…. PFsense doesn't load saved configuration... ) :( :( :(
I've finished the code update for 2.3.x. As it will not be an official package, I'm finishing a script/manual install for this package.
-
Hello!
Does somebody have a modified system.inc for PFsenese 2.3.3 ? ( It doesn't work with system.inc from attached pfSense-2.3-Postfix.zip…. PFsense doesn't load saved configuration... ) :( :( :(
Here is my running /etc/inc/system.inc attached, I'm using the Patches package with Auto Apply, so it will be auto patched after an pfSense update has deleted the maillog line.
--- system.inc 2017-03-08 11:19:12.000000000 +0100 +++ system-new.inc 2017-03-08 11:21:39.000000000 +0100 @@ -1164,6 +1164,7 @@ local4.* {$log_directive}{$g['varlog_path']}/portalauth.log local5.* {$log_directive}{$g['varlog_path']}/nginx.log local7.* {$log_directive}{$g['varlog_path']}/dhcpd.log +mail.* /var/log/maillog *.notice;kern.debug;lpr.info;mail.crit;daemon.none;news.err;local0.none;local3.none;local4.none;local7.none;security.*;auth.info;authpriv.info;daemon.info {$log_directive}{$g['varlog_path']}/system.log auth.info;authpriv.info |exec /usr/local/sbin/sshlockout_pf 15 *.emerg *
And don't forget to reboot after patching. :)
-
Thank you Bismarck - It works !!!
P.S. for others
Next edit:
/conf/config.xml
- and add Postfix to the Service Status and Menu:
<service><name>postfix</name>
<rcfile>postfix.sh</rcfile>
<executable>master</executable></service><menu>
<name>Postfix Forwarder</name>
<tooltiptext>Configure Postfix Forwarder</tooltiptext>
Services
<url>/pkg_edit.php?xml=postfix.xml&id=0</url>
</menu><menu>
<name>Search Mail</name>
<tooltiptext>Search postfix logs</tooltiptext>
Diagnostics
<url>/postfix_search.php</url>
</menu><menu>
<name>Postfix Queue</name>
<tooltiptext>check postfix queue</tooltiptext>
Status
<url>/postfix_queue.php</url>
</menu>Those must be inserted in the <installedpackages>section :)</installedpackages>
-
Hi everybody.
It's finally done 8)
Here are install instructions for UNOFFICIAL postfix package for pfSense(R) software 2.3.x
Under console/ssh, fetch the install script, check what it does if you want and then execute it.
cd /root fetch https://raw.githubusercontent.com/marcelloc/Unofficial-pfSense-packages/master/pkg-postfix/files/install_postfix_23.sh sh ./install_postfix_23.sh
Once it finishes, all must be in place. If you do not see the menu after it finishes, try to install any pfSense package from GUI, like cron for example.
WARNING
Use it at your own risk.
This script install packages from freebsd and change your config file.
-
Thank you looks very good so far, just one thing, the Widget always shows reject = 0.
-
Thank you looks very good so far, just one thing, the Widget always shows reject = 0.
I've updated some improvements on log to database function and search as well. Try updating the gui files or running the install process again.
Also check if you have reject logs on /var/log/maillog.
-
To follow updates on the package, check
https://github.com/marcelloc/Unofficial-pfSense-packages/commits/master/pkg-postfix
-
Hello marcelloc, I did run the install process again but no luck, reject is still 0 and I have different stats about the spam count in MailWatch as well.
Any idea?
BTW SPF and DKIM integration is awesome, thank you!
-
Do you have any non word character on server name like antispam-01 ?
The stats on widget are based on destination recipients. Is this what mailwatch does?
A message sid can have more then one destination recipient.
The spam message on widget is specific for spamassassin message that has the alert on logs with 'is spam'.
-
Do you have any non word character on server name like antispam-01 ?
No its just pfsense
The stats on widget are based on destination recipients. Is this what mailwatch does?
Yes, but it looks like the widget just counts high scored spam and not all, same when searching for spam in postfix_search.php it just finds high scored spam and the numbers of high scored spam are are always the same in the widget and MailMatch.
The spam message on widget is specific for spamassassin message that has the alert on logs with 'is spam'.
Yes, but for some odd reason, only the high scored spam gets logged to sqlite.
In the first unofficial version, the logging to sqlite was working fine, nothing changed since with my setup, except the new Postfix package.
If you like I can send you my maillog?
/edit
Searching for spam in postfix_search.php before the update in a sqlite db it shows all spam messages, the low and high scored.
-
-
Yes, but it looks like the widget just counts high scored spam and not all, same when searching for spam in postfix_search.php it just finds high scored spam and the numbers of high scored spam are are always the same in the widget and MailMatch.
The point is that database gets the last status from message. 'Normal spam' on your configuration are sent to user, this way, last state is sent, instead of spam.
The spam message on widget is specific for spamassassin message that has the alert on logs with 'is spam'.
There was some logic error on widget I've fixed too.
There was also an index on database that suposed to be unique but wasn't. Fixed this too.
https://github.com/marcelloc/Unofficial-pfSense-packages/commit/5cea314818b93122582be87bdf63c0a1eedad475
Thanks for your feedback. :)ps: Your mailscanner and spamassassin looks working really great. Did you had to change a lot of default gui config or rules? Are you using other spamassassin rules?
-
https://github.com/marcelloc/Unofficial-pfSense-packages/commit/5cea314818b93122582be87bdf63c0a1eedad475
Thanks for your feedback. :)I've applied the patch and it looks very good so far! :)
ps: Your mailscanner and spamassassin looks working really great. Did you had to change a lot of default gui config or rules? Are you using other spamassassin rules?
I've changed a lot of small things and yes I use custom scripts, rule channels and clamav sigs etc. but I think a good bayes training is the key.
If you like a can pack it all together for you?
Muito obrigado novamente! ;)