Mailman 3 October 2007 - Mailman-coders

[ mailman-Patches-657951 ] Generate RSS summary in archives
by SourceForge.net Aug. 19, 2022

Aug. 19, 2022

Patches item #657951, was opened at 2002-12-23 14:17 Message generated for change (Comment added) made by bwarsaw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i… Category: Pipermail Group: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 7 Submitted By: A.M. Kuchling (akuchling) Assigned to: Nobody/Anonymous (nobody) Summary: Generate RSS summary in archives Initial Comment: Here's a first-draft patch. Things that need fixing: * The generated RSS feed needs to be validated. (It passed the W3C's RDF validator, but RSS validators still need to be checked.) * The date should be given in YYYY-MM-DD format, which requires parsing the .fromdate attribute. * How do I get the URL for an archived message? The generated RSS currently just uses the filename, which is wrong. How do I get at the PUBLIC_ARCHIVE_URL setting? * Getting the most recent N postings is inefficient; the code loops through all of the archived messages and takes the last N of them. We could add .last() and .prev() methods to the Database class, but that's more ambitious for 2.1beta than I like. (Would be nice to get this into 2.1final...) * The list index page should have a LINK element pointing to the RSS file. Please make any comments you have, and I'll rework the patch accordingly. ---------------------------------------------------------------------- >Comment By: Barry A. Warsaw (bwarsaw) Date: 2003-04-18 18:43 Message: Logged In: YES user_id=12800 Andrew, to get the url for the archived message use mlist.GetBaseArchiveURL(), which knows about private vs. public archives, the host name and the list name. From there you should be able to tack on just the part of the path under "archives/private/listname". See Mailman/Handlers/Scrubber.py for an example. Only other minor comment: NUM_ARTICLES can probably go in Defaults.py.in ---------------------------------------------------------------------- Comment By: Justin Mason (jmason) Date: 2003-03-26 16:49 Message: Logged In: YES user_id=935 big thumbs up from me too. Much better solution than http://taint.org/mmrss/ ;) ---------------------------------------------------------------------- Comment By: Uche Ogbuji (uche) Date: 2003-03-17 20:09 Message: Logged In: YES user_id=38966 I'd like to add my vote to this item. This is a fantastic idea, Andrew. Thanks. --Uche ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 15:42 Message: Logged In: YES user_id=11375 Updated patch: * Dates are now rendered as ISO-8601 (date only, not the time of the message) * By hard-wiring 2002-December, I got the RSS to validate using Mark Pilgrim's validator. ---------------------------------------------------------------------- Comment By: captain larry (captainlarry) Date: 2002-12-23 14:36 Message: Logged In: YES user_id=147905 Just voting for support here. This is *great* thanks for the patch and I hope the maintainers include it as soon as it's appropriate :) Adam. ---------------------------------------------------------------------- Comment By: Barry A. Warsaw (bwarsaw) Date: 2002-12-23 14:27 Message: Logged In: YES user_id=12800 Deferring until post-2.1 ---------------------------------------------------------------------- Comment By: A.M. Kuchling (akuchling) Date: 2002-12-23 14:21 Message: Logged In: YES user_id=11375 Argh; SF choked on the file upload. Attaching the patch again... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=657951&group_i…

2 1

[ mailman-Feature Requests-1822565 ] Plain text option for nondigest
by SourceForge.net Oct. 31, 2007

Oct. 31, 2007

