[Mailman-Users] Replying to digests
Hello, I'm in the process of setting up Mailman for a discussion group of about 100 members. From past experience, I know some people will prefer to have digest but they'll also probably just hit the reply button without editing the subject or deleting anything automatically included. I think this will mean their replies will contain the entire digest: difficult to work out which message they're replying to and using archive space on the server. 1. How do I stop this happening? At the moment, the only thing I can think of is to filter out messages containing digest in the subject line and hold those for moderation. 2. Can I also filter messages with digest in the body? I can't see where to do this in the administrative interface. 3. When I'm reviewing a message held for moderation, can I edit it to remove unwanted bits of the digest? I need to do this without altering the sender's details so members know the message is from them and not from me? When I click on the message in the moderation queue, I can see a message excerpt but can't see how to edit it. 4. If messages have got through with lots of unwanted text, is it possible for me to edit them in the archive? Otherwise my archive may be unnecessarily large and I can't afford endless server space. Thanks for your help. Clare -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Archive access Forbidden
Thank you in advance for replies. The list is now working fine however access to the archive is blocked : From: http://www.vizion2000.net/mailman/listinfo/bps_comps_print_announce On line: To see collection of prior postings to the list, visit the clicking link for bps_comps_print_announce Archives goes to: http://www.vizion2000.net/pipermail/bps_comps_print_announce/ with result: Forbidden You don't have permission to access/pipermail/bps_comps_print_announce/ on this server Attempt to view archives from Topic Section of the mailing list administration page using link for Go to list archives also fails Extract from httpd-error.log [Tue Dec 29 12:50:12 2009] [error] [client 62.49.197.51] attempt to invoke directory as script: /usr/local/mailman/cgi-bin/ [Tue Dec 29 12:50:47 2009] [error] [client 62.49.197.51] Symbolic link not allowed or link target not accessible: /usr/local/mailman/archives/public/bps_comps_print_announce, referer: http://www.vizion2000.net/mailman/listinfo/bps_comps_print_announce Extract from httpd.conf ScriptAlias /mailman /usr/local/mailman/cgi-bin Directory /usr/local/mailman Options FollowSymLinks ExecCGI AllowOverride None Order allow,deny Allow from all /Directory ScriptAlias /pipermail /usr/local/mailman/archives/public Directory /usr/local/mailman/archives/public Options FollowSymLinks ExecCGI AllowOverride None Order allow,deny Allow from all Options Indexes MultiViews AddDefaultCharset Off /Directory dns1# pwd /usr/local/mailman dns1# ls -l total 36 drwxrwsr-x 11 mailman mailman 2048 Dec 29 09:03 Mailman drwxrwsr-x 4 www www 512 Dec 28 13:07 archives drwxrwsr-x 2 root mailman 1024 Dec 28 13:07 bin drwxrwsr-x 2 root mailman 512 Dec 28 13:07 cgi-bin drwxrwsr-x 2 root mailman 512 Dec 28 13:07 cron drwxrwsr-x 2 mailman mailman 512 Dec 28 15:54 data drwxrwsr-x 2 root mailman 512 Dec 28 13:07 icons drwxrwsr-x 6 mailman mailman 512 Dec 28 15:45 lists drwxrwsr-x 2 root mailman 512 Dec 29 14:00 locks drwxrwsr-x 2 mailman mailman 512 Dec 29 09:04 logs drwxrwsr-x 2 root mailman 512 Dec 28 13:07 mail drwxrwsr-x 37 root mailman 512 Dec 28 13:07 messages drwxrwsr-x 5 root mailman 512 Dec 28 13:07 pythonlib drwxrwsr-x 11 mailman mailman 512 Dec 28 15:54 qfiles drwxrwsr-x 2 root mailman 512 Dec 28 13:07 scripts drwxrwsr-x 2 root mailman 512 Dec 28 13:07 spam drwxrwsr-x 38 root mailman 512 Dec 28 13:07 templates drwxrwsr-x 4 root mailman 512 Dec 28 13:07 tests dns1# cd archives dns1# ls -l total 4 drwxrws--- 10 www www 512 Dec 28 15:45 private drwxrwsr-x 2 www www 512 Dec 28 15:46 public dns1# cd private dns1# ls -l total 16 drwxrwsr-x 2 www www 512 Dec 19 17:58 bps_comp_print_chat drwxrwsr-x 2 www www 512 Dec 19 17:58 bps_comp_print_chat.mbox drwxrwsr-x 2 www www 512 Dec 19 17:57 bps_comp_print_reminders drwxrwsr-x 2 www www 512 Dec 19 17:57 bps_comp_print_reminders.mbox drwxrwsr-x 4 www www 512 Dec 29 03:27 bps_comps_print_announce drwxrwsr-x 2 www www 512 Dec 28 15:54 bps_comps_print_announce.mbox drwxrwsr-x 2 www www 512 Dec 28 15:45 mailman drwxrwsr-x 2 www www 512 Dec 28 15:45 mailman.mbox dns1# cd ../public dns1# ls -l total 0 lrwxr-xr-x 1 www www 55 Dec 19 17:58 bps_comp_print_chat - /usr/local/mailman/archives/private/bps_comp_print_chat lrwxr-xr-x 1 www www 60 Dec 19 17:57 bps_comp_print_reminders - /usr/local/mailman/archives/private/bps_comp_print_reminders lrwxr-xr-x 1 www www 60 Dec 19 17:56 bps_comps_print_announce - /usr/local/mailman/archives/private/bps_comps_print_announce dns1# cd /usr/local/mailman/archives/private/bps_comps_print_announce dns1# ls -l total 14 drwxrwsr-x 2 www www 512 Dec 28 15:54 2009-December -rw-rw-r-- 1 www www 2870 Dec 28 15:54 2009-December.txt -rw-rw-r-- 1 www www 1356 Dec 29 03:27 2009-December.txt.gz drwxrws--- 2 www www 512 Dec 28 15:54 database -rw-rw-r-- 1 www www 1110 Dec 28 15:54 index.html -rw-rw 1 www www 870 Dec 28 15:54 pipermail.pck dns1# Thanks in advance ___ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Replying to digests
Clare Redstone wrote: I'm in the process of setting up Mailman for a discussion group of about 100 members. From past experience, I know some people will prefer to have digest but they'll also probably just hit the reply button without editing the subject or deleting anything automatically included. I think this will mean their replies will contain the entire digest: difficult to work out which message they're replying to and using archive space on the server. 1. How do I stop this happening? At the moment, the only thing I can think of is to filter out messages containing digest in the subject line and hold those for moderation. You can do that with Privacy options ... - Spam filters - header_filter_rules, or you can just moderate all members or all digest members and reject their posts until they learn. You can also set General Options - max_message_size small enough to catch these. In particular, if digests are triggered on size only, you should be able to find a sweet spot that will catch all quoted digests but not most 'good' posts. 2. Can I also filter messages with digest in the body? I can't see where to do this in the administrative interface. No. Filtering on anything in the message body requires a custom handler. See the FAQ at http://wiki.list.org/x/l4A9. 3. When I'm reviewing a message held for moderation, can I edit it to remove unwanted bits of the digest? I need to do this without altering the sender's details so members know the message is from them and not from me? When I click on the message in the moderation queue, I can see a message excerpt but can't see how to edit it. Without source modifications, you can't edit a held message from the admindb interface. What you can do depends on your MUA. I do the following occasionally (when a quoted digest is held for size). I have admin_immed_notify set to yes, so I receive a notice containing the post as part 2 of 3 message parts. First, I discard the original held message. Then, using Mutt, I open the notice and then the message/rfc822 part containing the post, edit it and then 'bounce' it to the list. 'Bounce' is Mutt's term for resending the original message to additional recipients. This is not forwarding; it is resending with the original headers. Not all MUAs can do this. Also see the FAQ at http://wiki.list.org/x/24A9. OTOH, you'll get more mileage in the long run by rejecting the post and requiring the user to generate a proper reply. 4. If messages have got through with lots of unwanted text, is it possible for me to edit them in the archive? Otherwise my archive may be unnecessarily large and I can't afford endless server space. This requires shell access to the server. See the FAQ at http://wiki.list.org/x/OAB0. (Note: These days, file space is a lot cheaper than your time to do this, even if you do it as a hobby.) Also note that if the members subscribe to the MIME format digest (make it the default), many MUAs allow opening an individual message from the digest and replying to it alone. It might be easier to train your users if they have this ability. Aside: I would think this behavior would be self correcting as it renders digests (particularly plain format digests) virtually unreadable, but the ability of users to blindly act in opposition to their own interests continues to amaze me. I guess that when replying to the current digest, the readability of the next digest is what economists call an externality. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Archive access Forbidden
David Southwell wrote: Thank you in advance for replies. The list is now working fine however access to the archive is blocked [...] dns1# pwd /usr/local/mailman dns1# ls -l total 36 drwxrwsr-x 11 mailman mailman 2048 Dec 29 09:03 Mailman drwxrwsr-x 4 www www 512 Dec 28 13:07 archives This and everything subordinate to it needs to be group mailman. drwxrwsr-x 2 root mailman 1024 Dec 28 13:07 bin drwxrwsr-x 2 root mailman 512 Dec 28 13:07 cgi-bin drwxrwsr-x 2 root mailman 512 Dec 28 13:07 cron drwxrwsr-x 2 mailman mailman 512 Dec 28 15:54 data drwxrwsr-x 2 root mailman 512 Dec 28 13:07 icons drwxrwsr-x 6 mailman mailman 512 Dec 28 15:45 lists drwxrwsr-x 2 root mailman 512 Dec 29 14:00 locks drwxrwsr-x 2 mailman mailman 512 Dec 29 09:04 logs drwxrwsr-x 2 root mailman 512 Dec 28 13:07 mail drwxrwsr-x 37 root mailman 512 Dec 28 13:07 messages drwxrwsr-x 5 root mailman 512 Dec 28 13:07 pythonlib drwxrwsr-x 11 mailman mailman 512 Dec 28 15:54 qfiles drwxrwsr-x 2 root mailman 512 Dec 28 13:07 scripts drwxrwsr-x 2 root mailman 512 Dec 28 13:07 spam drwxrwsr-x 38 root mailman 512 Dec 28 13:07 templates drwxrwsr-x 4 root mailman 512 Dec 28 13:07 tests dns1# cd archives dns1# ls -l total 4 drwxrws--- 10 www www 512 Dec 28 15:45 private The owner of archives/private needs to be the user the web server runs as. I would think that would be 'www', but then I don't understand why public archive access doesn't work. See http://www.list.org/mailman-install/node9.html for info on archives/private. Normally, it is o+x, but if not, it needs to be owned by the web server user but still group mailman. check_perms should fix a lot of this, but you may also need to do chggrp -R mailman /usr/local/mailman/archives/ and possibly for d in `find /usr/local/mailman/archives/ -type d -print` ; do chmod g+s $d done With the ownership and permissions you have here, Mailman shouldn't be able to even store anything in the archives. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Archive access Forbidden
-Original Message- From: mailman-users-bounces+s.watkins=nhm.ac...@python.org [mailto:mailman-users-bounces+s.watkins=nhm.ac...@python.org] On Behalf Of David Southwell Sent: 29 December 2009 15:04 To: mailman-users@python.org Subject: [Mailman-Users] Archive access Forbidden with result: Forbidden You don't have permission to access/pipermail/bps_comps_print_announce/ on this server Attempt to view archives from Topic Section of the mailing list administration page using link for Go to list archives also fails Extract from httpd-error.log [Tue Dec 29 12:50:12 2009] [error] [client 62.49.197.51] attempt to invoke directory as script: /usr/local/mailman/cgi-bin/ [Tue Dec 29 12:50:47 2009] [error] [client 62.49.197.51] Symbolic link not allowed or link target not accessible: /usr/local/mailman/archives/public/bps_comps_print_announce, referer: http://www.vizion2000.net/mailman/listinfo/bps_comps_print_announce Extract from httpd.conf ScriptAlias /mailman /usr/local/mailman/cgi-bin Directory /usr/local/mailman Options FollowSymLinks ExecCGI AllowOverride None Order allow,deny Allow from all /Directory ScriptAlias /pipermail /usr/local/mailman/archives/public Directory /usr/local/mailman/archives/public Options FollowSymLinks ExecCGI AllowOverride None Order allow,deny Allow from all Options Indexes MultiViews AddDefaultCharset Off /Directory Hi, I'm guessing that the directory indexing mechanism of Apache is getting confused. The line ScriptAlias /pipermail /usr/local/mailman/archives/public tells apache that anything with a URI starting with /pipermail is a script, so Apache will take any call to that URI as a call for an exectuable. Looking at my local setup I see that the only indexing material in the 'archive/public' subdirectories are the file index.html. So you have to configure Apache to look for index.html as the indexing mechanism within a script only directory. Something like: Directory /usr/local/mailman/archives/public DirectoryIndex index.html /Directory should do the trick. Don't forget to restart Apache after adding that line. HTH, S Watkins -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Archive access Forbidden
Steff Watkins wrote: I'm guessing that the directory indexing mechanism of Apache is getting confused. The line ScriptAlias /pipermail /usr/local/mailman/archives/public tells apache that anything with a URI starting with /pipermail is a script, so Apache will take any call to that URI as a call for an exectuable. Good catch! I missed that. It should be Alias /pipermail /usr/local/mailman/archives/public not ScriptAlias. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Archive access Forbidden
Steff Watkins wrote: I'm guessing that the directory indexing mechanism of Apache is getting confused. The line ScriptAlias /pipermail /usr/local/mailman/archives/public tells apache that anything with a URI starting with /pipermail is a script, so Apache will take any call to that URI as a call for an exectuable. Good catch! I missed that. It should be Alias /pipermail /usr/local/mailman/archives/public not ScriptAlias. OK guys -- thank you everyone BUT BUT still no success I changed the entries in httpd.conf and restarted the server but still get the same result. As a matter of curiosity I tried http://www.vizion2000.net/pipermail which simply gave me a page Index of /pipermail . Parent Directory Following the link Parent Directory took me to http://www.vizion2000.net/ So we know the Alias pipermail line in httpd.conf is being read but we still get no further. It seems there must be something wrong with the httpd.conf so I am reposting it as it now stands: Options Indexes FollowSymLinks # # AllowOverride controls what directives may be placed in .htaccess files. # It can be All, None, or any combination of the keywords: # Options FileInfo AuthConfig Limit # AllowOverride None # # Controls who can get stuff from this server. # Order allow,deny Allow from all /Directory ScriptAlias /mailman /usr/local/mailman/cgi-bin Directory /usr/local/mailman Options FollowSymLinks ExecCGI AllowOverride None Order allow,deny Allow from all /Directory Alias /pipermail /usr/local/mailman/archives/public Directory /usr/local/mailman/archives/public/ Options FollowSymLinks ExecCGI AllowOverride None Order allow,deny Allow from all Options Indexes MultiViews AddDefaultCharset Off DirectoryIndex index.html /Directory -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Replying to digests
On 2009-12-29, Mark Sapiro (m...@msapiro.net) wrote: Also note that if the members subscribe to the MIME format digest (make it the default), many MUAs allow opening an individual message from the digest and replying to it alone. It might be easier to train your users if they have this ability. I don't recall where, but I have seen some digest lists that actually have Reply/Forward 'links' for each message in the digest in the included 'headers' of each individual message in the digest. Using these links creates a reply identical to one that would be generated if the message had been received individually. Any chance of Mailman ever being able to do that? Or is that what you are talking about with the MIME format digest? -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Archive access Forbidden
-Original Message- From: David Southwell [mailto:da...@vizion2000.net] Sent: 29 December 2009 16:23 To: mailman-users@python.org Cc: Mark Sapiro; Steff Watkins Subject: Re: [Mailman-Users] Archive access Forbidden OK guys -- thank you everyone BUT BUT Alias /pipermail /usr/local/mailman/archives/public Directory /usr/local/mailman/archives/public/ Options FollowSymLinks ExecCGI AllowOverride None Order allow,deny Allow from all Options Indexes MultiViews AddDefaultCharset Off DirectoryIndex index.html /Directory Errm... suggestion... tidy up! :) AFAIK Apache doesn't allow you to just sequently add Options lines together. If I've read it correctly, the Options Indexes MultiViews would cancel the Options FollowSymLinks ExecCGI as it is a later instruction.. I could be wrong on that, been a while since I went grubbing around in Apache's mechanics. My own setup for this looks like: Alias /pipermail/ /usr/local/mailman/archives/public/ Directory /usr/local/mailman/archives/public Options FollowSymLinks AllowOverride None Order allow,deny Allow from all /Directory No Indexes, no Multiviews and definitely No ExecCGI. Something just makes me feels queasy about making a web archive of a public mailing list in a way that it might be possible to have someone include a script in the mail that may have an ever so slight chance of executing. You're not running SSIs, are you? Really, make life as easy as possible for yourself. K.I.S.S... Kiss It Simple, Sunshine! As simple as you can possibly get away with. One other problem with this is that we only see the relevent part of the httpd.conf file. I am not knocking you for that, security minded people work on the idea of least-disclosed the better. Problem is that there may be a directive in some other part of the httpd.conf file which totally banjaxs your mailman setup. Are you in a position to run a test instance of the webserver, say on something like port 8080 with a totally plain-vanilla stock httpd.conf file? You could then inject the mailman configuration into that and see what is needed to make it work. If you then inject those changes into your standard (port 80) httpd.conf and they still fail, you would at least know that there was some directive in the original webserver setup that was playing havok with your mailman setup. Regards, S Watkins -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Archive access Forbidden
Steff Watkins wrote: From: David Southwell [mailto:da...@vizion2000.net]=20 OK guys -- thank you everyone BUT BUT Alias /pipermail /usr/local/mailman/archives/public Directory /usr/local/mailman/archives/public/ Options FollowSymLinks ExecCGI AllowOverride None Order allow,deny Allow from all Options Indexes MultiViews AddDefaultCharset Off DirectoryIndex index.html /Directory Errm... suggestion... tidy up! :) AFAIK Apache doesn't allow you to just sequently add Options lines together. If I've read it correctly, the Options Indexes MultiViews would cancel the Options FollowSymLinks ExecCGI as it is a later instruction.. I could be wrong on that, been a while since I went grubbing around in Apache's mechanics. That is correct. You can add options with a + as in Options FollowSymLinks ExecCGI Options +Indexes +MultiViews but without + to add or - to take away, The options will replace any prior options. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Replying to digests
Tanstaafl wrote: I don't recall where, but I have seen some digest lists that actually have Reply/Forward 'links' for each message in the digest in the included 'headers' of each individual message in the digest. Using these links creates a reply identical to one that would be generated if the message had been received individually. This sounds like something with a web based 'archive' that allows replying/forwarding via the web. Any chance of Mailman ever being able to do that? Or is that what you are talking about with the MIME format digest? The MIME format digest does allow something like this if your MUA supports it, but I don't think it's what you're talking about. MM3 will have more flexibility to enable doing things like this. You may eventually see it in MM 3. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Replying to digests
On 2009-12-29 1:43 PM, Mark Sapiro wrote: Tanstaafl wrote: I don't recall where, but I have seen some digest lists that actually have Reply/Forward 'links' for each message in the digest in the included 'headers' of each individual message in the digest. Using these links creates a reply identical to one that would be generated if the message had been received individually. This sounds like something with a web based 'archive' that allows replying/forwarding via the web. No, it was definitely in an HTML formatted digest list... But now that I think about it, I may be mistaken about the resulting reply being the same... ok, I just went and looked - it was Yahoo Group Digest messages... I really like the way these digests work. You can click on a message in the summary at the top and it scrolls down to that message. Then it has 'Reply to sender' and 'Reply to Group' links, as well as a 'Back to top' link at the bottom of each message which makes it easy to get back to the summary if you are cherry picking which messages you want to read - *very* useful for busy lists that have a lot of messages. It does reply with the correct Subject when you use those links, but it does *not* generate In-Reply-To headers, which is the only shortcoming I can see. Any chance of Mailman ever being able to do that? Or is that what you are talking about with the MIME format digest? The MIME format digest does allow something like this if your MUA supports it, but I don't think it's what you're talking about. MM3 will have more flexibility to enable doing things like this. You may eventually see it in MM 3. As one who does not hate HTML messages like some people do - especially for things like this where the HTML code can provide extremely useful behavior like this - I really do hope that Mailman can (will) be extended with this kind of functionality some day. -- Best regards, Charles -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Replying to digests
it was Yahoo Group Digest messages... I really like the way these digests work. You can click on a message in the summary at the top and it scrolls down to that message. Yes, that was the first thing I noticed, trying out the Mailman digest - that it doesn't do this, so takes a bit longer viewing messages in a digest. Then it has 'Reply to sender' and 'Reply to Group' links, as well as a 'Back to top' link at the bottom of each message which makes it easy to get back to the summary if you are cherry picking which messages you want to read - *very* useful for busy lists that have a lot of messages. I'd forgotten about the reply to links the Yahoo digests have as well. The Mailman MIME digest works pretty well for me in Outlook 2007. One attachment has the list of messages, then each message is a separate attachment so can be viewed and replied to individually. Keeping correct subject. It doesn't work in Yahoo Mail though :( I'd be very happy if digests in the next MM can be navigated and replied to individually with ease. In the mean time, I'll follow Mark's suggestions. (Those I can work out how to do!) Clare -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Replying to digests
Thanks for this very helpful reply, Mark. I'm going to follow your advice and mainly aim at training members. I do want to be flexible about this though: some infrequent posters have some very good things to say that will help us all. But they're also probably more likely to be a bit computer-fearful and want digests because busy inboxes confound them but not be aware of editing subject and body. I really don't want to be so strict that I frighten them off posting. So: Step 1a, filtering digest from headers will pick up most and I'll send those back to members to clean up for themselves. (But sometimes do what I can myself-see below.) Step 1b, I'll set default as MIME which will help in some cases, depending on MUA. Step 2, set repeat offenders to moderate, or if it's a widespread problem, every now and then check through the subscriber list and set all digest people to moderate. I might exceptionally see if I can edit and resend messages when I think it's particularly worth it and the sender likely to be flummoxed by being asked to clean and resend. I'm having trouble following the instructions though. I use Outlook 2007 on Windows XP so don't have Mutt. What you can do depends on your MUA. I do the following occasionally (when a quoted digest is held for size). I have admin_immed_notify set to yes, so I receive a notice containing the post as part 2 of 3 message parts. First, I discard the original held message. Then, using Mutt, I open the notice and then the message/rfc822 part containing the post, edit it... In Outlook, I get an email telling me there's a message waiting for authorisation, with 2 attachments: one called by the post subject and the other called confirm 2ff72... long string of numbers/letters. Test 1. Subject is the actual rogue post. I can use reply or forward, edit the message and address it to the list. I changed options to send in plain text, wrote approved: password at the top of the body and, just below that, changed the line To: testl...@... to Resent-To: testlist@ ... The message made it through OK, but appears to be from me instead of from the original sender, and has the headers written at the top of the body of the message in the same way any replied to or forwarded email would have (albeit changed to Resent-To.) So I've got it working in part and this will do if there isn't a straightforward solution. The approved bit worked and I could edit the message, but how do I make a Resent-To instead of a Forward? Which is what I think you mean by: and then 'bounce' it to the list. 'Bounce' is Mutt's term for resending the original message to additional recipients. This is not forwarding; it is resending with the original headers. Not all MUAs can do this. Is it possible in Outlook? Another odd thing is that although it's been approved (via email) and received by list members, the original post is still sitting in the admin queue on the web interface. So I'll need to remember to delete it manually. One of the wiki pages you linked to, about editing messages before approving them (thank you, very helpful) says, If this feature is not available in your MUA, you can still post the edited message directly if you are on a machine with an MTA, e.g., sendmail, etc., by saving the edited message in a file and giving a command similar to the following: /path/to/sendmail l...@example.com edited_message_file I haven't a clue what any of that means so guess it's beyond me. Thanks for the other links too. I'll explore them but after a quick read, I think it's likely to be beyond me. Good advice too about server space being so cheap compared with the amount of time I could spend tidying up digests and archives. Thank you again for such a helpful reply. Any solutions getting Resent-To (Bounce?) to work through Outlook? Clare -Original Message- From: Mark Sapiro [mailto:m...@msapiro.net] Sent: 29 December 2009 15:06 To: Clare Redstone; mailman-users@python.org Subject: Re: [Mailman-Users] Replying to digests Clare Redstone wrote: I'm in the process of setting up Mailman for a discussion group of about 100 members. From past experience, I know some people will prefer to have digest but they'll also probably just hit the reply button without editing the subject or deleting anything automatically included. I think this will mean their replies will contain the entire digest: difficult to work out which message they're replying to and using archive space on the server. 1. How do I stop this happening? At the moment, the only thing I can think of is to filter out messages containing digest in the subject line and hold those for moderation. You can do that with Privacy options ... - Spam filters - header_filter_rules, or you can just moderate all members or all digest members and reject their posts until they learn. You can also set General Options - max_message_size small enough to catch these. In particular, if digests are triggered on size only, you
Re: [Mailman-Users] Replying to digests
Clare Redstone wrote: I might exceptionally see if I can edit and resend messages when I think it's particularly worth it and the sender likely to be flummoxed by being asked to clean and resend. I'm having trouble following the instructions though. I use Outlook 2007 on Windows XP so don't have Mutt. What you can do depends on your MUA. I do the following occasionally (when a quoted digest is held for size). I have admin_immed_notify set to yes, so I receive a notice containing the post as part 2 of 3 message parts. First, I discard the original held message. Then, using Mutt, I open the notice and then the message/rfc822 part containing the post, edit it... In Outlook, I get an email telling me there's a message waiting for authorisation, with 2 attachments: one called by the post subject and the other called confirm 2ff72... long string of numbers/letters. Yes, that's correct. The one with the 'confirm ...' subject can be used to approve or discard the original. If you open that message and reply to it, the original post will be discarded. If you insert Approved: password as the first line of that reply, the original UNEDITED post will ba accepted for the list. Test 1. Subject is the actual rogue post. I can use reply or forward, edit the message and address it to the list. I changed options to send in plain text, wrote approved: password at the top of the body and, just below that, changed the line To: testl...@... to Resent-To: testlist@ ... The Approved: password here may or may not be needed. It is only to ensure that the resent message doesn't get held a second time. If you edit out the things that caused it to be held, you don't need the Approved: password. The message made it through OK, but appears to be from me instead of from the original sender, and has the headers written at the top of the body of the message in the same way any replied to or forwarded email would have (albeit changed to Resent-To.) Yes. That is because you are replying or forwarding. The headers you are editing are copies of the original message headers in the body of your reply/forward. You are effectively creating a new message From: you to the list, and this is not what you want to do. So I've got it working in part and this will do if there isn't a straightforward solution. The approved bit worked and I could edit the message, but how do I make a Resent-To instead of a Forward? The Approved: bit may or may not have been required as I note above. Which is what I think you mean by: and then 'bounce' it to the list. 'Bounce' is Mutt's term for resending the original message to additional recipients. This is not forwarding; it is resending with the original headers. Not all MUAs can do this. Is it possible in Outlook? I don't know. What happens if you drag the attachment containing the original message to your Drafts folder? Do you have such a thing? If so, you might be able to do that, and then edit the draft and send it. I don't know if that would work, but it is worth a try. Another odd thing is that although it's been approved (via email) and received by list members, the original post is still sitting in the admin queue on the web interface. So I'll need to remember to delete it manually. Right. The original post will always have to be manually deleted. Even if you get the editing down so the resend is From: the original sender with the original Message-ID: and In-Reply-To: and References: headers (for threading in the archives, although if it's a reply to a digest, it won't be threaded anyway), it's still a separate post as far as Mailman is concerned, and the original has to be manually discarded. One of the wiki pages you linked to, about editing messages before approving them (thank you, very helpful) says, If this feature is not available in your MUA, you can still post the edited message directly if you are on a machine with an MTA, e.g., sendmail, etc., by saving the edited message in a file and giving a command similar to the following: /path/to/sendmail l...@example.com edited_message_file I haven't a clue what any of that means so guess it's beyond me. That is not directly applicable to Windows XP without installing other software. It would be possible to do this with a Windows MUA like popcorn http://www.ultrafunk.com/popcorn/. If you configured popcorn to be able to send mail, you could save the original message part from outlook and then open it as a draft with popcorn and then edit and send it. That is possibly the easiest thing if you need to install something, but try the outlook drafts idea first. Thank you again for such a helpful reply. Any solutions getting Resent-To (Bounce?) to work through Outlook? Try the drafts idea. There may actually be a way to directly resend a message from outlook, but I know little about it, and the drafts trick is all I can think of. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area,
