Mailman 3 November 2005 - Mailman-coders

[ mailman-Patches-1365282 ] Add New Langauge Punjabi (pa) to mailman
by SourceForge.net 23 Nov '05

23 Nov '05

Patches item #1365282, was opened at 2005-11-24 05:19 Message generated for change (Settings changed) made by aalam You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1365282&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Amanpreet Singh Alam (aalam) >Assigned to: Tokio Kikuchi (tkikuchi) Summary: Add New Langauge Punjabi (pa) to mailman Initial Comment: Hello I translate mailman to Punajbi and Want to include in mailman. As per direction from Barry, I m attaching file here! following is info about Language "Punjabi" ISO Code = "pa" Coding = Unicode (UTF-8) Can u please include those files for Punjabi to Mailman? thanks AP Singh Alam http://punlinux.sf.net ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1365282&group_…

1 0

[ mailman-Patches-1365282 ] Add New Langauge Punjabi (pa) to mailman
by SourceForge.net 23 Nov '05

23 Nov '05

Patches item #1365282, was opened at 2005-11-24 05:19 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1365282&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: internationalization Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Amanpreet Singh Alam (aalam) Assigned to: Nobody/Anonymous (nobody) Summary: Add New Langauge Punjabi (pa) to mailman Initial Comment: Hello I translate mailman to Punajbi and Want to include in mailman. As per direction from Barry, I m attaching file here! following is info about Language "Punjabi" ISO Code = "pa" Coding = Unicode (UTF-8) Can u please include those files for Punjabi to Mailman? thanks AP Singh Alam http://punlinux.sf.net ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1365282&group_…

1 0

[ mailman-Bugs-971957 ] Uncaught runner exception
by SourceForge.net 23 Nov '05

23 Nov '05

Bugs item #971957, was opened at 2004-06-12 20:36 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=971957&group_i… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: John Distler (jd_waverly) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception Initial Comment: In 2.1.5 Apparently some email message characters can crash the Runner.py. I have inserted $mailman in place of my mailman path in the message below from $mailman/logs/error Jun 12 01:25:48 2004 (16604) Uncaught runner exception: ASCII decoding error: ordinal not in range (128) Jun 12 01:25:48 2004 (16604) Traceback (most recent call last): File "$mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File $mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "$mailman/Mailman/Queue/CommandRunner.py", line 223, in _dispose res = Results(mlist, msg, msgdata) File "$mailman/Mailman/Queue/CommandRunner.py", line 77, in __init__ subj = make_header(decode_header (subj)).__unicode__() File "$mailman/pythonlib/email/Header.py", line 144, in make_header h.append(s, charset) File "$mailman/pythonlib/email/Header.py", line 272, in append ustr = unicode(s, incodec, errors) UnicodeError: ASCII decoding error: ordinal not in range (128) ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2005-11-22 22:00 Message: Logged In: YES user_id=1123998 gray-john wrote: > >I'm seeing this in 2.1.6 as well. We are running Debian >Sarge. Any word on getting this resolved? This error was fixed in source in 2.1.6 by catching and passing the UnicodeError exception. See bug 909490 which is the same problem. If you are seeing this error in 2.1.6, it must be coming from somewhere other than CommandRunner calling make_header. I suggest you try to get a resolution by posting your specific error trace to mailman-users(a)python.org. I'm closing this report. ---------------------------------------------------------------------- Comment By: John Gray (gray-john) Date: 2005-11-22 15:31 Message: Logged In: YES user_id=392368 I'm seeing this in 2.1.6 as well. We are running Debian Sarge. Any word on getting this resolved? ---------------------------------------------------------------------- Comment By: Tommi Tervo (tomtervo) Date: 2004-07-30 06:42 Message: Logged In: YES user_id=1094436 Do you need some additional information for debugging this one, I've over 200 mails stuck on shunts. AFAIK this is quite fatal bug, emails just disappear and nobody gets notification. UnicodeDecodeError: 'ascii' codec can't decode byte 0xf6 in position 10: ordinal not in range(128) Mailman 2.1.5 and python 2.3.4 on Solaris 8. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=971957&group_i…

1 0

[ mailman-Bugs-971957 ] Uncaught runner exception
by SourceForge.net 22 Nov '05

22 Nov '05

