Mailman 3 June 2006 - Mailman-coders

[ mailman-Bugs-1506338 ] cannot post to list
by SourceForge.net 15 Jun '06

15 Jun '06

Bugs item #1506338, was opened at 2006-06-14 14:07 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1506338&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: 5 Submitted By: mdbiker (mdbiker) Assigned to: Nobody/Anonymous (nobody) Summary: cannot post to list Initial Comment: i am an administrator (but i didn't install it nor do i have access to the server) of an announcement only mailing list. despite having 3 addresses listed as administrator and moderator, we have only been able to use one address to post. that was ok till last week when we were subject to a spoofing attack appearing to come from that address. i removed that address, having forgotten about the problem in posting from the others. now i cannot post tothe list at all even though i returned the removed address. for each i get back a "this is an announcement list - send your email to xxxx for posting and now even xxxx cannot post. so the bug is that even though listed as admin/mod i cannot post. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-06-14 17:25 Message: Logged In: YES user_id=1123998 First, I see you've already posted this to mailman-users(a)python.org which is probably a more appropriate place to go first. Second, this is not a bug. The addresses in the 'owner' and 'moderator' attributes are ONLY addresses to which owner and moderator notices are mailed, and in the case of owner, listed in the 'run by' footer at the bottom of web pages. These addresses have no other function. If they are not also members, they will not receive list posts. If posting is restricted to members or unmoderated members, they will not be allowed to post unless they are (unmoderated) members or listed in accept_these_nonmembers. It seems from your description that the default for your list is that new members are moderated and moderated members can't post. You deleted the one unmoderated member so no one could post and when you added xxxx back, xxxx was moderated by default. You could turn off moderation for those members you want to post, but a more 'spoof proof' method is use of an Approved: header as discussed in FAQs http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.011.htp and http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.034.htp ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1506338&group_…

1 0

[ mailman-Bugs-1506338 ] cannot post to list
by SourceForge.net 14 Jun '06

14 Jun '06

Bugs item #1506338, was opened at 2006-06-14 17: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=1506338&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: mdbiker (mdbiker) Assigned to: Nobody/Anonymous (nobody) Summary: cannot post to list Initial Comment: i am an administrator (but i didn't install it nor do i have access to the server) of an announcement only mailing list. despite having 3 addresses listed as administrator and moderator, we have only been able to use one address to post. that was ok till last week when we were subject to a spoofing attack appearing to come from that address. i removed that address, having forgotten about the problem in posting from the others. now i cannot post tothe list at all even though i returned the removed address. for each i get back a "this is an announcement list - send your email to xxxx for posting and now even xxxx cannot post. so the bug is that even though listed as admin/mod i cannot post. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1506338&group_…

1 0

[ mailman-Bugs-1495122 ] Mailman strips format=flowed from Content-Type header
by SourceForge.net 13 Jun '06

13 Jun '06

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 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: 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 13 Jun '06

13 Jun '06

Bugs item #1495122, was opened at 2006-05-25 21:24 Message generated for change (Comment added) made by radiantskies 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 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: Bart Jacobs (radiantskies) Date: 2006-06-13 08: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-1504546 ] Subscription log mixes up names and email addresses
by SourceForge.net 12 Jun '06

12 Jun '06

Bugs item #1504546, was opened at 2006-06-12 04:19 Message generated for change (Settings changed) made by mnaumann You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1504546&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: (un)subscribing Group: 2.1 (stable) >Status: Closed >Resolution: Invalid Priority: 5 Submitted By: Moritz Naumann (mnaumann) Assigned to: Nobody/Anonymous (nobody) Summary: Subscription log mixes up names and email addresses Initial Comment: On /var/log/mailman/subscribe successful subscriptions are logged like this: Jun 11 18:40:58 2006 (30403) mylistname: new (digest) "henry23(a)hotmail.com" <Henry>, via web confirmation The intended way to log them is probably rather this: Jun 11 18:40:58 2006 (30403) mylistname: new (digest) "Henry" <henry23(a)hotmail.com>, via web confirmation Thanks! ---------------------------------------------------------------------- >Comment By: Moritz Naumann (mnaumann) Date: 2006-06-12 04:42 Message: Logged In: YES user_id=407680 This indeed refers to 2.1.7. And the patch you refer to should fix this. Thanks for the quick reply. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2006-06-12 04:35 Message: Logged In: YES user_id=1123998 What Mailman version is this? This error was fixed in 2.1.8 unless there is some other way it can occur. See http://svn.sourceforge.net/viewcvs.cgi/mailman/tags/Release_2_1_8/mailman/M… ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1504546&group_…

1 0

[ mailman-Bugs-1504546 ] Subscription log mixes up names and email addresses
by SourceForge.net 12 Jun '06

12 Jun '06

