Fix: Postfix File too big error

Valic —  March 13, 2013 — 1 Comment

I was looking in my server logs and I’ve found an error from my Postfix Mail Server. That appeared when I wanted to send a 10MB backup trough mail. The error was found in /var/log/mail.err file and looks like this:

postfix/postdrop[197353]: warning: uid=0: File too large
postfix/sendmail[197352]: fatal: root(0): message file too big

To check the default attachments size settings of Postfix use the following command:

# postconf -d | grep size
berkeley_db_create_buffer_size = 16777216
berkeley_db_read_buffer_size = 131072
body_checks_size_limit = 51200
bounce_size_limit = 50000
header_size_limit = 102400
mailbox_size_limit = 51200000
message_size_limit = 10240000
tcp_windowsize = 0

As you can see the Postfix default value for a mailbox size is 51200000 bytes and max message size is 10240000 bytes.
To fix this issue the maximum outgoing message size needs to be increased as well as the mailbox size.
By entering the following commands we will set unlimited for both, mailbox size and max message size:

postconf -e mailbox_size_limit=0 Continue Reading...

If you want to set-up an mail server in Debian Linux using Postfix and SquirrelMail you need to follow the next guide:

Step1.  Install Postfix:

apt-get install postfix

This command will remove sendmail. Sendmail is installed by default on Debian.

Step2. Configure Postfix:

Open the file /etc/postfix/ with your favorite editor and uncomment or add the followins:

inet_interfaces = all
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
home_mailbox = Maildir/

Step3. Restart and test if Postfix is working:

/etc/init.d/postfix restart

Continue Reading…

To delete the Postfix mail queue use the following command:

[email protected]:~# postsuper -d ALL
postsuper: Deleted: 5 messages
[email protected]:~#

You can also use man postsuper command for more options.

Postfix stable release 2.8.0

Valic —  January 21, 2011 — Leave a comment

Postfix stable release 2.8.0 is available. This release continues the move towards improving code and documentation, and making the system better prepared for changes in the threat environment.

  • The postscreen daemon (a zombie blocker in front of Postfix) is now included with the stable release. postscreen now supports TLS and can log the rejected sender, recipient and helo information.

    See the POSTSCREEN_READM file for recommended usage scenarios.

  • Support for DNS whitelisting (permit_rhswl_client), and for pattern matching to filter the responses from DNS white/blacklist
    servers (e.g.,  reject_rhsbl_client[1..10]).
  • Improved message tracking across SMTP-based content filters; the after-filter SMTP server can log the before-filter queue ID (the XCLIENT protocol was extended).
  • Read-only support for sqlite databases. See sqlite_table(5) and SQLITE_README.
  • Support for ‘footers’ that are appended to SMTP server “reject” responses. See “smtpd_reject_footer” in the postconf(5) manpage.

No functionality has been removed, but it is a good idea to review the RELEASE_NOTES file for the usual minor incompatibilities or limitations.

You can find Postfix version 2.8.0 at the mirrors listed at

The same code is also available as Postfix snapshot 2.9-20110120.
Updated versions of Postfix version 2.7, 2.6, 2.5 and 2.4 will be released as time permits. Support for Postfix 2.4 will end soon.

Page 1 of 11