Mailman 3 February 2007 - Mailman-coders

[ mailman-Bugs-1667570 ] RegExp not working in 2.1.5
by SourceForge.net Feb. 23, 2007

Feb. 23, 2007

Bugs item #1667570, was opened at 2007-02-23 19:07 Message generated for change (Comment added) made by qchrontech You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1667570&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: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Michael O (qchrontech) Assigned to: Nobody/Anonymous (nobody) Summary: RegExp not working in 2.1.5 Initial Comment: Under "accept_these_nonmembers (privacy): List of non-member addresses whose postings should be automatically accepted." I have the following RegExp's and I still continue to receive notices as the admin to approve the email from addresses listed below. I tested the RegExp to make sure that the e-mail addresses are successfully matched and they are. I believe in 2.1.2 this was working fine with the same RegExp. List of non-member addresses whose postings should be automatically accepted. ^[^@]+@(.*\.)?qchron\.(?=com$|net$).*$ ^[^@]+@(.*\.)?nyc\.gov$ post from emeeks(a)comptroller.nyc.gov requires approval post from ahutchi(a)comptroller.nyc.gov requires approval post from jsimmon(a)comptroller.nyc.gov requires approval I saw no previous bug reports on this and am unsure if this is fixed in 2.1.9 so I submitted it. ---------------------------------------------------------------------- >Comment By: Michael O (qchrontech) Date: 2007-02-23 21:30 Message: Logged In: YES user_id=1631912 Originator: YES Vetta log Feb 13 12:57:25 2007 (13626) Editors post from emeeks(a)comptroller.nyc.gov held, message-id=<9634B41B9ED66B44AAC9674F95755AAB035518AE(a)smex03.comptroller.nycnet>: Message has implicit destination ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-23 20:03 Message: Logged In: YES user_id=1123998 Originator: NO It works for me in current mailman, and the only changes to Mailman/Handlers/Moderate since 2.1.3 have to do with allowing a list specified nonmember_rejection_notice. The only other change since 2.1.2 was to accept posts from the news->mail gateway. Are you sure these posts aren't being held for some other reason. What does Mailman's vette log give as the hold reason. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1667570&group_…

1 0

[ mailman-Bugs-1667570 ] RegExp not working in 2.1.5
by SourceForge.net Feb. 23, 2007

Feb. 23, 2007

Bugs item #1667570, was opened at 2007-02-23 16:07 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1667570&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: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Michael O (qchrontech) Assigned to: Nobody/Anonymous (nobody) Summary: RegExp not working in 2.1.5 Initial Comment: Under "accept_these_nonmembers (privacy): List of non-member addresses whose postings should be automatically accepted." I have the following RegExp's and I still continue to receive notices as the admin to approve the email from addresses listed below. I tested the RegExp to make sure that the e-mail addresses are successfully matched and they are. I believe in 2.1.2 this was working fine with the same RegExp. List of non-member addresses whose postings should be automatically accepted. ^[^@]+@(.*\.)?qchron\.(?=com$|net$).*$ ^[^@]+@(.*\.)?nyc\.gov$ post from emeeks(a)comptroller.nyc.gov requires approval post from ahutchi(a)comptroller.nyc.gov requires approval post from jsimmon(a)comptroller.nyc.gov requires approval I saw no previous bug reports on this and am unsure if this is fixed in 2.1.9 so I submitted it. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-02-23 17:03 Message: Logged In: YES user_id=1123998 Originator: NO It works for me in current mailman, and the only changes to Mailman/Handlers/Moderate since 2.1.3 have to do with allowing a list specified nonmember_rejection_notice. The only other change since 2.1.2 was to accept posts from the news->mail gateway. Are you sure these posts aren't being held for some other reason. What does Mailman's vette log give as the hold reason. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1667570&group_…

1 0

[ mailman-Bugs-1667570 ] RegExp not working in 2.1.5
by SourceForge.net Feb. 23, 2007

Feb. 23, 2007

Bugs item #1667570, was opened at 2007-02-23 19:07 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=1667570&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: security/privacy Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Michael O (qchrontech) Assigned to: Nobody/Anonymous (nobody) Summary: RegExp not working in 2.1.5 Initial Comment: Under "accept_these_nonmembers (privacy): List of non-member addresses whose postings should be automatically accepted." I have the following RegExp's and I still continue to receive notices as the admin to approve the email from addresses listed below. I tested the RegExp to make sure that the e-mail addresses are successfully matched and they are. I believe in 2.1.2 this was working fine with the same RegExp. List of non-member addresses whose postings should be automatically accepted. ^[^@]+@(.*\.)?qchron\.(?=com$|net$).*$ ^[^@]+@(.*\.)?nyc\.gov$ post from emeeks(a)comptroller.nyc.gov requires approval post from ahutchi(a)comptroller.nyc.gov requires approval post from jsimmon(a)comptroller.nyc.gov requires approval I saw no previous bug reports on this and am unsure if this is fixed in 2.1.9 so I submitted it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1667570&group_…

1 0

[ mailman-Feature Requests-1664425 ] next/previous message links should use active sort method
by SourceForge.net Feb. 20, 2007

Feb. 20, 2007

Feature Requests item #1664425, was opened at 2007-02-20 10:30 Message generated for change (Comment added) made by mamandel You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1664425&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: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mark A. Mandel (mamandel) Assigned to: Nobody/Anonymous (nobody) Summary: next/previous message links should use active sort method Initial Comment: When you are reading a message in an archive, the "previous message" and "next message" always refer to the sort by date, ignoring the sort that you are currently using. This makes them useless for reading through a thread, or for looking at messages by the same author or with the same subject line. They should use the sort order that the user has selected. We use version 2.1.7. ---------------------------------------------------------------------- >Comment By: Mark A. Mandel (mamandel) Date: 2007-02-20 19:46 Message: Logged In: YES user_id=915526 Originator: YES (Update) So, give the admin an option, check boxes, for which sort order(s) to use when building the archive. If I as administrator am willing to spend the space at the top of each letter page to show prev and next by date, prev and next by thread, prev and next by author, and prev and next by subject, or any subset of those pairs, I'd like that option. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-20 19:31 Message: Logged In: YES user_id=1123998 Originator: NO Actually, the previous and next links refer to thread order, not date order. Also, this issue has been partially addressed for Mailman 2.2 by changing the description of the links to: # Previous message (by thread): <prior subject> # Next message (by thread): <next subject> I know this doesn't answer your request, but given the way the pipermail html archives are built as static html pages, your request would require a separate html file for each message/sequence, thus nearly quadrupling the size of the html archive. The alternative would require archive message pages to be built on the fly by CGIs for both public and private archives. Neither of these alternatives is likely to be implemented in the current pipermail archiver. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1664425&group_…

1 0

[ mailman-Feature Requests-1664425 ] next/previous message links should use active sort method
by SourceForge.net Feb. 20, 2007

Feb. 20, 2007

Feature Requests item #1664425, was opened at 2007-02-20 07:30 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1664425&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: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mark A. Mandel (mamandel) Assigned to: Nobody/Anonymous (nobody) Summary: next/previous message links should use active sort method Initial Comment: When you are reading a message in an archive, the "previous message" and "next message" always refer to the sort by date, ignoring the sort that you are currently using. This makes them useless for reading through a thread, or for looking at messages by the same author or with the same subject line. They should use the sort order that the user has selected. We use version 2.1.7. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-02-20 16:31 Message: Logged In: YES user_id=1123998 Originator: NO Actually, the previous and next links refer to thread order, not date order. Also, this issue has been partially addressed for Mailman 2.2 by changing the description of the links to: # Previous message (by thread): <prior subject> # Next message (by thread): <next subject> I know this doesn't answer your request, but given the way the pipermail html archives are built as static html pages, your request would require a separate html file for each message/sequence, thus nearly quadrupling the size of the html archive. The alternative would require archive message pages to be built on the fly by CGIs for both public and private archives. Neither of these alternatives is likely to be implemented in the current pipermail archiver. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1664425&group_…

1 0

[ mailman-Feature Requests-1664425 ] next/previous message links should use active sort method
by SourceForge.net Feb. 20, 2007

Feb. 20, 2007

Feature Requests item #1664425, was opened at 2007-02-20 10:30 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1664425&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: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Mark A. Mandel (mamandel) Assigned to: Nobody/Anonymous (nobody) Summary: next/previous message links should use active sort method Initial Comment: When you are reading a message in an archive, the "previous message" and "next message" always refer to the sort by date, ignoring the sort that you are currently using. This makes them useless for reading through a thread, or for looking at messages by the same author or with the same subject line. They should use the sort order that the user has selected. We use version 2.1.7. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1664425&group_…

1 0

[ mailman-Bugs-1495122 ] Mailman strips format=flowed from Content-Type header
by SourceForge.net Feb. 19, 2007

Feb. 19, 2007

