Owner and/or moderator not being notified of held message
I have RTFM and have done searches, but have been unable to find the solution. I'll try to be brief and include answers to questions asked of those with similar issues in the past.
I have had mailman 2.1 installed since 2005 and it has been working fine -- until recently. Now, I'm not notified when a post is held for moderation. I may get a notice a day to several days later that I have moderator request(s) waiting.
. Messages not held for moderation are delivered without delay . Issues seem to be related to messages held for moderator approval . Lists have the *admin_immed_notify* set to 'yes'. . The held messages do not appear in the web admindb interface . They also do not show up in the 'vette' log . cron/checkdbs runs every morning at 8 am. . Messages are held in ~mailman/data/heldmesg-listname-###.txt . Email sent to listname-owner@domain.com is successfully delivered.
. Mailman version: 2.1 . python-2.3.2 . Postfix 2.1.4 . Solaris 8 10/01 s28s_u6wos_08a SPARC (yes, I know) . Built from http://www.list.org/download.html back in the day
Any pointers would be most welcome.
Thanks in advance,
Mike
Mike Beaty wrote:
. The held messages do not appear in the web admindb interface . They also do not show up in the 'vette' log . cron/checkdbs runs every morning at 8 am. . Messages are held in ~mailman/data/heldmesg-listname-###.txt
If the ~mailman/data/heldmesg-listname-###.txt is created with the message but the message is not visible in the admindb interface, some exception is being thrown between writing the ~mailman/data/heldmesg-listname-###.txt file and saving the lists request.pck file. I'd guess a permissions issue, but what's in Mailman's error log?
. Mailman version: 2.1
Really? Mailman 2.1 was released in 2002; the current version in 2005 was 2.1.5 or 2.1.6 (released May 2005). 2.1.15 is the latest release, but recent versions require Python 2.4+ http://wiki.list.org/x/pYA9.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Apr 4, 2013, Mark Sapiro wrote:
Mike Beaty wrote:
. The held messages do not appear in the web admindb interface . They also do not show up in the 'vette' log . cron/checkdbs runs every morning at 8 am. . Messages are held in ~mailman/data/heldmesg-listname-###.txt
If the ~mailman/data/heldmesg-listname-###.txt is created with the message but the message is not visible in the admindb interface, some exception is being thrown between writing the ~mailman/data/heldmesg-listname-###.txt file and saving the lists request.pck file. I'd guess a permissions issue, but what's in Mailman's error log?
That's possible, though I don't think that anyone's been twiddling with the file system or the mailman installation. However, I would very much like for it to be a permissions issue, as I know how to fix permissions :-).
I've put the last ~500 lines of ~mailman/logs/error into http://www.mikebeaty.com/mailman_log.txt
Interestingly (to me), I see this error ImportError: No module named Mailmann.UserDesc which began on or about the day I first noticed the issues. Searches on the term Mailmann.UserDesc yielded no results, so my installation must be uniquely horked.
. Mailman version: 2.1
Really? Mailman 2.1 was released in 2002; the current version in 2005 was 2.1.5 or 2.1.6 (released May 2005). 2.1.15 is the latest release, but recent versions require Python 2.4+ http://wiki.list.org/x/pYA9.
37 /export/mailman/bin> version
Using Mailman version: 2.1
And I was mistaken in my original post. According to the logs, the correct date was Feb 04 11:29:54 2004 . I apologize for the confusion. This installation has been working fine for over nine years. Unfortunately, I'm not the only sysadmin on this box, so something may have been upgraded and/or changed without my knowledge.
I greatly appreciate your reply!
Mike
Mike Beaty wrote:
I've put the last ~500 lines of ~mailman/logs/error into http://www.mikebeaty.com/mailman_log.txt
Interestingly (to me), I see this error ImportError: No module named Mailmann.UserDesc which began on or about the day I first noticed the issues. Searches on the term Mailmann.UserDesc yielded no results, so my installation must be uniquely horked.
There should be a Mailman/UserDesc.py module. It's been there since the start of the 2.1 branch.
Yes your installation must be uniquely horked.
Do you know how your installation was installed and can you reinstall it the same way?
You can get individual source files from http://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1 and a tarball from http://ftp.gnu.org/gnu/mailman/mailman-2.1.tgz.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mike Beaty wrote:
Interestingly (to me), I see this error ImportError: No module named Mailmann.UserDesc which began on or about the day I first noticed the issues.
Ooops. just noticed the double 'nn'. That's a different issue. It's something corrupt in the pending.pck file. In your version, it's data/pending.pck in Mailman's var_prefix. You can simply move it aside or delete it and also, any pending.db.
You will lose old pending requests, but they've all expired by now anyway.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Apr 4, 2013, Mark Sapiro wrote:
Ooops. just noticed the double 'nn'. That's a different issue. It's something corrupt in the pending.pck file. In your version, it's data/pending.pck in Mailman's var_prefix. You can simply move it aside or delete it and also, any pending.db.
I was hoping it was something simple like this. I deleted the pending.pck file, then ran http://www.msapiro.net/scripts/hold_again as hold_again -a from the ~mailman/bin directory. KaCHOW! Back in business.
Thanks, Mark!
Mike
participants (2)
-
Mark Sapiro
-
Mike Beaty