Feature Requests item #1822565, was opened at 2007-10-30 03:33 Message generated for change (Comment added) made by jimpop You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1822565&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 Private: No Submitted By: Cyndi (cyndi) Assigned to: Nobody/Anonymous (nobody) Summary: Plain text option for nondigest Initial Comment: I searched this to the best of my ability and there seems to be no current method to do it. I found this: http://www.mail-archive.com/mailman-users@python.org/msg36881.html and searched the feature requests, but it seems no one has submitted this yet, as far as I can tell. You have a plain-text option for subscribers to select if they receive the digest. I've tested it and it works perfectly. Messages that came through as HTML gobblygook in the nondigest will display as lovely plain text in the digest. What I would love is a plain-text option for the nondigest. Just exactly what you do for the digests, only post by post. Yahoogroups does it, as do many other mailing list sites/programs. It seems that currently I have only three choices: 1) Convert all posts to plain text. I can't get this to work right though (I am using a hosting service via my ISP, so they may not have all the prereqs, or I need to tweak it more myself). But this means people who want HTML can't get it. 2) Get MM to hold all HTML posts for moderation, then I send rejection notices insisting that people post in plain text only. This "works" but disenfranchises people with poor email skills or who use mailers/ISP's like AOL. I run a support group filled with people who have brain processing deficits, as well as those who simply don't understand computers. I've tried for years to get folks to post in plain text and most just can't. I finally gave up and hand-edited the HTML posts, but this isn't possible on MM (and I hate doing it). 3) Live with it. Most people have HTML-capable mailers (I'm an oldtimer holdout, but can switch). The problem is that some of my subscribers are blind or otherwise can't deal with HTML-formatted email (not all have converting software). A choice #4 (user option for nondigest plain text) would be wonderful. Thanks. ---------------------------------------------------------------------- Comment By: Jim Popovitch (jimpop) Date: 2007-10-31 02:39 Message: Logged In: YES user_id=3142 Originator: NO Hi Cyndi, First, I am a huge fan of Mailman as well as a long time administrator of a Mailman system. Now that I have said that, let me say that I agree with you that scrub_nondigest doesn't work the way you (nor I) feel it should. I leave it disabled on our systems. That said, what I think you need is something like demime before the email hits Mailman. I used that for years before deciding that HTML email would be ok for our lists. I do understand your situation is such that you don't have console access to the system, but perhaps you can ask your hosting provider to supply if for you. Again, I don't think that scrub_nondigest will do what you need, and there is little else in Mailman to change the overall format of incoming email messages. Best wishes. -Jim P. ---------------------------------------------------------------------- Comment By: Cyndi (cyndi) Date: 2007-10-31 02:23 Message: Logged In: YES user_id=1925111 Originator: YES If I miss a question, or don't give the answer you need, please ask again. Note that I say "HTML" when I really mean "HTML or MIME or related encodings." I am using Mailman on sonic.net. Version 2.1.9. I can't find more information than that...my guess is that it's being run on a unix box (or some flavor of linux). If it is modified, I don't know where or how. I started a mailman test list with 4 other volunteers from my current (majordomo) list so we can work out the kinks. I am subscribed under two addresses, so I have digest and nondigest. I use a non-HTML capable mailer for most of my work, though I have access to HTML/MIME-capable ones. My volunteers use various ISP's and mailers and mostly post in HTML. When someone posts to the test list in HTML, I get gobbygook in the individual posts. The readability varies, depending on their mailer and settings. Then I did my new subscription address and chose digest with plain text. The digests are completely readable with no HTML code or anything else like that. This includes digests made up of posts that were HTML/junk in nondigest mail. So the same emails are coming through differently in nondigest (no conversion) and digest (plain text conversion). When I tested the scrub_nondigest setting, the posts still went through, but the content was removed from any that were not sent in plain text. For example, this was the complete body of one message (the sender posted in HTML and included a small graphic as part of the test; the MM footer was appended correctly at the bottom, which I have removed here): An HTML attachment was scrubbed... URL: http://lists.sonic.net/mailman/private/immune-test/attachments/20071028/4b5… ml If you go to that URL, you'll see that the message is a complete mess. My plain text posts came through fine (just like they did before using the scrub_nondigest setting), but anything with HTML or a graphic got the treatment above. So, I turned the scrub_nondigest setting back off and went to the Content Filtering page. I turned it on and removed the attachment types but otherwise left defaults as is. I got errors similar to those with scrub_nondigest. Perhaps I need to put more of the defaults back in; I am willing to play with it if I can find some clear directions. If it would be helpful, I would be happy to forward emails to you from my tests. Or I could run new tests at your request. I've already posted to sonic.help.lists which is my ISP's internal newsgroup for MM issues (no replies on that topic yet). Thanks very much for your discussion and let me know if I failed to answer a question fully. Cyndi ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-10-30 23:15 Message: Logged In: YES user_id=1123998 Originator: NO Sorry. I didn't read the message you referenced in your original description. My bad. However, I don't understand why you say scrub_nondigest "was a total disaster" and regarding plain digests "I've tested it and it works perfectly." Exactly the same scrubber process is applied in both cases. Perhaps when you tested the digest, you looked at a multipart/alternative message and when you tested scrub_nondigest, you looked at an HTML only message. Or perhaps you are using someone else's modified Mailman. If so, perhaps you could convince them to abide by the terms of the GPL and submit their patches. As far as the scrubber links not working well is concerned, the only issue with current Mailman project Mailman that I am aware of is you have to log in if your archives are private. There are other issues I am aware of with some cPanel versions, but those are beyond our control. What problems did you have, and what Mailman version is this? HTML to plain text conversion relies on an external program (default lynx). In older versions of Mailman there were issues because quoted-printable and base64 encoded HTML was passed to the external program without decoding, but this was fixed in (I think) 2.1.7. As far as the request for an individual option is concerned, it is a valid request, but even though you seem convinced that we know how to do what you want for digests, I'm not convinced, so we need to resolve that first. Otherwise you may get a user option for something that you consider unsatisfactory. ---------------------------------------------------------------------- Comment By: Cyndi (cyndi) Date: 2007-10-30 22:24 Message: Logged In: YES user_id=1925111 Originator: YES Well, you yourself said that anyone wanting this ability to be per-user should submit a feature request here (see http://www.mail-archive.com/mailman-users@python.org/msg36881.html ). So I did. If it can be per user for digests, I don't see why not for nondigests, but you know the limitations of the software. I already tested the scrub_nondigest option and it was a total disaster. It didn't do any conversion. All it did was take all the text (along with any attachments) in the message and remove it, then put a link to where to find it. Even that didn't work well. I also tested the Content Filtering to do HTML conversion to plain text and it was even more of a disaster. I found some instructions that indicate it is very complex to setup, but my browser crashed so I'll have to look them up again. I think it might be possible to do HTML conversion on all the posts but only if my ISP agrees to do some stuff on their end. And it's not straightforward. For right now, I would be happy with a bug-free way to do conversions for the entire list. But I still think a feature where the user can choose HTML or plain text individual posts is a good thing. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-10-30 21:48 Message: Logged In: YES user_id=1123998 Originator: NO Perhaps you didn't search well enough, or perhaps we just hide or don't describe the option in these terms, but the Non-digest options->scrub_nondigest option in the list admin interface will do what you want. It will apply the same process that is applied to the plain digest to individual messages. The only problem is this is a list option, not an individual subscriber option. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1822565&group_…

