-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug report: ClamAV: failed to scan, maximum retransmits exceed #3320
Comments
I think I had seen this in my Rspamd log as well, but as I didn't see it anywhere else, I was not investigating further. I will have a look though. |
Probably related to Mailu/Mailu#2321 and https://community.mailcow.email/d/1940-clamav-failed-to-scan-maximum-retransmits-exceed. Should be a non-issue when it comes to actually receiving e-mails. They just wont be scanned by Clam. |
Adding timeout = 10;
retransmits = 2; to these seem to be valid settings, even though they are poorly documented. @rhyst could you please also try them? You could set the settings in |
I have created
And the error is maybe no longer appearing (have recieved a few emails). Will keep an eye on it. Is there a way to confirm that rspamd is actually running clamav? |
If any mail is sent locally to a system user like It's common for cron jobs run as Amavis (which includes for SpamAssassin IIRC) to not have an alias configured, thus they arrive at |
It is noted in the Rspamd log at I will provide a PR for this, but we'll wait a bit to make sure the error really is gone. |
@rhyst have you been seeing the issue ever since you adjusted |
I have not seen the error again, so it seems to be an effective fix for me |
Alright, thanks for the feedback. I merged #3331 which will bring this addition to If the issue re-appears, please ping me :) |
Preliminary Checks
Affected Component(s)
Rspamd antivirus scanning
What happened and when does this occur?
When an email is recieved I see the error:
In the rspamd web ui, on the history page, in the errors section.
What did you expect to happen?
I don't expect to see that error, or I expect to see an error with Clamav somewhere.
How do we replicate the issue?
ENABLE_RSPAMD
andENABLE_CLAMAV
in the environment vars....
DMS version
v12.1.0
What operating system is DMS running on?
Linux
Which operating system version?
Ubuntu 20.04
What instruction set architecture is DMS running on?
AMD64 / x86_64
What container orchestration tool are you using?
Docker
compose.yaml
Relevant log output
Log from recieving an email:
Other relevant information
It looks like clamav is running:
But I don't see any errors anywhere else.
I actually don't know for sure if this worked for sure with spamassassin as I am not sure where the errors would surface there. I am unsure how to debug further.
Thank you for any help
What level of experience do you have with Docker and mail servers?
Improvements to this form?
No response
The text was updated successfully, but these errors were encountered: