Mailman-coders August 2005

mailman-coders@python.org

2 participants
40 discussions

[ mailman-Bugs-1263239 ] Mailman on SSL sends passwords in plain text
by SourceForge.net 18 Aug '05

18 Aug '05

Bugs item #1263239, was opened at 2005-08-18 17:25 Message generated for change (Comment added) made by doolyo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1263239&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: None Status: Open Resolution: None Priority: 8 Submitted By: Daniel (doolyo) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman on SSL sends passwords in plain text Initial Comment: I have tried putting Mailman on a secure path of my server on an https url. It seemed to work approximately when adding the following directive in apache: RewriteCond %{HTTPS} !=on RewriteRule /mailman/(.*) https://www\.mysite\.com/mailman/$1 [R] However, I have sniffed the TCP/HTTP traffic during a list creation and I have seen that all the form is posted IN CLEAR. This is normal in fact as we send that to the http link first (see Bug Request #1263219). Therefore the whole test is sent in clear and only afterwards the client receives back the document move to https from apache to redirect to the proper page. I think that this could be solved if all links of the mailman binaries (admin, create and so forth) are taking dynamically the link specified in the mm_cfg.py, in the DEFAULT_URL_HOST tag. However maybe there is another clean way of putting that on a secure url. If so I would be interested in how to do that because I didn't find anything about that subject appart people doing all like I did. Thanks, Daniel ---------------------------------------------------------------------- >Comment By: Daniel (doolyo) Date: 2005-08-18 18:09 Message: Logged In: YES user_id=1320890 P.S.: I have seen that we can use fix_url.py to fix the URL for a specific list. However, it does not seem to fix the links of /mailman/create and the others and thus does not solve the problem, as I want to have the SSL on that page. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1263239&group_…

1 0

[ mailman-Bugs-1263239 ] Mailman on SSL sends passwords in plain text
by SourceForge.net 18 Aug '05

18 Aug '05

Bugs item #1263239, was opened at 2005-08-18 17:25 Message generated for change (Settings changed) made by doolyo You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1263239&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: None Status: Open Resolution: None >Priority: 8 Submitted By: Daniel (doolyo) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman on SSL sends passwords in plain text Initial Comment: I have tried putting Mailman on a secure path of my server on an https url. It seemed to work approximately when adding the following directive in apache: RewriteCond %{HTTPS} !=on RewriteRule /mailman/(.*) https://www\.mysite\.com/mailman/$1 [R] However, I have sniffed the TCP/HTTP traffic during a list creation and I have seen that all the form is posted IN CLEAR. This is normal in fact as we send that to the http link first (see Bug Request #1263219). Therefore the whole test is sent in clear and only afterwards the client receives back the document move to https from apache to redirect to the proper page. I think that this could be solved if all links of the mailman binaries (admin, create and so forth) are taking dynamically the link specified in the mm_cfg.py, in the DEFAULT_URL_HOST tag. However maybe there is another clean way of putting that on a secure url. If so I would be interested in how to do that because I didn't find anything about that subject appart people doing all like I did. Thanks, Daniel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1263239&group_…

1 0

[ mailman-Bugs-1263239 ] Mailman on SSL sends passwords in plain text
by SourceForge.net 18 Aug '05

18 Aug '05

Bugs item #1263239, was opened at 2005-08-18 17:25 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=1263239&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: None Status: Open Resolution: None Priority: 5 Submitted By: Daniel (doolyo) Assigned to: Nobody/Anonymous (nobody) Summary: Mailman on SSL sends passwords in plain text Initial Comment: I have tried putting Mailman on a secure path of my server on an https url. It seemed to work approximately when adding the following directive in apache: RewriteCond %{HTTPS} !=on RewriteRule /mailman/(.*) https://www\.mysite\.com/mailman/$1 [R] However, I have sniffed the TCP/HTTP traffic during a list creation and I have seen that all the form is posted IN CLEAR. This is normal in fact as we send that to the http link first (see Bug Request #1263219). Therefore the whole test is sent in clear and only afterwards the client receives back the document move to https from apache to redirect to the proper page. I think that this could be solved if all links of the mailman binaries (admin, create and so forth) are taking dynamically the link specified in the mm_cfg.py, in the DEFAULT_URL_HOST tag. However maybe there is another clean way of putting that on a secure url. If so I would be interested in how to do that because I didn't find anything about that subject appart people doing all like I did. Thanks, Daniel ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1263239&group_…

1 0

[ mailman-Bugs-1263219 ] Link of the 'admin' page not updated if config change
by SourceForge.net 18 Aug '05

18 Aug '05

Bugs item #1263219, was opened at 2005-08-18 16:57 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1263219&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: None Status: Open Resolution: None Priority: 5 Submitted By: Daniel (doolyo) Assigned to: Nobody/Anonymous (nobody) Summary: Link of the 'admin' page not updated if config change Initial Comment: If I change the mailman url on the server, the link displayed on the admin page that shows the 'mailing list overview page' is not updated in consequence. I have put the followings in mm_cfg.py: DEFAULT_URL_HOST = 'https://www.mysite.com/mailman' (secure connection), and we can see on the admin page that the link is on the http:// page and not https://. It should also be the same for the other pages. BTW it would be good if we could also change the pages ourselves. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1263219&group_…