Bugs item #1495122, was opened at 2006-05-25 12:24 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1495122&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: Open Resolution: None Priority: 5 Private: No Submitted By: Bart Jacobs (radiantskies) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman strips format=flowed from Content-Type header Initial Comment: It seems that Mailman strips the format=flowed argument from the Content-Type: text/plain header when delivering incoming e-mails to subscribers. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-02-19 17:12 Message: Logged In: YES user_id=1123998 Originator: NO I have attached a patch (flowed.patch.txt) that applies to Mailman 2.1.9 and 2.1.8. Line numbers may need adjusting for earlier versions. This is a preliminary patch for testing and shouldn't be considered official at this point. Feedback will be appreciated. File Added: flowed.patch.txt ---------------------------------------------------------------------- Comment By: P T Withington (ptwithy) Date: 2006-10-13 13:37 Message: Logged In: YES user_id=615189 Thanks, that's great. For now, I am very happy that I can just turn off my footer and get the right behavior (as a work-around). ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-10-13 11:23 Message: Logged In: YES user_id=1123998 Regarding the previous comment. I don't disagee with you, and my 2006-06-13 comment wasn't meant to imply that I wasn't interested in fixing this, just that there might be more to it than is apparent at first glance. I do have it on my 'to do' list. ---------------------------------------------------------------------- Comment By: P T Withington (ptwithy) Date: 2006-10-13 10:05 Message: Logged In: YES user_id=615189 Man this bug drives me NUTS! Surely it is more important to maintain the content of the message that to quibble about the format on header/footer. Any halfway intelligent mail client will wrap long URLs, expecting them to be reflowed by the recipient, but since mailman strips out the format and delsp from the Content-type, the recipient is left in the lurch and sees the URL as multiple lines. In format-flowed, only lines that end in <space><linefeed> are re-flowed. If the header/footer lines end in <linefeed> they will not be reflowed, so I don't see the need to have a different format for them? What am I missing? ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-06-13 09:34 Message: Logged In: YES user_id=1123998 I think you have found the cause. Scrubber also does the same thing when flattening the message, but now we have a difficult decision. If we want to 'fix' Decorate, we now are faced with a situation where we may be adding a 'format=fixed' header and/or footer to a 'format=flowed' message body. This potential incompatability may require us to 'wrap' the message and add the header/footer as separate parts in this case. This will undoubtedly raise additional complaints. In the case of Scrubber, this may lead us to scrub the actual message body part - not a good thing. I may be over-reacting here. It may turn out that it is OK to render the header/footer/scrubber messages as 'format=flowed'. Although I can contrive a footer for example (by putting trailing spaces on intermediate lines) that will be munged by rendering as 'format=flowed', this may not be a problem in practice, and Decorate could always be made to strip the spaces. There are also potentially issues with stripping of leading spaces because of the assumption that they are 'stuffed'. I don't know how big an issue this is in practice. Note, if we do preserve 'format=' we also need to preserve 'delsp='. ---------------------------------------------------------------------- Comment By: Bart Jacobs (radiantskies) Date: 2006-06-12 23:54 Message: Logged In: YES user_id=924185 I've browsed the mailman source code a bit and I found some suspicious code in /trunk/mailman/Mailman/Handlers/Decorate.py. If the list admin specifies a header or footer to be added to outgoing messages, then the content-type header is zapped and then regenerated from just the charset info, i.e. the format=flowed parameter is lost. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1495122&group_…

1 0

[ mailman-Bugs-1661574 ] arch corrupts archives, but only for the last month
by SourceForge.net Feb. 16, 2007

Feb. 16, 2007

