Visvanath Ratnaweera wrote:
>
>The confustion was the difference in ownership, some owner mailman
>some root.
Owner generally doesn't matter. It depends on who owned the process
that created the file or directory in the first place. The important
thing is group. Everything should be group 'mailma
Hi Mark
Many thanks for the hotline!
Ref: Mark Sapiro <[EMAIL PROTECTED]> 10.02.2008 23:04
> Mark Sapiro wrote:
>
> >Visvanath Ratnaweera wrote:
> >>
> >>withing OURLIST there is some confusion:
> >>drwxrwsr-x 2 rootmailman 12288 2008-02-10 19:11 2007-September/
> >>-rw-r--r-- 1 root
Mark Sapiro wrote:
>Visvanath Ratnaweera wrote:
>>
>>withing OURLIST there is some confusion:
>>drwxrwsr-x 2 rootmailman 12288 2008-02-10 19:11 2007-September/
>>-rw-r--r-- 1 rootmailman 481377 2008-02-10 19:11 2007-September.txt
>>-rw-r--r-- 1 rootmailman 92418 2008-02-07 03:2
Visvanath Ratnaweera wrote:
>
>drwxrwsr-x 4 root mailman 4096 2007-11-11 15:30 archives//
>drwxrwsr-x 2 root mailman 4096 2007-11-13 22:55 public/
Above are good.
>interesting
>lrwxrwxrwx 1 root mailman 43 2007-11-13 22:55
>/usr/local/mailman/archives/public/OURLIST ->
>/usr/local/mailman/arc
Hi Mark
Ref: Mark Sapiro <[EMAIL PROTECTED]> 10.02.2008 21:24
> Visvanath Ratnaweera wrote:
> >
> >My Defaults.py set it correctly
> >---
> >DEFAULT_ARCHIVE = On
> >DEFAULT_ARCHIVE_PRIVATE = 0
> >ARCHIVE_TO_MBOX = 2
> >---
> >
> >and not touched in mm_cfg.py. Does an explicite override in
> >mm_cf
Visvanath Ratnaweera wrote:
>
>My Defaults.py set it correctly
>---
>DEFAULT_ARCHIVE = On
>DEFAULT_ARCHIVE_PRIVATE = 0
>ARCHIVE_TO_MBOX = 2
>---
>
>and not touched in mm_cfg.py. Does an explicite override in
>mm_cfg.py necessary?
No.
Perhaps there is a permissions problem. Try running bin/check_
Hi Mark
Ref: Mark Sapiro <[EMAIL PROTECTED]> 10.02.2008 20:28
> >
> >I did a "clean-up" in the server. Rather than starting qrunner,
> >ArchRunner etc manually, /usr/local/mailman/scripts/mailman being
> >now called with "start" as argument during boot. Mail delivery is OK
> >but the archive is n
Visvanath Ratnaweera wrote:
>
>I did a "clean-up" in the server. Rather than starting qrunner,
>ArchRunner etc manually, /usr/local/mailman/scripts/mailman being
>now called with "start" as argument during boot. Mail delivery is OK
>but the archive is not created automatically. I have to call
>bi
Hi
Ref: Visvanath Ratnaweera <[EMAIL PROTECTED]> 04.02.2008 22:23
>
> Ref: Mark Sapiro <[EMAIL PROTECTED]> 04.02.2008 20:53
> > Visvanath Ratnaweera wrote:
> > >
> > >The testmails are also delivered. But not archived. What could
> > >be missing?
> >
> >
> > Is ArchRunner running?
>
> That was
Hi Mark
Ref: Mark Sapiro <[EMAIL PROTECTED]> 04.02.2008 20:53
> Visvanath Ratnaweera wrote:
> >
> >The testmails are also delivered. But not archived. What could
> >be missing?
>
>
> Is ArchRunner running?
That was it! It did a lot of processing. At the end "Feb 2008"
archive appeared with the
Visvanath Ratnaweera wrote:
>
>Only later I noticed that one small step is still missing: The mails
>are not archived!
>
>I issued # bin/check_perms -f and got a whole lot of messages like:
>...
>article db files must be 0660: /usr/local/mailman/archives/private/
>/database/2006-March-article (fixi
Hi all
Only later I noticed that one small step is still missing: The mails
are not archived!
I issued # bin/check_perms -f and got a whole lot of messages like:
...
article db files must be 0660: /usr/local/mailman/archives/private/
/database/2006-March-article (fixing)
During the second run it
12 matches
Mail list logo
