Mark Sapiro wrote: >Xueshan Feng wrote: > >>The real operational question here is each time if we have to stop / start >>mailman to move files, than for large volume queues, it would take a lot >>of manual process. The procedure I have used is: >> >>- stop mailman >>- move queue files or .bak file aside > > Move the whole directory, not the contents. > > >>- start mailman >>- move some files back, or .bak back into the queue >>(note files are moved back while mailman is running)
It's implied by the rest of my reply, but moving a .bak file into the queue while the runner for that slice is running does nothing until that runner is stopped or crashes and is restarted. If you want to actually process a .bak file you've moved aside, rename it .pck before moving it back. Note that you can examine the messages in queue entries with Mailman's bin/show_qfiles and see the messages and metadata with Mailman's bin/dumpdb. This may help in deciding whether to reprocess a particular entry. But, in your case, where the backlog in processing was due to an MTA outage, all the entries should be good. -- Mark Sapiro <[email protected]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list [email protected] 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
