efa-project.org

Guessing by the lack of response, I'm the only one having issues with the no scan.

Just closing out this thread to say that I got it to work the way I need with rules and a bit of bash scripting for a cron job.

In the unlikely event someone lands here....

Change the setting in MailScanner.conf ...

I found the custom end function SQLSpamScores that seems to process the database noscan variable in the SQLSpamSettings.pm perl module. Unfortunately, I don't know perl other than regex/PCRE, so I don't know exactly what is going on. I did find the following code though.

#
# Close down Spam ...

When setting up a user, I thought that if I cleared the checkbox "Scan e-mail for Spam" for the "Scan for Spam" setting, it would allow email to pass through unscanned and maybe stored. When I test things, I am still seeing the X-Spam-Status messages, so it appears to be scanned and stored. I ...

I have some users requesting that their quarantine reports be sent first thing in the morning. The anacron daemon had started sending them at 11AM recently.

I checked that the system time was correct.

I had modified /etc/anarontab to the following:

SHELL=/bin/sh
PATH=/sbin:/bin:/usr/sbin:/usr ...

Just did an install on Alma 9 that went fine.

I enabled it as an outbound relay, and sending went fine.

Incoming does not work. I only created a single account, and email is rejected when I replied to the message from that account.

The maillog messge is: 450 4.1.1 <...> Recipient address ...

Just did an install on Alma 9 that went fine.

I enabled it as an outbound relay, and sending went fine.

Incoming does not work. I only created a single account, and email is rejected when I replied to the message from that account.

The maillog messge is: 450 4.1.1 <...> Recipient address ...

Have you tried adding the domains you want email from to the IgnoreMailFrom directive in opendmarc.conf file?
That may allow mail from the domain to process through the other filters.

bostjanc wrote: 18 May 2023 13:15 Btw. Awi.de is not even on blacklist if i check with mx toolbox. Whats up with this domain?

The problem is with the ARC-Seal headers. I don't believe it's intentional.

Steve

Question in case anyone knows.

Before I tried the solution above for a restart of the opendmarc service, I tried adding the opendmarc service to /etc/sysconfig/eFa-Monitor file with the line change

MonitoredServices=("mysqld=mysqld" "MailScanner=mailscanner" "master=postfix" "httpd=httpd" "clamd ...

The is a known issue with opendmarc.

See https://github.com/trusteddomainproject/OpenDMARC/issues/236

The fix is to edit the file /usr/lib/systemd/system/opendmarc.service and change the [Service] section to match the below by adding the restart directives.

[Service]
Type=forking
PIDFile=/run ...

New post 'cause the other is getting long.

If helpful, I have the email that caused the above issue. When the eFa server the second time, it was sent to the plain postfix backup server.

I confirmed that flushing the cache to send it from backup to primary causes eFa to crash.

Steve

Can confirm that it has happened to our eFa install as well.

Blocked the awi.de domain for now.

Steve

Edit: more debug info added

First crash was in libbsd.so.0.8.3 at offset E5D4 I don't have the disassembly for this.

Second crash was in libbsd.so.0.11.7 at offset CA84 with the disassembly ...