• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1091
  • Last Modified:

Postfix Bounce Error

Hi there,
   I am running Postfix (2.1.5) and am getting the following Bounce message for a single user -

The NDR is - " [servername] #5.0.0 X-Postfix; cannot access mailbox /var/mail/[username] for    user [username]. error writing message: File too large"

The maillog entry is mx1 postfix/local[9317]: 2F82D3747AA: to=<[alias]@domain.org.au>, relay=local, delay=1, status=bounced (cannot access mailbox /var/mail/[username] for user [username]. error writing message: File too large)

I have changed  "virtual_mailbox_limit = 0" and reloaded the config.. Still getting the same bounce msg..
The users mbox size is - 79227539

Here is the "postconf -n"
alias_maps = hash:/etc/aliases
allow_untrusted_routing = yes
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory = /usr/libexec/postfix
debug_peer_level = 2
disable_vrfy_command = yes
html_directory = no
mailq_path = /usr/bin/mailq.postfix
manpage_directory = /usr/share/man
mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
mynetworks =
myorigin = [domain].org.au
newaliases_path = /usr/bin/newaliases.postfix
sendmail_path = /usr/sbin/sendmail.postfix
setgid_group = postdrop
smtpd_banner = myhostname ESMTP $mail_name ($mail_version)
smtpd_recipient_restrictions = permit_mynetworks, check_client_access hash:/etc/postfix/pop-before-smtp, reject_unauth_destination
unknown_local_recipient_reject_code = 550
virtual_mailbox_limit = 0

I know that it is specifically related to the mailbox size as I have since POPd the Mailbox (instead of IMAP) and since sucking all the mail off the server I can now succesfully deliver mail to the POP client.. Though this is a temp fix as I need the mail stores to reside on the server - not on client machines..

Assistance would be greatly appreciated..
I have given this 500 Points as the mailbox in question is (naturally) the CEO's and he is getting a little agitated..

  • 5
  • 3
1 Solution
80Mb mailbox is a good reason to change your mailstore format from mailbox to maildir.

What POP3 server are you using?

I recommend you to change your POP server to Courier IMAP or Cyrus IMAP. They support maildir format, but of course, require Postfix adoptation.
This link may also help http://www.pocock.com.au/linux-doc/mbox-maildir.html

google is your friend,

ComputergateAuthor Commented:
The shock is that I have another user that has 400MB and can accept mail delivery fine to the mailbox..

I am using Dovecot for POP/IMAP..

I guess there is no reason that I could not change to Courier or Cyrus - but I would still like to know what is causing this issue and where the inconsistency has come from..

mailbox_size_limit = 0;
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

and this (which is more probably the reason):

Anyway with such large mailboxes is time to move to maildir :)
ComputergateAuthor Commented:
It looks as though the "mailbox_size_limit = 0" has done the trick - but I am just testing so I'll issue the points as soon as I have confirmed that it is right (tomorrow at the latest).. Thank you *greatly* for your assistance.

Any tips on converting from mailbox to maildir/?
The postfix portion of it is simple - I have just done it in a dev environment and it is easy peasy - but what about the mbox data conversion?

Again - thanks heaps for your thoughts and suggestions - I'll deliver you the points by tomorrow at the latest..

Mailbox format is very simple. You can break mailbox file to individual messages by single regex.

man mail.local

It's a text from my "man mail.local":

"Individual mail messages in the mailbox are delimited by an empty  line followed  by  a  line beginning with the string ``From ''.  A line containing the string ``From '', the sender's name and  a  time  stamp  is  prepended  to each delivered mail message.  A blank line is appended to each message.  A greater-than character (``>'')  is  prepended  to  any line  in  the message which could be mistaken for a ``From '' delimiter line (that is, a line beginning with the five characters ``From '' following a blank line)."

After processing each mailbox file you will get a number of .eml messages. Now you may deliver them back to that user in their original order. Delivery method depends on your local mail delivery mechanism. For Cyrus it's a 'deliver' program, that accepts user name as parameter and message body as stdin, then it puts it to maildir. For Courier it's a 'maildrop' utility. For Dovecot I don't know, sorry.

Of course you should convert your mailbox aside, on some test server, then test how it works, then go to production system.
ComputergateAuthor Commented:
Mate, you're a champ..
Thank you so much for your input and guidance..

The "mailbox_size_limit = 0" has definately resolved the issue so the points are yours..

I shall test the mbox conversion over the weekend and quite probably migrate from Dovecot to one of the above recommendations..



Thank you, Computergate.

Good luck with your experiments :)

Featured Post

Prep for the ITIL® Foundation Certification Exam

December’s Course of the Month is now available! Enroll to learn ITIL® Foundation best practices for delivering IT services effectively and efficiently.

  • 5
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now