Need help?

Our experts have had an average response time of 13.14 minutes in February 2024 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

Zimbra message size limit – Easy way to change the parameter

by | Dec 25, 2019

Are you looking for how to change the Zimbra message size limit?

It is quite easy to change the global Zimbra parameters to alter default size limits on messages.

At Bobcares, we often change the size of the message passing through Zimbra MTA, as a part of our Server Management Services.

Today, we will see how our Support Engineers do this for our customers.

A brief look onto Zimbra MTA

The Zimbra Mail Transfer Agent receives mail via SMTP. It routes the message, using the Local Mail Transfer Protocol to the Zimbra mailbox server.

The Zimbra MTA server includes Postfix, ClamAV, SpamAssassin, and Amavisd. It uses Postfix MTA for mail routing, relaying and blocking attachment.

Many of our customers approach us to change the default size limit on the mails. Let us see how we do it.

 

How we change the default Zimbra message size limit?

The total mail content size consists of both message size and file content size. But, we can change this value by changing the required parameters.

Firstly, our Support Engineers check the already existing value. For this, we get into the Zimbra console using the command,

su - zimbra

Later we check the message_size_limit and the result appears as,

Zimbra message size limit

To change this value we have to edit the zmmtaconfig file. But we can invoke this using commands. The command to change the message size limit appears as,

zmprov modifyConfig zimbraMtaMaxMessageSize 20480000
postfix reload

And this changes the default value to 20MB. But this alone does not determine the mail size. So let us see how our Support Engineers change the related parameter.

 

Other related parameters

So, we change the file upload size also. We either give a global value or give separate value per server. To set the global value we use the command,

zmprov modifyConfig zimbraFileUploadMaxSize 5000000

To set a particular file upload size for the server, we use the command,

zmprov modifyServer mail.domain.com zimbraFileUploadMaxSize 20000000

Here the file upload size just applies to mail.domain.com.

But, the zimbraMailContentMaxSize determines the overall message size. And we change the default parameter as follows,

zmprov modifyConfig zimbraMailContentMaxSize 20000000

Hence all these parameters together determine the total size of a mail passed through Zimbra.

 

[Need assistance in fixing Zimbra MTA errors? – We are available 24/7.]

 

Conclusion

In short, the Zimbra message size limit together with file upload size determines the total size of the mail. To change these parameters we can either edit the Zimbra config file or invoke it using commands. Today, we saw how our Support Engineers do this.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Categories

Tags

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF