I'm new to Mailman, so please bear with me.
There's an existing list that was set up a few weeks ago. All was well, until I noticed something rather odd.
When a user was unsubscribed (through the web interface), they continued to receive emails. And when additional users were subscribed, they still haven't received any of the list traffic.
This is on FreeBSD / Postfix. Anyone know what I might have forgotten to do? Everything else works correctly.
-- Jay Chandler Network Administrator Chapman University
Jay Chandler wrote:
Mailman maintains a current version of its config file and a backup that is one generation older. It sounds to me like the current config is corrupt and it is falling back on the backup.
This should show up in the logs, probably the error log or maybe qrunner.
Something you can try is to run bin/dumpdb on the config.pck and config.pck.last files for that list to see if it throws an exception or reports a problem.
Dragon
Venimus, Saltavimus, Bibimus (et naribus canium capti sumus)
Dragon wrote:
This is unlikely to be the case. First of all, config.pck.last is at most one transaction behind config.pck. Then, if config.pck can't be loaded, the list will be loaded (if possible) from config.pck.last, but saved back to config.pck so after one fallback event, config.pck will have the latest list state.
The only time you get a significant rollback in this situation is if you magrated from an old config.db and left the old config.db in the lists/listname/ directory after the config.pck was created. Then, if both the config.pck and config.pck.last became unusable at the same time, you'd fall back to the config.db which would really be out of date.
This should show up in the logs, probably the error log or maybe qrunner.
It's logged in Mailman's 'error' log.
At this point, after one or more posts or other events, even if the config.pck had been corrupt, it would have been overwritten with a good file.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Fri, 09 Mar 2007 14:52:54 -0800 "Jay Chandler" <chandler.lists@chapman.edu> wrote:
This is on FreeBSD / Postfix. Anyone know what I might have forgotten to do? Everything else works correctly.
Any chance you have two installations of mailman and the mail aliases are pointing to the old one?
Sent with SnapperMail www.snappermail.com
Jay Chandler wrote:
Do your subs and unsubs require approval? Any admindb requests waiting.
If sub requires confirmation, did the new subs receive the confirmation email and respond?
Is the unsub still in Membership management...-Membership list? Are the new subs there?
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Jay Chandler quoted me and replied:
So if I understand correctly, you have new subscribers on the admin Membership list pages with delivery enabled and not digest, and they aren't receiving list mail but other members are. Is this correct?
Are they bouncing? (look in mailman's bounce log and/or follow the link to their options page).
Also, you have a former list member who does not appear on the admin Membership list pages who is still receiving mail from the list. Is this correct?
Is it possible this person is getting mail forwarded from another address which is on the list?
Examine the complete headers of the mail received by this person to try to determine how it got to her/him.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Jay Chandler wrote:
Mailman maintains a current version of its config file and a backup that is one generation older. It sounds to me like the current config is corrupt and it is falling back on the backup.
This should show up in the logs, probably the error log or maybe qrunner.
Something you can try is to run bin/dumpdb on the config.pck and config.pck.last files for that list to see if it throws an exception or reports a problem.
Dragon
Venimus, Saltavimus, Bibimus (et naribus canium capti sumus)
Dragon wrote:
This is unlikely to be the case. First of all, config.pck.last is at most one transaction behind config.pck. Then, if config.pck can't be loaded, the list will be loaded (if possible) from config.pck.last, but saved back to config.pck so after one fallback event, config.pck will have the latest list state.
The only time you get a significant rollback in this situation is if you magrated from an old config.db and left the old config.db in the lists/listname/ directory after the config.pck was created. Then, if both the config.pck and config.pck.last became unusable at the same time, you'd fall back to the config.db which would really be out of date.
This should show up in the logs, probably the error log or maybe qrunner.
It's logged in Mailman's 'error' log.
At this point, after one or more posts or other events, even if the config.pck had been corrupt, it would have been overwritten with a good file.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Fri, 09 Mar 2007 14:52:54 -0800 "Jay Chandler" <chandler.lists@chapman.edu> wrote:
This is on FreeBSD / Postfix. Anyone know what I might have forgotten to do? Everything else works correctly.
Any chance you have two installations of mailman and the mail aliases are pointing to the old one?
Sent with SnapperMail www.snappermail.com
Jay Chandler wrote:
Do your subs and unsubs require approval? Any admindb requests waiting.
If sub requires confirmation, did the new subs receive the confirmation email and respond?
Is the unsub still in Membership management...-Membership list? Are the new subs there?
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Jay Chandler quoted me and replied:
So if I understand correctly, you have new subscribers on the admin Membership list pages with delivery enabled and not digest, and they aren't receiving list mail but other members are. Is this correct?
Are they bouncing? (look in mailman's bounce log and/or follow the link to their options page).
Also, you have a former list member who does not appear on the admin Membership list pages who is still receiving mail from the list. Is this correct?
Is it possible this person is getting mail forwarded from another address which is on the list?
Examine the complete headers of the mail received by this person to try to determine how it got to her/him.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (5)
-
chandler.lists＠chapman.edu -
Dragon -
Jay Chandler
-
Mark Sapiro -
Paul Tomblin