1 0

[ mailman-Feature Requests-1822565 ] Plain text option for nondigest
by SourceForge.net Oct. 31, 2007

Oct. 31, 2007

Feature Requests item #1822565, was opened at 2007-10-30 00:33 Message generated for change (Comment added) made by cyndi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1822565&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 Private: No Submitted By: Cyndi (cyndi) Assigned to: Nobody/Anonymous (nobody) Summary: Plain text option for nondigest Initial Comment: I searched this to the best of my ability and there seems to be no current method to do it. I found this: http://www.mail-archive.com/mailman-users@python.org/msg36881.html and searched the feature requests, but it seems no one has submitted this yet, as far as I can tell. You have a plain-text option for subscribers to select if they receive the digest. I've tested it and it works perfectly. Messages that came through as HTML gobblygook in the nondigest will display as lovely plain text in the digest. What I would love is a plain-text option for the nondigest. Just exactly what you do for the digests, only post by post. Yahoogroups does it, as do many other mailing list sites/programs. It seems that currently I have only three choices: 1) Convert all posts to plain text. I can't get this to work right though (I am using a hosting service via my ISP, so they may not have all the prereqs, or I need to tweak it more myself). But this means people who want HTML can't get it. 2) Get MM to hold all HTML posts for moderation, then I send rejection notices insisting that people post in plain text only. This "works" but disenfranchises people with poor email skills or who use mailers/ISP's like AOL. I run a support group filled with people who have brain processing deficits, as well as those who simply don't understand computers. I've tried for years to get folks to post in plain text and most just can't. I finally gave up and hand-edited the HTML posts, but this isn't possible on MM (and I hate doing it). 3) Live with it. Most people have HTML-capable mailers (I'm an oldtimer holdout, but can switch). The problem is that some of my subscribers are blind or otherwise can't deal with HTML-formatted email (not all have converting software). A choice #4 (user option for nondigest plain text) would be wonderful. Thanks. ---------------------------------------------------------------------- >Comment By: Cyndi (cyndi) Date: 2007-10-30 23:23 Message: Logged In: YES user_id=1925111 Originator: YES If I miss a question, or don't give the answer you need, please ask again. Note that I say "HTML" when I really mean "HTML or MIME or related encodings." I am using Mailman on sonic.net. Version 2.1.9. I can't find more information than that...my guess is that it's being run on a unix box (or some flavor of linux). If it is modified, I don't know where or how. I started a mailman test list with 4 other volunteers from my current (majordomo) list so we can work out the kinks. I am subscribed under two addresses, so I have digest and nondigest. I use a non-HTML capable mailer for most of my work, though I have access to HTML/MIME-capable ones. My volunteers use various ISP's and mailers and mostly post in HTML. When someone posts to the test list in HTML, I get gobbygook in the individual posts. The readability varies, depending on their mailer and settings. Then I did my new subscription address and chose digest with plain text. The digests are completely readable with no HTML code or anything else like that. This includes digests made up of posts that were HTML/junk in nondigest mail. So the same emails are coming through differently in nondigest (no conversion) and digest (plain text conversion). When I tested the scrub_nondigest setting, the posts still went through, but the content was removed from any that were not sent in plain text. For example, this was the complete body of one message (the sender posted in HTML and included a small graphic as part of the test; the MM footer was appended correctly at the bottom, which I have removed here): An HTML attachment was scrubbed... URL: http://lists.sonic.net/mailman/private/immune-test/attachments/20071028/4b5… ml If you go to that URL, you'll see that the message is a complete mess. My plain text posts came through fine (just like they did before using the scrub_nondigest setting), but anything with HTML or a graphic got the treatment above. So, I turned the scrub_nondigest setting back off and went to the Content Filtering page. I turned it on and removed the attachment types but otherwise left defaults as is. I got errors similar to those with scrub_nondigest. Perhaps I need to put more of the defaults back in; I am willing to play with it if I can find some clear directions. If it would be helpful, I would be happy to forward emails to you from my tests. Or I could run new tests at your request. I've already posted to sonic.help.lists which is my ISP's internal newsgroup for MM issues (no replies on that topic yet). Thanks very much for your discussion and let me know if I failed to answer a question fully. Cyndi ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-10-30 20:15 Message: Logged In: YES user_id=1123998 Originator: NO Sorry. I didn't read the message you referenced in your original description. My bad. However, I don't understand why you say scrub_nondigest "was a total disaster" and regarding plain digests "I've tested it and it works perfectly." Exactly the same scrubber process is applied in both cases. Perhaps when you tested the digest, you looked at a multipart/alternative message and when you tested scrub_nondigest, you looked at an HTML only message. Or perhaps you are using someone else's modified Mailman. If so, perhaps you could convince them to abide by the terms of the GPL and submit their patches. As far as the scrubber links not working well is concerned, the only issue with current Mailman project Mailman that I am aware of is you have to log in if your archives are private. There are other issues I am aware of with some cPanel versions, but those are beyond our control. What problems did you have, and what Mailman version is this? HTML to plain text conversion relies on an external program (default lynx). In older versions of Mailman there were issues because quoted-printable and base64 encoded HTML was passed to the external program without decoding, but this was fixed in (I think) 2.1.7. As far as the request for an individual option is concerned, it is a valid request, but even though you seem convinced that we know how to do what you want for digests, I'm not convinced, so we need to resolve that first. Otherwise you may get a user option for something that you consider unsatisfactory. ---------------------------------------------------------------------- Comment By: Cyndi (cyndi) Date: 2007-10-30 19:24 Message: Logged In: YES user_id=1925111 Originator: YES Well, you yourself said that anyone wanting this ability to be per-user should submit a feature request here (see http://www.mail-archive.com/mailman-users@python.org/msg36881.html ). So I did. If it can be per user for digests, I don't see why not for nondigests, but you know the limitations of the software. I already tested the scrub_nondigest option and it was a total disaster. It didn't do any conversion. All it did was take all the text (along with any attachments) in the message and remove it, then put a link to where to find it. Even that didn't work well. I also tested the Content Filtering to do HTML conversion to plain text and it was even more of a disaster. I found some instructions that indicate it is very complex to setup, but my browser crashed so I'll have to look them up again. I think it might be possible to do HTML conversion on all the posts but only if my ISP agrees to do some stuff on their end. And it's not straightforward. For right now, I would be happy with a bug-free way to do conversions for the entire list. But I still think a feature where the user can choose HTML or plain text individual posts is a good thing. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-10-30 18:48 Message: Logged In: YES user_id=1123998 Originator: NO Perhaps you didn't search well enough, or perhaps we just hide or don't describe the option in these terms, but the Non-digest options->scrub_nondigest option in the list admin interface will do what you want. It will apply the same process that is applied to the plain digest to individual messages. The only problem is this is a list option, not an individual subscriber option. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1822565&group_…

