efa-project.org

keep your old vm running, install and configure and test a new, clean installation and when it is working, switch over to the new box.

For the amount of work involved, you're probably better off installing a brand new clean efa5 installation.

What is so important that you want to preserve from your efa3 installation?

Always go with the latest version.

When I mention the major version and not the minor version, it means the latest minor version which is 9.4 at the time of this post.

Do you have the full error message? Without the full error message, we cannot know. The full error message will tell you exactly what the problem is.

Which mail server is returning this error?

Did you try doing a search engine search for that error? (try "smtp error 5.7.1 code 554").

This article ...

[I am leaving this post here to document how I am troubleshooting this problem and it's eventual resolution]

ok, it's a couple of days later and I am still getting spamassassin timeouts. This is one example from /var/log/maillog

Jul 21 17:16:20 efa4 MailScanner[11087]: New Batch: Scanning 1 ...

Did you restore the v4 backup as mentioned in the section "v5 Commission" step?

It sounds like that the v4 database was not restored to your new system, hence the reason why you do not see the older messages.

> eFa 5 should work on any Red Hat Linux 9 compatible distribution. You don't have to use CentOS 9 Stream. You could opt for Rocky, AlmaLinux, Oracle, or even Red Hat.

I would pick one of the above. I am going with AlmaLinux 9 to replace my eFa4/Centos 7 box.

At the final stage of running /usr/sbin/eFa-Init
/usr/sbin/eFa-Commit: line 1066: unexpected EOF while looking for matching `''
/usr/sbin/eFa-Commit: line 1078: syntax error: unexpected end of file
[eFa] - Error initializing system! Please try again...

That looks familiar...

919 # Remove EFA ...

Alma Linux 9.4, minimal, fresh, install

From the /var/log/eFa/build.log

* snip *
Created symlink /etc/systemd/system/multi-user.target.wants/httpd.service → /usr/lib/systemd/system/httpd.service.
Created symlink /etc/systemd/system/multi-user.target.wants/php-fpm.service → /usr/lib/systemd ...

+1 for Alma Linux for community reasons. If it bites me in the butt later, then it's on my own head.

Eric, did you ever resolve this issue?

This sounds like an exchange transport setting.

Any luck resolving this issue? I'm curious as to what the actual problem was and the solution might be interesting to read about.

Historically, there was the MCP for blocking content: https://forum.efa-project.org//viewtopic.php?f=14&t=444 but this is no longer recommended.

Things are kept simple by adding in your own SpamAssassin rules into /etc/mail/spamassassin/local.cf

Any instructions on adding your own spamassassin ...

I think we should be notified if the /usr/bin/mailwatch/tools/Cron_jobs/mailwatch_db_clean.php script runs into an error.

This script must have been failing for me for quite some time before the problem of an excessively large mtalog_ids table came to my attention.

Shawn, is this worth raising a ...

This is a problem I've recently come across and I'm documenting how I diagnosed it in case anyone else has a similar problem.

---
This is something I've noticed recently, that not all incoming messages are scanned. For example, see the following screenshot:

EFA-spam-failure.png

You can see that ...

This might be a silly question, but which certain features are you talking about?

It's hard to give a good answer without knowing the actual question.

it's resolved for me by defining the internal_relays parameter.

yes, postfix doesn't know how to verify the user.

if you want to use user verification, you have to configure postfix so postfix can know which users are valid.

If you are filtering on the spamassassin level, you will be able to see it in the spam score for the rules that test for dkim, spf and dmarc.

If you want to test a particular message, then run the message through spamassassin using debug mode:

spamassassin -D -t < [mail messagefile somewhere ...

Marking emails to internal users with a unique header is easily done using postfix header_checks.

As for forwarding mail from external users to different location, I don't know how to do that off the top of my head, but I suspect that could be handled with postfix as well.

When you say "send gmail emails through efa" can you be more specific?

Do you mean, @gmail.com emails? or your own custom domain hosted on the gmail servers?

As a security suggestion, you shouldn't be exposing your efa box to the internet.

It is more secure to keep it accessible via a vpn.

As for your suggested changes, that should be fine but remember your changes could get overwritten after an update of efa.

Keep track of any changes you make so ...

Serious question

How many times have you had a vm corrupted?

I've been running efa in a vm for 9 years now and I've had 0 crashes or corruptions.

Has anyone ever had a vm go bad? Is this a problem you really need to solve?

Efa only filters mail. It is not a mail server. Let's assume worst case ...

There is not enough information to diagnose your problem.

Also, if it is efa version 3, then it is a really old installation and may have other problems that are causing your current problem.

Unfortunately, you are going to need someone who understands linux and php to look through the server log ...

For me, it mostly comes down to tweaking my local spamassassin settings to reflect my local mail configuration and making sure I train the bayesian filters with undetected spam.

As for performance, I only process about 1200 messages a day, and keep 60 days history, so I have no performance issues.