[Mailman-Users] searchable archive

[Laack, Andrea P. via Mailman-Users]

I am setting up a Mailman 2 instance and am looking for a searchable archiver.  
Is there anything available for Mailman 2 that provides searching?

Andrea

Andrea Laack
Research & Tech Innov Svcs
Mayo Clinic
507-538-3831
laack.and...@mayo.edu

--
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/
Member address: arch...@jab.org

[Mailman-Users] Re: archive

[Mark Sapiro]

On 12/4/23 14:34, Laack, Andrea P. via Mailman-Users wrote:

I am attempting to read in majordomo archives into mailman 2 using /bin/arch.  
We are currently running a nightly archive which nightly moves list-archive to 
a mmmdd file.  Now I need to put these into one file to run /bin/arch in 
mailman to read them all in.  My question is, is it necessary to put the emails 
in date order in the list-archive file for mailman arch to read in, or will the 
arch script sort out the dates?



I do not understand mmmdd. Do you mean mmdf? In any case, the input to 
bin/arch does not need to be in date order. Messages will be added to 
the pipermail archive according to their Date: headers regardless of 
input order.


That said, bin/arch expects the input in mbox format. If you are going 
to provide it in mbox format, you should first run bin/cleanarch to 
verify there are no unescaped 'From ' lines in message bodies.


--
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/
Member address: arch...@jab.org

[Mailman-Users] MM2: Archive search function for a private list?

[Jayson Smith]

Hi,


I run a list for members of an organization. Recently I was asked by a 
member if the archives had a search function. With MM2 they don't, I 
know. This is a private list, so I don't want it publicly searchable. 
Does anyone know of a web application that can be deployed on a Linux 
server which will go through a list's archives, generate a searchable 
index, and allow members (possibly using their mailing list Email and 
password, or maybe something else) to access it?



Thanks,


Jayson


--
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?

