Mailman 3 February 2007 - 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-1246004 ] 2.1.6 bin/arch bombs out on unicodeerror
by SourceForge.net 28 Feb '07

28 Feb '07

Bugs item #1246004, was opened at 2005-07-27 15:19 Message generated for change (Comment added) made by schoinobates You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1246004&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: Auke Kok (sofar) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.6 bin/arch bombs out on unicodeerror Initial Comment: Running bin/arch on my i18n- development list I got this beauty: Updating HTML for article 2390 Updating HTML for article 2391 Pickling archive state into /var/mailman/archives/private/xfce-i18n/pipermail.pck Traceback (most recent call last): File "bin/arch", line 200, in ? main() File "bin/arch", line 188, in main archiver.processUnixMailbox(fp, start, end) File "/var/mailman/Mailman/Archiver/pipermail.py", line 573, in processUnixMailbox self.add_article(a) File "/var/mailman/Mailman/Archiver/pipermail.py", line 625, in add_article article.parentID = parentID = self.get_parent_info(arch, article) File "/var/mailman/Mailman/Archiver/pipermail.py", line 657, in get_parent_info article.subject) File "/var/mailman/Mailman/Archiver/HyperDatabase.py", line 311, in getOldestArticle self.__openIndices(archive) File "/var/mailman/Mailman/Archiver/HyperDatabase.py", line 251, in __openIndices t = DumbBTree(os.path.join(arcdir, archive + '-' + i)) File "/var/mailman/Mailman/Archiver/HyperDatabase.py", line 65, in __init__ self.load() File "/var/mailman/Mailman/Archiver/HyperDatabase.py", line 179, in load self.__sort(dirty=1) File "/var/mailman/Mailman/Archiver/HyperDatabase.py", line 73, in __sort self.sorted.sort() UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 0: ordinal not in range(128) ---------------------------------------------------------------------- Comment By: Schoinobates Volans (schoinobates) Date: 2007-02-28 22:16 Message: Logged In: YES user_id=41822 Originator: NO The script needs to actually upgrade all archive volumes, not only the current one, because if a post to a ML comes with a date in the past, it will be added to the old volume. New script: #! /usr/bin/python # # Copyright (C) 2007 Lionel Elie Mamane <lmamane(a)debian.org> # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. """Convert a list's archive databases to unicode where appropriate This script is intended to be run as a bin/withlist script, i.e. % bin/withlist -l -r unicodify_archives <mylist> """ import paths import time from Mailman.i18n import _ from Mailman import mm_cfg def unicodify_string(s): if isinstance(s,unicode): return s elif isinstance(s,str): try: return s.decode() except UnicodeDecodeError: pass try: return s.decode('utf-8') except UnicodeDecodeError: pass return s.decode('windows-1252', 'replace') def unicodify_fst(t): l = list(t[1:]) l.insert(0, unicodify_string(t[0])) return tuple(l) def unicodify_archives(mlist): # Only act if we are using the internal archiver if mm_cfg.PUBLIC_EXTERNAL_ARCHIVER: return else: from Mailman.Archiver import HyperArch h = HyperArch.HyperArchive(mlist) for archive in h.archives: for hdr in ('subject', 'author'): h.database.mapKeys(unicodify_fst, archive, hdr) h.close() if __name__ == '__main__': print _(__doc__.replace('%', '%%')) ---------------------------------------------------------------------- Comment By: Schoinobates Volans (schoinobates) Date: 2007-02-27 23:45 Message: Logged In: YES user_id=41822 Originator: NO In Debian, we fixed that problem with the following patch and running the following withlist script on all mailing list on upgrade. Let me note in passing that the code for clearIndex looks very suspicious: it takes an "index" argument but completely ignores it. It should probably clear its argument and not be hardcoded to clear the thread index. --- Mailman/Archiver/HyperDatabase.py 2005-08-27 03:40:17.000000000 +0200 +++ Mailman/Archiver/HyperDatabase.py 2007-02-27 20:33:41.103527160 +0100 @@ -324,15 +343,22 @@ def clearIndex(self, archive, index): self.__openIndices(archive) if hasattr(self.threadIndex, 'clear'): self.threadIndex.clear() return finished=0 try: key, msgid=self.threadIndex.first() except KeyError: finished=1 while not finished: del self.threadIndex[key] try: key, msgid=self.threadIndex.next() except KeyError: finished=1 + + def mapKeys(self, f, archive, index): + self.__openIndices(archive) + index = getattr(self, index + 'Index') + d = index.dict + index.dict = dict(zip(map(f, d.keys()), d.values())) + index.__dirty = 1 #! /usr/bin/python # # Copyright (C) 2007 Lionel Elie Mamane <lmamane(a)debian.org> # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. """Convert a list's archive databases to unicode where appropriate This script is intended to be run as a bin/withlist script, i.e. % bin/withlist -l -r unicodify_archives <mylist> """ import paths import time from Mailman.i18n import _ from Mailman import mm_cfg def unicodify_string(s): if isinstance(s,unicode): return s elif isinstance(s,str): try: return s.decode() except UnicodeDecodeError: pass try: return s.decode('utf-8') except UnicodeDecodeError: pass return s.decode('windows-1252', 'replace') def unicodify_fst(t): l = list(t[1:]) l.insert(0, unicodify_string(t[0])) return tuple(l) def unicodify_archives(mlist): # Only act if we are using the internal archiver if mm_cfg.PUBLIC_EXTERNAL_ARCHIVER: return else: from Mailman.Archiver import HyperArch h = HyperArch.HyperArchive(mlist) currentVolume = h.dateToVolName(time.time()) if currentVolume in h.archives: for hdr in ('subject', 'author'): h.database.mapKeys(unicodify_fst, currentVolume, hdr) h.close() if __name__ == '__main__': print _(__doc__.replace('%', '%%')) ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-12-15 19:10 Message: Logged In: YES user_id=1123998 Originator: NO See the threads at http://mail.python.org/pipermail/mailman-developers/2006-February/018587.ht… and http://mail.python.org/pipermail/mailman-users/2006-February/049345.html ---------------------------------------------------------------------- Comment By: Eugene Crosser (crosser) Date: 2006-12-15 11:37 Message: Logged In: YES user_id=124141 Originator: NO I can see the same thing (line numbers are different) with 2.1.9 version. Can it be that no one else got bitten by it yet? How to fix it? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1246004&group_…

1 0

[ mailman-Bugs-1246004 ] 2.1.6 bin/arch bombs out on unicodeerror
by SourceForge.net 27 Feb '07

27 Feb '07

Bugs item #1246004, was opened at 2005-07-27 15:19 Message generated for change (Comment added) made by schoinobates You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1246004&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: Auke Kok (sofar) Assigned to: Nobody/Anonymous (nobody) Summary: 2.1.6 bin/arch bombs out on unicodeerror Initial Comment: Running bin/arch on my i18n- development list I got this beauty: Updating HTML for article 2390 Updating HTML for article 2391 Pickling archive state into /var/mailman/archives/private/xfce-i18n/pipermail.pck Traceback (most recent call last): File "bin/arch", line 200, in ? main() File "bin/arch", line 188, in main archiver.processUnixMailbox(fp, start, end) File "/var/mailman/Mailman/Archiver/pipermail.py", line 573, in processUnixMailbox self.add_article(a) File "/var/mailman/Mailman/Archiver/pipermail.py", line 625, in add_article article.parentID = parentID = self.get_parent_info(arch, article) File "/var/mailman/Mailman/Archiver/pipermail.py", line 657, in get_parent_info article.subject) File "/var/mailman/Mailman/Archiver/HyperDatabase.py", line 311, in getOldestArticle self.__openIndices(archive) File "/var/mailman/Mailman/Archiver/HyperDatabase.py", line 251, in __openIndices t = DumbBTree(os.path.join(arcdir, archive + '-' + i)) File "/var/mailman/Mailman/Archiver/HyperDatabase.py", line 65, in __init__ self.load() File "/var/mailman/Mailman/Archiver/HyperDatabase.py", line 179, in load self.__sort(dirty=1) File "/var/mailman/Mailman/Archiver/HyperDatabase.py", line 73, in __sort self.sorted.sort() UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 0: ordinal not in range(128) ---------------------------------------------------------------------- Comment By: Schoinobates Volans (schoinobates) Date: 2007-02-27 23:45 Message: Logged In: YES user_id=41822 Originator: NO In Debian, we fixed that problem with the following patch and running the following withlist script on all mailing list on upgrade. Let me note in passing that the code for clearIndex looks very suspicious: it takes an "index" argument but completely ignores it. It should probably clear its argument and not be hardcoded to clear the thread index. --- Mailman/Archiver/HyperDatabase.py 2005-08-27 03:40:17.000000000 +0200 +++ Mailman/Archiver/HyperDatabase.py 2007-02-27 20:33:41.103527160 +0100 @@ -324,15 +343,22 @@ def clearIndex(self, archive, index): self.__openIndices(archive) if hasattr(self.threadIndex, 'clear'): self.threadIndex.clear() return finished=0 try: key, msgid=self.threadIndex.first() except KeyError: finished=1 while not finished: del self.threadIndex[key] try: key, msgid=self.threadIndex.next() except KeyError: finished=1 + + def mapKeys(self, f, archive, index): + self.__openIndices(archive) + index = getattr(self, index + 'Index') + d = index.dict + index.dict = dict(zip(map(f, d.keys()), d.values())) + index.__dirty = 1 #! /usr/bin/python # # Copyright (C) 2007 Lionel Elie Mamane <lmamane(a)debian.org> # # This program is free software; you can redistribute it and/or # modify it under the terms of the GNU General Public License # as published by the Free Software Foundation; either version 2 # of the License, or (at your option) any later version. # # This program is distributed in the hope that it will be useful, # but WITHOUT ANY WARRANTY; without even the implied warranty of # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the # GNU General Public License for more details. # # You should have received a copy of the GNU General Public License # along with this program; if not, write to the Free Software # Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. """Convert a list's archive databases to unicode where appropriate This script is intended to be run as a bin/withlist script, i.e. % bin/withlist -l -r unicodify_archives <mylist> """ import paths import time from Mailman.i18n import _ from Mailman import mm_cfg def unicodify_string(s): if isinstance(s,unicode): return s elif isinstance(s,str): try: return s.decode() except UnicodeDecodeError: pass try: return s.decode('utf-8') except UnicodeDecodeError: pass return s.decode('windows-1252', 'replace') def unicodify_fst(t): l = list(t[1:]) l.insert(0, unicodify_string(t[0])) return tuple(l) def unicodify_archives(mlist): # Only act if we are using the internal archiver if mm_cfg.PUBLIC_EXTERNAL_ARCHIVER: return else: from Mailman.Archiver import HyperArch h = HyperArch.HyperArchive(mlist) currentVolume = h.dateToVolName(time.time()) if currentVolume in h.archives: for hdr in ('subject', 'author'): h.database.mapKeys(unicodify_fst, currentVolume, hdr) h.close() if __name__ == '__main__': print _(__doc__.replace('%', '%%')) ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-12-15 19:10 Message: Logged In: YES user_id=1123998 Originator: NO See the threads at http://mail.python.org/pipermail/mailman-developers/2006-February/018587.ht… and http://mail.python.org/pipermail/mailman-users/2006-February/049345.html ---------------------------------------------------------------------- Comment By: Eugene Crosser (crosser) Date: 2006-12-15 11:37 Message: Logged In: YES user_id=124141 Originator: NO I can see the same thing (line numbers are different) with 2.1.9 version. Can it be that no one else got bitten by it yet? How to fix it? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1246004&group_…

1 0

[ mailman-Bugs-1495122 ] Mailman strips format=flowed from Content-Type header
by SourceForge.net 26 Feb '07

26 Feb '07

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: Mark Sapiro (msapiro) 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-26 09:39 Message: Logged In: YES user_id=1123998 Originator: NO I replaced the patch again. This time, the Scrubber.py patch is functionally identical to 217616: flowed.patch.txt, but I have added more comments to the Scrubber patch specifically related to why it won't work for the archive or the plain format digest. The Decorate.py patch has been updated to remove any trailing spaces from lines of msg_header and msg_footer so they won't be inadvertently flowed. I have the feeling that the biggest issue for most occurs in Decorate.py in adding msg_header and/or msg_footer, and this is fixed. File Added: flowed.patch.txt ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-24 22:38 Message: Logged In: YES user_id=1123998 Originator: NO I have replaced the flowed.patch.txt file attached. The previous scrubber patch didn't work. This one has been more thoroughly tested and does work at least for the test cases tried. There is an additional fix in this scrubber patch which has to do with getting the appropriate character set for the part separator. See the thread beginning at <http://mail.python.org/pipermail/mailman-users/2006-November/054515.html>. File Added: flowed.patch.txt ---------------------------------------------------------------------- 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-1495122 ] Mailman strips format=flowed from Content-Type header
by SourceForge.net 25 Feb '07

25 Feb '07

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-24 22:38 Message: Logged In: YES user_id=1123998 Originator: NO I have replaced the flowed.patch.txt file attached. The previous scrubber patch didn't work. This one has been more thoroughly tested and does work at least for the test cases tried. There is an additional fix in this scrubber patch which has to do with getting the appropriate character set for the part separator. See the thread beginning at <http://mail.python.org/pipermail/mailman-users/2006-November/054515.html>. File Added: flowed.patch.txt ---------------------------------------------------------------------- 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-1667570 ] RegExp not working in 2.1.5
by SourceForge.net 23 Feb '07

