My usual limit is 100MB and then I explain to my users that:
1) That's the _email size limit_ and not the size limit for an attachment to an
email
2) Email is inefficient when used for transferring files, thus overhead
3) Email is not intended to be a system for routinely moving large files
4) You can't garuntee what other mail servers in the chain may have enabled as
maximum size limits, so upping the local limit isn't going to solve all your
problems
5) Look at OneDrive, Dropbox or Google Drive as readily available ad-hoc file
transfer options.
At 100MB I hear very few complaints. I certainly wouldn't be making the limit
any higher for the OP's scenario.
Some legacy mail systems I have to deal with, struggle with the combination of
large email + large number of recipients (when processing rules require you to
bifurcate the email into one-email-per-recipient in order to enable
per-recipient rule handling, your single 100MB email can become several
gigabytes of processing) so that's another potential factor.
Mark.
-Original Message-
From: mailop On Behalf Of Grant Taylor via mailop
Sent: Saturday, 24 October 2020 6:37 pm
To: mailop@mailop.org
Subject: [mailop] Maximum message size - tag along question.
Do you take into account the 4/3 inflation with Base64 encoding and / or allow
for any message body when setting the maximum message size that your servers
allow?
--
Grant. . . .
unix || die
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop