On Thu, 2002-10-10 12:54:18, [EMAIL PROTECTED] wrote: > Thank you for the explanation. The former problems, I can do nothing > about.
Actually there is. Use an email client that doesn't violate well established rules. At IBM the Linux support and development engineers have two email addresses for this reason. One is routed through the Notes/Domino system and is used for "internal" email. The other bypasses it. When interacting with the outside world, such as posting to the "Linux Kernel Mailing List", you use the non-Notes address and an email client that isn't brain-dead. When retrieving your paycheck (which is encrypted using some proprietary Lotus scheme) you use your Notes address and client. Simple :-) I make it even simpler by forwarding all my email from the Notes address to my non-Notes address. Which means the only time I have to deal with Notes is when I need to see my paycheck. > As to the second problem (the reply-to) problem, I can indeed refrain > from doing that. I'll bet that most people, like me, were totally > unaware that it creates a problem in the rare email client that does > threading. (BTW: what are some examples that do it?) I was just a > little taken aback to have someone ranting and threatening to 'blacklist' > me and others for something of which we were totally unaware. Mutt, the email client I use, is just one example out of many. For example, this discussion thread appears like the following block of text to me. It isn't an exact representation (because plain text can't replicate how mutt displays a thread) but conveys the sense of the presentation. The left most number is the message number in the folder. The lower-case 'r' means I replied to the message. The question-mark means my email address does not appear in the "to:" or "cc:" headers. The "F" means the message is from me. The asterisks in the thread display indicate that mutt could not find a "in-reply-to" or "references" header and is basing its decision to include the message in the thread on the subject line. In other words, it is doing its best to deal with a broken email system. The rest should be self explanatory. 67 ? Oct 09 Michael Nordstr (1.2K) Mailing list etiquette 68 ? Oct 09 Jason Day (0.7K) |-> 69 ? Oct 09 Troy Eckhardt (0.5K) |-> 70 ? Oct 09 MJ Ray (0.5K) |-> 71 ? Oct 09 Troy Eckhardt (0.8K) |-> 72 r ? Oct 10 [EMAIL PROTECTED] (3.2K) |*> 73 F Oct 09 To plucker-list (2.2K) |-> 74 ? Oct 10 [EMAIL PROTECTED] (4.9K) |*> It's cognitively jarring to be reading messages in a discussion thread and suddenly find yourself dealing with a different topic. There are good reasons why written material is organized in paragraphs, sections, chapters, etc. The fact that modern email clients make it far too easy to violate such conventions is why Michael Nordstr�m responded as he did. _______________________________________________ plucker-list mailing list [EMAIL PROTECTED] http://lists.rubberchicken.org/mailman/listinfo/plucker-list