23 Feb '07

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: Closed Resolution: Invalid 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 19:46 Message: Logged In: YES user_id=1123998 Originator: NO I'm not sure you understand what require_explicit_destination and acceptable_aliases do. If require explicit destination is Yes, some address in the To: or Cc: headers of the post must be either the list posting address or match an address or re in acceptable aliases. If you put ^[^@]+@(.*\.)?qchron\.(?=com$|net$).*$ in acceptable aliases, it will only have an effect if a matching address (e.g. jdoe(a)server.qchron.net) is in the To: or Cc: of a post to the list. If any address that can deliver to your list is in the qchron.com or qchron.net domain, then yes, this will allow them all to be accepted as well as a whole bunch more IF the address that got to the list was in a To: or Cc: header. But, I suspect the problem in this case was that no list address was in a To: or Cc: of the post. This has nothing to do with who the post is From: or whether or not it is from a list member. If a member or an acceptable non-member sends a post To: msapiro(a)users.sourceforge.net with a Bcc: to your list, your list is going to hold it for implicit destination. The question you have to answer for yourself is do you want to accept without moderator action, posts which aren't explicitly addressed in To: or Cc: to your list or to some other address that gets to your list. If you do, then set require_explicit_destination to No. If you don't, then set require_explicit_destination to Yes and make sure that any 'other' addresses that will deliver to your list are in acceptable_aliases (this should be very few addresses). In the later case posters will be required to explicitly name the list or an acceptable alias in To: or Cc: or the post will be held. ---------------------------------------------------------------------- Comment By: Michael O (qchrontech) Date: 2007-02-23 19:14 Message: Logged In: YES user_id=1631912 Originator: YES ^[^@]+@(.*\.)?qchron\.(?=com$|net$).*$ posted in the acceptable_aliases. Will this allow all aliases to the mail list to pass? ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-23 18:48 Message: Logged In: YES user_id=1123998 Originator: NO Re: your followup. You have several choices, but adding ^[^@]+@(.*\.)?nyc\.gov$ to acceptable aliases isn't one of them. The post was held because it wasn't explicitly addressed To: (or Cc:) the list. I.e. the canonical list posting address, say listname(a)example.com, was not in To: or Cc:. Maybe it was a Bcc: to the list. Maybe the post was addressed to listname(a)mail.example.com. If the former, and you can't convince to poster to explicitly address the list, then you have to turn off require_explicit_destination. If the latter, you can add listname(a)mail.example.com to acceptable aliases. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-23 18:40 Message: Logged In: YES user_id=1123998 Originator: NO So the message is held for implicit destination which means two things: 1) It passed your accept_these_nonmembers test. 2) It was held because Privacy Options...->Recipient filters->require_explicit_destination is Yes and the list posting address or another address in the acceptable_aliases list was not found in any To: or Cc: header of the post. ---------------------------------------------------------------------- Comment By: Michael O (qchrontech) Date: 2007-02-23 18:39 Message: Logged In: YES user_id=1631912 Originator: YES ok so i looked this up. Does this mean I should turn off require_explicit_destination OR should i add ^[^@]+@(.*\.)?nyc\.gov$ to the acceptable_aliases? ---------------------------------------------------------------------- Comment By: Michael O (qchrontech) Date: 2007-02-23 18: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 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 23 Feb '07

23 Feb '07

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: Closed Resolution: Invalid 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 22:14 Message: Logged In: YES user_id=1631912 Originator: YES ^[^@]+@(.*\.)?qchron\.(?=com$|net$).*$ posted in the acceptable_aliases. Will this allow all aliases to the mail list to pass? ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-23 21:48 Message: Logged In: YES user_id=1123998 Originator: NO Re: your followup. You have several choices, but adding ^[^@]+@(.*\.)?nyc\.gov$ to acceptable aliases isn't one of them. The post was held because it wasn't explicitly addressed To: (or Cc:) the list. I.e. the canonical list posting address, say listname(a)example.com, was not in To: or Cc:. Maybe it was a Bcc: to the list. Maybe the post was addressed to listname(a)mail.example.com. If the former, and you can't convince to poster to explicitly address the list, then you have to turn off require_explicit_destination. If the latter, you can add listname(a)mail.example.com to acceptable aliases. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-23 21:40 Message: Logged In: YES user_id=1123998 Originator: NO So the message is held for implicit destination which means two things: 1) It passed your accept_these_nonmembers test. 2) It was held because Privacy Options...->Recipient filters->require_explicit_destination is Yes and the list posting address or another address in the acceptable_aliases list was not found in any To: or Cc: header of the post. ---------------------------------------------------------------------- Comment By: Michael O (qchrontech) Date: 2007-02-23 21:39 Message: Logged In: YES user_id=1631912 Originator: YES ok so i looked this up. Does this mean I should turn off require_explicit_destination OR should i add ^[^@]+@(.*\.)?nyc\.gov$ to the acceptable_aliases? ---------------------------------------------------------------------- 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 23 Feb '07

23 Feb '07

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: Closed Resolution: Invalid 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 18:48 Message: Logged In: YES user_id=1123998 Originator: NO Re: your followup. You have several choices, but adding ^[^@]+@(.*\.)?nyc\.gov$ to acceptable aliases isn't one of them. The post was held because it wasn't explicitly addressed To: (or Cc:) the list. I.e. the canonical list posting address, say listname(a)example.com, was not in To: or Cc:. Maybe it was a Bcc: to the list. Maybe the post was addressed to listname(a)mail.example.com. If the former, and you can't convince to poster to explicitly address the list, then you have to turn off require_explicit_destination. If the latter, you can add listname(a)mail.example.com to acceptable aliases. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-23 18:40 Message: Logged In: YES user_id=1123998 Originator: NO So the message is held for implicit destination which means two things: 1) It passed your accept_these_nonmembers test. 2) It was held because Privacy Options...->Recipient filters->require_explicit_destination is Yes and the list posting address or another address in the acceptable_aliases list was not found in any To: or Cc: header of the post. ---------------------------------------------------------------------- Comment By: Michael O (qchrontech) Date: 2007-02-23 18:39 Message: Logged In: YES user_id=1631912 Originator: YES ok so i looked this up. Does this mean I should turn off require_explicit_destination OR should i add ^[^@]+@(.*\.)?nyc\.gov$ to the acceptable_aliases? ---------------------------------------------------------------------- Comment By: Michael O (qchrontech) Date: 2007-02-23 18: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 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 23 Feb '07

23 Feb '07

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: Closed >Resolution: Invalid 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 18:40 Message: Logged In: YES user_id=1123998 Originator: NO So the message is held for implicit destination which means two things: 1) It passed your accept_these_nonmembers test. 2) It was held because Privacy Options...->Recipient filters->require_explicit_destination is Yes and the list posting address or another address in the acceptable_aliases list was not found in any To: or Cc: header of the post. ---------------------------------------------------------------------- Comment By: Michael O (qchrontech) Date: 2007-02-23 18:39 Message: Logged In: YES user_id=1631912 Originator: YES ok so i looked this up. Does this mean I should turn off require_explicit_destination OR should i add ^[^@]+@(.*\.)?nyc\.gov$ to the acceptable_aliases? ---------------------------------------------------------------------- Comment By: Michael O (qchrontech) Date: 2007-02-23 18: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 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 23 Feb '07

23 Feb '07

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:39 Message: Logged In: YES user_id=1631912 Originator: YES ok so i looked this up. Does this mean I should turn off require_explicit_destination OR should i add ^[^@]+@(.*\.)?nyc\.gov$ to the acceptable_aliases? ---------------------------------------------------------------------- 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 23 Feb '07

23 Feb '07

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 23 Feb '07

23 Feb '07

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 23 Feb '07

23 Feb '07

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 20 Feb '07

20 Feb '07

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 20 Feb '07

20 Feb '07

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 20 Feb '07

20 Feb '07

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 19 Feb '07

19 Feb '07

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 16 Feb '07

16 Feb '07

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 16 Feb '07

16 Feb '07

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 16 Feb '07

16 Feb '07

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

[ mailman-Bugs-1660666 ] syntax error in CheckFixUid.py
by SourceForge.net 15 Feb '07

15 Feb '07

Bugs item #1660666, was opened at 2007-02-15 15:39 Message generated for change (Comment added) made by chris_ress You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1660666&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: Closed Resolution: Fixed Priority: 5 Private: No Submitted By: Christian Reß (chris_ress) Assigned to: Nobody/Anonymous (nobody) Summary: syntax error in CheckFixUid.py Initial Comment: bin/CheckFixUid.py is created by bin/check_perms_grsecurity.py. It has a syntax error that keeps mailman from starting up. Reproducable: always Steps to reproduce: 1. run bin/check_perms_grsecurity.py -f 2. run bin/mailmanctl start The error: NameError: name 'uid' is not defined Traceback (most recent call last): File "/usr/local/mailman/bin/qrunner", line 80, in ? import CheckFixUid File "/usr/local/mailman/bin/CheckFixUid.py", line 6, in ? class CheckFixUid: File "/usr/local/mailman/bin/CheckFixUid.py", line 12, in CheckFixUid if os.geteuid() != uid: A proposed fix is attached. ---------------------------------------------------------------------- >Comment By: Christian Reß (chris_ress) Date: 2007-02-15 21:01 Message: Logged In: YES user_id=1720190 Originator: YES No Problem, thanks for patching it! ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-15 19:52 Message: Logged In: YES user_id=1123998 Originator: NO Never Mind! I was originally looking at my installed Mailman that doesn't include the contrib directory. I see that it is in the contributed software for which the README says: <quote> This directory contains unofficial contributed scripts and extensions to Mailman. They are unsupported by the Mailman developers. If you have questions or problems with them, please contact the contribution author directly. </quote> However, since the patch is so simple and obvious, I'll go ahead and patch it. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-15 19:44 Message: Logged In: YES user_id=1123998 Originator: NO Perhaps I am mistaken. Can you tell me the exact path to where you found check_perms_grsecurity.py in either the Mailman 2.1.9 tarball or SVN? ---------------------------------------------------------------------- Comment By: Christian Reß (chris_ress) Date: 2007-02-15 18:10 Message: Logged In: YES user_id=1720190 Originator: YES Since it is part of the official distribution and is also in you SVN, I thought you'd like to quickly apply a fix to it. Anyway, I'll contact the contributor. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-15 18:05 Message: Logged In: YES user_id=1123998 Originator: NO These are not GNU Mailman scripts. They must be part of some redistribution. Please report this bug to your packager. There's nothing the Mailman project can do about it. ---------------------------------------------------------------------- Comment By: Christian Reß (chris_ress) Date: 2007-02-15 15:40 Message: Logged In: YES user_id=1720190 Originator: YES I forgot: You need to start Mailman as root for the error to occur. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1660666&group_…

1 0

[ mailman-Bugs-1660666 ] syntax error in CheckFixUid.py
by SourceForge.net 15 Feb '07

15 Feb '07

Bugs item #1660666, was opened at 2007-02-15 06:39 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1660666&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: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Christian Reß (chris_ress) Assigned to: Nobody/Anonymous (nobody) Summary: syntax error in CheckFixUid.py Initial Comment: bin/CheckFixUid.py is created by bin/check_perms_grsecurity.py. It has a syntax error that keeps mailman from starting up. Reproducable: always Steps to reproduce: 1. run bin/check_perms_grsecurity.py -f 2. run bin/mailmanctl start The error: NameError: name 'uid' is not defined Traceback (most recent call last): File "/usr/local/mailman/bin/qrunner", line 80, in ? import CheckFixUid File "/usr/local/mailman/bin/CheckFixUid.py", line 6, in ? class CheckFixUid: File "/usr/local/mailman/bin/CheckFixUid.py", line 12, in CheckFixUid if os.geteuid() != uid: A proposed fix is attached. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-02-15 10:52 Message: Logged In: YES user_id=1123998 Originator: NO Never Mind! I was originally looking at my installed Mailman that doesn't include the contrib directory. I see that it is in the contributed software for which the README says: <quote> This directory contains unofficial contributed scripts and extensions to Mailman. They are unsupported by the Mailman developers. If you have questions or problems with them, please contact the contribution author directly. </quote> However, since the patch is so simple and obvious, I'll go ahead and patch it. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-15 10:44 Message: Logged In: YES user_id=1123998 Originator: NO Perhaps I am mistaken. Can you tell me the exact path to where you found check_perms_grsecurity.py in either the Mailman 2.1.9 tarball or SVN? ---------------------------------------------------------------------- Comment By: Christian Reß (chris_ress) Date: 2007-02-15 09:10 Message: Logged In: YES user_id=1720190 Originator: YES Since it is part of the official distribution and is also in you SVN, I thought you'd like to quickly apply a fix to it. Anyway, I'll contact the contributor. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-15 09:05 Message: Logged In: YES user_id=1123998 Originator: NO These are not GNU Mailman scripts. They must be part of some redistribution. Please report this bug to your packager. There's nothing the Mailman project can do about it. ---------------------------------------------------------------------- Comment By: Christian Reß (chris_ress) Date: 2007-02-15 06:40 Message: Logged In: YES user_id=1720190 Originator: YES I forgot: You need to start Mailman as root for the error to occur. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1660666&group_…

1 0

[ mailman-Bugs-1660666 ] syntax error in CheckFixUid.py
by SourceForge.net 15 Feb '07

15 Feb '07

Bugs item #1660666, was opened at 2007-02-15 06:39 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1660666&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: Invalid Priority: 5 Private: No Submitted By: Christian Reß (chris_ress) Assigned to: Nobody/Anonymous (nobody) Summary: syntax error in CheckFixUid.py Initial Comment: bin/CheckFixUid.py is created by bin/check_perms_grsecurity.py. It has a syntax error that keeps mailman from starting up. Reproducable: always Steps to reproduce: 1. run bin/check_perms_grsecurity.py -f 2. run bin/mailmanctl start The error: NameError: name 'uid' is not defined Traceback (most recent call last): File "/usr/local/mailman/bin/qrunner", line 80, in ? import CheckFixUid File "/usr/local/mailman/bin/CheckFixUid.py", line 6, in ? class CheckFixUid: File "/usr/local/mailman/bin/CheckFixUid.py", line 12, in CheckFixUid if os.geteuid() != uid: A proposed fix is attached. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-02-15 10:44 Message: Logged In: YES user_id=1123998 Originator: NO Perhaps I am mistaken. Can you tell me the exact path to where you found check_perms_grsecurity.py in either the Mailman 2.1.9 tarball or SVN? ---------------------------------------------------------------------- Comment By: Christian Reß (chris_ress) Date: 2007-02-15 09:10 Message: Logged In: YES user_id=1720190 Originator: YES Since it is part of the official distribution and is also in you SVN, I thought you'd like to quickly apply a fix to it. Anyway, I'll contact the contributor. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-15 09:05 Message: Logged In: YES user_id=1123998 Originator: NO These are not GNU Mailman scripts. They must be part of some redistribution. Please report this bug to your packager. There's nothing the Mailman project can do about it. ---------------------------------------------------------------------- Comment By: Christian Reß (chris_ress) Date: 2007-02-15 06:40 Message: Logged In: YES user_id=1720190 Originator: YES I forgot: You need to start Mailman as root for the error to occur. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1660666&group_…

