> It's a feature not a bug. You're using dbmail-smtp, and as I understand > Jesse's > remarks last week about lmtp versus pipe delivery: temp-failures in case of > delivery errors such as over-quota are only effective when using lmtp.
dbmail-smtp (which still needs renamed, paul :) can/does of course detect the condition, it just can't report it to the mta while the smtp client is still online. (On a related note, I started working on a postfix policy daemon that does exactly that.) If it's going to report an over quota message it has to send a completely new message to the sender, not just return an error code (which postfix would give to the smtp client). > > THIS COULD BE THE PROBLEM!!! > > Apr 11 09:52:51 portero dbmail/smtp[3805]: sort.c, sort_and_deliver: error > > copying message to user [49],maxmail exceeded > > > > Apr 11 09:52:51 portero dbmail/smtp[3805]: pipe.c, insert_messages: > > temporary failure sort_and_deliver for useridnr [49] > > So, dbmail actually detects a temp-failure. As expected. Good. This sounds somewhat/exactly like another bug from not terribly long ago (I think 2.0+ timeframe) - over quota messages were being bounced as a temporary failure. I recall that was determined to be the wrong behavior, ie. it should be reported as a permanent to the mta -- is that's what's happening (again)? I'd need to review this thread again to see what the exact symptoms were (or perhaps they've changed since it started...). -- Jesse Norell jesse @ kci.net
