In some cases this problem is caused by the way that the MTA handles local deliveries (where there is a problem with the local user).
In postfix for example, the default install has local bounces mis-identified so that Mailman will try, try again to deliver to a bogus local user address. Nothing shows up in the logs, since the MTA indicates that the user is legal, just not currently available. I suggest that you-all look in the MTA log files to see if there are multiple failed deliveries to a local user. Barry has a work-around for this problem that will be included in the next release. Jon Carnes On Wed, 2003-05-28 at 13:20, Ryan K. Brooks wrote: > Odd. I have the same problem! (postfix here, and it's fine) > > -R > > Arnar Birgisson wrote: > > >Something of the sort yes.. if I stop mailman, there is one message in > >the out queue. However, using dumpdb reveals that this is just a normal > > > > > > ------------------------------------------------------ > 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
