efa-project.org

For some reason your machine choked on this function. This function is indeed called by RPC. Based on the PHP warning, it couldn't open the /var/spool/postfix/hold directory. function postfixinq() { $handle = opendir('/var/spool/postfix/hold/'); $inq = 0; while (false !== ($file = readdir($handle)))...

Also recommend that you have SPF/DKIM/DMARC configured for your domain(s).

Here's a link for setting up ARC viewtopic.php?p=19707

postfwd is a great solution to this problem

Yes, it has been a while. Sorry about that. Life gets in the way sometimes.

I have eFa5 for EL9 OSes nearly complete and am going to release a postfix update for eFa4 very soon.

Hope this helps.

Make sure opendkim-tools and openarc is installed and execute the following (substitute your domain for example.com) opendkim-genkey -D /etc/openarc -s arc -d example.com Make an entry for DNS in your domain and name it arc._domainkey using info in arc.txt /etc/openarc.conf: Syslog yes UserID openar...

You won't want to keep emails in eFa indefinitely for this reason. You'll want to come up with a reasonable quarantine retention that balances performance.

You can adjust the retention in eFa-Configure under MailWatch Settings.

What is in /var/log/eFa/build.log ?

Look forward to seeing what you have done.

This is the right forum to post, thank you for posting those.

Yes, please continue to post them here. I am looking into how to mitigate them with an update.

Should be fixed now. One of the mirrors was way behind.

I believe this is the DKIM code in SpamAssassin that is the culprit here. I'd be curious how this compares to the Authentication-Results header in the same email. I'm betting that opendkim says it is passing and SpamAssassin is erroneously saying otherwise.

This definitely looks like a bug. The Received line should always look like this: Received: from out208-127.dm.aliyun.com (out208-127.dm.aliyun.com [140.205.208.127]) and never like this: Received: from out208-127.dm.aliyun.com (4S00JX0yDtz4x8Mx) The "4S00JX0yDtz4x8Mx" is a smtp queue ID. ...

I am deciding what to do. I have been away most of this year due to many things going on in my life.

I have an "eFa v5" built on CentOS 9 Stream, though. With some fixes I can get it out the door. This would get anyone interested an upgrade path for continued OS support.

I will work on getting things fixedup for CentOS 7 here. Apologies for the delay. I have had health issues.

I'm not exactly sure why this is failing. To troubleshoot, what I would do is manually carry out the restore tasks that can be found in /var/eFa/lib/eFa-Configure/func_systemrestore So, starting on line 60 when a backup is chosen it starts by cd in to /var/eFa/backup and then expands the tarball. Th...

Just out of curiosity, did you set up the replacement with eFa Init before restoring the backup?

It appears either the database isn't running or wasn't initialized, which means you may need to run through setting up the appliance, then run the restore over it so that the database is in a ready state.

Your problem is likely clamd. The /var/log/maillog would reveal what is going on.

You are also on v3, and I'm surprised it is still even functioning.

Fixed here:

https://github.com/MailScanner/v5/pull/614

I'll roll up a new release of MailScanner and pull into eFa, I have quite a few fixes pending.

The DMARC reports are controlled with cron jobs that you can optionally disable. /etc/cron.daily/eFa-Daily-DMARC is probably the one you want to examine. Comment the line mentioning /usr/sbin/opendmarc-reports

Glad to know you got it fixed!

eFa is not ready for v9 OSes yet. I have to do some work there.

Yeah this is a bug. The PeerList needs to be comma separated. You can work around it by using brackets for the IP portion and editing /etc/opendkim.conf to comma separate the entries. I'll prepare a fix.