Mailman 3 April 2003 - Mailman-Developers

Outgoing qrunner dies on 'None' object has no attribute...
by Martin Maechler 19 Apr '03

19 Apr '03

This has happened with increasing intensity here, only since running mailman 2.1.1 (since March 4 or so). Note that the following is an informal bug report of what I think at least two different problems. ------------------------------------------------------------------------------- AttributeError: 'None' object has no attribute 'has_key' Traceback (most recent call last): File "/usr/local/app/mailman-sfs/2.1.1/bin/qrunner", line 270, in ? main() File "/usr/local/app/mailman-sfs/2.1.1/bin/qrunner", line 230, in main qrunner.run() File "/usr/local/app/mailman-sfs/2.1.1/Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/local/app/mailman-sfs/2.1.1/Mailman/Queue/Runner.py", line 88, in _oneloop msg, msgdata = self._switchboard.dequeue(filebase) File "/usr/local/app/mailman-sfs/2.1.1/Mailman/Queue/Switchboard.py", line 151, in dequeue if data.has_key('rejection-notice'): ------------------------------------------------------------------------------- Qrunner dies and is restarted -- but only 10 times when it really dies with ------ logs/qrunner ------------------------------------- Apr 14 11:06:24 2003 (1230) Qrunner OutgoingRunner reached maximum restart limit of 10, not restarting. --------------------------------------------------------- I have just now set this (MAX_RESTARTS in bin/mailmanctl) to 10000 instead of 10 (BTW, shouldn't this be configurable via mm_cfg.py as well?) >From then on, qfiles/out/* starts growing and growing and mailing list delivery becomes very slow at least in the case, where I have two (or 4) slices Outgoing Runners. --- Bug # 2 --- BTW: When I do have more than one runner, things get faster, *BUT* I sometimes get the same message delivered by more than one of the outgoing runners. This seems to happen (almost?) ony in the case where the queue is almost empty. But it is quite embarrassing to this twice delivered to everyone on the list. Thank you for mailman, and thanks for feedback / suggestions / fixes ... Martin Maechler <maechler(a)stat.math.ethz.ch> http://stat.ethz.ch/~maechler/ Seminar fuer Statistik, ETH-Zentrum LEO C16 Leonhardstr. 27 ETH (Federal Inst. Technology) 8092 Zurich SWITZERLAND phone: x-41-1-632-3408 fax: ...-1228 <><

2 1

Bug on mailman 2.1.1 with non ascii mails?
by Guille -bisho- 19 Apr '03

19 Apr '03

I have a problem with mailman 2.1.1 (Debian package 2.1.1-4) The OutgoingRunner was failing as follows: Traceback (most recent call last): File "/var/lib/mailman/bin/qrunner", line 270, in ? main() File "/var/lib/mailman/bin/qrunner", line 230, in main qrunner.run() File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 59, in run filecnt = self._oneloop() File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 114, in _oneloop self._doperiodic() File "/usr/lib/mailman/Mailman/Queue/OutgoingRunner.py", line 136, in _doperiodic mlist.registerBounce(recip, msg) File "/var/lib/mailman/Mailman/Bouncer.py", line 155, in registerBounce self.disableBouncingMember(member, info, msg) File "/var/lib/mailman/Mailman/Bouncer.py", line 165, in disableBouncingMember self.__sendAdminBounceNotice(member, msg) File "/var/lib/mailman/Mailman/Bouncer.py", line 187, in __sendAdminBounceNotice lang=self.preferred_language) File "/var/lib/mailman/Mailman/Message.py", line 203, in __init__ self['Subject'] = Header(subject, charset, header_name='Subject') File "/var/lib/mailman/pythonlib/email/Header.py", line 164, in __init__ self.append(s, charset) File "/var/lib/mailman/pythonlib/email/Header.py", line 230, in append ustr = unicode(s, incodec) UnicodeError : ASCII decoding error: ordinal not in range(128) In that line there was a: ustr = unicode(s, ustr = unicode(s, incodecincodec) And the incodec was set on line 229 as: incodec = charset.input_codec or 'us-ascii' It seems that charset.input_codec was not set, and the pending to send emails were not us-ascii code. I have to change that line to: incodec = charset.input_codec or 'iso-8859-15' And also change the line 234: - outcodec = charset.output_codec or 'us-ascii' + outcodec = charset.output_codec or 'iso-8859-15' and the OutgoingRunner was able then to process the emails without hanging. Is important to make more checks, to avoid DOS atacks to mailman servers. A message with non-ascii chars could be considered as ascii making the OutgoingRunner to die, and stoping the service. This only happens if: if isinstance(s, StringType): because the exception is not caught later the the conversion is done properly capturing the exception: elif isinstance(s, UnicodeType): for charset in USASCII, charset, UTF8: try: outcodec = charset.output_codec or 'us-ascii' s = s.encode(outcodec) break except UnicodeError: ... How you think this should be solved? I'm not and expert in python... -- ,,,.. .-. / -_.' ' "" ,/ ,/, / , ,\ , , ``-, , , , ) PAZ SÍ /,,' ,/ ,/ / ¡GUERRA NO! , / bisho! -=] 15/04/2003 [=-

2 1

Re: [Mailman-Developers] Mailman web interfaces and design
by mch＠cix.compulink.co.uk 19 Apr '03

19 Apr '03

In-Reply-To: <E193HzZ-0001LX-02(a)mail.python.org> Anthony wrote: > > I know that there are templates, and I have defined the <MM-Stylesheet> > > tag, but for some of those templates it doesn't get translated...It > is the bit that you don't know that really interests me ;) Ah. Didn't know about the <MM-Stylesheet> tag... as you may have seen, I used a fully-qualified URL for the stylesheet. That saved me worrying about the path to the stylesheet... which, I *guess*, may be your problem... It would be, er, elegant, to make the default templates point to a stylesheet in the list's own directory, and supply a default stylesheet? No? Mike

