Mailman 3 April 2002 - Mailman-Developers

Traceback on double rename
by Marc MERLIN 03 May '02

03 May '02

I have a user who says he got this on mailman 2.1b1cvs He explains below how he did it. ----- Forwarded message from David T-G <davidtg(a)justpickone.org> ----- Subject: Mailman results for Empeg-faq From: empeg-faq-request(a)merlins.org To: davidtg-empeg(a)justpickone.org X-List-Administrivia: yes This is an automated response. There were problems with the email commands you sent to Mailman via the administrative address empeg-faq-request(a)empeg.merlins.org. To obtain instructions on valid Mailman email commands, send email to empeg-faq-request(a)empeg.merlins.org with the word "help" in the subject line or in the body of the message. If you want to reach the human being that manages this mailing list, please send your message to empeg-faq-owner(a)empeg.merlins.org. The following is a detailed description of the problems. ***** confirm 97bbfd70939538b155776d5e652af14bc6032c36 >>>>> An unexpected Mailman error has occurred. >>>>> >>>>> Please forward your request to the human list administrator in charge >>>>> of this list at <empeg-faq-owner(a)empeg.merlins.org>. The traceback is >>>>> attached below and will be forwarded to the list administrator >>>>> automatically. Traceback (most recent call last): File "/var/local/mailman/Mailman/MailCommandHandler.py", line 273, in ParseMailCommands self.__dispatch[cmd](args, line, msg) File "/var/local/mailman/Mailman/MailCommandHandler.py", line 727, in ProcessConfirmCmd results = self.ProcessConfirmation(args[0], msg) File "/var/local/mailman/Mailman/MailList.py", line 1041, in ProcessConfirmation self.ApprovedChangeMemberAddress(oldaddr, newaddr, globally) File "/var/local/mailman/Mailman/MailList.py", line 976, in ApprovedChangeMemberAddress self.changeMemberAddress(oldaddr, newaddr) File "/var/local/mailman/Mailman/OldStyleMemberships.py", line 234, in changeMemberAddress self.__assertIsMember(member) File "/var/local/mailman/Mailman/OldStyleMemberships.py", line 113, in __assertIsMember raise Errors.NotAMemberError, member NotAMemberError: davidtg(a)bigfoot.com ----- End forwarded message ----- ----- Forwarded message from David T-G <davidtg(a)justpickone.org> ----- % Were you trying to change your subscription from davidtg(a)bigfoot.com to % davidtg-empeg(a)justpickone.org via the mail interface? No; I did it thru the web interface. % If so, do you mind sending me a copy of the mails you sent to the list % manager (I run a devel version of the upcoming mailman, and I try to help Sorry; any sort of subscribe and confirm messages I just toss in the bit bucket. In addition, once the subscriptions were confirmed, I tossed the list server messages as well. Sorry! % out with small bugs. This one seems to be minor, but we should probably look % into it anyway) Sorry :-) It should be easy to duplicate, though; subscribe to two lists (like empeg-faq and empeg-announce), open two web browsers, go to the two list control pages and log in on each, and then send a change from one and a change from the other. Remember to hit "global" at some point along the way. When replying to the confirmation messages, reply to the first before doing the global change but the second, which might confusingly arrive after said global change, later after the web is done. ----- End forwarded message ----- -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f(a)merlins.org for PGP key

2 1

Prompt Enhancement Request.
by Phil Barnett 02 May '02

02 May '02

What would be the chance of enhancing the following text in the membership modificiation page? I find a lot of people using this option to 'unsubscribe' from the list. I think this would happen less often if there was a better description with a pointer that this is not an unsubscribe function. ------------------- Disable mail delivery Turn this on if you want mail to not be delivered to you for a little while.

3 3

Uncaught runner exception: 'NoneType' object
by totschnig.michael＠uqam.ca 02 May '02

02 May '02

Hello an error related to NoneType objects having no attributes has already been reported on this list. I get such an error only when I create a new list, only the mail sent to mailman-owner enumerating the new aliases to add seems to get caught in this. Should I test the patch Barry sent in message <15534.7944.843739.720556(a)anthem.wooz.org> to solve this problem? My MTA is sendmail. Thanks, Michael Apr 30 00:41:51 2002 (602) Uncaught runner exception: 'NoneType' object has no attribute 'Load' Apr 30 00:41:51 2002 (602) Traceback (most recent call last): File "/var/Mailman/Mailman/Queue/Runner.py", line 105, in __oneloop self.__onefile(msg, msgdata) File "/var/Mailman/Mailman/Queue/Runner.py", line 155, in __onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/var/Mailman/Mailman/Queue/OutgoingRunner.py", line 58, in _dispose mlist.Load() AttributeError: 'NoneType' object has no attribute 'Load'

2 1

a bug?
by Simone Piunno 02 May '02

02 May '02

The site language of my installation is 'it'. Creating a new list with the only permitted language as 'en' I have a list with ['en','it'] (which makes sense) and the preferred language marked as 'it', (which is wrong) Cheers

2 1

[ mailman-Bugs-550524 ] archiving with invalid dates
by noreply＠sourceforge.net 30 Apr '02

30 Apr '02

Bugs item #550524, was opened at 2002-04-30 09:58 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550524&group_id… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Michael Kallas (valshaq) Assigned to: Nobody/Anonymous (nobody) Summary: archiving with invalid dates Initial Comment: If you look at http://mail.gnu.org/mailman/listinfo/help-hurd you'll notice there are mails archived into future archives (because of faked timestamps). I think this should not happen, either deleting it instead (SPAM) or archiving it into the current archive. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550524&group_id…

1 0

[ mailman-Bugs-550462 ] New feature: Automoderate microsoft user
by noreply＠sourceforge.net 30 Apr '02

30 Apr '02

Bugs item #550462, was opened at 2002-04-29 21:53 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550462&group_id… Category: (un)subscribing Group: 2.1 beta Status: Open Resolution: None Priority: 5 Submitted By: Mark Whitis (whitis) Assigned to: Nobody/Anonymous (nobody) Summary: New feature: Automoderate microsoft user Initial Comment: I am not using mailman at the moment but I was looking at its feature list and planned upgrades and found this missing. And it could be added in a very general form that could support many other uses. Reason for suggesting: everytime I post a message on a Linux list, I get a bunch of virus messages from bozos who have subscribed to those lists from a windows box. And I am certainly not alone in that respect. Usually these messages do not arrive via the list but are sent to anyone who posts to the list (often by lurkers). Users of real operating systems who subscribe to lists related to those should not be inconvinienced by those who use microsoft products, there of all places. I would like to suggest that future versions of Mailman include a feature (selected by the moderator) which automatically takes certain actions based on the subscibers email client. This feature could be activated based on the message headers in the replies to subscription confirmation messages. Actions could include: - Placing the user in moderated status (prevents sending virus to the list directly but doesn't prevent the virus from getting addresses from the user). - Cancelling the subscription - Sending a warning message to the user - Requiring the user to send a control message agreeing that their virus software will be kept up to date. - hide or mung all email addresses in copies of messages delivered to this user so email worms/viruses cannot harvest them. The email client status could be updated when the user sends a new control message. Optionally, it could also detect microsoft platforms via the browser ID when people sign on via the web site. Detection could be controlled by a configuration file listing with four fields: action, mail/web, field, and regex: ACCEPT MAIL X-Mailer .*Microsoft Sucks.* REJECT MAIL X-Mailer .*Microsoft Outlook.* REJECT MAIL X-Mimeole .*Microsoft Exchange.* REJECT WEB Browser-ID .*Internet Explorer.* (note: this would be triggered by opera in identify as Internet Explorer mode, but the user can switch to identify as opera). REJECT WEB Browser-ID .*Windows 95.* REJECT WEB Browser-ID .*Windows 98.* REJECT WEB Browser-ID .*Windows NT.* REJECT WEB Browser-ID .*Windows ME.* REJECT WEB Browser-ID .*Windows 2000.* REJECT WEB Browser-ID .*Win16.* REJECT WEB Browser-ID .*Win32.* REJECT WEB Browser-ID .*MSIE.* If you place someone on moderated status based on their mail client or web browser, the reason for moderation should be noted so that they can be automatically un-moderated (if otherwise consistent with policy) when they use a real computer to access the list. This feature could also be used to protect some protection against other problems, as well. Spam, REJECT MAIL From .*hotmail.com.* REJECT MAIL Subject: .*casino.* REJECT ATTACH Content-Type: application/octet-stream REJECT ATTACH Content-Type: audio/x-wav REJECT ATTACH Content-Type: audio/x-midi REJECT BODY "insurance" MODERATE-MSG BODY "profaneword" The config file could be XMLized: <filter action="reject" source="mail" header="X-Mailer" contents=".*microsoft.*" /> Possible Extensions: action: make "actions" instead and allow a comma separated list (or even nested XML action tags) moderate-msg moderate-user unmoderate-user strip-attachments strip-attachment bounce-message append-boilerplate source: comma separated list WEB_POST, WEB_CONTROL, MAIL_POST, MAIL_CONTROL, POST_BODY, POST_ATTACHMENT_HDR, POST_ATTACHMENT_BODY. blacklist: added field. .rss.mail-abuse.org .dul-mail-abuse.org Note that for the Dial Up list, this should only be applied to the first Received line added by the mail server itself. user-status: the users existing status (normal, moderated, moderated-newbie, moderated-badsoftware, trusted, moderator, list_owner, etc.) could be considered in applying filters. XML structure could be much more complicated, as well. <filter userclass="..." source="..."> <pattern> </pattern> <pattern> <exception> <pattern> </pattern> </exception> </pattern> <blacklist> </blacklist> </filter> One could also allow a user so detected to subscribe only after they had pledged to keep their virus checker up to date by sending a special control message or visiting a special web page. This could also be used to filter certain types of spam that have consistent patterns. I have seen the same websites repeately spammed to the same list (until I blew those websites away) from different aliases. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550462&group_id…

1 0

[ mailman-Bugs-517192 ] 2.0.8 borks on dot in local part of addr
by noreply＠sourceforge.net 29 Apr '02

29 Apr '02

