[Mailman-Users] Re: Archive Issue -- prune_arch doesn't remove detached attachments?

2020-12-22 Thread Juliano Alves Guidini 
Hi,

I'm observed this behavior too. To solve, I used a script on cron, like
this, to maintain 2 years of archive:

[...]
year=`date --date='2 years ago' +%Y`
month=`date --date='last month' +%m`
data_corte="${ano}${mes}"
path_private='/usr/local/mailman/archives/private'

find "${path_private}" -depth -regextype posix-egrep -regex
".*/attachments/${data_corte}.*/.*" -delete

Running this script monthly solve my problem of space.


Best Regards,

Juliano Alves Guidini
Analista de Sistemas
USP - STI -  CeTI-SP - DVTIN - SCTIN - SCTS


Em ter., 22 de dez. de 2020 às 11:49, Stephen J. Turnbull <
turnbull.stephen...@u.tsukuba.ac.jp> escreveu:

> Ralf Hildebrandt writes:
>
>  > Today I issued "prune_arch -l flohmarkt -d 30" and wondered about
>  > the immense size of the corresponding archive directory
>  > archives/private/flohmarkt
>
>  > Shouldn't prune_arch also clean out the "attachments" directory?
>  > (mailman-2.1.34)
>
> Probably, but that's up to Mark (and I'm pretty sure that's one of his
> personally-maintained scripts rather than one distributed by Mailman).
> --
> Mailman-Users mailing list -- mailman-users@python.org
> To unsubscribe send an email to mailman-users-le...@python.org
> https://mail.python.org/mailman3/lists/mailman-users.python.org/
> Mailman FAQ: http://wiki.list.org/x/AgA3
> Security Policy: http://wiki.list.org/x/QIA9
> Searchable Archives:
> https://www.mail-archive.com/mailman-users@python.org/
> https://mail.python.org/archives/list/mailman-users@python.org/
>
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Archive Issue -- prune_arch doesn't remove detached attachments?

2020-12-22 Thread Mark Sapiro 
On 12/22/20 8:35 AM, Mark Sapiro wrote:
> 
> My current thinking is if the list's scrub_nondigest setting is Yes,
> remove the "pruned" attachments and if either -b/--backup or
> -p/--preserve is specified, backup/preserve them too.
> 
> Other thoughts are welcome.
> 


I've updated the script at 
and . It does
essentially what I say above. In Ralf's "prune_arch -l flohmarkt -d 30"
case, it will just remove all the
archives/private/flohmarkt/attachment/mmdd directories older than 30
days in addition to removing the older archived messages.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Archive Issue -- prune_arch doesn't remove detached attachments?

2020-12-22 Thread Mark Sapiro 
On 12/22/20 6:48 AM, Stephen J. Turnbull wrote:
> Ralf Hildebrandt writes:
> 
>  > Today I issued "prune_arch -l flohmarkt -d 30" and wondered about
>  > the immense size of the corresponding archive directory
>  > archives/private/flohmarkt
> 
>  > Shouldn't prune_arch also clean out the "attachments" directory?
>  > (mailman-2.1.34)
> 
> Probably, but that's up to Mark (and I'm pretty sure that's one of his
> personally-maintained scripts rather than one distributed by Mailman).


This is tricky. Prune_arch without the -n/--nobuild option will rebuild
the archive from the pruned mbox file with `bin/arch --wipe`. The issue
is that in the case where the list's scrub_nondigest setting is Yes,
`bin/arch --wipe` preserves the old attachments/ directory because it
contains scrubbed attachments which are not in the mbox file. I.e., the
mbox messages have only links to the attachments in the attachments/
directory.

The attachments directory contains subdirectories of the form mmdd
so it would be possible for prune_arch to determine which ones should
also be pruned. I can look into adding that, although it probably should
be optional because in the case where prune_arch is doing  -b/--backup
or -p/--preserve, the only place where the scrubbed attachments exist is
in those attachments/ directories and removing those directories will
result in possibly unintended loss of information. I.e., the backed up
or pruned mbox will contain links to attachments which will be broken if
the attachments are removed.

My current thinking is if the list's scrub_nondigest setting is Yes,
remove the "pruned" attachments and if either -b/--backup or
-p/--preserve is specified, backup/preserve them too.

Other thoughts are welcome.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Archive Issue

2020-09-18 Thread Mark Sapiro 
On 9/18/20 6:48 AM, Dennis Putnam wrote:
> 
> You are correct. However, the test system was cloned with just a
> hostname change. The original production system, from which the test
> system was cloned, has the same problem.


So you should fix that in the same way. How it broke, I don't know
unless at some point you did a backup and restore on the production system.


> I followed your instructions and it worked on the test system. What is
> really odd, to me, is that now the archives after Feb 2020 are showing
> up. Anyway, it looks like we are good to go. Thanks yet again.