1 0

[ mailman-Feature Requests-1822565 ] Plain text option for nondigest
by SourceForge.net Oct. 31, 2007

Oct. 31, 2007

Feature Requests item #1822565, was opened at 2007-10-30 00:33 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1822565&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 Private: No Submitted By: Cyndi (cyndi) Assigned to: Nobody/Anonymous (nobody) Summary: Plain text option for nondigest Initial Comment: I searched this to the best of my ability and there seems to be no current method to do it. I found this: http://www.mail-archive.com/mailman-users@python.org/msg36881.html and searched the feature requests, but it seems no one has submitted this yet, as far as I can tell. You have a plain-text option for subscribers to select if they receive the digest. I've tested it and it works perfectly. Messages that came through as HTML gobblygook in the nondigest will display as lovely plain text in the digest. What I would love is a plain-text option for the nondigest. Just exactly what you do for the digests, only post by post. Yahoogroups does it, as do many other mailing list sites/programs. It seems that currently I have only three choices: 1) Convert all posts to plain text. I can't get this to work right though (I am using a hosting service via my ISP, so they may not have all the prereqs, or I need to tweak it more myself). But this means people who want HTML can't get it. 2) Get MM to hold all HTML posts for moderation, then I send rejection notices insisting that people post in plain text only. This "works" but disenfranchises people with poor email skills or who use mailers/ISP's like AOL. I run a support group filled with people who have brain processing deficits, as well as those who simply don't understand computers. I've tried for years to get folks to post in plain text and most just can't. I finally gave up and hand-edited the HTML posts, but this isn't possible on MM (and I hate doing it). 3) Live with it. Most people have HTML-capable mailers (I'm an oldtimer holdout, but can switch). The problem is that some of my subscribers are blind or otherwise can't deal with HTML-formatted email (not all have converting software). A choice #4 (user option for nondigest plain text) would be wonderful. Thanks. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-10-30 20:15 Message: Logged In: YES user_id=1123998 Originator: NO Sorry. I didn't read the message you referenced in your original description. My bad. However, I don't understand why you say scrub_nondigest "was a total disaster" and regarding plain digests "I've tested it and it works perfectly." Exactly the same scrubber process is applied in both cases. Perhaps when you tested the digest, you looked at a multipart/alternative message and when you tested scrub_nondigest, you looked at an HTML only message. Or perhaps you are using someone else's modified Mailman. If so, perhaps you could convince them to abide by the terms of the GPL and submit their patches. As far as the scrubber links not working well is concerned, the only issue with current Mailman project Mailman that I am aware of is you have to log in if your archives are private. There are other issues I am aware of with some cPanel versions, but those are beyond our control. What problems did you have, and what Mailman version is this? HTML to plain text conversion relies on an external program (default lynx). In older versions of Mailman there were issues because quoted-printable and base64 encoded HTML was passed to the external program without decoding, but this was fixed in (I think) 2.1.7. As far as the request for an individual option is concerned, it is a valid request, but even though you seem convinced that we know how to do what you want for digests, I'm not convinced, so we need to resolve that first. Otherwise you may get a user option for something that you consider unsatisfactory. ---------------------------------------------------------------------- Comment By: Cyndi (cyndi) Date: 2007-10-30 19:24 Message: Logged In: YES user_id=1925111 Originator: YES Well, you yourself said that anyone wanting this ability to be per-user should submit a feature request here (see http://www.mail-archive.com/mailman-users@python.org/msg36881.html ). So I did. If it can be per user for digests, I don't see why not for nondigests, but you know the limitations of the software. I already tested the scrub_nondigest option and it was a total disaster. It didn't do any conversion. All it did was take all the text (along with any attachments) in the message and remove it, then put a link to where to find it. Even that didn't work well. I also tested the Content Filtering to do HTML conversion to plain text and it was even more of a disaster. I found some instructions that indicate it is very complex to setup, but my browser crashed so I'll have to look them up again. I think it might be possible to do HTML conversion on all the posts but only if my ISP agrees to do some stuff on their end. And it's not straightforward. For right now, I would be happy with a bug-free way to do conversions for the entire list. But I still think a feature where the user can choose HTML or plain text individual posts is a good thing. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-10-30 18:48 Message: Logged In: YES user_id=1123998 Originator: NO Perhaps you didn't search well enough, or perhaps we just hide or don't describe the option in these terms, but the Non-digest options->scrub_nondigest option in the list admin interface will do what you want. It will apply the same process that is applied to the plain digest to individual messages. The only problem is this is a list option, not an individual subscriber option. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1822565&group_…

