[Mailman-Developers] [ mailman-Bugs-663593 ] Traceback when changing email address
Bugs item #663593, was opened at 2003-01-07 11:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663593&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Deleted >Resolution: Duplicate Priority: 5 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback when changing email address Initial Comment: I got this traceback when trying to change a member's email address on his options page. His name contained a non-ASCII character, which is probably why this happened. Traceback (most recent call last): File "/home/mailman/scripts/driver", line 87, in run_main main() File "/home/mailman/Mailman/Cgi/options.py", line 269, in main if membername and membername <> oldname: UnicodeError: ASCII decoding error: ordinal not in range(128) -- >Comment By: Daniel Buchmann (avalon) Date: 2003-01-08 09:01 Message: Logged In: YES user_id=184577 Deleting this bug report, as this is a dupe of bug #660675 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663593&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Patches-645513 ] qmail VERP-enabled delivery handler
Patches item #645513, was opened at 2002-11-28 18:58 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Colin Palmer (tzs) Assigned to: Nobody/Anonymous (nobody) Summary: qmail VERP-enabled delivery handler Initial Comment: This is based on Peter D. Gray's popen-avoiding Sendmail.py module, tweaked so it can use qmail-inject instead of sendmail and ask qmail to do VERP when the message is delivered, which is much faster than getting Mailman to do it at message injection time. You'll need the following in mm_cfg.py: DELIVERY_MODULE = 'Qmail' SENDMAIL_CMD = '/var/qmail/bin/qmail-inject' DO_QMAIL_VERP = 1 -- Comment By: Ed Lau (edlau) Date: 2003-01-08 01:49 Message: Logged In: YES user_id=675094 using the version released 2003-01-07 17:27, with DO_QMAIL_VERP = 0, any post to a list gets posted to all members properly, but also gets shunted. This happened because I didn't have QMAIL_LOG_EVERY_MESSAGE, QMAIL_LOG_SUCCESS, or QMAIL_LOG_FAILURE defined. Is the Email shunted, yet posted event supposed to happen? I'll be testing out VERP later on -- Comment By: Colin Palmer (tzs) Date: 2003-01-07 12:46 Message: Logged In: YES user_id=658762 Oops, should have been comparing it's function with 'SMTPDirect' as well as 'Sendmail'... this version should work a lot better. It doesn't support personalisation or mailman-generated VERP headers, but should do everything else now. Read the the comments at the top of the module for things that need to be in mm_cfg.py for it to work. -- Comment By: Ed Lau (edlau) Date: 2002-12-24 16:32 Message: Logged In: YES user_id=675094 Running as listed except DO_QMAIL_VERP = 0, messages don't appear to have the footer tacked on at the bottom. Everything else (header-wise) seems there. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
Re: [Mailman-Developers] Qmail Doc patch for 2.1
EL> This is a documentation patch for the README.QMAIL file. EL> There's not much testing here, but Barry would you consider EL> applying it? Sure, if other qmailers like it. Can you upload it as a patch to SF? Thanks, -Barry ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Patches-643011 ] bug: Scrubbed messages are re-decoded
Patches item #643011, was opened at 2002-11-24 05:21 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643011&group_id=103 Category: Pipermail Group: Mailman 2.1 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Hatuka*nezumi (hatukanezumi) Assigned to: Nobody/Anonymous (nobody) Summary: bug: Scrubbed messages are re-decoded Initial Comment: Content-Transfer-Encoding must be cleared. -- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-08 07:50 Message: Logged In: YES user_id=12800 Thanks for the follow up. -- Comment By: Hatuka*nezumi (hatukanezumi) Date: 2003-01-08 01:11 Message: Logged In: YES user_id=529503 This seems to be fixed at rev. 2.18. Please delete. -- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 22:32 Message: Logged In: YES user_id=12800 Could you give more details about why this patch is necessary? If you have message examples, please attach them (don't paste them into a comment). -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=643011&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Bugs-664466 ] 2.0 cookies break 2.1 web auth
Bugs item #664466, was opened at 2003-01-08 11:30 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=664466&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Bryan Fullerton (fehwalker) Assigned to: Nobody/Anonymous (nobody) Summary: 2.0 cookies break 2.1 web auth Initial Comment: (as discussed on mailman-users) If there are *any* mm2.0 cookies in the URI-space mm2.1 looks in, the following code will always raise a Cookie.CookieException and return 0. # Treat the cookie data as simple strings, and do application level # decoding as necessary. By using SimpleCookie, we prevent any kind # of security breach due to untrusted cookie data being unpickled # (which is quite unsafe). try: c = Cookie.SimpleCookie(cookiedata) except Cookie.CookieError: return 0 If python's Cookie code (or at least SimpleCookie) doesn't like cookies with :'s in them that'd explain it. This is rather a problem for anyone thinking they could run both mm2.0 and mm2.1 mapped into the same URI-space. Simply put, you can't (without re-auth'ing with every action in 2.1 lists), unless the mm2.1 code is rewritten to handle that exception better. Or unless you nuke all your cookies after every use of a 2.0 list (not just logout - in my testing that doesn't actually remove the cookie, just the cookie's contents). The good news is that this should be no problem once everything is moved to 2.1. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=664466&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Bugs-664575 ] mailman 2.1 tarball permissions
Bugs item #664575, was opened at 2003-01-08 14:24 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=664575&group_id=103 Category: configuring/installing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Barry A. Warsaw (bwarsaw) Assigned to: Nobody/Anonymous (nobody) Summary: mailman 2.1 tarball permissions Initial Comment: The tarball contains world writeable directories and files by default. This may be a problem on systems where users do not have a sane umask or safe directory permissions, allowing an attacker to modify source code that is later compiled (usually as root) and that is installed setuid/setgid (allowing for easy insertion of backdoors). [EMAIL PROTECTED] -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=664575&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
Re: [Mailman-Developers] Qmail Doc patch for 2.1
On Wed, 8 Jan 2003, Barry A. Warsaw wrote: > EL> This is a documentation patch for the README.QMAIL file. > EL> There's not much testing here, but Barry would you consider > EL> applying it? > Sure, if other qmailers like it. It looks good to me. -- ** Colin Palmer, Systems and Development Group, University of Waikato, NZ ** ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] small 2.1 bin/sync_members fix
It dies with an 'UnboundLocalError:' for me otherwise:
--- sync_members~ Wed Jan 8 08:41:08 2003
+++ sync_membersThu Jan 9 09:49:51 2003
@@ -255,6 +255,7 @@
try:
if not dryrun:
mlist.ApprovedAddMember(userdesc, welcome, notifyadmin)
+enc = sys.getdefaultencoding()
s = email.Utils.formataddr((name, addr)).encode(enc, 'replace')
print _('Added : %(s)s')
except Errors.MMAlreadyAMember:
--
** Colin Palmer, Systems and Development Group, University of Waikato, NZ **
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Patches-664611 ] Updated README.QMAIL doc patch
Patches item #664611, was opened at 2003-01-08 11:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664611&group_id=103 Category: documentation Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Ed Lau (edlau) Assigned to: Nobody/Anonymous (nobody) Summary: Updated README.QMAIL doc patch Initial Comment: Main item: distinction between MM2.0 & MM2.1 alias generation scripts. Also, information on VERP -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664611&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Patches-645513 ] qmail VERP-enabled delivery handler
Patches item #645513, was opened at 2002-11-29 15:58 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Colin Palmer (tzs) Assigned to: Nobody/Anonymous (nobody) Summary: qmail VERP-enabled delivery handler Initial Comment: This is based on Peter D. Gray's popen-avoiding Sendmail.py module, tweaked so it can use qmail-inject instead of sendmail and ask qmail to do VERP when the message is delivered, which is much faster than getting Mailman to do it at message injection time. You'll need the following in mm_cfg.py: DELIVERY_MODULE = 'Qmail' SENDMAIL_CMD = '/var/qmail/bin/qmail-inject' DO_QMAIL_VERP = 1 -- >Comment By: Colin Palmer (tzs) Date: 2003-01-09 09:09 Message: Logged In: YES user_id=658762 Yes, python throws an exception if they (or any other config options) are undefined. Set them to 'None' if you don't want logging to happen. -- Comment By: Ed Lau (edlau) Date: 2003-01-08 22:49 Message: Logged In: YES user_id=675094 using the version released 2003-01-07 17:27, with DO_QMAIL_VERP = 0, any post to a list gets posted to all members properly, but also gets shunted. This happened because I didn't have QMAIL_LOG_EVERY_MESSAGE, QMAIL_LOG_SUCCESS, or QMAIL_LOG_FAILURE defined. Is the Email shunted, yet posted event supposed to happen? I'll be testing out VERP later on -- Comment By: Colin Palmer (tzs) Date: 2003-01-08 09:46 Message: Logged In: YES user_id=658762 Oops, should have been comparing it's function with 'SMTPDirect' as well as 'Sendmail'... this version should work a lot better. It doesn't support personalisation or mailman-generated VERP headers, but should do everything else now. Read the the comments at the top of the module for things that need to be in mm_cfg.py for it to work. -- Comment By: Ed Lau (edlau) Date: 2002-12-25 13:32 Message: Logged In: YES user_id=675094 Running as listed except DO_QMAIL_VERP = 0, messages don't appear to have the footer tacked on at the bottom. Everything else (header-wise) seems there. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Bugs-663421 ] Links on admindb script discard pending posts
Bugs item #663421, was opened at 2003-01-06 18:43 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663421&group_id=103 Category: Web/CGI Group: 2.1 (stable) >Status: Closed >Resolution: Rejected Priority: 5 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: Links on admindb script discard pending posts Initial Comment: I get my daily notification of pending posts that didn't go through (mostly spam), I click on the link and the admindb script is launched as normal. I see the summary of the held posts, but if I click on the details link, all the held posts go away. All the radio buttons on the summary form were set to "Defer". The post log file shows the following for one of the posts that was dumped ... Jan 06 10:06:44 2003 (22141) openerp400: Discarded posting: From: [EMAIL PROTECTED] Subject: =?ISO-8859-1?Q?Happy New Year?= -- >Comment By: David Gibbs (midrangeman) Date: 2003-01-08 17:31 Message: Logged In: YES user_id=86339 Don't ask me what was going on ... but it fixed itself. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663421&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] RFQ: Member moderation feature.
In discussion with one of my list members an idea arose to help reduce moderator load and (better) allow posters to guide/control the threads they create: Assuming a fully moderated list: 1) A poster may indicate on their posting that they wish to moderate the subsequent thread. This could be done by custom header or special first line in a special format on the message. 2) All posts on that thread are then held for their approval, and they can view that moderation queue as if they were a first class list moderator, with the only difference being that they can only see and process the posts held for them, and won't see the posts held for other members or the list in general. 3) The real moderator(s) view of the moderation queue will show all messages. 4) A member moderator can defer, accept, reject, or discard the messages in his queue, just as per a normal moderator EXCEPT that in all cases the commands have no effect other than annotating the message for the real moderator. (ie the member moderator supplies hints to the real moderator). 5) The real moderator in reviewing his moderation queue will see normal messages, messages in member moderator queues, and annotated messages from member moderated queues. Messages being held on member moderation queues will be annotated to that effect. Any commands that a real moderator applies to any messages (no matter its status) in his moderation queue take place instantly (ie he's God and can do anything with final decisions resting with the real moderator). 6) A messages arrive on a member moderated thread the member moderator is emailed a standard "held message" email just like a real moderator. In fact the same message could be sent to both moderators, with the body of the message stating that the message is member moderated and who by. This could be extended for partially moderated or unmoderated lists by replacing #4 above with: 4a) A member moderator can defer, accept, reject, or discard the messages in his queue with the following results: Defer -- message remains held in his queue. Accept -- Message is broadcast or held as per any moderation flag applied to the poster. Reject -- Message is annotated with the member's proposed rejection message and left in the real moderator's moderation queue. Discard -- Message is annotated with the member's proposed discard reason and left in the real moderator's moderation queue. All the above assumes that member moderation is via the web only. I consider this acceptable. Yeah, moderation via email is great, but it doesn't have to be in version 1.0 of the feature. -*- Implementation notes: Tracing threads is unreliable. Not all MUAs properly support or generate References: or In-Reply-To: headers. For those that do, tracing and tracking Message-IDs is the (only) reliable route. I propose that when a thread/message becomes member moderated that Mailman log the Subject: header and Message-ID. Any subsequent message which has that Message-ID in an In-Reply-To: or References: header and has a Subject: which is (at least) a prefix substring (accounting for "Re:" etc) of the saved Subject: will be held for member moderation. Attempts by a member to moderate a thread already member moderated will be refused/rejected/denied/whatever. A member may however fork a thread and moderate the new fork _IF_ he changes the Subject: header as that breaks the check above. If desired we can support the ability for a member moderator to resign from moderating a thread (web interface again). Commentary: Currently Mailman has poor supports in general for multiple moderators. The above annotation features go a long way to better supporting multiple moderators. Adding a general moderation queue annotation feature would be a very useful as a way for moderators to pass each other notes as to held messages, as well as for single moderators to keep notes for themselves. -*- As a final tweak, and I find this one particularly delightful, I'd like to see a text field with a controlling checkbox in the displayed headers for a message held for moderation. If the checkbox is checked by a real or member moderator and text entered in the field, the held message will have its Subject: header edited/replaced ala: Subject: Newly entered text here (Was: Old subject goes here) Note that this would effectively allow a member moderator to fork a thread out of his control. More specifically this would be the only extent to which member moderators could edit held messages. Real moderators would retain normal abilities to edit message text. -*- Background reasoning: Moderated lists have a core scaling problem WRT moderator overload. This feature allows moderation to be (partially) distributed w
[Mailman-Developers] Anti-Virus
I have just download latest CVS version of MM and I am installing it. I use Postfix + procmail + AnomySanitizer + AVP_Antivirus + MailMan Today when I send a message to a mailinglist of users of my server I have the problem that the AnomySanitizer and AntiVirus scan each copy of message for each user. This causes a very important overload for the server. In other words, a message to a list [EMAIL PROTECTED] tavel the following way: message -> SMTP -> mailman post AllOfMyUsers -> (many copies) -> procmail -> AnomySanitizer -> Antivirus -> user1 mailmbox -> procmail -> AnomySanitizer -> Antivirus -> user2 mailmbox -> procmail -> AnomySanitizer -> Antivirus -> user3 mailmbox I would like to move the Sanitizer+Antivirus check before MM make many copies of the message and to check only one time. Something like this: message -> SMTP -> mailman post AllOfMyUsers -> AnomySanitizer -> Antivirus -> (many copies) -> procmail -> user1 mailmbox -> procmail -> user2 mailmbox -> procmail -> user3 mailmbox Can you tell me a tip to do that? -- Rodolfo Pilas <[EMAIL PROTECTED]> ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] Re: Anti-Virus
"Rodolfo Pilas" <[EMAIL PROTECTED]> wrote in message 1042071119.1373.76.camel@localhost">news:1042071119.1373.76.camel@localhost... > Today when I send a message to a mailinglist of users of my server I > have the problem that the AnomySanitizer and AntiVirus scan each copy of > message for each user. This causes a very important overload for the > server. I had the same quandry ... I was able to solve the problem by setting up multiple instances of sendmail ... one instance listening only on 127.0.0.1, which handled the mailman traffic and didn't do any virus scanning (I use MailScanner), and another instance listening on my other IP's (which does scan for viruses). When mail comes in from the outside, it gets scanned for viruses and handed off to Mailman. When mailman processes the message, it does NOT get scanned, because mailman connects on 127.0.0.1. Although I don't know how you would do it with Postfix, I'm sure it can be done. The scanner I use is MailScanner (http://www.mailscanner.info) ... it supports postfix, so you might be able to get information there on how to implement using your scanner. david ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Patches-664611 ] Updated README.QMAIL doc patch
Patches item #664611, was opened at 2003-01-08 11:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664611&group_id=103 Category: documentation Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Ed Lau (edlau) Assigned to: Nobody/Anonymous (nobody) Summary: Updated README.QMAIL doc patch Initial Comment: Main item: distinction between MM2.0 & MM2.1 alias generation scripts. Also, information on VERP -- >Comment By: Ed Lau (edlau) Date: 2003-01-08 19:50 Message: Logged In: YES user_id=675094 Didn't look like SF got my patch the first time. It's attached now -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664611&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Bugs-663421 ] Links on admindb script discard pending posts
Bugs item #663421, was opened at 2003-01-06 19:43 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663421&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Closed Resolution: Rejected Priority: 5 Submitted By: David Gibbs (midrangeman) Assigned to: Nobody/Anonymous (nobody) Summary: Links on admindb script discard pending posts Initial Comment: I get my daily notification of pending posts that didn't go through (mostly spam), I click on the link and the admindb script is launched as normal. I see the summary of the held posts, but if I click on the details link, all the held posts go away. All the radio buttons on the summary form were set to "Defer". The post log file shows the following for one of the posts that was dumped ... Jan 06 10:06:44 2003 (22141) openerp400: Discarded posting: From: [EMAIL PROTECTED] Subject: =?ISO-8859-1?Q?Happy New Year?= -- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-01-09 01:15 Message: Logged In: YES user_id=12800 I don't know which is scarier, the initial report or the follow up ;) -- Comment By: David Gibbs (midrangeman) Date: 2003-01-08 18:31 Message: Logged In: YES user_id=86339 Don't ask me what was going on ... but it fixed itself. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663421&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Patches-664611 ] Updated README.QMAIL doc patch
Patches item #664611, was opened at 2003-01-08 11:57 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664611&group_id=103 Category: documentation Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Ed Lau (edlau) Assigned to: Nobody/Anonymous (nobody) Summary: Updated README.QMAIL doc patch Initial Comment: Main item: distinction between MM2.0 & MM2.1 alias generation scripts. Also, information on VERP -- >Comment By: Ed Lau (edlau) Date: 2003-01-08 23:24 Message: Logged In: YES user_id=675094 Directory paths have changed to reflect new installations vs upgrading from prior installs -- Comment By: Ed Lau (edlau) Date: 2003-01-08 19:50 Message: Logged In: YES user_id=675094 Didn't look like SF got my patch the first time. It's attached now -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=664611&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
