[Mailman-Users] re subscribers not getting welcome email

2003-01-19 Thread Mark C
Hi, I have managed to so far sucessfully setup mailman on a private test network. I subscribed a few test users and, that worked no problem, each got a request email and a confirmation email. I then went to the web interface and unsubscribed them, and again I got a goodbye email. I then tested

[Mailman-Users] 2.1b4 -> 2.1 breaks archive message url's

2003-01-19 Thread Jasper Wallace
Hi, I just upgraded to 2.1 from 2.1b4 and rebuilt the archives (with --wipe) as part of the upgrade. Unfortunatly this changed all the urls for individual messages, and so links to messages have now broken, and so has googles site:foo search stuff. This is not good. Thinking about it there is

Re: [Mailman-Users] Passwords of members UPDATE

2003-01-19 Thread Barry A. Warsaw
Steve, You're first problem looks like a classic "permission denied" problem. I'd suggest running bin/check_perms to see if that clears up your problems. The second issue you had (no module name "time") looks like your Python installation is broken. You should be able to do something like the

Re: [Mailman-Users] qrunner troubles after install: "Uncaught runner exception"

2003-01-19 Thread Barry A. Warsaw
> "ANV" == A N Varady <[EMAIL PROTECTED]> writes: ANV> ./configure --with-cgi-gid=99 --with-mail-gid=mailman ANV> --prefix=/home/mailman --with-python=/usr/local/bin/python2.2 ANV> TypeError: isinstance() arg 2 must be a class or type Be sure that the python2.2 above points to P

Re: [Mailman-Users] Upgrade problems (2.0.13 -> 2.1);Incoming qrunner dies

2003-01-19 Thread Barry A. Warsaw
> "EO" == Ed Osinski <[EMAIL PROTECTED]> writes: EO> I've upgraded from 2.0.13 to 2.1, and am having problems: EO> When running "bin/mailmanctl start", I get a series of errors: EO> EOFError : EOF read where object expected EO> This is repeated 11 times. When I run ps to l

[Mailman-Users] Hiding email addresses in archives

2003-01-19 Thread tspeight
Moz, I remember a domain called listquest.com that archived messages from other lists that used a program that they said was in the public domain that converted all email addresses in each message to a gif, thereby rendering the email addresses useless when you tried to harvest the emails in th

[Mailman-Users] Hiding email addresses in archives

2003-01-19 Thread tspeight
Moz, I remember a domain called listquest.com that archived messages from other lists that used a program that they said was in the public domain that converted all email addresses in each message to a gif, thereby rendering the email addresses useless when you tried to harvest the emails in th

[Mailman-Users] Back tracking subscribers confirmations

2003-01-19 Thread Mark C
Hi, I'm about to install mailman for a friend of mine, basically he runs a motivation company (yes the one that employers send their staff onto to try to get them to enjoy and be motivated in their £4.50 an hour telesales job). Basically he wishes send mails out informing subscribers of new deal

[Mailman-Users] Re: Problems with content filtering

2003-01-19 Thread David Gibbs
"David Gibbs" <[EMAIL PROTECTED]> wrote in message b0d7d8$k5k$[EMAIL PROTECTED]">news:b0d7d8$k5k$[EMAIL PROTECTED]... > I solved the problem by changing the HTML to Plaintext command to links... Actually, I found a simpler solution that doesn't require installing any software. Turns out that Redh

[Mailman-Users] old request causes checkdbs failure in 2.1

2003-01-19 Thread Karl Berry
I updated my site (red hat linux 6.2, i686) to mailman 2.1 and python 2.2.2. Unfortunately, I managed to create a request to the new `mailman' list during the upgrade which ended up in the old format, and is causing cron/checkdbs to fail (see below). At least that's what I gather from the couple

[Mailman-Users] Hiding email addresses in archives

2003-01-19 Thread Moz
I'd like to hide or obfuscate email addresses in the list archives, but can't see an obvious way to do this. Right now we seem to be a target for address-harvesting, and it bothers our users. But we'd like to leave the archives public. Is there something I can do to mailman to get this behaviour?