efa-project.org

drewmorris,

dns blocklist support is already built into EFA, so you can add block lists either to postfix or to mailscanner, depending on your needs.

Going to see about pulling this in

https://github.com/E-F-A/v3/issues/213

It'll probably run the second part of the update soon, then.

You may be able to use postfix to map domain.net emails back to domain.com, effectively solving the problem at the MTA, so that you don't have to generate two lists or mess with proxyaddress mappings...

Good idea, I would suggest putting in a feature request over at MailWatch.

http://mailwatch.org/

[quote="heronimus"]Hello shawniverson, 1) There were 26 recipients in the TO: field. I will tell the sender to put them in the BCC: field. Instead of increasing the Mailscanner limit, is there any other workaround for this? If not, the only option seems to tell the endusers not using more ...

From: default
To: feedback@domain.com

not sure....I'll check...

https://github.com/E-F-A/v3/issues/194

https://github.com/E-F-A/v3/commit/5bf4 ... 350a237bc6

If auto update is enabled, perhaps something is preventing your system from updating? Rebooted lately?

I would try a manual update and see if you can spot if something is preventing the update.

Here's some info on how to update:

https://raw.githubusercontent.com/E-F-A ... LEASENOTES

templier,

I am wondering if MailScanner is having a little trouble with unicode...

Can you share the subject as it should appear?

1) How many recipients were in the To: field? (MailScanner has a limit of 20 for whitelisting by default, after than it ignores the whitelist)

2) How was the email released? Via the GUI or from the footer link? (This could be a real issue we need to fix)

This would be a good request for the MailWatch team.

http://mailwatch.org/

Are you sure it is frozen? Larger databases take longer to convert.

What version of EFA are you using?

Securiteinfo.com was removed in 3.0.0.8.

Issue #173 Enhancement - Securiteinfo.com support removed from unofficial-sigs

huh? Please elaborate.

ic, they are simply not showing up in the DNSBL lists.

Looking around the net this seems to be a pretty big issue. Who thought that all these new TLDs was a good idea? ... oh ... yea .. nvm ....

To gain rfc-822 compliance...

Should we go ahead and build in X-EFA-Origin as you describe? Wouldn't be a big deal and could be useful for other things.

Last issue then, when I log in as my users quarantine report is unchecked. Is there a setting somewhere that will enable the quarantine report for everyone? Yeah, I recall this. Not a setting per-se, but a way to force it on. The answer is hidden deep in the forums somewhere (its been a while)... h...

This sounds very possible.

I'm going to take note.

https://github.com/E-F-A/v3/issues/207

Thx for info! Sounds like we just need to abandon double file name extension checking and focus on real extensions, imo.