[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?

[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?

[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] Removed archive messages won't die

[Thomas Gramstad]

I'm trying to get rid of some test messages, unsubscribe 
messages, and a misdirected personal message from a public list 
archive (Mailman 2.1.29).


The problem is that the archived messages keep resurrecting 
themselves in the date.html file, even if the actual message 
files have been deleted, after I edit them away from the 
date.html file.


How can I prevent this behavior, so that only actually existing 
archive messages show up in the archive index file date.html?


--
Thomas Gramstad
tho...@gramstad.no
--
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

[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

[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

[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

[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

[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

[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

[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

[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: 

[Mailman-Users] Re: Archive Issue

[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

[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

[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

[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

[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

[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) 

[Mailman-Users] Re: Archive Issue

[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

[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

[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/

Re: [Mailman-Users] No archive files but 2 lists taking up 50MB in cPanel?

[Stephen J. Turnbull]

Tom Corcoran writes:
 >  Wow! Thanks, Steve!
 > 
 > My mention of pdf here, crossed over with my other post and
 > confused, sorry.

Not a problem.  I'm still a little worried about your settings,
though.  The question is, "Do you want to receive those PDFs?"  If
"application/pdf" is not in pass_these_mime_types, they will get
discarded.

 > With content_filtering turned on now hopefully no more attachments
 > accumulate.,

Correct.

 > collapse_alternatives
 > convert_html_to_plaintext
 > 
 > defaulted to Yes, so I turned them off.

This is safe to do.

--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] No archive files but 2 lists taking up 50MB in cPanel?

[Mark Sapiro]

On 10/14/19 3:43 AM, Tom Corcoran wrote:
> 
> 1. I looked at "Scrub attachments of the regular delivery message?
> (Details for scrub_nondigest)" which opens in a new window it's set to no
> already!2. In content filtering, I turned it on and changed nothing else.


If scrub_nondigest is No, attachments will Not be stored aside in the
archive and replaced by a link in the message. This is exactly what you
want.

Content filtering may be used to remove unwanted attachments, but with
scrub_nondigest off, attachments won't be stored aside anyway so it
won't affect the storage of things in the archive.

-- 
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
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/archive%40jab.org

Re: [Mailman-Users] No archive files but 2 lists taking up 50MB in cPanel?

[Tom Corcoran]

 Wow! Thanks, Steve!

My mention of pdf here, crossed over with my other post and confused,
sorry.

With content_filtering turned on now hopefully no more attachments
accumulate.,

collapse_alternatives
convert_html_to_plaintext

defaulted to Yes, so I turned them off.

Done and tested :-)


Cheers,

Tom.


On Mon, 14 Oct 2019 at 14:28, Stephen J. Turnbull <
turnbull.stephen...@u.tsukuba.ac.jp> wrote:

> Tom Corcoran writes:
>
>  > All emails that come in I want to forward to our 2 addresses with no
>  > archive so as far, as I am concerned ongoing admin having to accept
>  > messages from new addresses, is overkill and I would avoid doing it and
>  > accept all messages if that was possible. Also, sometimes some of the
>  > sports clubs for my kids attach a pdf.
>
> I would then add
>
> text/html
> application/pdf
>
> to pass_these_mime_types in the Content Filtering page.  The first
> allows HTML-only mail to come in, and since this is really personal
> mail I don't see a good reason to disallow HTML.  The second prevents
> the PDF from being discarded.  If you strongly *prefer* plain text to
> HTML-formatted email, you could set both of
>
> collapse_alternatives
> convert_html_to_plaintext
>
> to Yes in the same page.
>
> Steve
>
> --
> Mailman-Users mailing list Mailman-Users@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/boardtc%40gmail.com
>
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] No archive files but 2 lists taking up 50MB in cPanel?

[Stephen J. Turnbull]

Tom Corcoran writes:

 > All emails that come in I want to forward to our 2 addresses with no
 > archive so as far, as I am concerned ongoing admin having to accept
 > messages from new addresses, is overkill and I would avoid doing it and
 > accept all messages if that was possible. Also, sometimes some of the
 > sports clubs for my kids attach a pdf.

I would then add

text/html
application/pdf

to pass_these_mime_types in the Content Filtering page.  The first
allows HTML-only mail to come in, and since this is really personal
mail I don't see a good reason to disallow HTML.  The second prevents
the PDF from being discarded.  If you strongly *prefer* plain text to
HTML-formatted email, you could set both of

collapse_alternatives
convert_html_to_plaintext

to Yes in the same page.

Steve

--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] No archive files but 2 lists taking up 50MB in cPanel?

[Tom Corcoran]

Thanks, Brian & Steve!

I feel some context would be useful. I solely use mailing lists so both
myself and my wife can get emails from schools, sports clubs, bills, etc.

All emails that come in I want to forward to our 2 addresses with no
archive so as far, as I am concerned ongoing admin having to accept
messages from new addresses, is overkill and I would avoid doing it and
accept all messages if that was possible. Also, sometimes some of the
sports clubs for my kids attach a pdf.

I have only edited the bare minimum of the mailman settings.

1. I looked at "Scrub attachments of the regular delivery message?
(Details for scrub_nondigest)" which opens in a new window it's set to no
already!2. In content filtering, I turned it on and changed nothing else.

Hopefully, #2 means that attachments will now not be archived and I can
achieve my goal of zero build-up of any storage with messages passing
through?

I guess I'll have to wait and see if anything accumulates!

Thanks a million, Tom.

[for some reason this post of 7+ days ago, never appeared on the list, I
may have used the wrong from email]

>
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] No archive files but 2 lists taking up 50MB in cPanel?

[Stephen J. Turnbull]

Tom Corcoran writes:

 > *But*, the mystery for me is if archives are turned off how are the
 > attachments saved. Is there another setting? If not, surely one
 > should be added so this unnecessary support request is not needed?

Mailman has a facility for saving attachments so that (1) space usage
on multiuser systems can be reduced and (2) users have to take
explicit action to retrieve "dangerous" file types (.exe, for
example).  This feature is controlled by the "Nondigest options" ->
"Scrub Nondigest" option.  (I don't know how this affects digests; I
suppose it controls them too but this is undocumented AFAICS.)

If you want them discarded "with extreme prejudice", then I believe
this option should be set to "No" (which is counterintuitive, I guess)
and use the "Content Filtering" options to either remove and discard
content types you don't want, or pass only those types you do want,
and discard the rest.

Steve

--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] No archive files but 2 lists taking up 50MB in cPanel?

[Brian Carpenter]

On 10/3/19 1:21 PM, Tom Corcoran wrote:

Thanks Brian!

That's great to have that confirmed :-)

*But*, the mystery for me is if archives are turned off how are the
attachments saved. Is there another setting? If not, surely one should be
added so this unnecessary support request is not needed?

I may have done my isp a disservice. I had a separate request (no resolved)
re mailman auto discarding and I think that was the one the were pointing
me elsewhere for.


On Thu, 3 Oct 2019 at 18:09, Brian Carpenter  wrote:


Hi Tom,

I have provided Mailman hosting via cPanel for many years now. I
apologize for not responding earlier to your request. I know exactly
what is taking up that space: attachments. Mailman takes message
attachments and stores them in an attachment directory that is part of
the Mailman file structure. This directory cannot be access via a normal
cPanel user. It requires root access. We have clients who from time to
time ask us to reduce their disk usage by clearing out their attachment
directory which we are happy to do.

Personally I would like invite you to check us out at https://emwd.com
as I think your host did you wrong when they said they would not support
a 3rd party. If they are a cPanel host then Mailman is part of cPanel
and therefore should be supported.

Attachments still accumulate even with archiving turned off. I believe 
you have to enable content filtering to filter them out.


Your host still should have purged those attachments for you.

--
Please let me know if you need further assistance.

Thank you for your business. We appreciate our clients.
Brian Carpenter
EMWD.com

--
EMWD's Knowledgebase:
https://clientarea.emwd.com/index.php/knowledgebase

EMWD's Community Forums
http://discourse.emwd.com/

--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] No archive files but 2 lists taking up 50MB in cPanel?

[Tom Corcoran]

Thanks Brian!

That's great to have that confirmed :-)

*But*, the mystery for me is if archives are turned off how are the
attachments saved. Is there another setting? If not, surely one should be
added so this unnecessary support request is not needed?

I may have done my isp a disservice. I had a separate request (no resolved)
re mailman auto discarding and I think that was the one the were pointing
me elsewhere for.


On Thu, 3 Oct 2019 at 18:09, Brian Carpenter  wrote:

> Hi Tom,
>
> I have provided Mailman hosting via cPanel for many years now. I
> apologize for not responding earlier to your request. I know exactly
> what is taking up that space: attachments. Mailman takes message
> attachments and stores them in an attachment directory that is part of
> the Mailman file structure. This directory cannot be access via a normal
> cPanel user. It requires root access. We have clients who from time to
> time ask us to reduce their disk usage by clearing out their attachment
> directory which we are happy to do.
>
> Personally I would like invite you to check us out at https://emwd.com
> as I think your host did you wrong when they said they would not support
> a 3rd party. If they are a cPanel host then Mailman is part of cPanel
> and therefore should be supported.
>
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] No archive files but 2 lists taking up 50MB in cPanel?

[Brian Carpenter]

On 10/3/19 12:07 PM, Bryan Teague wrote:

Tom,

It isn’t that Mark is being unhelpful, it is that cpanel doess some … odd 
things with the packages that they bring into their ecosystem.  Most of the 
people on the mailman list are system admins, or at the very least, people who 
have command line access to the servers that run their mailman installations.

When I was running mailman lists through cPanel,  I found the cpanel forums to 
be  a great help, along with the documentation and information found on the 
support site for cpanel.  (Both of those links are contained in the second 
paragraph of the page for your convenience I included them here)

http://forums.cpanel.net/ <http://forums.cpanel.net/>

http://support.cpanel.net/ <http://support.cpanel.net/>

As to your specific problem of the private archives this is what I found when I 
looked at one of my cpanel installations:

https://documentation.cpanel.net/display/82Docs/Mailing+Lists
https://documentation.cpanel.net/display/82Docs/Archive

Hope this helps to clarify the issues for you.

Bryan Teague
Senior Web Administrator,
Library and Web Services
Information Technology Services
Maher Hall 196
5998 Alcalá Park
San Diego, CA 92110-2492
Work: 619.260.7842
Cell: 619.321.7288
bry...@sandiego.edu‌


On Oct 3, 2019, at 8:47 AM, Tom Corcoran  wrote:

I came to this group as my isp said they would not support a 3rd party.

I'm confused, Mark. I printed out the link you sent me but I was
dumbfounded when I read through it now that there was nothing about
clearing out the 50MB and an unhelpful page more or less telling people to
leave the group alone :-(

Would someone on this group willing to try and help me retrieve my precious
50MB?

Thanks!

On Tue, 1 Oct 2019 at 19:30, Mark Sapiro  wrote:


On 10/1/19 8:17 AM, Tom Corcoran wrote:

I don't have command line access to my cPanel - just FileManager.

How do I find out what these 50+MB are being used for and how do  I

recover

the 50+MB?

See the FAQ at <https://wiki.list.org/DOC/Mailman%20and%20CPanel>.



Hi Tom,

I have provided Mailman hosting via cPanel for many years now. I 
apologize for not responding earlier to your request. I know exactly 
what is taking up that space: attachments. Mailman takes message 
attachments and stores them in an attachment directory that is part of 
the Mailman file structure. This directory cannot be access via a normal 
cPanel user. It requires root access. We have clients who from time to 
time ask us to reduce their disk usage by clearing out their attachment 
directory which we are happy to do.


Personally I would like invite you to check us out at https://emwd.com 
as I think your host did you wrong when they said they would not support 
a 3rd party. If they are a cPanel host then Mailman is part of cPanel 
and therefore should be supported.


--
Please let me know if you need further assistance.

Thank you for your business. We appreciate our clients.
Brian Carpenter
EMWD.com

--
EMWD's Knowledgebase:
https://clientarea.emwd.com/index.php/knowledgebase

EMWD's Community Forums
http://discourse.emwd.com/

--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] No archive files but 2 lists taking up 50MB in cPanel?

[Bryan Teague]

Tom, 

It isn’t that Mark is being unhelpful, it is that cpanel doess some … odd 
things with the packages that they bring into their ecosystem.  Most of the 
people on the mailman list are system admins, or at the very least, people who 
have command line access to the servers that run their mailman installations. 

When I was running mailman lists through cPanel,  I found the cpanel forums to 
be  a great help, along with the documentation and information found on the 
support site for cpanel.  (Both of those links are contained in the second 
paragraph of the page for your convenience I included them here) 

http://forums.cpanel.net/ <http://forums.cpanel.net/>

http://support.cpanel.net/ <http://support.cpanel.net/>

As to your specific problem of the private archives this is what I found when I 
looked at one of my cpanel installations: 

https://documentation.cpanel.net/display/82Docs/Mailing+Lists
https://documentation.cpanel.net/display/82Docs/Archive

Hope this helps to clarify the issues for you.  

Bryan Teague
Senior Web Administrator, 
Library and Web Services
Information Technology Services
Maher Hall 196
5998 Alcalá Park
San Diego, CA 92110-2492
Work: 619.260.7842
Cell: 619.321.7288
bry...@sandiego.edu‌

> On Oct 3, 2019, at 8:47 AM, Tom Corcoran  wrote:
> 
> I came to this group as my isp said they would not support a 3rd party.
> 
> I'm confused, Mark. I printed out the link you sent me but I was
> dumbfounded when I read through it now that there was nothing about
> clearing out the 50MB and an unhelpful page more or less telling people to
> leave the group alone :-(
> 
> Would someone on this group willing to try and help me retrieve my precious
> 50MB?
> 
> Thanks!
> 
> On Tue, 1 Oct 2019 at 19:30, Mark Sapiro  wrote:
> 
>> On 10/1/19 8:17 AM, Tom Corcoran wrote:
>>> 
>>> I don't have command line access to my cPanel - just FileManager.
>>> 
>>> How do I find out what these 50+MB are being used for and how do  I
>> recover
>>> the 50+MB?
>> 
>> See the FAQ at <https://wiki.list.org/DOC/Mailman%20and%20CPanel>.
>> 
> --
> Mailman-Users mailing list Mailman-Users@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/bryant%40sandiego.edu

--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] No archive files but 2 lists taking up 50MB in cPanel?

[Tom Corcoran]

 I came to this group as my isp said they would not support a 3rd party.

I'm confused, Mark. I printed out the link you sent me but I was
dumbfounded when I read through it now that there was nothing about
clearing out the 50MB and an unhelpful page more or less telling people to
leave the group alone :-(

Would someone on this group willing to try and help me retrieve my precious
50MB?

Thanks!

On Tue, 1 Oct 2019 at 19:30, Mark Sapiro  wrote:

> On 10/1/19 8:17 AM, Tom Corcoran wrote:
> >
> > I don't have command line access to my cPanel - just FileManager.
> >
> > How do I find out what these 50+MB are being used for and how do  I
> recover
> > the 50+MB?
>
> See the FAQ at <https://wiki.list.org/DOC/Mailman%20and%20CPanel>.
>
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] No archive files but 2 lists taking up 50MB in cPanel?

[Mark Sapiro]

On 10/1/19 8:17 AM, Tom Corcoran wrote:
> 
> I don't have command line access to my cPanel - just FileManager.
> 
> How do I find out what these 50+MB are being used for and how do  I recover
> the 50+MB?


See the FAQ at <https://wiki.list.org/DOC/Mailman%20and%20CPanel>.

This is a question only your hosting provider can answer.

-- 
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
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/archive%40jab.org

[Mailman-Users] No archive files but 2 lists taking up 50MB in cPanel?

[Tom Corcoran]

I have 3 lists, going to mailing list administration and clicking on Go to
list archives gives Private archive file not found for all.

But in cPanel mailing lists it says:

list 1 usage 14.98 MB
list 2 usage: 37.72 MB

list 3 has usage in KB, which is what I expect. All are I believe setup
identically

I don't have command line access to my cPanel - just FileManager.

How do I find out what these 50+MB are being used for and how do  I recover
the 50+MB?

Thanks!
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Suppressing Archive AND Digest Generation and collection

[Mark Sapiro]

On 06/14/2018 04:35 PM, Parker, Michael D. wrote:
> 
> How can the digest functionality be globally suppressed as well.


In a fashion similar to what you did for archiving, you can put

GLOBAL_PIPELINE.remove('ToDigest')

in mm_cfg.py. Archiving and digesting can also be disabled on a per-list
basis by setting the list's Archiving Options -> archive and/or Digest
options -> digestable settings to No.

-- 
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
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/archive%40jab.org

[Mailman-Users] Suppressing Archive AND Digest Generation and collection

[Parker, Michael D.]

I previously asked how to permanently and globally remove archives.

Based on a previous note, I added to my mm_cfg.py:
GLOBAL_PIPELINE.remove('ToArchive')

I assumed that the Digest file would be suppressed as well but I guess that is 
something different.
I note that a digest file is now created in /var/lib/mailman/lists/ 
for each note received to be reflected further.

How can the digest functionality be globally suppressed as well.

Thanks.


--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Private archive file not found

[david doonan]

Thanks Mark.

I ended up deleting and starting from scratch

On Tue, May 8, 2018 at 11:36 AM, Mark Sapiro <m...@msapiro.net> wrote:

> On 05/07/2018 08:58 AM, David Doonan wrote:
> >
> > Exploring the server via SFTP, this troublesome list only has one
> folder, with a sub-folder called attachments.
> >
> > The rest of the lists are set up correctly, with two folders, one with
> the name of the list and the second with the name of the list and .mbox as
> a suffix.
> >
> > The troublesome list is not new; it was created a decade or more ago.
> Can’t believe that no has complained about the lack of archives.
> >
> > Is there a solution other than to re-install?
>
> It is possible that something was somehow deleted or lost from the
> archive. If you have any older backups, you might look for them.
>
> If not, if you have shell access, rather than just SFTP, what you need
> to do is create the archives/private/LISTNAME.mbox directory and an
> empty archives/private/LISTNAME.mbox/LISTNAME.mbox file. These should
> have the same ownership and permissions as the ones for other lists, in
> particular drwxrwsr-x for the directory and -rw-rw-r-- for the file and
> mailman's group for both.
>
> Then run Mailman's
>
> bin/arch --wipe LISTNAME
>
> and that will create the (empty) archive.
>
> Alternatively, you can back up the lists/LISTNAME/ directory, containing
> the config.pck and other files. Then delete the list or just remove the
> lists/LISTNAME/ directory and then create the list and replace the
> lists/LISTNAME/ directory with the one you backed up. This should cerate
> the list with a "proper" empty archive and then restoring the
> lists/LISTNAME/ directory and contents will restore the list config and
> membership.
>
> --
> Mark Sapiro <m...@msapiro.net>The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> --
> Mailman-Users mailing list Mailman-Users@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/
> dadoonan%40gmail.com
>



-- 
David Doonan
3 Gray Avenue #2
Greenwich, New York 12834
518-265-4030
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Private archive file not found

[David Doonan]

ignore all.

ended up deleting and reinstalling

> On May 7, 2018, at 11:58 AM, David Doonan <dadoo...@mac.com> wrote:
> 
> I manage a couple of dozen mailman lists, all of which are functioning 
> correctly except for one.
> 
> When I go to the list archives, the following error message is displayed:
>> Private archive file not found
> 
> Tried changing the settings Archive Yes to No to Yes.
> 
> Tried changing the settings from Private to Public to Private.
> 
> Error message still appears.
> 
> Exploring the server via SFTP, this troublesome list only has one folder, 
> with a sub-folder called attachments.
> 
> The rest of the lists are set up correctly, with two folders, one with the 
> name of the list and the second with the name of the list and .mbox as a 
> suffix.
> 
> The troublesome list is not new; it was created a decade or more ago. Can’t 
> believe that no has complained about the lack of archives.
> 
> Is there a solution other than to re-install?
> 
> david
> 
> 
> 
> 
> 
> --
> Mailman-Users mailing list Mailman-Users@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/dadoonan%40mac.com

--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Private archive file not found

[Mark Sapiro]

On 05/07/2018 08:58 AM, David Doonan wrote:
> 
> Exploring the server via SFTP, this troublesome list only has one folder, 
> with a sub-folder called attachments.
> 
> The rest of the lists are set up correctly, with two folders, one with the 
> name of the list and the second with the name of the list and .mbox as a 
> suffix.
> 
> The troublesome list is not new; it was created a decade or more ago. Can’t 
> believe that no has complained about the lack of archives.
> 
> Is there a solution other than to re-install?

It is possible that something was somehow deleted or lost from the
archive. If you have any older backups, you might look for them.

If not, if you have shell access, rather than just SFTP, what you need
to do is create the archives/private/LISTNAME.mbox directory and an
empty archives/private/LISTNAME.mbox/LISTNAME.mbox file. These should
have the same ownership and permissions as the ones for other lists, in
particular drwxrwsr-x for the directory and -rw-rw-r-- for the file and
mailman's group for both.

Then run Mailman's

bin/arch --wipe LISTNAME

and that will create the (empty) archive.

Alternatively, you can back up the lists/LISTNAME/ directory, containing
the config.pck and other files. Then delete the list or just remove the
lists/LISTNAME/ directory and then create the list and replace the
lists/LISTNAME/ directory with the one you backed up. This should cerate
the list with a "proper" empty archive and then restoring the
lists/LISTNAME/ directory and contents will restore the list config and
membership.

-- 
Mark Sapiro <m...@msapiro.net>The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

[Mailman-Users] Private archive file not found

[David Doonan]

I manage a couple of dozen mailman lists, all of which are functioning 
correctly except for one.

When I go to the list archives, the following error message is displayed:
> Private archive file not found

Tried changing the settings Archive Yes to No to Yes.

Tried changing the settings from Private to Public to Private.

Error message still appears.

Exploring the server via SFTP, this troublesome list only has one folder, with 
a sub-folder called attachments.

The rest of the lists are set up correctly, with two folders, one with the name 
of the list and the second with the name of the list and .mbox as a suffix.

The troublesome list is not new; it was created a decade or more ago. Can’t 
believe that no has complained about the lack of archives.

Is there a solution other than to re-install?

david





--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Searchable archive for mailman mailing-lists?

[Lindsay Haisley]

On Wed, 2017-01-18 at 07:09 +1100, Mark Dale wrote:
> Hi Fernando
> 
> For installing the Namazu search on Mailman 2.1.*, there is a good "how
> to" (with a working example) at:
> 
> http://bakacsin.ki.iif.hu/~kissg/project/mailman+namazu/

Some years ago I developed a set of patches and instructions to
integrate namazu with Mailman 2.1, generally collected under the name
nmzproc. See:

http://linode.fmp.com/namazu/

This works well, and has been in use here on some lists for several
years, but there are probably easier ways to get this capability. Some
Mailman sites I host use have used off-site services such as 
mail-archive.com.

> We've had great success using the guide over the years. It might be
> worth noting that on a recent installation on Debian Stretch I did have
> to get the required Namazu packages from the Jessie repository.
> 
> Regards,
> Mark
> 
> 
> 
> 
> 
> On 17/01/17 18:21, Fernando Gont wrote:
> > 
> > Folks,
> > 
> > I was meaning to provide some option for searching our mailman
> > mailing
> > lists.
> > 
> > Two questions:
> > 
> > 1) Any open source recommendations for this?
> > 
> > 2) In the past, we were providing this feature by mirroring the
> > mailing-lists with google-groups, and thus using the googlegroups
> > interface for searching our lists. However, it seems such option is
> > gone
> > from googlegroups. Has anyone been able to do this recently?
> > 
> > Thanks!
> > 
> > Best regards,
> > 
> --
> Mailman-Users mailing list Mailman-Users@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%40pyth
> on.org/
> Unsubscribe: https://mail.python.org/mailman/options/mailman-users/fm
> ouse%40fmp.com
-- 
Lindsay Haisley   | "The first casualty when
FMP Computer Services | war comes is truth."
512-259-1190  |
http://www.fmp.com| -- Hiram W Johnson

--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Searchable archive for mailman mailing-lists?

[Mark Dale]

Hi Fernando

For installing the Namazu search on Mailman 2.1.*, there is a good "how
to" (with a working example) at:

http://bakacsin.ki.iif.hu/~kissg/project/mailman+namazu/

We've had great success using the guide over the years. It might be
worth noting that on a recent installation on Debian Stretch I did have
to get the required Namazu packages from the Jessie repository.

Regards,
Mark





On 17/01/17 18:21, Fernando Gont wrote:
> Folks,
> 
> I was meaning to provide some option for searching our mailman mailing
> lists.
> 
> Two questions:
> 
> 1) Any open source recommendations for this?
> 
> 2) In the past, we were providing this feature by mirroring the
> mailing-lists with google-groups, and thus using the googlegroups
> interface for searching our lists. However, it seems such option is gone
> from googlegroups. Has anyone been able to do this recently?
> 
> Thanks!
> 
> Best regards,
> 
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Searchable archive for mailman mailing-lists?

[Mark Sapiro]

On 01/16/2017 11:21 PM, Fernando Gont wrote:
> 
> I was meaning to provide some option for searching our mailman mailing
> lists.


For Mailman 2.1 see <https://wiki.list.org/x/4030514>.

The HyperKitty archiver for Mailman 3 has search capability built in.

-- 
Mark Sapiro <m...@msapiro.net>The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

[Mailman-Users] Searchable archive for mailman mailing-lists?

[Fernando Gont]

Folks,

I was meaning to provide some option for searching our mailman mailing
lists.

Two questions:

1) Any open source recommendations for this?

2) In the past, we were providing this feature by mirroring the
mailing-lists with google-groups, and thus using the googlegroups
interface for searching our lists. However, it seems such option is gone
from googlegroups. Has anyone been able to do this recently?

Thanks!

Best regards,
-- 
Fernando Gont
SI6 Networks
e-mail: fg...@si6networks.com
PGP Fingerprint:  31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492




--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Mailman archive creation problem

[Mark Sapiro]

On 09/20/2016 08:36 PM, Limperis Antonis wrote:

> Traceback (most recent call last):
>   File "/var/mailman/bin/arch", line 201, in 
> main()
>   File "/var/mailman/bin/arch", line 189, in main
> archiver.processUnixMailbox(fp, start, end)
>   File "/var/mailman/Mailman/Archiver/pipermail.py", line 596, in 
> processUnixMailbox
> self.add_article(a)
>   File "/var/mailman/Mailman/Archiver/pipermail.py", line 640, in add_article
> author = fixAuthor(article.decoded['author'])
>   File "/var/mailman/Mailman/Archiver/pipermail.py", line 63, in fixAuthor
> while i>0 and (L[i-1][0] in lowercase or
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xdc in position 26: 
> ordinal not in range(128)


Pipermail is trying to canonicalize the display name in the From: header
of a message into "Last, First" form and it is trying to see if the
initial character of a "word" in the name is in the string of lower case
characters for the locale. At this point, the name is a unicode and
Python is trying to decode the "lowercase" string to unicode for the
comparison. For some reason, the "lowercase" string appears to be
iso-8859-7, but the decoding is being done as if it were ascii.


> I  found that  the reconstruction works properly if set locale to el_GR.utf8 
> with " export LC_ALL=el_GR.utf8".
> The original system  locale environment was:
> 
> LANG=el_GR.ISO8859-7
> LC_CTYPE=el_GR.ISO8859-7
> LC_NUMERIC=el_GR.ISO8859-7
> LC_TIME=el_GR.ISO8859-7
> LC_COLLATE=el_GR.ISO8859-7
> LC_MONETARY=el_GR.ISO8859-7
> LC_MESSAGES=C
> LC_PAPER="el_GR.ISO8859-7"
> LC_NAME="el_GR.ISO8859-7"
> LC_ADDRESS="el_GR.ISO8859-7"
> LC_TELEPHONE="el_GR.ISO8859-7"
> LC_MEASUREMENT="el_GR.ISO8859-7"
> LC_IDENTIFICATION="el_GR.ISO8859-7"
> LC_ALL=


I'm guessing that Python is confused because most of the locale stuff is
"el_GR.ISO8859-7", but LC_ALL is not. In any case, it appears you have
solved the problem by "export LC_ALL=el_GR.utf8".

-- 
Mark Sapiro <m...@msapiro.net>The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Mailman archive creation problem

[Limperis Antonis]

Hello mark

This is the complete  trace:

[root@mailman ~]# /var/mailman/bin/arch --wipe testlist
#0 <002f01c4a17b$0e714490$c7eb3fc2@avgoulea>
Αρίθμηση άρθρων ιστορικών αρχείων
2004-September
#1 <24ba97b6f4c0e84999709c650c255c2e604...@amfithea.cti.gr>
Αρίθμηση άρθρων ιστορικών αρχείων
2004-September
Ανανέωση των αρχείων καταλόγου για το ιστορικό αρχείο [2004-September]
  Date
  Subject
  Author
  Ακολουθία μηνύματος
Γίνεται υπολογισμός των περιεχομένων
Ανανέωση της HTML για το άρθρο 0
Pickling archive state into /var/mailman/archives/private/testlist/pipermail.pck
Traceback (most recent call last):
  File "/var/mailman/bin/arch", line 201, in 
main()
  File "/var/mailman/bin/arch", line 189, in main
archiver.processUnixMailbox(fp, start, end)
  File "/var/mailman/Mailman/Archiver/pipermail.py", line 596, in 
processUnixMailbox
self.add_article(a)
  File "/var/mailman/Mailman/Archiver/pipermail.py", line 640, in add_article
author = fixAuthor(article.decoded['author'])
  File "/var/mailman/Mailman/Archiver/pipermail.py", line 63, in fixAuthor
while i>0 and (L[i-1][0] in lowercase or
UnicodeDecodeError: 'ascii' codec can't decode byte 0xdc in position 26: 
ordinal not in range(128)


I  found that  the reconstruction works properly if set locale to el_GR.utf8 
with " export LC_ALL=el_GR.utf8".
The original system  locale environment was:

LANG=el_GR.ISO8859-7
LC_CTYPE=el_GR.ISO8859-7
LC_NUMERIC=el_GR.ISO8859-7
LC_TIME=el_GR.ISO8859-7
LC_COLLATE=el_GR.ISO8859-7
LC_MONETARY=el_GR.ISO8859-7
LC_MESSAGES=C
LC_PAPER="el_GR.ISO8859-7"
LC_NAME="el_GR.ISO8859-7"
LC_ADDRESS="el_GR.ISO8859-7"
LC_TELEPHONE="el_GR.ISO8859-7"
LC_MEASUREMENT="el_GR.ISO8859-7"
LC_IDENTIFICATION="el_GR.ISO8859-7"
LC_ALL=

Thank you for your attention.
Antonis



-Original Message-
From: Mailman-Users [mailto:mailman-users-bounces+limperis=cti...@python.org] 
On Behalf Of Mark Sapiro
Sent: Friday, September 16, 2016 6:31 PM
To: mailman-users@python.org
Subject: Re: [Mailman-Users] Mailman archive creation problem

On 09/16/2016 02:58 AM, Limperis Antonis wrote:
> 
> Hello mailman users
> 
> We have a mailman version 2.1.22 installation.
> We try to reconstruct a mail  list archive with command 'arch --wipe 
> listname'  and receive the following error.
> 
> #0 <f60795d9b7521c478f6f9174a9183dc94279d...@mail.cti.gr>
> ÎÏίθμηÏη άÏθÏÏν ιÏÏ
> οÏικÏν αÏÏείÏν 


There seems to be some character encoding issue here, but ...


> 2013-February Pickling archive state into 
> /var/mailman/archives/private/tenders/pipermail.pck
> Traceback (most recent call last):
>   File "/var/mailman/bin/arch", line 201, in 
> main()
>   File "/var/mailman/bin/arch", line 189, in main
> archiver.processUnixMailbox(fp, start, end)
>   File "/var/mailman/Mailman/Archiver/pipermail.py", line 596, in 
> processUnixMailbox


This traceback is incomplete. Please post the complete traceback, and if
possible, the correct rendering of the

ÎÏίθμηÏη άÏθÏÏν ιÏÏ ...

stuff. Or is that perhaps some garbled rendering of

Αρίθμηση άρθρων ιστορικών αρχείων

Also, is other stuff missing. I.e., is there more between
"2013-February" and "Pickling archive state into ..."

Normally, I would expect three lines like

#nn 
figuring article archives
-Month

for each message in the mbox followed by something like

Updating index files for archive [-Month]
  Date
  Subject
  Author
  Thread
Computing threaded index
Updating HTML for article n1
Updating HTML for article n2
...

for each month in the archive and then finally, the

Pickling archive state into ...

line.

I really need the complete traceback to begin to say more.

-- 
Mark Sapiro <m...@msapiro.net>The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@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/limperis%40cti.gr
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Mailman archive creation problem

[Mark Sapiro]

On 09/16/2016 02:58 AM, Limperis Antonis wrote:
> 
> Hello mailman users
> 
> We have a mailman version 2.1.22 installation.
> We try to reconstruct a mail  list archive with command 'arch --wipe 
> listname'  and receive the following error.
> 
> #0 <f60795d9b7521c478f6f9174a9183dc94279d...@mail.cti.gr>
> ÎÏίθμηÏη άÏθÏÏν ιÏÏ
> οÏικÏν αÏÏείÏν 


There seems to be some character encoding issue here, but ...


> 2013-February Pickling archive state into 
> /var/mailman/archives/private/tenders/pipermail.pck
> Traceback (most recent call last):
>   File "/var/mailman/bin/arch", line 201, in 
> main()
>   File "/var/mailman/bin/arch", line 189, in main
> archiver.processUnixMailbox(fp, start, end)
>   File "/var/mailman/Mailman/Archiver/pipermail.py", line 596, in 
> processUnixMailbox


This traceback is incomplete. Please post the complete traceback, and if
possible, the correct rendering of the

ÎÏίθμηÏη άÏθÏÏν ιÏÏ ...

stuff. Or is that perhaps some garbled rendering of

Αρίθμηση άρθρων ιστορικών αρχείων

Also, is other stuff missing. I.e., is there more between
"2013-February" and "Pickling archive state into ..."

Normally, I would expect three lines like

#nn 
figuring article archives
-Month

for each message in the mbox followed by something like

Updating index files for archive [-Month]
  Date
  Subject
  Author
  Thread
Computing threaded index
Updating HTML for article n1
Updating HTML for article n2
...

for each month in the archive and then finally, the

Pickling archive state into ...

line.

I really need the complete traceback to begin to say more.

-- 
Mark Sapiro <m...@msapiro.net>The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

[Mailman-Users] Mailman archive creation problem

[Limperis Antonis]

Hello mailman users

We have a mailman version 2.1.22 installation.
We try to reconstruct a mail  list archive with command 'arch --wipe listname'  
and receive the following error.

#0 <f60795d9b7521c478f6f9174a9183dc94279d...@mail.cti.gr>
ÎÏίθμηÏη άÏθÏÏν ιÏÏ
οÏικÏν αÏÏείÏν 2013-February Pickling 
archive state into /var/mailman/archives/private/tenders/pipermail.pck
Traceback (most recent call last):
  File "/var/mailman/bin/arch", line 201, in 
main()
  File "/var/mailman/bin/arch", line 189, in main
archiver.processUnixMailbox(fp, start, end)
  File "/var/mailman/Mailman/Archiver/pipermail.py", line 596, in 
processUnixMailbox

Is there some  suggestion  or  experience on this problem?

Thank you, for your attention.

 Antonis Limperis
 



--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] mailman archive not working

[Mark Sapiro]

On 08/09/2016 06:51 PM, Caesar Samsi wrote:
> 
> When I access the archive via a browser, it shows “Forbidden”
> 
> When I check /var/lib/mailman/archives/public they are all symlinks to 
> /var/lib/mailman/archives/private which I assume are not allowed to be read.


It is correct that /var/lib/mailman/archives/public/* are symlinks to
/var/lib/mailman/archives/private/*.

/var/lib/mailman/archives/private/ must be searchable by the web server
user. It must be either mode o+x (i.e. drwxrws--x) or owned by the web
server user. See <http://www.list.org/mailman-install/node9.html>.

If that isn't the answer, see
<http://www.list.org/mailman-install/node10.html>.

-- 
Mark Sapiro <m...@msapiro.net>The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

[Mailman-Users] mailman archive not working

[Caesar Samsi]

Hi Mark,

When I access the archive via a browser, it shows “Forbidden”

When I check /var/lib/mailman/archives/public they are all symlinks to 
/var/lib/mailman/archives/private which I assume are not allowed to be read.

I attempted to change the permissions, but that didn’t work.

Thank you, Caesar.
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] searchable archive options for cPanel server

[David Andrews]

At 02:30 PM 7/14/2016, Mark Sapiro wrote:

On 07/14/2016 12:07 PM, Jason Fayre wrote:
>
> We have a server running cPanel that hosts around 200 mailing lists. We
> really want to have searchable archives. If I install the mailman htdig
> patches, cPanel won't support us.


And what Mailman support do you currently get from cPanel that you'd be
giving up? Or do you mean that if you patch any piece, they won't
support anything including stuff you haven't touched?


He means all cPanel support, not just Mailman!



--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] searchable archive options for cpanel server

[Mark Sapiro]

On 07/14/2016 12:07 PM, Jason Fayre wrote:
> 
> We have a server running cPanel that hosts around 200 mailing lists. We
> really want to have searchable archives. If I install the mailman htdig
> patches, cPanel won't support us.


And what Mailman support do you currently get from cPanel that you'd be
giving up? Or do you mean that if you patch any piece, they won't
support anything including stuff you haven't touched?


> Other than not using cPanel, what are other folks doing:? I know we have the
> option of using mailarchive.org, but we would like to keep the archives
> internal if possible.


If by 'internal' you mean private as opposed to public you are fairly
limited. For public archives, you can use the site: and inurl: Google
search options, e.g. add site:mail.python.org inurl:mailman-users to
your Google search terms to search this list. See
<https://wiki.list.org/x/4030514>.

You can install local search engines such as htdig on your server
without the htdig integration patches. The search form would be a
non-Mailman web page rather than being integrated with Mailman's archive
pages, but you wouldn't need to patch Mailman.

-- 
Mark Sapiro <m...@msapiro.net>The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

[Mailman-Users] searchable archive options for cpanel server

[Jason Fayre]

Hi,

I really wish I didn't need to ask this, but alas, I do.

We have a server running cPanel that hosts around 200 mailing lists. We
really want to have searchable archives. If I install the mailman htdig
patches, cPanel won't support us.

Other than not using cPanel, what are other folks doing:? I know we have the
option of using mailarchive.org, but we would like to keep the archives
internal if possible.

Any suggestions would be appreciated!

 

 

 

--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Mailman Archive Migration Question

[Mark Sapiro]

On 04/09/2016 08:20 AM, Richard Robbins wrote:

> Once I have the collection culled to what I want to retain I thought it
> would be nice to use an email reader with a redirect command that would
> permit me to then send those messages to my WordPress site using the post
> by email function.
> 
> Does this approach make sense?  Are there alternatives I should consider?
> 
> Oh -- and I need to find a current mail program that will allow me redirect
> existing messages to a new address as opposed to using forward.


Mutt can 'bounce' (i.e. redirect) a mail to a new recipient, but it is
an almost trivial Python script to read a mbox and resend every message
to a new address. For example, the script at
<https://www.msapiro.net/scripts/post_from_mbox> does essentially that
in a Mailman context.

I have attached a rough modification of that script that can read a mbox
and remail the messages therein to a given address.

These things are set in the script

SMTPHOST = 'localhost'
SMTPPORT = 25
SMTPUSER = None
SMTPPW = None
MYHOST = socket.gethostname()
ENVFROM = 'root@{}'.format(MYHOST)

The script will work as is if there is an MTA listening on localhost:25
that can deliver the mail to the given address. If not, set SMTPHOST to
the fully qualified name of the MTA you want to use and set SMTPPORT to
the port. If you change nothing else, the script will attempt to send
via that host without authentication. If you need to authenticate, set
SMTPUSER and SMTPPW appropriately and the script will attempt to start
TLS and authenticate as that user.

MYHOST is the host name that will me used in EHLO for a startTLS
connection and may or may not need adjustment. ENVFROM is the envelope
sender and can be adjusted if needed.

The script does almost no error checking so if anything goes wrong, it
will stop with an exception and a traceback and you'll have to fix the
problem and try again.

Start with a mbox with only one or two messages and a test address to
send to until you're sure it works.

-- 
Mark Sapiro <m...@msapiro.net>The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan


#! /usr/bin/env python

"""Remail all messages in some mbox file to a given address.

Usage: %(PROGRAM)s [options] filename address

Where:

--verbose
-v
Print information about what's done.

--help
-h
Print this help message and exit.

'filename' is the name of a *nix mbox file containing one or more messages to
be remailed to 'address'.
"""

import sys
import getopt
import socket
import smtplib

from mailbox import mbox

PROGRAM = sys.argv[0]

def usage(code, msg=''):
if code:
fd = sys.stderr
else:
fd = sys.stdout
print >> fd, __doc__
if msg:
print >> fd, msg
sys.exit(code)


conn = None
SMTPHOST = 'localhost'
SMTPPORT = 25
SMTPUSER = None
SMTPPW = None
MYHOST = socket.gethostname()
ENVFROM = 'root@{}'.format(MYHOST)
def sendit(msg, address):
global conn
if not conn:
conn = smtplib.SMTP()
conn.connect(SMTPHOST, SMTPPORT)
if SMTPUSER:
conn.starttls()
conn.ehlo(MYHOST)
conn.login(SMTPUSER, SMTPPW)
conn.sendmail(ENVFROM, address, msg.as_string())


def main():
try:
opts, args = getopt.getopt(
sys.argv[1:], 'hv',
['help', 'verbose'])
except getopt.error, msg:
usage(1, msg)

verbose = False
for opt, arg in opts:
if opt in ('-h', '--help'):
usage(0)
elif opt in ('-v', '--verbose'):
verbose = True

if len(args) != 2:
usage(1, 'Exactly two arguments required.')

filename = args[0]
address = args[1]
mb = mbox(filename, create=False)
for msg in mb:
if verbose:
print """Resending message
Subject: %s
Date: %s
""" % (msg.get('subject', 'N/A'), msg.get('date', 'N/A'))
sendit(msg, address)


if __name__ == '__main__':
main()


--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

[Mailman-Users] Mailman Archive Migration Question

[Richard Robbins]

I have an archive of email messages from a mailman discussion list that I
would like to recreate as a series of WordPress posts.  The archive
currently exists as an mbox file that I'm pruning with an email reader.
Once I have the collection culled to what I want to retain I thought it
would be nice to use an email reader with a redirect command that would
permit me to then send those messages to my WordPress site using the post
by email function.

Does this approach make sense?  Are there alternatives I should consider?

Oh -- and I need to find a current mail program that will allow me redirect
existing messages to a new address as opposed to using forward.
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

[Mailman-Users] Delete Archive

[am via Mailman-Users]

I posted a similar q on 6th but did not see the post nor any responses. (I
may be still in the newbie doghouse :-) ...)

My question: Is there a way to reset the archive, or delete / restart it?

Mailman 2.1.20

Thank you -

C-L
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Delete Archive

[Mark Sapiro]

On 11/9/15 7:30 AM, am wrote:
> I posted a similar q on 6th but did not see the post nor any responses.
> (I may be still in the newbie doghouse :-) ...)


Your post was received. it is answered at
<https://mail.python.org/pipermail/mailman-users/2015-November/080074.html>.

-- 
Mark Sapiro <m...@msapiro.net>The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

[Mailman-Users] Delete archive?

[am via Mailman-Users]

Is there a way to wipe out an archive and restart it from scratch?

Mailman v2.1.20

C-L
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Delete archive?

[Mark Sapiro]

On 11/06/2015 06:50 AM, am via Mailman-Users wrote:
> Is there a way to wipe out an archive and restart it from scratch?


To delete the archive completely including the cumulative mbox file, do

echo > /path/to/mailman/archives/private/LISTNAME.mbox/LISTNAME.mbox
/path/to/mailman/bin/arch --wipe LISTNAME

To delete just the web archive without deleting messages from the
cumulative mbox file, just do

/path/to/mailman/bin/arch --wipe LISTNAME /dev/null

-- 
Mark Sapiro <m...@msapiro.net>The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

[Mailman-Users] merging archive volumes

[Fabian Santiago]

Hello,

I'm running centos 6.5 x86_64, mailman v 2.1.12, along with postfix. I 
use pipermail to display my list archives in a private fashion.


I originally had my archives set to monthly volumes and then after the 
1st month changed it to yearly. now, when i navigate to my archives 
page, i see two top level volume entries, one for the 1st month when i 
had it set to monthly archiving and one for everything else.


is there anyway i can merge the two into one solid archive volume? 
thanks everyone.


--

Sincerely,

- Fabian S.
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] merging archive volumes

[Mark Sapiro]

On 09/03/2014 02:24 PM, Fabian Santiago wrote:
 
 I originally had my archives set to monthly volumes and then after the
 1st month changed it to yearly. now, when i navigate to my archives
 page, i see two top level volume entries, one for the 1st month when i
 had it set to monthly archiving and one for everything else.
 
 is there anyway i can merge the two into one solid archive volume?


bin/arch --wipe listname

See 'bin/arch --help' for more info.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] merging archive volumes

[Fabian Santiago]

thanks! worked perfectly.

---

Sincerely,

- Fabian S.

On 2014-09-03 17:46, Mark Sapiro wrote:

On 09/03/2014 02:24 PM, Fabian Santiago wrote:


I originally had my archives set to monthly volumes and then after the
1st month changed it to yearly. now, when i navigate to my archives
page, i see two top level volume entries, one for the 1st month when i
had it set to monthly archiving and one for everything else.

is there anyway i can merge the two into one solid archive volume?



bin/arch --wipe listname

See 'bin/arch --help' for more info.

--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Moving Archive Lists

[McGregor, Donald (Don) (CIV)]

 Some systems put the configs and so on in a different place from the
 standard mailman install.  I infer that you have the right place,
 but please confirm.  On my Debian system, list configs look like
 
 /var/lib/mailman/lists/LISTNAME/config.pck
 
 and I've never seen a system that didn't conform to the
 .../mailman/lists/LISTNAME/config.pck pattern.

The old version was 2.12 rc2, so it’s not that old.

list_lists does not pick up the old, archived lists, but does find any
new lists created on the new host. Comparing the 
contents of a list from the old server to one created on the new
server:

// contents of list directory from old, crashed host for the list oldList:

[root lists]# ls -lR oldList
oldList:
total 8
drwxrwsr-x 2 root mailman 4096 May 29 14:10 en
-rw-rw-r-- 1 root mailman   24 May 29 14:10 request.pck

oldList/en:
total 8
-rw-r--r-- 1 root mailman 5582 May 29 14:10 listinfo.html

// Contents of directory for list, wocka17, created on the new host

[root lists]# ls -lR wocka17
wocka17:
total 12
-rw-rw 1 mailman mailman 3714 Jul 22 09:00 config.pck
-rw-rw 1 rootmailman 3714 Jul 21 12:05 config.pck.last
-rw-rw-r-- 1 rootmailman   24 Jul 21 12:05 request.pck

So it looks like I’m missing the config.pck files on the lists
from the old host. Did I get a bad backup?  The disks eventually
blew up on the old host so that’s plausible. 

Is there a way to re-generate the config.pck files? And where
is the list of subscribers for each list kept?

--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Moving Archive Lists

[Mark Sapiro]

On 07/22/2014 11:09 AM, McGregor, Donald (Don) (CIV) wrote:
 
 So it looks like I’m missing the config.pck files on the lists
 from the old host. Did I get a bad backup?  The disks eventually
 blew up on the old host so that’s plausible. 


If the config.pck files are missing from your backups, your backups are
incomplete.


 Is there a way to re-generate the config.pck files? And where
 is the list of subscribers for each list kept?


Unless you have a custom MemberAdaptor, the list membership is in the
config.pck along with all the list attributes. The only way to
re-generate it is to create the list, configure it and add the members.
There's nowhere else that the information is kept.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Moving Archive Lists

[McGregor, Donald (Don) (CIV)]

…And, that was it. Reverting to an earlier backup that got the whole
thing solved the problem.


On Jul 22, 2014, at 11:17 AM, Mark Sapiro m...@msapiro.net wrote:

 On 07/22/2014 11:09 AM, McGregor, Donald (Don) (CIV) wrote:
 
 So it looks like I’m missing the config.pck files on the lists
 from the old host. Did I get a bad backup?  The disks eventually
 blew up on the old host so that’s plausible. 
 
 
 If the config.pck files are missing from your backups, your backups are
 incomplete.
 
 
 Is there a way to re-generate the config.pck files? And where
 is the list of subscribers for each list kept?
 
 
 Unless you have a custom MemberAdaptor, the list membership is in the
 config.pck along with all the list attributes. The only way to
 re-generate it is to create the list, configure it and add the members.
 There's nowhere else that the information is kept.
 
 -- 
 Mark Sapiro m...@msapiro.netThe highway is for gamblers,
 San Francisco Bay Area, Californiabetter use your sense - B. Dylan
 --
 Mailman-Users mailing list Mailman-Users@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/mcgredo%40nps.edu

--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

[Mailman-Users] Moving Archive Lists

[McGregor, Donald (Don) (CIV)]

I had a server blow up on me. It’s dead, Jim, but I have backups of the 
/usr/local/mailman directory, and
I’m attempting to bring it up on a new box with a yum-supplied copy of mailman 
rather than the
old-fashioned hand install.

I’ve got the yum-supplied version configured, and can create new lists. But the 
old archive
lists, in the same directory with the same permissions, are not showing up. The 
yum-supplied
new mailman version is not the same as the version on the old server, and I 
can’t really bring
up the old server without some heroic measures.

Is there some pck database file I need to upgrade or massage to have the old 
lists
be recognized?
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

[Mailman-Users] Moving Archive Lists

[Stephen J. Turnbull]

Don:

  I’m attempting to bring it up on a new box with a yum-supplied copy
  of mailman rather than the old-fashioned hand install.

Some systems put the configs and so on in a different place from the
standard mailman install.  I infer that you have the right place,
but please confirm.  On my Debian system, list configs look like

/var/lib/mailman/lists/LISTNAME/config.pck

and I've never seen a system that didn't conform to the
.../mailman/lists/LISTNAME/config.pck pattern.

  The yum-supplied new mailman version is not the same as the version
  on the old server,

How old was the old Mailman?  AFAIK old configs should automatically
be upgraded if necessary when you upgrade Mailman, unless they're very
very old ( 2.1.9 at a guess).

  But the old archive lists, in the same directory with the same
  permissions, are not showing up.

Please clarify what you mean by old archive lists not showing up.
What's not showing up?  The list archives?  The public lists in the
mailman/listinfo page in the admin website?  It doesn't deliver posts
to those lists?  More than one of the above (please specify)?
Something else?

  Is there some pck database file I need to upgrade or massage to
  have the old lists be recognized?

No, Mailman 2.1 recognizes lists by the presence of a config.pck file
in the lists/list-name directory.  If you have the right place and
the version of Mailman that created the configs was not locally
modified and not decades old, it should recognize those configs.

HTH

Steve
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Moving Archive Lists

[Mark Sapiro]

On 07/21/2014 08:43 PM, Stephen J. Turnbull wrote:

 
 How old was the old Mailman?  AFAIK old configs should automatically
 be upgraded if necessary when you upgrade Mailman, unless they're very
 very old ( 2.1.9 at a guess).


Way older than that. Even config.db files from Mailman 2.0.x will be
properly converted/upgraded. There's even code in Mailman/versions.py,
which is what does the work, to address Mailman 1.0 lists, but I won't
guarantee it works on 1.0.x or the oldest 2.0.x config.db files but it
does the best it can to map things as closely as possible to their
current equivalents.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

Re: [Mailman-Users] Changing Archive Frequency

[Sajan Parikh]

Sorry.  Just realized there was a arch file in the bin directory.

./arch --wipe [listname] did the trick.

Sajan Parikh

On 03/12/2014 04:34 PM, Sajan Parikh wrote:

I'm running Mailman 2.1-3 on Ubuntu, installed from the repositories.

I changed the archive frequency on my list from daily to monthly and
noticed that the actual archive web page has not updated.  It still
shows the previous messages by day.

Assuming that it will be monthly from here on out, is there any way I
can regenerate the previous archives and have them show monthly as well?

Thanks.

--
Mailman-Users mailing list Mailman-Users@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/archive%40jab.org

[Mailman-Users] monthly archive

[Thufir]

When I visit the archive for my first list, alpha, it says:


 No messages have been posted to this list yet, so the archives are 
currently empty. You can get more information about this list.



However, I subscribed thu...@dur.bounceme.com, receive the e-mail 
locally, clicked the link, sent a first post, received a copy to 
thu...@dur.bounceme.net.  The list itself seems to work fine.


I've reviewed the list settings through the web UI and it says to 
archive monthly.  Do I need to wait a month before that first post shows 
in the archive?


Also, where are the settings for a list stored?  I browse to something like:

http://dur.bounceme.net/cgi-bin/mailman/admin/alpha/?VARHELP=archive/archive_volume_frequency

but I'm not sure where the config file for that setting for this mailing 
list actually resides.


Do I need to run mailman to create the archive?  Can I directly access 
the archive files and list config files without the web UI?




thanks,

Thufir
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] monthly archive

[Mark Sapiro]

Thufir wrote:

When I visit the archive for my first list, alpha, it says:


  No messages have been posted to this list yet, so the archives are 
currently empty. You can get more information about this list.


However, I subscribed thu...@dur.bounceme.com, receive the e-mail 
locally, clicked the link, sent a first post, received a copy to 
thu...@dur.bounceme.net.  The list itself seems to work fine.


Then the post should have been archived assuming ArchRunner is running,
no errors are reported in Mailman's logs/error log and the list's
Archiving options - archive is set to Yes.


I've reviewed the list settings through the web UI and it says to 
archive monthly.  Do I need to wait a month before that first post shows 
in the archive?


No


Also, where are the settings for a list stored?  I browse to something like:

http://dur.bounceme.net/cgi-bin/mailman/admin/alpha/?VARHELP=archive/archive_volume_frequency

but I'm not sure where the config file for that setting for this mailing 
list actually resides.


Mailman's lists/LISTNAME/config.pck


Do I need to run mailman to create the archive?


Mailman (ArchRunner) must be running to archive messages, but then if
Mailman isn't running, posts will not be processed and sent to list
members.


Can I directly access 
the archive files and list config files without the web UI?



Yes. The archive files are in archives/private/LISTNAME*

Tools for examining/changing the list configuration are in Mailman's
bin/ directory.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman archive - archive date does not match thedate the message was posted

[Anthony Wilson (Jaf)]

Thanks for your reply Mark.

I took a look in the .mbox file and unfortunately the dates in the From and
Date headers are 2000, so it seems a manual fix is in order. There's 230
messages so I'll put that on hold for now.

On Sun, Nov 4, 2012 at 11:07 PM, Mark Sapiro m...@msapiro.net wrote:

 Anthony Wilson (Jaf) wrote:

 There is an existing Mailman list with an archive which needs to be moved
 to a different server, however it seems that the archive is a bit messed
 up. I assume that the list was set up in 2006, but for some reason there
 is
 a 2002 archive, and all of the posts in there seem to have been posted in
 2012. It's a public archive so I assume there's no harm in posting a link
 to it - https://secure.neap.net/pipermail/montrealers/.  Is there some
 way
 to fix this?


 There are two different groups of messages in the archive for January,
 2002. One group is messages numbered 023657 through 023673. These
 actually belong in July, 2009 between
 https://secure.neap.net/pipermail/montrealers/2009-July/023656.html
 and
 https://secure.neap.net/pipermail/montrealers/2009-July/023674.html.

 The other group is messages numbered 052646 through 052858. These
 actually belong in May, 2012 between
 https://secure.neap.net/pipermail/montrealers/2012-May/052645.html
 and
 https://secure.neap.net/pipermail/montrealers/2012-May/052859.html.

 How they wound up with wrong dates is something of a mystery. My best
 guess is that the system clock on the server that archived them was
 set wrong during some periods in July 2009 and May 2012, but that
 seems far fetched.

 I'm assuming that the messages are in correct sequence in the
 archives/private/montrealers.mbox/montrealers.mbox file. The first
 step is to find some of these messages in that file ans see what the
 time stamps are in their From_ lines and Date: headers. If the time
 stamps appear correct there,

 bin/arch --wipe montrealers

 will probably fix everything. If those time stamps are from 2002, I
 think the answer is manually editing the timestamps in
 archives/private/montrealers.mbox/montrealers.mbox file and then
 running the above bin/arch command.

 --
 Mark Sapiro m...@msapiro.netThe highway is for gamblers,
 San Francisco Bay Area, Californiabetter use your sense - B. Dylan


--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman archive - archive date does not match the date the message was posted

[Anthony Wilson (Jaf)]

There is an existing Mailman list with an archive which needs to be moved
to a different server, however it seems that the archive is a bit messed
up. I assume that the list was set up in 2006, but for some reason there is
a 2002 archive, and all of the posts in there seem to have been posted in
2012. It's a public archive so I assume there's no harm in posting a link
to it - https://secure.neap.net/pipermail/montrealers/.  Is there some way
to fix this?
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman archive - archive date does not match thedate the message was posted

[Mark Sapiro]

Anthony Wilson (Jaf) wrote:

There is an existing Mailman list with an archive which needs to be moved
to a different server, however it seems that the archive is a bit messed
up. I assume that the list was set up in 2006, but for some reason there is
a 2002 archive, and all of the posts in there seem to have been posted in
2012. It's a public archive so I assume there's no harm in posting a link
to it - https://secure.neap.net/pipermail/montrealers/.  Is there some way
to fix this?


There are two different groups of messages in the archive for January,
2002. One group is messages numbered 023657 through 023673. These
actually belong in July, 2009 between
https://secure.neap.net/pipermail/montrealers/2009-July/023656.html
and
https://secure.neap.net/pipermail/montrealers/2009-July/023674.html.

The other group is messages numbered 052646 through 052858. These
actually belong in May, 2012 between
https://secure.neap.net/pipermail/montrealers/2012-May/052645.html
and
https://secure.neap.net/pipermail/montrealers/2012-May/052859.html.

How they wound up with wrong dates is something of a mystery. My best
guess is that the system clock on the server that archived them was
set wrong during some periods in July 2009 and May 2012, but that
seems far fetched.

I'm assuming that the messages are in correct sequence in the
archives/private/montrealers.mbox/montrealers.mbox file. The first
step is to find some of these messages in that file ans see what the
time stamps are in their From_ lines and Date: headers. If the time
stamps appear correct there,

bin/arch --wipe montrealers

will probably fix everything. If those time stamps are from 2002, I
think the answer is manually editing the timestamps in
archives/private/montrealers.mbox/montrealers.mbox file and then
running the above bin/arch command.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mailman archive forbidden

[Massimo Barbieri]

Hi,
I have a fresh installation of Mailman on Debian Wheezy, and my public
mailing list archive is inaccessible (403 Forbidden), but if I switch to
private archive it works without error.

1) I tryed to run check_perms -f as root and I got:
wrong group for /var/lib/mailman/cron (ha root invece di list) (fixed)
wrong group for /var/lib/mailman/mail (ha root invece di list) (fixed)
wrong group for /var/lib/mailman/icons (ha root invece di list) (fixed)
wrong group for /var/lib/mailman/logs (ha root invece di list) (fixed)
wrong group for /var/lib/mailman/bin (ha root invece di list) (fixed)
wrong group for /var/lib/mailman/scripts (ha root invece di list) (fixed)
wrong group for /var/lib/mailman/templates (ha root invece di list) (fixed)
wrong group for /var/lib/mailman/Mailman (ha root invece di list) (fixed)
wrong group for /var/lib/mailman/cgi-bin (ha root invece di list) (fixed)
wrong group for /var/lib/mailman/locks (ha root invece di list) (fixed)
Problemi riscontrati: 10
Per correggere gli errori rilancia il comando come
list (o root) con il flag -f

2) I tryed to put the user list in the www-data group as reported here:

http://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg1046834.html



Here is a part of my mailman.conf:

Directory /var/lib/mailman/archives/
Options FollowSymLinks
AllowOverride None
Order allow,deny
Allow from all
/Directory

Alias /pipermail/ /var/lib/mailman/archives/public/
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/
ScriptAlias / /usr/lib/cgi-bin/mailman/listinfo

-
Here are some file and folder permission that could be interesting to solve:
:/var/lib/mailman$ ls -l
drwxrwsr-x  4 root list 4096 apr 16 21:21 archives

:/var/lib/mailman/archives$ ls -l
drwxrws--- 8 list list 4096 set 10 21:37 private
drwxrwsr-x 2 list list 4096 set 11 08:07 public

:/var/lib/mailman/archives$ ls -l public/
lrwxrwxrwx 1 root list   41 apr 16 21:25 mailman -
/var/lib/mailman/archives/private/mailman
lrwxrwxrwx 1 www-data list   39 set 11 08:07 users -
/var/lib/mailman/archives/private/users

:/var/lib/mailman/archives$ ls -l /var/lib/mailman/archives/private
drwxrwsr-x 2 root list 4096 apr 16 21:25 mailman
drwxrwsr-x 2 root list 4096 apr 16 21:25 mailman.mbox
drwxrwsr-x 6 www-data list 4096 set 11 03:27 users
drwxrwsr-x 2 www-data list 4096 set 10 21:47 users.mbox

Does anyone have any suggestions?
Ciao,
Max-B

-- 
IM: ma...@jabber.org - OpenPGP Key-Id: 0x5D168FC1



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman archive forbidden

[Massimo Barbieri]

Hi,
I solved, in case could be useful for other here is my solution.

Il 11/09/2012 08:39, Massimo Barbieri ha scritto:
 :/var/lib/mailman/archives$ ls -l
 drwxrws--- 8 list list 4096 set 10 21:37 private
 drwxrwsr-x 2 list list 4096 set 11 08:07 public

The problem is that the private folder has wrong owner. I change it to
www-data.

Ciao,
Max-B


-- 
IM: ma...@jabber.org - OpenPGP Key-Id: 0x5D168FC1



signature.asc
Description: OpenPGP digital signature
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mailman archive forbidden

[Mark Sapiro]

Massimo Barbieri wrote:

I solved, in case could be useful for other here is my solution.

Il 11/09/2012 08:39, Massimo Barbieri ha scritto:
 :/var/lib/mailman/archives$ ls -l
 drwxrws--- 8 list list 4096 set 10 21:37 private
 drwxrwsr-x 2 list list 4096 set 11 08:07 public

The problem is that the private folder has wrong owner. I change it to
www-data.


This issue and its solution are well known. See section 4 of the GNU
Mailman installation manual
http://www.list.org/mailman-install/node9.html.

I'm sorry you encountered this issue. Perhaps there is something
lacking in the Debian installation documentation. Please see the FAQ
at http://wiki.list.org/x/OIDD, and if appropriate, report this to
Debian.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] regarding Archive messages

[Robert (Bob) Hamilton]

Hi Amit,

You are not alone as I have the same problem since late January and 
it is still not resolved with the suggestions I received here. I also 
know of another user with this problem so there has to be a bug somewhere.


Regards,
Bob


At 01:30 AM 4/3/2012, Amit Bhatt wrote:

Hello,

We can just see the archive til 9th March 2012 on our mailing list 
and after that there is no archive shown. What may be the cause?


regards,

Amit Bhatt
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/hamilton%40accesswave.ca


~~~
Robert A.C. Hamilton, P.O. Box 5033, Waverley, Nova Scotia, B2R 1S2
E-Mail: hamil...@accesswave.ca
Tel: 902-861-3277  Cell: (902) 456-6542
Visit my 
http://robertach.zenfolio.com/Zenfoliohttp://robertach.zenfolio.com/ 
Gallery and http://www.accesswave.ca/~hamiltonHome Page
~~~  
--

Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] regarding Archive messages

[Mark Sapiro]

Robert (Bob) Hamilton wrote:

You are not alone as I have the same problem since late January and 
it is still not resolved with the suggestions I received here. I also 
know of another user with this problem so there has to be a bug somewhere.


You posted about this in February
http://mail.python.org/pipermail/mailman-users/2012-February/072952.html.

In my reply
http://mail.python.org/pipermail/mailman-users/2012-February/072956.html
I asked Is ArchRunner running? Have you tried stopping and starting
(as opposed to restarting) Mailman? Have you looked in Mailman's
'error' and 'qrunner' logs?

We heard nothing further from you until now. If you think there is a
bug, please work with us to help find and fix it.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] regarding Archive messages

[Amit Bhatt]

Hello,

We can just see the archive til 9th March 2012 on our mailing list and after 
that there is no archive shown. What may be the cause?

regards,

Amit Bhatt
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] regarding Archive messages

[Mark Sapiro]

Amit Bhatt wrote:

We can just see the archive til 9th March 2012 on our mailing list and after 
that there is no archive shown. What may be the cause?


Is ArchiveRunner running? Also check Mailman's qrunner and error logs
to see why Archive Runner died or what other error's might be
preventing archiving since March 9.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Online archive contains odd strings like%(indexing_disable)s

[Rosenbaum, Larry M.]

 From: Mark Sapiro [mailto:m...@msapiro.net]
 
 Rosenbaum, Larry M. wrote:
 
 For some of our lists, the web interface for the archives are peppered
 with various strings like %(indexing_disable)s and %(htsearch)s.  The
 lists were recently migrated from a Solaris 9 box to a RHEL6 box.
 Rebuilding the archives doesn't fix the problem.  What do we need to do to
 fix it?
 
 We are running Mailman v2.1.12 with htDig integration.
 
 
 If rebuilding the archive doesn't fix it, something is wrong with your
 htDig integration.

Thank you for the help. It turns out that some of the files didn't get patched 
(or somehow got unpatched). I applied the patches and it is working properly 
now.

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Online archive contains odd strings like %(indexing_disable)s

[Rosenbaum, Larry M.]

For some of our lists, the web interface for the archives are peppered with 
various strings like %(indexing_disable)s and %(htsearch)s.  The lists were 
recently migrated from a Solaris 9 box to a RHEL6 box.  Rebuilding the archives 
doesn't fix the problem.  What do we need to do to fix it?

We are running Mailman v2.1.12 with htDig integration.

Larry M. Rosenbaum
Oak Ridge National Laboratory

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Online archive contains odd strings like%(indexing_disable)s

[Mark Sapiro]

Rosenbaum, Larry M. wrote:

For some of our lists, the web interface for the archives are peppered with 
various strings like %(indexing_disable)s and %(htsearch)s.  The lists were 
recently migrated from a Solaris 9 box to a RHEL6 box.  Rebuilding the 
archives doesn't fix the problem.  What do we need to do to fix it?

We are running Mailman v2.1.12 with htDig integration.


If rebuilding the archive doesn't fix it, something is wrong with your
htDig integration.

Those replacements are in the htDig integration version of the archive
templates and they should be properly replaced as messages are
archived or as the archive is being rebuilt.

If you run bin/arch --wipe on a list's archive, it *should* fix it. If
it doesn't, but newly archived posts are OK, I can't understand what
would be wrong. If newly archived posts also have uninterpolated
replacements, then something is missing from htDig integration.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Adding archive link to mail footer?

[Sascha Rissel]

Hello,

is there a nice way of adding a link to the list's archive to msg_footer?
Like it is done with the link to the list info page
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

Regards,
Sascha.
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Adding archive link to mail footer?

[Mailman Admin]

Hello Sascha Rissel


On 2012-03-05 16:26, Sascha Rissel wrote:
 
 is there a nice way of adding a link to the list's archive to msg_footer?
 Like it is done with the link to the list info page
 %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
 

Sure.

For private archives use
%(web_page_url)sprivate/%(_internal_name)s

And for public ones use
%(web_page_url)spublic/%(_internal_name)s


Kind regards,
Christian Mack
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Adding archive link to mail footer?

[Mark Sapiro]

Mailman Admin wrote:

For private archives use
%(web_page_url)sprivate/%(_internal_name)s


Yes.


And for public ones use
%(web_page_url)spublic/%(_internal_name)s


No. This won't work in a standard Mailman installation. It might work
if you have set

PUBLIC_ARCHIVE_URL = 'http://%(hostname)s/mailman/public/%(listname)s'

in mm_cfg.py and put the appropriate alias for mailman/public in your
web server, but for defauly public archives you need to use something
like

http://www.example.com/pipermail/%(list_name)s

Note that in msg and digest headers and footers, %(list_name)s and
%(_internal_name)s are equivalent, but %(_internal_name)s is a
deprecated usage (even though it is still in the default footer).

Note also that in the above, www.example.com could be replaced with
%(host_name)s, but only if the list's web and email hosts are the same
as %(host_name)s is the list's email host.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] No archive

[Peter]

Mark Sapiro schreef:

Peter wrote:
  

I did upgrade from Debian5 to 6 and running mailman version 2.1.13
I have postfix running with aliases in mysql.
I move the aliases tabel to the new server
To move the list to the new server did the next steps:
newlist ping, give the needed info, add the members.

Then I import the old mbox files and create the archive with:
bin/arch ping archives/private/ping.mbox/ping.mbox

So far so good.
I can send and receive  email to and receive them from the list.
I see the old archive, BUT there are no new emails archieved anymore




Have you checked whether ArchRunner is running and looked at Mailman's
error log?


  

Oops, first thing to check and i has done that.
\Found the error:
IOError: [Errno 13] Permission denied: 
'/var/lib/mailman/archives/private/ping.mbox/ping.mbox'


That clear!
Check the new list and Debian6 set users to root:www-data.
I changed it tot list:www-data and now added to the archive

Thanks

Peter
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] No archive

[Peter]

Hi

I did upgrade from Debian5 to 6 and running mailman version 2.1.13
I have postfix running with aliases in mysql.
I move the aliases tabel to the new server
To move the list to the new server did the next steps:
newlist ping, give the needed info, add the members.

Then I import the old mbox files and create the archive with:
bin/arch ping archives/private/ping.mbox/ping.mbox

So far so good.
I can send and receive  email to and receive them from the list.
I see the old archive, BUT there are no new emails archieved anymore

While creating the newlist I saw on the end to at the the aliass tabel:
ping:  |/var/lib/mailman/mail/mailman post ping
ping-admin:|/var/lib/mailman/mail/mailman admin ping
ping-bounces:  |/var/lib/mailman/mail/mailman bounces ping
ping-confirm:  |/var/lib/mailman/mail/mailman confirm ping
ping-join: |/var/lib/mailman/mail/mailman join ping
ping-leave:|/var/lib/mailman/mail/mailman leave ping
ping-owner:|/var/lib/mailman/mail/mailman owner ping
ping-request:  |/var/lib/mailman/mail/mailman request ping
ping-subscribe:|/var/lib/mailman/mail/mailman subscribe ping
ping-unsubscribe:  |/var/lib/mailman/mail/mailman unsubscribe ping

But how can I handle this in mysql?

I use the old style:
p...@example.com p...@lists.example.com
ping-ad...@example.com ping-ad...@lists.example.com
ping-boun...@example.com ping-boun...@lists.example.com
ping-conf...@example.com ping-conf...@lists.example.com
ping-j...@example.com ping-j...@lists.example.com
ping-le...@example.com ping-le...@lists.example.com
ping-ow...@example.com ping-ow...@lists.example.com
ping-requ...@example.com ping-requ...@lists.example.com
ping-subscr...@example.com ping-subscr...@lists.example.com
ping-unsubscr...@example.com ping-unsubscr...@lists.example.com


Has this a relation with the no archiving at the moment?

peter

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] No archive

[Mark Sapiro]

Peter wrote:

I did upgrade from Debian5 to 6 and running mailman version 2.1.13
I have postfix running with aliases in mysql.
I move the aliases tabel to the new server
To move the list to the new server did the next steps:
newlist ping, give the needed info, add the members.

Then I import the old mbox files and create the archive with:
 bin/arch ping archives/private/ping.mbox/ping.mbox

So far so good.
I can send and receive  email to and receive them from the list.
I see the old archive, BUT there are no new emails archieved anymore


Have you checked whether ArchRunner is running and looked at Mailman's
error log?


While creating the newlist I saw on the end to at the the aliass tabel:
ping:  |/var/lib/mailman/mail/mailman post ping
ping-admin:|/var/lib/mailman/mail/mailman admin ping
ping-bounces:  |/var/lib/mailman/mail/mailman bounces ping
ping-confirm:  |/var/lib/mailman/mail/mailman confirm ping
ping-join: |/var/lib/mailman/mail/mailman join ping
ping-leave:|/var/lib/mailman/mail/mailman leave ping
ping-owner:|/var/lib/mailman/mail/mailman owner ping
ping-request:  |/var/lib/mailman/mail/mailman request ping
ping-subscribe:|/var/lib/mailman/mail/mailman subscribe ping
ping-unsubscribe:  |/var/lib/mailman/mail/mailman unsubscribe ping

But how can I handle this in mysql?

I use the old style:
p...@example.com p...@lists.example.com
ping-ad...@example.com ping-ad...@lists.example.com
ping-boun...@example.com ping-boun...@lists.example.com
ping-conf...@example.com ping-conf...@lists.example.com
ping-j...@example.com ping-j...@lists.example.com
ping-le...@example.com ping-le...@lists.example.com
ping-ow...@example.com ping-ow...@lists.example.com
ping-requ...@example.com ping-requ...@lists.example.com
ping-subscr...@example.com ping-subscr...@lists.example.com
ping-unsubscr...@example.com ping-unsubscr...@lists.example.com


You could see the FAQ at http://wiki.list.org/x/ZoCj for some hints.
Also, see the FAQ at http://wiki.list.org/x/OIDD.


Has this a relation with the no archiving at the moment?


No. It is not related. Aliases and other Postfix configuration mostly
has to do with delivery of incoming mail to Mailman. It can also have
an effect on outgoing mail from Mailman, but this generally at least
works if Postfix is working at all.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] public archive points to private archive directory

[Russell L. Carter]

Greetings,
I've just brought up mailman on a debian-testing box
and almost everything works. (Hooray!) The problem I'm having
is that after creating a list, subscribing a user, and
sending a message to the list, I go to the list info
page:

http://lists.pinyon.org/listinfo/testing3

and click on ... visit the Testing3 Archives with
link:

http://lists.pinyon.org/pipermail/testing3/

and I get

Forbidden

You don't have permission to access /pipermail/testing3/ on this server.

So ok, this seems to be a permissions problem, and I'm bothering
you all so that I can learn the Right Way(tm) to fix it.

The relevant apache config is:

 Directory /var/lib/mailman/archives/
Options FollowSymLinks
AllowOverride None
 /Directory
 Alias /pipermail/ /var/lib/mailman/archives/public/

Here's the permissions trail (after bin/check_perms -f):

root@quine:/var/lib/mailman# ls
archives/  cgi-bin@  data/   lists/  logs@  Mailman@   qfiles/   spam/
bin@   cron@ icons@  locks@  mail@  messages/  scripts@  templates@
root@quine:/var/lib/mailman# ls -ld archives/
drwxrwsr-x 4 root list 4096 Oct 26 17:59 archives//
root@quine:/var/lib/mailman# ls -ld archives/*
drwxrws--- 6 list list 4096 Oct 27 15:09 archives/private/
drwxrwsr-x 2 root list 4096 Oct 27 15:09 archives/public/
root@quine:/var/lib/mailman# ls -ld archives/public/*
lrwxrwxrwx 1 root list 41 Oct 26 18:01 archives/public/mailman -
/var/lib/mailman/archives/private/mailman/
lrwxrwxrwx 1 www-data list 42 Oct 27 15:09 archives/public/testing3 -
/var/lib/mailman/archives/private/testing3/

Hmm, archives/public/testing3 points to archives/private/... but
apache running as www-data can't access archives/private because
private is list:list and with no world readers (as it should be).

However the list testing3 is configured to have *public* archives.
So... why is the public archive pointing to the private one?

What's the Right Way to fix this so that clicking the visit archives
link on a new list doesn't result in a 403 Forbidden barf?

Or have I possibly botched something else?

Many thanks,
Russell
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] public archive points to private archive directory

[Mark Sapiro]

Russell L. Carter wrote:

I've just brought up mailman on a debian-testing box
and almost everything works. (Hooray!) The problem I'm having
is that after creating a list, subscribing a user, and
sending a message to the list, I go to the list info
page:

http://lists.pinyon.org/listinfo/testing3

and click on ... visit the Testing3 Archives with
link:

http://lists.pinyon.org/pipermail/testing3/

and I get

Forbidden

You don't have permission to access /pipermail/testing3/ on this server.

[...]
Here's the permissions trail (after bin/check_perms -f):

[...]
drwxrws--- 6 list list 4096 Oct 27 15:09 archives/private/
[...]
Hmm, archives/public/testing3 points to archives/private/... but
apache running as www-data can't access archives/private because
private is list:list and with no world readers (as it should be).


[...]
However the list testing3 is configured to have *public* archives.
So... why is the public archive pointing to the private one?


Because the archives are always in the archives/private/ tree and
archives/public contains only symlinks to archives/public.

If this were not the case, changing an archive from private to public
or vice versa would require moving the tree rather than just
adding/removing a symlink.


What's the Right Way to fix this so that clicking the visit archives
link on a new list doesn't result in a 403 Forbidden barf?


Make the archives/private/ directory searchable by the web server.
Either

chown www-data:list archives/private

or

chmod o+x archives/private.

See section 4 of the installation manual at
http://www.list.org/mailman-install/node9.html. Also see
http://wiki.list.org/x/OIDD, and if this is the way the Debian
package installs, report this to Debian as a packaging bug.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] public archive points to private archive directory

[Mark Sapiro]

Mark Sapiro wrote:

Because the archives are always in the archives/private/ tree and
archives/public contains only symlinks to archives/public.


That should be

archives/public contains only symlinks to archives/private.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] public archive points to private archive directory

[Russell L. Carter]

On 10/27/2011 04:33 PM, Mark Sapiro wrote:

 What's the Right Way to fix this so that clicking the visit archives
 link on a new list doesn't result in a 403 Forbidden barf?
 
 
 Make the archives/private/ directory searchable by the web server.
 Either
 
 chown www-data:list archives/private
 
 or
 
 chmod o+x archives/private.
 
 See section 4 of the installation manual at
 http://www.list.org/mailman-install/node9.html. Also see
 http://wiki.list.org/x/OIDD, and if this is the way the Debian
 package installs, report this to Debian as a packaging bug.
 

Ok, I guess I need to purge the current installation and
figure out where the permissions go awry while configuring the
debian installed package.

Thanks for the pointers.

Best,
Russell

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] public archive points to private archivedirectory

[Mark Sapiro]

Russell L. Carterwrote:

On 10/27/2011 04:33 PM, Mark Sapiro wrote:

 What's the Right Way to fix this so that clicking the visit archives
 link on a new list doesn't result in a 403 Forbidden barf?
 
 
 Make the archives/private/ directory searchable by the web server.
 Either
 
 chown www-data:list archives/private
 
 or
 
 chmod o+x archives/private.
 
 See section 4 of the installation manual at
 http://www.list.org/mailman-install/node9.html. Also see
 http://wiki.list.org/x/OIDD, and if this is the way the Debian
 package installs, report this to Debian as a packaging bug.
 

Ok, I guess I need to purge the current installation and
figure out where the permissions go awry while configuring the
debian installed package.


One possibility is that the archives/private directory was installed
o+x and bin/check_perms told you

Warning: Private archive directory is other-executable (o+x).
 This could allow other users on your system to read private
archives.
 If you're on a shared multiuser system, you should consult the
 installation manual on how to fix this.

and you then set o-x without also changing the owner to www-data.

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Include archive URL for the current email (in the footer)?

[Sebastian Kayser]

Hi,

this question has been asked before [1]. Mailman can include various
list URLs in the footer [2], can it also include a link to the exact
archive URL for the current email?

Judging by the wishlist, this feature doesn't yet exist [3]. In absence
thereof, what do you guys do to determine the archive URL for an email?

Background: I often find myself referring people to our Mailman archives
when there were previous emails on the topic in question. My current
workflow looks like this:

1) Find email in $MUA (mutt in my case) where search is powerful
   and close to second nature.
2) Use google to find the relevant archive URL (site:$archive $topic).

The second step feels disconnected and would be redundant if the mail
itself had a link to the archived message.

Sebastian

P.S.: Only found out about the wishlist after re-reading [1]. Would be a
good candidate to be included in the mailman-users intro text [4] (next
to FAQ and searchable archives).

[1] http://www.mail-archive.com/mailman-users@python.org/msg12190.html
[2] http://www.gnu.org/s/mailman/mailman-admin/node18.html
[3] http://www.gnu.org/s/mailman/todo.html (API between MM and archiver)
[4] http://mail.python.org/mailman/listinfo/mailman-users
--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Include archive URL for the current email (in thefooter)?

[Mark Sapiro]

Sebastian Kayser wrote:

this question has been asked before [1]. Mailman can include various
list URLs in the footer [2], can it also include a link to the exact
archive URL for the current email?


See the FAQ at http://wiki.list.org/x/RAKJ.

Also, this ability will be available in Mailman 3.


[...]
P.S.: Only found out about the wishlist after re-reading [1]. Would be a
good candidate to be included in the mailman-users intro text [4] (next
to FAQ and searchable archives).

[1] http://www.mail-archive.com/mailman-users@python.org/msg12190.html
[2] http://www.gnu.org/s/mailman/mailman-admin/node18.html
[3] http://www.gnu.org/s/mailman/todo.html (API between MM and archiver)


The content of this page is old and not maintained. The date at the top
is the date the page was last formatted, not the date of the contents.

Check the wiki at http://wiki.list.org/ for more current info. Also,
the tracker at https://bugs.launchpad.net/mailman has feature
requests.

[4] http://mail.python.org/mailman/listinfo/mailman-users

-- 
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://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: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org