Dear proxmox,
we've some troubles receiving mails from an external domain including attachements of a size of roundabout 7Mbyte.
Our Proxmox mail-gateway HA cluster has version 2.0 build 2123. In 'configuration' --> 'mail-proxy' --> 'options' --> 'message size limit' is set to zero. I've already tried the following but nothing works at all:
- sender in rules' whitelist added
- sender-domain in greylist-exclusions added
- sender-domain to recipient in quarantine-whitelist added
Additional I've tested mail delivery with an 10Mbyte attachement which includes a zip-file. With or without setting a password in the zip archive doesn't matter.
Each time I've got back an error message looking like this:
user.name@destinationdomain.de
SMTP error from remote mailer after end of data:
host mailserver2.destinationdomain.de [1.2.3.4]: 552 5.3.4 Error:
message file too big
I appreciate any suggestions.
By the way: Does Clam-AV could produce such a mail handling by looking into the zip archive and reckognizing an executable which is hitting the default rule of dangerous content although this rule only removes the attachement and should delive the mail to the recipient?
Kind regards,
Olli
we've some troubles receiving mails from an external domain including attachements of a size of roundabout 7Mbyte.
Our Proxmox mail-gateway HA cluster has version 2.0 build 2123. In 'configuration' --> 'mail-proxy' --> 'options' --> 'message size limit' is set to zero. I've already tried the following but nothing works at all:
- sender in rules' whitelist added
- sender-domain in greylist-exclusions added
- sender-domain to recipient in quarantine-whitelist added
Additional I've tested mail delivery with an 10Mbyte attachement which includes a zip-file. With or without setting a password in the zip archive doesn't matter.
Each time I've got back an error message looking like this:
user.name@destinationdomain.de
SMTP error from remote mailer after end of data:
host mailserver2.destinationdomain.de [1.2.3.4]: 552 5.3.4 Error:
message file too big
I appreciate any suggestions.
By the way: Does Clam-AV could produce such a mail handling by looking into the zip archive and reckognizing an executable which is hitting the default rule of dangerous content although this rule only removes the attachement and should delive the mail to the recipient?
Kind regards,
Olli