[Mailman-Developers] [ mailman-Bugs-598844 ] BASE64 attachmentsbarfing
Bugs item #598844, was opened at 2002-08-22 15:52 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=598844&group_id=103 Category: Pipermail Group: 2.1 beta Status: Closed Resolution: Fixed Priority: 5 Submitted By: Patrick Finnerty (finnertyp) Assigned to: Nobody/Anonymous (nobody) Summary: BASE64 attachments barfing Initial Comment: When testing MIME attachments I get the following error which occurs using arch to convert a mailbox or when posting to the archive: Pickling archive state into /usr/local/mailman/archives/private/opsarchtest/pipermail.pck Traceback (most recent call last): File "bin/arch", line 160, in ? main() File "bin/arch", line 148, in main archiver.processUnixMailbox(fp, Article, start, end) File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 545, in processUnixMailbox m = mbox.next() File "/usr/local/lib/python2.2/mailbox.py", line 34, in next return self.factory(_Subfile(self.fp, start, stop)) File "/usr/local/mailman/Mailman/Mailbox.py", line 69, in scrubber return mailbox.scrub(msg) File "/usr/local/mailman/Mailman/Mailbox.py", line 89, in scrub return self._scrubber(self._mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 114, in process url = save_attachment(mlist, part, filter_html=0) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 217, in save_attachment decodedpayload = msg.get_payload(decode=1) File "/usr/local/mailman/pythonlib/email/Message.py", line 177, in get_payload return Utils._bdecode(payload) File "/usr/local/mailman/pythonlib/email/Utils.py", line 71, in _bdecode value = base64.decodestring(s) File "/usr/local/lib/python2.2/base64.py", line 44, in decodestring return binascii.a2b_base64(s) binascii.Error: Incorrect padding I've narrowed this down to HTML attachments that include tables. I've attached a mbox that will give this error when used with arch. This only happens when base64 is used. I've also found that even when messages with HTML attachments are archived, clicking on the attachment doesn't display the page but the source instead. Or in some cases it can be garbage. I can supply more info on this if you wish. -- Comment By: Samuel Nicolary (nicolary) Date: 2003-01-17 10:29 Message: Logged In: YES user_id=27555 When I monitored what strings were causing this to barf I found that there were two scenarios - one when the mailman generated html descibing the file was being sent to this function (I have no idea why it is doing this) Ex. A non-text attachment was scrubbed... The second scenario that was truly a padding issue I got around by doing the following in the _bdecode funtion: value = base64.decodestring(s+'=') let me know if you want a full patch of my trashy hack. -- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-08-22 19:09 Message: Logged In: YES user_id=12800 Thanks for the report and the mbox file, this was indeed a bug, which will be fixed in beta4. As for you second question, what you're seeing could be caused by this bug, but it's more likely just the behavior specified by ARCHIVE_HTML_SANTIZER in Defaults.py/mm_cfg.py. To prohibit evil stuff like cross-site scripting, or web bugs and virus from affecting your archive readers, html is typically santized to be harmless. -- Comment By: Patrick Finnerty (finnertyp) Date: 2002-08-22 15:58 Message: Logged In: YES user_id=594846 Whoops. Attached the html file which was used as attachment instead of the mbox file ...which I'm gonna upload now. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=598844&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
Re: [Mailman-Developers] Sourceforge notifications considered harmful
> 1. Do nothing, everything's fine just the way it is -1 > 2. Do a + b +1 > 3. Do a + b + c 0 And, separately, to use summaries instead of full messages for bugs/patches/etc. +1 -- Misha msg05721/pgp0.pgp Description: PGP signature ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
Re: [Mailman-Developers] mm2.1 - DEFAULT_PLAIN_DIGEST_KEEP_HEADERS
On Thursday, January 16, 2003, at 09:06 PM, Bryan Fullerton wrote: On Wednesday, January 15, 2003, at 07:24 PM, Tokio Kikuchi wrote: Please try this patch. https://sourceforge.net/tracker/ index.php?func=detail&aid=668819&group_id=103&atid=300103 This looks good. I've applied it - will let you know how digests look when they go out (midnight). Aaand... it worked great! My customers are happy! Please merge this patch into CVS (or something equivalent). Thanks, Bryan ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] mailmanctl and syslog
Hello, wouldn't be a good idea to log the start and stop of mailmanctl in the syslog? Something like "Mailman $version services started successfuly" and "Mailman $version services stopped successfuly". Just to leave a trace of the activity in the system log. -- Best regards, Luigi mailto:[EMAIL PROTECTED] ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
Re: [Mailman-Developers] mailmanctl and syslog
On Friday, January 17, 2003, at 09:49 AM, Luigi Rosa wrote: wouldn't be a good idea to log the start and stop of mailmanctl in the syslog? This information is effectively logged in logs/qrunner, as seen below, though it might be nice to have a single log-line entry indicating the commands passed to mailmanctl. Jan 15 13:25:37 2003 (67350) Master watcher caught SIGTERM. Exiting. Jan 15 13:25:37 2003 (67350) Master qrunner detected subprocess exit (pid: 67356, sig: None, sts: 15, class: OutgoingRunner, slice: 1/1) Jan 15 13:25:37 2003 (67350) Master qrunner detected subprocess exit (pid: 67355, sig: None, sts: 15, class: NewsRunner, slice: 1/1) Jan 15 13:25:37 2003 (67350) Master qrunner detected subprocess exit (pid: 67354, sig: None, sts: 15, class: IncomingRunner, slice: 1/1) Jan 15 13:25:37 2003 (67350) Master qrunner detected subprocess exit (pid: 67353, sig: None, sts: 15, class: CommandRunner, slice: 1/1) Jan 15 13:25:37 2003 (67350) Master qrunner detected subprocess exit (pid: 67352, sig: None, sts: 15, class: BounceRunner, slice: 1/1) Jan 15 13:25:37 2003 (67350) Master qrunner detected subprocess exit (pid: 67351, sig: None, sts: 15, class: ArchRunner, slice: 1/1) Jan 15 13:25:37 2003 (67350) Master qrunner detected subprocess exit (pid: 67357, sig: None, sts: 15, class: VirginRunner, slice: 1/1) Jan 15 13:25:41 2003 (67471) OutgoingRunner qrunner started. Jan 15 13:25:41 2003 (67468) CommandRunner qrunner started. Jan 15 13:25:41 2003 (67467) BounceRunner qrunner started. Jan 15 13:25:41 2003 (67472) VirginRunner qrunner started. Jan 15 13:25:41 2003 (67469) IncomingRunner qrunner started. Jan 15 13:25:41 2003 (67470) NewsRunner qrunner started. Jan 15 13:25:41 2003 (67466) ArchRunner qrunner started. Bryan ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
Re[2]: [Mailman-Developers] mailmanctl and syslog
Hello Bryan, Friday, January 17, 2003, 3:59:26 PM, you wrote: >> wouldn't be a good idea to log the start and stop of mailmanctl in the >> syslog? BF> This information is effectively logged in logs/qrunner, as seen below, BF> though it might be nice to have a single log-line entry indicating the BF> commands passed to mailmanctl. Mybe I should rephrase my question. Would'nt it be better if mailman can log either in a logfile or in a user configurable SysLog facility? I mean, for each logfile that mm creates, could it be possible to specify a filename or a syslog target? -- Best regards, Luigi mailto:[EMAIL PROTECTED] ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
Re: Re[2]: [Mailman-Developers] mailmanctl and syslog
On Friday, January 17, 2003, at 10:05 AM, Luigi Rosa wrote: Mybe I should rephrase my question. Would'nt it be better if mailman can log either in a logfile or in a user configurable SysLog facility? I mean, for each logfile that mm creates, could it be possible to specify a filename or a syslog target? Aah. :) I probably wouldn't use that (or change from defaults), but I can see how it'd be useful for the logging to be more configurable. Bryan ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Bugs-669874 ] partial string.lower() in Address Matching
Bugs item #669874, was opened at 2003-01-17 18:24 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669874&group_id=103 Category: configuring/installing Group: 2.0.x Status: Open Resolution: None Priority: 5 Submitted By: Jasper van Beusekom (jvbeusek) Assigned to: Nobody/Anonymous (nobody) Summary: partial string.lower() in Address Matching Initial Comment: FindMatchingAddresses of Utils.py (mailman 2.0.13) compares the given 'name' variable to the given dictionary, for example privacy/forbidden_posters. In this comparison, 'name' is converted to lower case (both if SMART_ADDRESS_MATCH is true or false). Unfortunately this dictionary that is being compared to is not converted to lower case. As a result, addresses that should be matched aren't. Additionally, the configuration web-interface doesn't encourage the list owner to only use lowercase. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669874&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Feature Requests-669922 ] list creation without password
Feature Requests item #669922, was opened at 2003-01-17 11:47 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=669922&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Calvin Leung (cleung) Assigned to: Nobody/Anonymous (nobody) Summary: list creation without password Initial Comment: There should be an option which allow list creation without password but treated as a pending request by the site admin. The site admin can approve the list creation (like the moderation process) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=669922&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Patches-670080 ] list_lists selection based on archive category
Patches item #670080, was opened at 2003-01-17 18:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670080&group_id=103 Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: list_lists selection based on archive category Initial Comment: This patch adds two new command line parms to the list_lists script. -r / --private-archives, which causes only lists with private archives to be displayed -u / --public-archives, which causes only lists with public archives to be displayed. I wanted to control the creation of htpasswd files for only private archives, so this modification was born. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670080&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Patches-670142 ] Generate .htaccess from subscriber list
Patches item #670142, was opened at 2003-01-17 22:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670142&group_id=103 Category: command line scripts Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: Generate .htaccess from subscriber list Initial Comment: This is a version of the 2.0.x script, that generates htaccess files based on list subscribers, adapted for MM 2.1 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670142&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Patches-670167 ] fix i18n attachment description in archive
Patches item #670167, was opened at 2003-01-18 05:58 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670167&group_id=103 Category: Pipermail Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Tokio Kikuchi (tkikuchi) Assigned to: Nobody/Anonymous (nobody) Summary: fix i18n attachment description in archive Initial Comment: Bug-ID 669081 (Major attachment handling bug!) is caused inaccurate handling of charset in Scrubber.py. This is caused by misuse of email functions (or by bug in email package). In Scrubber.py, attempt is made to get message charset by part.get_charset() but it returns only None, as far as I experimented. In this patch, message charset is extracted from regular expression pattern in content-type header. This also set the charset of internally crafted message part. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670167&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Bugs-669081 ] Major attachment handling bug!
Bugs item #669081, was opened at 2003-01-16 14:46 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669081&group_id=103 Category: Pipermail Group: 2.1 (stable) Status: Open Resolution: None Priority: 9 Submitted By: Daniel Buchmann (avalon) Assigned to: Barry A. Warsaw (bwarsaw) Summary: Major attachment handling bug! Initial Comment: Attachments are not handled correctly. Attached to this bug report is an example email in a mbox file. How to reproduce: 1. create a list called "clasohlson" 2. copy this mbox file to the archive mbox file 3. run bin/arch for the list 4. look at the resulting archive I will post a followup which will contain the resulting html file I got when doing this. -- >Comment By: Tokio Kikuchi (tkikuchi) Date: 2003-01-18 06:03 Message: Logged In: YES user_id=67709 Please try this patch. https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670167&group_id=103 (Patch ID 670167) -- Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 16:29 Message: Logged In: YES user_id=184577 -changing priority and assignment- -- Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 15:31 Message: Logged In: YES user_id=184577 And here is the html file in english. Notice the difference. Lots of garbage (also called mojibake?) ;) -- Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 15:28 Message: Logged In: YES user_id=184577 Here is the generated html page for the email, if list language is set to norwegian. -- Comment By: Daniel Buchmann (avalon) Date: 2003-01-16 15:26 Message: Logged In: YES user_id=184577 Sorry, my web browser hung after submitting the bug, and I had to go offfline in a hurry. Trying again :) -- Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-16 15:07 Message: Logged In: YES user_id=12800 There was no attachment, are you sure you clicked the checkbox? :( -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=669081&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Feature Requests-670171 ] Adding [label] tag to HTML pages
Feature Requests item #670171, was opened at 2003-01-18 07:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=670171&group_id=103 Category: None Group: None Status: Open Resolution: None Priority: 5 Submitted By: Benjamin Sonntag (benjaminsonntag) Assigned to: Nobody/Anonymous (nobody) Summary: Adding [label] tag to HTML pages Initial Comment: The tag allow a text to be associated with a form component. eg. : do you like pizza ? Yes: No: The problem is that those radiobutton MUST be clicked precisely, you cannot click on the "yes" or "no" text associated with the radio button. In fact they are only graphically associated. Since HTML 2.0, you can associate a text to a field form. This tag, named "label" is known by all major browsers (mozilla, ie, ns...) So you may add a LABEL tag for each checkbox or radio button to mailman's web pages : eg. : Languages supported by this list. Czech German will become : Languages supported by this list. Czech German So, the user may click on the word "German" to check/uncheck the associated checkbox. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=670171&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Patches-670186 ] add tag to radio/checkbox arrays
Patches item #670186, was opened at 2003-01-18 08:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670186&group_id=103 Category: None Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Benjamin Sonntag (benjaminsonntag) Assigned to: Nobody/Anonymous (nobody) Summary: add tag to radio/checkbox arrays Initial Comment: as of feature request [ 670171 ] : The tag allow a text to be associated with a form component. eg. : do you like pizza ? Yes: No: The problem is that those radiobutton MUST be clicked precisely, you cannot click on the "yes" or "no" text associated with the radio button. In fact they are only graphically associated. Since HTML 2.0, you can associate a text to a field form. This tag, named "label" is known by all major browsers (mozilla, ie, ns...) Here is a patch to add tags to radio and checkbox arrays it works on mailman-2.1-5.deb (debian sid package) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670186&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Patches-670186 ] add tag to radio/checkbox arrays
Patches item #670186, was opened at 2003-01-18 08:28 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670186&group_id=103 Category: None Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Benjamin Sonntag (benjaminsonntag) Assigned to: Nobody/Anonymous (nobody) Summary: add tag to radio/checkbox arrays Initial Comment: as of feature request [ 670171 ] : The tag allow a text to be associated with a form component. eg. : do you like pizza ? Yes: No: The problem is that those radiobutton MUST be clicked precisely, you cannot click on the "yes" or "no" text associated with the radio button. In fact they are only graphically associated. Since HTML 2.0, you can associate a text to a field form. This tag, named "label" is known by all major browsers (mozilla, ie, ns...) Here is a patch to add tags to radio and checkbox arrays it works on mailman-2.1-5.deb (debian sid package) -- >Comment By: Benjamin Sonntag (benjaminsonntag) Date: 2003-01-18 08:31 Message: Logged In: YES user_id=193384 Sorry, forgot the attachment. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=670186&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