Yes. As I've tried to explain, archiving only updates
/var/lib/mailman/archives/private/*. pipermail URLs reference
/var/lib/mailman/archives/public/* which should be symlinks to
/var/lib/mailman/archives/private/* to see the updated archive, but if
/var/lib/mailman/archives/public/* is an actual file hierarchy, it is
static and you won't see changes.

By fixing this and making /var/lib/mailman/archives/public/* the
appropriate symlinks, pipermail URLs are now showing you the content in
/var/lib/mailman/archives/private/* which was being updated all along.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Archive Issue

2020-09-18 Thread Dennis Putnam 
On 9/17/2020 8:15 PM, Mark Sapiro wrote:
> On 9/17/20 4:49 PM, Dennis Putnam wrote:
>>  
>> I'll give that a try tomorrow. In the meantime I discovered something
>> that may or may not be relevant. Apparently the last saved archive was
>> in Feb 2020. That was when I did a 'yum update' to version 2.1.15 to
>> resolve the DMARC problem. I am betting that the RHEL version did
>> something to cause this problem. It is too much of a coincidence to
>> think otherwise.
>
> I really doubt that. Is my conjecture correct that you are working on a
> test system copied from a production system? If so, is the contents of
> /var/lib/mailman/archives/public on the production system symlinks or
> entire file hierarchies. I suspect the former and that the full file
> hierarchies in /var/lib/mailman/archives/public only exist in the backups.
>
Hi Mark,

You are correct. However, the test system was cloned with just a
hostname change. The original production system, from which the test
system was cloned, has the same problem.

I followed your instructions and it worked on the test system. What is
really odd, to me, is that now the archives after Feb 2020 are showing
up. Anyway, it looks like we are good to go. Thanks yet again.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Archive Issue

2020-09-17 Thread Mark Sapiro 
On 9/17/20 4:49 PM, Dennis Putnam wrote:
>  
> I'll give that a try tomorrow. In the meantime I discovered something
> that may or may not be relevant. Apparently the last saved archive was
> in Feb 2020. That was when I did a 'yum update' to version 2.1.15 to
> resolve the DMARC problem. I am betting that the RHEL version did
> something to cause this problem. It is too much of a coincidence to
> think otherwise.


I really doubt that. Is my conjecture correct that you are working on a
test system copied from a production system? If so, is the contents of
/var/lib/mailman/archives/public on the production system symlinks or
entire file hierarchies. I suspect the former and that the full file
hierarchies in /var/lib/mailman/archives/public only exist in the backups.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Archive Issue

2020-09-17 Thread Dennis Putnam 
On 9/17/2020 5:34 PM, Mark Sapiro wrote:
> On 9/17/20 11:50 AM, Dennis Putnam wrote:
>> Hit a bug page. Note this is the production server running 2.1.15 but
>> the test server running 2.1.34 got the same thing. This is the error log:
>>
>> Sep 17 12:37:13 2020 admin(24458):
>> 
>> admin(24458): [- Mailman Version: 2.1.15 -]
>> admin(24458): [- Traceback --]
>> admin(24458): Traceback (most recent call last):
>> admin(24458):   File "/usr/lib/mailman/scripts/driver", line 112, in
>> run_main
>> admin(24458): main()
>> admin(24458):   File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 227,
>> in main
>> admin(24458): mlist.Save()
>> admin(24458):   File "/usr/lib/mailman/Mailman/MailList.py", line 582,
>> in Save
>> admin(24458): self.CheckHTMLArchiveDir()
>> admin(24458):   File "/usr/lib/mailman/Mailman/Archiver/Archiver.py",
>> line 236, in CheckHTMLArchiveDir
>> admin(24458): breaklink(pubdir)
>> admin(24458):   File "/usr/lib/mailman/Mailman/Archiver/Archiver.py",
>> line 56, in breaklink
>> admin(24458): os.unlink(link)
>> admin(24458): OSError: [Errno 21] Is a directory:
> I thought that might happen, but I didn't confirm it. Oh well ...
>
> Do this:
>
> rm -rf /var/lib/mailman/archives/public/*
>
> Then Toggle the archive_private setting in the web admin UI for both lists.
>
> The background on what caused this in the first place is you apparently
> copied your production Mailman installation to a test environment, but
> whatever process you used to do the copy, copied the targets of the
> symlinks in /var/lib/mailman/archives/public/ instead of copying the
> symlinks as symlinks.
>
> This is what causes the issue with public archives no longer being
> updated. They actually are updated in
> /var/lib/mailman/archives/private/, but the pipermail URLs point to the
> old, static archive now copied to /var/lib/mailman/archives/public/.
>
> We've seen this multiple times in backup/restore scenarios and moving
> installations to another server.
>
> The bottom line is when backing up, always ensure you copy symlinks as
> symlinks and not their targets. For rsync, this is -l/--links (included
> as part of -a/--archive). For cp, it's -d or -P/--no-dereference or
> -a/--archive.
>
Hi Mark,
 
I'll give that a try tomorrow. In the meantime I discovered something
that may or may not be relevant. Apparently the last saved archive was
in Feb 2020. That was when I did a 'yum update' to version 2.1.15 to
resolve the DMARC problem. I am betting that the RHEL version did
something to cause this problem. It is too much of a coincidence to
think otherwise.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Archive Issue

2020-09-17 Thread Mark Sapiro 
On 9/17/20 11:50 AM, Dennis Putnam wrote:
> Hit a bug page. Note this is the production server running 2.1.15 but
> the test server running 2.1.34 got the same thing. This is the error log:
> 
> Sep 17 12:37:13 2020 admin(24458):
> 
> admin(24458): [- Mailman Version: 2.1.15 -]
> admin(24458): [- Traceback --]
> admin(24458): Traceback (most recent call last):
> admin(24458):   File "/usr/lib/mailman/scripts/driver", line 112, in
> run_main
> admin(24458): main()
> admin(24458):   File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 227,
> in main
> admin(24458): mlist.Save()
> admin(24458):   File "/usr/lib/mailman/Mailman/MailList.py", line 582,
> in Save
> admin(24458): self.CheckHTMLArchiveDir()
> admin(24458):   File "/usr/lib/mailman/Mailman/Archiver/Archiver.py",
> line 236, in CheckHTMLArchiveDir
> admin(24458): breaklink(pubdir)
> admin(24458):   File "/usr/lib/mailman/Mailman/Archiver/Archiver.py",
> line 56, in breaklink
> admin(24458): os.unlink(link)
> admin(24458): OSError: [Errno 21] Is a directory:

I thought that might happen, but I didn't confirm it. Oh well ...

Do this:

rm -rf /var/lib/mailman/archives/public/*

Then Toggle the archive_private setting in the web admin UI for both lists.

The background on what caused this in the first place is you apparently
copied your production Mailman installation to a test environment, but
whatever process you used to do the copy, copied the targets of the
symlinks in /var/lib/mailman/archives/public/ instead of copying the
symlinks as symlinks.

This is what causes the issue with public archives no longer being
updated. They actually are updated in
/var/lib/mailman/archives/private/, but the pipermail URLs point to the
old, static archive now copied to /var/lib/mailman/archives/public/.

We've seen this multiple times in backup/restore scenarios and moving
installations to another server.

The bottom line is when backing up, always ensure you copy symlinks as
symlinks and not their targets. For rsync, this is -l/--links (included
as part of -a/--archive). For cp, it's -d or -P/--no-dereference or
-a/--archive.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Archive Issue

2020-09-17 Thread Dmitri Maziuk 

On 9/17/2020 2:13 PM, Dennis Putnam wrote:


I know. That is what Mark is trying to help me fix. Public contains all
the archives rather than private so creating a symlink will destroy the
archives.


??? Can't you move it?

Dima
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Archive Issue

2020-09-17 Thread Dennis Putnam 
On 9/17/2020 2:57 PM, Dmitri Maziuk wrote:
> On 9/17/2020 1:50 PM, Dennis Putnam wrote:
>
>> admin(24458): OSError: [Errno 21] Is a directory:
>> '/var/lib/mailman/archives/public/rushtalk'
>
> ICBW but files in public/ should be symlinks to subdirs in private/
> i.e. public/rushtalk should be a symlink to private/rushtalk and not a
> directory.
>
> Dima
I know. That is what Mark is trying to help me fix. Public contains all
the archives rather than private so creating a symlink will destroy the
archives.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Archive Issue

2020-09-17 Thread Dmitri Maziuk 

On 9/17/2020 1:50 PM, Dennis Putnam wrote:


admin(24458): OSError: [Errno 21] Is a directory:
'/var/lib/mailman/archives/public/rushtalk'


ICBW but files in public/ should be symlinks to subdirs in private/ i.e. 
public/rushtalk should be a symlink to private/rushtalk and not a directory.


Dima
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
   https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Archive Issue

2020-09-17 Thread Dennis Putnam 
On 9/17/2020 1:06 PM, Mark Sapiro wrote:
> OK. First make a backup of /var/lib/mailman/archives/public/ just in
> case, although it appears that
> /var/lib/mailman/archives/private/rushtalk is more up to date. Then go
> to the web admin UI for both the mailman and rushtalk lists and set
> Archiving Options -> archive_private to private and then set it back to
> public.
>
> That should fix it.
>
> The story is all updates are done in /var/lib/mailman/archives/private,
> and /var/lib/mailman/archives/public should contain only symlinks to
> /var/lib/mailman/archives/private. Since
> /var/lib/mailman/archives/public contains archives rather than symlinks,
> those archives are static as of whatever created them and are never updated.
Hit a bug page. Note this is the production server running 2.1.15 but
the test server running 2.1.34 got the same thing. This is the error log:

Sep 17 12:37:13 2020 admin(24458):

admin(24458): [- Mailman Version: 2.1.15 -]
admin(24458): [- Traceback --]
admin(24458): Traceback (most recent call last):
admin(24458):   File "/usr/lib/mailman/scripts/driver", line 112, in
run_main
admin(24458): main()
admin(24458):   File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 227,
in main
admin(24458): mlist.Save()
admin(24458):   File "/usr/lib/mailman/Mailman/MailList.py", line 582,
in Save
admin(24458): self.CheckHTMLArchiveDir()
admin(24458):   File "/usr/lib/mailman/Mailman/Archiver/Archiver.py",
line 236, in CheckHTMLArchiveDir
admin(24458): breaklink(pubdir)
admin(24458):   File "/usr/lib/mailman/Mailman/Archiver/Archiver.py",
line 56, in breaklink
admin(24458): os.unlink(link)
admin(24458): OSError: [Errno 21] Is a directory:
'/var/lib/mailman/archives/public/rushtalk'
admin(24458): [- Python Information -]
admin(24458): sys.version =   2.7.5 (default, Jun 11 2019, 14:33:56)
[GCC 4.8.5 20150623 (Red Hat 4.8.5-39)]
admin(24458): sys.executable  =   /usr/bin/python
admin(24458): sys.prefix  =   /usr
admin(24458): sys.exec_prefix =   /usr
admin(24458): sys.path    =   ['/usr/lib/mailman/pythonlib',
'/usr/lib/mailman', '/usr/lib/mailman/scripts', '/usr/lib/mailman',
'/usr/lib64/python27.zip', '/usr/lib64/python2.7/',
'/usr/lib64/python2.7/plat-linux2', '/usr/lib64/python2.7/lib-tk',
'/usr/lib64/python2.7/lib-old', '/usr/lib64/python2.7/lib-dynload',
'/usr/lib/python2.7/site-packages']
admin(24458): sys.platform    =   linux2
admin(24458): [- Environment Variables -]
admin(24458):   HTTP_COOKIE:
rushtalk+admin=28020069a4ac635f73280031666237653866353739613765303565326633653266646330663738613838333931383633386635
admin(24458):   CONTEXT_DOCUMENT_ROOT: /usr/lib/mailman/cgi-bin/
admin(24458):   SERVER_SOFTWARE: Apache/2.4.6 (Red Hat Enterprise Linux)
OpenSSL/1.0.2k-fips
admin(24458):   CONTEXT_PREFIX: /mailman/
admin(24458):   SERVER_SIGNATURE:
admin(24458):   REQUEST_METHOD: GET
admin(24458):   PATH_INFO: /rushtalk/archive
admin(24458):   SERVER_PROTOCOL: HTTP/1.1
admin(24458):   QUERY_STRING:
admin(24458):   HTTP_USER_AGENT: Mozilla/5.0 (Windows NT 6.1; Win64;
x64; rv:80.0) Gecko/20100101 Firefox/80.0
admin(24458):   HTTP_CONNECTION: keep-alive
admin(24458):   HTTP_REFERER: http://galene.csd.net/mailman/admin/rushtalk
admin(24458):   SERVER_NAME: galene.csd.net
admin(24458):   REMOTE_ADDR: 162.230.29.192
admin(24458):   PATH_TRANSLATED: /var/www/html/rushtalk/archive
admin(24458):   SERVER_PORT: 80
admin(24458):   SERVER_ADDR: 204.181.152.21
admin(24458):   DOCUMENT_ROOT: /var/www/html
admin(24458):   PYTHONPATH: /usr/lib/mailman
admin(24458):   SCRIPT_FILENAME: /usr/lib/mailman/cgi-bin/admin
admin(24458):   SERVER_ADMIN: root@localhost
admin(24458):   HTTP_DNT: 1
admin(24458):   HTTP_HOST: galene.csd.net
admin(24458):   SCRIPT_NAME: /mailman/admin
admin(24458):   HTTP_UPGRADE_INSECURE_REQUESTS: 1
admin(24458):   REQUEST_URI: /mailman/admin/rushtalk/archive
admin(24458):   HTTP_ACCEPT:
text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
admin(24458):   GATEWAY_INTERFACE: CGI/1.1
admin(24458):   REMOTE_PORT: 61998
admin(24458):   HTTP_ACCEPT_LANGUAGE: en-US,en;q=0.5
admin(24458):   REQUEST_SCHEME: http
admin(24458):   HTTP_ACCEPT_ENCODING: gzip, deflate
admin(24458):   UNIQUE_ID: X2Os2dJmdT9yDBIgbsvt@gk
>
> Note that if you go to the private archive URL at
> http://example.com/mailman/private/rushtalk or wherever it it, you
> should see your recent messages.
>
> I'll be out for a few hours, so if you need more, it'll have to wait.
>
I can wait. Thanks.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http

[Mailman-Users] Re: Archive Issue

2020-09-17 Thread Mark Sapiro 
On 9/17/20 9:39 AM, Dennis Putnam wrote:
> On 9/17/2020 12:29 PM, Mark Sapiro wrote:
>> On 9/17/20 9:06 AM, Dennis Putnam wrote:
>>
>> Before doing anything, show me the results of
>> ls -la /var/lib/mailman/archives/public/
> # ls -la /var/lib/mailman/archives/public/
> total 44
> drwxrwsr-x.   4 root mailman    37 Jul 31  2019 .
> drwxrwsr-x.   4 root mailman    35 Jul 31  2019 ..
> drwxrwsr-x.   2 root mailman    24 Feb 16  2020 mailman
> drwxrwsr-x. 302 root mailman 28672 Feb 16  2020 rushtalk
>>
>> and
>>
>> ls -la /var/lib/mailman/archives/private/
> # ls -la /var/lib/mailman/archives/private/
> total 44
> drwxrws---.   6 apache  mailman    78 Jul 31  2019 .
> drwxrwsr-x.   4 root    mailman    35 Jul 31  2019 ..
> drwxrwsr-x.   2 mailman mailman    24 Feb 16  2020 mailman
> drwxrwsr-x.   2 mailman mailman 6 Feb 16  2020 mailman.mbox
> drwxrwsr-x. 309 mailman mailman 28672 Sep  1 09:38 rushtalk
> drwxrwsr-x.   2 mailman mailman    27 Feb 16  2020 rushtalk.mbox


OK. First make a backup of /var/lib/mailman/archives/public/ just in
case, although it appears that
/var/lib/mailman/archives/private/rushtalk is more up to date. Then go
to the web admin UI for both the mailman and rushtalk lists and set
Archiving Options -> archive_private to private and then set it back to
public.

That should fix it.

The story is all updates are done in /var/lib/mailman/archives/private,
and /var/lib/mailman/archives/public should contain only symlinks to
/var/lib/mailman/archives/private. Since
/var/lib/mailman/archives/public contains archives rather than symlinks,
those archives are static as of whatever created them and are never updated.

Note that if you go to the private archive URL at
http://example.com/mailman/private/rushtalk or wherever it it, you
should see your recent messages.

I'll be out for a few hours, so if you need more, it'll have to wait.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Archive Issue

2020-09-17 Thread Dennis Putnam 
On 9/17/2020 12:29 PM, Mark Sapiro wrote:
> On 9/17/20 9:06 AM, Dennis Putnam wrote:
>
> Before doing anything, show me the results of
> ls -la /var/lib/mailman/archives/public/
# ls -la /var/lib/mailman/archives/public/
total 44
drwxrwsr-x.   4 root mailman    37 Jul 31  2019 .
drwxrwsr-x.   4 root mailman    35 Jul 31  2019 ..
drwxrwsr-x.   2 root mailman    24 Feb 16  2020 mailman
drwxrwsr-x. 302 root mailman 28672 Feb 16  2020 rushtalk
>
> and
>
> ls -la /var/lib/mailman/archives/private/
# ls -la /var/lib/mailman/archives/private/
total 44
drwxrws---.   6 apache  mailman    78 Jul 31  2019 .
drwxrwsr-x.   4 root    mailman    35 Jul 31  2019 ..
drwxrwsr-x.   2 mailman mailman    24 Feb 16  2020 mailman
drwxrwsr-x.   2 mailman mailman 6 Feb 16  2020 mailman.mbox
drwxrwsr-x. 309 mailman mailman 28672 Sep  1 09:38 rushtalk
drwxrwsr-x.   2 mailman mailman    27 Feb 16  2020 rushtalk.mbox
>
> First you need to do something like
>
> rsync -a /var/lib/mailman/archives/public/
> /var/lib/mailman/archives/private/
>
> to copy the entire structure from /var/lib/mailman/archives/public/ to
> /var/lib/mailman/archives/private/.
>
> Alternatively, assuming your
> /var/lib/mailman/archives/private/.mbox/.mbox files
> are good and contain all the messages except recent tests, you could
> just do something like
> ```
> for list in `bin/list_lists --bare`; do
> bin/arch --wipe $list
> done
>
> to rebuild the archives from the .mbox files, but if any of the .mbox
> files go back before Mailman 2.1, they should first be checked with
> bin/cleanarch for unescaped 'From ' lines in message bodies and fixed first.
>
> This part I don't understand. What does
>
> ls -la /var/lib/mailman/archives/private/*.mbox
>
> show?
# ls -la /var/lib/mailman/archives/private/*.mbox
/var/lib/mailman/archives/private/mailman.mbox:
total 0
drwxrwsr-x. 2 mailman mailman  6 Feb 16  2020 .
drwxrws---. 6 apache  mailman 78 Jul 31  2019 ..

/var/lib/mailman/archives/private/rushtalk.mbox:
total 1093228
drwxrwsr-x. 2 mailman mailman 27 Feb 16  2020 .
drwxrws---. 6 apache  mailman 78 Jul 31  2019 ..
-rw-rw-r--. 1 mailman mailman 1119459801 Sep 17 09:38 rushtalk.mbox

That is weird. That mbox seems to be updating but nothing shows up on
the archives web page after Feb 2020.



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Archive Issue

2020-09-17 Thread Mark Sapiro 
On 9/17/20 9:06 AM, Dennis Putnam wrote:

> There are no sym links. Private looks like just place holders as there
> is no data there nor any archives. It looks like everything is in
> public. The ownership is root:mailman and the group has R/O permissions.
> Only root has write. I'm assuming that is correct, otherwise check_perms
> would fix it.

Before doing anything, show me the results of

ls -la /var/lib/mailman/archives/public/

and

ls -la /var/lib/mailman/archives/private/

First you need to do something like

rsync -a /var/lib/mailman/archives/public/
/var/lib/mailman/archives/private/

to copy the entire structure from /var/lib/mailman/archives/public/ to
/var/lib/mailman/archives/private/.

Alternatively, assuming your
/var/lib/mailman/archives/private/.mbox/.mbox files
are good and contain all the messages except recent tests, you could
just do something like
```
for list in `bin/list_lists --bare`; do
bin/arch --wipe $list
done

to rebuild the archives from the .mbox files, but if any of the .mbox
files go back before Mailman 2.1, they should first be checked with
bin/cleanarch for unescaped 'From ' lines in message bodies and fixed first.

>> Are new messages being appended to the
>> /var/lib/mailman/archives/private/.mbox/.mbox files?
> No


This part I don't understand. What does

ls -la /var/lib/mailman/archives/private/*.mbox

show?

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Archive Issue

2020-09-17 Thread Dennis Putnam 
On 9/17/2020 11:40 AM, Mark Sapiro wrote:
>
> What makes you think messages aren't being archived?
Because when I look at it via the web, the emails I sent as a test are
not there. There is no September 2020 link and the date on the mbox file
is old (Feb 2020).
>
> Is your archive public? If so, is
> /var/lib/mailman/archives/public/ a symlink to
> /var/lib/mailman/archives/private/, or is it an entire archive
> structure. The latter can occur in some backup-restore scenarios and
> results in a public (pipermail URL) archive that is never updated
> because only/var/lib/mailman/archives/private/ is actually
> updated.
There are no sym links. Private looks like just place holders as there
is no data there nor any archives. It looks like everything is in
public. The ownership is root:mailman and the group has R/O permissions.
Only root has write. I'm assuming that is correct, otherwise check_perms
would fix it.
>
> /var/lib/mailman/archives/public/ must be a symlink to
> /var/lib/mailman/archives/private/. If that's the issue, you
> can fix it manually, or I think just setting Archiving Options ->
> archive_private to private and then back to public in the web admin UI
> will fix it.
Looks like it is backwards. This must be the problem but how it got this
way I have no clue. Since the real data is in public, doing either would
mess it up, right?
>
> Eailier I asked "Is
> /var/lib/mailman/archives/private/.mbox/.mbox being
> updated?" and you answered "No. Those files are owned by
> mailman:mailman." which doesn't answer the question.
The no applied to your question. I included the other information in
case it you asked.
>
> Are new messages being appended to the
> /var/lib/mailman/archives/private/.mbox/.mbox files?
No




signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Archive Issue

2020-09-17 Thread Mark Sapiro 
On 9/17/20 7:56 AM, Dennis Putnam wrote:
> On 9/17/2020 10:43 AM, Mark Sapiro wrote:
>>
>> Is ArchRunner running? Are there entries in /var/spool/mailman/archive/?
> Looks like it:



What makes you think messages aren't being archived?

Is your archive public? If so, is
/var/lib/mailman/archives/public/ a symlink to
/var/lib/mailman/archives/private/, or is it an entire archive
structure. The latter can occur in some backup-restore scenarios and
results in a public (pipermail URL) archive that is never updated
because only/var/lib/mailman/archives/private/ is actually
updated.

/var/lib/mailman/archives/public/ must be a symlink to
/var/lib/mailman/archives/private/. If that's the issue, you
can fix it manually, or I think just setting Archiving Options ->
archive_private to private and then back to public in the web admin UI
will fix it.

Eailier I asked "Is
/var/lib/mailman/archives/private/.mbox/.mbox being
updated?" and you answered "No. Those files are owned by
mailman:mailman." which doesn't answer the question.

Are new messages being appended to the
/var/lib/mailman/archives/private/.mbox/.mbox files?

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Archive Issue

2020-09-17 Thread Dennis Putnam 
On 9/17/2020 10:43 AM, Mark Sapiro wrote:
>
> Is ArchRunner running? Are there entries in /var/spool/mailman/archive/?
Looks like it:

● mailman.service - GNU Mailing List Manager
   Loaded: loaded (/usr/lib/systemd/system/mailman.service; disabled;
vendor preset: disabled)
   Active: active (running) since Thu 2020-09-17 07:39:59 MDT; 1h 10min ago
  Process: 28178 ExecStart=/usr/lib/mailman/bin/mailmanctl -s start
(code=exited, status=0/SUCCESS)
  Process: 28175 ExecStartPre=/bin/chmod 660 /var/log/mailman/error
(code=exited, status=0/SUCCESS)
  Process: 28172 ExecStartPre=/bin/chown mailman:mailman
/var/log/mailman/error (code=exited, status=0/SUCCESS)
  Process: 28169 ExecStartPre=/bin/touch /var/log/mailman/error
(code=exited, status=0/SUCCESS)
  Process: 28165 ExecStartPre=/usr/bin/install -m644 -o root -g root
/usr/lib/mailman/cron/crontab.in /etc/cron.d/mailman (code=exited,
status=0/SUCCESS)
  Process: 28162 ExecStartPre=/usr/lib/mailman/bin/mailman-update-cfg
(code=exited, status=0/SUCCESS)
 Main PID: 28180 (mailmanctl)
    Tasks: 9
   CGroup: /system.slice/mailman.service
   ├─28180 /bin/python /usr/lib/mailman/bin/mailmanctl -s start
   ├─28189 /bin/python /usr/lib/mailman/bin/qrunner
--runner=ArchRunner:0:1 -s
   ├─28190 /bin/python /usr/lib/mailman/bin/qrunner
--runner=BounceRunner:0:1 -s
   ├─28191 /bin/python /usr/lib/mailman/bin/qrunner
--runner=CommandRunner:0:1 -s
   ├─28192 /bin/python /usr/lib/mailman/bin/qrunner
--runner=IncomingRunner:0:1 -s
   ├─28193 /bin/python /usr/lib/mailman/bin/qrunner
--runner=NewsRunner:0:1 -s
   ├─28194 /bin/python /usr/lib/mailman/bin/qrunner
--runner=OutgoingRunner:0:1 -s
   ├─28195 /bin/python /usr/lib/mailman/bin/qrunner
--runner=VirginRunner:0:1 -s
   └─28196 /bin/python /usr/lib/mailman/bin/qrunner
--runner=RetryRunner:0:1 -s

Sep 17 07:39:59 harmonia.csd.net systemd[1]: Starting GNU Mailing List
Manager...
Sep 17 07:39:59 harmonia.csd.net mailmanctl[28178]: Starting Mailman's
master qrunner.
Sep 17 07:39:59 harmonia.csd.net systemd[1]: Started GNU Mailing List
Manager.

>
> This looks OK. The ownership is irrelevant as long as the group is
> 'mailman' and /var/log/mailman/ itself is group mailman and SETGID.
> (Those owned by apache were created by a web action.)
>
> I'm assuming that the 'error' log has nothing relevant, but it is being
> written so no archiving exceptions have been logged which makes me think
> ArchRunner isn't running. What's in the 'qrunner' log?
>
Error doesn't have anything recent. As for the qrunner log, I don't see
anything interesting (just my restart of MM):

Sep 17 07:39:41 2020 (21351) VirginRunner qrunner caught SIGTERM.  Stopping.
Sep 17 07:39:41 2020 (21351) VirginRunner qrunner exiting.
Sep 17 07:39:41 2020 (21350) OutgoingRunner qrunner caught SIGTERM. 
Stopping.
Sep 17 07:39:41 2020 (21349) NewsRunner qrunner caught SIGTERM.  Stopping.
Sep 17 07:39:41 2020 (21349) NewsRunner qrunner exiting.
Sep 17 07:39:41 2020 (21350) OutgoingRunner qrunner exiting.
Sep 17 07:39:41 2020 (21346) BounceRunner qrunner caught SIGTERM.  Stopping.
Sep 17 07:39:41 2020 (21346) BounceRunner qrunner exiting.
Sep 17 07:39:41 2020 (21348) IncomingRunner qrunner caught SIGTERM. 
Stopping.
Sep 17 07:39:41 2020 (21348) IncomingRunner qrunner exiting.
Sep 17 07:39:41 2020 (21345) ArchRunner qrunner caught SIGTERM.  Stopping.
Sep 17 07:39:41 2020 (21345) ArchRunner qrunner exiting.
Sep 17 07:39:41 2020 (21336) Master watcher caught SIGTERM.  Exiting.
Sep 17 07:39:41 2020 (21347) CommandRunner qrunner caught SIGTERM. 
Stopping.
Sep 17 07:39:41 2020 (21347) CommandRunner qrunner exiting.
Sep 17 07:39:41 2020 (21352) RetryRunner qrunner caught SIGTERM.  Stopping.
Sep 17 07:39:41 2020 (21352) RetryRunner qrunner exiting.
Sep 17 07:39:41 2020 (21336) Master qrunner detected subprocess exit
(pid: 21346, sig: None, sts: 15, class: BounceRunner, slice: 1/1)
Sep 17 07:39:41 2020 (21336) Master qrunner detected subprocess exit
(pid: 21351, sig: None, sts: 15, class: VirginRunner, slice: 1/1)
Sep 17 07:39:41 2020 (21336) Master watcher caught SIGTERM.  Exiting.
Sep 17 07:39:41 2020 (21336) Master qrunner detected subprocess exit
(pid: 21349, sig: 15, sts: None, class: NewsRunner, slice: 1/1)
Sep 17 07:39:41 2020 (21336) Master qrunner detected subprocess exit
(pid: 21350, sig: 15, sts: None, class: OutgoingRunner, slice: 1/1)
Sep 17 07:39:41 2020 (21336) Master qrunner detected subprocess exit
(pid: 21352, sig: 15, sts: None, class: RetryRunner, slice: 1/1)
Sep 17 07:39:41 2020 (21336) Master qrunner detected subprocess exit
(pid: 21347, sig: 15, sts: None, class: CommandRunner, slice: 1/1)
Sep 17 07:39:41 2020 (21336) Master qrunner detected subprocess exit
(pid: 21345, sig: 15, sts: None, class: ArchRunner, slice: 1/1)
Sep 17 07:39:41 2020 (21336) Master qrunner detected subprocess exit
(pid: 21348, sig: 15, sts: None, class: IncomingRunner, slice: 1/1)
Sep 17 07:40:00 2020 (28189) Arc

[Mailman-Users] Re: Archive Issue

2020-09-17 Thread Mark Sapiro 
On 9/17/20 7:24 AM, Dennis Putnam wrote:
> On 9/17/2020 9:59 AM, Mark Sapiro wrote:
>> On 9/17/20 6:49 AM, Dennis Putnam wrote:
>>> For some reason, messages are not being archived. I see no error in the
>>> logs and check_perms says no problems found. Any suggestions on how to
>>> get archive working? Thanks.
>>
>> Is /var/lib/mailman/archives/private/.mbox/.mbox
>> being updated?
> No. Those files are owned by mailman:mailman.


Is ArchRunner running? Are there entries in /var/spool/mailman/archive/?


>> Are any logs being written? What are mode and user:group on
>> /var/log/mailman/?
> Yes, some logs are being written but most of the files are old and
> empty. The files for today are the test emails I sent. The ownership of
> log files varies:
> 
> -rw-rw-r--. 1 mailman mailman 0 Sep 13 19:13 bounce
> -rw-rw-r--. 1 mailman mailman 0 Aug 16 03:43 bounce-20200823
> -rw-rw-r--. 1 mailman mailman 0 Aug 23 03:40 bounce-20200830
> -rw-rw-r--. 1 mailman mailman 0 Aug 30 03:13 bounce-20200906
> -rw-rw-r--. 1 mailman mailman 0 Sep  6 03:33 bounce-20200913
> -rw-rw. 1 mailman mailman   275 Sep 17 07:39 error
> -rw-rw. 1 mailman mailman 0 Aug 16 03:43 error-20200823
> -rw-rw. 1 mailman mailman 0 Aug 23 03:40 error-20200830
> -rw-rw. 1 mailman mailman   692 Sep  5 07:15 error-20200906
> -rw-rw. 1 mailman mailman 0 Sep  6 03:33 error-20200913
> -rw-rw-r--. 1 apache  mailman   639 Sep  5 07:15 mischief
> -rw-rw-r--. 1 mailman mailman   409 Sep 17 07:50 post
> -rw-rw-r--. 1 mailman mailman 10939 Aug 22 23:23 post-20200823
> -rw-rw-r--. 1 mailman mailman  2546 Aug 29 20:39 post-20200830
> -rw-rw-r--. 1 mailman mailman  6108 Sep  5 10:29 post-20200906
> -rw-rw-r--. 1 mailman mailman  5840 Sep 12 18:00 post-20200913
> -rw-rw-r--. 1 mailman mailman  6048 Sep 17 07:40 qrunner
> -rw-rw-r--. 1 mailman mailman   738 Aug 16 03:43 qrunner-20200823
> -rw-rw-r--. 1 mailman mailman   738 Aug 23 03:40 qrunner-20200830
> -rw-rw-r--. 1 mailman mailman   738 Aug 30 03:13 qrunner-20200906
> -rw-rw-r--. 1 mailman mailman   738 Sep  6 03:33 qrunner-20200913
> -rw-rw-r--. 1 mailman mailman   284 Sep 17 07:50 smtp
> -rw-rw-r--. 1 mailman mailman  8875 Aug 22 23:23 smtp-20200823
> -rw-rw-r--. 1 mailman mailman  1804 Aug 29 20:39 smtp-20200830
> -rw-rw-r--. 1 mailman mailman  4854 Sep  5 10:29 smtp-20200906
> -rw-rw-r--. 1 mailman mailman  4715 Sep 12 18:00 smtp-20200913
> -rw-rw-r--. 1 mailman mailman 0 Sep 13 19:13 smtp-failure
> -rw-rw-r--. 1 mailman mailman 0 Aug 16 03:43 smtp-failure-20200823
> -rw-rw-r--. 1 mailman mailman 0 Aug 23 03:40 smtp-failure-20200830
> -rw-rw-r--. 1 mailman mailman 0 Aug 30 03:13 smtp-failure-20200906
> -rw-rw-r--. 1 mailman mailman 0 Sep  6 03:33 smtp-failure-20200913
> -rw-rw-r--. 1 apache  mailman 0 Sep 13 19:13 subscribe
> -rw-rw-r--. 1 apache  mailman 0 Aug 16 03:43 subscribe-20200823
> -rw-rw-r--. 1 apache  mailman 0 Aug 23 03:40 subscribe-20200830
> -rw-rw-r--. 1 apache  mailman 0 Aug 30 03:13 subscribe-20200906
> -rw-rw-r--. 1 apache  mailman 0 Sep  6 03:33 subscribe-20200913
> -rw-rw-r--. 1 mailman mailman 0 Sep 13 19:13 vette
> -rw-rw-r--. 1 mailman mailman 0 Aug 16 03:43 vette-20200823
> -rw-rw-r--. 1 mailman mailman 0 Aug 23 03:40 vette-20200830
> -rw-rw-r--. 1 mailman mailman 0 Aug 30 03:13 vette-20200906
> -rw-rw-r--. 1 mailman mailman 0 Sep  6 03:33 vette-20200913


This looks OK. The ownership is irrelevant as long as the group is
'mailman' and /var/log/mailman/ itself is group mailman and SETGID.
(Those owned by apache were created by a web action.)

I'm assuming that the 'error' log has nothing relevant, but it is being
written so no archiving exceptions have been logged which makes me think
ArchRunner isn't running. What's in the 'qrunner' log?

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Archive Issue

2020-09-17 Thread Dennis Putnam 
On 9/17/2020 9:59 AM, Mark Sapiro wrote:
> On 9/17/20 6:49 AM, Dennis Putnam wrote:
>> For some reason, messages are not being archived. I see no error in the
>> logs and check_perms says no problems found. Any suggestions on how to
>> get archive working? Thanks.
>
> Is /var/lib/mailman/archives/private/.mbox/.mbox
> being updated?
No. Those files are owned by mailman:mailman.
>
> Are any logs being written? What are mode and user:group on
> /var/log/mailman/?
Yes, some logs are being written but most of the files are old and
empty. The files for today are the test emails I sent. The ownership of
log files varies:

-rw-rw-r--. 1 mailman mailman 0 Sep 13 19:13 bounce
-rw-rw-r--. 1 mailman mailman 0 Aug 16 03:43 bounce-20200823
-rw-rw-r--. 1 mailman mailman 0 Aug 23 03:40 bounce-20200830
-rw-rw-r--. 1 mailman mailman 0 Aug 30 03:13 bounce-20200906
-rw-rw-r--. 1 mailman mailman 0 Sep  6 03:33 bounce-20200913
-rw-rw. 1 mailman mailman   275 Sep 17 07:39 error
-rw-rw. 1 mailman mailman 0 Aug 16 03:43 error-20200823
-rw-rw. 1 mailman mailman 0 Aug 23 03:40 error-20200830
-rw-rw. 1 mailman mailman   692 Sep  5 07:15 error-20200906
-rw-rw. 1 mailman mailman 0 Sep  6 03:33 error-20200913
-rw-rw-r--. 1 apache  mailman   639 Sep  5 07:15 mischief
-rw-rw-r--. 1 mailman mailman   409 Sep 17 07:50 post
-rw-rw-r--. 1 mailman mailman 10939 Aug 22 23:23 post-20200823
-rw-rw-r--. 1 mailman mailman  2546 Aug 29 20:39 post-20200830
-rw-rw-r--. 1 mailman mailman  6108 Sep  5 10:29 post-20200906
-rw-rw-r--. 1 mailman mailman  5840 Sep 12 18:00 post-20200913
-rw-rw-r--. 1 mailman mailman  6048 Sep 17 07:40 qrunner
-rw-rw-r--. 1 mailman mailman   738 Aug 16 03:43 qrunner-20200823
-rw-rw-r--. 1 mailman mailman   738 Aug 23 03:40 qrunner-20200830
-rw-rw-r--. 1 mailman mailman   738 Aug 30 03:13 qrunner-20200906
-rw-rw-r--. 1 mailman mailman   738 Sep  6 03:33 qrunner-20200913
-rw-rw-r--. 1 mailman mailman   284 Sep 17 07:50 smtp
-rw-rw-r--. 1 mailman mailman  8875 Aug 22 23:23 smtp-20200823
-rw-rw-r--. 1 mailman mailman  1804 Aug 29 20:39 smtp-20200830
-rw-rw-r--. 1 mailman mailman  4854 Sep  5 10:29 smtp-20200906
-rw-rw-r--. 1 mailman mailman  4715 Sep 12 18:00 smtp-20200913
-rw-rw-r--. 1 mailman mailman 0 Sep 13 19:13 smtp-failure
-rw-rw-r--. 1 mailman mailman 0 Aug 16 03:43 smtp-failure-20200823
-rw-rw-r--. 1 mailman mailman 0 Aug 23 03:40 smtp-failure-20200830
-rw-rw-r--. 1 mailman mailman 0 Aug 30 03:13 smtp-failure-20200906
-rw-rw-r--. 1 mailman mailman 0 Sep  6 03:33 smtp-failure-20200913
-rw-rw-r--. 1 apache  mailman 0 Sep 13 19:13 subscribe
-rw-rw-r--. 1 apache  mailman 0 Aug 16 03:43 subscribe-20200823
-rw-rw-r--. 1 apache  mailman 0 Aug 23 03:40 subscribe-20200830
-rw-rw-r--. 1 apache  mailman 0 Aug 30 03:13 subscribe-20200906
-rw-rw-r--. 1 apache  mailman 0 Sep  6 03:33 subscribe-20200913
-rw-rw-r--. 1 mailman mailman 0 Sep 13 19:13 vette
-rw-rw-r--. 1 mailman mailman 0 Aug 16 03:43 vette-20200823
-rw-rw-r--. 1 mailman mailman 0 Aug 23 03:40 vette-20200830
-rw-rw-r--. 1 mailman mailman 0 Aug 30 03:13 vette-20200906
-rw-rw-r--. 1 mailman mailman 0 Sep  6 03:33 vette-20200913





signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/

[Mailman-Users] Re: Archive Issue

2020-09-17 Thread Mark Sapiro 
On 9/17/20 6:49 AM, Dennis Putnam wrote:
> For some reason, messages are not being archived. I see no error in the
> logs and check_perms says no problems found. Any suggestions on how to
> get archive working? Thanks.


Is /var/lib/mailman/archives/private/.mbox/.mbox
being updated?

Are any logs being written? What are mode and user:group on
/var/log/mailman/?

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list -- mailman-users@python.org
To unsubscribe send an email to mailman-users-le...@python.org
https://mail.python.org/mailman3/lists/mailman-users.python.org/
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/
https://mail.python.org/archives/list/mailman-users@python.org/