FAQ
Greetings,

Thanks for any time you can give this problem.

I just moved our Mailman lists to a new server. Accessing the listinfo
and admin pages works fine. After creating a new list mail sent to that
list is delivered. However mail set to the old lists, the ones that
were moved to this server, is not delivered.

I do however get moderation and bounce notices from those lists. I ran
check_perms to see if there were any problems with permissions and got
the following:

file permissions must be at least 660:
/var/lib/mailman/lists/ofap_mgrs/config.db (fixing)
file permissions must be at least 660:
/var/lib/mailman/lists/ofap_mgrs/config.db.last (fixing)
file permissions must be at least 660:
/var/lib/mailman/lists/python/config.db (fixing)
file permissions must be at least 660:
/var/lib/mailman/lists/python/config.db.last (fixing)
file permissions must be at least 660:
/var/lib/mailman/lists/python/next-digest (fixing)
file permissions must be at least 660:
/var/lib/mailman/lists/python/next-digest-topics (fixing)

A second run showed no errors yet still not message being delivered when
sent to the older lists.

I also have this from the logs.

Jul 14 14:25:36 chandon postfix/qmgr[3905]: C13DF3793B:
from=<username at host.ucar.edu>, sizeb9, nrcpt=1 (queue active)
Jul 14 14:25:36 chandon postfix/smtpd[9619]: disconnect from
host2.atd.ucar.edu[128.117.80.16]
Jul 14 14:25:36 chandon postfix/local[9833]: C13DF3793B:
to=<listname at host.ucar.edu>, relay=local, delay=0, status=sent
(delivered to command: /usr/lib/mailman/mail/mailman post listname)
Jul 14 14:25:36 chandon postfix/qmgr[3905]: C13DF3793B: removed