Bugs item #1661574, was opened at 2007-02-16 06:54 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1661574&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: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 9 Private: No Submitted By: David A. Desrosiers (desrod) Assigned to: Nobody/Anonymous (nobody) Summary: arch corrupts archives, but only for the last month Initial Comment: I think this problem has been reported before in previous versions, and its back again in 2.1.9. When I regenerate archives for our lists, if ANY message contains a '<' character in the body, Mailman splits it as a new message, and everything after that gets corrupted. This means if someone pastes some XML into the body of a message (which happens quite often on our lists) or some HTML, or the headers of an email, Mailman will break it, but *ONLY* for the latest month's messages, even if the message that started it, was months or years ago. If a message sent in April of 2003 includes an '<' as the first character anywhere in the body of the message, February 2007's archive will be corrupted. You can see the results of this over here: http://lists.plkr.org/pipermail/plucker-list/2007-February/thread.html And also here: http://lists.plkr.org/pipermail/plucker-dev/2007-February/thread.html The raw mbox files are fine, every message is intact. I don't see this problem on other lists I maintain, it only seems to affect lists where HTML or XML or mail headers are pasted into the body of the message. I'd call this grave, because its odd how it just dumps itself on the latest month's archive, when the latest month's messages don't even have the problem. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-02-16 08:58 Message: Logged In: YES user_id=1123998 Originator: NO What am I looking for at <http://lists.plkr.org/pipermail/plucker-list/2007-February/thread.html>? It looks OK to me. <http://lists.plkr.org/pipermail/plucker-dev/2007-February/thread.html> returns a 404. There is an issue in that if the body of some message in the archives/private/<listname>.mbox/<listname>.mbox file (or whatever mbox is input to bin/arch) contains a line that begins with "From ", the archiver takes that line as an mbox message separator and the message is truncated at that point, and the rest of the message is seen as a new message without a date so it is archived with the current date. It sounds like that may be what you are seeing, but it has nothing to do with a '<' as the first character of a line. It has to do with 'unescaped' 'From ' lines in the bodies of messages. Mailman currently precedes any 'From ' at the beginning of a body line with a '>' making it '>From ' in the .mbox and avoiding the problem, but old .mbox files and .mbox files from other sources may have unescaped 'From ' lines. There is a bin/cleanarch script distributed with Mailman to help 'fix' old .mbox files with this problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1661574&group_…

1 0

[ mailman-Bugs-1661574 ] arch corrupts archives, but only for the last month
by SourceForge.net Feb. 16, 2007

Feb. 16, 2007

Bugs item #1661574, was opened at 2007-02-16 14:54 Message generated for change (Settings changed) made by desrod You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1661574&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: command line scripts Group: 2.1 (stable) Status: Open Resolution: None >Priority: 9 Private: No Submitted By: David A. Desrosiers (desrod) Assigned to: Nobody/Anonymous (nobody) Summary: arch corrupts archives, but only for the last month Initial Comment: I think this problem has been reported before in previous versions, and its back again in 2.1.9. When I regenerate archives for our lists, if ANY message contains a '<' character in the body, Mailman splits it as a new message, and everything after that gets corrupted. This means if someone pastes some XML into the body of a message (which happens quite often on our lists) or some HTML, or the headers of an email, Mailman will break it, but *ONLY* for the latest month's messages, even if the message that started it, was months or years ago. If a message sent in April of 2003 includes an '<' as the first character anywhere in the body of the message, February 2007's archive will be corrupted. You can see the results of this over here: http://lists.plkr.org/pipermail/plucker-list/2007-February/thread.html And also here: http://lists.plkr.org/pipermail/plucker-dev/2007-February/thread.html The raw mbox files are fine, every message is intact. I don't see this problem on other lists I maintain, it only seems to affect lists where HTML or XML or mail headers are pasted into the body of the message. I'd call this grave, because its odd how it just dumps itself on the latest month's archive, when the latest month's messages don't even have the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1661574&group_…

1 0

[ mailman-Bugs-1661574 ] arch corrupts archives, but only for the last month
by SourceForge.net Feb. 16, 2007

Feb. 16, 2007

Bugs item #1661574, was opened at 2007-02-16 14:54 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=1661574&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: command line scripts Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: David A. Desrosiers (desrod) Assigned to: Nobody/Anonymous (nobody) Summary: arch corrupts archives, but only for the last month Initial Comment: I think this problem has been reported before in previous versions, and its back again in 2.1.9. When I regenerate archives for our lists, if ANY message contains a '<' character in the body, Mailman splits it as a new message, and everything after that gets corrupted. This means if someone pastes some XML into the body of a message (which happens quite often on our lists) or some HTML, or the headers of an email, Mailman will break it, but *ONLY* for the latest month's messages, even if the message that started it, was months or years ago. If a message sent in April of 2003 includes an '<' as the first character anywhere in the body of the message, February 2007's archive will be corrupted. You can see the results of this over here: http://lists.plkr.org/pipermail/plucker-list/2007-February/thread.html And also here: http://lists.plkr.org/pipermail/plucker-dev/2007-February/thread.html The raw mbox files are fine, every message is intact. I don't see this problem on other lists I maintain, it only seems to affect lists where HTML or XML or mail headers are pasted into the body of the message. I'd call this grave, because its odd how it just dumps itself on the latest month's archive, when the latest month's messages don't even have the problem. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1661574&group_…

1 0