Bugs item #971957, was opened at 2004-06-12 23:36 Message generated for change (Comment added) made by gray-john You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=971957&group_i… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: John Distler (jd_waverly) Assigned to: Nobody/Anonymous (nobody) Summary: Uncaught runner exception Initial Comment: In 2.1.5 Apparently some email message characters can crash the Runner.py. I have inserted $mailman in place of my mailman path in the message below from $mailman/logs/error Jun 12 01:25:48 2004 (16604) Uncaught runner exception: ASCII decoding error: ordinal not in range (128) Jun 12 01:25:48 2004 (16604) Traceback (most recent call last): File "$mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File $mailman/Mailman/Queue/Runner.py", line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "$mailman/Mailman/Queue/CommandRunner.py", line 223, in _dispose res = Results(mlist, msg, msgdata) File "$mailman/Mailman/Queue/CommandRunner.py", line 77, in __init__ subj = make_header(decode_header (subj)).__unicode__() File "$mailman/pythonlib/email/Header.py", line 144, in make_header h.append(s, charset) File "$mailman/pythonlib/email/Header.py", line 272, in append ustr = unicode(s, incodec, errors) UnicodeError: ASCII decoding error: ordinal not in range (128) ---------------------------------------------------------------------- Comment By: John Gray (gray-john) Date: 2005-11-22 18:31 Message: Logged In: YES user_id=392368 I'm seeing this in 2.1.6 as well. We are running Debian Sarge. Any word on getting this resolved? ---------------------------------------------------------------------- Comment By: Tommi Tervo (tomtervo) Date: 2004-07-30 09:42 Message: Logged In: YES user_id=1094436 Do you need some additional information for debugging this one, I've over 200 mails stuck on shunts. AFAIK this is quite fatal bug, emails just disappear and nobody gets notification. UnicodeDecodeError: 'ascii' codec can't decode byte 0xf6 in position 10: ordinal not in range(128) Mailman 2.1.5 and python 2.3.4 on Solaris 8. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=971957&group_i…

1 0

[ mailman-Bugs-1363422 ] Valid E-mails Rejected as Invalid
by SourceForge.net 21 Nov '05

21 Nov '05

Bugs item #1363422, was opened at 2005-11-21 21:26 Message generated for change (Settings changed) made by krellis You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1363422&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None >Priority: 7 Submitted By: Tim Wilde (krellis) Assigned to: Nobody/Anonymous (nobody) Summary: Valid E-mails Rejected as Invalid Initial Comment: I ran into a problem recently with sync_members. I was attempting to add a list of addresses that included "---tim---(a)krellis.org", but this address was rejected: bin/sync_members -a=no -f /usr/local/mailinglists/lists/system-status.txt system-status Invalid : ---tim---(a)krellis.org You must fix the preceding invalid addresses first. While this is an ODD address, it is perfectly legal, per section 3.4 of RFC 2822 (http://www.faqs.org/rfcs/rfc2822.html). Rejecting a valid address like this seems like a pretty major problem to me. This was with MailMan 2.1.6 on FreeBSD 4. If there is any more information I can provide, please let me know. Regards, Tim Wilde ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1363422&group_…

1 0

[ mailman-Bugs-1363422 ] Valid E-mails Rejected as Invalid
by SourceForge.net 21 Nov '05

21 Nov '05

Bugs item #1363422, was opened at 2005-11-22 00:26 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1363422&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Krellis (krellis) Assigned to: Nobody/Anonymous (nobody) Summary: Valid E-mails Rejected as Invalid Initial Comment: I ran into a problem recently with sync_members. I was attempting to add a list of addresses that included "---tim---(a)krellis.org", but this address was rejected: bin/sync_members -a=no -f /usr/local/mailinglists/lists/system-status.txt system-status Invalid : ---tim---(a)krellis.org You must fix the preceding invalid addresses first. While this is an ODD address, it is perfectly legal, per section 3.4 of RFC 2822 (http://www.faqs.org/rfcs/rfc2822.html). Rejecting a valid address like this seems like a pretty major problem to me. This was with MailMan 2.1.6 on FreeBSD 4. If there is any more information I can provide, please let me know. Regards, Tim Wilde ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1363422&group_…

1 0

[ mailman-Patches-1246003 ] 2.1.6 senddigests unicode error exception handling
by SourceForge.net 18 Nov '05

18 Nov '05