1 0

[ mailman-Bugs-1660666 ] syntax error in CheckFixUid.py
by SourceForge.net 15 Feb '07

15 Feb '07

Bugs item #1660666, was opened at 2007-02-15 15:39 Message generated for change (Comment added) made by chris_ress You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1660666&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: Invalid Priority: 5 Private: No Submitted By: Christian Reß (chris_ress) Assigned to: Nobody/Anonymous (nobody) Summary: syntax error in CheckFixUid.py Initial Comment: bin/CheckFixUid.py is created by bin/check_perms_grsecurity.py. It has a syntax error that keeps mailman from starting up. Reproducable: always Steps to reproduce: 1. run bin/check_perms_grsecurity.py -f 2. run bin/mailmanctl start The error: NameError: name 'uid' is not defined Traceback (most recent call last): File "/usr/local/mailman/bin/qrunner", line 80, in ? import CheckFixUid File "/usr/local/mailman/bin/CheckFixUid.py", line 6, in ? class CheckFixUid: File "/usr/local/mailman/bin/CheckFixUid.py", line 12, in CheckFixUid if os.geteuid() != uid: A proposed fix is attached. ---------------------------------------------------------------------- >Comment By: Christian Reß (chris_ress) Date: 2007-02-15 18:10 Message: Logged In: YES user_id=1720190 Originator: YES Since it is part of the official distribution and is also in you SVN, I thought you'd like to quickly apply a fix to it. Anyway, I'll contact the contributor. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-15 18:05 Message: Logged In: YES user_id=1123998 Originator: NO These are not GNU Mailman scripts. They must be part of some redistribution. Please report this bug to your packager. There's nothing the Mailman project can do about it. ---------------------------------------------------------------------- Comment By: Christian Reß (chris_ress) Date: 2007-02-15 15:40 Message: Logged In: YES user_id=1720190 Originator: YES I forgot: You need to start Mailman as root for the error to occur. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1660666&group_…

1 0

[ mailman-Bugs-1660666 ] syntax error in CheckFixUid.py
by SourceForge.net 15 Feb '07

15 Feb '07

Bugs item #1660666, was opened at 2007-02-15 06:39 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1660666&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: Pending >Resolution: Invalid Priority: 5 Private: No Submitted By: Christian Reß (chris_ress) Assigned to: Nobody/Anonymous (nobody) Summary: syntax error in CheckFixUid.py Initial Comment: bin/CheckFixUid.py is created by bin/check_perms_grsecurity.py. It has a syntax error that keeps mailman from starting up. Reproducable: always Steps to reproduce: 1. run bin/check_perms_grsecurity.py -f 2. run bin/mailmanctl start The error: NameError: name 'uid' is not defined Traceback (most recent call last): File "/usr/local/mailman/bin/qrunner", line 80, in ? import CheckFixUid File "/usr/local/mailman/bin/CheckFixUid.py", line 6, in ? class CheckFixUid: File "/usr/local/mailman/bin/CheckFixUid.py", line 12, in CheckFixUid if os.geteuid() != uid: A proposed fix is attached. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-02-15 09:05 Message: Logged In: YES user_id=1123998 Originator: NO These are not GNU Mailman scripts. They must be part of some redistribution. Please report this bug to your packager. There's nothing the Mailman project can do about it. ---------------------------------------------------------------------- Comment By: Christian Reß (chris_ress) Date: 2007-02-15 06:40 Message: Logged In: YES user_id=1720190 Originator: YES I forgot: You need to start Mailman as root for the error to occur. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1660666&group_…

1 0

[ mailman-Bugs-1660666 ] syntax error in CheckFixUid.py
by SourceForge.net 15 Feb '07

15 Feb '07

Bugs item #1660666, was opened at 2007-02-15 15:39 Message generated for change (Comment added) made by chris_ress You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1660666&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: Christian Reß (chris_ress) Assigned to: Nobody/Anonymous (nobody) Summary: syntax error in CheckFixUid.py Initial Comment: bin/CheckFixUid.py is created by bin/check_perms_grsecurity.py. It has a syntax error that keeps mailman from starting up. Reproducable: always Steps to reproduce: 1. run bin/check_perms_grsecurity.py -f 2. run bin/mailmanctl start The error: NameError: name 'uid' is not defined Traceback (most recent call last): File "/usr/local/mailman/bin/qrunner", line 80, in ? import CheckFixUid File "/usr/local/mailman/bin/CheckFixUid.py", line 6, in ? class CheckFixUid: File "/usr/local/mailman/bin/CheckFixUid.py", line 12, in CheckFixUid if os.geteuid() != uid: A proposed fix is attached. ---------------------------------------------------------------------- >Comment By: Christian Reß (chris_ress) Date: 2007-02-15 15:40 Message: Logged In: YES user_id=1720190 Originator: YES I forgot: You need to start Mailman as root for the error to occur. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1660666&group_…

1 0

[ mailman-Bugs-1660666 ] syntax error in CheckFixUid.py
by SourceForge.net 15 Feb '07

15 Feb '07

Bugs item #1660666, was opened at 2007-02-15 15:39 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=1660666&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: Christian Reß (chris_ress) Assigned to: Nobody/Anonymous (nobody) Summary: syntax error in CheckFixUid.py Initial Comment: bin/CheckFixUid.py is created by bin/check_perms_grsecurity.py. It has a syntax error that keeps mailman from starting up. Reproducable: always Steps to reproduce: 1. run bin/check_perms_grsecurity.py -f 2. run bin/mailmanctl start The error: NameError: name 'uid' is not defined Traceback (most recent call last): File "/usr/local/mailman/bin/qrunner", line 80, in ? import CheckFixUid File "/usr/local/mailman/bin/CheckFixUid.py", line 6, in ? class CheckFixUid: File "/usr/local/mailman/bin/CheckFixUid.py", line 12, in CheckFixUid if os.geteuid() != uid: A proposed fix is attached. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1660666&group_…

1 0

[ mailman-Bugs-1658920 ] charset proble,
by SourceForge.net 13 Feb '07

13 Feb '07

Bugs item #1658920, was opened at 2007-02-13 05:06 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1658920&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: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: dudeua (dudeua) Assigned to: Mark Sapiro (msapiro) Summary: charset proble, Initial Comment: Hello, I need help. I have mailman 2.1.9 .... if I receive mail in charset, different that koi8, than mailman in admins area shows this mail in "quoted-printable" charset ... But after approving this email, via web-interface email shows with correct charset. How to fix charset? ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-02-13 10:53 Message: Logged In: YES user_id=1123998 Originator: NO The screenshot is unnecessary. I understood exactly what the issue was from your original description. I know you only see the problem in the "message excerpt" in the admindb message detail. I tried to explain that the reason for this is that this excerpt is not decoded. It would be possible to patch Mailman/Cgi/admindb.py with the attached patch to decode this "message excerpt" before displaying it, but then you would have the issue that the characters in the box in your screenshot would be Windows CP1251 characters which would probably still be garbled when displayed in the character set of the rest of the page. Also, my suggestion to set admin_immed_notify to 1 was not intended to 'correct' this display. It causes this message to be also sent to you in an email so that if it is necessary for you to see the message text in order to decide what action to take with the message, you can see the text in the email notice. File Added: admindb.patch.txt ---------------------------------------------------------------------- Comment By: dudeua (dudeua) Date: 2007-02-13 08:55 Message: Logged In: YES user_id=1718234 Originator: YES set admin_immed_notify at /mailman/bun/config ? It already setted to 1; Pleasee see attacged screenshot. I can't use MUA (mail agent), because I meet problem with encoding only at admin area. Thanks for help. File Added: ggg.jpg ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-13 08:36 Message: Logged In: YES user_id=1123998 Originator: NO Quoted-printable is not a character set. It is an encoding. That is, it is a way of representing data which contains non-printable, us-ascii characters using only the us-ascii character set as required by RFC2822 for email messages. The issue here is that encoded message bodies are not decoded for display in the admindb message detail. This may change in the future, but then there _will_ be character set and content-type issues. These are more complicated as in general, different message parts may have different character sets and may not even be text. Currently, if you really need to see the decoded text, you need to set admin_immed_notify to Yes so you get an email notice of the held message and use an MUA (mail client) that shows you the decoded message in the notice. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1658920&group_…

1 0

[ mailman-Bugs-1658920 ] charset proble,
by SourceForge.net 13 Feb '07

13 Feb '07

Bugs item #1658920, was opened at 2007-02-13 13:06 Message generated for change (Comment added) made by dudeua You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1658920&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: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: dudeua (dudeua) Assigned to: Mark Sapiro (msapiro) Summary: charset proble, Initial Comment: Hello, I need help. I have mailman 2.1.9 .... if I receive mail in charset, different that koi8, than mailman in admins area shows this mail in "quoted-printable" charset ... But after approving this email, via web-interface email shows with correct charset. How to fix charset? ---------------------------------------------------------------------- >Comment By: dudeua (dudeua) Date: 2007-02-13 16:55 Message: Logged In: YES user_id=1718234 Originator: YES set admin_immed_notify at /mailman/bun/config ? It already setted to 1; Pleasee see attacged screenshot. I can't use MUA (mail agent), because I meet problem with encoding only at admin area. Thanks for help. File Added: ggg.jpg ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-13 16:36 Message: Logged In: YES user_id=1123998 Originator: NO Quoted-printable is not a character set. It is an encoding. That is, it is a way of representing data which contains non-printable, us-ascii characters using only the us-ascii character set as required by RFC2822 for email messages. The issue here is that encoded message bodies are not decoded for display in the admindb message detail. This may change in the future, but then there _will_ be character set and content-type issues. These are more complicated as in general, different message parts may have different character sets and may not even be text. Currently, if you really need to see the decoded text, you need to set admin_immed_notify to Yes so you get an email notice of the held message and use an MUA (mail client) that shows you the decoded message in the notice. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1658920&group_…

1 0

[ mailman-Bugs-1658920 ] charset proble,
by SourceForge.net 13 Feb '07

13 Feb '07

Bugs item #1658920, was opened at 2007-02-13 05:06 Message generated for change (Settings changed) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1658920&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: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: dudeua (dudeua) >Assigned to: Mark Sapiro (msapiro) Summary: charset proble, Initial Comment: Hello, I need help. I have mailman 2.1.9 .... if I receive mail in charset, different that koi8, than mailman in admins area shows this mail in "quoted-printable" charset ... But after approving this email, via web-interface email shows with correct charset. How to fix charset? ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-02-13 08:36 Message: Logged In: YES user_id=1123998 Originator: NO Quoted-printable is not a character set. It is an encoding. That is, it is a way of representing data which contains non-printable, us-ascii characters using only the us-ascii character set as required by RFC2822 for email messages. The issue here is that encoded message bodies are not decoded for display in the admindb message detail. This may change in the future, but then there _will_ be character set and content-type issues. These are more complicated as in general, different message parts may have different character sets and may not even be text. Currently, if you really need to see the decoded text, you need to set admin_immed_notify to Yes so you get an email notice of the held message and use an MUA (mail client) that shows you the decoded message in the notice. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1658920&group_…

1 0

[ mailman-Bugs-1658920 ] charset proble,
by SourceForge.net 13 Feb '07

13 Feb '07

Bugs item #1658920, was opened at 2007-02-13 13:06 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=1658920&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: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: dudeua (dudeua) Assigned to: Nobody/Anonymous (nobody) Summary: charset proble, Initial Comment: Hello, I need help. I have mailman 2.1.9 .... if I receive mail in charset, different that koi8, than mailman in admins area shows this mail in "quoted-printable" charset ... But after approving this email, via web-interface email shows with correct charset. How to fix charset? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1658920&group_…

1 0

[ mailman-Feature Requests-1657458 ] feature request: batch deletion of subscription requests
by SourceForge.net 12 Feb '07

12 Feb '07

Feature Requests item #1657458, was opened at 2007-02-11 18:55 Message generated for change (Comment added) made by tarheelcoxn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1657458&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: Cristobal M. Palmer (tarheelcoxn) Assigned to: Nobody/Anonymous (nobody) Summary: feature request: batch deletion of subscription requests Initial Comment: please add a tick box for "delete all pending subscription requests marked /defer/" to the admindb page. It's great that I can scan a page and delete all pending messages that are spam, but several lists I deal with are getting a lot of spam in the form of subscription requests, and making those lists invisible is not an option and wouldn't help at this point. ---------------------------------------------------------------------- >Comment By: Cristobal M. Palmer (tarheelcoxn) Date: 2007-02-12 05:57 Message: Logged In: YES user_id=1297390 Originator: YES The latter (a single box that discards all) would be fine by me, but perhaps somebody with better UI sense than myself should make that call. I would say that regardless of which is the case, it should be *very* clear what exactly is getting discarded. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-12 05:28 Message: Logged In: YES user_id=1123998 Originator: NO Re: the comment: Are the bodies of subscription requests visible in recent Mailman? No, they are not. Re: the original request. Do you specifically want a second tick box, or would a single box to "Discard all messages and requests marked _Defer_" be just as good? I can see advantages to separating the discard functions, but OTOH, I see advantages to keeping the page simpler with a single box. ---------------------------------------------------------------------- Comment By: Stephen J. Turnbull (yaseppochi) Date: 2007-02-12 04:57 Message: Logged In: YES user_id=88738 Originator: NO Are the bodies of subscription requests visible in recent Mailman (I'm currently using 2.1.5)? If not, it would be helpful to make them so. My lists don't get so much spam to the subscription address, but it's difficult to determine when somebody has a peculiar address and when it's autogenerated by a spammer sometimes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1657458&group_…

1 0

[ mailman-Feature Requests-1657458 ] feature request: batch deletion of subscription requests
by SourceForge.net 12 Feb '07

12 Feb '07