1 0

[ mailman-Feature Requests-1822565 ] Plain text option for nondigest
by SourceForge.net Oct. 31, 2007

Oct. 31, 2007

Feature Requests item #1822565, was opened at 2007-10-30 00:33 Message generated for change (Comment added) made by cyndi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1822565&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 Private: No Submitted By: Cyndi (cyndi) Assigned to: Nobody/Anonymous (nobody) Summary: Plain text option for nondigest Initial Comment: I searched this to the best of my ability and there seems to be no current method to do it. I found this: http://www.mail-archive.com/mailman-users@python.org/msg36881.html and searched the feature requests, but it seems no one has submitted this yet, as far as I can tell. You have a plain-text option for subscribers to select if they receive the digest. I've tested it and it works perfectly. Messages that came through as HTML gobblygook in the nondigest will display as lovely plain text in the digest. What I would love is a plain-text option for the nondigest. Just exactly what you do for the digests, only post by post. Yahoogroups does it, as do many other mailing list sites/programs. It seems that currently I have only three choices: 1) Convert all posts to plain text. I can't get this to work right though (I am using a hosting service via my ISP, so they may not have all the prereqs, or I need to tweak it more myself). But this means people who want HTML can't get it. 2) Get MM to hold all HTML posts for moderation, then I send rejection notices insisting that people post in plain text only. This "works" but disenfranchises people with poor email skills or who use mailers/ISP's like AOL. I run a support group filled with people who have brain processing deficits, as well as those who simply don't understand computers. I've tried for years to get folks to post in plain text and most just can't. I finally gave up and hand-edited the HTML posts, but this isn't possible on MM (and I hate doing it). 3) Live with it. Most people have HTML-capable mailers (I'm an oldtimer holdout, but can switch). The problem is that some of my subscribers are blind or otherwise can't deal with HTML-formatted email (not all have converting software). A choice #4 (user option for nondigest plain text) would be wonderful. Thanks. ---------------------------------------------------------------------- >Comment By: Cyndi (cyndi) Date: 2007-10-30 19:24 Message: Logged In: YES user_id=1925111 Originator: YES Well, you yourself said that anyone wanting this ability to be per-user should submit a feature request here (see http://www.mail-archive.com/mailman-users@python.org/msg36881.html ). So I did. If it can be per user for digests, I don't see why not for nondigests, but you know the limitations of the software. I already tested the scrub_nondigest option and it was a total disaster. It didn't do any conversion. All it did was take all the text (along with any attachments) in the message and remove it, then put a link to where to find it. Even that didn't work well. I also tested the Content Filtering to do HTML conversion to plain text and it was even more of a disaster. I found some instructions that indicate it is very complex to setup, but my browser crashed so I'll have to look them up again. I think it might be possible to do HTML conversion on all the posts but only if my ISP agrees to do some stuff on their end. And it's not straightforward. For right now, I would be happy with a bug-free way to do conversions for the entire list. But I still think a feature where the user can choose HTML or plain text individual posts is a good thing. ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-10-30 18:48 Message: Logged In: YES user_id=1123998 Originator: NO Perhaps you didn't search well enough, or perhaps we just hide or don't describe the option in these terms, but the Non-digest options->scrub_nondigest option in the list admin interface will do what you want. It will apply the same process that is applied to the plain digest to individual messages. The only problem is this is a list option, not an individual subscriber option. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1822565&group_…

