Mailman 3 January 2005 - Mailman-coders

[ mailman-Patches-657951 ] Generate RSS summary in archives
by SourceForge.net 19 Aug '22

19 Aug '22

Patches item #657951, was opened at 2002-12-23 14:17 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i… Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 18:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 16:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-17 20:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 15:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 14:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 14:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 14:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i…

2 1

[ mailman-Bugs-1113318 ] translation of 1st-4th quarter in archive
by SourceForge.net 31 Jan '05

31 Jan '05

Bugs item #1113318, was opened at 2005-01-31 18:43 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=1113318&group_… Category: Web/CGI Group: None Status: Open Resolution: None Priority: 5 Submitted By: Thomas Arendsen Hein (thomas_ah) Assigned to: Nobody/Anonymous (nobody) Summary: translation of 1st-4th quarter in archive Initial Comment: Mailman/Archiver/HyperArch.py contains this code: if each == 'quarter': d =["", _("First"), _("Second"), _("Third"), _("Fourth") ] ord = d[int(match.group('quarter'))] return _("%(ord)s quarter %(year)i") "First" to "Fourth" are very generic, therefore the german translation (and probably others, too) look very ugly: Erste(s) Quartal Zweite(r) Quartal Erste(s) Quartal Vierte(s) Quartal It should be: Erstes Quartal Zweites Quartal Drittes Quartal Viertes Quartal I suggest changing the strings to include "quarter": if each == 'quarter': d = ["", _("First quarter"), _("Second quarter"), _("Third quarter"), _("Fourth quarter")] ord = d[int(match.group('quarter'))] return _("%(ord)s %(year)i") Looking at the .po file there are other uses of 1st to 4th, where a similar change would be important for translators. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1113318&group_…

1 0

[ mailman-Bugs-1107972 ] privacy bug in Mailman 2.1.4
by SourceForge.net 30 Jan '05

30 Jan '05

Bugs item #1107972, was opened at 2005-01-23 16:56 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1107972&group_… Category: None Group: None >Status: Closed >Resolution: Duplicate Priority: 5 Submitted By: Leonardo Gregianin (leogregianin) Assigned to: Nobody/Anonymous (nobody) Summary: privacy bug in Mailman 2.1.4 Initial Comment: Traceback (most recent call last): File "/var/lib/mailman/scripts/driver", line 96, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 203, in main change_options(mlist, category, subcat, cgidata, doc, mlist_language) File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 1384, in change_options gui.handleForm(mlist, category, subcat, cgidata, doc) File "/var/lib/mailman/Mailman/Gui/Privacy.py", line 510, in handleForm GUIBase.handleForm(self, mlist, category, subcat, cgidata, doc) File "/var/lib/mailman/Mailman/Gui/GUIBase.py", line 154, in handleForm doc.addError( File "/var/lib/mailman/Mailman/htmlformat.py", line 347, in addError self.AddItem(Header(3, Bold(FontAttr( TypeError: not enough arguments for format string ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-01-29 19:32 Message: Logged In: YES user_id=1123998 This is bug# 1099840 which is fixed in 2.1.6. See https://sourceforge.net/tracker/?func=detail&aid=1099840&group_id=103&atid=… for a more complete description of the cause. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1107972&group_…

1 0

[ mailman-Bugs-1112349 ] Upper-case chars in acceptable_aliases pattern fail to match
by SourceForge.net 30 Jan '05

30 Jan '05