4 3

Umbrella and nested lists moderation requests
by HINSHAW,JERRY L (HP-Boise,ex1) 19 Apr '03

19 Apr '03

HI, SORRY to send this to developers directly. This question is still awaiting approval to the Mailman users list. I want to create an umbrella list (a list with ONLY lists nested within it). The top level list is simply named top. The nested lists are injerry, inclint, and incat. I have mailman-v2.1.1 installed and is the FIRST mailman to be installed on these servers. I have reviewed the FAQs and the mailing lists archives, which currently only address ensuring unique mail addresses are in the nested lists. I have currently set ALL lists (top, injerry, incat, and inclint) with NO Moderation and accepting from everyone. If I mail to any one of the nested (injerry, incat, and inclint) lists as anyone the message delivers no problems. HOWEVER when I send to the umbrella list (top) the List owner of the nested lists (injerry, incat, and inclint) get a message indicating moderation is required for the message sent. Have a missed something or is this incorrect behavior?? BELOW is the config_list output of the parameters I think are important. Attached is the complete config_list output for the umbrella list (top) and a nested list (injerry). Also is the mm_cfg.py settings for the site. Any help or ideas would be appreciated. Thanks Jerry TOP Level List (Umbrella List) bash-2.04$ grep member top | grep -v "^#" umbrella_member_suffix = '-owner' new_member_options = 256 default_member_moderation = 0 member_moderation_action = 0 member_moderation_notice = '' accept_these_nonmembers = [] hold_these_nonmembers = [] reject_these_nonmembers = [] discard_these_nonmembers = [] generic_nonmember_action = 0 NESTED LIST bash-2.04$ grep member injerry | grep -v "^#" umbrella_member_suffix = '-owner' new_member_options = 256 default_member_moderation = 0 member_moderation_action = 0 member_moderation_notice = '' accept_these_nonmembers = [] hold_these_nonmembers = [] reject_these_nonmembers = [] discard_these_nonmembers = [] generic_nonmember_action = 0 Mm_cfg.py settings other than virtual host which is set. # Should a list, by default be advertised? What is the default maximum number # of explicit recipients allowed? What is the default maximum message size # allowed? DEFAULT_LIST_ADVERTISED = 1 DEFAULT_MAX_NUM_RECIPIENTS = 100000 DEFAULT_MAX_MESSAGE_SIZE = 0 # KB # Are archives on or off by default? DEFAULT_ARCHIVE = 0 # 0=Off, 1=On # Set this variable to 1 to allow list owners to delete their own mailing # lists. You may not want to give them this power, in which case, setting # this variable to 0 instead requires list removal to be done by the site # administrator, via the command line script bin/rmlist. OWNERS_CAN_DELETE_THEIR_OWN_LISTS = 1 ##### # Digestification defaults ##### # Will list be available in non-digested form? DEFAULT_NONDIGESTABLE = 1 # Will list be available in digested form? DEFAULT_DIGESTABLE = 0 DEFAULT_DIGEST_IS_DEFAULT = 0 # This variable controls whether monthly password reminders are sent. DEFAULT_SEND_REMINDERS = 0 # Send welcome messages to new users? Probably should keep this set to 1. DEFAULT_SEND_WELCOME_MSG = 0 # Send goodbye messages to unsubscribed members? Probably should keep this # set to 1. DEFAULT_SEND_GOODBYE_MSG = 0 # How long should messages which have delivery failures continue to be # retried? After this period of time, a message that has failed recipients # will be dequeued and those recipients will never receive the message. DELIVERY_RETRY_PERIOD = days(3) # Should list members, by default, have their posts be moderated? DEFAULT_DEFAULT_MEMBER_MODERATION = 0 # What shold happen to non-member posts which are do not match explicit # non-member actions? # 0 = Accept # 1 = Hold # 2 = Reject # 3 = Discard DEFAULT_GENERIC_NONMEMBER_ACTION = 0 # See "Bitfield for user options" below; make this a sum of those options, to # make all new members of lists start with those options flagged. We assume # by default that people don't want to receive two copies of posts. Note # however that the member moderation flag's initial value is controlled by the # list's config variable default_member_moderation. # 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 #DEFAULT_NEW_MEMBER_OPTIONS = 256

2 1

New MTA Handler
by Alan K. Stebbens 18 Apr '03

18 Apr '03

Howdy, I've written a new MTA handler for mailman for integrating a procmail delivery system with Mailman. In particular, it is very useful for delivery through a virtual host user. The MTA handler has hooks for the creation and deletion of lists. When a list is created, or when one is deleted, the MTA handler causes the a procmail recipe file to be (re)created with the appropriate recipes to direct incoming mail to the appropriate Mailman commands. I've posted it to the patches at: https://sourceforge.net/tracker/index.php?func=detail&aid=723918&group_id=1… The patch includes a shar archive of the Procmail.py and updated Defaults.py modules. -- Best regards, Alan K. Stebbens <aks(a)stebbens.org> (Voice/Fax: +1.866.579.0801) Ill-chosen abstraction is particularly evident in the design of the ADA runtime system. The interface to the ADA runtime system is so opaque that it is impossible to model or predict its performance, making it effectively useless for real-time systems. -- Marc D. Donner and David H. Jameson.

1 0

Bug in Mailman version 2.1.1 -- ASCII decoding error
by Martin Maechler 17 Apr '03

17 Apr '03

Dear developers, I got this from a user of one of my mailing list, where I have allowed all possible languages for a user interface -- and I *do* get bad errors that kill the outgoing runner, seen mostly when users chose "ja" (Japanese) and "fr" (French) Can you advise me (as site and list administrator) what I could / should do and try? Is this the proper mailing list? Regards, Martin Maechler <maechler(a)stat.math.ethz.ch> http://stat.ethz.ch/~maechler/ Seminar fuer Statistik, ETH-Zentrum LEO C16 Leonhardstr. 27 ETH (Federal Inst. Technology) 8092 Zurich SWITZERLAND phone: x-41-1-632-3408 fax: ...-1228 <>< ------- start of forwarded message ------- Hi, I have the following bug when I click on the button "Résilier" (unsubscribe in french) after having received the mail with the URL for unsubscription. As a result, I can not unsubscribe ! Thanks ! <.......> Bug in Mailman version 2.1.1 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (most recent call last): File "/usr/local/app/mailman-sfs/2.1.1/scripts/driver", line 87, in run_main main() File "/usr/local/app/mailman-sfs/2.1.1/Mailman/Cgi/confirm.py", line 118, in main unsubscription_confirm(mlist, doc, cookie) File "/usr/local/app/mailman-sfs/2.1.1/Mailman/Cgi/confirm.py", line 399, in unsubscription_confirm op, addr = mlist.ProcessConfirmation(cookie) File "/usr/local/app/mailman-sfs/2.1.1/Mailman/MailList.py", line 1081, in ProcessConfirmation self.ApprovedDeleteMember(addr, whence=whence) File "/usr/local/app/mailman-sfs/2.1.1/Mailman/MailList.py", line 935, in ApprovedDeleteMember msg = Message.OwnerNotification(self, subject, text) File "/usr/local/app/mailman-sfs/2.1.1/Mailman/Message.py", line 257, in __init__ UserNotification.__init__(self, recips, sender, subject, text, lang) File "/usr/local/app/mailman-sfs/2.1.1/Mailman/Message.py", line 203, in __init__ self['Subject'] = Header(subject, charset, header_name='Subject') File "/usr/local/app/mailman-sfs/2.1.1/pythonlib/email/Header.py", line 164, in __init__ self.append(s, charset) File "/usr/local/app/mailman-sfs/2.1.1/pythonlib/email/Header.py", line 230, in append ustr = unicode(s, incodec) UnicodeError: ASCII decoding error: ordinal not in range(128) ------------------------------------------------------------------------ -------- Python information: Variable Value sys.version 2.1.3 (#2, Jul 11 2002, 15:08:42) [GCC 3.1] sys.executable /usr/local/app/python/current/bin/python sys.prefix /usr/local/app/python/current sys.exec_prefix /usr/local/app/python/current sys.path /usr/local/app/python/current sys.platform sunos5 ------------------------------------------------------------------------ -------- Environment variables: Variable Value SSL_SERVER_I_DN /C=CH/ST=Switzerland/L=Zurich/O=ETH Zurich/OU=Department of Mathematics/CN=ISG D-MATH/Email=webmaster(a)math.ethz.ch downgrade_1_0 1 SSL_SERVER_S_DN_O ETH Zurich SSL_CIPHER_USEKEYSIZE 128 SSL_SERVER_M_VERSION 1 SSL_VERSION_INTERFACE mod_ssl/2.8.10 CONTENT_TYPE application/x-www-form-urlencoded SSL_SERVER_V_END Feb 4 16:20:08 2013 GMT ssl_unclean_shutdown 1 REQUEST_METHOD POST HTTP_ACCEPT_LANGUAGE fr SSL_PROTOCOL SSLv3 GATEWAY_INTERFACE CGI/1.1 nokeepalive 1 SSL_SERVER_I_DN_Email webmaster(a)math.ethz.ch HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/msword, application/x-shockwave-flash, */* REQUEST_URI /mailman/confirm/r-help SSL_SERVER_S_DN_C CH HTTP_ACCEPT_ENCODING gzip, deflate HTTPS on HTTP_HOST www.stat.math.ethz.ch TZ MET SSL_SERVER_S_DN_L Zurich SSL_SERVER_A_SIG md5WithRSAEncryption SSL_SERVER_M_SERIAL 07 SERVER_ADMIN webmaster(a)math.ethz.ch SCRIPT_FILENAME /usr/local.hg/app/apache/vhosts/sfs/mailman/confirm PYTHONPATH /usr/local/app/mailman-sfs/2.1.1 SSL_VERSION_LIBRARY OpenSSL/0.9.6c SSL_SERVER_S_DN_OU Seminar for Statistics SERVER_PROTOCOL HTTP/1.1 SSL_SERVER_S_DN_Email webmaster(a)math.ethz.ch SSL_SERVER_I_DN_OU Department of Mathematics DOCUMENT_ROOT /usr/local.hg/app/apache/vhosts/sfs/htdocs SERVER_ADDR 129.132.148.206 SSL_SERVER_V_START Feb 7 16:20:08 2003 GMT SSL_SERVER_I_DN_O ETH Zurich SSL_SERVER_I_DN_L Zurich SERVER_PORT 443 PATH_TRANSLATED /usr/local.hg/app/apache/vhosts/sfs/htdocs/r-help UNIQUE_ID Pp5yw4GElMUAAA@goHM SSL_CIPHER_ALGKEYSIZE 128 REMOTE_ADDR 81.1.18.46 SERVER_NAME www.stat.math.ethz.ch SSL_SERVER_I_DN_CN ISG D-MATH HTTP_CONNECTION Keep-Alive HTTP_USER_AGENT Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) SSL_CLIENT_VERIFY NONE CONTENT_LENGTH 65 SSL_SESSION_ID B923993173D4BEB1CA2680BA3F265B6E234FBC330ECE7F6CD7A5FE374EF1E126 SSL_SERVER_I_DN_ST Switzerland SSL_CIPHER RC4-MD5 SSL_SERVER_S_DN /C=CH/ST=Switzerland/L=Zurich/O=ETH Zurich/OU=Seminar for Statistics/CN=www.stat.math.ethz.ch/Email=webmaster(a)math.ethz.ch SSL_SERVER_S_DN_CN www.stat.math.ethz.ch PATH_INFO /r-help REMOTE_PORT 4038 SSL_SERVER_I_DN_C CH SERVER_SIGNATURE Apache/1.3.26 Server at www.stat.math.ethz.ch Port 443 SSL_SERVER_S_DN_ST Switzerland SSL_SERVER_A_KEY rsaEncryption SCRIPT_NAME /mailman/confirm QUERY_STRING SERVER_SOFTWARE Apache/1.3.26 (Unix) PHP/4.2.2 DAV/1.0.3 mod_perl/1.27 mod_ssl/2.8.10 OpenSSL/0.9.6c HTTP_CACHE_CONTROL no-cache SSL_CIPHER_EXPORT false HTTP_REFERER https://www.stat.math.ethz.ch/mailman/confirm/r-help/ae97e43f39ab5e9884f 6f8c5a75a1a56eb56ed65 force_response_1_0 1 ------- end of forwarded message -------

1 0

2.1.1 mbox archive doesn't handle lines starting with "From " correctly?
by Eric D. Christensen 17 Apr '03

17 Apr '03

I'm seeing problems with the mbox archives after upgrading mailman from 2.0 to 2.1.1. I started to report these as bugs, but then thought that I'd better check in here first just in case I'm missing something silly. Apologies for cross posting to both users and developers lists.... First, a little background... I use both pipermail and mbox format archives for all of our lists. I use the mbox format mainly as a backup so we can regenerate the pipermail archives (via 'arch --wipe list'). Since some of our lists have over 5 years of mailman archives now, having the mbox archives around has save my butt several times. Too bad servers don't last as long as the mailing lists running on them! :-) I'll admit up front that I'm NOT a python programmer.... perl, C, java, PHP, but not python. So I'm only slightly familiar with the syntax and totally clueless beyond that. I'm hoping to NOT have to use this problem as a reason to learn python (though I'd like to someday when I'm not quite so busy). Anyway, here are the two problems I'm seeing with mbox archives: After upgrading mailman from 2.0 to 2.1.1 (and python itself to 2.2.2) I regenerated the pipermail archives from the mbox archives and found that suddenly I had a bunch of messages with "[no subject]", all together starting just about the time I switched the lists over the 2.1.1. Upon further investigation I found two issues that make the mbox file invalid (or at least suspect): 1. No newline before "From " lines in the mbox with 2.1.1. Sine the 2.1.1 update it appears the the mbox archiver is no longer instering a newline before starting a new message. This results in the "From_" line being directly below the last line of the previous message. This confuses the mbox parser something awful.... it also confuses elm, mutt, and mh if I try to read the mbox files with them. I found the code in Mailbox.py (in AppendMessage @ line 46) that gets called from Archiver/Archiver.py to handle inserting the newline if the last thing in the mbox file isn't already a newline before appending the message, but it doesn't seem to be working correctly. Am I missing something or is AppendMessage broken in this respect? 2. Lines beginning with "From " inside of a message body are not handled. If a line inside a message body starts with the string "From ", it is being mis-interpreted as the beginning of a new message (i.e. it's being treated as an envelope "From " line. I'm not quite sure who to fault on this one... I believe that it's common practice to somehow quote this case, in which case it s Generator that's not doing the right thing. I think this is supported by the fact the other mail agents (elm, mutt, etc...) are confused by this unquoted "From " in the message body. It's probably a bit much to ask utilities like arch to try to discern body from envelope on the fly while reading in the mbox file. Any insight, pointers or ideas on these before I report them as bugs? -- Eric D. Christensen <edc(a)proadmin.com> Proadmin, Inc. - http://www.proadmin.com

2 2

Re: [Mailman-Developers] English (USA)
by Roger Lynn 14 Apr '03

14 Apr '03

Marty Galyean wrote: > How hard would it really be for someone really concerned about the lack > of a non-USA English option to port a non-USA English (UK I assume) and > so add to the project rather than just trying to relabel what is clearly > in reality American English? This was my preferred solution, but I couldn't find any documentation on www.list.org on how to produce a new translation. I might have another go when I have some time, but renaming the language was the easy fix. As I said before, so far I've noticed only *ONE* word that needed changing. <snip> > What I find ironic is that I am strongly of the mind that if American > English had been labeled as merely 'English' to start with that someone > out there would have been offended about "Americans *assuming* that > their brand of English is standard! I want it labeled 'English (USA) so > that people are not deceived!". This is probably true. > Oh yeah, almost forgot. I suppose we need a Canadian English also. I > don't think I'd do very well on that. As far as I know it is the same > as UK which shows how little I know, I am sure. I'm probably wrong, but afaik US spelling is used in Canada. Roger

2 2

Display full name in roster display
by Net Ops Center 12 Apr '03

12 Apr '03

The following diff to HTMLFormatter.py in Ver 2.1.1 will display the full name if defined in the roster (view subscriber) list. It will display in full email address format as: "Full Name" < [obscured]email.addr > Caveat- I don't think this breaks anything else. I don't know for sure. Enjoy, MB /usr/local/mailman/Mailman/$ diff HTMLFormatter.py.dist HTMLFormatter.py 92c92 < showing = Utils.ObscureEmail(person, for_text=1) --- > email = Utils.ObscureEmail(person, for_text=1) 94c94,99 < showing = person --- > email = person > fullname = Utils.uncanonstr(self.getMemberName(person), lang) > if fullname: > showing = '"%s" < %s >' % (fullname, email) > else: > showing = email

1 0

Help with patch install
by Adam Boettiger 11 Apr '03

11 Apr '03

I need help installing this patch on 2.1.1: Edit header/body of messages <http://sourceforge.net/tracker/index.php?func=detail&aid=644129&group_id=10 3&atid=300103> Rather than have someone do it for me, I'd like someone to walk me through it so that I can install future patches myself. I am willing to pay money. Please contact me off-list at boettiger(a)pobox.com Thanks. AB

1 0