Feature Requests item #1657458, was opened at 2007-02-11 10:55 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1657458&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: Cristobal M. Palmer (tarheelcoxn) Assigned to: Nobody/Anonymous (nobody) Summary: feature request: batch deletion of subscription requests Initial Comment: please add a tick box for "delete all pending subscription requests marked /defer/" to the admindb page. It's great that I can scan a page and delete all pending messages that are spam, but several lists I deal with are getting a lot of spam in the form of subscription requests, and making those lists invisible is not an option and wouldn't help at this point. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-02-11 21:28 Message: Logged In: YES user_id=1123998 Originator: NO Re: the comment: Are the bodies of subscription requests visible in recent Mailman? No, they are not. Re: the original request. Do you specifically want a second tick box, or would a single box to "Discard all messages and requests marked _Defer_" be just as good? I can see advantages to separating the discard functions, but OTOH, I see advantages to keeping the page simpler with a single box. ---------------------------------------------------------------------- Comment By: Stephen J. Turnbull (yaseppochi) Date: 2007-02-11 20:57 Message: Logged In: YES user_id=88738 Originator: NO Are the bodies of subscription requests visible in recent Mailman (I'm currently using 2.1.5)? If not, it would be helpful to make them so. My lists don't get so much spam to the subscription address, but it's difficult to determine when somebody has a peculiar address and when it's autogenerated by a spammer sometimes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1657458&group_…

1 0

[ mailman-Feature Requests-1657458 ] feature request: batch deletion of subscription requests
by SourceForge.net 11 Feb '07

11 Feb '07

Feature Requests item #1657458, was opened at 2007-02-12 03:55 Message generated for change (Comment added) made by yaseppochi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1657458&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: Cristobal M. Palmer (tarheelcoxn) Assigned to: Nobody/Anonymous (nobody) Summary: feature request: batch deletion of subscription requests Initial Comment: please add a tick box for "delete all pending subscription requests marked /defer/" to the admindb page. It's great that I can scan a page and delete all pending messages that are spam, but several lists I deal with are getting a lot of spam in the form of subscription requests, and making those lists invisible is not an option and wouldn't help at this point. ---------------------------------------------------------------------- Comment By: Stephen J. Turnbull (yaseppochi) Date: 2007-02-12 13:57 Message: Logged In: YES user_id=88738 Originator: NO Are the bodies of subscription requests visible in recent Mailman (I'm currently using 2.1.5)? If not, it would be helpful to make them so. My lists don't get so much spam to the subscription address, but it's difficult to determine when somebody has a peculiar address and when it's autogenerated by a spammer sometimes. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1657458&group_…

1 0

[ mailman-Feature Requests-1657458 ] feature request: batch deletion of subscription requests
by SourceForge.net 11 Feb '07

11 Feb '07

Feature Requests item #1657458, was opened at 2007-02-11 18:55 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=1657458&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: Cristobal M. Palmer (tarheelcoxn) Assigned to: Nobody/Anonymous (nobody) Summary: feature request: batch deletion of subscription requests Initial Comment: please add a tick box for "delete all pending subscription requests marked /defer/" to the admindb page. It's great that I can scan a page and delete all pending messages that are spam, but several lists I deal with are getting a lot of spam in the form of subscription requests, and making those lists invisible is not an option and wouldn't help at this point. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1657458&group_…

1 0

[ mailman-Bugs-1656289 ] Unable to process the "in" folder: out of memory
by SourceForge.net 09 Feb '07

09 Feb '07

Bugs item #1656289, was opened at 2007-02-09 13:14 Message generated for change (Comment added) made by zhenxjell You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1656289&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: 2.1 (stable) >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Paul Laudanski (zhenxjell) Assigned to: Nobody/Anonymous (nobody) Summary: Unable to process the "in" folder: out of memory Initial Comment: The files in mailman/qfiles/in are not being processed. Rather the following errors are displaying in the error log file. Its the same error over and over in version 2.1.9. Does this error effect the processing of the "in" folder? Currently 161 files are in there. The retry and out folders are empty. Feb 08 11:13:03 2007 (16016) Uncaught runner exception: out of memory Feb 08 11:13:06 2007 (16016) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 112, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 170, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SpamDetect.py", line 111, in process g.flatten(p) File "/usr/local/mailman/pythonlib/email/Generator.py", line 101, in flatten self._write(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 129, in _write self._dispatch(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 155, in _dispatch meth(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 258, in _handle_multipart print >> self._fp, '\n--' + boundary + '--', MemoryError: out of memory Feb 08 11:13:07 2007 qrunner(16016): Traceback (most recent call last): Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/bin/qrunner", line 278, in ? Feb 08 11:13:07 2007 qrunner(16016): main() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/bin/qrunner", line 238, in main Feb 08 11:13:07 2007 qrunner(16016): qrunner.run() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 71, in run Feb 08 11:13:07 2007 qrunner(16016): filecnt = self._oneloop() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 124, in _oneloop Feb 08 11:13:07 2007 qrunner(16016): new_filebase = self._shunt.enqueue(msg, msgdata) Feb 08 11:13:08 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 106, in enqueue Feb 08 11:13:08 2007 qrunner(16016): msgsave = cPickle.dumps(_msg, protocol) Feb 08 11:13:08 2007 qrunner(16016): MemoryError : out of memory ---------------------------------------------------------------------- >Comment By: Paul Laudanski (zhenxjell) Date: 2007-02-09 19:19 Message: Logged In: YES user_id=1329578 Originator: YES Bingo, that did the trick. There was a file immensely large, that once removed and restarted, mailman worked. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-02-09 14:52 Message: Logged In: YES user_id=1123998 Originator: NO This is not a Mailman bug per se. IncomingRunner is processing a message. It calls the process() function in the SpamDetect handler which encounters the MemoryError exception which occurs when some Python process tries to allocate more memory and is denied by the OS. Normally, the offending message queue entry would be shunted and processing would continue with the next message, but the attempt to shunt the message also hits the MemoryError. I suggest first trying 'bin/mailmanctl restart' if you haven't done so in case there is a memory leak somewhere in Python. If that doesn't fix it, I think the first file in qfiles/in is probably very large and contains a very large message which is causing the problem. Try 'bin/mailmanctl stop', then move that file aside and do 'bin/mailmanctl start' and see if that resolves the issue. If it does, you may be able to examine the file with bin/dumpdb or bin/show_qfiles. If you need further help, please follow up on mailman-users(a)python.org. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1656289&group_…

1 0

[ mailman-Bugs-1656289 ] Unable to process the "in" folder: out of memory
by SourceForge.net 09 Feb '07

09 Feb '07

