bogus archive directory messages to mailman list
![](https://secure.gravatar.com/avatar/784960f0e0e27d2748a3276cca2409ee.jpg?s=120&d=mm&r=g)
This is Mailman 2.1.5rc on Linux. I have seen this happen with 2.1.4 as well. Each night nightly-gzip creates a complaint about this:
List kunden-alle has a bogus archive_directory: /usr/local/mailman/archives/private/kunden-alle
I'm not sure what it means. There's a symlink from private pointing to a non-existant directory in public. I removed that symlink but it still creates the same message. So, what does it want? Do I need to change configuration somewhere? (archiving = no) Or should I have created the directory the symlink was pointing to instead of removing the symlink?
(this list was created by copying a list directory with all content and then editing the new list. This way the original archive directory wasn't copied.)
Ok, that was one question, probably easily explained. But there's more. This message is obviously sent to the mailman umbrella list which doesn't accept it because the sender (root@<hostname>) is not a member of the list. Should I add it to the list, should I do something else? I just created that list as I was told in some Mailman setup instruction. There wasn't anything about adding members in it. This list doesn't have any members.
Kai
--
Kai Schätzl, Berlin, Germany Get your web at Conactive Internet Services: http://www.conactive.com IE-Center: http://ie5.de & http://msie.winware.org
![](https://secure.gravatar.com/avatar/4f36b4d2b1cde650bbb41d889c64bc07.jpg?s=120&d=mm&r=g)
On Tue, Jun 29, 2004 at 09:31:31PM +0200, Kai Schaetzl wrote:
It should be the other direction. By default the archives are created in the private tree, and a symbolic link is created in the public tree pointing at them if the archives are to be public.
Check the permissions of your private archive directory, and if it contains the expected *.txt files. It sounds like mailman is having trouble writing there. The message is complaining that the expected archive files don't exist even though you have specified archiving and the list claims to have received at least one post.
If you don't want archiving, you can disable it on the "Archiving Options" page of the administrative interface.
-- Jim Tittsler http://www.OnJapan.net/ GPG: 0x01159DB6 Python Starship http://Starship.Python.net/ Ringo MUG Tokyo http://www.ringo.net/rss.html
![](https://secure.gravatar.com/avatar/4f36b4d2b1cde650bbb41d889c64bc07.jpg?s=120&d=mm&r=g)
On Tue, Jun 29, 2004 at 09:31:31PM +0200, Kai Schaetzl wrote:
It should be the other direction. By default the archives are created in the private tree, and a symbolic link is created in the public tree pointing at them if the archives are to be public.
Check the permissions of your private archive directory, and if it contains the expected *.txt files. It sounds like mailman is having trouble writing there. The message is complaining that the expected archive files don't exist even though you have specified archiving and the list claims to have received at least one post.
If you don't want archiving, you can disable it on the "Archiving Options" page of the administrative interface.
-- Jim Tittsler http://www.OnJapan.net/ GPG: 0x01159DB6 Python Starship http://Starship.Python.net/ Ringo MUG Tokyo http://www.ringo.net/rss.html
participants (2)
-
Jim Tittsler
-
Kai Schaetzl