Postfix - antispam and relay package

biggsy

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?

marcelloc

@biggsy:

Why aren't these two packages re-enabled automatically after updating, if they were enabled before?

The uninstall process disables it.

buv

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.

@marcelloc:

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 Coutinho

I 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>

buv

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

buv

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

ics

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…

marcelloc

@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.

expert_az

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?

marcelloc

Did you tried stopping postfix process and removing current /var/db file to start a new one?

expert_az

Thank you marcelloc,after stoping postfix and deleting db file it's ok now,
I will monitor logs and will inform you if it happens again

expert_az

Marcello

It happened again:((

Jun 29 09:03:51 postfix/postscreen[54318]: fatal: btree:/var/db/postfix/postscreen_cache: unable to get exclusive lock: Resource temporarily unavailable
Jun 29 09:02:50 postfix/postscreen[61744]: fatal: btree:/var/db/postfix/postscreen_cache: unable to get exclusive lock: Resource temporarily unavailable
Jun 29 09:01:49 postfix/postscreen[63059]: fatal: btree:/var/db/postfix/postscreen_cache: unable to get exclusive lock: Resource temporarily unavailable

jemarti

I need to configure PostFix to accept mail from a specific IP address even though that address is both blacklisted and is presenting a non-existent host name during HELO.

I have tried placing entries like this:
123.231.132.213 OK
in the "helo" section of the "Access Lists" tab, and also added them to /usr/local/etc/postfix/helo_check
but I am still getting the following reject message in the logs:
RCPT from unknown[123.231.132.213]: 550 5.7.1 Client host rejected: cannot find your hostname, [123.231.132.213]

Could anyone advise me on the correct way to configure PostFix so that it will bypass the helo and RBL checks for specific IP addresses?

Thanks.

KriogenBoard

Hi guys! Sorry for my bad English. I found an interesting bug. The package is sensitive to the hostname. If you do not correct the host name does not occur the record in db file. Example: mail1.example.com working, mail-1.example.com not working. All the matter in the function function_grep_log in file /usr/local/www/postfix.php . Please note this bug in the next update. Thank you. :)

kwaci

Hi All,

Im new in this forum. Im just installing pfSense with Postfix and Mailscanner package as SMTP relay for our Exchange 2003 server.
It work very well. Postscreen and RBL checks are the day saver. :)

One thing i want to ask, is it possible to block certain email address from my trusted (mynetworks) SMTP client ?

I had put the email address in the Access List –> Sender, but it doestnt have any effect. I think it is because the order in the **_smtpd_client_restrictions_** and _**smtpd_recipient_restrictions**_ started by **_permit_mynetworks_** and followed by other rules. So if the first rule is passed, it wont check the following rules.
Also im trying to change the order from the shell, but when im reload the Postfix from the GUI the main.cf back to default order.

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

Thank you

SMTPD_SENDER.jpg_thumb

kwaci

@expert_az:

Marcello

It happened again:((

Jun 29 09:03:51 postfix/postscreen[54318]: fatal: btree:/var/db/postfix/postscreen_cache: unable to get exclusive lock: Resource temporarily unavailable
Jun 29 09:02:50 postfix/postscreen[61744]: fatal: btree:/var/db/postfix/postscreen_cache: unable to get exclusive lock: Resource temporarily unavailable
Jun 29 09:01:49 postfix/postscreen[63059]: fatal: btree:/var/db/postfix/postscreen_cache: unable to get exclusive lock: Resource temporarily unavailable

Hi expert_az,

I think you have configured the Postfix to listen on multiple interfaces.
You can workaround this issue by listening postfix on localhost only and then nat external ips to 127.0.0.1. (http://forum.pfsense.org/index.php/topic,46334.msg242753.html#msg242753)

Listen_Loopback_Only.jpg_thumb

NAT_to_Loopback.jpg_thumb

expert_az

kwaci thank you for reply,i will try solution

expert_az

hello marcelloc,after upgrade version 2.10.0 pkg v.2.3.5 all queued mails in Search Mail tab displayed as hold(status) mail.

but some of theme have sent,spam or hold status,anyway to correct this issue?

FlashPan

Hi all,

I seem to having a little issue with the widget for this package.

Emails are flowing in and out fine but the widget does not show the number of emials which have been rejected etc.

The only disply the widget shows is the number of "Sent" emails which are emails that have passed through successfully and allowed into my exchange server.

I am not using the additional mailscanner and I am running pfsense 2.0.3 i386 and postfix forwarder 2.10.0 pkg v.2.3.5

Any ideas or tweaks I need to make?

Thanks and cheers all.

kwaci

@jemarti:

I need to configure PostFix to accept mail from a specific IP address even though that address is both blacklisted and is presenting a non-existent host name during HELO.

I have tried placing entries like this:
123.231.132.213 OK
in the "helo" section of the "Access Lists" tab, and also added them to /usr/local/etc/postfix/helo_check
but I am still getting the following reject message in the logs:
RCPT from unknown[123.231.132.213]: 550 5.7.1 Client host rejected: cannot find your hostname, [123.231.132.213]

Could anyone advise me on the correct way to configure PostFix so that it will bypass the helo and RBL checks for specific IP addresses?

Thanks.

Hi jemarti, try to put it in the Access List –> MyNetworks.

MyNetworks.jpg_thumb

biggsy

Jemarti,

you can add that IP to mynetworks but it would be far better to email the owner of 123.231.132.213 and ask him to fix his DNS entries so that IP address resolves to the host name sent in the HELO/EHLO command.