Nick Bright: > > The patch should not allow message size limit> mailbox size limit. > > Unpatched Postfix forbids this, but they removed that check. > > > > In this case, mailbox_size_limit shouldn't come in to play. If I'm > reading http://www.postfix.org/postconf.5.html#mailbox_size_limit > correctly, that parameter only effects local delivery; not virtual.
I should have written: virtual_mailbox_limit. I suggest that you look for Postfix panic, fatal, error or warning messages as per these instructions: http://www.postfix.org/DEBUG_README.html#logging LOOK FOR OBVIOUS SIGNS OF TROUBLE ================================= Postfix logs all failed and successful deliveries to a logfile. The file is usually called /var/log/maillog or /var/log/mail; the exact pathname is defined in the /etc/syslog.conf file. When Postfix does not receive or deliver mail, the first order of business is to look for errors that prevent Postfix from working properly: % egrep '(warning|error|fatal|panic):' /some/log/file | more Note: the most important message is near the BEGINNING of the output. Error messages that come later are less useful. The nature of each problem is indicated as follows: * "panic" indicates a problem in the software itself that only a programmer can fix. Postfix cannot proceed until this is fixed. * "fatal" is the result of missing files, incorrect permissions, incorrect configuration file settings that you can fix. Postfix cannot proceed until this is fixed. * "error" reports an error condition. For safety reasons, a Postfix process will terminate when more than 13 of these happen. * "warning" indicates a non-fatal error. These are problems that you may not be able to fix (such as a broken DNS server elsewhere on the network) but may also indicate local configuration errors that could become a problem later. When no mail is delivered, the logfile will tell you why. Wietse