1 0

[ mailman-Bugs-1263213 ] checkbox "Send list created" not saved if failure
by SourceForge.net 18 Aug '05

18 Aug '05

Bugs item #1263213, was opened at 2005-08-18 16:50 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=1263213&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: None Status: Open Resolution: None Priority: 5 Submitted By: Daniel (doolyo) Assigned to: Nobody/Anonymous (nobody) Summary: checkbox "Send list created" not saved if failure Initial Comment: On the list creation page (/mailman/create), if we check the "Send list created e-mail to list owner" button to 'yes' and that we put a wrong password by submitting the form, the checkbox will come back to 'no'. This is not the case with the other checkboxes or the text, everything else comes back to the previously chosen values. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1263213&group_…

1 0

[ mailman-Feature Requests-1041100 ] moderation approval should send email notification
by SourceForge.net 12 Aug '05

12 Aug '05

Feature Requests item #1041100, was opened at 2004-10-05 17:35 Message generated for change (Comment added) made by kiwimonster You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1041100&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: Kirsten Petersen (kiwimonster) Assigned to: Nobody/Anonymous (nobody) Summary: moderation approval should send email notification Initial Comment: When a non-member attempts to post to a moderated list, they receive an email informing them that their message is pending moderation. However, when the moderator has approved the message, they receive no follow-up to let them know this has happened. Since the non-member is not on the list, they have no way of knowing whether their post was successful. It would be nice to have a checkbox that allowed the moderator to notify the poster when their message has been approved. Or, to have notification sent by default. ---------------------------------------------------------------------- >Comment By: Kirsten Petersen (kiwimonster) Date: 2005-08-12 10:40 Message: Logged In: YES user_id=1122614 Okay, so it's a feature request. Is there any chance that this functionality will be added to Mailman? ---------------------------------------------------------------------- Comment By: Tokio Kikuchi (tkikuchi) Date: 2004-10-13 06:10 Message: Logged In: YES user_id=67709 This is more a feature request than a bug. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1041100&group_…

1 0

[ mailman-Bugs-1257306 ] Email is discarded when the subject is in Unicode (Chinese)
by SourceForge.net 12 Aug '05

12 Aug '05

Bugs item #1257306, was opened at 2005-08-12 05:23 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=1257306&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 Submitted By: gamelover (gamelover9001) Assigned to: Nobody/Anonymous (nobody) Summary: Email is discarded when the subject is in Unicode (Chinese) Initial Comment: If you send an email with the subject in unicode (e.g., Chinese) to a mailing list, the email will be discarded. The Mailman does not give any information to the sender. So both senders and recipients will not know anything about what is going on about the email. This is a bug for 2.1.5. I am not sure if the bug is still there for 2.1.6. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1257306&group_…

1 0

[ mailman-Bugs-1256879 ] Bug report: hanging message (shunting)
by SourceForge.net 11 Aug '05

11 Aug '05

Bugs item #1256879, was opened at 2005-08-11 18:44 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=1256879&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: None Status: Open Resolution: None Priority: 5 Submitted By: Loek Jehee (loekjehe) Assigned to: Nobody/Anonymous (nobody) Summary: Bug report: hanging message (shunting) Initial Comment: Hello, I repeatedly have a shunted message when it is a message made in Eudora 6.2 (on Mac OS X) that contains a so-called "in-line" image (like jpg). When I send such message to the list (and I approve it as a moderator), then the message gets "shunted" and manually has to be put in the normal queue. I consider this a bug in MailMan which I would like to inform you of. I don't know if this list is the right place to post such bug report but I thought it might be interesting also for other users to know that such thing can happen. Maybe someone has a solution for me for this type of messages containing in-line pictures. The bug recently happens always when I send such message so it is a reproducible error. Below is the error log for your information. Best regards, Loek Jehee -------- Hi Loek, if you report this to mailman-users mailing list, here is the error log. It is for the default installation of version 2.1.6. Aug 10 19:29:19 2005 (30334) Uncaught runner exception: [Errno 5] Input/output error Aug 10 19:29:19 2005 (30334) Traceback (most recent call last): File "/usr/local/mailman/Mailman/Queue/Runner.py", line 111, in _oneloop self._onefile(msg, msgdata) File "/usr/local/mailman/Mailman/Queue/Runner.py", line 167, 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/ToDigest.py", line 92, in process send_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 133, in send_digests send_i18n_digests(mlist, mboxfp) File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 315, in send_i18n_digests msg = scrubber(mlist, msg) File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 286, in process payload = part.get_payload(decode=True) File "/usr/local/mailman/pythonlib/email/Message.py", line 223, in get_payload uu.decode(StringIO(payload+'\n'), sfp) File "/usr/lib/python2.4/uu.py", line 139, in decode sys.stderr.write("Warning: %s\n" % str(v)) File "/usr/local/mailman/Mailman/Logging/MultiLogger.py", line 45, in write _logexc(logger, msg) File "/usr/local/mailman/Mailman/Logging/Utils.py", line 22, in _logexc sys.__stderr__.write('Logging error: %s\n' % logger) IOError: [Errno 5] Input/output error Aug 10 19:29:19 2005 (30334) SHUNTING: 1123691170.7004039+8fe48db8d809846344debd6eddb21ddcfb95ffca "Shunting" means putting the message into the deferred queue. "Unshunting" means pulling the message out into the normal queue, so it is sent out. Another piece of info that might help is the output of bin/unshunt: Aug 10 23:15:12 2005 qrunner(7630): Warning: Trailing garbage Aug 10 23:15:12 2005 qrunner(7630): Warning: Trailing garbage Aug 10 23:15:12 2005 qrunner(7630): Warning: Trailing garbage Aug 10 23:15:12 2005 qrunner(7630): Warning: Trailing garbage Aug 10 23:15:12 2005 qrunner(7630): Warning: Trailing garbage Aug 10 23:15:12 2005 qrunner(7630): Warning: Trailing garbage ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1256879&group_…