Bugs item #1504546, was opened at 2006-06-11 19:19 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1504546&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: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Moritz Naumann (mnaumann) Assigned to: Nobody/Anonymous (nobody) Summary: Subscription log mixes up names and email addresses Initial Comment: On /var/log/mailman/subscribe successful subscriptions are logged like this: Jun 11 18:40:58 2006 (30403) mylistname: new (digest) "henry23(a)hotmail.com" <Henry>, via web confirmation The intended way to log them is probably rather this: Jun 11 18:40:58 2006 (30403) mylistname: new (digest) "Henry" <henry23(a)hotmail.com>, via web confirmation Thanks! ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-06-11 19:35 Message: Logged In: YES user_id=1123998 What Mailman version is this? This error was fixed in 2.1.8 unless there is some other way it can occur. See http://svn.sourceforge.net/viewcvs.cgi/mailman/tags/Release_2_1_8/mailman/M… ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1504546&group_…

1 0

[ mailman-Bugs-1504546 ] Subscription log mixes up names and email addresses
by SourceForge.net 12 Jun '06

12 Jun '06

Bugs item #1504546, was opened at 2006-06-12 04:19 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=1504546&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: (un)subscribing Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Moritz Naumann (mnaumann) Assigned to: Nobody/Anonymous (nobody) Summary: Subscription log mixes up names and email addresses Initial Comment: On /var/log/mailman/subscribe successful subscriptions are logged like this: Jun 11 18:40:58 2006 (30403) mylistname: new (digest) "henry23(a)hotmail.com" <Henry>, via web confirmation The intended way to log them is probably rather this: Jun 11 18:40:58 2006 (30403) mylistname: new (digest) "Henry" <henry23(a)hotmail.com>, via web confirmation Thanks! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1504546&group_…

1 0

[ mailman-Feature Requests-782436 ] members per page on admin page
by SourceForge.net 11 Jun '06

11 Jun '06

Feature Requests item #782436, was opened at 2003-08-03 12:32 Message generated for change (Comment added) made by jwbaxter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=782436&group_i… 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: JC Dill (jcdill) Assigned to: Nobody/Anonymous (nobody) Summary: members per page on admin page Initial Comment: Put a radio button option on the membership page to allow list owners to change the number of members returned on each page. I suggest that the options include: 25 per page 50 per page 100 per page 200 per page 500 per page all subscribers on one page (use with caution if you have a big list!) ---------------------------------------------------------------------- Comment By: John W. Baxter (jwbaxter) Date: 2006-06-11 10:55 Message: Logged In: YES user_id=664644 This seems like a quite reasonable proposal. Is the intent to return to the old method, where the pages (except last) were all full and there was on each page an index of links giving the first (first and last) address on each other page? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=782436&group_i…

1 0

[ mailman-Bugs-1504204 ] re-confirm memberships
by SourceForge.net 11 Jun '06

11 Jun '06

Bugs item #1504204, was opened at 2006-06-10 19:32 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1504204&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: None >Status: Deleted >Resolution: Duplicate Priority: 5 Submitted By: Daevid Vincent (daevid) Assigned to: Nobody/Anonymous (nobody) Summary: re-confirm memberships Initial Comment: I have a suspicion that some of my lists' mails are not getting to their destinations. This could be that some people used their job email and no longer work there, could be that they are on AOL or hotmail (which seem to just silently discard), or could be just people that joined up and now 'junk mail or filter' the list because they're either to stupid or lazy to properly unsubscribe. Bottom line is that I'm paying per emails sent (via my quota on DynDNS) and I want to unsubscribe these dead members. It would be great if I could push a button in the web GUI (or run some command on the CLI) and mailman would reset every members status to 'unconfirmed' (or whatever it is), mail them a link to click (with some crazy code in it like when you join a list), and then mark the responders as 'confirmed'. Then after some period of time, say a week or so, I could then go into the GUI, click some link and see a list of all 'unconfirmed' people with the option to unsubscribe them all (without sending an email obviously, since the address is bogus). Extra points if I can schedule this task to occur every month, every six months, once a year, etc... (probably some 'day' interval would be sufficient here). ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2006-06-10 20:45 Message: Logged In: YES user_id=1123998 This is really an RFE, not a bug and it duplicates RFE 1495305. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1504204&group_…

1 0

[ mailman-Bugs-1504204 ] re-confirm memberships
by SourceForge.net 11 Jun '06

11 Jun '06

Bugs item #1504204, was opened at 2006-06-10 19:32 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=1504204&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: None Status: Open Resolution: None Priority: 5 Submitted By: Daevid Vincent (daevid) Assigned to: Nobody/Anonymous (nobody) Summary: re-confirm memberships Initial Comment: I have a suspicion that some of my lists' mails are not getting to their destinations. This could be that some people used their job email and no longer work there, could be that they are on AOL or hotmail (which seem to just silently discard), or could be just people that joined up and now 'junk mail or filter' the list because they're either to stupid or lazy to properly unsubscribe. Bottom line is that I'm paying per emails sent (via my quota on DynDNS) and I want to unsubscribe these dead members. It would be great if I could push a button in the web GUI (or run some command on the CLI) and mailman would reset every members status to 'unconfirmed' (or whatever it is), mail them a link to click (with some crazy code in it like when you join a list), and then mark the responders as 'confirmed'. Then after some period of time, say a week or so, I could then go into the GUI, click some link and see a list of all 'unconfirmed' people with the option to unsubscribe them all (without sending an email obviously, since the address is bogus). Extra points if I can schedule this task to occur every month, every six months, once a year, etc... (probably some 'day' interval would be sufficient here). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1504204&group_…

1 0