Bugs item #1656289, was opened at 2007-02-09 10:14 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1656289&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: Pending Resolution: None Priority: 5 Private: No Submitted By: Paul Laudanski (zhenxjell) Assigned to: Nobody/Anonymous (nobody) Summary: Unable to process the "in" folder: out of memory Initial Comment: The files in mailman/qfiles/in are not being processed. Rather the following errors are displaying in the error log file. Its the same error over and over in version 2.1.9. Does this error effect the processing of the "in" folder? Currently 161 files are in there. The retry and out folders are empty. Feb 08 11:13:03 2007 (16016) Uncaught runner exception: out of memory Feb 08 11:13:06 2007 (16016) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 112, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 170, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SpamDetect.py", line 111, in process g.flatten(p) File "/usr/local/mailman/pythonlib/email/Generator.py", line 101, in flatten self._write(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 129, in _write self._dispatch(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 155, in _dispatch meth(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 258, in _handle_multipart print >> self._fp, '\n--' + boundary + '--', MemoryError: out of memory Feb 08 11:13:07 2007 qrunner(16016): Traceback (most recent call last): Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/bin/qrunner", line 278, in ? Feb 08 11:13:07 2007 qrunner(16016): main() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/bin/qrunner", line 238, in main Feb 08 11:13:07 2007 qrunner(16016): qrunner.run() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 71, in run Feb 08 11:13:07 2007 qrunner(16016): filecnt = self._oneloop() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 124, in _oneloop Feb 08 11:13:07 2007 qrunner(16016): new_filebase = self._shunt.enqueue(msg, msgdata) Feb 08 11:13:08 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 106, in enqueue Feb 08 11:13:08 2007 qrunner(16016): msgsave = cPickle.dumps(_msg, protocol) Feb 08 11:13:08 2007 qrunner(16016): MemoryError : out of memory ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-02-09 11:52 Message: Logged In: YES user_id=1123998 Originator: NO This is not a Mailman bug per se. IncomingRunner is processing a message. It calls the process() function in the SpamDetect handler which encounters the MemoryError exception which occurs when some Python process tries to allocate more memory and is denied by the OS. Normally, the offending message queue entry would be shunted and processing would continue with the next message, but the attempt to shunt the message also hits the MemoryError. I suggest first trying 'bin/mailmanctl restart' if you haven't done so in case there is a memory leak somewhere in Python. If that doesn't fix it, I think the first file in qfiles/in is probably very large and contains a very large message which is causing the problem. Try 'bin/mailmanctl stop', then move that file aside and do 'bin/mailmanctl start' and see if that resolves the issue. If it does, you may be able to examine the file with bin/dumpdb or bin/show_qfiles. If you need further help, please follow up on mailman-users(a)python.org. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1656289&group_…

1 0

[ mailman-Bugs-1656289 ] Unable to process the "in" folder: out of memory
by SourceForge.net 09 Feb '07

09 Feb '07

Bugs item #1656289, was opened at 2007-02-09 13:14 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=1656289&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: Paul Laudanski (zhenxjell) Assigned to: Nobody/Anonymous (nobody) Summary: Unable to process the "in" folder: out of memory Initial Comment: The files in mailman/qfiles/in are not being processed. Rather the following errors are displaying in the error log file. Its the same error over and over in version 2.1.9. Does this error effect the processing of the "in" folder? Currently 161 files are in there. The retry and out folders are empty. Feb 08 11:13:03 2007 (16016) Uncaught runner exception: out of memory Feb 08 11:13:06 2007 (16016) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 112, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 170, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File "/usr/local/mailman/Mailman/Handlers/SpamDetect.py", line 111, in process g.flatten(p) File "/usr/local/mailman/pythonlib/email/Generator.py", line 101, in flatten self._write(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 129, in _write self._dispatch(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 155, in _dispatch meth(msg) File "/usr/local/mailman/pythonlib/email/Generator.py", line 258, in _handle_multipart print >> self._fp, '\n--' + boundary + '--', MemoryError: out of memory Feb 08 11:13:07 2007 qrunner(16016): Traceback (most recent call last): Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/bin/qrunner", line 278, in ? Feb 08 11:13:07 2007 qrunner(16016): main() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/bin/qrunner", line 238, in main Feb 08 11:13:07 2007 qrunner(16016): qrunner.run() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 71, in run Feb 08 11:13:07 2007 qrunner(16016): filecnt = self._oneloop() Feb 08 11:13:07 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 124, in _oneloop Feb 08 11:13:07 2007 qrunner(16016): new_filebase = self._shunt.enqueue(msg, msgdata) Feb 08 11:13:08 2007 qrunner(16016): File "/usr/local/mailman/Mailman/Queue/Switchboard.py", line 106, in enqueue Feb 08 11:13:08 2007 qrunner(16016): msgsave = cPickle.dumps(_msg, protocol) Feb 08 11:13:08 2007 qrunner(16016): MemoryError : out of memory ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1656289&group_…

1 0

[ mailman-Feature Requests-1656269 ] code analysis, flaw detection
by SourceForge.net 09 Feb '07

09 Feb '07

Feature Requests item #1656269, was opened at 2007-02-09 18:36 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=1656269&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: Markus Elfring (elfring) Assigned to: Nobody/Anonymous (nobody) Summary: code analysis, flaw detection Initial Comment: Would you like to use the approach "http://en.wikipedia.org/wiki/Static_code_analysis"? Would you like to integrate the tool "http://splint.org/" into your build process? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1656269&group_…

1 0

[ mailman-Patches-1656171 ] list_members moderation options
by SourceForge.net 09 Feb '07

09 Feb '07

Patches item #1656171, was opened at 2007-02-09 15:43 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=1656171&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: list administration Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Anna (annalangley) Assigned to: Nobody/Anonymous (nobody) Summary: list_members moderation options Initial Comment: This patch modifies the list_members command so that in addition to the other options it can filter the addresses listed according to whether the addresses have the "Moderated" bit set (or not). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1656171&group_…

1 0

[ mailman-Bugs-1655187 ] Check return codes everywhere
by SourceForge.net 08 Feb '07

08 Feb '07

Bugs item #1655187, was opened at 2007-02-08 14:47 Message generated for change (Settings changed) made by elfring You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1655187&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: Markus Elfring (elfring) >Assigned to: Barry A. Warsaw (bwarsaw) Summary: Check return codes everywhere Initial Comment: Some checks for return codes are missing. Examples: Would you like to add more error handling for return values from "printf" like in the function "fatal" and from "malloc" in the function "run_script"? http://mailman.svn.sourceforge.net/viewvc/mailman/trunk/mailman/src/common.… ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1655187&group_…

1 0

[ mailman-Bugs-1655187 ] Check return codes everywhere
by SourceForge.net 08 Feb '07

08 Feb '07

Bugs item #1655187, was opened at 2007-02-08 14:47 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=1655187&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: Markus Elfring (elfring) Assigned to: Nobody/Anonymous (nobody) Summary: Check return codes everywhere Initial Comment: Some checks for return codes are missing. Examples: Would you like to add more error handling for return values from "printf" like in the function "fatal" and from "malloc" in the function "run_script"? http://mailman.svn.sourceforge.net/viewvc/mailman/trunk/mailman/src/common.… ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1655187&group_…

1 0

[ mailman-Feature Requests-1650065 ] Search feature
by SourceForge.net 01 Feb '07

01 Feb '07

Feature Requests item #1650065, was opened at 2007-02-01 10:45 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1650065&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: Charles-Andr� Landemaine (charles-andre) Assigned to: Nobody/Anonymous (nobody) Summary: Search feature Initial Comment: This is a feature request. I think it would be invaluable to have a search feature like the Google Groups have. This would bring Mailman head-to-head with Google Groups. Thanks. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-02-01 12:18 Message: Logged In: YES user_id=1123998 Originator: NO The submitter wrote: > This is a feature request. So I'm moving it to feature requests. And we agree that Mailman should have a built in archive search. We just haven't figured out how to package it. Also, see <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq01.011.htp> for information on integrating Namazu and htdig with Mailman. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1650065&group_…

1 0

[ mailman-Bugs-1650065 ] Search feature
by SourceForge.net 01 Feb '07

01 Feb '07

Bugs item #1650065, was opened at 2007-02-01 16:45 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=1650065&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: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Charles-Andr� Landemaine (charles-andre) Assigned to: Nobody/Anonymous (nobody) Summary: Search feature Initial Comment: This is a feature request. I think it would be invaluable to have a search feature like the Google Groups have. This would bring Mailman head-to-head with Google Groups. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1650065&group_…

1 0