Re: [Mailman-Users] Messages not being delivered.

Brandon Slaten wrote:
Mark Sapiro wrote:
Brandon Slaten wrote:
~mailman -> /usr/lib/mailman
There is no lock, qfiles, or log directories there to look at to assess items 6-8 in the link above.
In redhat 2.1.5, they may be in /var/mailman
(see below)
I did find the mentioned mailman logs in /var/logs/mailman Here is the most recent entry in the errors log. atd_systems_notes is one of the lists moved over from the old server and one I have been testing with.
Jul 15 08:38:21 2007 (26407) No such list "aa-optical": Jul 15 08:40:42 2007 (26482) No such list "aa-hygro-growth": Jul 15 08:52:45 2007 (26737) No such list "aa-phys-size": Jul 15 09:02:44 2007 (27140) No such list "aa-satellite": Jul 15 09:09:19 2007 (4397) Uncaught runner exception: [Errno 13] Permission denied:'/var/lib/mailman/lists/atd_systems_notes/digest.mbox' Jul 15 09:09:19 2007 (4397) Traceback (most recent call last): File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/lib/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/lib/mailman/Mailman/Handlers/ToDigest.py", line 76, in process mboxfp = open(mboxfile, 'a+') IOError: [Errno 13] Permission denied: '/var/lib/mailman/lists/atd_systems_notes/digest.mbox'
Jul 15 09:09:19 2007 (4397) SHUNTING: 1184512159.0603149+56cd041d3f9dcb1c15807c25c069d965 53d266da Jul 15 09:22:48 2007 (27873) No such list "aa-model": Jul 15 09:31:34 2007 (28149) No such list "esigupcoming":
The permissions on the digest.mbox seems to be the issue, after changing it to be the same as the digest.mbox for the newly created list (660) all seems to be working. I am surprised that the check_perms script did not catch that.
It's a recently discovered bug in check_perms fixed for 2.1.10. See <http://mail.python.org/pipermail/mailman-users/2007-June/057487.html>.
You can now run bin/unshunt to reprocess the shunted messages, but first look at the files in qfiles/shunt to make sure there aren't unwanted stale messages there. You can use bin/dumpdb or bin/show_qfiles (although there is a bug in 2.1.5 show_qfiles that affects some entries, but probably not these) to look at the individual *.pck files in qfiles/shunt and can just remove unwanted ones before running bin/unshunt.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

Mark Sapiro wrote:
Brandon Slaten wrote:
Mark Sapiro wrote:
Brandon Slaten wrote:
~mailman -> /usr/lib/mailman
There is no lock, qfiles, or log directories there to look at to assess items 6-8 in the link above.
In redhat 2.1.5, they may be in /var/mailman
But OTOH, the fact that the lists are in /var/lib/mailman/lists/* and The python Modules are in /usr/lib/mailman/Mailman says that this is RedHat's FHS compliant scheme.
There should be an INSTALL.REDHAT document somewhere in your installation that tells you how to map various old RedHat locations (mostly /var/mailman/*) into the FHS locations.
If you can't find this document, the mapping is in the online version at <http://cvs.fedora.redhat.com/viewcvs/*checkout*/rpms/mailman/F-7/mailman.INS...> and also in a post at <http://mail.python.org/pipermail/mailman-developers/2004-October/017343.html>.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (1)
-
Mark Sapiro