Topic: [SOLVED --MAYBE--] message_size error driving me crazy
==== Provide required information to help troubleshoot and get quick answer ====
- iRedMail version:
- Linux/BSD distribution name and version:
- Any related log? Log is helpful for troubleshooting.
==== ==== Provide required information to help troubleshoot and get quick answer ====
- iRedMail version: 0.7.4
- Linux/BSD distribution name and version: CentOS 6.2 64bits
- Any related log? Log is helpful for troubleshooting.
====
I have a problem after changing the message_size_limit to 100MB.
I have this error all over my logs:
Apr 25 12:01:26 mail postfix/local[28532]: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit
Apr 25 12:01:27 mail postfix/master[27830]: warning: process /usr/libexec/postfix/local pid 28532 exit status 1
Apr 25 12:01:27 mail postfix/master[27830]: warning: /usr/libexec/postfix/local: bad command startup -- throttling
here is my postconf | 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 = 2621440000
message_size_limit = 104857600
and my 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
It seems that postfix takes the message_size_limit from the main.cf but the mailbox_size_limit from the default value stored "somewhere"...
It is bugging me since months and my logs are crying ![]()
Furthermore it seems that being 'fatal' the pid for postfix is killed and restarted (I wonder if it takes a hit on system performance as it happens even 2 or 3 times per minute)
HELP!!! ![]()
----
Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.