On Wed, Apr 22, 2009 at 07:53:01AM -0400, Wietse Venema wrote: > Steve Head: > > This all works well for most of the lists we have, however on the > > largish list (without fail in my testing today) I get for the first > > three deliveries (which all happen to be local): 550 Mailbox unknown, > > 250 Successful delivery, followed by a 452 Over quota. and then postfix > > immediately sticks it in the deferred queue and then attempts to deliver > > to the same 3 recipients 10 minutes later, without attempting to deliver > > to any other addresses. I can see other lists where postfix is > > successfully reciving a 452 over quota but still going and delivering to > > the rest of the recipients on the list. > > > [mailq] > > C5012280E0 6390 Wed Apr 22 16:56:29 > > owner-commun...@infoxchange.net.au > > (host 192.168.210.99[192.168.210.99] said: 452 4.2.2 Over quota (in > > reply to RCPT TO command)) > > over-quota-username-repla...@infoxchange.net.au > > community-mj-l...@infoxchange.net.au > > Try delivering ONE recipient per LMTP transaction. > > http://www.postfix.org/postconf.5.html/transport_destination_recipient_limit > > This parameter must be set in main.cf, and you must use "postfix reload".
I've set lmtp_destination_recipient_limit = 1 followed by a postfix reload and postsuper -r C5012280E0 But end up with the same result, immediatly placed in the deffered queue when faced with the temporary delivery failure for that one user. One difference I can see, when doing a postcat of a queue file of a smaller list which also has a deferred recipient. [snip] sender: owner-<listname>@infoxchange.net.au named_attribute: rewrite_context=local original_recipient: <listname>-mj-list done_recipient: $us...@infoxchange.net.au ... original_recipient: <listname>-mj-list recipient: $us...@infoxchange.net.au $user2 being over quota. When doing a postcat of the queue file for this larger list (after having postsuper -r $queuefile): [snip] sender: owner-commun...@infoxchange.net.au original_recipient: community-mj-list recipient: community-mj-l...@infoxchange.net.au No done_recipient: entries (not even the one that was successful) and one would expect there to be many recipient: entries, but there is only the one (which would indicate to me the list hasn't been expanded?). Perhaps my postsuper -r has rewritten the address? Or perhaps there is some sort of corrupt address on the list causing the the entire listfile from being read? One of our reasons for continuing with majordomo is that we have hacked it to populate the list members from a database and it is entirely possible there is a corrupt address on the list. I'll delete this queue file and get the person with the actual content to send again, which will have to wait until tomorrow and see how it goes. Steve. -- The potential for mischief varies inversely with one's proximity to the authority figure: M ~ 1/P_A - Martin Prince
