The files are .pck Looking at them they appear to be posts waiting to be sent since mailman has stopped sending. I just need to make sure none get sent when I restart mailman as has happened in the past.
The version is 2.1.9 Still do as suggested? Thanks, Dan On 9/14/2010 3:37 PM, Mark Sapiro wrote:
Dan Young wrote:Not concerned about the lock since it only happened once in a year. But some of the posts are time sensitive and in the /var/spool/in directory I see some that are a week old and I do not want them to send if I restart mailman.If they are .bak files and Mailman is restarted, they will be reprocessed?If I just delete these and restart mailman can I be comfortably assured that and posts received after the issue will not be sent? Another option may be to empty the membership and restart then re-pop the membership. I just don't want anything old to send.What is the current issue? I suggest stopping Mailman entirely. Then you can use bin/dumpdb or bin/show_qfiles to examint the various /var/spool/in and other /var/spool/* Mailman queue entries and any you don't want can be removed or moved elsewhere. Then start Mailman and the stuf you removed or moved aside will not be further processed.
------------------------------------------------------ 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
