Bugs item #640664, was opened at 2002-11-19 12:49
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640664&group_id=103
Category: nntp/news
Group: 2.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Chris Dudley (dudleyc)
Assigned to: Nobody/Anony
I just cvsupped because I discovered that my current installation (about a
week old) was initializing some fields in the web forms with the word
"archive".
I've seen this as the initial name of a list when creating one, and as the
password when clicking on a subscriber's email address in Membershi
> "SB" == Stonewall Ballard <[EMAIL PROTECTED]> writes:
SB> I just cvsupped because I discovered that my current
SB> installation (about a week old) was initializing some fields
SB> in the web forms with the word "archive".
SB> I've seen this as the initial name of a list whe
This turned out to be a very confused password-auto-enter function on
Chimera (the OS X browser).
I've got Apache protecting my archives with a basic auth, and somehow,
Chimera thinks that belongs in the first field on any page in that path.
Sorry for the bother.
- Stoney
On 11/19/02 9:28 AM,
Bugs item #640775, was opened at 2002-11-19 16:28
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640775&group_id=103
Category: command line scripts
Group: 2.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: David Weisgerber (davidweisgerber)
As
Well, if the SF project pages come up before midnight EST. :/
-Barry
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
> "BAW" == Barry A Warsaw <[EMAIL PROTECTED]> writes:
BAW> Well, if the SF project pages come up before midnight EST. :/
Looks like it was just a bogus cache entry. SF is fine.
-Barry
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
htt
On Tue, Nov 19, 2002 at 11:49:34AM -0500, Barry A. Warsaw wrote:
> Well, if the SF project pages come up before midnight EST. :/
Small note. You said that all files for 2.1 should have revision 2.x,
there are some files (in templates/en) that are not. :)
--
Misha
msg05047/pgp0.pgp
Descript
> "MS" == Mikhail Sobolev <[EMAIL PROTECTED]> writes:
MS> Small note. You said that all files for 2.1 should have
MS> revision 2.x, there are some files (in templates/en) that are
MS> not. :)
True, but the templates don't bother me as much, mostly because others
have checkin pri
Bugs item #640374, was opened at 2002-11-18 16:57
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=640374&group_id=103
Category: Web/CGI
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Paul Marshall (paulmarshll)
Assigned to: Nobody
I've had bin/arch croak on a few different list archives (though for one of
the lists, it worked the 2nd time I ran it, so that's good!) with the
following error:
Updating HTML for article 2
Traceback (most recent call last):
File "./arch", line 173, in ?
main()
File "./arch", line 163, in
A few more lists, a few different errors:
Traceback (most recent call last):
File "./arch", line 173, in ?
main()
File "./arch", line 163, in main
archiver.close()
File "/home/services/mailman/Mailman/Archiver/pipermail.py", line 303, in
close
self.update_dirty_archives()
File "/home/
I love answering my own questions. Either that, or I'm far too hasty
posting problems to the list before I try to fix them. In anycase,
hopefully this will help anyone else who is having problems regenerating
their archives.
Try renaming the html archive directory for a given list to listname.
On 19 November 2002, Andrew D. Clark said:
> Try renaming the html archive directory for a given list to listname.backup.
> Then run arch again and let it recreate the whole html archive from
> scratch. Worked for me on a few archives that arch was barfing on.
Did you remember to run bin/b4b5-ar
Mailman Developers,
If a non-member of a list sends a mail message to the request address
to "set nomail on passwd", the non-member gets a traceback and the
admin gets an "unexpected mailman error" message.
Instead, the MailCommandHandler probably wants to catch the exception
and suggest to the n
Hey, I just had an idea for a Mailman (not necessarily 2.1) feature
enhancement. Smack me if this isn't reasonable.
See, I just had to get myself off an opt-out spam list that Walgreens
put me on, which process involved their system mailing me a randomly
computer-generated username and password i
From: "Phil Stracchino" <[EMAIL PROTECTED]>
> So, my idea: GPG support for mailman, which the server operator has a
> configuration option to disable, and allow registered listmembers to
> upload a GPG public key. This key could be used in either or both of
> two ways:
I have only windows users
On Wed, Nov 20, 2002 at 01:45:42AM +0100, Danny Terweij wrote:
> From: "Phil Stracchino" <[EMAIL PROTECTED]>
>
> > So, my idea: GPG support for mailman, which the server operator has a
> > configuration option to disable, and allow registered listmembers to
> > upload a GPG public key. This key c
I've released Mailman 2.1 beta 5, and upgraded the python.org server
to run this version, so with this announcement you are seeing its
effects. :) Everything seems to be cruising along smoothly, so
hopefully we'll have better luck with this version than with 2.1b4.
See below for a list of changes
On Tuesday 19 November 2002 07:45 pm, Danny Terweij wrote:
> > So, my idea: GPG support for mailman, which the server operator has a
> > configuration option to disable, and allow registered listmembers to
> > upload a GPG public key. This key could be used in either or both of
> > two ways:
> I
On Tuesday, November 19, 2002, at 08:44 PM, Phil Barnett wrote:
...and so we should dumb down all their software so it doesn't offend
them...
No, the proper question is whether it's appropriate for the list server
software to take the lead in pushing this technology out to the users.
In the
On Tuesday 19 November 2002 11:51 pm, Chuq Von Rospach wrote:
> On Tuesday, November 19, 2002, at 08:44 PM, Phil Barnett wrote:
> > ...and so we should dumb down all their software so it doesn't offend
> > them...
> No, the proper question is whether it's appropriate for the list server
> softwa
On Tuesday, November 19, 2002, at 10:02 PM, Phil Barnett wrote:
As far as I can see, there's only one reason. The server is locking
the client
into passing plaintext passwords around the planet without an
alternative.
give me a nice, usable encryption system that doesn't require a masters
d
23 matches
Mail list logo
