This seems to be a somewhat common problem, so I've looked at the archives at all the suggestions, tried everything that is recent and nothing has worked. It looks like no archives are actually being created, despite the "yes" option being selected in the list configuration.


Thanks for any help.
Kevin Nowaczyk


I'm running mailman 2.1.18 on debian 8.2 (Jessie)


mm_cfg.py has the line
DEFAULT_URL_PATTERN = 'http://%s/'
  and no value for PUBLIC_ARCHIVE_URL.
messing with these setting seemed to be a 10 year old issue, so I didn't play around with this for fear of breaking something else


My apache config:
<VirtualHost *:80>
ServerName lists.example.com
DocumentRoot /usr/lib/cgi-bin/mailman
ErrorLog /var/log/apache2/lists-error.log
CustomLog /var/log/apache2/lists-access.log combined


Alias /pipermail/ /var/lib/mailman/archives/public/
<Directory /var/lib/mailman/archives/public>
     Options +FollowSymLinks
     Order allow,deny
     Allow from all
</Directory>
Alias /images/mailman/ /usr/share/images/mailman/
ScriptAlias /admin /usr/lib/cgi-bin/mailman/admin
ScriptAlias /admindb /usr/lib/cgi-bin/mailman/admindb
ScriptAlias /confirm /usr/lib/cgi-bin/mailman/confirm
ScriptAlias /create /usr/lib/cgi-bin/mailman/create
ScriptAlias /edithtml /usr/lib/cgi-bin/mailman/edithtml
ScriptAlias /listinfo /usr/lib/cgi-bin/mailman/listinfo
ScriptAlias /options /usr/lib/cgi-bin/mailman/options
ScriptAlias /private /usr/lib/cgi-bin/mailman/private
ScriptAlias /rmlist /usr/lib/cgi-bin/mailman/rmlist
ScriptAlias /roster /usr/lib/cgi-bin/mailman/roster
ScriptAlias /subscribe /usr/lib/cgi-bin/mailman/subscribe
ScriptAlias /mailman/ /usr/lib/cgi-bin/mailman/
</VirtualHost>


Directory Listing:


.:
total 16
drwxrwsr-x 4 root list 4096 Sep 9 20:35 .
drwxrwsr-x 8 root list 4096 Jul 6 11:55 ..
-rw-r--r-- 1 root list 0 Sep 9 20:35 list
drwxrws--- 8 www-data list 4096 Feb 24 2015 private
drwxrwsr-x 2 root list 4096 Sep 9 20:04 public


./private:
total 32
drwxrws--- 8 www-data list 4096 Feb 24 2015 .
drwxrwsr-x 4 root list 4096 Sep 9 20:35 ..
drwxrwsr-x 2 root list 4096 Sep 9 19:40 LISTNAME
drwxrwsr-x 2 root list 4096 Feb 14 2014 LISTNAME.mbox
drwxrwsr-x 2 root list 4096 Feb 13 2014 mailman
drwxrwsr-x 2 root list 4096 Feb 13 2014 mailman.mbox


./private/LISTNAME:
total 12
drwxrwsr-x 2 root list 4096 Sep 9 19:40 .
drwxrws--- 8 www-data list 4096 Feb 24 2015 ..
-rw-rw-r-- 1 root list 493 Feb 14 2014 index.html


./private/LISTNAME.mbox:
total 8
drwxrwsr-x 2 root list 4096 Feb 14 2014 .
drwxrws--- 8 www-data list 4096 Feb 24 2015 ..


./private/mailman:
total 12
drwxrwsr-x 2 root list 4096 Feb 13 2014 .
drwxrws--- 8 www-data list 4096 Feb 24 2015 ..
-rw-rw-r-- 1 root list 506 Feb 13 2014 index.html


./private/mailman.mbox:
total 8
drwxrwsr-x 2 root list 4096 Feb 13 2014 .
drwxrws--- 8 www-data list 4096 Feb 24 2015 ..


./public:
total 8
drwxrwsr-x 2 root list 4096 Sep 9 20:04 .
drwxrwsr-x 4 root list 4096 Sep 9 20:35 ..
lrwxrwxrwx 1 root list 42 Feb 14 2014 LISTNAME -> /var/lib/mailman/archives/private/LISTNAME
lrwxrwxrwx 1 root list 41 Feb 13 2014 mailman -> /var/lib/mailman/archives/private/mailman

