Skip to content

message_size_limit does not change clamd.conf MaxFileSize #2450

@lexxxel

Description

@lexxxel

Miscellaneous first checks

  • I checked that all ports are open and not blocked by my ISP / hosting provider.
  • I know that SSL errors are likely the result of a wrong setup on the user side and not caused by DMS itself. I'm confident my setup is correct.

Affected Component(s)

ClamAV

What happened and when does this occur?

I saw that clamd.conf has a fixed MaxFileSize of 25MB. I changed message_size_limit to ~50MB, that would mean, that clamd would not scan such attachments, right? I'm unsure about this behavior, maybe one would like to increase the MaxFileSize?

What did you expect to happen?

ClamAV scans all attachments

How do we replicate the issue?

None

DMS version

v10.4.0

What operating system is DMS running on?

Linux

What instruction set architecture is DMS running on?

x86_64 / AMD64

What container orchestration tool are you using?

Docker Compose

docker-compose.yml

No response

Relevant log output

No response

Other relevant information

POSTFIX_MESSAGE_SIZE_LIMIT=52428800

What level of experience do you have with Docker and mail servers?

  • I am inexperienced with docker
  • I am inexperienced with mail servers
  • I am uncomfortable with the CLI

Code of conduct

Improvements to this form?

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions