A year or so ago I had something in mailman lock. It showed as running but stop sending e-mails. I restarted mailman and it instantly started sending the posts that were not sent as of the issue. 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 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.
Thanks, Dan
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.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
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. Butsome 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 comfortablyassured 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.
Dan Young wrote:
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?
Yes. Stop Mailman; remove or move aside the /var/spool/*/*.pck files you don't want sent, and start Mailman.
Note, if the problem is a stale list lock (see <http://wiki.list.org/x/noA9>) probably, just removing the stale lock without stoping and starting Mailman will solve it, but you would still want to remove or move aside the /var/spool/*/*.pck files before removing the lock.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Hi, I'm new in mailman and I have the same problem, one list have a lot mails with errors(xxxx at htamil.com), and mailman everytime is processing that, so when I send new mail a list, this is very slow, but I dont know how to erase an e-mail in waiting, I tried with mailq(I use postfix) and tried in /var/spool/ ** and I hadn't good luck, could you tell me where located the e-mail tail is?
My incoming posts that have not yet been sent were in: /var/spool/mailman/in They were individual .pck files
May want to delete anything old in your mail queue as well. If users are attaching files to their posts they can slow things down.
I also had to throttle outgoing bandwidth so the server did not take up all our bandwidth and effect our other servers accessibility. It now of course takes a little longer to send out the posts.
Dan
On 9/22/2010 11:32 AM, ap wrote:
Hi, I'm new in mailman and I have the same problem, one list have a lot mails with errors(xxxx at htamil.com <http://htamil.com>), and mailman everytime is processing that, so when I send new mail a list, this is very slow, but I dont know how to erase an e-mail in waiting, I tried with mailq(I use postfix) and tried in /var/spool/ ** and I hadn't good luck, could you tell me where located the e-mail tail is?
ap wrote:
Hi, I'm new in mailman and I have the same problem, one list have a lot mails with errors(xxxx at htamil.com), and mailman everytime is processing that, so when I send new mail a list, this is very slow, but I dont know how to erase an e-mail in waiting, I tried with mailq(I use postfix) and tried in /var/spool/ ** and I hadn't good luck, could you tell me where located the e-mail tail is?
Outgoing mail from Mailman that hasn't yet been delivered to the MTA is in Mailman's out/ queue. Mail which has had some failures and is waiting to be retried is in Mailman's retry/ queue.
In a default Mailman install, these are in /usr/local/mailman/qfiles/
In recent RedHat packages, the out/ and retry/ queues are in /var/spool/mailman. In other packages, they are in var-prefix.
Note that there is probably one out/ queue file named *.bak (all the others are *.pck). The *.bak file is a backup of the message currently in process by OutgoingRunner. It is only used in case of a crash and changing it will normally have no effect unless you first stop Mailman.
There is a script at <http://www.msapiro.net/scripts/remove_recips> that can remove recipients from a queue file.
Also note that if bad domains are slowing mail delivery from Mailman, your MTA is doing domain verification on recipient addresses. Search the FAQ at <http://wiki.list.org/display/DOC/Frequently+Asked+Questions> for "performance" for info on why this is not a good idea.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
ap -
Dan Young -
Mark Sapiro