FAQ
All,
I am using Mailman 2.1.5 with Postfix on CentOS 3.5 (RHEL 3). My problem
is that I have no archives. They are not being created.

Each list is set to archive, and to make the archives public. I do have
Apache set to follow symlinks. I also do not have any mbox directories or
files being kept. I don't know why. I figure that I have no archives
because I have no mboxes. I have checked the permissions (check_perms).

Any thoughts on how to remedy or what to check next ?

Thanks,
Mike

Search Discussions

  • Mark Sapiro at Aug 1, 2005 at 12:11 am

    Michael J McCafferty wrote:

    I am using Mailman 2.1.5 with Postfix on CentOS 3.5 (RHEL 3). My problem
    is that I have no archives. They are not being created.

    Each list is set to archive, and to make the archives public. I do have
    Apache set to follow symlinks. I also do not have any mbox directories or
    files being kept. I don't know why. I figure that I have no archives
    because I have no mboxes. I have checked the permissions (check_perms).

    Any thoughts on how to remedy or what to check next ?
    Are you using SELinux? There might be a security policy issue.

    Normally, the list creation process creates the
    archives/private/listname/listname.mbox/ directory and the first
    archived message creates the
    archives/private/listname/listname.mbox/listname.mbox file. It seems
    that you have neither the directory or file for your lists. If you
    create the directories by hand (in the 'mailman' group and group
    writable and searchable and normally setgid although I don't think
    that setgid is really necessary), that may allow messages to be
    archived, but it doesn't answer the question of why the directories
    weren't created in the first place.

    There may be relevant messages in Mailman's 'error' log. Also, the
    unarchived posts may be in the shunt queue such that creating the
    directories and running bin/unshunt will archive those posts.

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Michael J McCafferty at Aug 1, 2005 at 12:48 am
    Mark,
    Thanks for the rapid reply.
    I am not using SELinux (doesn't come in RHEL3 or CentOS 3.x)
    The lists were recovered from only partial backups (the customer
    only provided the /var/mailman/lists directory, and nothing else.) So, if
    the place for the mbox files were created only during list creation, that
    could account for it. The error log does indicate that the mbox file or
    directory is missing. I should have looked there (slaps forehead).
    I have created the directories and run check_perms -f to make
    sure it's all ok. now all I gotta do is wait for some posts to the lists
    (they are not my lists) to see if it works.

    Thanks !!!
    Mike
    At 05:11 PM 7/31/2005 -0700, Mark Sapiro wrote:
    Michael J McCafferty wrote:
    I am using Mailman 2.1.5 with Postfix on CentOS 3.5 (RHEL 3). My problem
    is that I have no archives. They are not being created.

    Each list is set to archive, and to make the archives public. I do have
    Apache set to follow symlinks. I also do not have any mbox directories or
    files being kept. I don't know why. I figure that I have no archives
    because I have no mboxes. I have checked the permissions (check_perms).

    Any thoughts on how to remedy or what to check next ?
    Are you using SELinux? There might be a security policy issue.

    Normally, the list creation process creates the
    archives/private/listname/listname.mbox/ directory and the first
    archived message creates the
    archives/private/listname/listname.mbox/listname.mbox file. It seems
    that you have neither the directory or file for your lists. If you
    create the directories by hand (in the 'mailman' group and group
    writable and searchable and normally setgid although I don't think
    that setgid is really necessary), that may allow messages to be
    archived, but it doesn't answer the question of why the directories
    weren't created in the first place.

    There may be relevant messages in Mailman's 'error' log. Also, the
    unarchived posts may be in the shunt queue such that creating the
    directories and running bin/unshunt will archive those posts.

    --
    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 Aug 1, 2005 at 1:11 am

    Michael J McCafferty wrote:

    I have created the directories and run check_perms -f to make
    sure it's all ok. now all I gotta do is wait for some posts to the lists
    (they are not my lists) to see if it works.

    At 05:11 PM 7/31/2005 -0700, Mark Sapiro wrote:
    <snip>
    Normally, the list creation process creates the
    archives/private/listname/listname.mbox/ directory and the first
    archived message creates the
    archives/private/listname/listname.mbox/listname.mbox file.
    Perhaps you noticed the error in the above and weren't misled by it,
    but I gave the wrong path for the .mbox files.

    The archive directory structure is in archives/private/listname, but
    the cumulative mbox file is in
    archives/private/listname.mbox/listname.mbox, NOT in
    archives/private/listname/listname.mbox/listname.mbox.

    Sorry for any confusion.

    --
    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 31, '05 at 11:38p
activeAug 1, '05 at 1:11a
posts4
users2
websitelist.org

People

Translate

site design / logo © 2022 Grokbase