Bugs item #517192, was opened at 2002-02-13 13:20 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id… Category: mail delivery Group: 2.0.x >Status: Open Resolution: Out of Date Priority: 5 Submitted By: CrackMonkey (monkeymaster) Assigned to: Nobody/Anonymous (nobody) Summary: 2.0.8 borks on dot in local part of addr Initial Comment: In a mail address's local part (the part to the left of the at sign), it is perfectly valid to have periods. However, mailman stops reading the address right at the @, so that "mr.bad(a)pigdog.org" is shown as "mr.bad". this is disastrous for lists where only subscribers are allowed to post, since the system doesn't allow for exceptions that lack an @ and a FQDN. Either allowing exceptions to be of a more forgiving format, or fixing the broken regex that truncates the mail addresses would solve my problem. I'm getting tired of moderating a legitimate user's posts, especially since the system won't even send the warnings to the correct address. ---------------------------------------------------------------------- >Comment By: CrackMonkey (monkeymaster) Date: 2002-04-29 15:21 Message: Logged In: YES user_id=76237 This happens even when I use python 2.2 ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-04-27 09:34 Message: Logged In: YES user_id=12800 This is really a bug with earlier versions of Python, I believe. MM2.0.x uses the standard library function rfc822.parseaddr() to break and address into its realname + email constituent parts. Here are some examples: % python Python 2.2.1 (#1, Apr 22 2002, 17:14:12) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad <mr.bad(a)pigdog.org>') ('Mr. Bad', 'mr.bad(a)pigdog.org') % python2.1 Python 2.1.3 (#1, Apr 22 2002, 18:17:38) [GCC egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)] on linux2 Type "copyright", "credits" or "license" for more information. >>> from rfc822 import parseaddr >>> parseaddr('Mr. Bad <mr.bad(a)pigdog.org>') ('', 'Mr.Bad') So this is clearly broken in Python 2.1.3, and works in Python 2.2.1. I'll look at backporting the fix to Python 2.1 in case there's ever a 2.1.4. But if you're using an earlier version of Python, this will still be broken. Consider upgrading to Python 2.2.1. ---------------------------------------------------------------------- Comment By: CrackMonkey (monkeymaster) Date: 2002-04-26 12:54 Message: Logged In: YES user_id=76237 The bug turns out not to be when there is a period in the address, but in the plain text name. The mail address in question is: Mr. Bad <mr.bad(a)pigdog.org> I realized this when I saw people who had different text names from their e-mail addresses, as in: Jr. Pickle <picklejr(a)someplace.foo> This would show up as the mythical address "jr.pickle" in mailman, and things would b0rk. ---------------------------------------------------------------------- Comment By: Barry Warsaw (bwarsaw) Date: 2002-03-14 11:18 Message: Logged In: YES user_id=12800 Either I need more information, or this problem is fixed in MM2.1. Quite often I uses test addresses like "barry.warsaw@<wherever>" and I've had no problems with it. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=517192&group_id…

1 0

[ mailman-Bugs-550314 ] Sending to multiple lists chooses one.
by noreply＠sourceforge.net 29 Apr '02

29 Apr '02

Bugs item #550314, was opened at 2002-04-29 14:48 You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550314&group_id… Category: mail delivery Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Jeff Posner (jposnersails) Assigned to: Nobody/Anonymous (nobody) Summary: Sending to multiple lists chooses one. Initial Comment: When I send a single message addressed as multiple lists on to 'TO:' line, each recipient receives exactly one copy. If a single user is a memeber of more than one list, he receives the copy to a "seemingly" random list. I am new to this version (just upgraded from 1.x) and have not seen this problem before. Thanks. ---------------------------------------------------------------------- You can respond by visiting: http://sourceforge.net/tracker/?func=detail&atid=100103&aid=550314&group_id…

1 0

Notifications for bug reports and patches
by barry＠zope.com 29 Apr '02

29 Apr '02

Currently the SourceForge bug and patch trackers for the Mailman project are set to send messages to mailman-cabal(a)python.org, which reaches just the core developers (of which I think I'm the only person currently not .forwarding to /dev/null ;). I'm wondering if it would be useful to redirect those messages to mailman-developers. It would certainly be helpful for me, because it would give you guys a chance to be notified of new bugs or patches, and comment on them via the trackers. This works well in the Python community, and I could certainly use other opinions on a number of bugs and patches. I don't think it would innundate you all with too much traffic. Thoughts? I'd probably turn this on after I finish my current bug triage pass. -Barry

2 1

2.1b1: web-based create and DEFAULT_EMAIL_HOST?
by Harald Koch 28 Apr '02

28 Apr '02

I just created a new list via the web interface, and the 'host_name' parameter for the list was "www.cfrq.net" (the value of DEFAULT_URL_HOST) instead of "cfrq.net" (the value of DEFAULT_EMAIL_HOST). This surprised me... Mailman/Cgi/create.py uses the VIRTUAL_HOSTS stuff to get the correct value for host_name, but I don't have any VIRTUAL_HOSTS defined (other than the default, which should correctly map DEFAULT_URL_HOST to DEFAULT_EMAIL_HOST). Any suggestions as to where to look would be appreciated... -- Harald Koch <chk(a)pobox.com>

2 3