Re: [Mailman-Users] attachments are not scrubbed
Hello,
messages sent to non-digest subscribers. If this was the case in your
2.1.4, you must have had a local patch to do it which was 'removed'
when you upgraded to 2.1.5.
Hm, I don't remember exactly the version of mailman but it really worked
'out of box'.
if not GLOBAL_PIPELINE.count('Scrubber'):
GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('MimeDel') + 1,
'Scrubber')
Thanks. I put it into mm_cfg.py and everything works agains: attachments
are scrubbed from non-digest mails.
Bye,
Saylius
--
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=showamp;file=faq01.027.htp
[Mailman-Users] general subscription and removal
Hi, I am administering around 50 mailing conferences under Mailman 2.1.5. How can I easily subscribe/remove a person to/ from other mailing lists for which he wants to be/is a member? So far I have done so manually - by a/ subscribing the person to each list separately b/ listing the person´s other subscriptions and unsubscribing him from the lists one by one - but this is very time-consuming. Thanks a lot, Klara -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] ISO-8859-1/Latin1 vs UTF-8
On Mon, 2005-10-24 at 12:52 +0200, Hannah Schroeter wrote: [...] On Sun, Oct 23, 2005 at 11:58:37PM +0200, Bernd Petrovitsch wrote: Apparently all of the German translation of Mailman is in ISO-8859-1 (or ISO-8859-15) - at least in the standard Debian mailman package. Is there a special reason for not moving to UTF-8 in general? I'd say: YAGNI (Ya ain't gonna need it). If the charset is declared If I don't need it, I do not care. correctly, it isn't worse for German text. And it has less overhead then. The problem is that I enter text in the web-interface on a default UTF-8 system and it is apparently stored as UTF-8. The pages are delivered as ISO-8859-1 according to the HTTP header and the header in the file. So the CGI scripts actually should convert correctly the ML-admins data from the given charset into ISO-8859-1 (which is not 100% possible but for German and in practice it will be good enough IMO). The other solution is to use ouml; and brothers and blame the ML admin if he doesn't do so (and put in somwhere into the docs or so). There is BTW a similar problem: If I enter (quotes) in the web interface, they are converted to quot; (probably by the browser - I didn't check) and then sent out in a plain/text email. So in both cases I actually want to know what the way to go is. Bernd -- Firmix Software GmbH http://www.firmix.at/ mobil: +43 664 4416156 fax: +43 1 7890849-55 Embedded Linux Development and Services -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] ISO-8859-1/Latin1 vs UTF-8
At 1:04 PM +0200 2005-10-24, Bernd Petrovitsch wrote: The other solution is to use ouml; and brothers and blame the ML admin if he doesn't do so (and put in somwhere into the docs or so). There is BTW a similar problem: If I enter (quotes) in the web interface, they are converted to quot; (probably by the browser - I didn't check) and then sent out in a plain/text email. These two are actually a result of the same thing -- the Mailman code scrubs input text from the web interface, to try to prevent cross-site scripting attacks. If you want this stuff to show up correctly, you will need to edit the template files directly as opposed to using the web interface. If you go back and use the web interface to edit that text again, it will get re-scrubbed, so once you go the template route, you need to stick with editing those files directly. -- 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 http://www.sage.org/ 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=showamp;file=faq01.027.htp
[Mailman-Users] Qmail trouble
I'm trying to get mailman running under FreeBSD 5.4. I'm using qmail as the MTA, and appears to be unable to make it actually deliver any mail. When a message is sent to the list I get the following in maillog: Oct 24 16:42:56 ia qmail: 1130164976.495580 new msg 262 Oct 24 16:42:56 ia qmail: 1130164976.496106 info msg 262: bytes 877 from [EMAIL PROTECTED] qp 49909 uid 82 Oct 24 16:42:56 ia qmail: 1130164976.498677 starting delivery 47: msg 262 to local [EMAIL PROTECTED] Oct 24 16:42:56 ia qmail: 1130164976.498866 status: local 1/10 remote 0/20 Oct 24 16:42:56 ia qmail: 1130164976.672177 delivery 47: success: did_0+0+1/ Oct 24 16:42:56 ia qmail: 1130164976.672779 status: local 0/10 remote 0/20 Oct 24 16:42:56 ia qmail: 1130164976.673287 end msg 262 No attempts to deliver mail to the list members, but the mails appear in the list archive. I *think* I've followed all instructions on http://www.gnu.org/software/mailman/mailman-install/qmail-issues.html, but must have missed something. /Par -- Par Leijonhufvud [EMAIL PROTECTED] This e-mail is confidential and solely for the use of the intended recipient. If you are not the intended recipient, you are obligated to kill yourself and others who might have seen it immediately. Thank you. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] ascii error
Doc Schneider wrote: Subject: [UHS] =?iso-8859-1?q?B=D6C=3A__knees_or_feet=3F?= This this would be the one? Probably not. That is a properly RFC 2047 encoded subject that says BÍC:__knees_or_feet? The literal subject itself does not contain any non-ascii data and the decoded subject does not contain á. If as I suspect, the listname.mbox is current, but the HTML archive ends on Oct 19, the offending message is either the last one in the HTML archive (i.e. archives/private/listname/2005-October/nn.html where nn is the highest number there) or the first one after that. However, it may be the case that they all have nn.html files in which case it may only be the subject, date and thread .html files that are truncated. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] ascii error
Hello! On Mon, Oct 24, 2005 at 07:55:45AM -0700, Mark Sapiro wrote: Doc Schneider wrote: Subject: [UHS] =?iso-8859-1?q?B=D6C=3A__knees_or_feet=3F?= This this would be the one? Probably not. That is a properly RFC 2047 encoded subject that says BÍC:__knees_or_feet? No, it says BÍC: knees or feet? _ is a substitute for space in q encoding. See section 4.2, no. (2), in RFC 2047. It's used, because spaces are frequent in encoded headers and unencoded spaces aren't allowed in an encoded-word. [...] Kind regards, Hannah. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Qmail trouble
Par Leijonhufvud said: I'm trying to get mailman running under FreeBSD 5.4. I'm using qmail as the MTA, and appears to be unable to make it actually deliver any mail. When a message is sent to the list I get the following in maillog: Oct 24 16:42:56 ia qmail: 1130164976.495580 new msg 262 Oct 24 16:42:56 ia qmail: 1130164976.496106 info msg 262: bytes 877 from [EMAIL PROTECTED] qp 49909 uid 82 Oct 24 16:42:56 ia qmail: 1130164976.498677 starting delivery 47: msg 262 to local [EMAIL PROTECTED] Oct 24 16:42:56 ia qmail: 1130164976.498866 status: local 1/10 remote 0/20 Oct 24 16:42:56 ia qmail: 1130164976.672177 delivery 47: success: did_0+0+1/ Oct 24 16:42:56 ia qmail: 1130164976.672779 status: local 0/10 remote 0/20 Oct 24 16:42:56 ia qmail: 1130164976.673287 end msg 262 No attempts to deliver mail to the list members, but the mails appear in the list archive. I *think* I've followed all instructions on http://www.gnu.org/software/mailman/mailman-install/qmail-issues.html, but must have missed something. Look in the Mailman error log: mailmaninstallpath/logs/error. I was seeing something like that when I had MM misconfigured. Qmail was delivering the message, but MM was choking. The MM error log showed me what was going on (once Mark Sapiro gave me some hints on how to read it). /dwight -- Dwight N. Tovey email: [EMAIL PROTECTED] web: http://www.dtovey.net/~dwight --- I don't get even, I get odder. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] ascii error
Hannah Schroeter wrote: No, it says B=CDC: knees or feet? _ is a substitute for space in q encoding. Of course you are correct. Thank you. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] get all lists' subscribe_policy
Xiaoyan Ma wrote:
I need a script that gets all lists' subscribe_policy/unsubscribe_policy and
outputs to a file.
Similar to lists_admins, but instead of getting administrator's email
address, it gets
subscribe_policy. I looked into MailList.py, config_list, list_lists and
withlist ... but have
not figured out how to do it. Can someone point me to the right direction?
Since you want something similar to list_admins, look at that. In
particular find
owners = COMMASPACE.join(mlist.owner)
print _('List: %(listname)s, \tOwners: %(owners)s')
You don't need COMMASPACE.join(mlist.owner) because subscribe policy is
a number, not a list of e-mail addresses, but if you are going to use
the i18n._ method you do have to assign mlist.subscribe_policy to a
variable or you can just
print 'List: %s, \tPolicy: %d' % (listname,
mlist.subscribe_policy)
--
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=showamp;file=faq01.027.htp
Re: [Mailman-Users] general subscription and removal
Klara Schirova wrote: I am administering around 50 mailing conferences under Mailman 2.1.5. How can I easily subscribe/remove a person to/ from other mailing lists for which he wants to be/is a member? So far I have done so manually - by a/ subscribing the person to each list separately b/ listing the person's other subscriptions and unsubscribing him from the lists one by one - but this is very time-consuming. Thanks a lot, Klara If you have command line access, you may be able to create a shell script using bin/add_members and bin/remove_members to help. Otherwise, there's not much you can do. It's really easier if the users are responsible for subscribing and unsubscribing themselves. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Bounce processing
kate griffiths wrote: Can anyone give me some advice about the bounce processing function of the mailman lists? Can I configure the list so that it does not automatically disable/unsubscribe people for excessive bounces? Should this be done by switching to 'no' in the section that asks 'Should mailman perform automatic bounce processing for the list'? Yes. You could also set bounce_info_stale_after to zero. This would have the advantage of continuing to log the bounces in Mailman's bounce log, while discarding yesterday's bounces so the threshold is never reached. If you can't view the log, this probably doesn't matter. Does this have any adverse effects other than not telling me when a message does not reach certain members of the list? Yes. If you continue to mail dead addresses, some ISPs will eventually start blocking all your mail. If you are having problems with people being disabled who shouldn't be, say because they tend to have full mailboxes for long periods, it is better to adjust the various bounce processing parameters for a satisfactory result by perhaps increasing the threshold and the number of warnings. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Restart Mailman and IP help
On Sat, 2005-10-22 at 20:47 +0800, ML wrote: Hi, I paid to have Mailman installed on my DirectAdmin CentOS server a few months ago, recently I had to change the server hostname and IP and Mailman no longer sends out emails! (the people that originally installed Mailman will fix the problem if I pay for a one hour support charge, but I believe it is just a matter of updating to the new IP or hostname) Also: 1) I can¹t find the mm_cfg.py file! Where should it be? 2) how exactly do I restart mailman, what directory must I be in? Does anyone know where on Mailman or server I need to enter/change the new IP or hostname? CentOS is a repackaging of Red Hat Enterprise Linux, assuming your consultant installed the Red Hat mailman rpm then the mailman source files are in /usr/lib/mailman/Mailman. mm_cfg.py is also sym linked from /etc/mailman/mm_cfg.py. You could also locate the files via rpm -ql mailman or by reading /usr/share/doc/mailman-*/INSTALL.REDHAT (unless CentOS changed the name, they are required to remove all branding). The mm_cfg we ship derives the host name from the socket networking code, you don't have to explicitly set it in mm_cfg. However, if you created a list and then changed the hostname you'll have to fix the lists you already created because that information is embedded in the list after creation. The mailman FAQ covers this topic in detail. -- John Dennis [EMAIL PROTECTED] -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] ISO-8859-1/Latin1 vs UTF-8
Bernd Petrovitsch wrote: The problem is that I enter text in the web-interface on a default UTF-8 system and it is apparently stored as UTF-8. The pages are delivered as ISO-8859-1 according to the HTTP header and the header in the file. So the CGI scripts actually should convert correctly the ML-admins data from the given charset into ISO-8859-1 (which is not 100% possible but for German and in practice it will be good enough IMO). The other solution is to use ouml; and brothers and blame the ML admin if he doesn't do so (and put in somwhere into the docs or so). There is BTW a similar problem: If I enter (quotes) in the web interface, they are converted to quot; (probably by the browser - I didn't check) and then sent out in a plain/text email. So in both cases I actually want to know what the way to go is. As Brad points out in another reply, some of this problem is because all text entered in the web interface (except for General Options-info which is a special case) is HTML escaped to prevent XSS attacks. Mailman arguably goes overboard on this, but the 4 characters '' '' '' and '' are changed respectively to amp;, lt;, gt; and quot; by Python's cgi.escape() method. Thus, you can't even enter ouml; and have it work in HTML or plain text. You can convert Mailman to use utf-8 for German language, but this will not solve the html escaping issue. If you are interested in converting to utf-8, there is relevant information in the archives of this list. See the thread beginning at http://mail.python.org/pipermail/mailman-users/2005-September/046467.html and continued at http://mail.python.org/pipermail/mailman-users/2005-September/046480.html and the thread beginning at http://mail.python.org/pipermail/mailman-users/2005-October/046850.html and continued at http://mail.python.org/pipermail/mailman-users/2005-October/046883.html and http://mail.python.org/pipermail/mailman-users/2005-October/046938.html -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Qmail trouble
Dwight Tovey wrote: Par Leijonhufvud said: I'm trying to get mailman running under FreeBSD 5.4. I'm using qmail as the MTA, and appears to be unable to make it actually deliver any mail. snip No attempts to deliver mail to the list members, but the mails appear in the list archive. I *think* I've followed all instructions on http://www.gnu.org/software/mailman/mailman-install/qmail-issues.html, but must have missed something. Look in the Mailman error log: mailmaninstallpath/logs/error. I was seeing something like that when I had MM misconfigured. Qmail was delivering the message, but MM was choking. The MM error log showed me what was going on (once Mark Sapiro gave me some hints on how to read it). (thanks) In this case, the mail gets to the archive so it has been delivered to Mailman and processing has gotten fairly far along, but the mail isn't going back out. Does any mail go out, e.g. subscription confirmations or other notices? If not, it is likely an outgoing mail problem. Look in Mailman's smtp and smtp-failure logs in addition to the error log. If some mail goes out, but not posts, maybe everyone is on digest and no digest has been sent yet. Also, go to the FAQ wizard Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py and search for 'troubleshooting' or 'no mail' (without quotes). -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] ISO-8859-1/Latin1 vs UTF-8
On Mon, 2005-10-24 at 09:52 -0700, Mark Sapiro wrote: [...] As Brad points out in another reply, some of this problem is because all text entered in the web interface (except for General Options-info which is a special case) is HTML escaped to prevent XSS attacks. Mailman arguably goes overboard on this, but the 4 characters Which is a good thing. '' '' '' and '' are changed respectively to amp;, lt;, gt; and quot; by Python's cgi.escape() method. Makes sense. Hmm, mailman could replace that four chars with the ASCII chars just for plain/text parts od sent out emails. That should not open any security hole and yield real plain/text. Thus, you can't even enter ouml; and have it work in HTML or plain text. Yes, of course, these are two distinct issues. Sorry for confusion. You can convert Mailman to use utf-8 for German language, but this will not solve the html escaping issue. If you are interested in converting to utf-8, there is relevant information in the archives of this list. I actually reported a bug (though it may not sound so): I enter (apparently) UTF-8 text (with Firefox it that is important) and it comes back disguised (and as part of) ISO-8859-1 text. The question is: Which part is doing something wrong and how to fix it? Bernd -- Firmix Software GmbH http://www.firmix.at/ mobil: +43 664 4416156 fax: +43 1 7890849-55 Embedded Linux Development and Services -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Qmail trouble
Mark Sapiro [EMAIL PROTECTED] [2005.10.24] wrote: Look in the Mailman error log: mailmaninstallpath/logs/error. Nothing (except when I made a spelling error on the listname). In this case, the mail gets to the archive so it has been delivered to Mailman and processing has gotten fairly far along, but the mail isn't going back out. Does any mail go out, e.g. subscription confirmations or other notices? If not, it is likely an outgoing mail problem. Look in Mailman's smtp and smtp-failure logs in addition to the error log. Nope, no mail goes out. In the smtp-error log I find Oct 24 15:52:24 2005 (46216) delivery to [EMAIL PROTECTED] failed with code 553: sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1) Ahh, a relaying problem. I'll mess with the MTA config some more. Thanks for the help! /Par -- Par Leijonhufvud [EMAIL PROTECTED] Sooner murder an infant in its cradle than nurse unacted desires -- William Blake -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] ascii error
Mark Sapiro wrote: Hannah Schroeter wrote: No, it says B=CDC: knees or feet? _ is a substitute for space in q encoding. Of course you are correct. Thank you. Just wanted you all to know I removed that message and now the list is archiving fine. I did as you suggested Mark and looked at where the archives stopped and also where the shunts/ started and for some reason it all pointed to that particular message. Removed it and rebuild the archives and tested the list and all is now well.. Thanks, -Doc -- 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=showamp;file=faq01.027.htp
[Mailman-Users] Map of mailman users (OT)
Hi, We've developed an automatic email mapping capability from Google Maps API. To try it out, we mapped origins of emails to this group from October 3, 2005 through October 14th. The result of this map is at: http://www.zeesource.net/maps/map.do?group=473 Would like to hear what you think of it. Best wishes Claire -- Claire McLister [EMAIL PROTECTED] 1684 Nightingale Avenue Suite 201 Sunnyvale, CA 94087 408-733-2737(fax) http://www.zeesource.net -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] ISO-8859-1/Latin1 vs UTF-8
Bernd Petrovitsch wrote: I actually reported a bug (though it may not sound so): I enter (apparently) UTF-8 text (with Firefox it that is important) and it comes back disguised (and as part of) ISO-8859-1 text. The question is: Which part is doing something wrong and how to fix it? What happens here is that Mailman creates the web page with the META tag in the header META http-equiv=Content-Type content=text/html; charset= where is the encoding of the language of the list (default iso-8859-1 for German), but the web server sends its own http Content-Type: header specifying charset=utf-8. For reasons I don't understand, the HTML standard says the server provided Content-Type: charset takes priority over that specified by an HTML META tag. Thus your browser sets it's encoding as utf-8, but mailman thinks what it gets back is iso-8859-1 and thus garbles the multibyte unicode sequences. It can be fixed by setting the 'German' character set to utf-8 and recoding the German language templates, messages and list archives in utf-8 as discussed in the archive threads I mentioned previously. Alternatively, it can be addressed in the web server by configuring it so it doesn't specify these documents as utf-8. -- 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=showamp;file=faq01.027.htp
[Mailman-Users] bounce-events
hi all... i found (and deleted) a bunch of relatively big bounce-events-* files under the data directory. on line i found a posting citing: - your bounce queue runner isn't running as a possible reason for why these files are piling up there. i do have the qrunner on but which one is the bounce queue runner?! thanks -- -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] bounce-events
have all of those except 'runner=BounceRunner:0:1 -s' ?!??!?! thanks... i do have the qrunner on but which one is the bounce queue runner?! ps -aux | grep qrunner mailman253 0.0 1.433284 12792 ?? S13Oct05 12:49.98 /usr/bin/python /usr/share/mailman/bin/qrunner -- runner=ArchRunner:0:1 -s mailman254 0.0 1.031684 9592 ?? S13Oct05 7:39.19 /usr/bin/python /usr/share/mailman/bin/qrunner -- runner=BounceRunner:0:1 -s mailman255 0.0 1.031684 9456 ?? S13Oct05 6:32.72 /usr/bin/python /usr/share/mailman/bin/qrunner -- runner=CommandRunner:0:1 -s mailman256 0.0 1.131964 10408 ?? S13Oct05 12:23.22 /usr/bin/python /usr/share/mailman/bin/qrunner -- runner=IncomingRunner:0:1 -s mailman257 0.0 0.830260 7112 ?? S13Oct05 6:18.44 /usr/bin/python /usr/share/mailman/bin/qrunner -- runner=NewsRunner:0:1 -s mailman258 0.0 1.737600 15512 ?? S13Oct05 33:56.42 /usr/bin/python /usr/share/mailman/bin/qrunner -- runner=OutgoingRunner:0:1 -s mailman259 0.0 1.031688 9500 ?? S13Oct05 7:50.87 /usr/bin/python /usr/share/mailman/bin/qrunner -- runner=VirginRunner:0:1 -s mailman260 0.0 0.830260 7068 ?? S13Oct05 0:01.80 /usr/bin/python /usr/share/mailman/bin/qrunner -- runner=RetryRunner:0:1 -s The second in this list. Dan -- -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] bounce-events
kalin mintchev wrote: i found (and deleted) a bunch of relatively big bounce-events-* files under the data directory. on line i found a posting citing: - your bounce queue runner isn't running as a possible reason for why these files are piling up there. i do have the qrunner on but which one is the bounce queue runner?! I see from your followup that you determined that the bounce runner has died. This could cause at most one orphaned bounce-events-n.pck file. These files, where n is the pid of the bounce runner are both written and periodically processed and deleted by the bounce runner, so if the bounce runner is not running, new files won't be created and at most one file can be left behind. When the bounce runner is restarted (via Mailman being restarted or whatever), it likely gets a new pid so the old file is orphaned. Clearly this has happened more than once in your case as you had several orphaned files. There may be entries in Mailman's qrunner log noting when the bounce runner died and there may be associated error log entries that might help determine why. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] bounce-events
There may be entries in Mailman's qrunner log noting when the bounce runner died and there may be associated error log entries that might help determine why. hi Mark... here is the log for the last restart of mailman today... there isn't anything about BounceRunner. i used mailmanctl... Oct 24 16:02:27 2005 (1097) Master watcher caught SIGINT. Restarting. Oct 24 16:02:27 2005 (2031) ArchRunner qrunner caught SIGINT. Stopping. Oct 24 16:02:27 2005 (2031) ArchRunner qrunner exiting. Oct 24 16:02:27 2005 (2030) RetryRunner qrunner caught SIGINT. Stopping. Oct 24 16:02:27 2005 (2030) RetryRunner qrunner exiting. Oct 24 16:02:27 2005 (2035) CommandRunner qrunner caught SIGINT. Stopping. Oct 24 16:02:27 2005 (2035) CommandRunner qrunner exiting. Oct 24 16:02:27 2005 (2034) VirginRunner qrunner caught SIGINT. Stopping. Oct 24 16:02:27 2005 (2034) VirginRunner qrunner exiting. Oct 24 16:02:27 2005 (2033) NewsRunner qrunner caught SIGINT. Stopping. Oct 24 16:02:27 2005 (2033) NewsRunner qrunner exiting. Oct 24 16:02:27 2005 (2032) OutgoingRunner qrunner caught SIGINT. Stopping. Oct 24 16:02:27 2005 (2032) OutgoingRunner qrunner exiting. Oct 24 16:02:27 2005 (2029) IncomingRunner qrunner caught SIGINT. Stopping. Oct 24 16:02:27 2005 (2029) IncomingRunner qrunner exiting. Oct 24 16:02:28 2005 (1097) Master qrunner detected subprocess exit (pid: 2031, sig: None, sts: 2, class: ArchRunner, slice: 1/1) [restarting] Oct 24 16:02:28 2005 (1097) Master qrunner detected subprocess exit (pid: 2035, sig: None, sts: 2, class: CommandRunner, slice: 1/1) [restarting] Oct 24 16:02:28 2005 (1097) Master qrunner detected subprocess exit (pid: 2034, sig: None, sts: 2, class: VirginRunner, slice: 1/1) [restarting] Oct 24 16:02:28 2005 (1097) Master qrunner detected subprocess exit (pid: 2032, sig: None, sts: 2, class: OutgoingRunner, slice: 1/1) [restarting] Oct 24 16:02:28 2005 (1097) Master qrunner detected subprocess exit (pid: 2030, sig: None, sts: 2, class: RetryRunner, slice: 1/1) [restarting] Oct 24 16:02:28 2005 (1097) Master qrunner detected subprocess exit (pid: 2029, sig: None, sts: 2, class: IncomingRunner, slice: 1/1) [restarting] Oct 24 16:02:28 2005 (1097) Master qrunner detected subprocess exit (pid: 2033, sig: None, sts: 2, class: NewsRunner, slice: 1/1) [restarting] Oct 24 16:02:39 2005 (2049) CommandRunner qrunner started. Oct 24 16:02:39 2005 (2048) ArchRunner qrunner started. Oct 24 16:02:39 2005 (2053) IncomingRunner qrunner started. Oct 24 16:02:39 2005 (2052) RetryRunner qrunner started. Oct 24 16:02:39 2005 (2050) VirginRunner qrunner started. Oct 24 16:02:39 2005 (2051) OutgoingRunner qrunner started. Oct 24 16:02:40 2005 (2054) NewsRunner qrunner started. -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] bounce-events
kalin mintchev wrote: here is the log for the last restart of mailman today... there isn't anything about BounceRunner. i used mailmanctl... I think that's because you did 'restart' and mailmanctl only restarted those runners that were there. What happens if you do 'stop' and then 'start'? Also, are there any prior entries mentioning BounceRunner between the last time it started and now? -- 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=showamp;file=faq01.027.htp
Re: [Mailman-Users] Migrating lists from old system
Mark Sapiro said: In your case, I'd recommend starting with just the site list on the new system and then copying the lists/ and archives/ directories. The new Mailman will automatically translate the old format files in lists/ as they are used. Well, damn. That was too easy. I was going through all that export/import stuff because I figured that's what I would have to do to keep from bringing a bunch of old cruft with me. Never occurred to me that all I had to do was move the files over. Spent too much time moving database systems around I guess. Thanks for your help. /dwight -- Dwight N. Tovey email: [EMAIL PROTECTED] web: http://www.dtovey.net/~dwight --- Caution - Objects on Calendar are closer than they appear. -- 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=showamp;file=faq01.027.htp
