efa-project.org

Yeah, one of the bigger rules was no one listed in the TO field (since they BCC everyone for privacy).
I might suggest that they address the email to themselves to save a couple of spam points.

Thanks for the pointers. I'll give the trusted network a try and see what happens. It's hard to describe to the client how to make the emails less spammy, which is why I thought whitelisting the email address they use should have worked. It does work fine when they send to a low number of recipients...

Since "whitelist" isn't a searchable term on here I'm having to make this query (sorry). I have recently added a new client to our email hosting. We use Exchange 2013, and EFA sits in between the real world and the Exchange server filtering in both directions. We've had pretty much zero pr...

rickriv90210 wrote: ↑16 Feb 2018 16:32How can I request a new feature for the ability to block by from email domain?

I've just run into the situation where I'd like to implement this feature also (via sender_access, not blacklists).
I have a feeling I once configured something similar in the past, but having a mental block right now.

Figured out what it was... one of the extensions was being picked up in mime_header_checks so Postfix was binning the file before MailScanner even got to see it.

I'll leave this here as a reminder.

Hi all, I've followed the instructions on this forum to allow double extension file names, but I'm still seeing 5.7.1 message content rejected coming up in our logs. What would be the best procedure to test why this still might be occurring? We have a client who needs to drop this rule due to them r...

Happy to help.
Hopefully it proves helpful to others also.

Lucky for you I scribbled down notes as I did this. Hopefully they make sense. Create a new user account for the external user before starting. These details will be used toward the end of the procedure. Also, don't forget to open port 587 to EFA. nano /etc/postfix/master.cf remove # from line #subm...

We don't want to expose Exchange any more than port 443 for our Outlook users.
Having EFA sitting in between provides a good layer of protection between the outside world and Exchange.

Got it working... had to use a combination of the posts to get it working, but the contractor can now send using our EFA server as an SMTP server after authentication via TLS on port 587. Thanks for the links above, and looking forward to any future developments being able to do this natively as hin...

Many thanks Shawn... we'll test on Monday when back in the office.

Pardon my ignorance, but our knowledge only extends far enough to get EFA installed and working perfectly, but not for modifying the configuration very much. We'd like to achieve the following if possible, and would appreciate any insight as to how we can make it happen. We would like to allow an ex...

I noticed this happen in far more versions that just the latest.
Never worried about it as freshclam always worked fine, even via cron.
Happy to see a resolution for it though.

Flush web cache and cookies apparently resolves this.
Didn't permanently work in my case, but easy enough to try.

solarthread wrote: ↑29 Mar 2017 07:32 The security token issue just logout clear your cache and log back in and it should behave

Except it still happens after a cache & cookie clear. This is not a definitive fix for us.

We upgraded our RAID card from zero to 4GB of cache, and what a difference it made.
It now takes 1-2 secs to learn compared to the ~30 it used to take.
This very much feels like it's related to disk IO speed.

Could this possibly be caused by someone attempting to login/hack Mailwatch whilst you are already logged in? The same error just occurred to me on one server after I'd been working on it for ~10 mins. The following line came out of error_log: [Tue Mar 28 09:32:30 2017] [error] [client 93.174.93.136...

Looking forward to it... having several issues since the update unfortunately.
Thanks for the great work so far.

Also having this issue across 3 recently upgraded servers.
Is there a way to automate this fix, or does it require manual intervention?

Also receiving a lot of "Error: unable to validate security token" problems after upgrade.

jon, edit /etc/MailScanner/MailScanner.conf Change the following line to something more suitable. I've used 900 for my setup. SpamAssassin Timeout = 900 (Should be set to 75 by default) Anything less than this and spam would pass through to our mail server. I'm not sure what the issue is, but of the...