Skip to content
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

make ClamAV respect MESSAGE_SIZE_LIMIT #1646

Closed
lub opened this issue Sep 28, 2020 · 2 comments
Closed

make ClamAV respect MESSAGE_SIZE_LIMIT #1646

lub opened this issue Sep 28, 2020 · 2 comments

Comments

@lub
Copy link
Member

lub commented Sep 28, 2020

Currently ClamAV has hardcoded file size limits:
https://github.com/Mailu/Mailu/blob/master/optional/clamav/conf/clamd.conf#L44-L45

I think we should adjust these limits to also use MESSAGE_SIZE_LIMIT, as otherwise you have the confusing situation that big emails are allowed, but big attachments are getting blocked.

@lub lub added the type/bug Bug. Not working as intended label Sep 28, 2020
@jigsmshah
Copy link

lub,

any updates on this issue?

@Diman0 Diman0 removed the type/bug Bug. Not working as intended label Aug 19, 2022
@Diman0
Copy link
Member

Diman0 commented Aug 19, 2022

After discussing this in the previous triage meeting, we determined this is not a bug.
The size limits are already sane limits that cover all normal circumstances.

Allowing huge emails is something that must be done with care.
The same applies to changing the configuration of clamvav. Changing the settings to a higher setting makes you vulnerable for zip bombs (emails with smaller attachments with huge files. E.g. a small zip archive with a 8GB iso file).

It should not be too easy to change the clamav settings. People who know what they do, can simply create an host mount for directly changing the clamd config file. That is a small change to the docker-compose.yml file.

@Diman0 Diman0 closed this as completed Aug 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants