Re: [Mailman-Users] Archiving problems

[Mark Sapiro]

On 01/28/2015 07:15 PM, Bill Christensen wrote:

> Well, I had it all working on Monday night.
> 
> I got a report today that someone was getting "Forbidden" again.
> 
> The owner of the list in question (and only that one list, not any of
> the other publicly archived lists - which have not seen any posts in the
> last two days) had changed back from _www to root.  CHOWNing it back to
> _www again brings up the archive, but then it was only showing the last
> two days worth of archives (owner of those posts: _mailman, the rest
> were root).  Rebuilding the archives with --wipe and running Check perms
> -f (which is already cron jobbed to run every night) made the rest of
> them visible again.
> 
> What do i need to do so that I don't have to jump these hoops daily?
>

Have you tried running Mailman's bin/check_perms?

Here's what you should have in the way of ownership and permissions.
Group should be _mailman on everything. 'owner' doesn't matter except in
the one case where I indicate _www. SETGID bits are important.

drwxrwsr-x  owner _mailman  /path/to/mailman

drwxrwsr-x  owner _mailman  /path/to/mailman/archives

drwxrwsr-x  owner _mailman  /path/to/mailman/archives/

drwxrwsr-x  owner _mailman  /path/to/mailman/archives/public
 and only symlinks in this directory

Either
drwxrws--x  owner _mailman  /path/to/mailman/archives/private
or
drwxrws---  _www  _mailman  /path/to/mailman/archives/private

If you want to protect against access to private archives by local users
of the machine, you want the latter. Otherwise the former is fine.

drwxrwsr-x  owner _mailman  /path/to/mailman/archives/private/*

And similarly for subordinate /path/to/mailman/archives/private/*/*
directories.

-rw-rw-r--  owner _mailman  for most files subordinate to
/path/to/mailman/archives/private/*.


Again, SETGID bits are important.

-- 
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] Archiving problems

[Bill Christensen]

On 1/26/15 11:27 PM, Mark Sapiro wrote:

On 01/26/2015 09:12 PM, Bill Christensen wrote:

All the archives work when in private state.  But I had to manually
change the owner of all the publicly available list archives to _www in
private in order for them to be readable.  Otherwise they get a big
"Forbidden" message.  Should *all* the lists be _www? Everything in
archives/private, or just the archive folders and not the mbox folders?
The archives/private folder itself is already _www.

Thanks for your continued tolerance and assistance.


For public archives to work, the web server needs to be able to search
the archives/private directory that the archives/public/ symlinks point
into.

Normally this only requires that the archives/private/ directory itself,
not any subordinates, be either o+x or owned by the web server user. The
subordinate LISTNAME and LISTNAME.mbox directories are normally
rwxrwsr-x and Mailman's group so Mailman can read and write them and
subordinates will be created in Mailman's group and the web server can
read and search them.

It's only archives/private itself which is in Mailman's group and either
rwxrws--x or if rwxrws---, owned by the web server user. Otherwise,
ownership doesn't matter.

See .


Well, I had it all working on Monday night.

I got a report today that someone was getting "Forbidden" again.

The owner of the list in question (and only that one list, not any of 
the other publicly archived lists - which have not seen any posts in the 
last two days) had changed back from _www to root.  CHOWNing it back to 
_www again brings up the archive, but then it was only showing the last 
two days worth of archives (owner of those posts: _mailman, the rest 
were root).  Rebuilding the archives with --wipe and running Check perms 
-f (which is already cron jobbed to run every night) made the rest of 
them visible again.


What do i need to do so that I don't have to jump these hoops daily?

Thanks yet again.





--
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] Archiving problems

[Mark Sapiro]

On 01/26/2015 09:12 PM, Bill Christensen wrote:
> 
> All the archives work when in private state.  But I had to manually
> change the owner of all the publicly available list archives to _www in
> private in order for them to be readable.  Otherwise they get a big
> "Forbidden" message.  Should *all* the lists be _www? Everything in
> archives/private, or just the archive folders and not the mbox folders? 
> The archives/private folder itself is already _www.
> 
> Thanks for your continued tolerance and assistance.


For public archives to work, the web server needs to be able to search
the archives/private directory that the archives/public/ symlinks point
into.

Normally this only requires that the archives/private/ directory itself,
not any subordinates, be either o+x or owned by the web server user. The
subordinate LISTNAME and LISTNAME.mbox directories are normally
rwxrwsr-x and Mailman's group so Mailman can read and write them and
subordinates will be created in Mailman's group and the web server can
read and search them.

It's only archives/private itself which is in Mailman's group and either
rwxrws--x or if rwxrws---, owned by the web server user. Otherwise,
ownership doesn't matter.

See .

-- 
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] Archiving problems

[Bill Christensen]

On 1/26/15 9:32 PM, Mark Sapiro wrote:

On 01/26/2015 06:08 PM, Mark Sapiro wrote:

You weren't supposed to remove/move archives/private, just the
subordinate listname directories.


And once again, I misspoke (mistyped). I again meant the subordinate
listname directories under archives/public, not archives/private.

Mailman expects archives/public to exist, but the subordinates which are
supposed to be symlinks into archives/private are checked and
added/removed if necessary each time the list object is saved because
the list's archive_private setting might have changed necessitating the
addition or removal of symlinks.


Ok.

I put the archives/public folder back.

Toggling the archives setting on the publicly archived lists from public 
to private and back again created the symlinks.  So far so good.


All the archives work when in private state.  But I had to manually 
change the owner of all the publicly available list archives to _www in 
private in order for them to be readable.  Otherwise they get a big 
"Forbidden" message.  Should *all* the lists be _www? Everything in 
archives/private, or just the archive folders and not the mbox folders?  
The archives/private folder itself is already _www.


Thanks for your continued tolerance and assistance.


--
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] Archiving problems

[Mark Sapiro]

On 01/26/2015 06:08 PM, Mark Sapiro wrote:
> 
> You weren't supposed to remove/move archives/private, just the
> subordinate listname directories.


And once again, I misspoke (mistyped). I again meant the subordinate
listname directories under archives/public, not archives/private.

Mailman expects archives/public to exist, but the subordinates which are
supposed to be symlinks into archives/private are checked and
added/removed if necessary each time the list object is saved because
the list's archive_private setting might have changed necessitating the
addition or removal of symlinks.

-- 
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] Archiving problems

[Mark Sapiro]

On 01/26/2015 06:00 PM, Bill Christensen wrote:

> Ok, I removed the public archives.  I didn't rm -r, just copied them
> elsewhere in case this didn't work.
...

> The public archive folder didn't rebuild.
> 
> Tail on the error log says:
> 
>  mlist.Save()
> 
>   File "/opt/local/share/mailman/Mailman/MailList.py", line 574, in Save
> 
> self.CheckHTMLArchiveDir()
> 
>   File "/opt/local/share/mailman/Mailman/Archiver/Archiver.py", line
> 241, in CheckHTMLArchiveDir
> 
> makelink(privdir, pubdir)
> 
>   File "/opt/local/share/mailman/Mailman/Archiver/Archiver.py", line 49,
> in makelink
> 
> os.symlink(old, new)
> 
> OSError: [Errno 2] No such file or directory
> 
> 
> Your thoughts?  FYI, this is on Mac 10.9.5, non-server version, if that
> makes any difference.


You weren't supposed to remove/move archives/private, just the
subordinate listname directories.

-- 
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] Archiving problems

[Bill Christensen]

On 1/25/15 7:27 PM, Mark Sapiro wrote:

On 01/25/2015 05:21 PM, Stephen J. Turnbull wrote:

Mark Sapiro writes:

  > The solution is simple:
  >
  > rm -r archives/private/*

You mean "rm -r archives/public/*", don't you?  As given it erases all
the data, no?


Oh My yes! Absolutely! I hope nobody does the former. Thanks for
catching this Steve.

Ok, I removed the public archives.  I didn't rm -r, just copied them 
elsewhere in case this didn't work.


Our digest goes out at noon (and did).  I assume that qualifies as "the 
next time it does anything to the list".   Four new messages went 
through the list since then as well.


The public archive folder didn't rebuild.

Tail on the error log says:

 mlist.Save()

  File "/opt/local/share/mailman/Mailman/MailList.py", line 574, in Save

self.CheckHTMLArchiveDir()

  File "/opt/local/share/mailman/Mailman/Archiver/Archiver.py", line 
241, in CheckHTMLArchiveDir


makelink(privdir, pubdir)

  File "/opt/local/share/mailman/Mailman/Archiver/Archiver.py", line 
49, in makelink


os.symlink(old, new)

OSError: [Errno 2] No such file or directory


Your thoughts?  FYI, this is on Mac 10.9.5, non-server version, if that 
makes any difference.




--
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] Archiving problems

[Mark Sapiro]

On 01/25/2015 05:21 PM, Stephen J. Turnbull wrote:
> Mark Sapiro writes:
> 
>  > The solution is simple:
>  > 
>  > rm -r archives/private/*
> 
> You mean "rm -r archives/public/*", don't you?  As given it erases all
> the data, no?


Oh My yes! Absolutely! I hope nobody does the former. Thanks for
catching this Steve.

-- 
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] Archiving problems

[Stephen J. Turnbull]

Mark Sapiro writes:

 > The solution is simple:
 > 
 > rm -r archives/private/*

You mean "rm -r archives/public/*", don't you?  As given it erases all
the data, no?



--
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] Archiving problems

[Mark Sapiro]

On 01/25/2015 03:45 PM, Bill Christensen wrote:
> 
> I was able to bring most of the archives up to date manually, but one
> fairly active one with public archives is still only showing through
> October 2014.   When I run that manually it shows that it's processing
> posts beyond the last one seen in the web-visible archives and updates
> the index for 1st quarter 2015, but still no visibility and the files in
> archive/public aren't updated.  The files in archive/private *are*
> updated...
> 
> How do I make the public archives reflect what's in private?


At some point you moved or copied the archives and instead of copying
the symlinks in archives/public as symlinks, you copied the target data
which is never updated.

The ONLY thing that ever should be in archives/public/ is symlinks to
the corresponding items in archives/private/.

The solution is simple:

rm -r archives/private/*

Mailman will automatically recreate the necessary archives/public/
symlinks for each publicly archived list the next time it does anything
to the list.

-- 
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] archiving an other list

[jdd]

Le 21/11/2014 16:59, Mark Sapiro a écrit :


to subscribe yourself. A list can have no members and will still accept
and archive posts.


oh, yes, I wanted to subscribe to have posts accepted :-)

jdd
--
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] archiving an other list

[Mark Sapiro]

On 11/21/2014 12:19 AM, jdd wrote:
> Le 21/11/2014 00:08, Mark Sapiro a écrit :

>>
>>> is there anything I can do not to break anything :-)
>>
>>
>> I think the above covers it.
>>
> seen, thanks!!

A couple more things. Be sure to turn off password reminders either for
the list or for the other_list-bounces member, and you don't really need
to subscribe yourself. A list can have no members and will still accept
and archive posts.

-- 
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] archiving an other list

[jdd]

Le 21/11/2014 00:08, Mark Sapiro a écrit :


Also, if the archive can be public, see .


I know it, but it don't works (never receive the confirmation mail), I 
don't know why :-(






is there anything I can do not to break anything :-)



I think the above covers it.


seen, thanks!!

jdd
--
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] archiving an other list

[Mark Sapiro]

On 11/20/2014 08:21 AM, jdd wrote:
> 
> so I wonder if I could use my mailman instance, for example creating a
> dummy mailing list with only me as subscriber to send it every mail from
> my group and have it archived (of course with the group owner consent).


This will work, but you will also want to subscribe
 (or possibly
 if the other list
is VERPing) to your list and set it to no mail to avoid have posts held
for not being from a member and avoid accepting nonmember posts.

Also, if the archive can be public, see .


> is there anything I can do not to break anything :-)


I think the above covers it.

-- 
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] Archiving : 2 Questions

[Mark Sapiro]

On 11/06/2014 10:20 AM, John Young wrote:
> Sorry, I should have noted that the current archives are in month batches 
> which is what we are after for all of our mail lists.
> 
> - archiving
> - monthly
> - private (admins only)


Private archives are available to any list member who authenticates with
her list password.

There is no setting that makes an archive available to the list admin only.


> On 7/11/2014, at 7:17 am, John Young  wrote:
> 
>> 1 - We want to enable private archiving on all of our mailman lists.  Some 
>> already have archiving , most don’t.  But we want this enabled on all so we 
>> have the ability to go through the postings.


Put the following 3 lines in a file

archive = 1
archive_private = 1
archive_volume_frequency = 1

Then run the following shell script

#! /bin/sh
for list in `/path/to/mailman/bin/list_lists --bare` ; do
/path/to/mailman/bin/config_list -i /path/to/above/file $list
done


>> 2 - We want to purge all our existing archives older than a certain date.


See the script at 

-- 
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] Archiving : 2 Questions

[John Young]

Sorry, I should have noted that the current archives are in month batches which 
is what we are after for all of our mail lists.

- archiving
- monthly
- private (admins only)

Thanks again 

John

On 7/11/2014, at 7:17 am, John Young  wrote:

> Hiya,
> 
> I’m brand new to this list and was hoping for some direction.
> 
> I’ve read through a heap of archives but can’t quite find the correct answers 
> (or am searching for the wrong terms!)
> 
> 1 - We want to enable private archiving on all of our mailman lists.  Some 
> already have archiving , most don’t.  But we want this enabled on all so we 
> have the ability to go through the postings.
> 
> 2 - We want to purge all our existing archives older than a certain date.
> 
> Kind regards
> 
> John

--
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] archiving gets "shunted"

[Mark Sapiro]

Lucio Chiappetti wrote:
>
>>> The other question is that if I send a message to a list, the member
>>> receive it, but the message is NOT archived.
>>>
>>>I see that a file appears in qfiles/shunt/
>
>> Have you run Mailman's bin/check_perms?
>
>yes I did. As a result of the first run, as instructed in manual, I did
>
> cd /var/lib/mailman/archives/
> chown wwwrun private
> chmod o-x private
>
>and re-run it again.
>(wwwrun is the suse user under which apache runs)


While the above changes result in the most secure configuration, they
are only necessary (as opposed to o+x) if you have a multi-user system
and you are concerned about local users being able to access private
archives.


>I see now that the default configuration of the list is archive=yes
>archive_private=public.
>
>I see there are directories archive/private/listname, 
>archive/private/listname.mbox and public/listname. The latter is a 
>softlink to private. Is this normal ?


Yes, this is exactly as it should be. archives/private/listname.mbox
contains a single file archives/private/listname.mbox/listname.mbox
which is a unix mbox containing all archived posts to the list and
which can be used as input to bin/arch to rebuild the pipermail
archive which is in archives/private/listname/.

The symlinks in archives/public/ exist only for lists with public
archives and are used by the web server to serve public archive pages
without authentication. These are maintained automatically by Mailman
as the list archives are changed from public to private or vice versa.

The actual archive is always in archives/private.


>All of them are setgid directories owned by wwwrun.mailman except for 
>those of list mailman which are owned by root.mailman, but I guess such 
>list is special, and will have no traffic to be archived.


The owner doesn't matter. Only the group. The 'mailman' list is not
special in this case and can have archives. The ownership difference
is because the mailman list was created with bin/newlist (by root)
whereas the others were created by the web CGI.


>As a result of posting the first message to the list, a file listname.mbox 
>is created in archive/private/listname.mbox (why private ?) and it contain 
>the messages. But the index.html is not updated. A message is shunted, 
>and the attached errors are generated.


The HTML is not updated because the exception occurs after the
listname.mbox file is (created and) written, but before the HTML
archive is updated.

The underlying problem is the same Mailman 2.1.11/Python2.6.5
incompatibility I mentioned in the 'bug adding user, and archiving
gets "shunted"' thread.

-- 
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
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] Archiving

[Mark Sapiro]

Stephens, Clyde wrote:

>How do change the number of Archive files that are kept?  Currently only the 
>last 5 months are being kept on our system.


Removal of older archives is not a Mailman feature. This is most likely
being done by some shell script which runs periodically (via cron?)
and removes the older files.

-- 
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
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Archiving is broken

[Mark Sapiro]

Mark Heer wrote:
> 
> The bigger issue is the complete lack of archiving.   even public 
> lists which used to archive just fine are not doing anything.  You 
> may recall that you provided the syntax for the external 
> prvate/public archive entry I placed in the mmcfg.py file.  It worked
>  perfeclty for over a month and simply stopped workin 8/12.  Can you 
> offer some debug advice or some way of unwedging the archive routine?
>  I feel really stuck.  I have been archiving to our old hypermail 
> setup until I can unravel this problem. As I mentioned, the only 
> change on 8/12 was to change 1 list to yearly vs monthly after which 
> I recreated the archive from a flat file (mm mbos with hypermail flat
>  file catted to the end). could this be a factor?


And in another message


> Sorry, I should clarify our installation -  we have 2 mail servers
> handling the mail exchanges and 1 server handling the admin functions
> all are running mailman.  When the mail servers send to the external
> archive they send to our admin mailman server which accepts the piped
> mail and runs the /bin/arch script populating the pipermail archive.
> The key on the admin machine receives the piped mail and does the
> right thing - all until lat week.  I ran the /bin/arch to re-create
> the archive as a yearly archive on the receiving side or - admin
> machine, not on the mail exchangers.

It's possible that your rebuilding of the archive caused permissions
issues if you didn't run bin/arch as the mailman user. Since this is all
you did, it seems worth investigating.

As far as debugging the 'external' archiving from the mail machines to
the admin machine is concerned, did you try running the command manually
as I suggested in a prior reply.

If the external archiver fails, there should be a "external archiver
non-zero exit status: %d" message in Mailman's error log on the mail
machine, but more likely, the ssh command succeeds and the failure is in
the script on the admin machine which at best you might see as output if
you run the ssh by hand.

If your script on the admin machine is like the one at
,
you could try changing

  bin/arch $1 $f

or whatever similar command you have to something like

  bin/arch $1 $f >>/path/to/log/file 2>>/path/to/log/error

to see what the command is actually doing.

-- 
Mark Sapiro <[EMAIL PROTECTED]>The 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
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Archiving is broken

[Mark Sapiro]

Mark Heer wrote:
>
>I only get the following error for a few lists but in each case the ownership 
>is mailman:mailman
>I noted an error re: ownership problems - but mailman user and group do indeed 
>own the dirs/files so that message is confusing : 
>sr/local/mailman/archives/public/wan-data-transfers'
>Aug 20 09:31:06 2008 (27219) Traceback (most recent call last):
>  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 114, in _oneloop
>self._onefile(msg, msgdata)
>  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 185, in _onefile
>keepqueued = self._dispose(mlist, msg, msgdata)
>  File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 133, in 
> _dispose
>mlist.Save()
>  File "/usr/local/mailman/Mailman/MailList.py", line 568, in Save
>self.CheckHTMLArchiveDir()
>  File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 236, in 
> CheckHTMLArchiveDir
>breaklink(pubdir)
>  File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 56, in breaklink
>os.unlink(link)
>OSError: [Errno 1] Not owner: 
>'/usr/local/mailman/archives/public/wan-data-transfers'
>
>Aug 20 09:31:06 2008 (27219) SHUNTING: 
>1219249865.3392961+47525c120442e9f4bd836c09cd41c46b6feb351e


It appears that at some point, the archive of this list
(wan-data-transfers) was changed from public to private and now
mailman is trying to remove the symlink from
/usr/local/mailman/archives/public/wan-data-transfers to
/usr/local/mailman/archives/prvate/wan-data-transfers. It is being
denied by the OS when it tries to do this.

This may be a permissions issue not checked by check_perms or it may be
a SELinux or other security policy manager issue or it may be that
IncomingRunner was not started properly (i.e. by 'mailmanctl start'
run by root) and is not running as the correct user:group.

-- 
Mark Sapiro <[EMAIL PROTECTED]>The 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
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Archiving to 3rd machine

[Mark Sapiro]

Mark Heer wrote:
>
>I'd like to have all archives sent to one system.  Currently we use hypermail 
>for this but as we move to mailman it will be necessary to retain this sort of 
> architecture.   Can mailman be configured to have mailserver1 and mailserver2 
>send archives
>to adminmachine3 ?  (all 3 running mailman).  One posssibility as noted in the 
>faq is using MHonArc - but could I use similar 
>PUBLIC_EXTERNAL_ARCHIVER configs to point to adminmachine3 using mailman's 
>pipermail?  


Just off the top of my head, you could try something on machines 1 and
2 like

PUBLIC_EXTERNAL_ARCHIVER = 'ssh -e none [EMAIL PROTECTED] "script
%(listname)s"'

(all on one line), and similarly for PRIVATE_EXTERNAL_ARCHIVER, where
script would be on machine3 and would be something like

#!/bin/sh
f=`mktemp`
cat > $f
bin/arch $1 $f
rm $f

Of course, it wouldn't have to be ssh and could be it's own script, but
just something to push the message to a script on machine 3 which
would copy the message to a file and feed it to bin/arch for the
correct list.

-- 
Mark Sapiro <[EMAIL PROTECTED]>The 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://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Archiving only certain topics and/or the "default"topic

[Mark Sapiro]

Kelly Jones wrote:

>I admin a mailing list that receives two types of messages:
>
>1. Important human-typed messages that should be archived
>
>2. Transient machine-generated messages that people may want to read,
>but which lose value rapidly, and, therefore, shouldn't be archived.
>
>I've set up topics so that all the transient messages have their own
>topic (they're machine-generated so the subjects always match known
>regexps).


Don't do this with topics. The topics may be OK for other reasons, but
for archiving there is a better way (using topics to control archiving
will require code modification or a custom handler).

Have your machine generated messages include an X-No-Archive: header
and they won't be archived. Headers that will work to not archive
messages are

X-No-Archive: Yes
X-No-Archive: any value
X-Archive: No

They are not case sensitive.

-- 
Mark Sapiro <[EMAIL PROTECTED]>   The 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://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] archiving turned off, attachments still saved

[Mark Sapiro]

Richard Kirkcaldy wrote:

>Am I missing something here?  I've got archiving set to private and
>turned off for one particular list, and it's quite rightly not
>archiving.  However, it is saving attachments in the form
>private/listname/attachments/mmdd/hash.
>
>Is there a reason these attachments are being saved?  And is there a
>way I can stop them being saved?  And can I simply delete them,
>possibly with a cron job?


Yes, there is a reason. Attachments are removed and stored in the
archives/private/listname/attachments/ directory by 'Scrubber'.
Scrubber is invoked in 3 ways to do this.

1) if Non-digest options->scrub_nondigest is Yes, all messages will be
scrubbed in incoming message processing.

2) messages are scrubbed in digest processing for the 'plain' format
digest.

3) messages are scrubbed for the pipermail archiving.

If you don't want any attachments scrubbed and saved, you have to be
sure scrub_nondigest is No, archiving is off, and the list is not
digestable (digestable = No on Digest options).

You can delete them, but then they won't be available to digest
subscribers whose digests have links to them.

-- 
Mark Sapiro <[EMAIL PROTECTED]>   The 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://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] archiving partial duplicates

[Mark Sapiro]

Patrick Bogen wrote:
>
>Bash can do this for you:
>
>#!/bin/bash
>bin/arch --wipe

>
>...Assuming that bin/arch --wipe alone does what I think it does.

It needs to be

bin/arch --wipe listname /dev/null

listname is always required. The next argument is the .mbox file which
defaults to the archives/private/listname.mbox/listname.mbox file if
ommitted.

-- 
Mark Sapiro <[EMAIL PROTECTED]>   The 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://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] archiving partial duplicates

[Mark Sapiro]

Con Wieland wrote:
>
>When I checked the archives for the  
>current month a number of partial messages showed up with no from  
>line and no date.
>
>Any idea's on what to look for would be appreciated.


Look for messages containing unescaped "From " lines in the body.

The bin/cleanarch script can help with fixing a .mbox file that
contains these.

-- 
Mark Sapiro <[EMAIL PROTECTED]>   The 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://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] archiving partial duplicates

[Dragon]

Patrick Bogen sent the message below at 08:18 4/7/2006:
>On 4/6/06, Dragon <[EMAIL PROTECTED]> wrote:
> > So if you decided 500 was a good number to index, for the first chunk
> > you would do:
> >
> >  bin/arch --wipe --start=1 --end=500 listname
> >
> > For subsequent chunks you would do (adjusting the start and end
> > indexes of course...):
> >
> >  bin/arch --start=501 --end=1000 listname
> >
>
>Bash can do this for you:
>
>#!/bin/bash
>bin/arch --wipe
>for i in `seq 0 10`
>do
> bin/arch --start=$(( 1+$i*500 )) --end=$(( 500+$i*500 )) listname
>done
>
>...Assuming that bin/arch --wipe alone does what I think it does.
>Also, if you have more than 5500 messages in the mbox file, you'll
>need to adjust the second argument in the 'seq' upwards. And, of
>course, replace 'listname' with the list name.
 End original message. -

Or Perl or Python or whatever your favorite scripting language might be...

But that's just icing on the cake and not really a necessity.

The --wipe argument deletes all the old files and builds new ones. 
Which is great but ii did have one unfortunate consequence for me. I 
am using htdig to allow search of my archives and when I rebuilt the 
archives after editing the templates and installing htdig, all of the 
file dates on the messages were set to the date I rebuilt the 
archive. This destroyed the date context for the archive and the file 
dates displayed by the htdig search were not reflecting when the 
message was originally posted.

So, I wrote a small Perl script to "fix" the file dates to match the 
message date in each of the message files. If anyone is interested in 
that script, I would be happy to share it with you. Just e-mail me 
directly and I will send it to you.

Dragon

~~~
  Venimus, Saltavimus, Bibimus (et naribus canium capti sumus)
~~~

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] archiving partial duplicates

[Patrick Bogen]

On 4/6/06, Dragon <[EMAIL PROTECTED]> wrote:
> So if you decided 500 was a good number to index, for the first chunk
> you would do:
>
>  bin/arch --wipe --start=1 --end=500 listname
>
> For subsequent chunks you would do (adjusting the start and end
> indexes of course...):
>
>  bin/arch --start=501 --end=1000 listname
>

Bash can do this for you:

#!/bin/bash
bin/arch --wipe
for i in `seq 0 10`
do
bin/arch --start=$(( 1+$i*500 )) --end=$(( 500+$i*500 )) listname
done

...Assuming that bin/arch --wipe alone does what I think it does.
Also, if you have more than 5500 messages in the mbox file, you'll
need to adjust the second argument in the 'seq' upwards. And, of
course, replace 'listname' with the list name.

--
- Patrick Bogen
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] archiving partial duplicates

[Dragon]

Con Wieland sent the message below at 11:50 4/6/2006:
>Hello,
>
>I'm having trouble with one of my archives. This archive is about 5
>years old and is fairly large. The problem is I recently had to
>remove a message and reindex. When I checked the archives for the
>current month a number of partial messages showed up with no from
>line and no date. These actually turned out to be chunks from some
>very old messages. I am confused though because the original message
>shows up fine and the current month's archive shows an incomplete
>portion of the old message. I'm assuming it's a corrupt message but I
>don't understand why it's showing up in both places. I have a couple
>dozen of these. I don't know if this existed before my last arch
>rebuild.  I have gone through several of these and am not able to see
>anything unusual. I have also checked the messages preceding and
>after the messages in question to no avail.
>
>Any idea's on what to look for would be appreciated.
 End original message. -

I am just kinda guessing here but there is a caveat somewhere in the 
documentation about pipermail or the arch script that it has trouble 
digesting large MBOX files at a single gulp. It may be that this is 
the cause of the problem, it may not.

It is also stated somewhere in the documentation for either pipermail 
or the arch script that you can specify a start and end index for a 
chunk of messages in the MBOX file. What you could then do is rebuild 
the archive in chunks, say 500 posts at a time to see what happens.

So if you decided 500 was a good number to index, for the first chunk 
you would do:

 bin/arch --wipe --start=1 --end=500 listname

For subsequent chunks you would do (adjusting the start and end 
indexes of course...):

 bin/arch --start=501 --end=1000 listname

Hope that helps.

Dragon

~~~
  Venimus, Saltavimus, Bibimus (et naribus canium capti sumus)
~~~

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Archiving Question

[Mark Sapiro]

Jeff Edwards wrote:
>I would like for
>the content of the HTML to appear on the HTML page for that message, rather
>than requiring an extra clickthrough to see half the message. Is it possible
>to make Mailman do this?


You need to use an external archiver. See
.

The issue is that Pipermail does not handle multipart messages so they
have to be scrubbed to a single text/plain part before being archived.
Content filtering with HTML to plain text conversion can help, but
often because of character set issues, the converted part is scrubbed
anyway.

-- 
Mark Sapiro <[EMAIL PROTECTED]>   The 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://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Archiving

[David]

Ok Thanks I was just finding this out in the FAQ (Who ever checks these 
thingsSorry) and the List Home Page.  How ever I see it is on the 
wish list for 2.2 or 3.0 or some future release so I think I am just 
gonna go ahead archive as the list is new on a new site and by the time 
the archives get unruly that option should be available and I should be 
fine.  Thanks again!!

 Thanks David

Mark Sapiro wrote:
> David wrote:
>
>   
>> Im on a hosted server.  I am trying to decide if I want to archive my 
>> lists or not.  I don't seem to see any place that allows trimming the 
>> archives if they start taking up too much space or just get too many in 
>> general if I want to do it on weekly basis.  Is that option available 
>> some place? 
>> 
>
> There is no option within Mailman to prune old messages from the
> archives.
>
>   

-- 
No Smoking Forum - Http://www.nicodemon.info/community
Lansing Forum - Http://www.greater-lansing.com/community

He's Not My President!!!
Blue States Rock~



--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Archiving

[Christopher X. Candreva]

On Fri, 21 Oct 2005, Mark Sapiro wrote:

> >lists or not.  I don't seem to see any place that allows trimming the 
> >archives if they start taking up too much space or just get too many in 
> >general if I want to do it on weekly basis.  Is that option available 
> >some place? 
> 
> There is no option within Mailman to prune old messages from the
> archives.

If the archive file is just an mbox file, you should be able to use any mail 
program that uses mbox format to remove messages -- mail, elm, pine, etc.

Then regenerate the web archive.

-Chris

==
Chris Candreva  -- [EMAIL PROTECTED] -- (914) 967-7816
WestNet Internet Services of Westchester
http://www.westnet.com/
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] Archiving

[Mark Sapiro]

David wrote:

>Im on a hosted server.  I am trying to decide if I want to archive my 
>lists or not.  I don't seem to see any place that allows trimming the 
>archives if they start taking up too much space or just get too many in 
>general if I want to do it on weekly basis.  Is that option available 
>some place? 

There is no option within Mailman to prune old messages from the
archives.

-- 
Mark Sapiro <[EMAIL PROTECTED]>   The 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://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: 
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] archiving attachments via 3rd party software with no mailbox access

[Brad Knowles]

At 1:44 PM -0800 2005-02-17, Chuq Von Rospach wrote:
 check out MHonarc. (www.mhonarc.org). It should do what you want.
	But doesn't that require administrative privileges to install? 
Doesn't that require shell access to the server?  My understanding is 
that these are two things that the OP doesn't have, which means that 
I don't think there are any solutions that anyone can offer to him.

--
Brad Knowles, <[EMAIL PROTECTED]>
"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."
-- Benjamin Franklin (1706-1790), reply of the Pennsylvania
Assembly to the Governor, November 11, 1755
  SAGE member since 1995.  See  for more info.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] archiving attachments via 3rd party software with no mailbox access

[Brad Knowles]

At 11:11 AM -0800 2005-02-08, Robert Flach wrote:
 Unfortunately, all of the solutions in the FAQ (which I checked
 before posting) require either access to mailboxes or access to the
 Mailman internals, neither of which I have in my current setup.
	So far as I know, there are no other alternatives.  You could ask 
your hosting provider to install something for you, or you could move 
to a different hosting provider.

--
Brad Knowles, <[EMAIL PROTECTED]>
"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."
-- Benjamin Franklin (1706-1790), reply of the Pennsylvania
Assembly to the Governor, November 11, 1755
  SAGE member since 1995.  See  for more info.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] archiving attachments via 3rd party software with no mailbox access

[Chuq Von Rospach]

check out MHonarc. (www.mhonarc.org). It should do what you want.
On Feb 8, 2005, at 11:11 AM, Robert Flach wrote:
Unfortunately, all of the solutions in the FAQ (which I checked before 
posting) require either access to mailboxes or access to the Mailman 
internals, neither of which I have in my current setup.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] archiving attachments via 3rd party software with no mailbox access

[Robert Flach]

Unfortunately, all of the solutions in the FAQ (which I checked before 
posting) require either access to mailboxes or access to the Mailman 
internals, neither of which I have in my current setup.

Mark Sapiro wrote:
Robert Flach wrote:
 

 
 Need:  I need to archive messages in a way that retains attachments 
(preferably as separate files with link inserted into message)
   

Have you seen
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.004.htp ?
There might be something there you can use.

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.027.htp

Re: [Mailman-Users] archiving attachments via 3rd party software withno mailbox access

[Mark Sapiro]

Robert Flach wrote:
>   
>   Need:  I need to archive messages in a way that retains attachments 
>(preferably as separate files with link inserted into message)

Have you seen
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.004.htp ?
 There might be something there you can use.

--
Mark Sapiro <[EMAIL PROTECTED]>   The 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://www.python.org/cgi-bin/faqw-mm.py
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] archiving on mailman

[Tokio Kikuchi]

Ako Ito wrote:
hello sir,
whenever I access it through the archives it gets relinked to certain
location where the extension is either .obj or .bin ..problem is whenever a
user is accessing it.. he is asked on what application to open it with.. can
this prevented... that is still retains its attachments original extension
files. ex. .xls .doc? thanks for the prompt response...
Mailman archiver is designed to attain safety against malicious files
like viruses. Typical virus mail has an attachment like this:
--=_NextPart_000_001B_01C0CA80.6B015D10
Content-Type: audio/x-wav;
name="message.scr"
Content-Transfer-Encoding: base64
Content-ID: <[EMAIL PROTECTED]>
TVqQAAME//8AALgAQAAA
Windows will execute this code if the extension is kept as .scr
which is not an audio/x-wav file extension.
Some mailers are not compliant with the IANA registered mime extension
and put application/octet-stream content-type for excel or msword.
In this case, mailman is very cautious not to trust the original
extention and change it to .bin. If these files are sent by a compliant
mailer like netscape, the content-type will be application/msword or
application/vnd.ms-excel and the extension will become .doc or .xls.
So, if you really don't care the safety, you must hack the code at your
own risk.
Oh, there is an option to use an external archiver...
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.003.htp
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

Re: [Mailman-Users] archiving on mailman

[Tokio Kikuchi]

Ako Ito wrote:
hello gurus,
is it possible on mailman 2.1.4 to not scrubbed the mailman attachments on the 
archives? just leave it as is? if not what other solutions do i need to undertake for 
me accomplish this?
So, how do you retrieve the attachments from the archive ?
Without scrubbing, you will get MIME Base64 strings on the archived
message page.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

Re: [Mailman-Users] Archiving

[Jon Carnes]

On Fri, 2003-10-17 at 05:36, Geert De Pecker wrote:
> Hi,
> 
> I'm new to this list (and mailman). Just installed the mailman 2.1.3
> with the htdig extensions. Seems to work ok, but I can't find how I can
> set the archiving frequency. Should I put bin/arch in the crontab, or is
> there a setting somewhere that I forgot? I had the impression that with
> the former version I had on the machine, messages showed up in the
> archive immediately.
> 
> Any hints?
> 
> Thanks,
> 
> Geert

In this version of Mailman, Archiving is a function of one of the
qrunner's controlled by Mailmanctl. It will move the messages into the
archives for you (assuming you have Archiving turned on for the list).

Arch should only be used if you want to manually re-archive a list.  I
use it mainly after hand editing the Archive Mbox file for a list.

You'll find a lot of discussion about archiving in the list Archives as
well as in the FAQ.

Good Luck.  I'm sure patience will bring all things to light.

Jon Carnes



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

RE: [Mailman-Users] archiving

[Sylvain Langlade]

>
> I had an archive up and running and doing fine. I did not
> change anything to
> the setting but messages are being send but not archived.
> Anyone have a hint
> as to what the problem might be?

IIRC, I once got this problem with HTML messages produced with standard
email client. If your list is configured to accept such messages without
stripping the HTML part, the message is not archived (you have to do it
manually with $prefix/bin/arch).

I had to configure all lists to strip out the HTML part of all incoming
message. Which leads to a problem for HTML-only messages produced by web
client like Hotmail...

So try to send a raw text message to your list and see if it appears in the
archives.

HTH


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] archiving

[Jon Carnes]

Check your cron to make sure it is still running.

Other than that, you will need to include more information:
  Version of Mailman that you are running, How it was installed (via
rpm, apt-get, source, provided by host), the MTA that you are using, and
the Operating System that your host is running.

Good luck - Jon Carnes
 
On Thu, 2003-08-07 at 06:06, webulous wrote:
> I had an archive up and running and doing fine. I did not change anything to
> the setting but messages are being send but not archived. Anyone have a hint
> as to what the problem might be?
> 
> Also does anyone know if it possible to have the number of messages in a
> thread mentioned in the archive.
> 
> thanks,
> 
> Jeroen
> 
> 
> --
> Mailman-Users mailing list
> [EMAIL PROTECTED]
> http://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> 
> This message was sent to: [EMAIL PROTECTED]
> Unsubscribe or change your options at
> http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Archiving doesn't work under Mac OS X 10.1

[Peter Bengtson]

Editing the sources in the indicated manner (plus adjusting the level 
of indentation of the remaining part of the function) indeed works. 
Editing i18n.py in the install directory doesn't suffice, however - it 
is necessary to edit the file in the distribution directory and then do 
a 'make install'. Anyway, thanks for the pointer!

However, should Mailman really require that strptime is defined? As it 
is now, archiving doesn't work _at_all_ in Mailman 2.x under Mac OS X 
10.1.

	/ Peter

On lördag, feb 22, 2003, at 22:36 Europe/Stockholm, Jon Carnes wrote:

The function is used only once in Mailman, inside i18n.py

  year, mon, day, hh, mm, ss, wday, ydat, dst = time.strptime(date)

You could easily replace this line of code with a small block that does
the same thing but without referencing the strptime function.
In fact, looking at the code, it looks like there is already an 
existing
block that would do this for you... Try deleting the 4 lines of code
that I marked with an *

if isinstance(date, StringType):
try:
*year, mon, day, hh, mm, ss, wday, ydat, dst =
time.strptime(date)
*tzname = time.tzname[dst and 1 or 0]
*except ValueError:
*try:
wday, mon, day, hms, year = date.split()
hh, mm, ss = hms.split(':')
year = int(year)
day = int(day)
hh = int(hh)
mm = int(mm)
ss = int(ss)
except ValueError:
return date
===
If that works then you won't need the time.strptime function at all.
Good Luck - Jon

BTW: good detective work tracing down the lack of strptime function in
Max OSX v10.1!
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Archiving doesn't work under Mac OS X 10.1

[Jon Carnes]

The function is used only once in Mailman, inside i18n.py

  year, mon, day, hh, mm, ss, wday, ydat, dst = time.strptime(date)

You could easily replace this line of code with a small block that does
the same thing but without referencing the strptime function.

In fact, looking at the code, it looks like there is already an existing
block that would do this for you... Try deleting the 4 lines of code
that I marked with an * 

if isinstance(date, StringType):
try:
*year, mon, day, hh, mm, ss, wday, ydat, dst = 
time.strptime(date)
*tzname = time.tzname[dst and 1 or 0]
*except ValueError:
*try:
wday, mon, day, hms, year = date.split()
hh, mm, ss = hms.split(':')
year = int(year)
day = int(day)
hh = int(hh)
mm = int(mm)
ss = int(ss)
except ValueError:
return date
===
If that works then you won't need the time.strptime function at all.

Good Luck - Jon 

BTW: good detective work tracing down the lack of strptime function in
Max OSX v10.1!

On Sat, 2003-02-22 at 09:40, Peter Bengtson wrote:
> Some time ago, I reported that archiving doesn't work in Mailman 2.1.1 
> under Mac OS X 10.1. Every attempt to archive a message would result in 
> the following entry in 'logs/error':
> 
> > Feb 22 00:15:42 2003 (1950) SHUNTING: 
> > 1045869340.680055+e0e16d1c92bfc3454ac70ca2586b40b6f9ba5a4e
> > Feb 22 15:20:28 2003 (1950) Uncaught runner exception: 'module' object 
> > has no attribute 'strptime'
> > Feb 22 15:20:28 2003 (1950) Traceback (most recent call last):
> >   File "/Users/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop
> > self._onefile(msg, msgdata)
> >   File "/Users/mailman/Mailman/Queue/Runner.py", line 155, in _onefile
> > keepqueued = self._dispose(mlist, msg, msgdata)
> >   File "/Users/mailman/Mailman/Queue/ArchRunner.py", line 73, in 
> > _dispose
> > mlist.ArchiveMail(msg)
> >   File "/Users/mailman/Mailman/Archiver/Archiver.py", line 207, in 
> > ArchiveMail
> > h.close()
> >   File "/Users/mailman/Mailman/Archiver/pipermail.py", line 304, in 
> > close
> > self.update_dirty_archives()
> >   File "/Users/mailman/Mailman/Archiver/pipermail.py", line 518, in 
> > update_dirty_archives
> > self.update_archive(i)
> >   File "/Users/mailman/Mailman/Archiver/HyperArch.py", line 1038, in 
> > update_archive
> > self.__super_update_archive(archive)
> >   File "/Users/mailman/Mailman/Archiver/pipermail.py", line 424, in 
> > update_archive
> > self._update_simple_index(hdr, archive, arcdir)
> >   File "/Users/mailman/Mailman/Archiver/pipermail.py", line 434, in 
> > _update_simple_index
> > self.write_index_header()
> >   File "/Users/mailman/Mailman/Archiver/HyperArch.py", line 955, in 
> > write_index_header
> > print self.html_head()
> >   File "/Users/mailman/Mailman/Archiver/HyperArch.py", line 640, in 
> > html_head
> > d = {"listname": html_quote(mlist.real_name, self.lang),
> >   File "/Users/mailman/Mailman/Archiver/HyperArch.py", line 638, in 
> > quotetime
> > return html_quote(i18n.ctime(s), self.lang)
> >   File "/Users/mailman/Mailman/i18n.py", line 98, in ctime
> > year, mon, day, hh, mm, ss, wday, ydat, dst = time.strptime(date)
> > AttributeError: 'module' object has no attribute 'strptime'
> 
> Further research shows that the offending function, strptime, doesn't 
> exist in Mac OS X 10.1 - the function isn't defined, which causes 
> HAVE_STRPTIME to become undefined by ./configure. (I don't know the 
> situation under 10.2.). Doing a
> 
>   python
>   import time
>   time.strptime
> 
> results in an error message, saying that strptime is an unknown entity.
> 
> At first I thought this might be a bug which only showed up when 
> archiving was set to something else than the distribution defaults, but 
> changing or removing the date clobbering settings in mm_cfg.py didn't 
> improve the situation. All archiving still seems to break.
> 
> A clean install of Python (2.2.2) doesn't improve the situation, either.
> 
> If 'strptime' is unavailable in 10.1, then all Mailman users under Mac 
> OS X 10.1 wouldn't be able to archive any messages at all. Are there 
> very few users on Mac OS X, or don't people generally use automatic 
> archiving? I would be interested to hear from anybody who has got it to 
> work under Mailman 2.x and Mac OS X 10.1.
> 
> Archiving used to work flawlessly - I have quite extensive archives 
> produced by a now defunct mailing list - but in one of the later 
> versions, presumable where the archiving routines were rewritten or 
> updated, it stopped working.
> 
> Should Mailman assume that 'strptime' is available? Is there a 
> workaround?
> 
> Any ideas or pointers most welcome.
> 
>   / Peter Bengtson
> 
> 
> --
> Mailman-Users maili

Re: [Mailman-Users] Archiving doesn't work + National chars inpasswords

[Peter Bengtson]

There are no mails in the queue, so that's not the answer either (I 
wouldn't report this as a bug or configuration issue if I hadn't checked 
the most obvious things first). My guess, as a programmer, is that 
something was changed in one of the late betas. The error message

>   AttributeError: 'module' object has no attribute 'strptime'

certainly indicates the issue is related to module handling.

	/ Peter

Jon Carnes wrote:
That being the case (it was working then it simply stopped) the problem
must be one of the emails in the queue.

On Sat, 2003-02-08 at 06:42, Peter Bengtson wrote:


Python 2.2 is indeed installed, so that can't be the issue. 
bin/check_perms reveals no problems either.

I've used the 2.1 alphas and betas for a long time without any problems. 
The archives stopped working fairly lately, but I'm not sure it happened 
when installing 2.1. It might have been a little earlier.

Any ideas? I need those archives.

		/ Peter Bengtson

Jon Carnes wrote:

What version of Python do you have installed?  Mailman v2.1.x needs
Python 2.2.x

It looks like you have a Python module that is incompatible with Mailman
v2.1:
  year, mon, day, hh, mm, ss, wday, ydat, dst = time.strptime(date)
  AttributeError: 'module' object has no attribute 'strptime'





--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com









--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Archiving doesn't work + National chars inpasswords

[Jon Carnes]

That being the case (it was working then it simply stopped) the problem
must be one of the emails in the queue.

On Sat, 2003-02-08 at 06:42, Peter Bengtson wrote:
> Python 2.2 is indeed installed, so that can't be the issue. 
> bin/check_perms reveals no problems either.
> 
> I've used the 2.1 alphas and betas for a long time without any problems. 
> The archives stopped working fairly lately, but I'm not sure it happened 
> when installing 2.1. It might have been a little earlier.
> 
> Any ideas? I need those archives.
> 
>   / Peter Bengtson
> 
> Jon Carnes wrote:
> > What version of Python do you have installed?  Mailman v2.1.x needs
> > Python 2.2.x
> > 
> > It looks like you have a Python module that is incompatible with Mailman
> > v2.1:
> >year, mon, day, hh, mm, ss, wday, ydat, dst = time.strptime(date)
> >AttributeError: 'module' object has no attribute 'strptime'
> 
> 
> 
> 
> --
> Mailman-Users mailing list
> [EMAIL PROTECTED]
> http://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> 
> This message was sent to: [EMAIL PROTECTED]
> Unsubscribe or change your options at
> http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Archiving doesn't work + National charsinpasswords

[Danny Terweij]

> Jon Carnes wrote:
> > What version of Python do you have installed?  Mailman v2.1.x needs
> > Python 2.2.x
> >
> > It looks like you have a Python module that is incompatible with Mailman
> > v2.1:
> >year, mon, day, hh, mm, ss, wday, ydat, dst = time.strptime(date)
> >AttributeError: 'module' object has no attribute 'strptime'

Can a python version check be buildin when you do a ./configure or make ?
So it does not install if no good python is on the system?

Danny.




--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Archiving doesn't work + National chars inpasswords

[Peter Bengtson]

Python 2.2 is indeed installed, so that can't be the issue. 
bin/check_perms reveals no problems either.

I've used the 2.1 alphas and betas for a long time without any problems. 
The archives stopped working fairly lately, but I'm not sure it happened 
when installing 2.1. It might have been a little earlier.

Any ideas? I need those archives.

		/ Peter Bengtson

Jon Carnes wrote:
What version of Python do you have installed?  Mailman v2.1.x needs
Python 2.2.x

It looks like you have a Python module that is incompatible with Mailman
v2.1:
   year, mon, day, hh, mm, ss, wday, ydat, dst = time.strptime(date)
   AttributeError: 'module' object has no attribute 'strptime'





--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Archiving doesn't work + National chars inpasswords

[Jon Carnes]

What version of Python do you have installed?  Mailman v2.1.x needs
Python 2.2.x

It looks like you have a Python module that is incompatible with Mailman
v2.1:
   year, mon, day, hh, mm, ss, wday, ydat, dst = time.strptime(date)
   AttributeError: 'module' object has no attribute 'strptime'

===
$ python

Python 2.2 (#1, Nov  5 2002, 15:43:24)
[GCC 2.96 2731 (Mandrake Linux 8.2 2.96-0.76mdk)] on linux-i386
Type "help", "copyright", "credits" or "license" for more information.
>>> import time
>>> time.strptime


'Use Ctrl-D (i.e. EOF) to exit.'
>>>
===

On Fri, 2003-02-07 at 10:26, Peter Bengtson wrote:
> Messages do not get archived properly. Mac OS 10.1.x, Mailman 2.1. The 
> logs reveal the following:
> 
> > Feb 07 12:51:16 2003 (389) SHUNTING: 
>1044618675.177514+be324eff2aafe6a8b13f0aa43b6580cf9d345fc4
> > Feb 07 13:27:59 2003 (389) Uncaught runner exception: 'module' object has no 
>attribute 'strptime'
> > Feb 07 13:27:59 2003 (389) Traceback (most recent call last):
> >   File "/Users/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop
> > self._onefile(msg, msgdata)
> >   File "/Users/mailman/Mailman/Queue/Runner.py", line 155, in _onefile
> > keepqueued = self._dispose(mlist, msg, msgdata)
> >   File "/Users/mailman/Mailman/Queue/ArchRunner.py", line 73, in _dispose
> > mlist.ArchiveMail(msg)
> >   File "/Users/mailman/Mailman/Archiver/Archiver.py", line 207, in ArchiveMail
> > h.close()
> >   File "/Users/mailman/Mailman/Archiver/pipermail.py", line 304, in close
> > self.update_dirty_archives()
> >   File "/Users/mailman/Mailman/Archiver/pipermail.py", line 518, in 
>update_dirty_archives
> > self.update_archive(i)
> >   File "/Users/mailman/Mailman/Archiver/HyperArch.py", line 1032, in update_archive
> > self.__super_update_archive(archive)
> >   File "/Users/mailman/Mailman/Archiver/pipermail.py", line 424, in update_archive
> > self._update_simple_index(hdr, archive, arcdir)
> >   File "/Users/mailman/Mailman/Archiver/pipermail.py", line 434, in 
>_update_simple_index
> > self.write_index_header()
> >   File "/Users/mailman/Mailman/Archiver/HyperArch.py", line 949, in 
>write_index_header
> > print self.html_head()
> >   File "/Users/mailman/Mailman/Archiver/HyperArch.py", line 637, in html_head
> > d = {"listname": html_quote(mlist.real_name, self.lang),
> >   File "/Users/mailman/Mailman/Archiver/HyperArch.py", line 635, in quotetime
> > return html_quote(i18n.ctime(s), self.lang)
> >   File "/Users/mailman/Mailman/i18n.py", line 98, in ctime
> > year, mon, day, hh, mm, ss, wday, ydat, dst = time.strptime(date)
> > AttributeError: 'module' object has no attribute 'strptime'
> 
> Any ideas?
> 
> Also, using national characters such as åäöüéèô and so forth in a 
> user-supplied personal password causes Mailman to crash miserably:
> 
> > Bug in Mailman version 2.1
> > We're sorry, we hit a bug!
> > If you would like to help us identify the problem, please email a copy of this 
>page to the webmaster for this site with a description of what happened. Thanks! 
>Traceback:
> > Traceback (most recent call last):
> >   File "/Users/mailman/scripts/driver", line 87, in run_main
> > main()
> >   File "/Users/mailman/Mailman/Cgi/subscribe.py", line 94, in main
> > process_form(mlist, doc, cgidata, language)
> >   File "/Users/mailman/Mailman/Cgi/subscribe.py", line 176, in process_form
> > mlist.AddMember(userdesc, remote)
> >   File "/Users/mailman/Mailman/MailList.py", line 795, in AddMember
> > cookie = Pending.new(Pending.SUBSCRIPTION, userdesc)
> >   File "/Users/mailman/Mailman/Pending.py", line 69, in new
> > hashfood = str(now) + str(n) + str(content)
> >   File "/Users/mailman/Mailman/UserDesc.py", line 56, in __repr__
> > return '' % (
> > UnicodeError: ASCII decoding error: ordinal not in range(128)
> 
> 
> 
>   / Peter Bengtson
> 
> 
> --
> Mailman-Users mailing list
> [EMAIL PROTECTED]
> http://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> 
> This message was sent to: [EMAIL PROTECTED]
> Unsubscribe or change your options at
> http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

RE: [Mailman-Users] Archiving stops

[Jon Carnes]

I've had this happen under version 2.0.8 before.  Once because the
existing archive had gotten hosed.  I simply deleted the html files and
regenerated the archives using arch.  That worked fine.

Another time, I did the same thing and arch continuously stopped at one
point.  I went into the Mbox file and looked at the next message and
sure enough it was malformed - not enough to kill delivery, but enough
to hose the Pipermail archiver.  Once I deleted the malformed email,
arch ran fine and everything worked again.

I suggest you look at your current Archives then go to your Mbox file
for that list and look at the next message.

The html archive files for lists are stored in:
  ~mailman/archives/private//..
The mbox file for the archives are stored in:
  ~mailman/archives/private//

Good Luck - Jon Carnes

On Fri, 2003-01-24 at 15:53, Tom Maddox wrote:
> > Anyway, my latest issue is that Mailman stopped archiving messages last
> > night around 9:30 p.m., for no apparent reason.  There's nothing
> > in the logs
> > to indicate why archiving stopped.  Has anyone ever seen this before?
> 
> I've since restarted Mailman, and archiving is still hosed.  If anyone could
> suggest a possible cause or solution, I'd be very grateful.
> 
> 
> 
> --
> Mailman-Users mailing list
> [EMAIL PROTECTED]
> http://mail.python.org/mailman/listinfo/mailman-users
> Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
> 
> This message was sent to: [EMAIL PROTECTED]
> Unsubscribe or change your options at
> http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

RE: [Mailman-Users] Archiving stops

[Tom Maddox]

> Anyway, my latest issue is that Mailman stopped archiving messages last
> night around 9:30 p.m., for no apparent reason.  There's nothing
> in the logs
> to indicate why archiving stopped.  Has anyone ever seen this before?

I've since restarted Mailman, and archiving is still hosed.  If anyone could
suggest a possible cause or solution, I'd be very grateful.



--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Archiving: email address are not hidden dispitesetting

[Barry A. Warsaw]

> "MC" == Marc Christensen <[EMAIL PROTECTED]> writes:

MC> Is there a way to fix the problem without an upgrade?

Not easily, unfortunately.
-Barry

--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Archiving: email address are not hidden dispitesetting

[Marc Christensen]

On Thursday 23 January 2003 16:18, Barry A. Warsaw wrote:
> > "MC" == Marc Christensen <[EMAIL PROTECTED]> writes:
>
> MC> Dispite this, the archives still show the full addresses.
>
> MC> Has anyone seen this or know how to fix this?
>
> This is fixed in Mailman 2.1.
> -Barry

Is there a way to fix the problem without an upgrade?  I don't think there are 
deb packages for 2.1 yet.

Unless someone knows that there are deb packages, I'd realy like to fix the 
problem.

Thanks.

-- 
Marc C.
http://www.mecworks.com
http://www.mecworks.com/~marc/resume

--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Archiving: email address are not hidden dispitesetting

[Barry A. Warsaw]

> "MC" == Marc Christensen <[EMAIL PROTECTED]> writes:

MC> Dispite this, the archives still show the full addresses.

MC> Has anyone seen this or know how to fix this?

This is fixed in Mailman 2.1.
-Barry

--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

This message was sent to: archive@jab.org
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

RE: [Mailman-Users] Archiving?

[John Handelaar]

% -Original Message-
% From: [EMAIL PROTECTED]
% [mailto:[EMAIL PROTECTED]]On Behalf Of David Mir
% Sent: 26 August 2002 15:39
% To: [EMAIL PROTECTED]
% Subject: [Mailman-Users] Archiving?
% 
% I'm using Mailman on RH7.3 Everything seems to work great , 
% except archiving.  
% No matter what the settings (i.e. daily, weekly, monthly) it 
% never seems to 
% archive just gives the "raw" output!  Am I missing something?  

Possibly, possibly not.

% Could some one 
% tell me where to look for errors if there are any(pipermail 
% errors somewhere 
% else?)  

The error log is in $prefix/logs - if you're fortunate, something
might turn up there.

If you're using SpamAssasin, apparently it does something to
the mail headers - search for it in the archives for more info.

Try su'ing to the mailman user and execute $prefix/bin/arch listname;
perhaps running it from the command line will return an error
which isn't showing up in the logs.

And obviously check your permissions.

After all of that, it might not work.  I'm one of about 30 people
on this list who have tried to get to the bottom of the fact that
sometimes, and without generating any errors at all, for some
people it just doesn't bloody work.  And no bugger has any idea
why not.

Although the failure to log an error when pipermail fails is
surely quite an ugly little bug.

--
John Handelaar

T +44 20 8933 1494   M +44 7930 681789
F +44 870 169 7657   E [EMAIL PROTECTED]
-- 

--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

Re: [Mailman-Users] archiving

[J C Lawrence]

On Wed, 21 Aug 2002 11:23:35 -0400 (EDT) 
Greg Westin <[EMAIL PROTECTED]> wrote:

> With all this discussion of archiving, I have to ask: What does it say
> about the developers' confidence in Mailman that this list isn't
> archived by Mailman, but by an external service?  

The Mailman lists are archived at python.org using Pipermail, Mailman's
internal archiver.  They are also archived at various other external
sites which use various other tools.  Don't confuse the two.

> This is like when I was having trouble setting up Mailman on Mac OS X,
> and then discovered that Apple doesn't use Macs for its mail servers,
> it uses Sun computers.

As does Microsoft FWIW -- they just hide it better.

Also note that in Apple's case the Sun box in question is bigger than
any of the boxes that Apple currently makes and sells.  

> It seems to me that if this list is archived externally, maybe I, too,
> should look into that as an option. 

The internal archiver in mailman 2.1 is considerably more capable than
the archiver in Mailman 2.0.  It does not and likely never will match
the capability of external tools like MHonArc.  

If there's something you want from your archiver that Pipermail can't
offer, then investigate using an external archiver.  Otherwise look at
the archiver in v2.1.

I use an external archiver for my lists (see the FAQ for details) as I
want a variety of extra feature supports that Pipermail cannot offer (eg
replies from the web).  Other's find Pipermail's feature set quite
acceptable, especially in v2.1.

-- 
J C Lawrence
-(*)Satan, oscillate my metallic sonatas. 
[EMAIL PROTECTED]   He lived as a devil, eh?  
http://www.kanga.nu/~claw/  Evil is a name of a foeman, as I live.


--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/

Re: [Mailman-Users] Archiving problem

[Greg Ward]

On 25 October 2001, leanne lai said:
> Seems like the Mailman archiving function does not work properly with
> mailx.  When I use netscape mail or pipe or elm to reply to a mail
> list, the archiving function seems to work fine ie it is indented. But
> when I try to use mailx to reply, Mailman archival function seems to
> treat it as a new thread (no indentation) instead of a reply to an
> existing thread.

Perhaps mailx doesn't set the In-reply-to header.  Take a look in the
archive mbox file to see for sure.

> Does anyone else have this problem or know ways to get around this?

Umm, don't use mailx?

Greg
-- 
Greg Ward - software developer[EMAIL PROTECTED]
MEMS Exchangehttp://www.mems-exchange.org

--
Mailman-Users maillist  -  [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users