Search Discussions

  • Mark Sapiro at Jul 15, 2007 at 2:41 pm

    Brandon Slaten wrote:
    I just moved our Mailman lists to a new server. Accessing the listinfo
    and admin pages works fine. After creating a new list mail sent to that
    list is delivered. However mail set to the old lists, the ones that
    were moved to this server, is not delivered.

    What happens to mail to the old lists (after delivery to Mailman - see
    below)?


    See
    <http://www.python.org/cgi-bin/faqw-mm.py?req=show&fileúq04.078.htp>.

    I do however get moderation and bounce notices from those lists. I ran
    check_perms to see if there were any problems with permissions and got
    the following:

    file permissions must be at least 660:
    /var/lib/mailman/lists/ofap_mgrs/config.db (fixing)
    file permissions must be at least 660:
    /var/lib/mailman/lists/ofap_mgrs/config.db.last (fixing)
    file permissions must be at least 660:
    /var/lib/mailman/lists/python/config.db (fixing)
    file permissions must be at least 660:
    /var/lib/mailman/lists/python/config.db.last (fixing)
    file permissions must be at least 660:
    /var/lib/mailman/lists/python/next-digest (fixing)
    file permissions must be at least 660:
    /var/lib/mailman/lists/python/next-digest-topics (fixing)

    The log entry below "(delivered to command:
    /usr/lib/mailman/mail/mailman post listname)" says you are running
    Mailman 2.1.x. These residual 2.0.x files were converted to config.pck
    and digest.mbox files when the installation was upgraded to 2.1. They
    should now be deleted (assuming they are old and there are current
    config.pck* files.

    I also have this from the logs.

    Jul 14 14:25:36 chandon postfix/qmgr[3905]: C13DF3793B:
    from=<username at host.ucar.edu>, sizeb9, nrcpt=1 (queue active)
    Jul 14 14:25:36 chandon postfix/smtpd[9619]: disconnect from
    host2.atd.ucar.edu[128.117.80.16]
    Jul 14 14:25:36 chandon postfix/local[9833]: C13DF3793B:
    to=<listname at host.ucar.edu>, relay=local, delay=0, status=sent
    (delivered to command: /usr/lib/mailman/mail/mailman post listname)
    Jul 14 14:25:36 chandon postfix/qmgr[3905]: C13DF3793B: removed

    Assuming 'listname' above is one of the affected lists, the message is
    being delivered to Mailman so the Postfix Aliases are OK. Refer to the
    FAQ above (items 6-8 in particular) for other things which might be
    wrong.

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Brandon Slaten at Jul 15, 2007 at 3:01 pm
    Some additional information:

    The old server:

    Using Mailman version: 2.1.6
    Compiled from src.
    SunOS 5.8 Generic_117350-14 sun4u sparc SUNW,Ultra-4

    The new server:

    Using Mailman version: 2.1.5
    Installed from mailman-2.1.5.1-34.rhel4.5
    Linux 2.6.9-55.0.2.ELsmp #1 SMP Tue Jun 12 17:59:08 EDT 2007 i686 i686
    i386 GNU/Linux

    Since it looks like the mail server is handing off to the mailman
    script, I have been looking for some sort of log or error messages in
    the various system logs, with out luck so far.


    Brandon Slaten wrote:
    Greetings,

    Thanks for any time you can give this problem.

    I just moved our Mailman lists to a new server. Accessing the listinfo
    and admin pages works fine. After creating a new list mail sent to that
    list is delivered. However mail set to the old lists, the ones that
    were moved to this server, is not delivered.

    I do however get moderation and bounce notices from those lists. I ran
    check_perms to see if there were any problems with permissions and got
    the following:

    file permissions must be at least 660:
    /var/lib/mailman/lists/ofap_mgrs/config.db (fixing)
    file permissions must be at least 660:
    /var/lib/mailman/lists/ofap_mgrs/config.db.last (fixing)
    file permissions must be at least 660:
    /var/lib/mailman/lists/python/config.db (fixing)
    file permissions must be at least 660:
    /var/lib/mailman/lists/python/config.db.last (fixing)
    file permissions must be at least 660:
    /var/lib/mailman/lists/python/next-digest (fixing)
    file permissions must be at least 660:
    /var/lib/mailman/lists/python/next-digest-topics (fixing)

    A second run showed no errors yet still not message being delivered when
    sent to the older lists.

    I also have this from the logs.

    Jul 14 14:25:36 chandon postfix/qmgr[3905]: C13DF3793B:
    from=<username at host.ucar.edu>, sizeb9, nrcpt=1 (queue active)
    Jul 14 14:25:36 chandon postfix/smtpd[9619]: disconnect from
    host2.atd.ucar.edu[128.117.80.16]
    Jul 14 14:25:36 chandon postfix/local[9833]: C13DF3793B:
    to=<listname at host.ucar.edu>, relay=local, delay=0, status=sent
    (delivered to command: /usr/lib/mailman/mail/mailman post listname)
    Jul 14 14:25:36 chandon postfix/qmgr[3905]: C13DF3793B: removed


    ------------------------------------------------------
    Mailman-Users mailing list
    Mailman-Users at python.org
    http://mail.python.org/mailman/listinfo/mailman-users
    Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
    Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
    Unsubscribe: http://mail.python.org/mailman/options/mailman-users/brandon%40ucar.edu

    Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&amp;fileúq01.027.htp
  • Brad Knowles at Jul 16, 2007 at 5:56 am

    On 7/15/07, Brandon Slaten wrote:

    Some additional information:

    The old server:

    Using Mailman version: 2.1.6
    [ ... deletia ... ]
    The new server:

    Using Mailman version: 2.1.5
    With regards to software in general, moving backward in the version
    number scheme is problematic. Can you upgrade the new machine to a
    more recent version, like 2.1.9?

    --
    Brad Knowles <brad at shub-internet.org>, Consultant & Author
    LinkedIn Profile: <http://tinyurl.com/y8kpxu>
    Slides from Invited Talks: <http://tinyurl.com/tj6q4>

    09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0
  • Mark Sapiro at Jul 15, 2007 at 4:59 pm

    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 at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Mark Sapiro at Jul 16, 2007 at 3:41 am

    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.INSTALL.REDHAT.in>
    and also in a post at
    <http://mail.python.org/pipermail/mailman-developers/2004-October/017343.html>.

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedJul 14, '07 at 9:01p
activeJul 16, '07 at 5:56a
posts6
users3
websitelist.org

People

Translate

site design / logo © 2022 Grokbase