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.

Postfix queue file size limit exceeded – Quick fix!

by | Nov 1, 2019

Is your server reporting Postfix queue file size limit exceeded error?

This can be simply resolved by changing the message size limit in the config file.

Mails are so crucial today and so are the mail errors.

Hence, at Bobcares we provide an immediate fix for Postfix errors, as a part of our Server Management Services.

Today, let’s see how our Support Engineers set proper limits in Postfix server.

 

Understanding Postfix configuration

Postfix is one of the popular Mail Transfer Agents. And the MTA is responsible for receiving, routing and sending emails.

Now let’s have a deeper look into the configuration of Postfix.

By default, the configuration files are at /etc/postfix. The main configuration files are main.cf and major.cf.

Among both, main.cf is our topic of interest today. Because this file specifies the parameters necessary for emails.

 

How we change the Postfix file size limit?

Most times when users try to send large mail they receive the error: message file too big. When we check the log file, it gives a more detailed message. That is, the queue file size limit exceeded.

This indicates that the config setting in Postfix does not allow us to send or receive emails. Because the config has a size restriction specified. Hence, our Support Engineers edit the config file and increase the size.

Typical error message on Outlook email client appears as,

Postfix queue file size limit exceeded in Outlook.

Firstly, we open the config file that is, /etc/postfix/main.cf

Later, we add or edit the parameter message_size_limit. Always specify this value in bytes. And it indicates the maximum size of the message that can be sent or received.

We can also change this value without manually editing the config file. Our Support Engineers do this using the command,

postconf -e message_size_limit = 10240000

Here 10240000 = 10M. This is the default limit including the envelope size. The envelope size indicates the MIME encoding size.

In addition, we change the values of related parameters like mailbox_size_limit and virtual_mailbox_limit . We update the later in case of a virtual mailbox configuration. The mailbox size must be greater than the message size limit.

Finally, we reload the Postfix service to save the changes we made.

/etc/init.d/postfix reload

In some dedicated servers, it is possible to set the message_size_limit = 0 for sending an unlimited size of email attachments. However, this option can be misused by spammers. Therefore, we enable it only after tightening the security of the server.

 

[Need assistance in fixing Postfix errors? – We’ll help you.]

 

Conclusion

In short, the Postfix queue file size limit exceeded indicates the email message size is larger than configured. To change this value, we edit the value for message_size_limit in main.cf file. Today, we saw how our Support Engineers change this value and fix the error.

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