Mailman-coders February 2006

mailman-coders@python.org

1 participants
42 discussions

[ mailman-Bugs-1432090 ] Emails not entered in the filter rules very well

by SourceForge.net

Bugs item #1432090, was opened at 2006-02-15 03:14 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1432090&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: Closed Resolution: Invalid Priority: 2 Submitted By: gw- (gw-) Assigned to: Nobody/Anonymous (nobody) Summary: Emails not entered in the filter rules very well Initial Comment: When accepting an email from a non-subscriber (in a closed mailing list) and selecting the option that the sender should be added to the filter list of allowed senders - this is not done very well, because it adds a plain string representation of the email address, not an regular expression (as which everything in that filter-field is interpreted). (mailman from Debian-i386, 2.1.5-8) ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-02-15 08:31 Message: Logged In: YES user_id=1123998 I can't read the Slovene translation, but it may be an accurate rendition of the English which is a bit ambiguous. It says: "In the text boxes below, add one address per line; start the line with a ^ character to designate a Python regular expression. When entering backslashes, do so as if you were using Python raw strings (i.e. you generally just use a single backslash)." It means "you may start the line ...". The next paragraph says: "Note that non-regexp matches are always done first." which implies you don't need regexps. The 'details' for these say: "Add member addresses one per line; start the line with a ^ character to designate a regular expression match." Perhaps these should say "optionally start the line ..." or something similar. ---------------------------------------------------------------------- Comment By: gw- (gw-) Date: 2006-02-15 07:58 Message: Logged In: YES user_id=1334052 Oh, thanks for the explanation. Than this means that the Slovene translation is invalid. The current: "SporoÄila s katerega od teh naslovov bodo samodejno odobrena, brez dodatne modifikacije. Dodajte naslove Älanov, vsakega v svojo vrstico; ki jo zaÄnete z znakom ^, ki predstavlja regularni izraz za iskanje ujemanj." should be replaced with: "SporoÄila prejeta s katerega od teh naslovov bodo samodejno odobrena, brez dodatne modifikacije. Naslove Älanov dodajte vsakega v svojo vrstico. Äe Å¾elite pri tem uporabljati regularne izraze za iskanje ujemanj, morate vrstico zaÄeti z ^." ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-02-15 07:21 Message: Logged In: YES user_id=1123998 It works as designed and as it should. Entries in *_these_nonmembers are only interpreted as regular expressions if they begin with '^'. Anything else is an exact plain string match (case insensitive). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1432090&group_…

15 years, 4 months

[ mailman-Bugs-1432090 ] Emails not entered in the filter rules very well

by SourceForge.net

Bugs item #1432090, was opened at 2006-02-15 12:14 Message generated for change (Comment added) made by gw- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1432090&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: Closed Resolution: Invalid Priority: 2 Submitted By: gw- (gw-) Assigned to: Nobody/Anonymous (nobody) Summary: Emails not entered in the filter rules very well Initial Comment: When accepting an email from a non-subscriber (in a closed mailing list) and selecting the option that the sender should be added to the filter list of allowed senders - this is not done very well, because it adds a plain string representation of the email address, not an regular expression (as which everything in that filter-field is interpreted). (mailman from Debian-i386, 2.1.5-8) ---------------------------------------------------------------------- >Comment By: gw- (gw-) Date: 2006-02-15 16:58 Message: Logged In: YES user_id=1334052 Oh, thanks for the explanation. Than this means that the Slovene translation is invalid. The current: "SporoÄila s katerega od teh naslovov bodo samodejno odobrena, brez dodatne modifikacije. Dodajte naslove Älanov, vsakega v svojo vrstico; ki jo zaÄnete z znakom ^, ki predstavlja regularni izraz za iskanje ujemanj." should be replaced with: "SporoÄila prejeta s katerega od teh naslovov bodo samodejno odobrena, brez dodatne modifikacije. Naslove Älanov dodajte vsakega v svojo vrstico. Äe Å¾elite pri tem uporabljati regularne izraze za iskanje ujemanj, morate vrstico zaÄeti z ^." ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-02-15 16:21 Message: Logged In: YES user_id=1123998 It works as designed and as it should. Entries in *_these_nonmembers are only interpreted as regular expressions if they begin with '^'. Anything else is an exact plain string match (case insensitive). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1432090&group_…

15 years, 4 months

[ mailman-Bugs-1432090 ] Emails not entered in the filter rules very well

by SourceForge.net

Bugs item #1432090, was opened at 2006-02-15 03:14 Message generated for change (Settings changed) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1432090&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: Closed >Resolution: Invalid Priority: 2 Submitted By: gw- (gw-) Assigned to: Nobody/Anonymous (nobody) Summary: Emails not entered in the filter rules very well Initial Comment: When accepting an email from a non-subscriber (in a closed mailing list) and selecting the option that the sender should be added to the filter list of allowed senders - this is not done very well, because it adds a plain string representation of the email address, not an regular expression (as which everything in that filter-field is interpreted). (mailman from Debian-i386, 2.1.5-8) ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-02-15 07:21 Message: Logged In: YES user_id=1123998 It works as designed and as it should. Entries in *_these_nonmembers are only interpreted as regular expressions if they begin with '^'. Anything else is an exact plain string match (case insensitive). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1432090&group_…

15 years, 4 months

