[Mailman-Users] cgi scripts fail silently

Hello, Mailman users, A little while ago I wrote to report a problem that my admindb was not being updated when I tried to manage it through the web page interface. It turns out my problem was more general: all web page cgi scripts simply do nothing (fail silently). When you press submit, you ret

[Mailman-Users] Bogus "admin request(s) waiting" message

Greetings from a total newbie to *nix! I'm hoping someone can help resolve a question regarding a bogus "admin request(s) waiting" daily message. I've searched the archives and FAQ, but haven't found relevant information there. My situation: I'm using Mailman installed as part of the CPanel hos

[Mailman-Users] Re: Commercial provider for Mailman 2.1?

On Thu, Jun 12, 2003 at 01:41:57PM -0700, Karen G. Schneider wrote: > However, at present Dreamhost is using Mailman 2.0.13, and there > are several must-have features I need for two large lists I manage > (5,000 and 16,000 subscribers). The last time I checked, they were > testing 2.1 but hadn't

[Mailman-Users] Commercial provider for Mailman 2.1?

Searched the archive and couldn't find an answer... I currently maintain a few small Mailman lists on Dreamhost. It's very reasonably priced and the service has been stable for the six months I've been using it, with only a few tiny gremlins I can ignore (not related to Mailman--more to do with h

Re: [Mailman-Users] 2 problems after upgrading from 2.0.11 to 2.1

There are changes in the way MM 2.1.x handles URLs by comparison with 2.1.x Take a look at the comments in $prefix/Mailman/Defaults.py before and after the definition of DEFAULT_URL_HOST and related config variables. The resulting changes you then make in mm_cfg.py may solve some of the problem

Re: [Mailman-Users] alternative archiver

At 10:54 12/06/2003, Jonas Meurer wrote: *** PGP Signature Status: unknown *** Signer: Unknown, Key ID xE25F2102 *** Signed: 12/06/2003 10:54:00 *** Verified: 12/06/2003 16:16:14 *** BEGIN PGP VERIFIED MESSAGE *** hello, i'm trying to get mailman 2.1.2 running with an alternative archiver. the arch

[Mailman-Users] 2 problems after upgrading from 2.0.11 to 2.1

Hi, after today's upgrade 1) The list archives URLs seem to be broken; clicking on Go to list archives accesses the URL http://mailman.shu.ac.uk:8080/pipermail/ instead of http://mailman.shu.ac.uk:8080/pipermail/listname I can add the listname in. but clearly this in not what I would like.

Re: [Mailman-Users] 403 Forbidden error accessing public archives

At 11:09 12/06/2003, Ronald van Engelen wrote: Thanks Richard for your useful info. I still however have the same problem. See details below for the modifications I've tried. Ronald One thing I should have said is that after changing hosts and such you may want to run the $prefix/bin/withlist scr

[Mailman-Users] missing listname in public archive's URL

(mailman 2.1.2 on Solaris/Intel) On the listinfo page the URL of a public archive is generated as http://myserver.mydomain/pipermail/ instead of http://myserver.mydomain/pipermail/listname/ The URL of a private archive is OK. It is generated as http://myserver.mydomain/mailman/private/listname

[Mailman-Users] Umlaut in message bodies are omitted

I have now found who swallows the Umlauts in message bodies: I had inserted a 'fmt -s -w 80' in the mail aliases. Unfortunately on Solaris 7 this command erases the Umlauts. Hence my next question: Is there an option in mailman 2.1.2 to autowrap the messages after 80 characters or so? -- Jean B

Re: [Mailman-Users] 403 Forbidden error accessing public archives

Thanks Richard for your useful info. I still however have the same problem. See details below for the modifications I've tried. Regards, Ronald Op do 12-06-2003, om 11:43 schreef Richard Barrett: > At 01:19 12/06/2003, Ronald van Engelen wrote: > >Hi, > > > >I'm getting the infamous 403 Access Fo

[Mailman-Users] alternative archiver

hello, i'm trying to get mailman 2.1.2 running with an alternative archiver. the archiver gets the mail through a program called 'lurker-index'. commandline usage would be: /usr/bin/lurker-index -l $(listname) -m < /path/to/message so, $listname has to be the stuff in front of the @, like mailman-u

Re: [Mailman-Users] Removing

At 01:12 12/06/2003, Cody Harris wrote: How do i remove mailman? If you installed from RPMs then use the rpm command to delete the Mailman package. If you installed from source then 'rm -rf $prefix' where $prefix is the MM install directory will comprehensively delete MM stuff. The above will n

Re: [Mailman-Users] 403 Forbidden error accessing public archives

At 01:19 12/06/2003, Ronald van Engelen wrote: Hi, I'm getting the infamous 403 Access Forbidden error trying to access my public archives. I've read the faq and the README files but can't find my error. I'm using mailman 2.1.2-1 from Debian unstable with apache 1.3.27.0-1. In mm_cfg.py I have:

[Mailman-Users] Umlaut in message bodies are omitted

I have updated from Mailman 2.0.10 to 2.1.2 because of the international language support (on Solaris and Intel). German Umlauts (äöüß...) are now displayed correctly in the subject line, BUT ... they are simply omitted in the message body - in the received mails as well as in the archive. e.g.