1 0

[ mailman-Feature Requests-1822565 ] Plain text option for nondigest
by SourceForge.net Oct. 31, 2007

Oct. 31, 2007

Feature Requests item #1822565, was opened at 2007-10-30 00:33 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1822565&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 Private: No Submitted By: Cyndi (cyndi) Assigned to: Nobody/Anonymous (nobody) Summary: Plain text option for nondigest Initial Comment: I searched this to the best of my ability and there seems to be no current method to do it. I found this: http://www.mail-archive.com/mailman-users@python.org/msg36881.html and searched the feature requests, but it seems no one has submitted this yet, as far as I can tell. You have a plain-text option for subscribers to select if they receive the digest. I've tested it and it works perfectly. Messages that came through as HTML gobblygook in the nondigest will display as lovely plain text in the digest. What I would love is a plain-text option for the nondigest. Just exactly what you do for the digests, only post by post. Yahoogroups does it, as do many other mailing list sites/programs. It seems that currently I have only three choices: 1) Convert all posts to plain text. I can't get this to work right though (I am using a hosting service via my ISP, so they may not have all the prereqs, or I need to tweak it more myself). But this means people who want HTML can't get it. 2) Get MM to hold all HTML posts for moderation, then I send rejection notices insisting that people post in plain text only. This "works" but disenfranchises people with poor email skills or who use mailers/ISP's like AOL. I run a support group filled with people who have brain processing deficits, as well as those who simply don't understand computers. I've tried for years to get folks to post in plain text and most just can't. I finally gave up and hand-edited the HTML posts, but this isn't possible on MM (and I hate doing it). 3) Live with it. Most people have HTML-capable mailers (I'm an oldtimer holdout, but can switch). The problem is that some of my subscribers are blind or otherwise can't deal with HTML-formatted email (not all have converting software). A choice #4 (user option for nondigest plain text) would be wonderful. Thanks. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-10-30 18:48 Message: Logged In: YES user_id=1123998 Originator: NO Perhaps you didn't search well enough, or perhaps we just hide or don't describe the option in these terms, but the Non-digest options->scrub_nondigest option in the list admin interface will do what you want. It will apply the same process that is applied to the plain digest to individual messages. The only problem is this is a list option, not an individual subscriber option. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1822565&group_…

