Page 1 of 1

Bug after update 3.0.1.1 --> 3.0.1.4

Posted: 12 Sep 2016 17:00
by woundride
Hi,

After I've updated my EFA system 3.0.1.1 to 3.0.1.4, I've a bug, all my incomming mails are rejected with status "Others" :
bug_efa_mail_other.jpg
bug_efa_mail_other.jpg (170.56 KiB) Viewed 16257 times
I restored a snapshot :doh:

Have you an idea ? :think:

Thank you.

Best regards,

Charles

Re: Bug after update 3.0.1.1 --> 3.0.1.4

Posted: 12 Sep 2016 18:28
by pdwalker
Hi Charles,

I think I'd need to see the full headers of one of those messages (click on the #) to get a better idea of why.

Re: Bug after update 3.0.1.1 --> 3.0.1.4

Posted: 12 Sep 2016 21:18
by shawniverson
Some thoughts...

Rebooted after updating?

Any errors from the update itself?

Does the lint tests reveal any problems?

Are you using another A/V scanner and need to add it to the new mtagroup?

Re: Bug after update 3.0.1.1 --> 3.0.1.4

Posted: 13 Sep 2016 11:01
by woundride
Hi,

Thank you for your help ;)
With you, I've found the issue.
Reading the new MailScanner configuration file, I saw that F-Prot was not proposed in the AV list :?
By removing F-Prot it's solved.

For F-Prot Users :

F-Prot is no longer compatible

Still Thanks for your help !

Best regards,

Charles

Re: Bug after update 3.0.1.1 --> 3.0.1.4

Posted: 14 Sep 2016 02:57
by toddh
Any idea when, or if, F-Prot will be functional in EFA?

We use it as well in conjuction with Clam.

Thanks for all the great work!



.

Re: Bug after update 3.0.1.1 --> 3.0.1.4

Posted: 14 Sep 2016 14:10
by toddh
Disregard, thought we were using F-Prot but its actually Sophos on EFA.

Still thanks for all the Great Work!

.

Re: Bug after update 3.0.1.1 --> 3.0.1.4

Posted: 15 Sep 2016 09:44
by woundride
I guess that's it ended for F-Prot :(

In the new MailScanner's configuration file (/etc/MailScanner/MailScanner.conf), F-Prot is no longer in the list of compatible antivirus (even if it is still in one example).