Search Discussions

  • Mark Sapiro at Sep 10, 2015 at 7:10 am

    On 09/09/2015 01:44 PM, Kevin Nowaczyk via Mailman-Users wrote:
    It looks like no archives are actually being
    created, despite the "yes" option being selected in the list
    configuration.

    Thanks for any help. Kevin Nowaczyk

    I'm running mailman 2.1.18 on debian 8.2 (Jessie)

    mm_cfg.py has the line DEFAULT_URL_PATTERN = 'http://%s/' and no
    value for PUBLIC_ARCHIVE_URL. messing with these setting seemed to be
    a 10 year old issue, so I didn't play around with this for fear of
    breaking something else



    These are irrelevant to your problem.



    My apache config:



    As is your apache config. It is not a web server issue.

    Directory Listing:


    .:
    total 16
    drwxrwsr-x 4 root list 4096 Sep 9 20:35 .
    drwxrwsr-x 8 root list 4096 Jul 6 11:55 ..
    -rw-r--r-- 1 root list 0 Sep 9 20:35 list
    drwxrws--- 8 www-data list 4096 Feb 24 2015 private
    drwxrwsr-x 2 root list 4096 Sep 9 20:04 public



    This looks OK



    ./private:
    total 32
    drwxrws--- 8 www-data list 4096 Feb 24 2015 .
    drwxrwsr-x 4 root list 4096 Sep 9 20:35 ..
    drwxrwsr-x 2 root list 4096 Sep 9 19:40 LISTNAME
    drwxrwsr-x 2 root list 4096 Feb 14 2014 LISTNAME.mbox
    drwxrwsr-x 2 root list 4096 Feb 13 2014 mailman
    drwxrwsr-x 2 root list 4096 Feb 13 2014 mailman.mbox



    As does this



    ./private/LISTNAME:
    total 12
    drwxrwsr-x 2 root list 4096 Sep 9 19:40 .
    drwxrws--- 8 www-data list 4096 Feb 24 2015 ..
    -rw-rw-r-- 1 root list 493 Feb 14 2014 index.html



    And this says the archive is empty.



    ./private/LISTNAME.mbox:
    total 8
    drwxrwsr-x 2 root list 4096 Feb 14 2014 .
    drwxrws--- 8 www-data list 4096 Feb 24 2015 ..



    And no LISTNAME.mbox/LISTNAME.mbox file says archiving never got far.



    ./private/mailman:
    total 12
    drwxrwsr-x 2 root list 4096 Feb 13 2014 .
    drwxrws--- 8 www-data list 4096 Feb 24 2015 ..
    -rw-rw-r-- 1 root list 506 Feb 13 2014 index.html

    ./private/mailman.mbox:
    total 8
    drwxrwsr-x 2 root list 4096 Feb 13 2014 .
    drwxrws--- 8 www-data list 4096 Feb 24 2015 ..



    Ditto for the mailman list, but it may never have gotten a post.



    ./public:
    total 8
    drwxrwsr-x 2 root list 4096 Sep 9 20:04 .
    drwxrwsr-x 4 root list 4096 Sep 9 20:35 ..
    lrwxrwxrwx 1 root list 42 Feb 14 2014 LISTNAME -> /var/lib/mailman/archives/private/LISTNAME
    lrwxrwxrwx 1 root list 41 Feb 13 2014 mailman -> /var/lib/mailman/archives/private/mailman



    OK, but not really relevant to the issue.


    Is ArchRunner running?


    Is anything in /var/lib/mailman/queue/archive?


    What's in /var/lib/mailman/logs/qrunner and /var/lib/mailman/logs/error?


    --
    Mark Sapiro <mark@msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Mark Sapiro at Sep 10, 2015 at 7:22 am

    On 09/09/2015 01:44 PM, Kevin Nowaczyk via Mailman-Users wrote:
    This seems to be a somewhat common problem, so I've looked at the archives at all the suggestions, tried everything that is recent and nothing has worked. It looks like no archives are actually being created, despite the "yes" option being selected in the list configuration.



    My previous reply assumed that there had been successful posts to the
    list that weren't archived, but the "Forbidden" in the subject may imply
    that there have been no posts, but you are getting a 403 Forbidden
    status from apache when attempting to go to the archives.


    If this is the issue, the problem is probably that you have apache 2.4
    and this

    Alias /pipermail/ /var/lib/mailman/archives/public/
    <Directory /var/lib/mailman/archives/public>
    Options +FollowSymLinks
    Order allow,deny
    Allow from all
    </Directory>

    needs to be


    Alias /pipermail/ /var/lib/mailman/archives/public/
    <Directory /var/lib/mailman/archives/public>
         Options +FollowSymLinks
         Require all granted
    </Directory>


    If that isn't the answer, but the issue is 403 Forbidden, what's in
    /var/log/apache2/lists-error.log?


    --
    Mark Sapiro <mark@msapiro.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Kevin Nowaczyk at Sep 10, 2015 at 11:24 am
    Changing this apache configuration allows me to see the archive. The archive only shows one message, one that I posted yesterday. There must have been some other permissions issue which prevented mailman from saving all the previous messages to the archive.


    Thanks for the help!
    Kevin Nowaczyk
    --------------------------------------------
    On Thu, 9/10/15, Kevin Nowaczyk wrote:


      Subject: Re: [Mailman-Users] Forbidden Mailman Archive
      To: "Mark Sapiro" <mark@msapiro.net>
      Date: Thursday, September 10, 2015, 7:23 AM


      Changing this apache
      configuration allows me to see the archive. The archive only
      shows one message, one that I posted yesterday. There must
      have been some other permissions issue which prevented
      mailman from saving all the previous messages to the
      archive.


      Thanks for the
      help!
      Kevin Nowaczyk
      --------------------------------------------
      On Thu, 9/10/15, Mark Sapiro wrote:


       Subject: Re:
      [Mailman-Users] Forbidden Mailman Archive


      To: mailman-users at python.org
       Date: Thursday, September 10, 2015, 3:22 AM


       On 09/09/2015 01:44 PM,
       Kevin Nowaczyk via Mailman-Users wrote:
       >
       This seems to be a
      somewhat common problem, so I've
       looked
      at the archives at all the suggestions, tried
       everything that is recent and nothing has
      worked. It looks
       like no archives are
      actually being created, despite the


      "yes" option being selected in the list
       configuration.




       My previous reply assumed
      that there had been
       successful posts to
      the
       list that
       weren't
      archived, but the "Forbidden" in the
       subject may imply
       that there
      have been no
       posts, but you are getting a
      403 Forbidden
       status from apache when
      attempting to go to the
       archives.


       If this is the
       issue, the problem is probably that you have
      apache 2.4
       and this


       >
       Alias /pipermail/
      /var/lib/mailman/archives/public/
       >
      <Directory


      /var/lib/mailman/archives/public>

    ?
       ???Options +FollowSymLinks
    ?
       ???Order
      allow,deny
    ?

      ???Allow from all
       >


      </Directory>


       needs
      to
       be




      Alias /pipermail/


      /var/lib/mailman/archives/public/


      <Directory


      /var/lib/mailman/archives/public>
       ?
      ?
       Options +FollowSymLinks


      ? ? Require all
       granted


      </Directory>


       If
      that isn't the answer,
       but the issue is
      403 Forbidden, what's in


      /var/log/apache2/lists-error.log?


       --
       Mark


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


      ------------------------------------------------------
       Mailman-Users mailing list Mailman-Users at python.org
       https://mail.python.org/mailman/listinfo/mailman-users
       Mailman FAQ: http://wiki.list.org/x/AgA3
       Security Policy: http://wiki.list.org/x/QIA9
       Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
       Unsubscribe: https://mail.python.org/mailman/options/mailman-users/beakerboy99%40yahoo.com
  • Mark Sapiro at Sep 10, 2015 at 3:44 pm

    On 09/10/2015 04:24 AM, Kevin Nowaczyk via Mailman-Users wrote:
    Changing this apache configuration allows me to see the archive. The archive only shows one message, one that I posted yesterday. There must have been some other permissions issue which prevented mailman from saving all the previous messages to the archive.



    If there was some issue that prevented earlier messages from being
    archived, the messages may have encountered some exception causing them
    to be shunted. If so, Mailman's error log (/var/lib/mailman/logs/error
    in your case) will have more info, and the messages will probably be in
    the shunt queue (/var/lib/mailman/qfiles/shunt/). The shunted messages
    can be viewed with Mailman's bin/show_qfiles tool and requeued for the
    archive with bin/unshunt.


    --
    Mark Sapiro <mark@msapiro.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
postedSep 9, '15 at 8:44p
activeSep 10, '15 at 3:44p
posts5
users2
websitelist.org

2 users in discussion

Mark Sapiro: 3 posts Kevin Nowaczyk: 2 posts

People

Translate

site design / logo © 2021 Grokbase