1 0

[ mailman-Feature Requests-1822565 ] Plain text option for nondigest
by SourceForge.net Oct. 30, 2007

Oct. 30, 2007

Feature Requests item #1822565, was opened at 2007-10-30 00:33 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1822565&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 Private: No Submitted By: Cyndi (cyndi) Assigned to: Nobody/Anonymous (nobody) Summary: Plain text option for nondigest Initial Comment: I searched this to the best of my ability and there seems to be no current method to do it. I found this: http://www.mail-archive.com/mailman-users@python.org/msg36881.html and searched the feature requests, but it seems no one has submitted this yet, as far as I can tell. You have a plain-text option for subscribers to select if they receive the digest. I've tested it and it works perfectly. Messages that came through as HTML gobblygook in the nondigest will display as lovely plain text in the digest. What I would love is a plain-text option for the nondigest. Just exactly what you do for the digests, only post by post. Yahoogroups does it, as do many other mailing list sites/programs. It seems that currently I have only three choices: 1) Convert all posts to plain text. I can't get this to work right though (I am using a hosting service via my ISP, so they may not have all the prereqs, or I need to tweak it more myself). But this means people who want HTML can't get it. 2) Get MM to hold all HTML posts for moderation, then I send rejection notices insisting that people post in plain text only. This "works" but disenfranchises people with poor email skills or who use mailers/ISP's like AOL. I run a support group filled with people who have brain processing deficits, as well as those who simply don't understand computers. I've tried for years to get folks to post in plain text and most just can't. I finally gave up and hand-edited the HTML posts, but this isn't possible on MM (and I hate doing it). 3) Live with it. Most people have HTML-capable mailers (I'm an oldtimer holdout, but can switch). The problem is that some of my subscribers are blind or otherwise can't deal with HTML-formatted email (not all have converting software). A choice #4 (user option for nondigest plain text) would be wonderful. Thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1822565&group_…

