Re: [Mailman-Users] Attachments are unexpectedly re-created.
(10/03/03 16:54), Masaharu Kawada wrote: Hi Mark-san, I got a reply from the customer, but it was not possbile for the customer to provide the whole digest.mbox to us due to their policy. However, sevral parts of the error log and digest.mbox's content have been provided. As for the error messages, please see the attachment. And as for the digest.mbox which might be the problematic one, I see lots of messages look like below. Hi, Kawada san, The problem is that the Japanese mail users/MUA developers use CP-932 charset as Shift-JIS and its derivatives (ISO-2022-JP/EUC-JP). CP-932 contains more (extended) characters than Shift-JIS while Python codec is strict on the latter. The characters like circled numbers fail to be decoded in unicode and cause error. Similar errors are reported in Japanese Mailman users, like the thread starting from: http://mm.tkikuchi.net/pipermail/mmjp-users/2009-February/002487.html A workaround is to patch charset.py in Python email library as: --- Lib/email/charset.py2009-09-22 08:59:56.0 +0900 +++ Lib/email/charset.py.orig 2009-09-22 08:58:36.0 +0900 @@ -264,8 +264,7 @@ def convert(self, s): Convert a string from the input_codec to the output_codec. if self.input_codec != self.output_codec: -return unicode(s, self.input_codec, 'replace' - ).encode(self.output_codec, 'replace') +return unicode(s, self.input_codec).encode(self.output_codec) else: return s -- Tokio Kikuchi, tkiku...@is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Attachments are unexpectedly re-created.
Hi, (10/03/04 1:58), Mark Sapiro wrote: Masaharu Kawada wrote: There is one thing that I wonder, is that if the charset.py is done with that patch, what the current digest.mbox exsisted under lists/listname are supposed to be? Do they need to be deleted or not? My point on this is that once the patch is done, is there nothing else to do to fix this problem? That is correct. Assuming the underlying issue is fixed by the patch, all you need to do is apply the patch to the Python email library charset.py module (probably at /usr/lib/pythonx.x/lib/email/charset.py) and restart Mailman. Then the next time the digest is triggered, it will be sent with all messages and no more errors. If you apply the patch and restart Mailman and the errors continue, then they are caused by something else. In addition, you should have a lot of shunted messages in qfiles/shunt. They are safely deleted. Note that the patch: --- Lib/email/charset.py 2009-09-22 08:59:56.0 +0900 +++ Lib/email/charset.py.orig 2009-09-22 08:58:36.0 +0900 @@ -264,8 +264,7 @@ def convert(self, s): Convert a string from the input_codec to the output_codec. if self.input_codec != self.output_codec: -return unicode(s, self.input_codec, 'replace' - ).encode(self.output_codec, 'replace') +return unicode(s, self.input_codec).encode(self.output_codec) else: return s is reversed. The '+' is the original code and the '-' is the new code. Yes. Thanks Mark. -- Tokio Kikuchi, tkiku...@is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Attachments are unexpectedly re-created.
(10/03/04 11:47), Masaharu Kawada wrote: Hi Mark-san, Kikuchi-san, Thank you very much for your help. Just to make sure, about the patch, is it just need to be modified in the way you mentioned? Which means that it should be look like below. Yes, its OK. # vi /usr/lib/python2.4/email/Charset.py ---Before modifying--- 243 def convert(self, s): 244 Convert a string from the input_codec to the output_codec. 245 if self.input_codec self.output_codec: 246 return unicode(s, self.input_codec).encode(self.output_codec) 247 else: 248 return s ---After modifying--- 243 def convert(self, s): 244 Convert a string from the input_codec to the output_codec. 245 if self.input_codec != self.output_codec: 246 return unicode(s, self.input_codec, 'replace').encode(self.output_codec, 'replace') 247 return unicode(s, self.input_codec).encode(self.output_codec) 248 else: 249 return s Best Regards, Tokio Kikuchi wrote: Hi, (10/03/04 1:58), Mark Sapiro wrote: Masaharu Kawada wrote: There is one thing that I wonder, is that if the charset.py is done with that patch, what the current digest.mbox exsisted under lists/listname are supposed to be? Do they need to be deleted or not? My point on this is that once the patch is done, is there nothing else to do to fix this problem? That is correct. Assuming the underlying issue is fixed by the patch, all you need to do is apply the patch to the Python email library charset.py module (probably at /usr/lib/pythonx.x/lib/email/charset.py) and restart Mailman. Then the next time the digest is triggered, it will be sent with all messages and no more errors. If you apply the patch and restart Mailman and the errors continue, then they are caused by something else. In addition, you should have a lot of shunted messages in qfiles/shunt. They are safely deleted. Note that the patch: --- Lib/email/charset.py2009-09-22 08:59:56.0 +0900 +++ Lib/email/charset.py.orig2009-09-22 08:58:36.0 +0900 @@ -264,8 +264,7 @@ def convert(self, s): Convert a string from the input_codec to the output_codec. if self.input_codec != self.output_codec: -return unicode(s, self.input_codec, 'replace' - ).encode(self.output_codec, 'replace') +return unicode(s, self.input_codec).encode(self.output_codec) else: return s is reversed. The '+' is the original code and the '-' is the new code. Yes. Thanks Mark. -- Tokio Kikuchi tkiku...@is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Mailman Sibling lists
Hi, I currently have the below setup Parent list Sibling list Staff staff-info All-info Non-staff non-staff-info All-info This all works correctly except when a e-mail is sent to both the staff and non-staff parent lists. It results in the people on 'All-info' list receiving duplicate e-mails. I have tried adding the staff list into the regular_exclude_lists in the 'non-staff' list but this does not work Exclude/include is done if the list address appears explicitly on the To:/Cc: headers. You should write 'staff-info' and 'non-staff-info' in the regular_exclude_lists of 'All-info' and send a message 'To:staff-info,non-staff-info,All-info' to avoid duplicates. -- Tokio Kikuchi, tkiku...@is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] Post number in subject line
Hello all, Is there anyone know how to show the post number in subject line? This number will be increased every time the member post something to the list. I have tried to search through Mailman's settings but seem no luck. What is the version of your mailman? Subject numbering feature was introduced in 2.1.6. You will see the following info in admin-subject_prefix-detail page, if your version supports numbering: You can also add a sequencial number by %d substitution directive. eg.; [listname %d] - [listname 123] (listname %05d) - (listname 00123) Cheers, -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] UnicodeDecodeError during Archive Obscuring
Hi,
I've seen a increase in use of Unicod'ed email address which fail
HyperArch email obscuring and thus cause the msg to be shunted and not
archived.
Specifically the problem lies in the encoding (strangely the error says
Decode) of the text ' at ' (as a substitute for @) for Russian
users of GMail.
Here is the error in full:
File /usr/local/mailman/Mailman/Archiver/HyperArch.py, line 579, in
as_text
atmark = unicode(_(' at '), Utils.GetCharSet(self._lang))
UnicodeDecodeError: 'ascii' codec can't decode byte 0xd0 in position 1:
ordinal not in range(128)
Nov 22 04:42:31 2007 (755) SHUNTING: 1195717174.0985031
+6fdaf61658ca76ec5281e614be7b4b59d1e01bf6
This is a Mailman 2.1.9 system.
I did search the archives quite extensively, but I didn't find any cases
where Mailman was having trouble encoding the hard coded ' at ' into
unicode.
It is not ' at ' itself but it's translation which caused this error.
It's strange though the language set immediately before should work for
its unicode conversion.
Any ideas on what to try/test/do?
How about this patch (sorry for the word wrap) for work around.
=== modified file 'Mailman/Archiver/HyperArch.py'
--- Mailman/Archiver/HyperArch.py 2007-11-21 05:21:24 +
+++ Mailman/Archiver/HyperArch.py 2007-11-25 03:59:07 +
@@ -412,7 +412,8 @@
otrans = i18n.get_translation()
try:
i18n.set_language(self._lang)
-atmark = unicode(_(' at '),
Utils.GetCharSet(self._lang))
+atmark = unicode(_(' at '),
Utils.GetCharSet(self._lang),
+ 'replace')
subject = re.sub(r'([-+,.\w]+)@([-+.\w]+)',
'\g1' + atmark + '\g2', subject)
finally:
@@ -574,7 +575,7 @@
if mm_cfg.ARCHIVER_OBSCURES_EMAILADDRS:
otrans = i18n.get_translation()
try:
-atmark = unicode(_(' at '), cset)
+atmark = unicode(_(' at '), cset, 'replace')
i18n.set_language(self._lang)
body = re.sub(r'([-+,.\w]+)@([-+.\w]+)',
'\g1' + atmark + '\g2', body)
--
Tokio Kikuchi, [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
--
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] I lost my patch :-(
In my ‘board_member’ list, under “Privacy options” (Sender filters). I have: [EMAIL PROTECTED] in the box labeled “List of non-member addresses whose postings should be automatically accepted” http://sourceforge.net/tracker/index.php?func=detailaid=1220144group_id=103atid=300103 -- 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] archive processing problem (mmarch w/ MIME)
John Reddy wrote: What exactly was the Content-Type header line ? Here's the snippit of message header. I don't see any problem with the line as is, this is how it exists in the message header. The mbox is readable by mutt (my text email reader of choice). Content-Transfer-Encoding: binary Content-Type: multipart/alternative; boundary=_--=_1136314441199510 MIME-Version: 1.0 If I delete these lines from the mbox, the process will continue to the next entry in the mbox and then it will fail with the same set of error messages again: How about deleteing the first line (Content-Transfer-Encoding: binary) and leave the rest. Content-Transfer-Encoding: binary Content-Type: multipart/alternative; boundary=_--=_1136319711206230 MIME-Version: 1.0 Doesn't make much sense to me why it's having trouble ingesting MIME. I believe CTE should not be in the main section of message header if Content-Type is multipart. -John -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] archive processing problem (mmarch w/ MIME)
File /var/lib/mailman/Mailman/Handlers/Scrubber.py, line 175, in replace_payload_by_text msg.set_payload(text, charset) File email/Message.py, line 218, in set_payload File email/Message.py, line 242, in set_charset TypeError: us-ascii mmarch seems to be having trouble with the Content-Type header line. If I pull out that line for a given message, it is ingested, though it displays the full MIME text. What exactly was the Content-Type header line ? -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] Mail stopped sending out to mailing list users
Hi Jared, I'm curious what kind of message caused this error. I think that the exact message causing this error contains a header like: Content-Type: text/plain; charset=base64 It would be nice if you can check the moved digest.mbox and answer if my hyposis is right or not. Mark, I've checked in a patch for this error. Will you please review it and back out if it is not appropriate because I have not much time to spend now. Tokio Jared Nyland wote: Hi Mark, I have found a fix for this issue. In the /var/lib/mailman/lists/listname, I remane the digest.mbox then run the /bin/unshunt. It looks like it is working now. Thanks again for all your help Jared On 5/9/07, Jared Nyland [EMAIL PROTECTED] wrote: Hi Mark, Thanks for the help on this, I did try those but still does not work. In doing some more trouble shooting I have found that the message that I am sending is getting stuck in the shunt directory. I have also found in the mailman log file that I get this error. May 09 09:49:46 2007 (5607) Uncaught runner exception: May 09 09:49:46 2007 (5607) Traceback (most recent call last): File /usr/lib/mailman/Mailman/Queue/Runner.py, line 110, in _oneloop self._onefile(msg, msgdata) File /usr/lib/mailman/Mailman/Queue/Runner.py, line 160, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /usr/lib/mailman/Mailman/Queue/IncomingRunner.py, line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Handlers/ToDigest.py, line 91, in process send_digests(mlist, mboxfp) File /usr/lib/mailman/Mailman/Handlers/ToDigest.py, line 132, in send_digests send_i18n_digests(mlist, mboxfp) File /usr/lib/mailman/Mailman/Handlers/ToDigest.py, line 306, in send_i18n_digests msg = scrubber(mlist, msg) File /usr/lib/mailman/Mailman/Handlers/Scrubber.py, line 304, in process t = unicode(t, partcharset, 'replace') File /usr/lib/python2.3/encodings/base64_codec.py, line 41, in base64_decode assert errors == 'strict' AssertionError May 09 09:49:47 2007 (5607) SHUNTING: 1178725785.6627519+f5e2d81766111458741eb658164fc17d90bde0ab Thanks again Jared On 5/9/07, Mark Sapiro [EMAIL PROTECTED] wrote: Jared Nyland wrote: I have run into a issues where mail has all of a sudden stopped being sent to the mailing list. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.078.htp, particularly items 5b, 6 and 7. Most likely, one or more of your qrunners isn't running and messages are just waiting in Mailman's qfiles/in/ or qfiles/out/ queues. -- Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] Mail stopped sending out to mailing list users
I wrote: Hi Jared, I'm curious what kind of message caused this error. I think that the exact message causing this error contains a header like: Content-Type: text/plain; charset=base64 It would be nice if you can check the moved digest.mbox and answer if my hyposis is right or not. hypothesis of course. Sorry for bad english, my brain is still sleeping at 6AM. -- 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] Attachments - archives and encoding problems
Hi, Here is a URL where I created a list for testing mailman. https://mail.bioacademy.gr/pipermail/testlist2/2007-May/thread.html Your site use Mailman-2.1.5 which is way too old. Upgrade to the current version (2.1.9) and try again. -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] [Fwd: TypeError: us-ascii with python2.4 and mailman 2.1.8-1 (debian)]
Hi developers,
This particular problem is caused by a bug in email 4.0.1 package which
was fixed in the most recent subversion repository.
http://svn.python.org/view/python/trunk/Lib/email/message.py?rev=54333r1=50840r2=54333
Maybe it's time to think of next bug fix release of mailman 2.1.10 as
soon as the email 4.0.2(?) is out.
Justin Warren wrote:
Hi folks,
I hit the same sort of problem as a couple of other people apparently
have, eg:
http://mail.python.org/pipermail/mailman-users/2006-November/054246.html
I hit this when Mailman attempts to send digests.
I thought I'd tracked the issue to the way Charset is used within
Mailman/Scrubber.py, on line 193 (some modifications by me to print
debug output):
charset = None
lcset = Utils.GetCharSet(mlist.preferred_language)
print getting charset for preferred language:, repr(lcset)
lcset_out = Charset(lcset).output_charset or lcset
print lcset_out is:, repr(lcset_out)
Which yields:
getting charset for preferred language: 'us-ascii'
lcset_out is: u'us-ascii'
It appears that Charset returns a unicode string for
its .output_charset, which python2.4 email.Message.set_charset() does
not recognise as a string, and it isn't a Charset either, so a TypeError
is raised.
I don't know enough about why .output_charset is being used, or why it
is unicode, but it seems that changing line 193 to read:
lcset_out = Charset(lcset) or lcset
would prevent this error.
However, something else is also returning a unicode string, since after
changing Scrubber, you end up with this error:
Traceback (most recent call last):
File /usr/lib/mailman/cron/senddigests, line 94, in ?
main()
File /usr/lib/mailman/cron/senddigests, line 86, in main
mlist.send_digest_now()
File /var/lib/mailman/Mailman/Digester.py, line 60, in send_digest_now
ToDigest.send_digests(self, mboxfp)
File /var/lib/mailman/Mailman/Handlers/ToDigest.py, line 142, in
send_digests
send_i18n_digests(mlist, mboxfp)
File /var/lib/mailman/Mailman/Handlers/ToDigest.py, line 339, in
send_i18n_digests
mcset = msg.get_content_charset('')
File /usr/lib/python2.4/email/Message.py, line 805, in get_content_charset
charset = unicode(charset, 'us-ascii').encode('us-ascii')
TypeError: decoding Unicode is not supported
I haven't worked out what this other thing is as yet.
Alternately, patching email/Message.py (line 803) to ignore a charset
that is a unicode string seems to work, but is probably fragile or
broken in other ways:
# charset character must be in us-ascii range
try:
if not isinstance(charset, unicode):
charset = unicode(charset, 'us-ascii').encode('us-ascii')
except UnicodeError:
return failobj
I hope this helps someone more knowledgable about Mailman to work out
what the underlying problem is.
--
Tokio Kikuchi, [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
--
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] [Mailman-Developers] [Fwd: TypeError: us-asciiwith python2.4 and mailman 2.1.8-1 (debian)]
Mark Sapiro wrote: Tokio Kikuchi wrote: Hi developers, This particular problem is caused by a bug in email 4.0.1 package which was fixed in the most recent subversion repository. http://svn.python.org/view/python/trunk/Lib/email/message.py?rev=54333r1=50840r2=54333 Maybe it's time to think of next bug fix release of mailman 2.1.10 as soon as the email 4.0.2(?) is out. But Mailman 2.1.x ships with and should be installed with the email 2.5.x branch, so unless this bug was also introduced and subsequently fixed in that branch as well, it shouldn't affect a properly installed Mailman. Oh yes, you're right, Mark. I was too much involved in mailman 2.2 which will be shipped with email 4.0.x. Perhaps, we should make warning against package distributers that 'misc' directory (pythonlib) in the mailman source tree can't be omitted. BTW, I'm looking forward to see email 4.0.2 out. ;-) -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] Language encoding and digests...
Krystal F. Zipfel wrote: Random question, and unfortunately I'm having trouble finding answers since most of the things I have found aren't in my language... Has anyone here ever attempted to use EUC-JP encoding along with digests? I recently ran into an issue with a list whom was using Japanese as they're language, and the digest mbox file actually caused any other list on that server to not receive digests and I have absolutely no clue why or how. I don't fully understand your situation but there is a common problem in Japanese people who don't care (or ignorant) about 'machine dependent characters' like number in circle or double width roman numerals. If those characters are used in 'iso-2022-jp' declaration of charset, mailman and python codecs fail to process such characters and single processes like 'cron/senddigests' stops working. My advice is to remove (or rename for later inspection) the digest.mbox file from the Japanese list directory and set digestable=0 if they keep using the 'machine dependent characters'. Just a thought, Krystal -- -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] Infamous error ImportError: ld.so.1: python: fatal: libgcc_s.so.1
However, when I try to access Mailman via my browser (using Apache on the server side) I get the infamous error message: The /usr/local/lib version seems to be more recent. Before installation, I made sure that LD_LIBRARY_PATH was set to So, the apache was not running under LD_LIBRARY_PATH envrironment. You should setenv LD_RUN_PATH while compiling or use crle. Read the crle man for detail. -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] Infamous error ImportError: ld.so.1: python: fatal: libgcc_s.so.1 (followup)
Rolf E. Sonneveld wrote: Tokio Kikuchi wrote: However, when I try to access Mailman via my browser (using Apache on the server side) I get the infamous error message: The /usr/local/lib version seems to be more recent. Before installation, I made sure that LD_LIBRARY_PATH was set to So, the apache was not running under LD_LIBRARY_PATH envrironment. You should setenv LD_RUN_PATH while compiling or use crle. Read the crle man for detail. as a followup to my previous message: I just did a ldd for httpd and this is the result: bash-3.00# ldd /usr/local/apache/bin/httpd It's not httpd which caused that error. Maybe its python and/or a module which resides in python library path (.../lib/python2.x/) which is called from httpd running environment. You should set LD_RUN_PATH properly while compiling python, mailman, and httpd. LD_LIBRARY_PATH is only effective when the compiled executable is running. So, you might want to startup httpd like: # LD_LIBRARY_PATH=/whatever/lib /some/where/bin/apachectl start -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] [Mailman-Developers] Problem with format=flowed patch
Hi Mark,
I was working this patch on the trunk.
I think the indent level of this part in Scrubber.py should be
if charset is None:
charset = part.get_content_charset(lcset)
+format = part.get_param('format')
+delsp = part.get_param('delsp')
Sorry if I misunderstand.
Mark Sapiro wrote:
I have been working on a fix for the problem of Mailman's dropping
format=flowed from Content-Type: headers. There is a bug report and a
patch at
https://sourceforge.net/tracker/?func=detailatid=100103aid=1495122group_id=103.
The patch to Scrubber.py has just been revised (revised patch is
attached to the above tracker item).
Scrubber would throw an exception when processing a message with no
text/plain part. If you are using a prior version of this patch,
please get the current version to avoid this problem.
--
Tokio Kikuchi, [EMAIL PROTECTED]
http://weather.is.kochi-u.ac.jp/
--
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] [Mailman-Developers] Problem with format=flowed patch
Mark Sapiro wrote: I don't think your suggestion is correct. What I am trying to do is get the format= and delsp= parameters from only the first text/plain part in the message. Often, this will be the only part in which case it doesn't matter. Sorry that I misunderstood. It was a little bit too early in the morning to start working. ;-) (6AM Japan) I've almost done with this 'format=flowed' patch and others for Scrubber.py and Decorate.py for the trunk. I'll commit them after adding some more test codes. -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] [Mailman-Developers] My new job
Congratulations, Barry! I'm very happy to hear that you can spend more time on Mailman. I also learned by quick search that Canonical is founded by this nice guy. :) http://en.wikipedia.org/wiki/Mark_Shuttleworth Barry Warsaw wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello everyone, I just wanted to drop a quick note to let you know that I have started working for Canonical, the folks who distribute Ubuntu Linux and develop the Launchpad service for distributed open source development. I'm quite excited to be working for Canonical. They are a Python and Zope shop, very open source friendly, and based on Linux, so I'm working in an environment that's both familiar and fun. They're also a distributed company, without traditional offices, but with many folks working all over the world. They're also hiring wink, wink. :) While this is good for Barry (and hopefully good for Canonical :), I know you're thinking, what does this mean for Mailman? Well, I'm glad you asked! Part of my official duties will be to integrate Mailman with Launchpad so as to enable more powerful communication patterns among members of a distributed development team. While I won't be spending /all/ of my time on Mailman, it will be getting some official love. I hope that this will help move the current development branch closer to a release some time later this year. Other than that, not much will really change. Mailman is and will always be released under the GPL, and it will continue to be a GNU project. If you have any questions or concerns, please send them directly to me. I will attempt to answer them as best I can, and if there are common themes, I'll post updates here. Thanks for your support and keep on delivering with Mailman! - -Barry Here are some related links: http://www.canonical.com http://www.ubuntu.com http://launchpad.net P.S. I'll be at PyCon this year so if you're coming too, please say hi! -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (Darwin) iQCVAwUBRcUTb3EjvBPtnXfVAQIQKgP/XFVeeDBn6QVXkE9oK1YJxyrLZZET5GxT TAvTJgfndkcWPuUpbC5D6hcpDNa6sfIgJnR3enoW7MgKpOAtIXTuXqPpNiFMBVT2 qUhlDHhwYzdJWWyzI/oXGRvt0lMqqA69Iu7A6DAKrgksBB128V/mYxTfv8BPmF4W uASb/9MkmAQ= =h+IQ -END PGP SIGNATURE- -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] Read Receipt uncaught bounces was: (no subject)
Mark Sapiro wrote: Whitcomb, Jeff wrote: I am wondering if there is any way I can stop getting all these Read Receipt messages when people send an email to a Mailman list, without turning off bounce processing all together. This is just one more reason why Read Receipts are bad. What exactly is the header name? We already strip these headers by Mailman/Handlers/Cleanse.py: # Some headers can be used to fish for membership del msg['return-receipt-to'] del msg['disposition-notification-to'] del msg['x-confirm-reading-to'] It should not be difficult to add one or more in the next release. -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] A scrubber issue
Folks, I'm OK with changing the recomposing part in Scrubber.py: if not part or part.is_multipart(): continue to if part.is_multipart(): continue It looks like the email package is more robust than it was when the bug report was issued and the Scrubber code was patched. But as to the default charset is 'us-ascii' problem, if we put the part together the parts, some language text (like japanese) become irreversibly unreadable. It is safe to keep it in a separate file if you can't archive the whole message in multipart like in Pipermail. Additionally, the diff file which was said to be lost in the first post is in: http://lists.gnupg.org/pipermail/gnupg-users/attachments/20061207/6bd11edc/attachment.diff I believe the folks in gnupg.org can fix the reference in the pipermail archive by fixing the PUBLIC_ARCHIVE_URL in mm_cfg.py and re-generating the archive by bin/arch --wipe command. Mark Sapiro wrote: Todd Zullinger wrote: Related to the second part of Werner's message being scrubbed with the message: An embedded and charset-unspecified text was scrubbed... Poking in the email package (on python 2.4.4) shows: def get_content_charset(self, failobj=None): Return the charset parameter of the Content-Type header. The returned string is always coerced to lower case. If there is no Content-Type header, or if that header has no charset parameter, failobj is returned. This seems to violate section 5.2 of RFC 2045 which says parts lacking a Content-type header should be assumed to be text/plain with a charset of us-ascii. The get_content_type method in email.Message does mention RFC 2045 and uses text/plain if the content-type is invalid. It does seem inconsistent, but I don't think we can call it a violation of the RFC yet, it depends on what the caller does with it. Would it be appropriate to set failobj=us-ascii when calling this method in Scrubber.py? It might be, but I'd like to hear from Tokio first. Clearly this was considered at one point as a specific case and message exist for it where it would have been simpler to just assume it is us-ascii. Thus, I think there must be messages in the wild with parts with unspecified character sets that aren't us-ascii. -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] A scrubber issue
Hi all, Mark Sapiro wrote: Todd Zullinger wrote: Attached is the original message from the list mbox and one that I munged up to included a content-type: text/plain; charset=3Dus-ascii. I see the symptom with the original message. I'll look further, but it seems to have something to do with the fact that the first sub-part has no headers at all. I have looked at RFC 2045 and I don't see that any headers are required, but I don't yet know what the underlying issue in Scrubber is. It looks like the problem is something to do with email package behavior. Here is a test code to reproduce the problem: from email import message_from_string s = '''MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ABCDEFG Preamble --ABCDEFG A message without header --ABCDEFG Content-Disposition: inline Another text with a header --ABCDEFG-- ''' m = message_from_string(s) for p in m.walk(): print p.get_content_type() if p: print p.get_payload(decode=True) This program prints out like this: multipart/mixed None text/plain text/plain Another text with a header Note that 'A message without header' is not printed out. If I remove 'If p:' and print the payload unconditionally, I get: multipart/mixed None text/plain A message without header text/plain Another text with a header Here, the no-header part is printed out. The patch of revision 7281 may have been over-protective against the bug-id: 1099138 in message reconstruction part (line 327 in http://mailman.svn.sourceforge.net/viewvc/mailman/branches/Release_2_1-maint/mailman/Mailman/Handlers/Scrubber.py?r1=7207r2=7281 ) but we may have to be paranoid against wired message like no-header text. I believe well behaved MUAs won't generate no-header text parts. (or, I believed ;-) -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] Problem With DEFAULT_URL_PATTERN
DEFAULT_URL_HOST = 'https://mailman.ce.berkeley.edu' should be 'mailman.ce.berkeley.edu'. -- Tokio Kikuchi [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] Umbrella List / Moderation
(b) Duplicate receiving email addresses (on two or all three of the sublists) are not being eliminated. No way to win here, currently. Try this patch. http://sourceforge.net/tracker/index.php?func=detailaid=1347962group_id=103atid=300103 -- Tokio Kikuch, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] mail keeps looping back to list due to filter rule
Matthew Clarkson wrote: My mailing lists have been running fine on our mailman 2.1.7 server for the last year, however, I just implemented a filter for spam on one of our public lists to catch anything that spamassassin marks with a ***SPAM*** subject. The filter rule I imposed on this list is subject: .*SPAM.* This was fixed in 2.1.8 and now 2.1.9 is out. Please upgrade. -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] [Mailman-Developers] OS X Mailman Python
In summary my preferences would be: Mailman 2.1.x supported on Python 2.3, 2.4, and 2.5. Drop support for Python 2.1 and 2.2. We've done this accidentally in Mailman 2.1.9, so let's make it official. Mailman 2.2 supported on Python 2.4 and 2.5. +1 -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] can't call command line functions from php
couple of users to the mailman group, I've tried the chmod g+s for all the scripts. All to no effect. I'm beginning to wonder if it may be a systems issue--something wrong with the way it's handling group permissions. Scripts can't be run under setuid/setgid on *nix systems. You may have to change the user's primary group as mailman or use newgrp command on solaris. -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] Problems with digests
In short: Replace the first line in /usr/lib/mailman/cron/senddigests # ! /usr/bin/python by #! /usr/bin/python2.3 if you have a Python2.3 installed. As this problem appeared here (debian/etch, Mailman 2.1.8-2) after upgrading Python 2.3 to 2.4 this seems to be reasonable. Hi, I want to clarify the situation. Is this specific to debian? Can you try these and check the email version? $ python Python 2.4.3 ... import email email.__version__ '3.0.1' ^D $ cd prefix/cron $ python Python 2.4.3 ... import paths import email email.__version__ '2.5.7' The email-3.0.x in Python 2.4 is not suitable for mailman. Mailman 2.1.8(or 9) works best with the email-2.5.7(or 8) which is the bug fix version of Python 2.3 library. -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] Problems with digests
Hi, The email-3.0.x in Python 2.4 is not suitable for mailman. Mailman 2.1.8(or 9) works best with the email-2.5.7(or 8) which is the bug fix version of Python 2.3 library. I see. How can I fix that? I suspect the debian people have omitted the mailman-2.5.x package from their ports. File a bug report on their developers site. In the mean time, you can extract email-2.5.x from our official distribution and install into prefix/pythonlib directory. Or, you can edit cron/senddigests to use python2.3 as was suggested earlier. Cheers, -- Tokio Kikuchi, [EMAIL PROTECTED] http://weather.is.kochi-u.ac.jp/ -- 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] RELEASED: Mailman 2.1.8
On behalf of the development team, I'm pleased to announce the release of GNU Mailman 2.1.8. In this release, we have fixed a cross-site scripting security bug in the previous release (CVE-2006-1712), integrated a new version of email library (email-2.5.7), and added bounce processing supports for number of sites and MUAs. It is highly recommended that all sites using 2.1.7 and before should update to this release. Mailman is free software for managing email mailing lists and e-newsletters. For more information, see: http://mailman.sourceforge.net/ For links to download the Mailman 2.1.8 source tarball, see: http://sourceforge.net/project/showfiles.php?group_id=103 (Note that uploading to the mirror sites may be delayed.) -- Tokio Kikuchi -- 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] Released: Mailman 2.1.8 release candidate
Hi all, Mailman 2.1.8rc1 was released for the final test of 2.1.8. Important: This is not only a release candidate but also include a fix for a cross-site scripting bug found in 2.1.7. All sites running previous versions are adviced to upgrade to 2.1.8(rc1). I am going to release the final by the next weekend if nothing serious happens. Please download it from Sourceforge file area: http://sourceforge.net/project/showfiles.php?group_id=103 Cheers, Tokio --- Here is a history of user visible changes to Mailman. 2.1.8rc1 (07-Apr-2006) Security - A cross-site scripting hole in the private archive script of 2.1.7 has been closed. Thanks to Moritz Naumann for its discovery. Bug fixes and other patches - Bouncers support added: 'unknown user', Microsoft SMTPSVC, Prodigy.net and several others. - Updated email library to 2.5.7 which will encode payload into qp/base64 upon setting. This enabled backing out the scrubber related patches including 'X-Mailman-Scrubbed' header in 2.1.7. - Fix SpamDetect.py potential hold/reject loop problem. - A warning message from email package to the stderr can cause error in Logging because stderr may be detached from the process during the qrunner run. We chose not to output errors to stderr but to the logs/error if the process is running under mailmanctl subprocess. - DKIM header cleansing was separated from Cleanse.py and added to -owner messages too. - Fixes: Lose Topics when go directly to topics URL (1194419). UnicodeError running bin/arch (1395683). edithtml.py missing import (1400128). Bad escape in cleanarch. Wrong timezone in list archive index pages (1433673). bin/arch fails with TypeError (1430236). Subscription fails with some Language combinations (1435722). Postfix delayed notification not recognized (863989). 2.1.7 (VERP) mistakes delay notice for bounce (1421285). show_qfiles: 'str' object has no attribute 'as_string' (147). Utils.get_domain() wrong if VIRTUAL_HOST_OVERVIEW off (1275856). Miscellaneous - Brad Knowles' mailman daily status report script updated to 0.0.16. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] Released: Mailman 2.1.8b1
Hi Mailman-Users, -Developers and -i18ners, Mailman 2.1.8b1 was released for beta test. Talks are going around on the start of 2.2 after the release of 2.1.8 the final of 2.1-maint branch. I really want to call this final than beta but we should take careful steps. Please download it from Sourceforge file area: http://sourceforge.net/project/showfiles.php?group_id=103 Cheers, Tokio --- Here is a history of user visible changes to Mailman. 2.1.8b1 (23-Mar-2006) Bug fixes and other patches - Bouncers support added: 'unknown user', Microsoft SMTPSVC, Prodigy.net and several others. - Updated email library to 2.5.7 which will encode payload into qp/base64 upon setting. This enabled backing out the scrubber related patches including 'X-Mailman-Scrubbed' header in 2.1.7. - Fix SpamDetect.py potential hold/reject loop problem. - A warning message from email package to the stderr can cause error in Logging because stderr may be detached from the process during the qrunner run. We chose not to output errors to stderr but to the logs/error if the process is running under mailmanctl subprocess. - DKIM header cleansing was separated from Cleanse.py and added to -owner messages too. - Fixes: Lose Topics when go directly to topics URL (1194419). UnicodeError running bin/arch (1395683). edithtml.py missing import (1400128). Bad escape in cleanarch. Wrong timezone in list archive index pages (1433673). bin/arch fails with TypeError (1430236). Subscription fails with some Language combinations (1435722). Postfix delayed notification not recognized (863989). 2.1.7 (VERP) mistakes delay notice for bounce (1421285). show_qfiles: 'str' object has no attribute 'as_string' (147). Utils.get_domain() wrong if VIRTUAL_HOST_OVERVIEW off (1275856). Miscellaneous - Brad Knowles' mailman daily status report script updated to 0.0.16. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] 1 email for multiple email-list recipients onsame server?
Hi, Matt England wrote: At 3/9/2006 10:29 AM, Patrick Bogen wrote: On 3/9/06, Matt England [EMAIL PROTECTED] wrote: ...and this seems to be the trickiest part: which list becomes the primary one. I can envision straightforward (even though they are not easy to implement solutions) to everything except this last point. :( Easy enough: The first list on the list of lists (does that make sense? The first list that is listed in the message as a recipient) is primary. If I'm not first, I don't deliver. If I am, go for it. Or the first alphabetically. It doesn't really matter, as long as everything agrees. Makes sense. I suspect a feature like this will never make it into a pre-3 release, if ever. Actually, a patch to make it possible is waiting to be integrated in mailman-2.2. http://sourceforge.net/tracker/index.php?func=detailaid=1347962group_id=103atid=300103 I want to merge into the CVS trunk as soon as the next mailman-2.1.8 bug fix release is out. Alas, this makes for a nice reference thread; umbrella lists may be the more-popular answer, at least for now. -Matt -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] KNOWN_USERS + SpamAssassin discarding lots of mail
Patrick Bogen wrote:
Now, here's the problem with this.
X-Spam-Status for a non-spam message may look like:
X-Spam-Status: No, score=-5.0 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 ...
(and keeps going for a while.)
As should be pretty obvious, 'Yes' case-insensitively is found in
'BAYES'. This won't occur with the header_filter_rules, because they
match the header as a line, rather than treating the value separately.
So, as an alternative, it should be possible to use a KNOWN_SPAMMER of
('X-Spam-Status', '^Yes').
Or, you should use:
('x-spam-flag', 'yes'),
Cheers,
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
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] Unknown password on new list...
Daevid Vincent wrote: I just set up a new list, and must have fat fingered the password. How can I change it since I cannot log into the GUI? You can use the master site password to log in the admin page and change the list password. If you can not use GUI for any other reason, then use bin/withlist to change the password with a little trick like this: % bin/withlist test Loading list test (unlocked) The variable `m' is the mm-test MailList instance import sha p = 'newpass' cp = sha.new(p).hexdigest() m.Lock() m.password = cp m.Save() m.Unlock() Finalizing % I see 'mmsitepass', but it changes a master password for all lists. I don't want that. I only want to change for ONE specific list. Also, this seems kind of short-sighted that it takes only one password on the command line and hides the typing. Why doesn't mailman ask for a confirmation of the password, and keep re-prompting for a new one if they do not match? -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] 500 Internal Server Error with edithtml (but not admin, admindb and the rest)
Hi, Edward Muller wrote: I setup mailman for a customer of ours and when they try to use edithtml they get a 500 Internal Server Error. Apache's logs just say: Premature end of script headers: /home/virtual/site47/fst/var/www/mailman/edithtml So that's no help. This is *also* fixed by this patch: http://sourceforge.net/tracker/index.php?func=detailaid=1405790group_id=103atid=300103 Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] 500 Internal Server Error with edithtml (butnotadmin, admindb and the rest)
Edward Muller wrote: I reviewed the patch a bit and it looks reasonable to apply, so I applied it. However edithtml/traffic (traffic being the name of the list) still returns a 500 error and there is nothing in the error log. If nothing in the mailman log, then check the httpd (apache?) error_log. http://www.mission2007.org/mailman/edithtml/traffic On Tuesday 07 February 2006 04:16 pm, Mark Sapiro wrote: Edward Muller wrote: So which part of this patch fixes the problem I'm getting? The part that adds import re to Mailman/Cgi/edithtml.py But you may run into one of the other bugs sooner or later, so why not apply the whole patch? -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] Problem with arch after upgrade
Jon Harris wrote:
Hi List
I have just got round to upgrading from 2.1.6 to 2.1.7 and the upgrade
went well.
File /usr/local/mailman/Mailman/Archiver/HyperArch.py, line 579, in
as_text
'\g1' + _(' at ') + '\g2', body)
File /usr/lib/python2.2/sre.py, line 143, in sub
return _compile(pattern, 0).sub(repl, string, count)
UnicodeError: ASCII decoding error: ordinal not in range(128)
Please apply this patch and look how it goes.
http://sourceforge.net/tracker/index.php?func=detailaid=1405790group_id=103atid=300103
Apply with patch -p0 (or -p1) this_patch in the source tree and make
install again.
--
Which doesn't look good :-( Should I be worried?
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
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] mailing list not obeying sender filter
Steven Jones wrote: HI All, I have added the [EMAIL PROTECTED] and [EMAIL PROTECTED] for each server to the privacy-option - sender-filter - non-member filters box and done a submit, but the system is still asking me to moderate the emails...while I just want them accepted and posted. Check also the recipient filter. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] any info on this reported exploit?
Hi, Diana Orrick wrote: http://www.securityfocus.com/bid/16248/discuss GNU Mailman Large Date Data Denial Of Service Vulnerability GNU Mailman is prone to a denial of service attack. This issue affects the email date parsing functionality of Mailman. The vulnerability could be triggered by mailing list posts and will impact the availability of mailing lists hosted by the application. __ this notice was from [EMAIL PROTECTED]: 06.3.18 CVE: CVE-2005-4153 Platform: Unix Title: GNU Mailman Large Date Data Denial of Service Description: Mailman is software to help manage email discussion lists, much like Majordomo and SmartList. The application is exposed to a denial of service issue when it attempts to parse very large numbers of dates contained in email messages. All current versions are affected. Ref: http://www.securityfocus.com/bid/16248 __ Once it was only a bug which could cause nuisance in administrative task. Now they start to call it a DoS and threaten us. ;-) Mailman sends messages in both regular and digest delivery. The digest processing is inserted in the middle of regular delivery if the messages accumulated to a preset amount. If there is a serious error in the digest processing, the regular delivery fails. Since the messages are accumulated already, arrival of following message triggers the digest processing again and also fail in the subsequent regular delivery. This is the mechanism of Denial of Service. Therefore, the site administrator should check the qfiles/shunt directory and the logs/error file periodically. Brad Knowls' Daily Status Report should help in this respect. I really want to rewrite it in python and include in the official cron jobs (if I had enough time before the next release of mailman 2.2). http://sourceforge.net/tracker/index.php?func=detailaid=1123383group_id=103atid=300103 Mailman has many check points that prevents such a malicious messages to be passed through and site/list admins could be able to find workarounds. But, from mailman-2.1.7, we solved the problem by separating the error from regular delivery by the python try-except techique. The digest delivery will be still stopped by the malicious message but this should be notified to the site administrator by the cron/senddigests command. So, the answer to this CVE is upgrade to 2.1.7. We found mailman-2.1.7 still has a few bugs and also uploaded an official patch: http://sourceforge.net/tracker/index.php?func=detailaid=1405790group_id=103atid=300103 I hope we can announce mailman-2.1.8a1 very soon. -- We are running Mailman 2.1.5 and have just found extraordinary IO wait issues requiring shutdown|restart of Mailman. This may or may not related to the DoS issue. I suggest checking lock files, shunt directory, and pending requests and search mailman FAQ. The notice suggests all versions are vulnerable, is this the case? If so, suggested workaround? Patch/upgrade coming? Mailman-2.1.7 is not vulnerable to this issue. Cheers, -- Tokio Kikuchi -- 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] How to avoid dup copies to *multiple* email lists?
Matt England wrote: How can someone subscribed to 2 (or more) emails lists from the same GNUMailman email server avoid duplicate copies of emails that are sent to both (or more) of these email lists? Do you want this feature? http://sourceforge.net/tracker/index.php?func=detailaid=1347962group_id=103atid=300103 I plan to integrate it in mailman-2.2. My 2.1.6-rc2 server simply sends me multiple emails in such a case, even though I have the avoid duplicates set on my user-specific setting (which I believe is meant to avoid Cc:'s directly to me, and not necessarily the above scenario?). No, this is not for multiple lists. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] pgp key E099F769?
[EMAIL PROTECTED] wrote: Hi, 2.1.7 is signed by key-id E099F769, but i can't find that key anywhere! can someone put it on the public keyservers pls? Sorry for the inconvenience. Now it can be found at: http://keyserver.veridis.com:11371/search?q=0xE099F769 -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] [Mailman-Developers] Problems with uuencoded attachments
Barry Warsaw wrote:
On Jan 14, 2006, at 9:59 PM, Tokio Kikuchi wrote:
Mark Sapiro wrote:
File /usr/lib/python2.3/uu.py, line 139, in decode
sys.stderr.write(Warning: %s\n % str(v))
File /usr/lib/mailman/Mailman/Logging/MultiLogger.py, line 45,
in write
_logexc(logger, msg)
File /usr/lib/mailman/Mailman/Logging/Utils.py, line 22, in
_logexc
sys.__stderr__.write('Logging error: %s\n' % logger)
IOError: [Errno 32] Broken pipe
I think this could be fixed by changing
/usr/lib/mailman/pythonlib/email/Message.py, line 223 from
uu.decode(StringIO(payload+'\n'), sfp)
to
uu.decode(StringIO(payload+'\n'), sfp,
quiet=True)
There should be other chances that Python builtin modules spew
warnings to sys.stderr. How about this patch for Logging/Utils.py
to write these messages into syslog facility.
The only problem is that currently Mailman does not use the syslog
module, and I'm uncomfortable with adding it for this one situation
(are there others?). We should definitely be passing the quiet flag
to uu.decode(), but OTOH maybe we should also be testing whether
sys.__stderr__ is detached and then redirecting that to logs/errors?
In usual mailman qrunner execs, stderr is logged into logs/errors. It
is the additional tee_to_real_stderr in LogStdErr() setting which wants
to print the error into real stderr.
Isn't it safe to put the tee_to_real_stderr value 0 in bin/qrunner script ?
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
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] SpamDetect loop?
David Gibbs wrote: Tokio Kikuchi wrote: Can you test this patch? Seems to be working fine. david Thank you David. I changed the patch slightly and checked into the CVS. See also this patch tracker entry: http://sourceforge.net/tracker/index.php?func=detailaid=1405790group_id=103atid=300103 Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] [Mailman-Developers] Problems with uuencoded attachments
Barry Warsaw wrote:
On Mon, 2006-01-16 at 09:25 +0900, Tokio Kikuchi wrote:
In usual mailman qrunner execs, stderr is logged into logs/errors. It
is the additional tee_to_real_stderr in LogStdErr() setting which wants
to print the error into real stderr.
Isn't it safe to put the tee_to_real_stderr value 0 in bin/qrunner script ?
Ideally, tee_to_real_stderr would be !AS_SUBPROC (i.e. tee when not
running qrunner under mailmanctl). That would have to be done in main()
after processing the command line arguments.
Yeah, I noticed that too and played around. How about this patch.
I assumed running qrunner independently is for debugging purpose and
quit redirecting stderr into logs/error.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
Index: qrunner
===
RCS file: /cvsroot/mailman/mailman/bin/qrunner,v
retrieving revision 2.9.2.1
diff -u -r2.9.2.1 qrunner
--- qrunner 27 Aug 2005 01:40:16 - 2.9.2.1
+++ qrunner 16 Jan 2006 01:58:49 -
@@ -66,6 +66,9 @@
runner is required unless -l or -h is given, and it must be one of the names
displayed by the -l switch.
+
+Note also that this script should be started up from mailmanctl as a normal
+operation. It is only useful for debugging if it is run separately.
import sys
@@ -84,8 +87,6 @@
# Flag which says whether we're running under mailmanctl or not.
AS_SUBPROC = 0
-LogStdErr('error', 'qrunner', manual_reprime=0)
-
def usage(code, msg=''):
@@ -212,6 +213,10 @@
if len(runners) == 0:
usage(1, _('No runner name given.'))
+# Before we startup qrunners, we redirect the stderr to mailman syslog.
+if AS_SUBPROC:
+LogStdErr('error', 'qrunner', manual_reprime=0, tee_to_real_stderr=0)
+
# Fast track for one infinite runner
if len(runners) == 1 and not once:
qrunner = make_qrunner(*runners[0])
--
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] Messages shunted and kept out of archives
John Swartzentruber wrote:
I recently upgraded to Mailman 2.1.7. A user (and co-moderator) on one
of the lists that I run reported that some of his messages were missing
from the archives and that one of them had been delivered to him without
the normal Mailman footers and subject modification.
File /usr/local/mailman/Mailman/Archiver/HyperArch.py, line 579, in
as_text
'\g1' + _(' at ') + '\g2', body)
File /usr/lib/python2.3/sre.py, line 143, in sub
return _compile(pattern, 0).sub(repl, string, count)
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position
5749: ordinal not in range(128)
Jan 15 19:39:13 2006 (7863) SHUNTING:
1137283434.787801+8fcbe00f31f4008afd66221d0d9397ade1228077
Please fetch this patch from SF tracker and apply it in mailman-2.1.7
source.
http://sourceforge.net/tracker/index.php?func=detailaid=1405790group_id=103atid=300103
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
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] Problems with uuencoded attachments
Mark Sapiro wrote:
File /usr/lib/python2.3/uu.py, line 139, in decode
sys.stderr.write(Warning: %s\n % str(v))
File /usr/lib/mailman/Mailman/Logging/MultiLogger.py, line 45, in write
_logexc(logger, msg)
File /usr/lib/mailman/Mailman/Logging/Utils.py, line 22, in _logexc
sys.__stderr__.write('Logging error: %s\n' % logger)
IOError: [Errno 32] Broken pipe
I think this could be fixed by changing
/usr/lib/mailman/pythonlib/email/Message.py, line 223 from
uu.decode(StringIO(payload+'\n'), sfp)
to
uu.decode(StringIO(payload+'\n'), sfp, quiet=True)
There should be other chances that Python builtin modules spew warnings
to sys.stderr. How about this patch for Logging/Utils.py to write these
messages into syslog facility.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
Index: Utils.py
===
RCS file: /cvsroot/mailman/mailman/Mailman/Logging/Utils.py,v
retrieving revision 2.2.2.1
diff -u -r2.2.2.1 Utils.py
--- Utils.py27 Aug 2005 01:40:16 - 2.2.2.1
+++ Utils.py15 Jan 2006 02:50:11 -
@@ -16,12 +16,25 @@
import sys
import traceback
+import syslog
+import StringIO
+
+syslog.openlog('mailman', syslog.LOG_PID, syslog.LOG_MAIL)
def _logexc(logger=None, msg=''):
-sys.__stderr__.write('Logging error: %s\n' % logger)
-traceback.print_exc(file=sys.__stderr__)
-sys.__stderr__.write('Original log message:\n%s\n' % msg)
+try:
+sys.__stderr__.write('Logging error: %s\n' % logger)
+traceback.print_exc(file=sys.__stderr__)
+sys.__stderr__.write('Original log message:\n%s\n' % msg)
+except IOError:
+syslog.syslog(syslog.LOG_INFO, 'Logging error: %s\n' % logger)
+tbio = StringIO.StringIO()
+traceback.print_exc(file=tbio)
+syslog.syslog(syslog.LOG_INFO, tbio.getvalue())
+tbio.close()
+syslog.syslog(syslog.LOG_INFO, 'Original log message:\n%s\n' % msg)
+
def LogStdErr(category, label, manual_reprime=1, tee_to_real_stderr=1):
--
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] SpamDetect loop?
Hi, I've coded that bug in the last minute of releasing. :-( I think I can generate a patch, but in the meantime, please copy the SpamDetect.py file from 2.1.6 distribution and restart. David Gibbs wrote: Mark Sapiro wrote: There are a few things going on. Did you upgrade from 2.1.6 or from pre-2.1.6? 2.1.5 with some custom patches (nothing major, just text changes the like). Starting in 2.1.6, header_filter_rules are applied to the headers of sub-parts which might cause a problem if the admin notification contains something that matches, BUT there is a safety valve in that the SpamDetect process is never supposed to be applied to internally generated messages such as admin notifications. Ok, that does appear to be what is happening ... but the safety valve doesn't seem to be kicking in. So something is going wrong here, but I don't know what. I will investigate, but if you could send me off list what your header_filter_rules are and a copy of the original problem message, it may help me. I'll send that under separate cover :) david -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] SpamDetect loop?
David Gibbs wrote:
I think I can generate a patch, but in the meantime, please copy the
SpamDetect.py file from 2.1.6 distribution and restart.
I've temporarily removed the SpamDetect module from the owner pipeline
and it seems to be working ok for now.
David,
Can you test this patch?
Removing SpamDetect from the owner pipeline means spams pass through to
the list owner. This should be inconvenient.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
Index: SpamDetect.py
===
RCS file: /cvsroot/mailman/mailman/Mailman/Handlers/SpamDetect.py,v
retrieving revision 2.3.2.10
diff -u -r2.3.2.10 SpamDetect.py
--- SpamDetect.py 31 Dec 2005 06:15:33 - 2.3.2.10
+++ SpamDetect.py 12 Jan 2006 00:05:56 -
@@ -92,8 +92,12 @@
def process(mlist, msg, msgdata):
-if msgdata.get('approved') or msgdata.get('reduced_list_headers'):
-# TK: 'reduced_list_headers' is intenally crafted message (virgin).
+# Do not spam check if the messages is approved or if the message
+# was internally crafted and sent to the -owner address like
+# message hold notification. This avoids loop of hold notifications
+# since this module checks deep into the attachment headers.
+if msgdata.get('approved') or\
+ msgdata.get('toowner') and msg.get('x-list-administrivia') == 'yes':
return
# First do site hard coded header spam checks
for header, regex in mm_cfg.KNOWN_SPAMMERS:
--
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] unexpected code byte in Header.py
imacat wrote: Dear all, I have problem upgrading my Mailman 2.1.5 to Mailman 2.1.7. I got the following error in /var/lib/mailman/logs/error when I tried to send the who request: Jan 11 02:33:06 2006 (12256) Uncaught runner exception: 'utf8' codec can't decode byte 0xb4 in position 8: unexpected code byte Jan 11 02:33:06 2006 (12256) Traceback (most recent call last): File /opt/mailman/Mailman/Handlers/CookHeaders.py, line 188, in process i18ndesc = uheader(mlist, mlist.description, 'List-Id', maxlinelen=998) File /opt/mailman/Mailman/Handlers/CookHeaders.py, line 65, in uheader return Header(s, charset, maxlinelen, header_name, continuation_ws) File /opt/mailman/pythonlib/email/Header.py, line 188, in __init__ self.append(s, charset, errors) File /opt/mailman/pythonlib/email/Header.py, line 272, in append ustr = unicode(s, incodec, errors) UnicodeDecodeError: 'utf8' codec can't decode byte 0xb4 in position 8: unexpected code byte As Mark has responded, it is a error in CookHeaders.py 'List-Id' processing. The language code and charset for 'Traditional Chinese' have changes from big5/big5 to zh_TW/utf-8 because of compliance and code handling difficulty in python gettext. If you have set description in chinese previously by mailman-2.1.5, then you may have to reset it via the admin interface or by bin/withlist script. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] Bug in 2.1.7, can't edit Public HTML pages text files
Christopher X. Candreva wrote: Mailman is telling me there is a bug whenever I try to submit a page from the Edit the public HTML pages and text files menu. The page returned says: Bug in Mailman version 2.1.7 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. The most usefull thing I've found in the logs is: Jan 10 15:52:55 2006 admin(6592): admin(6592): [- Mailman Version: 2.1.7 -] admin(6592): [- Traceback --] admin(6592): Traceback (most recent call last): admin(6592): File /home/mailman/scripts/driver, line 101, in run_main admin(6592): main() admin(6592): File /home/mailman/Mailman/Cgi/edithtml.py, line 125, in main admin(6592): ChangeHTML(mlist, cgidata, template_name, doc) admin(6592): File /home/mailman/Mailman/Cgi/edithtml.py, line 160, in ChangeHTML admin(6592): code = re.sub(r'([/]?script.*?)', r'lt;\1gt;', code) admin(6592): NameError: global name 're' is not defined admin(6592): [- Python Information -] admin(6592): sys.version = 2.4.2 (#1, Nov 11 2005, 14:28:34) [GCC 3.4.4] I would be surprised if I was the only person to try to submit a changed HTML/text page in 2.1.7, but I suppose it's possible. However I haven't found anything in a search, and check_perms tells me everything is OK. Have I done something stupid, or is it a real bug and I should open a bug report ? Sorry for the inconvenience but I've put a new bug in the code while tighten up the security of the script. Work around is to put a line import re in the top part of the Mailman/Cgi/edithtml.py. The bug was reported in http://sourceforge.net/tracker/index.php?func=detailaid=1400128group_id=103atid=100103 -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] Shunting msgs.
Hi, Thomas von Hassel wrote: Hi i have a mailman 2.1.6 installation on freebsd 4.9 Many of the msgs. to my lists are beging shunted with this error: Uncaught runner exception: 'ascii' codec can't decode byte 0xe6 in position 18: ordinal not in range(128) Most of these msgs. are normal, plaintext msgs. Is there a way to force these msgs to the list, or is there something i could look at so these msgs. don't get shunted. Now mailman 2.1.7 is out and more robust with such error, I believe. Can you send me more details of error log, if you don't mind ? /thomas -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] manual upgrade
Jim Popovitch wrote: Hi, I normally build mailman (./configure; make install) on a dev system then tar/rsync it to a production machine. I checked the UPGRADING notes in the 2.1.7 release and there is no mention of anything (i.e. withlist, fix_url, etc) that needs to be done when upgrading from 2.1.5 to 2.1.7.Are lists (and specifically everything in --with-var-prefix) from a 2.1.5 install compatible with 2.1.7? If not, what post-install actions need to be taken to upgrade an existing system from 2.1.5 to 2.1.7? Upgrading from 2.1.5 to 2.1.7 should have no problems. Everything needed is done during the bin/update run in 'make install'. Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] RELEASED Mailman 2.1.7
I'm pleased to announce the release of GNU Mailman 2.1.7. This is a significant release, which includes security enhancement fixes, a new language (ia: Interlingua) support, a couple of new features, and many bug fixes. Mailman is free software for managing email mailing lists and e-newsletters. This release enhances the fixes for CAN-2005-0202 and CVE-2005-3573 which were fixed in mailman release 2.1.6, and reduces the chance of list admin privilege abuse. Because of these and other fixes, it is highly recommended that all sites update to 2.1.7. For more information, see: http://mailman.sourceforge.net/ For links to download the Mailman 2.1.7 source tarball, see: http://sourceforge.net/project/showfiles.php?group_id=103 Best regards and a happy new year! -- Tokio Kikuchi -- 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] Released: Mailman 2.1.7b1
Hi all, I've just released Mailman 2.1.7rc1 Release Candidate. I'm sorry for the violation of file name extension convention because I made a small mistake when tagging the release number. I will be releasing 2.1.7 final by December 31 if there is no problem. Please download it from SF or: http://mm.tkikuchi.net/mailman-2.1.7rc1.tar.gz Cheers, Tokio --- 2.1.7rc1 (24-Dec-2005) Security - The fix for CAN-2005-0202 has been enhanced to issue an appropriate message instead of just quietly dropping ./ and ../ from URLs. - A note on CVE-2005-3573: Although the RFC2231 bug example in the CVE has been solved in mailman-2.1.6, there may be more cases where ToDigest.send_digests() can block regular delivery. We put the send_digests() calling part in try - except clause and leave a message in the error log if something happened in send_digests(). Daily call of cron/senddigests will notify more detail to the site administrator. - List administrators can no longer change the user's option/subscription globally. Site admin can change these only if mm_cfg.ALLOW_SITE_ADMIN_COOKIES is set to Yes. - Script tag is disallowd in edithtml script. - Since probe message for the disabled users may reach unexpected persons, the password was excluded from sendProbe() and probe.txt. Note that the default value of VERP_PROBE has been set to `No' from 2.1.6., thus this change doesn't change the default behavior. New Features - Always remove DomainKey (and similar) headers (1287546) from messages sent to the list. - List owners can customize content filter behavior as not to collapse multipart/alternative to its first content. This allows HTML part to pass through after other content filtering is done. Internationalization - New language: Interlingua. Bug fixes and other patches - Defaults.py.in: SCRUBBER_DONT_USE_ATTACHMENT_FILENAME is set to True for safer operation. - Fix Scrubber.py mungs quoted-printable bug with introducing 'X-Mailman-Scrubbed' header for marking that the payload is scrubber-munged. The flag is referenced in ToDigest.py, ToArchive.py, Decorate.py and Archiver. Similar problem in ToDigest.py where the plain digest is generated is also fixed. - Fix Syslog.py to write quopri encoded message when it fail to write 8-bit characters. - Fix MTA/Postfix.py to check aliases group permission in check_perms and fix mailman-install document on this matter (1378270). - Fix private.py to go to the original URL after authorization (1080943). - Fix bounce log score messages to be more consistent. - Fix bin/remove_members to accept no arguments when both --fromall and --file= options are specified. - Change cgi-bin and mail wrapper group not found error message to be more descriptive of the actual problem. - Apply the list's ban_list to address changes and admin mass subscribe and invite and to confirmations/approvals of address changes, subscriptions and invitations. - Decode quoted-printable and base64 encoded parts before passing to HTML_TO_PLAIN_TEXT_COMMAND (1367783). - Remove Approve: header from post - treat as Approved: (1355707). - Stop removing line following Approve(d): line in body of post (1318883). - Remove Approve(d): password from all text/* parts in addition the initial text/plain part. It still must be the first non-blank line in the first text/plain part or it won't be found or removed at all (1181161). - Log post in post log with true sender, not listname-bounces (1287921). - Correctly initialize and remember the list's default_member_moderation attribute in the web list creation page (1263213). - Add PEP263 charset in config_list output (1343100). - header_filter_rules get lost if accessed directly and needed authenti- cation by login page (1230865). - Obscure email when the poster doesn't set full name in 'From:' header. - Take preambles and epilogues into account when calculating message sizes for holding purposes (Mark Sapiro). - Logging/Logger.py unicode transform option (1235567). - bin/update crashes with bogus files (949117). - Bugs and patches: 1212066/1301983 (Date header in create/remove notice) -- 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:
[Mailman-Users] Mailman 2.1.7rc1 (was Re: Released: Mailman 2.1.7b1)
Oops, Sorry for the typo in the message title. I mean Released: Mailman 2.1.7rc1 Release Candidate Tokio Kikuchi wrote: Hi all, I've just released Mailman 2.1.7rc1 Release Candidate. I'm sorry for the violation of file name extension convention because I made a small mistake when tagging the release number. I will be releasing 2.1.7 final by December 31 if there is no problem. Please download it from SF or: http://mm.tkikuchi.net/mailman-2.1.7rc1.tar.gz Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] filename too long error - stopping list
Hi Michael,
You can set Scrubber.py not to use the orginal filename in the message
by adding followin line in mm_cfg.py (mailman-2.1.6 and above).
SCRUBBER_DONT_USE_ATTACHMENT_FILENAME = True
Developers,
May be we should set this default in Defaults.py.in in the next release
of 2.1.7. Thoughts?
Michael Rasmussen wrote:
Resolved. The digest keeps a seperate mbox file at
{MMDIR}lists/LISTNAME/digest.mbox removing the email from that location
was the solution to my immediate problem.
This does expose a DOS attack potential for MM lists. The too long
attachment name needs to be handled in a more graceful manner.
Michael Rasmussen wrote:
Update:
I've found the offending message and purged it from the list archives,
purged it from the shunt files, and purged it from everywhere I could
find it.
Yet the problem persists. So I'm looking for the temp file/mail area
where the file that contains this attachment may be found.
Michael Rasmussen wrote:
I have a list that was sent a file with an attachement with too long a
name. (See error below) now all mail to the list is being shunted.
the filename listed does not exist on my system. There is no file on my
system with that name.
The directory
/var/lib/mailman/archives/private/rca-l/attachments/20051207/3d04c3a4 is
empty.
What do I need to do to resolve this problem?
== Error message =
Dec 22 06:08:46 2005 (2233) Uncaught runner exception: [Errno 36] File name
too long:
'/var/lib/mailman/archives/private/rca-l/attachments/20051207/3d04c3a4/iso-8859-1QThe_surface_of_the_SunA0_The_sun_has_a_rigid_iron_surfaceiso-8859-1Q_located_under_the_photosphere_that_is_revealed_by_satelliiso-8859-1Qte_imagery.A0_The_solar_surface_sits_beneath_the_suns_viiso-8859-1Qsible_photosphere_and_is_electrically_active..obj'
Dec 22 06:08:46 2005 (2233) Traceback (most recent call last):
File /usr/lib/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop
self._onefile(msg, msgdata)
File /usr/lib/mailman/Mailman/Queue/Runner.py, line 167, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /usr/lib/mailman/Mailman/Queue/IncomingRunner.py, line 130, in
_dispose
more = self._dopipeline(mlist, msg, msgdata, pipeline)
File /usr/lib/mailman/Mailman/Queue/IncomingRunner.py, line 153, in
_dopipeline
sys.modules[modname].process(mlist, msg, msgdata)
File /var/lib/mailman/Mailman/Handlers/ToDigest.py, line 91, in process
send_digests(mlist, mboxfp)
File /var/lib/mailman/Mailman/Handlers/ToDigest.py, line 132, in
send_digests
send_i18n_digests(mlist, mboxfp)
File /var/lib/mailman/Mailman/Handlers/ToDigest.py, line 306, in
send_i18n_digests
msg = scrubber(mlist, msg)
File /var/lib/mailman/Mailman/Handlers/Scrubber.py, line 265, in process
url = save_attachment(mlist, part, dir)
File /var/lib/mailman/Mailman/Handlers/Scrubber.py, line 447, in
save_attachment
fp = open(path, 'w')
IOError: [Errno 36] File name too long:
'/var/lib/mailman/archives/private/rca-l/attachments/20051207/3d04c3a4/iso-8859-1QThe_surface_of_the_SunA0_The_sun_has_a_rigid_iron_surfaceiso-8859-1Q_located_under_the_photosphere_that_is_revealed_by_satelliiso-8859-1Qte_imagery.A0_The_solar_surface_sits_beneath_the_suns_viiso-8859-1Qsible_photosphere_and_is_electrically_active..obj'
Dec 22 06:08:46 2005 (2233) SHUNTING:
1135258825.4376719+99568bcc1187c910d48aae8b9ae8f68ed3aa643b
== Error message =
--
Michael Rasmussen, Portland Oregon
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
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] Released: Mailman 2.1.7b1
Hi all, I've just released Mailman 2.1.7b1 for beta test and i18n translations. I'm tempted to jump into RC because the 2.1-maint branch is so stable and 2.1.7 is mainly for bug fixes, but we need more translations before the final release. Please download it from SF or: http://mm.tkikuchi.net/mailman-2.1.7b1.tgz Cheers, Tokio --- Here is a history of user visible changes to Mailman. 2.1.7b1 (20-Dec-2005) Security - The fix for CAN-2005-0202 has been enhanced to issue an appropriate message instead of just quietly dropping ./ and ../ from URLs. - A note on CVE-2005-3573: Although the RFC2231 bug example in the CVE has been solved in mailman-2.1.6, there may be more cases where ToDigest.send_digests() can block regular delivery. We put the send_digests() calling part in try - except clause and leave a message in the error log if something happened in send_digests(). Daily call of cron/senddigests will notify more detail to the site administrator. - List administrators can no longer change the user's option/subscription globally. Site admin can change these only if mm_cfg.ALLOW_SITE_ADMIN_COOKIES is set to Yes. - Script tag is disallowd in edithtml script. - Since probe message for the disabled users may reach unexpected persons, the password was excluded from sendProbe() and probe.txt. Note that the default value of VERP_PROBE has been set to `No' from 2.1.6., thus this change doesn't change the default behavior. New Features - Always remove DomainKey (and similar) headers (1287546) from messages sent to the list. - List owners can customize content filter behavior as not to collapse multipart/alternative to its first content. This allows HTML part to pass through after other content filtering is done. Internationalization - New language: Interlingua. Bug fixes and other patches - Fix Scrubber.py mungs quoted-printable bug with introducing 'X-Mailman-Scrubbed' header for marking that the payload is scrubber-munged. The flag is referenced in ToDigest.py, ToArchive.py, Decorate.py and Archiver. Similar problem in ToDigest.py where the plain digest is generated is also fixed. - Fix Syslog.py to write quopri encoded message when it fail to write 8-bit characters. - Fix MTA/Postfix.py to check aliases group permission in check_perms and fix mailman-install document on this matter (1378270). - Fix private.py to go to the original URL after authorization (1080943). - Fix bounce log score messages to be more consistent. - Fix bin/remove_members to accept no arguments when both --fromall and --file= options are specified. - Change cgi-bin and mail wrapper group not found error message to be more descriptive of the actual problem. - Apply the list's ban_list to address changes and admin mass subscribe and invite and to confirmations/approvals of address changes, subscriptions and invitations. - Decode quoted-printable and base64 encoded parts before passing to HTML_TO_PLAIN_TEXT_COMMAND (1367783). - Remove Approve: header from post - treat as Approved: (1355707). - Stop removing line following Approve(d): line in body of post (1318883). - Log post in post log with true sender, not listname-bounces (1287921). - Correctly initialize and remember the list's default_member_moderation attribute in the web list creation page (1263213). - Add PEP263 charset in config_list output (1343100). - header_filter_rules get lost if accessed directly and needed authenti- cation by login page (1230865). - Obscure email when the poster doesn't set full name in 'From:' header. - Take preambles and epilogues into account when calculating message sizes for holding purposes (Mark Sapiro). - Logging/Logger.py unicode transform option (1235567). - bin/update crashes with bogus files (949117). - Bugs and patches: 1212066/1301983 (Date header in create/remove notice) -- 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] Swedish version - Next message: is not translated
Hugo Hugo wrote: Hi all ! Another problem with the Swedish version. This concerns the Next message text shown when you display each mail in a Pipermail archive. This text is not translated. The text corresponding to Previous message:, however, is correctly translated. Both texts seem correct in the Swedish translation file. The template file is Article.html, and the variable name is next_wsubj. The variable is set in Hyperarch.py and it is not obvious to me that it is set differently from prev_wsubj which is correctly translated. There are many 'fuzzy' marks in the Swedish message catalog. You should edit these marked translations and delete #,fuzzy lines. Then do the make install again in the messages directory. You may also contact the language champions to make these fix merged in the CVS (and next release). See: http://www.list.org/i18n.html -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] Mailman 2.1.[56] installation problem w/ KoreanCodecs
Christophe Kalt wrote: Hi all, make install dies with (cd ./$p ; umask 02 ; PYTHONPATH=/home/mailman/2.1.5/pythonlib /usr/local/bin/python setup.py --quiet install --install-lib /home/mailman/2.1.5/pythonlib --install-purelib /home/mailman/2.1.5/pythonlib --install-data /home/mailman/2.1.5/pythonlib); \ done /usr/local/lib/python2.4/distutils/dist.py:222: UserWarning: 'licence' distribution option is deprecated; use 'license' warnings.warn(msg) src/hangul.c:33: error: syntax error before numeric constant src/hangul.c:34: error: syntax error before numeric constant error: command 'gcc' failed with exit status 1 *** Error code 1 This happens with either 2.1.5 or 2.1.6, various versions of Python as well. It's on Solaris 10 with Sun's bundled gcc (/usr/sfw/bin/gcc). Rather furstrating. Is there an easy way to just skip these codecs i have no use for? You are using python2.4 which should support Chinese/Korean/Japanese codecs by itself. So, you need not, in principle, install Korean/Japanese codecs which are included in mailman distribution. You may want to try my language select patch in the SF tracker: http://sourceforge.net/tracker/index.php?func=detailaid=1298355group_id=103atid=300103 Or, you can go to the mailman_source/misc directory and find [Kk]orean notation in Makefile and paths.py and comment them out, then do the make install again. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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-8-i messages goes to the shunt directory
[EMAIL PROTECTED] wrote:
Hello All,
I have the following of problem:
When message sent to the list in Hebrew Language in iso-8859-8-i encoding, it
doesn't sent and goes directly to /var/lib/mailman/qfiles/shunt,
so I have to run /usr/lib/mailman/bin/unshunt manually to release these
messages.
But then these messages released, the subject line of these messages is empty.
Here are some headers of these kind of messages:
Content-Type: text/html;
charset=iso-8859-8-i
Content-Transfer-Encoding: quoted-printable
Subject:
=?iso-8859-8-i?B?Rnc6IPf46eDkIODn+OXw5CDs8OXx8untIOz08Okg5OTu+ODkIA==?=
What's the problem here and how can I solve it?
It looks like python official codecs don't support RFC-1556
bi-directional handling of Arabic and Hebrew charsets. I really don't
know how we should solve this but how about this following patch?
You may also want to add your language description in mm_cfg.py (see
Defaults.py for the format).
% diff -u paths.py.orig paths.py
--- paths.py.orig Mon Nov 7 20:38:34 2005
+++ paths.pyMon Nov 7 20:51:21 2005
@@ -58,3 +58,12 @@
# changes this.
import korean
import korean.aliases
+# Arabic and Hebrew encoding aliases
+import encodings.aliases
+encodings.aliases.aliases.update({
+'iso_8859_6_e': 'iso8859_6',
+'iso_8859_6_i': 'iso8859_6',
+'iso_8859_8_e': 'iso8859_8',
+'iso_8859_8_i': 'iso8859_8',
+})
+
--
Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
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] Formatting the Subject-field in other languages
Hi, What is your problem? Will you please describe it in more detail or show me some example? And, what is your mailman version? Hannah Schroeter wrote: Hello! On Tue, Nov 01, 2005 at 09:30:25PM +0900, Tokio Kikuchi wrote: [...] Here is your patch. We have already integrated German and Dannish dialects. Does that really make sense? They don't even manage to use *one* localized reply prefix, witness AW: in a German version of one silly mail client (Outlook), and Betreff: in a German version of one other silly mail client (IncrediMail; the incredible nightmare for mailing list admins). Kind regards, Hannah. -- -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] Formatting the Subject-field in other languages
Hi,
[HUV] VS: VS: VS: VS: VS: VS: VS: VS: Järvenpää
So, Here you see that as normal Re: is instead VS:
Such a localized Re: altanative can cause troubles:
http://www.geocities.com/vsre_2000/
(I can't read Finnish. It just hit google search. ;-)
I'm running Mailman 2.1.6 on a Debian-woody server.
Here is your patch. We have already integrated German and Dannish dialects.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
Index: Mailman/Handlers/CookHeaders.py
===
RCS file: /cvsroot/mailman/mailman/Mailman/Handlers/CookHeaders.py,v
retrieving revision 2.40
diff -u -r2.40 CookHeaders.py
--- Mailman/Handlers/CookHeaders.py 28 Aug 2005 05:31:27 - 2.40
+++ Mailman/Handlers/CookHeaders.py 1 Nov 2005 12:22:55 -
@@ -268,7 +268,7 @@
else:
old_style = mm_cfg.OLD_STYLE_PREFIXING
subject = re.sub(prefix_pattern, '', subject)
-rematch = re.match('((RE|AW|SV)(\[\d+\])?:\s*)+', subject, re.I)
+rematch = re.match('((RE|AW|SV|VS)(\[\d+\])?:\s*)+', subject, re.I)
if rematch:
subject = subject[rematch.end():]
recolon = 'Re:'
Index: Mailman/Archiver/HyperArch.py
===
RCS file: /cvsroot/mailman/mailman/Mailman/Archiver/HyperArch.py,v
retrieving revision 2.45
diff -u -r2.45 HyperArch.py
--- Mailman/Archiver/HyperArch.py 31 Oct 2005 04:33:38 - 2.45
+++ Mailman/Archiver/HyperArch.py 1 Nov 2005 12:22:56 -
@@ -428,7 +428,7 @@
prefix_pat = re.sub(r'%\d*d', r'\s*\d+\s*', prefix_pat)
subject = re.sub(prefix_pat, '', subject)
subject = subject.lstrip()
-strip_pat = re.compile('^((RE|AW|SV)(\[\d+\])?:\s*)+', re.I)
+strip_pat = re.compile('^((RE|AW|SV|VS)(\[\d+\])?:\s*)+', re.I)
stripped = strip_pat.sub('', subject)
return stripped
--
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] Setting-up cascading, filtering list designs
Hi, [postnuke-cvsnotices] PostNuke/system/Modules/pnlang/eng admin.php pnlanguages-cvsenglish is subscribed to postnuke-cvsnotices. pnlanguages-cvsenglish has to examine the subject line of each message received and find all subject lines that contain: - pnlang/eng or lang/eng (indicating an English language directory was affected), - manual.html (indicating an on-line help file was affected), - readme.txt (a read-me file was affected), - version.php or pnversion.php (a module version information file was affected, - credits.txt or CREDITS.txt (indicating a credits file was affected). It should then forward to the list subscribers only those messages thus identified. http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.051.htp might be helpful. You can use two entries for header_filter_rules like: first rule = subject:.*(lang/eng|manual\.html|readme\.txt|version\.php|credits\.txt) set this Accept, second rule = . (single dot), and set this Discard. Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] apache errors
Hi, You have to accesss http://10.0.253.82/mailman/listinfo. Without the script name in the end of URI, Apache returns error because you set Options None. Options ExecCGI should not be used here for ScriptAliases is already specified. Options Indexes is the configuration for directory view but it is not recommended for security reason. http://httpd.apache.org/docs/2.0/mod/core.html#options Bryan Irvine wrote: I've jsut installed mailman, and think I've done everything right so far. When I try to browse to the mailman site though it doesn't seem to work properly. I've found other similar questions in the archive, but none of those had any resolution. When I browse to http://10.0.253.82/mailman/ I just get Forbidden You don't have permission to access /mailman/ on this server. Here's my httpd.conf ScriptAlias /mailman/ /usr/local/lib/mailman/cgi-bin/ Directory /usr/local/lib/mailman/cgi-bin AllowOverride None Options None Order allow,deny Allow from all /Directory Ideas? --Bryan -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] Running 2.2a0 want to downgrade to 2.1.6 stable
Hi, Joshua D. Drake wrote: Hello, We have a machine running 2.2a0. We would like to downgrade to the stable release of 2.1.6. Are there any known gotchas that we need to prepare for? When did you install 2.2a0? I believe you installed ot from CVS. The CVS HEAD is now versioned 2.2.0a0 and a backport of 2.1.6 plus a few bug fixes and is as stable as 2.1.6. Upgrading to the CVS HEAD should be as smooth as upgrading from 2.1.x to 2.1.6. Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] OverflowError: long int too large to convert to int
Marcel Meyer wrote: Some lists are no longer (worked before - no configuration or software update occured) delivered. All messages are shunted. The errorlog says the following: [...] OverflowError: long int too large to convert to int File /usr/local/mailman/Mailman/Handlers/Scrubber.py, line 131, in calculate_attachments_dir datedir = safe_strftime(fmt, now) File /usr/local/mailman/Mailman/Handlers/Scrubber.py, line 115, in safe_strftime return time.strftime(fmt, floatsecs) OverflowError: long int too large to convert to int Looks like we need this patch: Index: Scrubber.py === RCS file: /cvsroot/mailman/mailman/Mailman/Handlers/Scrubber.py,v retrieving revision 2.27 diff -u -r2.27 Scrubber.py --- Scrubber.py 28 Aug 2005 05:31:27 - 2.27 +++ Scrubber.py 7 Sep 2005 23:40:33 - @@ -113,7 +113,7 @@ def safe_strftime(fmt, floatsecs): try: return time.strftime(fmt, floatsecs) -except (TypeError, ValueError): +except (TypeError, ValueError, OverflowError): return None - -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] header_filter_rules possible bug
Hi,
I think you are right! I have to make warning when checking in because
this may cause incompatible behavior for already installed other
patterns. :-(
Iain Pople wrote:
Hi,
I have noticed some unexpected behaviour with header_filter_rules.
I wanted to reject messages with an empty subject line so i came up
with the following regex:
^subject:\s*$
However it wasn't working as desired. After delving around in the
SpamDetect.py code i noticed that the re.search call is not using
MULTILINE mode. So the headers are treated as one long string and ^
would only match the beginning of the string.
Is this the desired behaviour? To me it makes more sense that it
should use multiline mode.
i.e.:
--- SpamDetect.py.bak 2005-08-02 15:56:42.08327 +1000
+++ SpamDetect.py 2005-08-02 17:33:59.698226000 +1000
@@ -127,7 +127,7 @@
for pattern in patterns.splitlines():
if pattern.startswith('#'):
continue
-if re.search(pattern, headers, re.IGNORECASE):
+if re.search(pattern, headers, re.IGNORECASE|re.MULTILINE):
if action == mm_cfg.DISCARD:
raise Errors.DiscardMessage
if action == mm_cfg.REJECT:
@@ -137,3 +137,4 @@
hold_for_approval(mlist, msg, msgdata,
HeaderMatchHold)
if action == mm_cfg.ACCEPT:
return
--
Iain Pople
Systems Programmer
University of Melbourne
--
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/tkikuchi%40is.kochi-u.ac.jp
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
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] attachments being stored for plain-text digests
Hi Mark, Mark Sapiro wrote: Elizabeth Lear wrote: Is there any way to configure it to just pass the attachments through rather than trying to save them on the server? You could remove Scrubber from the pipeline, Sorry, but use of Mailman.Handlers.Scrubber is hard coded in ToDigest.py. I should have make it configurable like it was for the archiver. :-( but I don't think you want to do that because I think the MIME structure of the message with attachments will not be properly integrated into the overall digest, at least for 'plain' digests. This will result in digest recipients seeing MIME part headers, raw HTML, raw base64 encoded data and so forth instead of attachments. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] attachments being stored for plain-text digests
Hi, Elizabeth Lear wrote: Sorry, but use of Mailman.Handlers.Scrubber is hard coded in ToDigest.py. I should have make it configurable like it was for the archiver. :-( Ah, thanks. Before I give up completely, can you say whether scrubber can be hacked out without breaking things, or is it too integral to the code? I think the plain text digester expects all the messages should be either in plain text or can be scrubbed internally, IIRC. You should choose to use MIME digest if you want to deliver those attachments. Note also that Scrubber.py is used in the regular delivery (if list admin set so), the digester, and the archiver. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] Scheduled Administrative Option
Hi, Brad Knowles wrote: At 10:46 PM -0400 2005-07-12, LifeTrek Coaching wrote: When will you add a Schedule feature to the Tend to Pending Moderator Requests sections? Right now there are only 4 options (Defer, Accept, Reject, Discard). There should be 5 (Defer, Accept, Reject, Discard, Schedule). The Schedule feature would enable you to Schedule the distribution of a post for a specific date and time. This would be an enormous improvement to the list functionality. Let me know. Thanks. That sounds like a good idea. Please feel free to file a Request For Enhancement at http://sourceforge.net/tracker/?group_id=103atid=350103. Remember that current structure of mailman is not good at arbitrary scheduling. You may have to run a scheduling script every hour or so. It would be easier to use your PC (Windows or Linux) to send a message in a scheduled time. May be you can send a message with an Approved header and a confirm command with the confirmation string in the hold notice. Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] Scheduled Administrative Option
Carl Zwanzig wrote: In a flurry of recycled electrons, Tokio Kikuchi wrote: Remember that current structure of mailman is not good at arbitrary scheduling. You may have to run a scheduling script every hour or so. Seems like this already exists with qrunner. [knowing nothing about the internals..] If a message is 'scehduled' toss it into a different dierctory. At the same time, drop in a small file containing the time to send (a separate file should be lower overhead to open, and should have very little data.) Periodically check all these time-to-send files. Ought to be fairly trivial to impliment the sending portion. Don't know about the web pages, though. z! Hi, Then you should do it for Mr. LifeTrek Coaching. ;-) I only wanted to say that my (or developers') priority would be lowest if an RFE is submitted in SF and it might be better to seek alternative solutions. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] no subject prefix
Julien Francoz CoCoZ wrote: Julian Ohm wrote: Hi I'm using Mailman 2.1.6 and have a problem with the subject prefix. mailman doesent change the subject and i'm not able to fix that problem I hope someone can help me. system suse linux 9.0 postfix 2.0.14 apache 2 I had the same problem a few months ago, it still doesn't work. The prefix is not put in the subject, but it is put in the subject in archives. http://www.mail-archive.com/mailman-users@python.org/msg32852.html Strange. At least the prefix '[dept-linux/pedago]' works at my test site. What is your version of Python and what is your list language settings? I may be able to look into the problem if you can send me the copy of original post message. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] no subject prefix
Hi, Strange. At least the prefix '[dept-linux/pedago]' works at my test site. What is your version of Python and what is your list language settings? I may be able to look into the problem if you can send me the copy of original post message. I don't have access to the server for now on order to know the exact version. It is on a MacOsX server 10.0.4 (postfix) (default mailman installation), all lists are in French, they are all working well, except one list for which the subject prefix is not used. All mails to this list are deliver without prefix, but are in pipermail with the prefix. There is one point in the CookHeader.py where we abort prefixing: try: prefix_subject(mlist, msg, msgdata) except (UnicodeError, ValueError): # TK: Sometimes subject header is not MIME encoded for 8bit # simply abort prefixing. pass This means your clients should be MIME compliant if they want to get full service from Mailman. :-( But, in this case, no prefix should appear in the pipermail archive. I may be able to subscribe to your list and get some mail and browse the archive if your list policy accepts. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] Can't get personalization to work
Hi, David Ocaña wrote: Hi people, After reading the mailman FAQ, manuals, the list archive, and thousands of webs I've not been able to get personalization working. Here's my mm_cfg.py -- #QMAIL Options for bounces MTA_ALIASES_STYLE = 'qmail' DELIVERY_MODULE = 'Qmail' Non digest delivery personalization is only supported by SMTPDirect delivery module. Sorry about that but you need considerable hack to implement it in other modules. :-( -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] Stripping attachments but have them available for download?
Hi, What is your version of mailman? In mailman-2.1.6, there is a parameter to achieve this in the nondigest section of admin interface as `scrub_nondigest'. Set this `Yes'. Cheers, Michael Masse wrote: Is there any sort of filter that can have mailman strip attachments, make them available for http download, and put a little blurb in the email stating the URL? I'm trying to prevent the same document from being stored in 5000 mailboxes as well as being virus and spam checked 5000 times everytime an announcement is made. The senders refuse to learn how to do this manually. Mike -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] Message Unparsable
Hi, Dennis Putnam wrote: After some research I have concluded that the errors I am getting from Mailman are because of a malformed MIME content. Since I am creating the message myself with a php page I am not surprised (my first time). Since this probably is a MIME issue I know this is not the correct forum. However, I am posting the suspect raw data here in the hopes someone is familiar enough with MIME to spot the problem. At the very least perhaps someone can point me to a good MIME forum. TIA. Here is the MIME format message body for the problem message (I omitted the routing headers): MIME-version: 1.0 Content-type: multipart/mixed; boundry=!!!---===123_4567_890===---!!! ^^^ This should be 'boundary' not -dry. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] [Mailman-Developers] subject_prefix multiplication
Barry Warsaw wrote: On Fri, 2005-05-13 at 05:05, Brad Knowles wrote: At 12:41 AM -0400 2005-05-13, Barry Warsaw wrote: Thanks for the quick heads up. I think I just fixed it. At least I /hope/ so, 'cause I'm going to bed. ;) So far as I know, we had been running a plain-jane 2.1.6rc3 installation on this machine. Is the fix for the subject line duplication going to be included in 2.1.6rc4, or at least the final 2.1.6-REL? Yes. And I emailed Tokio last night (well, a few hours ago which for me included the briefest of naps :) that I think we'll need one more release candidate. I'll probably spin that today, er, in a few hours. -Barry I believe I could finally fix the bug and commited in CVS. IMHO, python re.escape() should escape special characters only -- I can't find '%' in special character list in the manual. -- Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] Mail going to qfiles/shunt
Oh, Yes! The fix should appear soon in anonymous CVS and viewcvs.
http://cvs.sourceforge.net/viewcvs.py/mailman/mailman/
Brad Knowles wrote:
At 9:42 PM +0900 2005-05-08, Tokio Kikuchi wrote:
I think I could track this down. I used Unicode{En|De}codeError but
they are introduced in Python2.3. It should be UnicodeError and this
catches both encode ande decode errots. I've updated CVS with this fix
for Decorate.py and cmd_subscribe.py. It was my fault not Barry's.
Ahh. Is this change going to be included in the final release
version of 2.1.6?
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
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] Mail going to qfiles/shunt
Larry Hansford wrote: I installed the Mailman 2.1.6rc3, and it tested okay. But, messages sent to previously existing lists all go to /home/mailman/files/shunt, and are not delivered. Is this a rights problem? I ran check_perms, and it did not find any errors. Hi, Since 2.1.6rc3 is a really latest version, the answer in FAQ won't be applicable. http://www.python.org/cgi-bin/faqw-mm.py?query=shuntquerytype=simplecasefold=yesreq=search Please find the cause of error in the logs/error log and report us. Or, you might be able to find fix to this and report us also. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] appended email addresses on probe?
Hi,
At 12:54 PM +0200 2005-04-24, Thomas Hochstein wrote:
I'm not sure where you're getting this so-called example from,
but the message body doesn't look like anything that Mailman would be
generating.
Obviously Mailman is forwarding a sample bounce in the probe message.
Yes. This is the last bounce notice which mailman (list-bounces
address) received. In general, it contains only the bounced addresses
and is no use for spammers (or useful to exclude them from their spam
list if they are clever enough).
You have to hack mailman code in order not to attach the bounce notice.
Here is the hack:
--- Deliverer.pyTue Jan 18 08:57:07 2005
+++ Deliverer.py.x Mon Apr 25 08:46:49 2005
@@ -224,7 +224,6 @@
outer.set_type('multipart/mixed')
text = MIMEText(text, _charset=Utils.GetCharSet(ulang))
outer.attach(text)
-outer.attach(MIMEMessage(msg))
# Turn off further VERP'ing in the final delivery step. We set
# probe_token for the OutgoingRunner to more easily handling local
# rejects of probe messages.
You may also want to customize your probe.txt in the template directory.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
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] Mailman 2.1.6 2nd release candidate
Hi all, Afrer the release of RC1, we had a couple of reasons to delay the final, including a move of FSF office in the end of this month which are to be included in all the copyleft notices in the files. I will also become busy on my paid duties and the final release of 2.1.6 may not occur by the middle of May. :- So, we have much time to test or translate this 2nd release candidate for the final 2.1.6. http://sourceforge.net/project/showfiles.php?group_id=103 or http://mm.tkikuchi.net/mailman-2.1.6rc2.tgz Cheers, -- Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] Mailman and spam
Andreas Rittershofer wrote:
Mails I receive are already processed by SpamAssassin, so spam is marked
with a X-Spam-Level.
Now I want that these mails addressed to mailing lists are deleted by
mailman and not held for approval.
How to do this?
I put this in mm_cfg.py:
KNOWN_SPAMMERS = [
('x-spam-flag', 'yes'),
... other stuffs
]
It is better not to use X-Spam-Level because the *'s are special
characters in python regular expression. Better to tweak in the
spamassassin configuration.
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
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] hostname instead of mx name - mailman.db warning
mm_cfg.py:add_virtualhost( 'lists.antipolis.fr' ) where is my mistake ? mm_cfg.py:add_virtualhost( 'lists.antipolis.fr', 'lists.antipolis.fr' ) -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] encoding errors
Hi, Mark Sapiro wrote: Heather Madrone wrote: Does anyone know why there are so many encoding errors with posts to this list? I thought that was also the case when the body was encoded quoted-printable or base64. I'm still pretty sure it is the case with base64, but apparently it isn't the case with quoted-printable. What is happening here is the original post has Content-Transfer-Encoding: quoted-printable This bug should go away if python.org mailman is upgraded to 2.1.6. Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] Mailman 2.1.6 release candidate up
Hi all, Now we are on the last stage before the final release of 2.1.6. After the release of 2.1.6b5, we've got translation updates from the language champions including Leona for zh_CN (Chinese, China). Hopefully, I will be able to release the 2.1.6 final within a week. Cheers, -- Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] Mailman 2.1.6 release candidate up
Sorry that I forget to add the download pointer; http://sourceforge.net/project/showfiles.php?group_id=103 or http://mm.tkikuchi.net/mailman-2.1.6rc1.tgz Hi all, Now we are on the last stage before the final release of 2.1.6. After the release of 2.1.6b5, we've got translation updates from the language champions including Leona for zh_CN (Chinese, China). Hopefully, I will be able to release the 2.1.6 final within a week. Cheers, -- Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] header not working in body
Erik Peterson wrote: I have been trying to get the Urgent: header to work and I can't seem to get it to happen. I can't modify my MUA's headers to add it directly, so I was attempting to make Urgent: listpassword the first line of the message followed by a blank line and then the original body, which seems to be indicated in a bunch of emails found while searching this list... http://www.mail-archive.com/mailman-users@python.org/msg15961.html http://www.mail-archive.com/mailman-users@python.org/msg16405.html This was simply ignored by Mailman. The message was sent out in tact with this line to the non-digest recipients and held for the digest recipients. Don't worry, I'm using a test list... I made sure that the message was sent in text/plain, no extraneous characters, the Urgent: was the first line of the message, etc. Browsing through the code, it looks like Urgent: is only valid in header position. Not supported for the first line in body. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] prob: Downgrade detected, from version 0x20200a0 to version 0x20106b5
Jan Kellermann wrote: Hi! Certainly you may help: we installed 2.2 some month ago and want now update to the current 1.6-version. the 2.2-version came from the cvs-rep on sf.net while installing we got the message -- Downgrade detected, from version 0x20200a0 to version 0x20106b5 This is probably not safe. Exiting. -- Try find Version.py in your prefix/Mailman directory and edit like: VERSION = 2.2a0 - 2.1.4 MINOR_REV = 2 - 1 MICRO_REV = 0 - 4 REL_LEVEL = ALPHA - FINAL Then install 2.1.6b5 from http://mm.tkikuchi.net/mailman-2.1.6b5.tgz -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] Mailman 2.1.6 beta 5 released
Hi, Sorry for the delay of 2.1.6 but a serious bug was found in the previous beta releases. I put a final beta release before jumping up to the release candidate. The bug is related to 'Privacy - SPAM filter - header_filter_rules'. So, I want all of you, who have had brave souls to upgrade 2.1.6 beta and who use this feature, to upgrade again to 2.1.6 beta 5. The tarball is placed at http://mm.tkikuchi.net/mailman-2.1.6b5.tgz # Sorry but it looks like I have not access to the file releases on SF. -- Tokio Kikuchi tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] Safe Archive Clean
Hi, Young, Darren wrote: Now, what I'm finding is that if a list has content filtering disabled, or set to allow other MIME types through (such as HTML) and if a member is of type digest and they have the plain option enabled for digests, they receive a message in their digest with a URL of where they can see a copy of the original message. The URL included has a pipermail address in it. On the server, the file was placed in that directory however I have pipermail disabled (since we don't support archives). Any way to disable this part or do I just need to wipe those archived files? Currently, the plain text digest saves attachments in the pipermail area on the hypothis that the archive is available. Or, the digest members have no means to get the attachments other than to decode MIME manually. You should wipe the archive periodically if you don't want those to be kept in the archive area. You may also have to tell the list owners (and users) your policy and not to use plain text digests but use mime digests. You will have to hack the code if you want to do this silently. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] A non-text attachment was scrubbed...
Hi Matt Clark wrote: Hi I'm also getting an identical error to Chris Boulter Oddly, when there is a text body as well as binary attachments, the attachments seem to be silently dropped without mention, and there is no hyperlink to retrieve them. Is there any reason why this might happen? I'm running Version 2.1.5. of mailman. I've tried applying the patch 891491 scrubber.py last ammended by Tokio Kikuchi In Sept 2004 using the following command Patch -p1 /path/to/patch With no joy. patch -p1 /tmp/scrubber.patch.20040912 can't find file to patch at input line 5 Perhaps you used the wrong -p or --strip option? Tried -p0 ? The text leading up to this was: -- |Index: Mailman/Handlers/Scrubber.py |=== |--- Mailman/Handlers/Scrubber.py (.../trunk) (revision 21) |+++ Mailman/Handlers/Scrubber.py (.../branches/scrubber_branch) (revision 21) -- You'd better get mailman-2.1.6b4.tgz from sourceforge and install because all my patches are now integrated in the codebase. Or, wait 2.1.6 final which will spin out soon. :-) -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] Codes
Hi,
PeteBell wrote:
Hi again!
Thank you for taking the time to give such a helpful and detailed answer!
I was hoping I could just change my PHP to something about if the code
is greater than 279 then hide the member. But it looks a little more
difficult than that.
It's also difficult when you consider that I don't have access to either
mailman or python. Where do I get this thing member_status you refer to?
This is what you call 'code'.
if your php program read like this:
if ($code 279) { ... }
then you only have to change like so:
if ($code 16) { ... }
You can browse the mailman source code from
http://sourceforge.net/projects/mailman/ - cvs - browse
http://cvs.sourceforge.net/viewcvs.py/mailman/
Thanks again
Regards
Pete
On 22 Feb 2005, at 00:44, Tokio Kikuchi wrote:
Hi, again.
PeteBell wrote:
Thanks very much.
One more thing, please. As you can see below, your email arrived
with rather strange formatting and each line was broken in odd
places. Can I just check:
Do you mean that all the following mean hide?...
280 and 314
And 264 means SHOW?
Or are you trying to explain something more complex which I am not
understanding?
Cheers
Pete, UK
On 21 Feb 2005, at 12:07, Tokio Kikuchi wrote:
280 16
16
264 16
0
314 16
16
This is python interactive mode operations.
Quote the keys to the value again.
# Bitfield for user options. See DEFAULT_NEW_MEMBER_OPTIONS above to
set
# defaults for all new lists.
Digests = 0 # handled by other mechanism, doesn't need a
flag.
DisableDelivery = 1 # Obsolete; use set/getDeliveryStatus()
DontReceiveOwnPosts = 2 # Non-digesters only
AcknowledgePosts= 4
DisableMime = 8 # Digesters only
ConcealSubscription = 16
SuppressPasswordReminder = 32
ReceiveNonmatchingTopics = 64
Moderate = 128
DontReceiveDuplicates = 256
Take number 280. This is 256 + 16 + 8
= DontReceiveDuplicates
+ ConcealSubscription
+ DisableMime
So the member doesn't want receive list mail if his address is in Cc:
list, not want to list his address in the roster page, and he want
plain text digest if he move to digest mode.
264 = 256 + 8 = DontReceiveDuplicates
+ DisableMime
Similar to above but this member doesn't care if his address is listed
in roster page.
314 = 256 + 32 + 16 + 8 + 2
= DontReceiveDuplicates
+ SuppressPasswordReminder
+ ConcealSubscription
+ DisableMime
+ DontReceiveOwnPosts
This member doesn't want to get monthly password reminder, and doesn't
want to receive his own posts adding the options of the first member.
There should be many combination of numbers which indicate 'hide'
status but there is a nice operation to get this; 'bitwise and'. So,
if you get members subscription status code in say member_status, then
you should write a program like:
if member_status 16:
print 'Hide this member.'
else:
print 'Expose this menber.'
This is Python code and not PHP in which you are wirting, but the
logic should be clear. You can refer to the php '' operation manual at
http://www.php.net/manual/en/language.operators.bitwise.php
(After quick googling).
Cheers,
--
Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp
http://weather.is.kochi-u.ac.jp/
--
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] auto-rejecting BCCs?
Hi, John Owens wrote: I apologize if this is a current option and I just can't find it ... I have generic_nonmember_action set to Accept, since we're using the list to have non-members as questions. I receive spam on this list too that is BCCed. Every mail I've seen on this list that has been BCCed has been spam. Thus require_explicit_destination is set to yes. What I can't find is how to reject this mail automatically; instead it's held for approval for me, and I'd rather it be junked immediately. Is there a setting for this? No. But there is a trick for this if you play with the spam filter. Go to admin - privacy - spam page and put following in spam filter rule 1: to:.*your-list-name and set this to Accept. Then, click Add new item (after this one) and put to:.* and set this to Reject or Discard. Do not forget to click [Submit Your Changes]. I've not fully tested but this should work. You can first set the second rule to Hold and check the effect. Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] auto-rejecting BCCs?
Sorry, my mistake. Go to admin - privacy - spam page and put following in spam filter rule 1: to:.*your-list-name ^to:.*your-list-name There was Delivered-To: header in my test message this matched. and set this to Accept. Then, click Add new item (after this one) and put to:.* and set this to Reject or Discard. Do not forget to click [Submit Your Changes]. I've not fully tested but this should work. You can first set the second rule to Hold and check the effect. Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] auto-rejecting BCCs?
AAYEE!! This doesn't work AT ALL! You will get deep recursive hold for administrative notices. I should look into the code. Tokio Kikuchi wrote: Sorry, my mistake. Go to admin - privacy - spam page and put following in spam filter rule 1: to:.*your-list-name ^to:.*your-list-name There was Delivered-To: header in my test message this matched. and set this to Accept. Then, click Add new item (after this one) and put to:.* and set this to Reject or Discard. Do not forget to click [Submit Your Changes]. I've not fully tested but this should work. You can first set the second rule to Hold and check the effect. Cheers, -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] auto-rejecting BCCs?
Sorry that I was so noizy by myself. :-P Tokio Kikuchi wrote: AAYEE!! This doesn't work AT ALL! You will get deep recursive hold for administrative notices. I should look into the code. Tokio Kikuchi wrote: Sorry, my mistake. Go to admin - privacy - spam page and put following in spam filter rule 1: \nto:.*your-list-name There was Delivered-To: header in my test message this matched. and set this to Accept. Then, click Add new item (after this one) and put . (anything match) and set this to Reject or Discard. Do not forget to click [Submit Your Changes]. '\n' is needed for the first rule because the headers are concatnated in a single string. Also, do not add '@your.dom.ain' in it because this doesn't match '[EMAIL PROTECTED]' which is the held notice destination and they are held and held again. (If you discard, that's OK.) I've not fully tested but this should work. You can first set the second rule to Hold and check the effect. I will fully test net time. ;-P Cheers, Tokio -- 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] auto-rejecting BCCs?
Brad Knowles wrote: At 9:59 PM +0900 2005-02-22, Tokio Kikuchi wrote: Go to admin - privacy - spam page and put following in spam filter rule 1: \nto:.*your-list-name What about Delivered-to: and/or Cc: headers? Oh yeah, you can change rule 1 like: \nto:.*your-list-name cc:.*your-list-name It looks like Delivered-to: is added by Postfix for Bcc:ed message and should not be added here. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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] auto-rejecting BCCs?
Thank you Brad. I went to bed after my last post. Brad Knowles wrote: At 9:37 AM -0800 2005-02-22, John Owens wrote: So, um, would you mind summarizing your suggestion? The large number I got makes me nervous about doing the right thing. Tokio did. Put this in your rule 1, and make your action Accept: \nto:.*your-list-name cc:.*your-list-name Put this in your rule 2, and make your action Reject or Discard as appropriate: . Yes, that is a single dot. That will allow the rule to match anything. I've just posted a new entry in the Mailman FAQ Wizard. http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.051.htp Feel free to add/edit this to grow the list of recipe. -- Tokio Kikuchi, tkikuchi@ is.kochi-u.ac.jp http://weather.is.kochi-u.ac.jp/ -- 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
