* Mark Sapiro <m...@msapiro.net>: > First of all, if the list is gone, i.e. there is no lists/LISTNAME/ > directory in Mailman's hierarchy, no currently queued messages will be > processed. Outgoing runner or some other runner may pick up queue > entries for this list, but the list won't be there, so the queued > message will be shunted with an error log message 'Dequeuing message > destined for missing list: LISTNAME'. Therefore, you can just restart > Mailman and any messages in Mailman's queues from the affected list > will just wind up in the shunt queue and won't be processed.
I am aware of how to get rid of shunted messages but I'd like to know if there are performance penalites for keeping a moderate amount (<1k) of messages around in the shunted queue for about a month. As far as I understand, the shunted queue is not directly involved in message delivery, so there should be no performance hit, right? This way I could "play it safe", keep those messages around for a certain time (they might turn out important after all) and then have a cron job delete them. Thanks Stefan ------------------------------------------------------ Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
