Invisible message for approval
Hello everybody and thanks for this helping tool.
I administer one list and had a "pending for approval" message on Sun Aug 14 21:11:08 2011 , but after several days I discarded it and no mode appeared in the admindb page.
But now I receive every morning an automated message with "The xxx mailing list has 1 request(s) waiting for your consideration", while there is'nt any retained message in the admindb page.
How can I effectively clean the moderation spool? It's Mailman 2.1.13 on Ubuntu 10.04.2
Thanks.
Narcis Garcia - GiLUG wrote:
Please see the FAQ at <http://wiki.list.org/x/EoCE>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
The two messages were sent from the main server and from a new mirror server. I only moderate on the production list server, of course, and the mirror makes data copy with some lag.
The matter I don't know how to solve is to have a mirror (available for production) but not sending mails while doesn't become the production one. (Server can know if it's main or mirror with a DNS query: ListServer IP =? My IP)
Al 10/10/11 08:14, En/na Narcis Garcia - GiLUG ha escrit:
Narcis Garcia - GiLUG wrote:
Presumably, you are not actually running Mailman on the mirror. The nn held messages waiting notices com from a Mailman cron job. You have several choices.
Don't mirror Mailman's crontab.
Don't run crond on the mirror server (probably the best option).
Update the mirror frequently enough so that changes on the production server are reflected on the mirror before Mailman's crons run (this won't avoid duplicate notices when there are held messages on the production server).
modify Mailman's crontab to only run the jobs on the production server.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Production and mirror are ready to work, and the only difference is the public DNS pointer. The design is planned to make only 1 change on a DNS record to change the role of a server.
I'll study the best point to make check if it's production or not, and then run crontab actions or not.
Thanks.
Al 11/10/11 21:18, En/na Mark Sapiro ha escrit:
Narcis Garcia - GiLUG wrote:
Please see the FAQ at <http://wiki.list.org/x/EoCE>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
The two messages were sent from the main server and from a new mirror server. I only moderate on the production list server, of course, and the mirror makes data copy with some lag.
The matter I don't know how to solve is to have a mirror (available for production) but not sending mails while doesn't become the production one. (Server can know if it's main or mirror with a DNS query: ListServer IP =? My IP)
Al 10/10/11 08:14, En/na Narcis Garcia - GiLUG ha escrit:
Narcis Garcia - GiLUG wrote:
Presumably, you are not actually running Mailman on the mirror. The nn held messages waiting notices com from a Mailman cron job. You have several choices.
Don't mirror Mailman's crontab.
Don't run crond on the mirror server (probably the best option).
Update the mirror frequently enough so that changes on the production server are reflected on the mirror before Mailman's crons run (this won't avoid duplicate notices when there are held messages on the production server).
modify Mailman's crontab to only run the jobs on the production server.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Production and mirror are ready to work, and the only difference is the public DNS pointer. The design is planned to make only 1 change on a DNS record to change the role of a server.
I'll study the best point to make check if it's production or not, and then run crontab actions or not.
Thanks.
Al 11/10/11 21:18, En/na Mark Sapiro ha escrit:
participants (2)
-
Mark Sapiro -
Narcis Garcia - GiLUG