Postfix - antispam and relay package

marcelloc

Darklogic,

try this setup on your postfix:

First go to on diagnostics -> edit file
type /etc/hosts in 'Save / Load from path:' then press load
WITH CAUTION, include the ip address and the wrong helo info from remote domain you want to receive email.

24.123.130.226 CNASRV.CNA.local

press save button.

Go to postfix configuration and add custom cf options:

disable_dns_lookups = yes

Save config and see what will happen with your server.
If it works, also check if /etc/hosts file keeps the info after a reboot.

I saw no options to relax reject_unknown_client_hostname.

This is the postfix documentation for this option:

disable_dns_lookups (default: no)
Disable DNS lookups in the Postfix SMTP and LMTP clients. When disabled, hosts are looked up with the getaddrinfo() system library routine which normally also looks in /etc/hosts.

DNS lookups are enabled by default.

darklogic

marcelloc,

It looks like it works. I have not had a chance to reboot yet. I will keep an eye on this and see how it pans out. Also, I like the new pfblocker you and tommyboy are working on.

Thanks for the detailed configuration info.

MDP

darklogic

marcelloc,

I added a couple more into the /etc/hosts and then saved the config. For some reason it is removing the entries. They will just randomly drop off the list, but I can see where dynamic dhcp client on the internal network are getting added to this list? The only entry that is not getting removed is the example one I used and you used in your post?

Not sure what I am doing wrong. It corrected the issue with only the first manually added host and IP.

Thanks,

MDP

marcelloc

For internal clients, the best way is to include their hostnames on your local dns.

Setup your pfSense box to use your internal dns.

But, if you are using dns Forwarder on pfsense, you can also include these host info on it.

And don't forget to save postfix config after any host change.

mauricioniñoavella

marcelloc

regards

what a pity to disturb, look I'm working and making changes to the cfg and Services: Postfix relay and spam, but not working.

not to do just what I want is a postfix relay host, that I may have a serviodor forwarder external mail, which is in zimbra

using a generic account with authentication and security is, with STARTTLS

as I have written before I had the problems that no longer do.

thanks
for your collaboration

marcelloc

mauricioniñoavella,

As we saw in ermal post, package cyrrus has a missing dependencie in pfsense. Its not a missing compile arg, so there is nothing I can do to Fix it.

For now, postfix Forwarder Does not has SASL option.

If you want a quick solution for that, buy some commercial support hours as ask pfsense team to Fix it.

If you google for you problem, you will find that openldap client requires cyrrus too.

good luck on your trouble shooting.

mauricioniñoavella

marcelloc
then you confirm that the problem is not yours, rom problems pfSense team, then you spor angry about this that you wrote

I see you work for us.

many thanks for your collaboration

marcelloc

@mauricioniñoavella:

marcelloc
then you confirm that the problem is not yours, rom problems pfSense team, then you spor angry about this that you wrote

I see you work for us.

many thanks for your collaboration

mauricioniñoavella,

you must understand one thing.

pfsense's team released version 2.0 with no need of cyrrus-sasl library, so the problem is not with pfsense's team.

Packages are contributions and almost created and maintained by community, so when a package has a problem, the problem is not on pfsense2.0.

When somebody builds a package, all ports compilation is done by pfsense team BUT it does not means that is fully supported by them.

Pfsense is one thing, packages is another thing completely apart of base project.

if you don't like the way libraries are missing on pfsense, try installing freebsd packages on labs.

I'm not angry about anything in pfsense's project, its perfect to me.

mauricioniñoavella

marcelloc

To my pfSense also is an excellent project.

In fact I think it is good to realize this problem, as I have experienced that served to improve your package. And that the community forum to find out.
It is very important to account for other versions as I could incorporate cyrrus-sasl library, I hope you will contribute to have been able to let you know this,
Thank you very much for your input.
To think this forum, to share and we want this project. As is pfSense, and do not take as a destructive criticism but a constructive criticism.
I hope you take it in practice because it is a benefit to all who participated in this forum, showing the possible problems that arise in the project, to improve it.
The Free BSD Project was born to be a complete Unix-like operating system free software, software that respects your freedom. and best of all and for all.

I will be working to bring you the package for continuous improvement in your work is excellent, because I think an excellent system, and wait when you merge with relay host including cyrrus-sasl.

thanks

Mauricio

marcelloc

HI all,

I've just released package version 2.2 with:

Sqlite database log support
Widget for dashboard with mail stats
Search email tool for diagnostics
checkbox to enable or not smtp_valid_hostname_check
few more help info for easier setup

check first post for screen shots.

darklogic

Awsome news. I hope this corrects my issue. I will post something here in a bit that I have encountered.

darklogic

OK, so the rejects that I have been getting seems to occure when the remote host excepts e-mail on a different public IP than the one it sends from. I discovered this by talking with some IT people that I have been getting all these legitamite e-mail rejects on the helo host not found. They have something like an ironport or barracuda acting as a mail gateway behind a firewall in bound SMTP on a particular IP and then their mail server has a statis 1-to-1 NAT rule that translates outbound sending of mail on a different IP.

I have not idea how to even resolve this since it tries the verify back to an IP that does not listen or forward mail back to the internal mail server.

Please let me know if this is not a clear enough write up on what I am saying.

Thanks for all you do marcelloc

marcelloc

The helo smtp info can be easily configured by email admins, including Micro$oft. The default option is something internal like hostname.local if you do not use any server for relay to internet.

Unckeck this option and see how postfix deals with your spammers.

On my clients networks, I do only accept mail from server that are not misconfigured.

darklogic

on your check box for helo check. I see it says checked for default. So if I check it, I am assuming it will check helo and if it is unchecked it will not check helo?

Thanks,

darklogic

ahhh, I think your updated package has worked. I am starting to recieve these e-mails now. I just recieved the ones from earlier today.

This makes me feel so much better.

Thanks marcelloc

marcelloc

Great news. In few days you will have many logs on Database. Take a look on dashboard postfix widget and on search mail.

darklogic

I am currently looking into it. Great work marcelloc.

darklogic

This is odd. I am getting an error when trying to go to avalible packages. Are you getting this?

darklogic

This is the error I am getting. It was just working???

Unable to communicate with www.pfsense.com. Please verify DNS and interface configuration, and that pfSense has functional Internet connectivity.

darklogic

It was SNORT HTTP inspect causing the issue.

Anyways, I have a question about the logs. I am not seeing anything showing up yet. I followed the instructions, but don't understand the last line that I highlighted below in red.

Choose how often pfSense will transfer log files to Sqlite database.
To use Diagnostics -> Search mail you need to:
Select Loggin Destination to /var/log/maillog
Select update Sqlite frequency
Inlcude /^Subject:/ WARN line in Acl Headers after all your Subject rules.

Thanks,