Make sure you local MTA correctly identifies the local user as bogus. Postfix by default does not correctly identify a user as being missing and instead sends a lesser error indicating that the user is just temporarily unavailable.
Modify your MTA to report the bogus user correctly, then Mailman will not loop on that error. A check is being added to the next version so this will not be a problem in the future (though it is not Mailman's error). Jon Carnes On Tue, 2003-05-27 at 17:22, Gerald Combs wrote: > I recently upgraded from Mailman 2.0.8 to 2.1.2. Since then I've run into > a wierd problem where qrunner appears to be looping on a message in the > "out" queue. The message itself is a subscription confirmation from a > nonexistent local user; apparently someone tried to subscribe and forgot > to add the domain to their email address. > > The only fix I've found so far is to manually stop qrunner, remove the > offending .db and .pck file, and restart qrunner. > > > ------------------------------------------------------ > Mailman-Users mailing list > [EMAIL PROTECTED] > http://mail.python.org/mailman/listinfo/mailman-users > Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py > Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ > > This message was sent to: [EMAIL PROTECTED] > Unsubscribe or change your options at > http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com ------------------------------------------------------ Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