1 0

[ mailman-Bugs-1256272 ] NNTP gatewaying trashes Message-IDs
by SourceForge.net 11 Aug '05

11 Aug '05

Bugs item #1256272, was opened at 2005-08-11 00: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=1256272&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: nntp/news Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Kate Turner (kateturner) Assigned to: Nobody/Anonymous (nobody) Summary: NNTP gatewaying trashes Message-IDs Initial Comment: when a message is relayed to NNTP, the NewsRunner unconditionally replaces the existing Message-ID with its own. this breaking threading when reading a list via news, and when an NNTP user replies to a list message. a better solution would be either: 1) do not rewrite the message-id unless the NNTP server reports an error when posting it (duplicate ID); or 2) optionally, always rewrite posters' message-ids into a mailman-generated ID, and use this ID for both mail and news. i have implemented the former at our site and it appears to work, but it's so ugly i'd not feel comfortable submitting a patch for it. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1256272&group_…

1 0

[ mailman-Bugs-1255548 ] Corrupt address -> message stuck in queue (endless loop)
by SourceForge.net 10 Aug '05

10 Aug '05

Bugs item #1255548, was opened at 2005-08-10 03:27 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1255548&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: bounce detection Group: 2.0.x >Status: Closed Resolution: None Priority: 5 Submitted By: mpellissetti (mpellissetti) Assigned to: Nobody/Anonymous (nobody) Summary: Corrupt address -> message stuck in queue (endless loop) Initial Comment: Version: mailman-2.0.8-1, on Red Hat Linux 7.2 We transferred email adresses from a Windows-based program (Filemaker), by exporting them in an ASCII file (Addresses.txt) and importing them to the mailman list with: /var/mailman/bin/remove_members -a Listname; /var/mailman/bin/add_members -n Addresses.txt Listname The file Addresses.txt contained one corrupt email address of the form: user1(a)host.domain^Kpers: user2(a)host.domain Viewing the file content with od showed the following exact character sequence (separate characters with one blank for better viewing): u s e r 1 @ h o s t . d o m a i n \v p e r s : u s e r 2 @ h o s t . d o m a i n Note: The corrupt address was not detected by mailman when it was imported! Sending an email to this mailing list caused the message to be stuck in /var/mailman/qfiles. Since qrunner is specified in /var/mailman/cron/crontab.in to be executed every minute, the message was sent out repeatedly (18 times mailman was killed manually) basically to the addresses preceding the corrupt one. The sender of the message received the following error message per email: ... ----- The following addresses had permanent fatal errors ----- pers: ----- Transcript of session follows ----- 553 5.1.3 pers:... List:; syntax illegal for recipient addresses ... Note: This bug is reproducible. This behavior denotes poor fault tolerance, I strongly hope that newer versions behave differently in such a case. It is always possible that a corrupt address is being entered, but the consequences (in the described case) are catastrophic! (Fortunately one of the approx. 500 recipients replied quite immediately, so "only" 18 copies of the message were sent out!) ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2005-08-10 08:04 Message: Logged In: YES user_id=12800 Mailman 2.0.8 is extremely old and no longer supported. If you upgrade to Mailman 2.1.6 (the current release of the 2.1 branch) and the problem persists, then feel free to open a new bug report, but please try to include the content of the offending message so that we can debug it. ---------------------------------------------------------------------- Comment By: mpellissetti (mpellissetti) Date: 2005-08-10 03:35 Message: Logged In: YES user_id=1326612 Rectification: After the message got stuck in /var/mailman/qfiles, the message was sent out repeatedly (18 times until mailman was killed manually), basically to the addresses FOLLOWING the corrupt one. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1255548&group_…

1 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

Mailman-coders August 2005