Postfix - antispam and relay package
-
This is why I would like to add a rule on my router so they can all go through the SMTP server of my ISP.
Can you do it with your package postfix?I think you will need authentication for these clients.
You can manually install and configure sasl as current version does not has this integrations on gui.
-
This is why I would like to add a rule on my router so they can all go through the SMTP server of my ISP.
Can you do it with your package postfix?I think you will need authentication for these clients.
You can manually install and configure sasl as current version does not has this integrations on gui.
ok, thank you!
-
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 - about a month later
-
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.
-
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.
- 15 days later
-
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 placeBut mail search is not working. DB is created, but it's empty ((
Pfsense ver 2.0.2 i386
-
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?
- 17 days later
-
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
-
- about a month later
-
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 = 30dCopying the postscreen_cache file saves having the new install re-learn all the whitelisted SMTP client IPs that the existing install knew about.
-
biggsy,
Thanks for your feedback :)
-
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
-
It's a normal behavior. You have low memory machines.
-
Thank you Marcelloc
Indeed I have 1024MB.
But why processes use so much memory now ?
This is a huge difference ! -
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_" -
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 …
-
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.)
-
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.
Thanks for your feedback. :)
-
It's fixed now.
Indeed it is.
Thank you once again marcelloc :)
-
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? -
Very nice work (um trabalho extraordinario!), congrats!
Thanks!:)
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/ -
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) -
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
-
@ics:
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 ?It's not such as big deal, in fact even Google's Gmail "reveals" its internal IPs / hostnames in the Received headers.
Anyway, if you really want to remove all traces of your local hostnames & IPs, you can use Postfix's
header_checks =
to instruct Postfix to ignore (i.e. delete when forwarding mail) certain "Received: " lines.
However I don't know if pfSense's Postfix package allows you to configure this feature from the webGUI.Btw could someone please comment on my question a few days ago: "Is the per process memory usage of 200M+ normal ?"
-
It's not such as big deal, in fact even Google's Gmail "reveals" its internal IPs / hostnames in the Received headers.
Anyway, if you really want to remove all traces of your local hostnames & IPs, you can use Postfix's
header_checks =
to instruct Postfix to ignore (i.e. delete when forwarding mail) certain "Received: " lines.
However I don't know if pfSense's Postfix package allows you to configure this feature from the webGUI.Btw could someone please comment on my question a few days ago: "Is the per process memory usage of 200M+ normal ?"
Thanks, I'll try that.
For me it's not normal that the process takes more than 200M as it was not the case in the previous version of pFsense.
But Marcello said that it's a normal behavior with low memory machines.
Then I added RAM up to 2GB and the process indeed takes about 68MB…So now the process takes less RAM but for that I had to increase server RAM...Weird !
-
Hello Marcelo, i have one question, i have a mail server behind a pfsense, one postfix mail server with 20 domains and 200 users aprox, if i install this package what is the more easy way to config this, to make my first level barrier of spam in pfsense ¿??? i don't want put all domains or users or ldap sync with my server :-( It is this possible ??
-
…one postfix mail server with 20 domains and 200 users...
If you are running a postfix mailserver I doubt that you get much benefit from running the postfix forwarder in pfSense. (You didn't mention postfix in your other post.) Maybe you just need to configure the postfix mailserver to do what you need.
-
what is the more easy way to config this, to make my first level barrier of spam in pfsense ¿???
Follow default options on gui, it will be easy :)
I don't want put all domains or users or ldap sync with my server :-( It is this possible ??
you have to configure it on pfsense to filter unknow domains, mailboxes, spf, forged sender domains, etc, etc ,etc during message header. this way, you save bandwidth while rejecting most spams before they send data.
-
Dear Marcello,
Thank you once again for the package ! My mail gateway is running well.
I have some questions:
- Did you updated it to 2.10.0 version? Is that correct? Because I saw on the Package Management of my pfsense box (pls see the attached file for more details).
- Does new version work smoothly? Does it has any new features? (Ex: SMTP Relay server by authentication or Trusted IPs methods)
Looking forward to hearing from you soon.
Best regards,
DQM -
@DQM:
- Did you updated it to 2.10.0 version? Is that correct? Because I saw on the Package Management of my pfsense box (pls see the attached file for more details).
Yes. 2.10 is the latest stable version.
@DQM:
- Does new version work smoothly? Does it has any new features? (Ex: SMTP Relay server by authentication or Trusted IPs methods)
Yes. The new feature on gui is an helo acl and new sync code and also working on pfsense 2.1 .
I'll include some thay mem cache for postscreen. I'm running my antispam boxes without issues with postfix 2.10. -
@DQM:
- Did you updated it to 2.10.0 version? Is that correct? Because I saw on the Package Management of my pfsense box (pls see the attached file for more details).
Yes. 2.10 is the latest stable version.
@DQM:
- Does new version work smoothly? Does it has any new features? (Ex: SMTP Relay server by authentication or Trusted IPs methods)
Yes. The new feature on gui is an helo acl and new sync code and also working on pfsense 2.1 .
I'll include some thay mem cache for postscreen. I'm running my antispam boxes without issues with postfix 2.10.Thanks for your information, Marcello !
-
what is the more easy way to config this, to make my first level barrier of spam in pfsense ¿???
Follow default options on gui, it will be easy :)
I don't want put all domains or users or ldap sync with my server :-( It is this possible ??
you have to configure it on pfsense to filter unknow domains, mailboxes, spf, forged sender domains, etc, etc ,etc during message header. this way, you save bandwidth while rejecting most spams before they send data.
Thank you Marcelo i try to search some information to sync ldap with my postfix server and try to make some tests, and search for get some free time :-(
-
I decided to auto-start my test pfSense 2.1 VM when booting ESXi - postfix failed to start and left the following log entries:
User.Error 192.168.111.51 May 24 16:35:28 php: : Stopping postfix User.Error 192.168.111.51 May 24 16:35:28 php: : Stopping postfix Mail.Critical 192.168.111.51 May 24 16:35:28 postfix/postfix-script[17736]: fatal: the Postfix mail system is not running User.Error 192.168.111.51 May 24 16:35:28 php: : The command '/usr/local/etc/rc.d/postfix.sh stop' returned exit code '1', the output was '/usr/pbi/postfix-amd64/sbin/postconf: warning: /usr/pbi/postfix-amd64/etc/postfix/master.cf: unused parameter: user=postfix' Mail.Critical 192.168.111.51 May 24 16:35:28 postfix/postfix-script[17885]: fatal: the Postfix mail system is not running User.Error 192.168.111.51 May 24 16:35:28 php: : The command '/usr/local/etc/rc.d/postfix.sh stop' returned exit code '1', the output was '/usr/pbi/postfix-amd64/sbin/postconf: warning: /usr/pbi/postfix-amd64/etc/postfix/master.cf: unused parameter: user=postfix' Syslog.Error 192.168.111.51 May 24 16:35:29 syslogd: exiting on signal 15 Kernel.Info 192.168.111.51 May 24 16:35:30 syslogd: kernel boot file is /boot/kernel/kernel User.Error 192.168.111.51 May 24 16:35:29 php: : Writing out configuration Syslog.Error 192.168.111.51 May 24 16:35:30 syslogd: exiting on signal 15 Kernel.Info 192.168.111.51 May 24 16:35:30 syslogd: kernel boot file is /boot/kernel/kernel User.Error 192.168.111.51 May 24 16:35:30 php: : Writing out configuration User.Error 192.168.111.51 May 24 16:35:32 php: : Writing rc_file User.Error 192.168.111.51 May 24 16:35:32 php: : Writing rc_file User.Error 192.168.111.51 May 24 16:35:33 php: : Stopping postfix Mail.Critical 192.168.111.51 May 24 16:35:33 postfix/postfix-script[27296]: fatal: the Postfix mail system is not running User.Error 192.168.111.51 May 24 16:35:33 php: : The command '/usr/local/etc/rc.d/postfix.sh stop' returned exit code '1', the output was '/usr/pbi/postfix-amd64/sbin/postconf: warning: /usr/pbi/postfix-amd64/etc/postfix/master.cf: unused parameter: user=postfix' User.Error 192.168.111.51 May 24 16:35:33 php: : Stopping postfix User.Error 192.168.111.51 May 24 16:35:34 php: : The command '/usr/local/etc/rc.d/postfix.sh stop' returned exit code '126', the output was '/usr/local/etc/rc.d/postfix.sh: Permission denied' User.Notice 192.168.111.51 May 24 16:35:34 check_reload_status: Syncing firewall Syslog.Error 192.168.111.51 May 24 16:35:34 syslogd: exiting on signal 15 Kernel.Info 192.168.111.51 May 24 16:35:35 syslogd: kernel boot file is /boot/kernel/kernel User.Error 192.168.111.51 May 24 16:35:35 php: : Writing out configuration Syslog.Error 192.168.111.51 May 24 16:35:35 syslogd: exiting on signal 15 Kernel.Info 192.168.111.51 May 24 16:35:36 syslogd: kernel boot file is /boot/kernel/kernel User.Error 192.168.111.51 May 24 16:35:36 php: : Writing out configuration User.Error 192.168.111.51 May 24 16:35:38 php: : Writing rc_file User.Error 192.168.111.51 May 24 16:35:38 php: : Writing rc_file User.Error 192.168.111.51 May 24 16:35:39 php: : Stopping postfix User.Error 192.168.111.51 May 24 16:35:39 php: : Stopping postfix Mail.Critical 192.168.111.51 May 24 16:35:39 postfix/postfix-script[39090]: fatal: the Postfix mail system is not running User.Error 192.168.111.51 May 24 16:35:39 php: : The command '/usr/local/etc/rc.d/postfix.sh stop' returned exit code '1', the output was '/usr/pbi/postfix-amd64/sbin/postconf: warning: /usr/pbi/postfix-amd64/etc/postfix/master.cf: unused parameter: user=postfix' User.Error 192.168.111.51 May 24 16:35:39 php: : The command '/usr/local/etc/rc.d/postfix.sh stop' returned exit code '126', the output was '/usr/local/etc/rc.d/postfix.sh: Permission denied' Syslog.Error 192.168.111.51 May 24 16:35:41 syslogd: exiting on signal 15 Kernel.Info 192.168.111.51 May 24 16:35:42 syslogd: kernel boot file is /boot/kernel/kernel User.Error 192.168.111.51 May 24 16:35:41 php: : Writing out configuration Syslog.Error 192.168.111.51 May 24 16:35:42 syslogd: exiting on signal 15 Kernel.Info 192.168.111.51 May 24 16:35:42 syslogd: kernel boot file is /boot/kernel/kernel User.Error 192.168.111.51 May 24 16:35:42 php: : Writing out configuration User.Error 192.168.111.51 May 24 16:35:44 php: : Writing rc_file User.Error 192.168.111.51 May 24 16:35:44 php: : Writing rc_file User.Error 192.168.111.51 May 24 16:35:45 php: : Stopping postfix User.Error 192.168.111.51 May 24 16:35:45 php: : Stopping postfix Mail.Critical 192.168.111.51 May 24 16:35:45 postfix/postfix-script[50014]: fatal: the Postfix mail system is not running User.Error 192.168.111.51 May 24 16:35:45 php: : The command '/usr/local/etc/rc.d/postfix.sh stop' returned exit code '1', the output was '/usr/pbi/postfix-amd64/sbin/postconf: warning: /usr/pbi/postfix-amd64/etc/postfix/master.cf: unused parameter: user=postfix' User.Error 192.168.111.51 May 24 16:35:45 php: : The command '/usr/local/etc/rc.d/postfix.sh stop' returned exit code '126', the output was '/usr/local/etc/rc.d/postfix.sh: Permission denied' User.Notice 192.168.111.51 May 24 16:35:46 check_reload_status: Syncing firewall Syslog.Error 192.168.111.51 May 24 16:35:46 syslogd: exiting on signal 15 Kernel.Info 192.168.111.51 May 24 16:35:47 syslogd: kernel boot file is /boot/kernel/kernel User.Error 192.168.111.51 May 24 16:35:47 php: : Writing out configuration Syslog.Error 192.168.111.51 May 24 16:35:47 syslogd: exiting on signal 15 Kernel.Info 192.168.111.51 May 24 16:35:48 syslogd: kernel boot file is /boot/kernel/kernel User.Error 192.168.111.51 May 24 16:35:47 php: : Writing out configuration User.Error 192.168.111.51 May 24 16:35:49 php: : Writing rc_file User.Error 192.168.111.51 May 24 16:35:49 php: : Writing rc_file User.Error 192.168.111.51 May 24 16:35:50 php: : Stopping postfix User.Error 192.168.111.51 May 24 16:35:50 php: : Stopping postfix Mail.Critical 192.168.111.51 May 24 16:35:50 postfix/postfix-script[59480]: fatal: the Postfix mail system is not running User.Error 192.168.111.51 May 24 16:35:50 php: : The command '/usr/local/etc/rc.d/postfix.sh stop' returned exit code '1', the output was '/usr/pbi/postfix-amd64/sbin/postconf: warning: /usr/pbi/postfix-amd64/etc/postfix/master.cf: unused parameter: user=postfix' User.Error 192.168.111.51 May 24 16:35:50 php: : The command '/usr/local/etc/rc.d/postfix.sh stop' returned exit code '126', the output was '/usr/local/etc/rc.d/postfix.sh: Permission denied' Syslog.Error 192.168.111.51 May 24 16:35:51 syslogd: exiting on signal 15 Kernel.Info 192.168.111.51 May 24 16:35:51 syslogd: kernel boot file is /boot/kernel/kernel User.Error 192.168.111.51 May 24 16:35:51 php: : Writing out configuration Syslog.Error 192.168.111.51 May 24 16:35:51 syslogd: exiting on signal 15 Kernel.Info 192.168.111.51 May 24 16:35:51 syslogd: kernel boot file is /boot/kernel/kernel User.Error 192.168.111.51 May 24 16:35:53 php: : Writing rc_file User.Error 192.168.111.51 May 24 16:35:53 php: : Writing rc_file User.Error 192.168.111.51 May 24 16:35:54 php: : Stopping postfix Mail.Critical 192.168.111.51 May 24 16:35:54 postfix/postfix-script[70188]: fatal: the Postfix mail system is not running User.Error 192.168.111.51 May 24 16:35:54 php: : The command '/usr/local/etc/rc.d/postfix.sh stop' returned exit code '1', the output was '/usr/pbi/postfix-amd64/sbin/postconf: warning: /usr/pbi/postfix-amd64/etc/postfix/master.cf: unused parameter: user=postfix' User.Error 192.168.111.51 May 24 16:35:54 php: : Stopping postfix User.Error 192.168.111.51 May 24 16:35:54 php: : The command '/usr/local/etc/rc.d/postfix.sh stop' returned exit code '126', the output was '/usr/local/etc/rc.d/postfix.sh: Permission denied' Kernel.Critical 192.168.111.51 May 24 16:35:56 kernel: VMware memory control driver initialized Auth.Info 192.168.111.51 May 24 16:35:57 login: login on ttyv0 as root System4.Notice 192.168.111.51 May 24 16:35:57 sshlockout[84092]: sshlockout/webConfigurator v3.0 starting up Auth.Emerg 192.168.111.51 May 24 16:56:29 php: /index.php: Successful login for user 'admin' from: 192.168.111.7 Auth.Emerg 192.168.111.51 May 24 16:56:29 php: /index.php: Successful login for user 'admin' from: 192.168.111.7 Auth.Emerg 192.168.111.51 May 24 16:56:29 php: /index.php: Successful login for user 'admin' from: 192.168.111.7 User.Error 192.168.111.51 May 24 16:57:21 php: /status_services.php: The command '/usr/local/etc/rc.d/postfix.sh stop' returned exit code '126', the output was '/usr/local/etc/rc.d/postfix.sh: Permission denied' Mail.Warning 192.168.111.51 May 24 16:57:24 postfix/postfix-script[62930]: warning: not owned by root: /var/spool/postfix Mail.Info 192.168.111.51 May 24 16:57:24 postfix/postfix-script[67208]: starting the Postfix mail system Mail.Info 192.168.111.51 May 24 16:57:24 postfix/master[67631]: daemon started -- version 2.10.0, configuration /usr/pbi/postfix-amd64/etc/postfix
Started fine from the service status page though.
-
Just realized that I did an update to the latest 2.1 snap last night and forgot to re-enable postfix and pfBlocker.
Why aren't these two packages re-enabled automatically after updating, if they were enabled before?
-
Why aren't these two packages re-enabled automatically after updating, if they were enabled before?
The uninstall process disables it.
- 9 days later
-
Hi Marcello,
first of all thank you very much for this excellent module! It makes my work much easier, since I am not really a postfix specialist.
I've never seen this error during package install.
check if pkg_info return two postfix installs or something.
EDIT:
Let me know if this feature works with zimbra ldap.
It's written for Active directory ldap search.att,
Marcello CoutinhoI am using the package in combination with the Zimbra mail server. When I try to do the recipient retrival via LDAP, I come to a limitation which has its cause in the different LDAP structure of Zimbra compared to MS AD. Looking at the query your module submits, I see that it is expecting a SAMAccount. This entity is not present in the Zimbra LDAP. The Zimbra LDAP structure looks like the following:
dc=tld
dc=mydomain
ou=people
uid= <user id1="">mail=u1@b.c
mail=u1_alias1@b.c
mail=u1_alias2@b.c
…
uid= <user id2="">mail=u2@b.c
mail=u2_alias1@b.c
...uid is of types inetOrgPerson, zimbraAccount and amavisAccount. Is it possible for me to modify the query in one of the config files, or does it require a change in the source code? Would you be interested in extending the LDAP part to include Zimbra queries? If so, I could prepare the query and provide it to you.
Greetings,
Burkhard</user></user> -
Hi,
maybe I found the solution: The LDAP query is nicely wrapped in the /usr/local/bin/adexport.pl, so no recompile neccessary. I did the following modification:
56c56 < our $filter = '(|(objectClass=publicFolder)(&(sAMAccountName=*)(mail=*)))'; --- > our $filter = '(&(uid=*)(mail=*))';
It seems to work and only lists userIds with valid email addresses. The technical users like spam and ham do not get selected and are not forwarded.
Does it make sense to use the filter value a Perl script parameter and make it selectable from a drop down box for Exchange and Zimbra (and potentially further mail server types)?
Greetings,
Burkhard -
ok, was a bit more complicated:
56c56 < our $filter = '(|(objectClass=publicFolder)(&(sAMAccountName=*)(mail=*)))'; --- > our $filter = '(&(uid=*)(mail=*))'; 92c92 < attrs => [ "proxyAddresses" ], --- > attrs => [ "mail" ], 163,164c163,164 < my @mails = grep { /^smtp:/i && !$gSeen{$_}++ } < $data->get_value( "proxyAddresses" ); --- > my @mails = grep { !$gSeen{$_}++ } > $data->get_value( "mail" ); 168c168 < print map { s/^smtp:(.+)$/\L$1\n/i; $_ } @mails; --- > print map { s/^(.+)$/\L$1\n/i; $_ } @mails;
I did not recognize the problem that the recipient list remained empty because all mails got forwarded to the mail server then anyhow…
Greetings,
Burkhard - 8 days later
-
I successfully upgraded to postfix v2.10 :)
I've noticed that with this new postfix package, the file /var/log/maillog is not deleted anymore after a reboot.Does it mean that now there is a kind of logrotate configured for this file ? If yes how is it configured ?
This file is 238MB and keep growing…
-
@ics:
Does it mean that now there is a kind of logrotate configured for this file ? If yes how is it configured ?
No log rotate yet.
- 16 days later
-
hello
I'm getting this error after update postfix 2.10
postfix/postscreen[63302]: fatal: btree:/var/db/postfix/postscreen_cache: unable to get exclusive lock: Resource temporarily unavailable
any solution?