[Mailman-Users] There are no pending requests
rex
rex.linuxuser at gmail.com
Wed Mar 26 08:28:26 CET 2014
The Mailman web page to approve messages held for approval always has
the message: "There are no pending requents," even when there
are messages in /var/lib/mailman/data/heldmsg-mynewlist-1.pck
Running Mailman 2.1.15 under Debian Wheezy with a new list that has
never existed on any local machine.
1) Mail that does not require approval is posted to the list normally.
2) All web pages with the exception of the one below function normally.
3) Mail from moderated subscribers produces the usual notice to the
list admin, but when the page:
http://myserver.net/cgi-bin/mailman/admindb/mynewlist
is visited, this message appears:
"There are no pending requests. Click here to reload this page."
Reloading the page makes no difference.
I tried the hold_again script from here:
http://fog.ccsf.edu/~msapiro/scripts/
When the hold_again script is run, this is the result:
root@ /usr/lib/mailman/bin# ./hold_again -n -v -l mynewlist
Requeueing message from file heldmsg-mynewlist-1.pck
The held message is in the data directory:
root@:/var/lib/mailman/data# ls -l
-rw-r----- 1 root list 41 May 3 2013 adm.pw
-rw-rw---- 1 root list 1997 Nov 6 2012 aliases
-rw-rw---- 1 list list 12288 Nov 6 2012 aliases.db
[...]
-rw-rw-r-- 1 list list 775 Mar 25 16:11 heldmsg-mynewlist-1.pck
[...]
-rw-rw-r-- 1 root list 10 Jul 13 2012 last_mailman_version
-rw-r--r-- 1 root list 14100 Jun 16 2012 sitelist.cfg
-rw-rw---- 1 root list 1831 Nov 6 2012 virtual-mailman
-rw-rw---- 1 list list 12288 Nov 6 2012 virtual-mailman.db
The hold_again command results in a new notice to the list admin re
the held message, but revisiting the web page shows the same "There
are no pending requests" message.
Responding via email to the list admin message with an
"Approved: listadminpswd" header" results in a copy of the sent message
being sent to the list admin, but no action re the held message; it's
still held, with the same timestamp.
The server is running apache 2.4.6-3.
The mailman.conf file in /etc/apache2/sites-available has:
# Sample configuration for Debian mailman with Apache
# We can find mailman here:
ScriptAlias /cgi-bin/mailman/ /usr/lib/cgi-bin/mailman/
# And the public archives:
Alias /pipermail/ /var/lib/mailman/archives/public/
# Logos:
Alias /images/mailman/ /usr/share/images/mailman/
# Use this if you don't want the "cgi-bin" component in your URL:
# In case you want to access mailman through a shorter URL you should enable
# this:
#ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/
# In this case you need to set the DEFAULT_URL_PATTERN in
# /etc/mailman/mm_cfg.py to http://%s/mailman/ for the cookie
# authentication code to work. Note that you need to change the base
# URL for all the already-created lists as well.
<Directory /usr/lib/cgi-bin/mailman/>
AllowOverride None
Options ExecCGI
AddHandler cgi-script .cgi
Require all granted
</Directory>
<Directory /var/lib/mailman/archives/public/>
Options FollowSymlinks
AllowOverride None
Require all granted
</Directory>
<Directory /usr/share/images/mailman/>
AllowOverride None
Require all granted
</Directory>
I've spent hours trying to resolve this problem. Any help would be
much appreciated.
TIA,
-rex
--
More information about the Mailman-Users
mailing list