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" :
I restored a snapshot
Have you an idea ?
Thank you.
Best regards,
Charles
Bug after update 3.0.1.1 --> 3.0.1.4
Re: Bug after update 3.0.1.1 --> 3.0.1.4
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.
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.
- shawniverson
- Posts: 3649
- Joined: 13 Jan 2014 23:30
- Location: Indianapolis, Indiana USA
- Contact:
Re: Bug after update 3.0.1.1 --> 3.0.1.4
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?
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
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
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
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!
.
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
Disregard, thought we were using F-Prot but its actually Sophos on EFA.
Still thanks for all the Great Work!
.
Still thanks for all the Great Work!
.
Re: Bug after update 3.0.1.1 --> 3.0.1.4
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).
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).