[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. Grüße is 'converted' to Gre. Did I miss an encoding option somewhere? Thanks in advance to anyone who can help! -- Jean Bausch -- 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] 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: PRIVATE_ARCHIVE_URL = '/mailman/private' PUBLIC_ARCHIVE_URL = '/pipermail' There were some changes in the URL handling between MM 2.0.x and 2.1.x It looks as though you are using the old style which may be causing you problems. In MM 2.1.2 PUBLIC_ARCHIVE_URL is a full URL pattern. Installing from source Defaults.py has the following definitions: PUBLIC_ARCHIVE_URL = 'http://%(hostname)s/pipermail/%(listname)s' MM 2.1.2's Defaults.py no longer defines PRIVATE_ARCHIVE_URL but is does say the following: quote DEFAULT_EMAIL_HOST = 'mailman.ftel.co.uk' DEFAULT_URL_HOST = 'mailman.ftel.co.uk' DEFAULT_URL_PATTERN = 'http://%s/mailman/' # DEFAULT_HOST_NAME has been replaced with DEFAULT_EMAIL_HOST, however some # sites may have the former in their mm_cfg.py files. If so, we'll believe # that, otherwise we'll believe DEFAULT_EMAIL_HOST. Same for DEFAULT_URL. DEFAULT_HOST_NAME = None DEFAULT_URL = None /quote Probably worth taking a closer look at Defaults.py and then updating your mm_cfg.py to take account of changes between MM 2.0.x and MM 2.1.x Then repost if you still have a problem. My relevant section in http.conf reads: Alias /pipermail/ /var/lib/mailman/archives/public/ Directory /var/lib/mailman/archives/public Options FollowSymLinks Order allow,deny Allow from all /Directory The directories in /var/lib/mailman/archives/public/ are default symlinks to /var/lib/mailman/archives/private/ The permissions on the archive-directories in the latter are: drwxrwsr-x5 www-data list On the index.html file: -rw-rw-rw-1 www-data list I hope anybody can help. Thanks, Ronald -- 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/r.barrett%40openinfo.co.uk -- Richard Barrett http://www.openinfo.co.uk -- 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] 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 not save any mail archives or useful material accumulated in the Mailman installation so on your head be it. -Cody Harris ++ | This Signature is best in plain text! | ++-+ | Linux Rox My Sox! | | Check out HCHS!| | http://vectec.net | ++--+ | Proud to use Mandrake Linux 8.1 as a server. | | Not proud to use Windows as a primary server. | ++--+ | Registered Linux user #315598 | | Registered Linux Computer #200951 | | Wrote on a Windoze Computer :( | ++ -- Richard Barrett http://www.openinfo.co.uk -- 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
[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-users for mailinglist [EMAIL PROTECTED] how can i add this archiver? how can i run it parallel to pipermail and how without pipermail? second, would it be possible to change $(listname) before archiver uses it? i wrote a little script that fixes the listname (it's not always the part in front of the @, but a algorithm that creates aconyms for listnames longer than 16 chars. so, in shell what i want would be: listname_new = `/usr/local/bin/fixlist.sh $listname` /usr/bin/lurker-index -l $(listname_new) -m email/message/post thanks for your help bye mejo -- Efficiency and progess is ours one more Now that we have the Neutron bomb It's nice and quick and clean and gets things done Kill kill kill kill kill the poor tonight pgp0.pgp Description: PGP signature -- 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] 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 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: PRIVATE_ARCHIVE_URL = '/mailman/private' PUBLIC_ARCHIVE_URL = '/pipermail' There were some changes in the URL handling between MM 2.0.x and 2.1.x It looks as though you are using the old style which may be causing you problems. In MM 2.1.2 PUBLIC_ARCHIVE_URL is a full URL pattern. Installing from source Defaults.py has the following definitions: PUBLIC_ARCHIVE_URL = 'http://%(hostname)s/pipermail/%(listname)s' I replaced my orginal PUBLIC_ARCHIVE_URL with the one above in mm_cfg.py MM 2.1.2's Defaults.py no longer defines PRIVATE_ARCHIVE_URL but is does say the following: quote DEFAULT_EMAIL_HOST = 'mailman.ftel.co.uk' DEFAULT_URL_HOST = 'mailman.ftel.co.uk' DEFAULT_URL_PATTERN = 'http://%s/mailman/' # DEFAULT_HOST_NAME has been replaced with DEFAULT_EMAIL_HOST, however some # sites may have the former in their mm_cfg.py files. If so, we'll believe # that, otherwise we'll believe DEFAULT_EMAIL_HOST. Same for DEFAULT_URL. DEFAULT_HOST_NAME = None DEFAULT_URL = None /quote I replaced my orginal lines with the ones above (commenting out DEFAULT_URL) and filling my sites parameters. Probably worth taking a closer look at Defaults.py and then updating your mm_cfg.py to take account of changes between MM 2.0.x and MM 2.1.x Then repost if you still have a problem. After making the changes above and restarting the apache and mailman daemons, I still have the same problem. My relevant section in http.conf reads: Alias /pipermail/ /var/lib/mailman/archives/public/ Directory /var/lib/mailman/archives/public Options FollowSymLinks Order allow,deny Allow from all /Directory The directories in /var/lib/mailman/archives/public/ are default symlinks to /var/lib/mailman/archives/private/ The permissions on the archive-directories in the latter are: drwxrwsr-x5 www-data list On the index.html file: -rw-rw-rw-1 www-data list I hope anybody can help. Thanks, Ronald -- 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/r.barrett%40openinfo.co.uk -- Richard Barrett http://www.openinfo.co.uk -- 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
[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 Bausch -- 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
[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/ In both cases the EDITHTML page shows the same encoding: MM-ArchiveMM-List-Name Archives/MM-Archive -- Jean Bausch -- 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] 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 script fix_url.py to update the web_page_url attribute of existing lists. That said, I do not think that is the cause of this problem. Have you checked your web server access and error logs to see if they give any clues? Richard 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 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: PRIVATE_ARCHIVE_URL = '/mailman/private' PUBLIC_ARCHIVE_URL = '/pipermail' There were some changes in the URL handling between MM 2.0.x and 2.1.x It looks as though you are using the old style which may be causing you problems. In MM 2.1.2 PUBLIC_ARCHIVE_URL is a full URL pattern. Installing from source Defaults.py has the following definitions: PUBLIC_ARCHIVE_URL = 'http://%(hostname)s/pipermail/%(listname)s' I replaced my orginal PUBLIC_ARCHIVE_URL with the one above in mm_cfg.py MM 2.1.2's Defaults.py no longer defines PRIVATE_ARCHIVE_URL but is does say the following: quote DEFAULT_EMAIL_HOST = 'mailman.xxx.co.uk' DEFAULT_URL_HOST = 'mailman.xxx.co.uk' DEFAULT_URL_PATTERN = 'http://%s/mailman/' # DEFAULT_HOST_NAME has been replaced with DEFAULT_EMAIL_HOST, however some # sites may have the former in their mm_cfg.py files. If so, we'll believe # that, otherwise we'll believe DEFAULT_EMAIL_HOST. Same for DEFAULT_URL. DEFAULT_HOST_NAME = None DEFAULT_URL = None /quote I replaced my orginal lines with the ones above (commenting out DEFAULT_URL) and filling my sites parameters. Probably worth taking a closer look at Defaults.py and then updating your mm_cfg.py to take account of changes between MM 2.0.x and MM 2.1.x Then repost if you still have a problem. After making the changes above and restarting the apache and mailman daemons, I still have the same problem. My relevant section in http.conf reads: Alias /pipermail/ /var/lib/mailman/archives/public/ Directory /var/lib/mailman/archives/public Options FollowSymLinks Order allow,deny Allow from all /Directory The directories in /var/lib/mailman/archives/public/ are default symlinks to /var/lib/mailman/archives/private/ The permissions on the archive-directories in the latter are: drwxrwsr-x5 www-data list On the index.html file: -rw-rw-rw-1 www-data list I hope anybody can help. Thanks, Ronald -- 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/r.barrett%40openin fo.co.uk -- Richard Barrett http://www.openinfo.co.uk -- Richard Barrett http://www.openinfo.co.uk -- 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
[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. 2) the Overview of all shu.ac.uk mailing lists link URL- my webserver is listening on port 8080 as implied above but the mailman ignored this port number for the overview URL http://mailman.shu.ac.uk/mailman/listinfo instead of http://mailman.shu.ac.uk:8080/mailman/listinfo again I can add this in by hand but... Can someone point me at info as to how I can resolve these problems, please? (they were working correctly in 2.0.11) Thanks, _ Ray Gardener CIS Sheffield Hallam University Howard Street Sheffield UK S1 1WB (44) 0114 225 4926 -- 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
[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 hosting a subdomain). 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 migrated to it yet. Can anyone recommend a commercial provider offering Mailman 2.1? (Dreamhost, feel free to step in and be my knight in shining e-mail...) -- Karen G. Schneider [EMAIL PROTECTED] http://lii.org Director,Librarians' Index to the Internet lii.org New This Week: http://lii.org/ntw lii.org: Information You Can Trust! -- -- 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
[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 migrated to it yet. Can anyone recommend a commercial provider offering Mailman 2.1? (Dreamhost, feel free to step in and be my knight in shining e-mail...) We are definitely planning on upgrading, and it should be in the near future. We were hoping to improve the virtual hosting aspect, but 2.1 wasn't as useful for this as we had hoped. There are still changes we need to make to our backend, however, and we need to figure out the most painless way to handle migration over to the new machine / version. I can say that this is currently being worked on, and while I can't give you a specific ETA on when 2.1 will be fully working, it should be fairly soon. You can email support@ if you're interested in being a candidate for early migration to 2.1 once it's setup. Will (DreamHost) -- Since when is skepticism un-American? Dissent's not treason but they talk like it's the same... (Sleater-Kinney - Combat Rock) -- 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
[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 hosting package, and I've gotten the impression thus far that my host is far from expert concerning Mailman. All of my interaction w/ Mailman has been through the Web administrative interface, and I'm not at all sure that I have access rights to do anything from the console, although I apparently have read access to at least some of the list files. Some time ago, when attempting to deal with a pending admin request, I received an error (in true luser style, I neglected to record it, but IIRC it was a write error or access error of some sort) in the Mailman web admin interface, but the interface thereafter showed no pending requests. However, ever since then, I've been getting a daily reminder saying that there's a pending post from [EMAIL PROTECTED], awaiting my approval. When I follow the link to the admin interface and log in, I get the AdminRequests page, but with the message that There are no pending requests. Is there any way I can reset the relevant file from the web interface, or some information that I can give the person hosting my site to clean this up? The daily notification email is becoming rather annoying. One voodoo solution I've tried unsuccessfully is running another admin request through; in that case, IIRC, the reminder email changed to say that there was one pending request, the genuine one. However, on handling that request, the old problem reappeared. Any help on this would be greatly appreciated. Many thanks in advance! -Joel I -- 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
[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 return to the page as though nothing had been submitted. In particular, nobody can subscribe, which is a real problem. I thought that perhaps the cgi scripts were expecting to be run by Apache under a different group membership, however I verified that our Apache is running as www and that Mailman was expecting www group membership -- seemingly no problem there. We're running Mailman 2.1.2 and Apache on FreeBSD and have reinstalled Mailman already. Running bin/check_perms -f seems not to help. I would appreciate any pointers or suggestions. Thanks, --Emil Emil Volcheck [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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