Bugs item #1112349, was opened at 2005-01-29 20:57 Message generated for change (Settings changed) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1112349&group_… Category: mail delivery Group: 2.1 (stable) >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Nobody/Anonymous (nobody) Summary: Upper-case chars in acceptable_aliases pattern fail to match Initial Comment: The HasExplicitDest() method in MailList.py first lower-cases all the To: and Cc: addresses. Then if the list address doesn't match any of these explicit addresses and there are acceptable_aliases, it goes on to attempt to match the lower-cased explicit addresses against the acceptable_aliases patterns using re.match() without an IGNORECASE flag. Thus, for example if acceptable_aliases is MyAddress(a)example.com and the message is To: MyAddress(a)example.com, the match will fail because the To: will be lower-cased and the match will be effectively re.match('MyAddress(a)example.com', 'myaddress(a)example.com') Clearly, this behavior is wrong, but it is not clear to me what the correct behavior is. We could just add an IGNORECASE flag to the re.match() in the domatch() helper. This would be consistent with matching against the lower-case list name, but according to RFC 2822, the local part of the address is locally interpreted so MyAddress(a)example.com may in fact not be the same as myaddress(a)example.com. Thus, it may be that the correct behavior is to build the recips[] list with case-preserved addresses so that the case-sensitive match works. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-01-30 13:34 Message: Logged In: YES user_id=12800 In general, Mailman's philosophy for member addresses is case-preserving, case-folding, meaning that FOO(a)example.com and foo(a)example.com are considered the same member, but if they were subscribed with the former, we will send the message to the former. I think it's valid to extend this philosophy to acceptable_aliases, and so I think the right thing to do is to treat an alias such as FOO(a)example.com the same as foo(a)example.com. I will commit a change that adds the IGNORECASE flag. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1112349&group_…

1 0

[ mailman-Bugs-1112349 ] Upper-case chars in acceptable_aliases pattern fail to match
by SourceForge.net 29 Jan '05

29 Jan '05

Bugs item #1112349, was opened at 2005-01-29 17:57 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=1112349&group_… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Mark Sapiro (msapiro) Assigned to: Nobody/Anonymous (nobody) Summary: Upper-case chars in acceptable_aliases pattern fail to match Initial Comment: The HasExplicitDest() method in MailList.py first lower-cases all the To: and Cc: addresses. Then if the list address doesn't match any of these explicit addresses and there are acceptable_aliases, it goes on to attempt to match the lower-cased explicit addresses against the acceptable_aliases patterns using re.match() without an IGNORECASE flag. Thus, for example if acceptable_aliases is MyAddress(a)example.com and the message is To: MyAddress(a)example.com, the match will fail because the To: will be lower-cased and the match will be effectively re.match('MyAddress(a)example.com', 'myaddress(a)example.com') Clearly, this behavior is wrong, but it is not clear to me what the correct behavior is. We could just add an IGNORECASE flag to the re.match() in the domatch() helper. This would be consistent with matching against the lower-case list name, but according to RFC 2822, the local part of the address is locally interpreted so MyAddress(a)example.com may in fact not be the same as myaddress(a)example.com. Thus, it may be that the correct behavior is to build the recips[] list with case-preserved addresses so that the case-sensitive match works. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1112349&group_…

1 0

[ mailman-Bugs-1107972 ] privacy bug in Mailman 2.1.4
by SourceForge.net 29 Jan '05

29 Jan '05

Bugs item #1107972, was opened at 2005-01-23 13:56 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1107972&group_… Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Leonardo Gregianin (leogregianin) Assigned to: Nobody/Anonymous (nobody) Summary: privacy bug in Mailman 2.1.4 Initial Comment: Traceback (most recent call last): File "/var/lib/mailman/scripts/driver", line 96, in run_main main() File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 203, in main change_options(mlist, category, subcat, cgidata, doc, mlist_language) File "/usr/lib/mailman/Mailman/Cgi/admin.py", line 1384, in change_options gui.handleForm(mlist, category, subcat, cgidata, doc) File "/var/lib/mailman/Mailman/Gui/Privacy.py", line 510, in handleForm GUIBase.handleForm(self, mlist, category, subcat, cgidata, doc) File "/var/lib/mailman/Mailman/Gui/GUIBase.py", line 154, in handleForm doc.addError( File "/var/lib/mailman/Mailman/htmlformat.py", line 347, in addError self.AddItem(Header(3, Bold(FontAttr( TypeError: not enough arguments for format string ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2005-01-29 16:32 Message: Logged In: YES user_id=1123998 This is bug# 1099840 which is fixed in 2.1.6. See https://sourceforge.net/tracker/?func=detail&aid=1099840&group_id=103&atid=… for a more complete description of the cause. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1107972&group_…

1 0

[ mailman-Bugs-1109325 ] Bug with upgrading to Mailman 2.1.4 in SuSE 9.1
by SourceForge.net 29 Jan '05

29 Jan '05

Bugs item #1109325, was opened at 2005-01-25 14:44 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1109325&group_… Category: Web/CGI Group: 2.0.x >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Tim Smith (jallen13) Assigned to: Nobody/Anonymous (nobody) Summary: Bug with upgrading to Mailman 2.1.4 in SuSE 9.1 Initial Comment: [NOTE: This is a "I did it!" story.. the fix is at the bottom of this post :) ) Just wanted to make a report here about some problems I had upgrading Mailman from 2.1.3 to 2.1.4 using Yast Online Update (YOU) in Suse 9.1 AMD64. It broke my web-based GUI, and spit this error into my apache error logs: [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] [----- Mailman Version: 2.1.4 -----] [Tue Jan 25 12:43:57 2005] [error] [client IPADDR [----- Traceback ------] [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] Traceback (most recent call last): [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] File "/usr/lib/mailman/scripts/driver", line 241, in ? [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] run_main() [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] File "/usr/lib/mailman/scripts/driver", line 69, in run_main [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] import xml.sax.saxutils [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] ImportError: No module named xml.sax.saxutils [Tue Jan 25 12:43:57 2005] [error] [client IPADDR] [Mailman: low level unrecoverable exception] And the output of the Web browser going to the mailman location gives this error: Bug in Mailman version 2.1.4 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: Content-type: text/html We're sorry, we hit a bug! Mailman experienced a very low level failure and could not even generate a useful traceback for you. Please report this to the Mailman administrator at this site. --------------------------------------------------------------------- So, I googled around, and found that this error is very common in 2.1.4 version. Just google for "Mailman Low level failure" and you'll get a lot of web pages like the one I just pasted, all for 2.1.4. I got some help from Don Burns from mailman-users list, he told me all I need to do is install python-xml. (Thanks Don!!) So, I used the trusty YAST and searched for python-xml and installed it. Wham-Bam, it works. I guess 2.1.4 version expects python-xml as a depends, whereas the earlier versions didn't care about that. I wanted to document this so maybe it''ll come up quicker for some poor sucker like myself googling around for this answer :) Cheers, Tim Smith ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-01-29 17:57 Message: Logged In: YES user_id=12800 This is really a problem with your Python installation since nothing in Mailman directly imports xml.sax.saxutils. But you knew that because your fix installed whatever bits of Python Suse didn't deem important enough to include by default <wink>. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1109325&group_…

1 0

[ mailman-Bugs-1085651 ] Broken PGP/MIME signature of messages with attachments
by SourceForge.net 29 Jan '05

29 Jan '05

Bugs item #1085651, was opened at 2004-12-15 03:54 Message generated for change (Comment added) made by egagnon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_… Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Etienne M. Gagnon (egagnon) Assigned to: Nobody/Anonymous (nobody) Summary: Broken PGP/MIME signature of messages with attachments Initial Comment: Hi, When I send a PGP/MIME signed message *with* attachments (in addition to the PGP signature) to a Mailman-based mailing list, Firefox/Enigmail fails to verify the signature of the message forwarded by mailman. I have uploaded an example message with a broken signature as attachment to this bug. You can also see how Mailman's automatic archives don't even handle such messages correctly by looking at how it archived that message at: http://sablecc.org/lists/sablecc-user/2004-December/000159.html I've looked in the bugs database and found that a somewhat related problem was reported a while ago, but note that the current bug is different. The original bug was about PGP/MIME signed messages without attachments that were handled incorrectly by Enigmail. This one is about messages with attachments, and it is likely that the bug is Mailman's, at least accroding to the reply I got in: http://bugzilla.mozdev.org/show_bug.cgi?id=8466 Thanks for your help (and for the magnificient software)! Etienne ---------------------------------------------------------------------- >Comment By: Etienne M. Gagnon (egagnon) Date: 2005-01-29 12:08 Message: Logged In: YES user_id=15365 Dear Bas, Thanks a lot for identifying the source of this bug and flagging an upstream bug on Python. Etienne ---------------------------------------------------------------------- Comment By: Bas Wijnen (shevek) Date: 2005-01-24 06:35 Message: Logged In: YES user_id=42389 I checked the source, and this appears to be a bug in Python. It can read and write e-mails, including headers, and they are interpreted. However, it doesn't preserve their whitespace, which is of course fatal for pgp signatures. The bug is filed for python here: http://sourceforge.net/tracker/index.php?func=detail&aid=968430&group_id=54… ---------------------------------------------------------------------- Comment By: Etienne M. Gagnon (egagnon) Date: 2005-01-18 12:30 Message: Logged In: YES user_id=15365 I am attaching a screen shot of the content filtering settings (see the options.png attachment I have added to this bug report). In short, content filtering is disabled, so I don't think it is the cause of the problem. :-/ Etienne ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-16 19:37 Message: Logged In: YES user_id=18417 Look at your content filter settings. What MIME-types are you configured to pass? At the very least, you should be configured to pass the following: multipart/mixed multipart/alternative text/plain application/pgp-signature multipart/signed ---------------------------------------------------------------------- Comment By: Toni Willberg (toniw) Date: 2005-01-07 20:23 Message: Logged In: YES user_id=190645 I can reproduce this bug also. Here's a diff what happened to me: diff -u mail.valid mail.invalid Content-Disposition: attachment; filename=configure.in.pre-pkgconfig.patch -Content-Type: text/x-patch; name=configure.in.pre-pkgconfig.patch; charset=UTF-8 +Content-Type: text/x-patch; name=configure.in.pre-pkgconfig.patch; + charset=UTF-8 Content-Transfer-Encoding: base64 And this was _inside_ gpg-signed block. Mailman should not alter that section at all, right? X-Mailman-Version: 2.1.4 Yours, Toni Willberg <toniw(a)iki.fi> ---------------------------------------------------------------------- Comment By: Etienne M. Gagnon (egagnon) Date: 2004-12-29 23:03 Message: Logged In: YES user_id=15365 Any update? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1085651&group_…

1 0

[ mailman-Patches-1111899 ] SMTPDirect.py can hang indefinitely
by SourceForge.net 28 Jan '05

28 Jan '05

Patches item #1111899, was opened at 2005-01-28 20:17 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=1111899&group_… Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: thienvu (thienvu) Assigned to: Nobody/Anonymous (nobody) Summary: SMTPDirect.py can hang indefinitely Initial Comment: SMTPDirect.py connects to an SMTPHOST that may terminate its TCP connection incorrectly. This will result in the OutgoingRunners hanging, especially if the SMTPHOST still accepts connections. This is a patch that wraps the SMTP transcaction in an alarm() to prevent OutgoingRunners from hanging indefinitely. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1111899&group_…

1 0

[ mailman-Bugs-1108814 ] convert_html_to_plaintext strips text from hotmail
by SourceForge.net 28 Jan '05

28 Jan '05

