efa-project.org

Can you ask in the forum about the missed macros – tell them that we use this rule
body MICROSOFT_OLE2MACRO eval:check_microsoft_ole2macro()
and it failed to find the documents that had macros.

The only difference I can see is that the messages encoded in base64 but did not observer line width ...

Thank you.

The "Blocked Files" in Today's Total in the top-right of the Main screen is not up to date. We have the report filter (see below) when there have been blocked files, but the count is not up to date. Not a huge deal, but something worth mentioning.

contained an Unacceptable Attachment (>0 = TRUE ...

The fix is confirmed to be working. All is good.

All is good and updated. Thanks.

Did you just compile clam from source into a new RPM? Just wondering how you fixed it (learning exercise).



daily.cld updated (version: 21162, sigs: 1733857, f-level: 63, builder: neo)
bytecode.cld is up to date (version: 270, sigs: 46, f-level: 63, builder ...

Thanks for the update. I will apply the upgrade again on our test machine.

Kevin

Hello,

We're trying to upgrade from 3.0.0.6 to 3.0.0.8 by running "EFA-Update -update." The 3.0.0.6 to 3.0.0.7 ran just fine, it had me reboot once or twice for that kernel update. However, 3.0.0.7 to 3.0.0.8 is having trouble. It is as if something to with the clamav package not existing on ...

I would agree that makes sense. However, before we made the fix, mxtoolbox detected the correct MX record which points to EFA. One would think if EFA couldn't find MX record internally, it would then search externally, instead of just giving up? Maybe not...hmm.

Postfix transport:
newdomain.com smtp:[internal IP]

It was inbound e-mail that was not working.

When we had the newdomain hosted externally, all was well.

Then, we moved newdomain to an internal DNS server and we could not receive inbound messages.

By adding the MX record to our internal DNS ...

We recently added a new domain and had the MX record on an external DNS. We had three users successfully receiving e-mail on Exchange 2010 via EFA. We recently switched the domain to our local DNS and our entire company to the new domain to receive e-mails. We accidentally found that for 24 hours we ...

We recently had a message come in that was designated to 4 different people and was marked as spam, but the user could try to release it. However, only one person was able to release it. After anyone else tried, this message came up:

Your message has not been released from quarantine.
Our system ...

I was looking at quarantine_report.php and saw the calls for the messages. I was hesitant on changing anything because it looked like the messages from postmaster, for example, were marked null for isspam and nonspam is marked 0. I saw your change and I bet that will work.

Sorry, it is the quarantine report that is saying "Reason: UNKNOWN."

In the e-mail report, all that is sent is:

Thanks for the help. I noticed that right after I posted.

Another question: Our reports are being sent daily, which is great, but it is listing "UNKOWN" for e-mails like "postmaster@domain.com", which is the e-mail used for releasing messages to people. It's also "UNKNOWN" reporting normal/regular ...

Hello,

I'm trying to implement EFA-3.0.0.6. I've run into an issue where users cannot release quarantined/spam messages. I'm trying to migrate from ESVA to EFA.

With the default setting for /etc/MailScanner/reports/en/recipient.spam.report.txt, the “{Spam Not Delivered}” message is sent to the ...