efa-project.org

I submitted a PR to MailWatch that should resolve this issue.

https://github.com/mailwatch/MailWatch/pull/1309

I see you posted to the Spamassassin list. I don't have any specific explanation other than the SA developers have made some major changes to the bayes scoring. I would try training the bayes with a balanced corpus of known ham and spam, turning off autolearn (it isn't very smart, any badly scored e...

In order to fix this, I'm going to need a sample of an email message with headers. Are you able to send me a sample? If so, please attach and send to shawniverson@efa-project.org

Sounds like a great feature!

Be sure to submit an issue to https://github.com/mailwatch/MailWatch for this feature

Sure, open an issue here:

https://github.com/mailwatch/MailWatch

Wow that hasn't been a thing since PHP 5.3. Can you share with me some more details or screenshots? Feel free to redact or DM me.

Take a look at /var/www/html/mailscanner/conf.php and set MAILWATCH_HOSTURL:

After you add to the custom safe sites list, did you run ?

Have you tried deleting the file and letting it run again?

Chances are your sa_user password is wrong in /etc/mail/spamassassin/mailscanner.cf for some reason, so it can't connect to the bayes table and export it. Not a showstopper, since that also means your bayes is probably not working on your box anyway, so you may want to skip and start a fresh bayes o...

The /etc/MailScanner/virus.scanners.conf lists the virus scanners that can be used by eFa. Unfortunately, some of these are now dated and may not work. For example, Sophos made a recent change to a more cloud-based scanner, so the wrapper for it no longer works. avg avast avastd bitdefender clamd es...

Let's Encrypt must've started defaulting to ecdsa. I wonder if I need to add an option for this.

That is good to hear!

tesme33 wrote: ↑25 Jul 2024 20:09 HI
as im now running this config for some weeks i would like to confirm that this seems to solve the issue.

I pushed out an update to get rid of the duplicate configurations. Thanks for the help!

Fixed in 5.0.0-11.

Thanks, fixing!

Is your eFa behind another smarthost or accepting email directly from the Internet?

Bayes doesn't kick in until at least 200 messages have been learned as spam or ham.

Won't need to open a request to mailwatch. We just need to dump the >/dev/null 2>&1 in the cron job. I'll work on this. I'm also adding an extra step to the cron job to help keep the mtalog_ids clean.

https://github.com/E-F-A/eFa5/issues/15

Automatic replies with no sender are tricky. These tend to come from mailer-daemons when emails bounce (soft-fail or perm-fail) from MTAs. MailScanner tries to detect them with a watermark in the header, but oftentimes that gets stripped out. If you are having trouble with this, you can try changing...

Those mails may be similar but are not the same. Chances are the sender domain is not the same... The second email hit RCVD_IN_DNSWL_HI, which is the bulk of the negative scoring You also have some problems.... You have no Bayes scoring happening currently. You might need to retrain your Bayes DB. Y...

CentOS 7 is now EoL.

To move forward see this guide:
https://wiki.efa-project.org/doku.php?i ... tion_guide

Well, although not ideal, you could stuff most of it into a single container. It should work, but you won't have the benefit of having everything in its own respective container, of course. I think getting this software to function in a microservice model will require a major rewrite of the code. Ma...

There have been many requests for Dockerized eFa... I haven't done it for the very reason you mention. MailScanner is not suitable for containerization and is not designed as a microservice and is quite monolithic. Although it has gotten better, the following problems still exist with MailScanner: A...

Shouldn't have to, the updates are cumulative, so switching from beta to release shouldn't have caused this sort of issue.

This is strange. I am able to toggle greylisting via eFa-Configure and the check_policy_service inet:127.0.0.1:2501 appears and drops off like is should. Looking at the code I don't see anything obvious that would cause this to happen.