Bugs item #1108814, was opened at 2005-01-24 22:04 Message generated for change (Comment added) made by kalvos You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1108814&group_… Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Kalvos (kalvos) Assigned to: Nobody/Anonymous (nobody) Summary: convert_html_to_plaintext strips text from hotmail Initial Comment: Mailman version 2.1.5 installed on FreeBSD at pair Networks. I use the web configuration of mailman. It is set up with convert_html_to_plaintext enabled. Recent email via Hotmail has been coming in with no body, even though the original email has text. The text is present, and although ugly, the code looks average for HTML mail. The actual original email content (without headers) is pasted below. No text is passed through Mailman. You can see this archive at http://five.pairlist.net/pipermail/coco/ and the result in this message: http://five.pairlist.net/pipermail/coco/2005-January/012347.html Any advice is appreciated if this is not a bug. <html><div style='background-color:'><DIV class=RTE> <P>OK, this is the hotmail test.<BR>_Glen<BR><BR></P></DIV>> <DIV></DIV>> <DIV></DIV>>OK, the next message from me will come from hotmail, as a test. <DIV></DIV>>-Glen <DIV></DIV>> > > <DIV></DIV>> > Well, the thing to do is, now that we've got a clue, go back to the <DIV></DIV>> > original email agent and make a couple of test posts, & we'll see <DIV></DIV>>who <DIV></DIV>> > gets what now that we know to look for it. <DIV></DIV>> <DIV></DIV>> > >> <DIV></DIV>> > >> > -- John. <DIV></DIV>> > > <DIV></DIV>> > >Brought to you by the 6809, the 6803 and their cousins! <DIV></DIV>> > >Yahoo! Groups Links <DIV></DIV>> > > <DIV></DIV>> > > <DIV></DIV>> > > <DIV></DIV>> > <DIV></DIV>> > -- <DIV></DIV>> > Cheers, Gene <DIV></DIV>> > "There are four boxes to be used in defense of liberty: <DIV></DIV>> >  soap, ballot, jury, and ammo. Please use in that order." <DIV></DIV>> > -Ed Howdershelt (Author) <DIV></DIV>> > 99.32% setiathome rank, not too shabby for a WV hillbilly <DIV></DIV>> > Yahoo.com attorneys please note, additions to this message <DIV></DIV>> > by Gene Heskett are: <DIV></DIV>> > Copyright 2005 by Maurice Eugene Heskett, all rights reserved. <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV>>Brought to you by the 6809, the 6803 and their cousins! <DIV></DIV>>Yahoo! Groups Links <DIV></DIV>> <DIV></DIV>><*> To visit your group on the web, go to: <DIV></DIV>>     http://groups.yahoo.com/group/ColorComputer/ <DIV></DIV>> <DIV></DIV>><*> To unsubscribe from this group, send an email to: <DIV></DIV>>     ColorComputer-unsubscribe(a)yahoogroups.com <DIV></DIV>> <DIV></DIV>><*> Your use of Yahoo! Groups is subject to: <DIV></DIV>>     http://docs.yahoo.com/info/terms/ <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV>> <DIV></DIV></div></html> ---------------------------------------------------------------------- >Comment By: Kalvos (kalvos) Date: 2005-01-28 11:07 Message: Logged In: YES user_id=1204060 Hi, Thanks again. I'm just a list administrator, so I need my hand held. The list members have been warned off HTML posting in the meantime, so these are the only headers I've got. If they don't help, I'll wait until we get another blank email with a Hotmail return address and try to trace it back to the original submission. Here is the header of the original email (as sent to me by another list member) before it goes from Yahoo Groups to the Mailman list: >From glenvdb@h... Mon Jan 24 13:11:23 2005 Return-Path: <glenvdb@h...> X-Sender: glenvdb@h... X-Apparently-To: ColorComputer(a)yahoogroups.com Received: (qmail 63953 invoked from network); 24 Jan 2005 21:11:22 -0000 Received: from unknown (66.218.66.172) by m21.grp.scd.yahoo.com with QMQP; 24 Jan 2005 21:11:22 -0000 Received: from unknown (HELO hotmail.com) (65.54.247.12) by mta4.grp.scd.yahoo.com with SMTP; 24 Jan 2005 21:11:22 -0000 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 24 Jan 2005 13:11:01 -0800 Message-ID: <BAY2-F12E39DA21AB595CF271B67BF850@p...> Received: from 198.53.120.64 by by2fd.bay2.hotmail.msn.com with HTTP; Mon, 24 Jan 2005 21:10:01 GMT X-Originating-Email: [glenvdb@h...] X-Sender: glenvdb@h... To: ColorComputer(a)yahoogroups.com Bcc: Date: Mon, 24 Jan 2005 14:10:01 -0700 Mime-Version: 1.0 Content-Type: text/html; format=flowed X-OriginalArrivalTime: 24 Jan 2005 21:11:01.0201 (UTC) FILETIME=[34DA8C10:01C50259] X-eGroups-Remote-IP: 65.54.247.12 From: "Glen VanDenBiggelaar" <glenvdb@h...> X-Originating-IP: [198.53.120.64] Subject: RE: [Coco] [Color Computer] Re: Blank Emails X-Yahoo-Group-Post: member; u=22654116 X-Yahoo-Profile: glenvdb Complete "blank" (HTML stripped) email with all headers shown by Eudora full-header mode, from the same poster as it comes out of Mailman to the list members: Return-Path: <coco-bounces(a)maltedmedia.com> Delivered-To: bathory-maltedmedia:com-dennis@maltedmedia.com X-Envelope-To: dennis(a)maltedmedia.com Received: (qmail 3612 invoked by uid 3002); 24 Jan 2005 00:26:11 -0000 Delivered-To: bathory-maltedmedia:com-bathory@maltedmedia.com Received: (qmail 3605 invoked from network); 24 Jan 2005 00:26:10 -0000 Received: from five.pairlist.net (216.92.1.121) by qs281.pair.com with SMTP; 24 Jan 2005 00:26:10 -0000 Received: from five.pairlist.net (localhost [127.0.0.1]) by five.pairlist.net (Postfix) with ESMTP id 6E36A1A7CF; Sun, 23 Jan 2005 19:26:05 -0500 (EST) X-Original-To: coco(a)lists5.maltedmedia.com Delivered-To: coco(a)five.pairlist.net Received: from qs281.pair.com (qs281.pair.com [216.92.131.37]) by five.pairlist.net (Postfix) with SMTP id 5E2BE1A7BB for <coco(a)lists5.maltedmedia.com>; Sun, 23 Jan 2005 19:26:04 -0500 (EST) Received: (qmail 3596 invoked by uid 3002); 24 Jan 2005 00:26:04 -0000 Delivered-To: bathory-maltedmedia:com-coco@maltedmedia.com Received: (qmail 3593 invoked from network); 24 Jan 2005 00:26:04 -0000 Received: from n8a.bulk.scd.yahoo.com (66.94.237.42) by qs281.pair.com with SMTP; 24 Jan 2005 00:26:04 -0000 Received: from [66.218.69.5] by n8.bulk.scd.yahoo.com with NNFMP; 24 Jan 2005 00:26:03 -0000 Received: from [66.218.66.27] by mailer5.bulk.scd.yahoo.com with NNFMP; 24 Jan 2005 00:26:03 -0000 X-Yahoo-Newman-Property: groups-email X-Sender: glenvdb(a)hotmail.com X-Apparently-To: ColorComputer(a)yahoogroups.com Received: (qmail 13033 invoked from network); 24 Jan 2005 00:26:02 -0000 Received: from unknown (66.218.66.172) by m21.grp.scd.yahoo.com with QMQP; 24 Jan 2005 00:26:02 -0000 Received: from unknown (HELO hotmail.com) (65.54.247.42) by mta4.grp.scd.yahoo.com with SMTP; 24 Jan 2005 00:26:02 -0000 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 23 Jan 2005 16:26:01 -0800 Message-ID: <BAY2-F426276C4D73702CA3BCE1ABF850(a)phx.gbl> Received: from 198.53.120.64 by by2fd.bay2.hotmail.msn.com with HTTP; Mon, 24 Jan 2005 00:25:58 GMT X-Originating-Email: [glenvdb(a)hotmail.com] X-Sender: glenvdb(a)hotmail.com In-Reply-To: <ct0u1j+93m9(a)eGroups.com> To: ColorComputer(a)yahoogroups.com X-OriginalArrivalTime: 24 Jan 2005 00:26:01.0788 (UTC) FILETIME=[4888AFC0:01C501AB] X-eGroups-Remote-IP: 65.54.247.42 From: "Glen VanDenBiggelaar" <glenvdb(a)hotmail.com> X-Originating-IP: [198.53.120.64] X-Yahoo-Profile: glenvdb Mailing-List: list ColorComputer(a)yahoogroups.com; contact ColorComputer-owner(a)yahoogroups.com Delivered-To: mailing list ColorComputer(a)yahoogroups.com Precedence: bulk Date: Sun, 23 Jan 2005 17:25:58 -0700 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Subject: [Coco] RE: [Color Computer] Re: Floppy drives on E-bay X-BeenThere: coco(a)maltedmedia.com X-Mailman-Version: 2.1.5 Reply-To: ColorComputer(a)yahoogroups.com, CoCoList for Color Computer Enthusiasts <coco(a)maltedmedia.com> List-Id: CoCoList for Color Computer Enthusiasts <coco.maltedmedia.com> List-Unsubscribe: <http://five.pairlist.net/mailman/listinfo/coco>, <mailto:coco-request@maltedmedia.com?subject=unsubscribe> List-Archive: <http://five.pairlist.net/pipermail/coco> List-Post: <mailto:coco@maltedmedia.com> List-Help: <mailto:coco-request@maltedmedia.com?subject=help> List-Subscribe: <http://five.pairlist.net/mailman/listinfo/coco>, <mailto:coco-request@maltedmedia.com?subject=subscribe> Sender: coco-bounces(a)maltedmedia.com Errors-To: coco-bounces(a)maltedmedia.com X-Spam-Filtered: 2339d97e2cf80afbc3f9b452dd9fb067 X-Spam-Status: No, hits=-4.2 required=4.0 tests=MSGID_FROM_MTA_HEADER,BAYES_00 X-Spam-Flag: NO X-Spam-Level: -- Coco mailing list Coco(a)maltedmedia.com http://five.pairlist.net/mailman/listinfo/coco ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-28 10:03 Message: Logged In: YES user_id=18417 Pasting the content of the message body is not useful. There is MIME structure outside of the message body that is not included, and it is this MIME structure information that we need in order to find out what has happened. This is why I said that we needed to be able to look at the *COMPLETE* message contents, both before and after processing by Mailman. You can't just cut-n-paste the message body. ---------------------------------------------------------------------- Comment By: Kalvos (kalvos) Date: 2005-01-28 08:40 Message: Logged In: YES user_id=1204060 Hello, Thanks for the response. In my original post, there was a link the defectively received message, and it is just like the one you found. The other message was as sent through Yahoo and received by Yahoo list members -- the content is pasted above. According to the author, it is what he sent. Pasted above is exactly what would have been received by Mailman. The Yahoo Groups list is a member of our list (with dupes turned off) so both groups can share posts. Dennis ---------------------------------------------------------------------- Comment By: Brad Knowles (shub) Date: 2005-01-28 05:25 Message: Logged In: YES user_id=18417 It was hard to find examples of what you were talking about. Can I assume that you mean messages like <http://five.pairlist.net/pipermail/ coco/2005-January/012348.html>? In this case, what we need to do is to see the original, unedited, version of the message as it was submitted to Mailman, so that we can try to figure out what went wrong and why it was stripped to be "blank" but then submitted to the system. This may require that someone subscribe to Hotmail and send some test messages, both directly to another account as well as to the mailing list, so that we can see both the edited and the unedited versions of the message. Another problem is that this issue may be specific to the configurations of particular people using Hotmail, and it may be difficult to find out what options they have set/changed which result in this kind of behaviour. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1108814&group_…

1 0