-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2005-07-29 at 15:50 +0530, Arun Khan wrote:
In the past couple of weeks I have sent a few suggestions to the list owner but have not received any feedback from him/her.
Basically here are my suggestions:
All of your questions are answered since ages ago on this list FAQ: that might be the reason you didn't get an answer from the owner. I'll just copy those Q&A from the FAQ for your convenience; please get the full FAQ yourself (easy: instructions for getting it are on about every email you receive from the list, and in the confirm message you got from the list server when you subscribed).
a) "Reply To" header - each SuSE list must use the "Reply To" header in the messages sent to members e.g. for this list, it should be "Reply To: suse-linux-e@suse.com" All other lists that I am a member of use this feature. When members reply, they do not have to worry about editing the "To" header or right clicking in their message body or whatever. With this header the response _simply_ goes to the relevant SuSE list. I don't understand why SuSE list manager is not configured to do so.
Q2. Why do my replies go to the original poster and not the list? A2. We do not "munge" the mail headers by inserting a "Reply-To: suse-linux-e@suse.com" because it makes it more difficult subscribers to handle the mail the way they want to. Your mail client probably has a "reply" function as well as a "reply to all" or "reply to list" one; Please use the latter if you want you message to go to the list and not just to the original poster. Also, please don't complain about this on the list, it has been discussed many, many, many times in the past already. For background information see http://www.unicom.com/pw/reply-to-harmful.html New! Even Sourceforge has turned to the dark side: http://sourceforge.net/docman/display_doc.php?docid=6693&group_id=1
b) Digest mode - provide a digest option when member subscribes to any of SuSE's list. Again, all other lists that I am a member of provide this feature. Personally, I prefer the digest since the messages downloaded are fewer. I am sure the mailer program for SuSE lists has the digest feature.
Q3. How to I get the list in digest form instead of separate emails? A3. We don't offer digested lists for several reasons: 1) Most of our lists (especially this one) are far to large to make digests useful. Are you really going to read an ~500K email once per day? Yes, it's the same amount that you would receive on as separate mail but it's easy to delete or skip messages that don't interest you in that case; it's not with a digest. 2) In our experience, digests tend to decrease the quality of list postings. They do this by encouraging the sorts of behaviors that are often considered rude or in poor 'netiquette': replying to mail with the incorrect subject header or other headers that make it impossible for threaded mail clients to work properly, replying to mail without reading the entire thread first, and probably more. Of course, people who do things like this are often the cause of huge flame wars about proper netiquette that can go on for days, often with the result of having very helpful and knowledgeable people leaving the list in disgust. 3) Usually, when people request digests what they are really asking for is a way to keep the list mail from flooding their mailbox and making it harder to find and read non-list mail. This is a valid concern and one that is best handled with mail filtering, not digests. If your system is configured to use procmail to deliver mail locally (SuSE's postfix and sendmail packages are) all you need to do is create a file in your home directory named '.procmailrc' that contains something like the following: MAILDIR=$HOME/Mail # where do you keep your mail? DEFAULT=$MAILDIR/inbox # what's you default mail box? # if mail is from list put it in $MAILDIR/foo :0 * ^X-Mailinglist::.*suse-linux-e $MAILDIR/foo Everything else will be placed in $DEFAULT. By default, procmail creates a normal mbox formatted mail box so if you want to copy the file somewhere (e.g., to a PDA) you only need to, in the above example, copy $MAILDIR/sle. Of course, procmail is capable of much more than what this simple example shows, so please read procmailrc(5) and procmailex(5) for more information.
c) Google search bar for each of SuSE list archives. At http://lists.suse.com/archive/ I did not see any search capability.
Q1. Why don't you provide searchable archives of this list? A1. The archives are far too large to be indexed by us. Very complete archives that are searchable can be found here: http://www.netsys.com/suse-linux-e/index.html http://marc.theaimsgroup.com/ Alternatively, you can prepend your search on Google.com with lists site:lists.suse.com E.g., to search for "lilo 1024" you would type lists site:lists.suse.com lilo 1024 into the search field.
Perhaps they will listen if enough people voice their opinion.
I don't think so ;-) - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFC6vQMtTMYHG2NR9URAtgiAJ4jjsI96qBp6QADqpGHz7MMIQxpEQCfU2Bu lbJaWlvDUIq2bAYY1WIyePQ= =RX+W -----END PGP SIGNATURE-----