Patches item #1246003, was opened at 2005-07-27 13:12 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1246003&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: internationalization Group: Mailman 2.1 >Status: Closed >Resolution: Accepted Priority: 5 Submitted By: Auke Kok (sofar) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.6 senddigests unicode error exception handling Initial Comment: Hi, I've had senddigests break on me and this seems to be resolved by adding a proper exception handling as follows: vi +333 Mailman/Handlers/ToDigest.py replace: except LookupError: with: except (UnicodeError, LookupError): after this adjustment all digests are sent out properly again for my lists. symptoms were: Traceback (most recent call last): File "/var/mailman/cron/senddigests", line 94, in ? main() File "/var/mailman/cron/senddigests", line 86, in main mlist.send_digest_now() File "/var/mailman/Mailman/Digester.py", line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 133, in send_digests send_i18n_digests(mlist, mboxfp) File "/var/mailman/Mailman/Handlers/ToDigest.py", line 331, in send_i18n_digests payload = unicode(payload, mcset, 'replace' UnicodeError: ISO-2022-JP decoding error: invalid designation ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-11-19 03:07 Message: Logged In: YES user_id=67709 Accepted and closed. Thank you. ---------------------------------------------------------------------- Comment By: Jonathan Polansky (polansky) Date: 2005-11-02 23:11 Message: Logged In: YES user_id=567517 I just wanted to add that I also ran into this error and this fix seems to have solved the problem. If this could be included in the next mm update, that'd be great. Also, thanks to Auke for the fix! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1246003&group_…

1 0

[ mailman-Patches-1220144 ] allow specifying another list in accept_these_nonmembers
by SourceForge.net 17 Nov '05

17 Nov '05

Patches item #1220144, was opened at 2005-06-14 06:29 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1220144&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: list administration >Group: Mailman 2.2 / 3.0 Status: Open Resolution: None >Priority: 6 Submitted By: Jim Tittsler (jtittsler) >Assigned to: Tokio Kikuchi (tkikuchi) Summary: allow specifying another list in accept_these_nonmembers Initial Comment: Add the capability to logically include the addresses all of the members of another list in the same Mailman installation to accept_these_nonmembers. '@listname' checks the poster's address against the membership of listname. ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-11-18 02:37 Message: Logged In: YES user_id=67709 Marking as an Mailman 2.2 new feature candidate. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1220144&group_…

1 0

[ mailman-Patches-1347962 ] Sibling list: avoid duplicate mail
by SourceForge.net 17 Nov '05

17 Nov '05

Patches item #1347962, was opened at 2005-11-04 05:57 Message generated for change (Comment added) made by tkikuchi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1347962&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Tokio Kikuchi (tkikuchi) Summary: Sibling list: avoid duplicate mail Initial Comment: This patch enables to avoid sending duplicate mail if other list address is specified in to: or cc: header. - Sibling lists are other mailing lists on this site whose members are excluded from regular delivery if those list addresses appear in To: or Cc: header. - The list addresses should be witten in full mail address format (e.g. mailman(a)example.com). Do not specify the list address mutually in the sibling list configuration page or those doubled members won't get message. TBD: - Is the terminology 'sibling' appropriate? - Need more comments in the processing code (CalcRecips.py). ---------------------------------------------------------------------- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2005-11-18 02:24 Message: Logged In: YES user_id=67709 On my second thought, I determined to add 'include' feature in this 'sibling list' idea. Also, the GUI is moved from Genral to NonDigest because I think it is more appropreate. - Exclude lists are the same as the original 'sibling lists' in the first post. - Include lists are the lists on the same mailman installation site whose members are included in the regular delivery if they are not appear in To: of Cc: header. Thus, it may work as 'umbrella list' if the lists are all in the same site. If you have already applied the first version of sibling.patch, you have to backout it before applying this. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1347962&group_…

1 0

[ mailman-Bugs-1268939 ] host_name tag doesn't allow IP addresses
by SourceForge.net 15 Nov '05

15 Nov '05