1 0

[ mailman-Bugs-1822121 ] notification e-mail and web interface out of sync
by SourceForge.net Oct. 30, 2007

Oct. 30, 2007

Bugs item #1822121, was opened at 2007-10-29 14:20 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=1822121&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 Private: No Submitted By: hammerandtongs (hammerandtongs) Assigned to: Nobody/Anonymous (nobody) Summary: notification e-mail and web interface out of sync Initial Comment: When a list adminstration asks for daily (say) e-mail notification of all pending messages awaiting moderation, the resulting e-mail lists those messages in time-forward order (and succinctly). By contrast, the web interface lists all pending messages awaiting moderation in author-alphabetic order (and verbosely). For a busy list, this makes the mail useless as one must, for a second time, read through the (verbose) list of messages looking for what you want to save while you delete the 95% spam. (Busy here means >100 spams per day.) If the interface for deleting it is in time forward order, then one can actually say "All entries through 9:34am can be deleted" even if the effect is limited to confirming that what was in the e-mail notification and what is displayed on the web interface are the same or not. If the interface is in alphabetic order by author, then newly arrived spam is inserted at an arbiitrary location into the list. As such, even a page reload means you have to start over from the top. Note that the ~mailman account is *NOT* available to list managers at this site (mit.edu), so such things as http://www.python.org/cgi-bin/faqw-mm.py?req=all#4.74 are irrelevant. Yours, H&T ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1822121&group_…

1 0

[ mailman-Feature Requests-1820727 ] Allow non-list members to approve their moderated messages.
by SourceForge.net Oct. 27, 2007

Oct. 27, 2007

Feature Requests item #1820727, was opened at 2007-10-26 10:18 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1820727&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 Private: No Submitted By: robbt (robbt) Assigned to: Nobody/Anonymous (nobody) Summary: Allow non-list members to approve their moderated messages. Initial Comment: I just had the idea when I was working with a mailman list when I get a lot of SPAM e-mails to it because we accept e-mails from non-members. A simple workaround that would prevent spammers and also take the load off of a moderator would be to create an option for moderation where someone who has their e-mail moderated for not being on the list could click onto the site and approve their own message. This option would be really useful for people who want to have open lists such as tech-support for opensource projects but don't want to be barraged with SPAM. Viva Opensource ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1820727&group_…

1 0

[ mailman-Patches-1798683 ] SMTP authentication and TLS support
by SourceForge.net Oct. 22, 2007

Oct. 22, 2007

Patches item #1798683, was opened at 2007-09-20 13:14 Message generated for change (Comment added) made by tsmetana You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1798683&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: Mailman 2.2 / 3.0 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Tomas Smetana (tsmetana) Assigned to: Nobody/Anonymous (nobody) Summary: SMTP authentication and TLS support Initial Comment: Hi, here's a patch for Mailman 2.x that enables it using SMTP AUTH and TLS connection. This features might be useful on more paranoid SMTP servers. ---------------------------------------------------------------------- >Comment By: Tomas Smetana (tsmetana) Date: 2007-10-22 08:59 Message: Logged In: YES user_id=1869522 Originator: YES You're right, I forgot to define SMTP_HELO_HOST. I'm uploading the updated patch. File Added: mailman-smtpauth.patch ---------------------------------------------------------------------- Comment By: Mark Sapiro (msapiro) Date: 2007-10-21 06:44 Message: Logged In: YES user_id=1123998 Originator: NO The patch seems good except if SMTP_USE_TLS is set True in mm_cfg.py, the patch references mm_cfg.SMTP_HELO_HOST which is neither defined nor documented in the patch. Perhaps the patch to Defaults.py.in should include something like SMTP_HELO_HOST = DEFAULT_EMAIL_HOST or even SMTP_HELO_HOST = '' and some comments describing what all the new variables are. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1798683&group_…

1 0