[ mailman-Bugs-1432090 ] Emails not entered in the filter rules very well

by SourceForge.net

Bugs item #1432090, was opened at 2006-02-15 12:14 Message generated for change (Settings changed) made by gw- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1432090&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: 2 Submitted By: gw- (gw-) Assigned to: Nobody/Anonymous (nobody) Summary: Emails not entered in the filter rules very well Initial Comment: When accepting an email from a non-subscriber (in a closed mailing list) and selecting the option that the sender should be added to the filter list of allowed senders - this is not done very well, because it adds a plain string representation of the email address, not an regular expression (as which everything in that filter-field is interpreted). (mailman from Debian-i386, 2.1.5-8) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1432090&group_…

15 years, 4 months

[ mailman-Bugs-1432090 ] Emails not entered in the filter rules very well

by SourceForge.net

Bugs item #1432090, was opened at 2006-02-15 12: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=1432090&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 Submitted By: gw- (gw-) Assigned to: Nobody/Anonymous (nobody) Summary: Emails not entered in the filter rules very well Initial Comment: When accepting an email from a non-subscriber (in a closed mailing list) and selecting the option that the sender should be added to the filter list of allowed senders - this is not done very well, because it adds a plain string representation of the email address, not an regular expression (as which everything in that filter-field is interpreted). (mailman from Debian-i386, 2.1.5-8) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1432090&group_…

15 years, 4 months

[ mailman-Bugs-1430919 ] edithtml.py missing 'import re' (version 2.1.7)

by SourceForge.net

Bugs item #1430919, was opened at 2006-02-13 14:43 Message generated for change (Comment added) made by sydelko You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1430919&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: Closed Resolution: Duplicate Priority: 5 Submitted By: Andrew Sydelko (sydelko) Assigned to: Nobody/Anonymous (nobody) Summary: edithtml.py missing 'import re' (version 2.1.7) Initial Comment: Line 160 of .../Mailman/Cgi/edithtml.py calls the re module which is never imported. Adding 'import re' at the top of the file makes it work. This is with version 2.1.7 of mailman. --andy. ---------------------------------------------------------------------- >Comment By: Andrew Sydelko (sydelko) Date: 2006-02-13 14:47 Message: Logged In: YES user_id=290934 duplicate ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1430919&group_…

15 years, 4 months

[ mailman-Bugs-1430919 ] edithtml.py missing 'import re' (version 2.1.7)

by SourceForge.net

Bugs item #1430919, was opened at 2006-02-13 14:43 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1430919&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 Submitted By: Andrew Sydelko (sydelko) Assigned to: Nobody/Anonymous (nobody) Summary: edithtml.py missing 'import re' (version 2.1.7) Initial Comment: Line 160 of .../Mailman/Cgi/edithtml.py calls the re module which is never imported. Adding 'import re' at the top of the file makes it work. This is with version 2.1.7 of mailman. --andy. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1430919&group_…

15 years, 4 months

[ mailman-Bugs-1430236 ] bin/arch fails with TypeError

by SourceForge.net

Bugs item #1430236, was opened at 2006-02-12 19:02 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=1430236&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 Submitted By: Andreas Thienemann (ixsnet) Assigned to: Nobody/Anonymous (nobody) Summary: bin/arch fails with TypeError Initial Comment: [root@bender mailman]# bin/arch -s 15965 -e 15965 bawue-net-admin archives/private/bawue-net-admin.mbox/bawue-net-admin.mbox Pickling archive state into /opt/mailman-2.1.7/archives/private/bawue-net-admin/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 "/opt/mailman-2.1.7/Mailman/Archiver/pipermail.py", line 569, in processUnixMailbox m = mbox.next() File "/usr/lib/python2.2/mailbox.py", line 34, in next return self.factory(_Subfile(self.fp, start, stop)) File "/opt/mailman-2.1.7/Mailman/Mailbox.py", line 89, in scrubber return mailbox.scrub(msg) File "/opt/mailman-2.1.7/Mailman/Mailbox.py", line 109, in scrub return self._scrubber(self._mlist, msg) File "/opt/mailman-2.1.7/Mailman/Handlers/Scrubber.py", line 352, in process t = part.get_payload(decode=decode) File "/opt/mailman-2.1.7/pythonlib/email/Message.py", line 213, in get_payload return Utils._qdecode(payload) File "/usr/lib/python2.2/quopri.py", line 161, in decodestring return a2b_qp(s, header = header) TypeError: argument 1 must be string or read-only buffer, not None ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1430236&group_…

15 years, 4 months

[ mailman-Bugs-1430209 ] Detatch from email

by SourceForge.net

Bugs item #1430209, was opened at 2006-02-12 13:17 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=1430209&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 Submitted By: Full Decent (fulldecent) Assigned to: Nobody/Anonymous (nobody) Summary: Detatch from email Initial Comment: Please allow posting from the website. And downloading content via RSS. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1430209&group_…

15 years, 4 months

[ mailman-Bugs-1428410 ] admin login and logout screens lack favicon

by SourceForge.net

Bugs item #1428410, was opened at 2006-02-09 10:51 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=1428410&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 Submitted By: Josh Kelley (yeshua) Assigned to: Nobody/Anonymous (nobody) Summary: admin login and logout screens lack favicon Initial Comment: The admin login and logout screens lack a favicon. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1428410&group_…

15 years, 4 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders February 2006