Bugs item #1268939, was opened at 2005-08-24 12:11 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1268939&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Submitted By: Daniel (doolyo) Assigned to: Nobody/Anonymous (nobody) Summary: host_name tag doesn't allow IP addresses Initial Comment: Hello. I have realised that we cannot put an IP address in the 'host_name' tag. Normally, we can send an e-mail from a client to a server that doesn't have a domain name by just putting it's IP address into square brackets like this: john(a)[142.56.2.72] This works, especially if you have put the same IP address on the destination server in your /etc/mail/local- host-names file on one line (for Sendmail): [142.56.2.72] Now the problem is that if we specify the IP address into square brackets in the 'host_name' tag, then the resolved hostname is returned in the e-mail address instead of this square brackets IP address. I have tried several backslashes like '', [], "", %5B and % 5D but nothing does. Square brackets are still correct to the standard, so I think that this is a bug. Regards, Daniel ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2005-11-15 20:35 Message: Logged In: YES user_id=1123998 Testing confirms that Mailman will accept and us a literal IP address as host_name for a list. This report is closed. ---------------------------------------------------------------------- Comment By: Daniel (doolyo) Date: 2005-11-15 00:24 Message: Logged In: YES user_id=1320890 Hello, msapiro. Thanks for that test. I don't know then what happened at that time on my box, but when I was sending something to a box configured like that with this address in brackets it was not received or processed. Now that you successfully tested it ony our side then my assumption that there was a problem by interpreting the brackets is gone. Maybe there was still a problem with the MTA for incoming mails but it's difficult to say. I don't have anymore that setup now as it's several months I have tested this, so I cannot reproduce this currently. Therefore I think that you can close this report. Thanks for your try. Best regards, Daniel ---------------------------------------------------------------------- Comment By: Daniel (doolyo) Date: 2005-11-14 12:19 Message: Logged In: YES user_id=1320890 The version of Mailman is mailman-2.1.5-33. It is installed from an RPM for RHEL4 (centOS4). The configuration file is the correct one and is properly done through the web interface. I don't think that it is the MTA which causes problems because it works well when I use it directly like this: 'mail john(a)[142.56.2.72]'. Therefore I still think that this could be a bug. Could someone try that on another setup ? Regards, Daniel ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-11-13 15:59 Message: Logged In: YES user_id=1123998 What version of mailman is this? Installed from source or from rpm or other package? In the standard installation the only .cfg file is data/sitelist.cfg. This is provided as an aid to configuring the site list (mailman list) because the normal site defaults for a new list are probably not appropriate for the site list. This file, sitelist.cfg, is intended to be used as input to bin/config_list to actually configure the list. Mailman itself in operation doesn't get anything from any *.cfg file. Actual list configurations are in lists/*/config.pck. So, are you just putting something in some *.cfg file and that's it, or do you or some other custom process in your installation actually run bin/config_list or equivalent to transfer that information the the actual list configuration? If in fact, you have updated the list configuration such that the value of host_name visible on the list's General Options in the web admin interface or visible in the output from 'bin/config_list -o' or in the output from 'bin/dumpdb lists/list_name/config.pck' is the bracketed numeric IP address, and you still have the problem of it being changed, then I think it must be your outgoing MTA that is changing it, not Mailman. As far as I can tell, Mailman always uses the list's host_name attribute as the domain for email addresses. The only exception is for the site list in some cases where the email domain is obtained from the VIRTUAL_HOSTS dictionary which is built by add_virtualhost() directives in Defaults.py/mm_cfg.py. If you have not actually changed the list's host_name attribute because you've only changed some .cfg file and nothing more, then you need to actually update the list. ---------------------------------------------------------------------- Comment By: Daniel (doolyo) Date: 2005-11-09 01:34 Message: Logged In: YES user_id=1320890 The 'host_name' tag I am speaking about is in the /etc/mailman/*.cfg file (or /var/lib/mailman/data/*.cfg). I can make the host_name accept the squared brackets IP address without any problem. It stays there and it is properly placed in the file, it is not changed. However, when I send an e-mail to the list itself, then the e- mail is indicated to come from 'myhost.mydomain.com' instead of keeping '[142.56.2.72]'. That is my problem, because I would like people to be able to answer to this IP address instead of the host name, as this host name is not yet active due to the fact that I am configuring Mailman and testing it. Once it passes my tests, then the domain will be active, but I need this 'from' header containing this exact same '[142.56.2.72]' string than 'host_name' for the system to receive back the e-mails. Kind regards, Daniel ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-11-08 17:14 Message: Logged In: YES user_id=1123998 Can you be more specific? I have tested both Mailman 2.1.5 and 2.1.6 and they accept a host_name of the form [142.56.2.72] on the General Options page with no problem. Is your issue that you can't get General Options to accept a numeric IP in square brackets, or that it is accepted, but it gets 'changed' somewhere else. Please clarify, and if the latter, please be specific about where you observe the 'change'. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1268939&group_…

1 0