Re: Message threading.
On Wed 02 Oct 2019 at 23:14:05 (+0200), Thomas Schmitt wrote: > pe...@easthope.ca wrote: > > Suppose you read a message in the Web based archive and it is no > > longer in your mailer. Either you weren't subscribed when the message > > was sent or you were subscribed but have deleted the message. Using > > tools available, in Debian or otherwise, can you reply with correct > > threading? > > Well, besides the aspect of software availablilty, it is a a matter of > knowing the message id of the mail to which you want to refer. > Then you have to put it into a "In-Reply-To:" header or a "References:" > header. > > The message ids are providently shown in the debian-user archive. > See > https://lists.debian.org/debian-user/2019/10/msg00127.html > Message-id: <[?] E1iFl97-0002sw-8y@joule.invalid> > > The string "[?] " is an artifact of copy+paste between web browser and > text editor. Your reply's headers should look like: > > References: > In-Reply-To: > > "References:" can take multiple ids separated by blanks and optional > newlines. Kindof a thread branch history. > Like: > References: > > > "In-Reply-To:" can take only one id. > > Now it depends on your mail client whether you can talk it into accepting > one or both of these header lines, ot the message id so that it composes > own reply headers. I thought we just flogged this topic to death here at the end of July. We discussed the conversion by the Oberon emailer of the Unicode "RIGHT-POINTING MAGNIFYING GLASS" characters into NULs embedded in the posts, how IMAP and MUAs react to them, why these characters appear on the Debian archive pages, how References and In-Reply-To work in threading, the usual fallacy that these field names are case-sensitive (they're not), and so on. Following this, the OP managed to send correctly threaded posts—see for example https://lists.debian.org/debian-user/2019/07/msg01360.html But when the solution is manual, lengthy and tedious (copy/pasting the in-reply-to and references fields into the reply's composition editor and then deleting the extraneous magnifying glasses), it's difficult to apply it every time and get it just right. FWIW I've never set up my browser to be able to reply to postings through the mailto: buttons at the end of each message, so I can't help the OP with that suggestion, particular when using the Oberon OS, which I've never seen. Cheers, David.
Re: Message threading.
Hi, pe...@easthope.ca wrote: > Suppose you read a message in the Web based archive and it is no > longer in your mailer. Either you weren't subscribed when the message > was sent or you were subscribed but have deleted the message. Using > tools available, in Debian or otherwise, can you reply with correct > threading? Well, besides the aspect of software availablilty, it is a a matter of knowing the message id of the mail to which you want to refer. Then you have to put it into a "In-Reply-To:" header or a "References:" header. The message ids are providently shown in the debian-user archive. See https://lists.debian.org/debian-user/2019/10/msg00127.html Message-id: <[?] E1iFl97-0002sw-8y@joule.invalid> The string "[?] " is an artifact of copy+paste between web browser and text editor. Your reply's headers should look like: References: In-Reply-To: "References:" can take multiple ids separated by blanks and optional newlines. Kindof a thread branch history. Like: References: "In-Reply-To:" can take only one id. Now it depends on your mail client whether you can talk it into accepting one or both of these header lines, ot the message id so that it composes own reply headers. Have a nice day :) Thomas
Re: Message threading.
On Wed, 02 Oct 2019 13:22:49 -0700 pe...@easthope.ca wrote: > Suppose you read a message in the Web based archive and it is no > longer in your mailer. Either you weren't subscribed when the message > was sent or you were subscribed but have deleted the message. Using > tools available, in Debian or otherwise, can you reply with correct > threading? If so, please outline the procedure. Under the message, you'll see a section headed "Reply to:". Clicking on one of the links in that section (assuming your browser is correctly configured to open "mailto:"; links) will create an appropriate email in an email client. Celejar
Message threading.
Suppose you read a message in the Web based archive and it is no longer in your mailer. Either you weren't subscribed when the message was sent or you were subscribed but have deleted the message. Using tools available, in Debian or otherwise, can you reply with correct threading? If so, please outline the procedure. Thanks,... Peter E. -- https://en.wikibooks.org/wiki/Medical_Machines https://en.wikibooks.org/wiki/Oberon Tel: +1 604 670 0140Bcc: peter at easthope. ca
Re (2): message threading
* From: lee * Date: Mon, 20 Jun 2011 02:59:40 +0200 > [References] go back to beginnings of subthreads at > least. > With only the In-Reply-To: header, threads would be broken ... In http://wiki.debian.org/DebianMailingLists I've added a section "Message Threading and Replying". Also simplified the section structure a little and revised a few bad sentences. If Lee or anyone else can read the page and report an error or deficiency, that would help. What other topics should be covered in that page? Thanks, ... Peter E. -- Telephone 1 360 450 2132. bcc: peasthope at shaw.ca Shop pages http://carnot.yi.org/ accessible as long as the old drives survive. Personal pages http://members.shaw.ca/peasthope/ . -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/171057104.81445.74650@cantor.invalid
Re: message threading; was Re (3): QCAD Pro in Squeeze
On Sun, 19 Jun 2011 15:15:57 -0800, peasthope wrote: >> Would you please fix your mail client so you stop breaking the list >> threading? > > Usually I manage to set In-reply-to to the Message-id of the message > being replied to. In the Web archive, the Follow-Ups and References > seem OK. Can anyone tell me what other parameter might be required to > "fix" threading as Chuck says? (...) I see nothing broken :-? http://lists.debian.org/debian-user/2011/06/thrd4.html#01594 Your MUA seems to add an extra (n) number to the subject but it respects the threading. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.06.20.11.38...@gmail.com
Re: Re (2): message threading
peasth...@shaw.ca writes: > From: lee > Date: Mon, 20 Jun 2011 00:54:27 +0200 >> You donA't seem to have any "References:" headers, ... > > Should the References trace back to the beginning of the thread? Just look at them, they go back to beginnings of subthreads at least. With only the In-Reply-To: header, threads would be broken for everyone who´s missing a single message of the thread. With the references, the thread can be displayed even when not all messages are available. > In principle, the list processor could copy the References from the > referenced message and append the id of that message. I don't know > how it actually works. It doesn´t work that way. How´s the MLM software supposed to know if you refer to articles and to which ones, unless you tell it? >> The message IA'm replying to is correctly displayed as the top of a new >> thread. > > Yes, I intended to start a new thread on "message threading". Hence > the subject "message threading; was Re (3): QCAD Pro in Squeeze". That´s why I´m asking. I think it´s more common to use a new subject when starting a new thread, and it´s more common to change the subject like you did within a thread without starting a new one. You changed the subject as if continuing the thread and made it a new one by omitting the references, and since the thread is about broken threading, it was unclear whether your intention was to start a new thread or to continue the thread with an adjusted subject. If your MUA doesn´t add the right headers automatically, it´s time to switch to a better one :) -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8739j5e2rn@yun.yagibdah.de
Re (2): message threading; was Re (3): QCAD Pro in Squeeze
From: lee Date: Mon, 20 Jun 2011 00:54:27 +0200 > You donA't seem to have any "References:" headers, ... Should the References trace back to the beginning of the thread? In principle, the list processor could copy the References from the referenced message and append the id of that message. I don't know how it actually works. > ... "in-reply-to" instead of "In-Reply-To". RIght oh; according to RFC 5322 the parameter names in the header are case sensitive. > The message IA'm replying to is correctly displayed as the top of a new > thread. Yes, I intended to start a new thread on "message threading". Hence the subject "message threading; was Re (3): QCAD Pro in Squeeze". Thanks, ... Peter E. -- Telephone 1 360 450 2132. bcc: peasthope at shaw.ca Shop pages http://carnot.yi.org/ accessible as long as the old drives survive. Personal pages http://members.shaw.ca/peasthope/ . -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/171057043.68097.41835@heaviside.invalid
Re: message threading; was Re (3): QCAD Pro in Squeeze
On 06/19/2011 06:15 PM, peasth...@shaw.ca wrote: From a private message; From: C P Date: Sun, 19 Jun 2011 16:30:55 -0400 Would you please fix your mail client so you stop breaking the list threading? Usually I manage to set In-reply-to to the Message-id of the message being replied to. In the Web archive, the Follow-Ups and References seem OK. Can anyone tell me what other parameter might be required to "fix" threading as Chuck says? And, yes, I'll document the explanation in http://wiki.debian.org/DebianMailingLists. Your MUA should do it automatically. Maybe that 8 year ld version of Oberon Mail doesn't have that feature? -- "Neither the wisest constitution nor the wisest laws will secure the liberty and happiness of a people whose manners are universally corrupt." Samuel Adams, essay in The Public Advertiser, 1749 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dfe853f.9040...@cox.net
Re: message threading; was Re (3): QCAD Pro in Squeeze
peasth...@shaw.ca writes: >>From a private message; > From: C P > Date: Sun, 19 Jun 2011 16:30:55 -0400 >> Would you please fix your mail client so you stop breaking the list >> threading? > > Usually I manage to set In-reply-to to the Message-id of the message > being replied to. In the Web archive, the Follow-Ups and References > seem OK. Can anyone tell me what other parameter might be required > to "fix" threading as Chuck says? Your threading is displayed fine here with gnus. You don´t seem to have any "References:" headers, and in <171057043.52499.41831@heaviside.invalid>, you have "in-reply-to" instead of "In-Reply-To". The message I´m replying to is correctly displayed as the top of a new thread. If it´s supposed to be part of the thread that starts with <171057043.43873.41829@heaviside.invalid>, your threading is actually broken. Your MUA should get it right automatically by default; what are you using? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/871uypfn4s@yun.yagibdah.de
message threading; was Re (3): QCAD Pro in Squeeze
>From a private message; From: C P Date: Sun, 19 Jun 2011 16:30:55 -0400 > Would you please fix your mail client so you stop breaking the list > threading? Usually I manage to set In-reply-to to the Message-id of the message being replied to. In the Web archive, the Follow-Ups and References seem OK. Can anyone tell me what other parameter might be required to "fix" threading as Chuck says? And, yes, I'll document the explanation in http://wiki.debian.org/DebianMailingLists. Thanks, ... Peter E. -- Telephone 1 360 450 2132. bcc: peasthope at shaw.ca Shop pages http://carnot.yi.org/ accessible as long as the old drives survive. Personal pages http://members.shaw.ca/peasthope/ . -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/171057043.62457.41832@heaviside.invalid
Routing via an OpenVPN tunnel; was "message threading ..."
From: Bob Proulx Date: Tue, 18 Jan 2011 21:12:47 -0700 > I am suggesting that you have such a complicated routing setup that it > is causing you difficulty and that you should simplify it by some > method. You listed five (5!) route commands in your configuration. Yes; addressing subnets rather than individual machines is better. Now there is just one route directive in joule:/etc/openvpn/myvpn.conf to identify the subnet at UBC. dalton:/etc/openvpn/myvpn.conf has one route directive to identify the subnet at home; but dalton has two other route directives to let the subnet at UBC connect to the Shaw FTP and SMTP servers. The Shaw SMTP server will accept a connection only via my home link. The FTP server will accept a connection from anywhere but the tunnel avoids exposing communication to the public. http://carnot.yi.org/NetworksPage.html is updated with the details. For now, I can't think of any further simplification. From: Mike Bird Date: Tue, 18 Jan 2011 21:07:47 -0800 > Once your routing gets that complexicational you might > want to consider using a routing deamon such as Quagga. > > You could probably use OSPF over the tunnels but we > prefer to use private BGP, with each office and laptop > and customer office network a separate private AS. I'll read about those. Now that the configurations are simplified I might leave them rather than install more software. Thanks for the ideas. Avoiding reliance on a DDNS for Joule by dropping the remote directive on Dalton was a crucial improvement. ... Peter E. -- Telephone 1 360 450 2132. Shop pages http://carnot.yi.org/ accessible as long as the old drives survive. Personal pages http://members.shaw.ca/peasthope/ . -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/171056900.36978.32436@cantor.invalid
Re (3): message threading in debian lists.
From: Bob Proulx Date: Tue, 18 Jan 2011 21:12:47 -0700 > And you have been having such trouble with your vpn(s). To me that is > like a house of cards. A light breeze blows it over. In order to be > more robust it needs to be simpler, less rigid, and more flexible. Iprovements in progress. Will reply after my documentation page is updated. > But you asked the question! :-) It isn't fair to ask a question, get > an answer, and then complain about it. :-) That is dirty dealing! OK, sorry, sorry. My disappointment is with http://lists.debian.org/ ; not with your answer. I've added this section. "http://wiki.debian.org/DebianMailingLists#MessageThreadingandReplyingtoaQuestion"; The preceeding sub-section, "How to continue a discussion", is inadequate. Some archived messages have links under the heading "References". In some cases there is more than one "layer" of reference. Presumeably the list software traces back recursively. Also there are "Follow-ups". A retroactive edit must occur to make one of these. Any additional ideas? If there are any comments or suggestions I am happy to continue work on the wiki page. Anyone who is registered can edit the page of course. Regards, ... Peter E. -- Telephone 1 360 450 2132. Shop pages http://carnot.yi.org/ accessible as long as the old drives survive. Personal pages http://members.shaw.ca/peasthope/ . -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/171056890.45653.31504@cantor.invalid
Re: Re (2): message threading in debian lists; was Re (6): OpenVPN server mode usage.
On Wednesday 19 January 2011 04:12:47 Bob Proulx wrote: > peasth...@shaw.ca wrote: > > Bob Proulx wrote: > > > You have a complicated setup! > > > > A complex setup. "complicated" is a verb. ... Sorry. > > Uhm... No. Complicated is an adjective. > > From WordNet (r) 2.0 [wn]: > >complicated >adj : difficult to analyze or understand; "a complicated problem"; > "complicated Middle East politics" I agree with Bob. I have checked in several dictionaries. The Shorter Oxford, 1944 would agree with you. I have checked in three others, more recently published, and they all have complicated as an adjective. Here is one: http://en.wiktionary.org/wiki/complicated Moreover, even if it had not already, some time ago, entered the language as an adjective, I would contend that it is perfectly legitimate to use a past participle adjectivally. Think of e.g. "a tried and tested method". Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201101191618.11180.lisi.re...@gmail.com
Re: Re (2): message threading in debian lists; was Re (6): OpenVPN server mode usage.
On Tue January 18 2011 20:12:47 Bob Proulx wrote: > peasth...@shaw.ca wrote: > > Are you suggesting that all of dalton's 'net traffic > > go through the tunnel and Joule? Are you suggesting > > that all of joule's 'net traffic go through the tunnel > > and dalton? Aren't both significantly disadvantageous? > > I am suggesting that you have such a complicated routing setup that it > is causing you difficulty and that you should simplify it by some > method. You listed five (5!) route commands in your configuration. Once your routing gets that complexicational you might want to consider using a routing deamon such as Quagga. You could probably use OSPF over the tunnels but we prefer to use private BGP, with each office and laptop and customer office network a separate private AS. BGP gives us better control of route propagation than OSPF. For example sysadmin laptops can communicate with customer office networks for maintenance purposes but customer office networks cannot see each other. --Mike Bird -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201101182107.47481.mgb-deb...@yosemite.net
Re: Re (2): message threading in debian lists; was Re (6): OpenVPN server mode usage.
peasth...@shaw.ca wrote: > Bob Proulx wrote: > > You have a complicated setup! > > A complex setup. "complicated" is a verb. ... Sorry. Uhm... No. Complicated is an adjective. From WordNet (r) 2.0 [wn]: complicated adj : difficult to analyze or understand; "a complicated problem"; "complicated Middle East politics" > It's simplifying slowly and surely. One helpful detail is to > route to a LAN rather than to individual machines. > route 172.23.0.0 255.255.0.0 > rather than > # Curie > route 172.23.4.2 > # Heaviside > route 172.23.5.2 Yes. Definitely yes. Simpler is better. > > But since you have routes to public IP space there perhaps you would > > want to route all of your traffic over the vpn (once you have it > > working) and then you wouldn't need specific routes for everything. > > Dalton has a relatively fast connection to the 'net > provided by the university. Joule at home has a > relatively slow connection to the net through shaw.ca. > > Are you suggesting that all of dalton's 'net traffic > go through the tunnel and Joule? Are you suggesting > that all of joule's 'net traffic go through the tunnel > and dalton? Aren't both significantly disadvantageous? I am suggesting that you have such a complicated routing setup that it is causing you difficulty and that you should simplify it by some method. You listed five (5!) route commands in your configuration. >>> # Machines in the local home zone reached _via_ the tunnel. >>> # Curie >>> route 172.23.4.2 >>> # Heaviside >>> route 172.23.5.2 >>> # Shaw mail servers _via_ the tunnel. >>> # route shawmail.gv.shawcable.net >>> route 64.59.128.135 >>> route 24.71.223.43 >>> # Shaw ftp server _via_ the tunnel. >>> # route ftp.shaw.ca >>> route 64.59.128.134 And you have been having such trouble with your vpn(s). To me that is like a house of cards. A light breeze blows it over. In order to be more robust it needs to be simpler, less rigid, and more flexible. > > Standard email headers apply. RFC 2822 would cover them. > > Certainly, but how many new Debian users will find RFC 2822, study > it and perceive how threading works when subscribing to debian-user? But you asked the question! :-) It isn't fair to ask a question, get an answer, and then complain about it. :-) That is dirty dealing! In response I will only say that most users will simply use an MUA (mail user agent) and will simply use it (mutt, thunderbird, gmail, whatever) to generate follow-ups. It is the MUA's job to do the right thing with respect to email headers. Let's hope the author of the MUA actually took the time to read the RFCs. Bob signature.asc Description: Digital signature
Re (2): message threading in debian lists; was Re (6): OpenVPN server mode usage.
From: Bob Proulx Date: Mon, 17 Jan 2011 21:59:42 -0700 > You have a complicated setup! A complex setup. "complicated" is a verb. ... Sorry. It's simplifying slowly and surely. One helpful detail is to route to a LAN rather than to individual machines. route 172.23.0.0 255.255.0.0 rather than # Curie route 172.23.4.2 # Heaviside route 172.23.5.2 From: Bob Proulx Date: Wed, 12 Jan 2011 11:53:04 -0700 > But since you have routes to public IP space there perhaps you would > want to route all of your traffic over the vpn (once you have it > working) and then you wouldn't need specific routes for everything. Dalton has a relatively fast connection to the 'net provided by the university. Joule at home has a relatively slow connection to the net through shaw.ca. Are you suggesting that all of dalton's 'net traffic go through the tunnel and Joule? Are you suggesting that all of joule's 'net traffic go through the tunnel and dalton? Aren't both significantly disadvantageous? > Standard email headers apply. RFC 2822 would cover them. Certainly, but how many new Debian users will find RFC 2822, study it and perceive how threading works when subscribing to debian-user? I might try adding a brief note about threading in http://wiki.debian.org/DebianEdu/MailingLists and I wonder how many new users will find that. Regards, ... Peter E. -- Telephone 1 360 450 2132. Shop pages http://carnot.yi.org/ accessible as long as the old drives survive. Personal pages http://members.shaw.ca/peasthope/ . -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/171056882.74741.66673@cantor.invalid
Re: message threading in debian lists; was Re (6): OpenVPN server mode usage.
peasth...@shaw.ca wrote: > A third case is when I am at work and the tunnel between dalton You have a complicated setup! > and joule is broken. Then POP3 can bring messages from the ISP > through the public Internet to cantor; but the ISP will not accept > a message from cantor via SMTP through the public Internet. In > this case messages must be sent through the Web interface of the ISP. > Presumeably it's this Web software which inserts " (#)". Now if a > message is read on cantor I have difficulty. That is not very nice of them. It is good that your tunnel is back working again so that you can avoid some of the problems. > The message-id is visible on cantor but I do not know of any way to > have the Web interface accept an In-reply-to parameter. That's when > a new thread begins. It must be more than this because the Subject line is also modified. Not having an In-Reply-To isn't changing the subject line. (shrug) > If the tunnel is broken I could simply refrain from retrieving mail to > the MUA on cantor and read all mail with the Web based interface. It wasn't the end of the world. It was just annoying and so I noted it. > Is threading of messages in Debian lists explained anywhere? I've never > seen an explanation. A few years ago I found how to use Message-id > and In-reply-to by exploration rather than straightforward reading. Standard email headers apply. RFC 2822 would cover them. Though perhaps the wikipedia page is more readable. http://en.wikipedia.org/wiki/Email#Message_header Bob signature.asc Description: Digital signature
message threading in debian lists; was Re (6): OpenVPN server mode usage.
Bob, From: Bob Proulx Date: Wed, 12 Jan 2011 11:22:23 -0700 > Every reply of yours is starting a new thread. You can see this in > the mailing list archives. Apologies. I understand and certainly would prefer not do that. > This is an aside but why is the subject being modified with a " (#)" > before the colon in "Re:"? Converting "Re:" to "Re (5):" for this > message for example? That causes the attempt to fall back without > In-Reply-To: to grouping messages by subject to be unable to do so. I'll explain all the cases for benefit of anyone who might be interested. Some of the information at http://carnot.yi.org/NetworksPage.html might help. The simplest is when I am at home and have a direct link to the ISP and POP3 brings messages from the ISP to the home workstation, heaviside, and SMTP takes messages from heaviside to the ISP. A message from debian-user can be read as an emessage or from the Web archive. In both cases the Message-id is available and I can insert it as the value of In-reply-to in a reply. lists.debian.org uses that message-id to connect the thread. So far, so good. A second case is when I am at work and the tunnel between dalton and joule is working properly. Then POP3 brings messages from the ISP to cantor via the tunnel and SMTP takes messages to the ISP. Email works the same for cantor as for heaviside in the case above. Still good. A third case is when I am at work and the tunnel between dalton and joule is broken. Then POP3 can bring messages from the ISP through the public Internet to cantor; but the ISP will not accept a message from cantor via SMTP through the public Internet. In this case messages must be sent through the Web interface of the ISP. Presumeably it's this Web software which inserts " (#)". Now if a message is read on cantor I have difficulty. The message-id is visible on cantor but I do not know of any way to have the Web interface accept an In-reply-to parameter. That's when a new thread begins. If the tunnel is broken I could simply refrain from retrieving mail to the MUA on cantor and read all mail with the Web based interface. If a reply is created, the correct value for In-reply-to will be generated automatically. My objection is that the Web interface is unbearably slow and clumsy. The tunnel is working again now and with any luck, will continue to do so for several years. As long as the tunnel works I can connect messages properly. Is threading of messages in Debian lists explained anywhere? I've never seen an explanation. A few years ago I found how to use Message-id and In-reply-to by exploration rather than straightforward reading. Regards, ... Peter E. -- Telephone 1 360 450 2132. Shop pages http://carnot.yi.org/ accessible as long as the old drives survive. Personal pages http://members.shaw.ca/peasthope/ . -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/171056881.47301.39653@heaviside.invalid
Re: Modern Message Threading Techniques (Was: replying to a message in debian-user)
On Thu, Jan 25, 2007 at 12:20:59PM -0700, Wesley J. Landaker wrote: > No, what I mean is that it's obviously *better* to use a MUA that supports > threading, Threading is good. I'd go nutty(no, wait, I did that years ago anyway) trying to follow high-volume e-mail lists without it. Good thread handling was one of the main things I was looking for when I switched from Pine to Mutt several years ago. It looks like Pine's threading capabilities have improved since then. > but even if you use a MUA that doesn't support threading properly, as long > as you keep the subject line the same, most modern MUAs will still > associate it to the thread. =) In the case of Mutt it uses the In-Reply-To header, not the subject, to thread messages. If a subject has been changed(such as I did with this message) Mutt still threads the message appropriately. On the other hand if someone posts a new message with an identical subject or replies to a digest and changes the subject appropriately Mutt threads those kind of replies/posts separately. In the case of a new message with an identical/siumilar subject that's probably a good thing. People replying to digests can really smeg up theading. This is especially true if one replies to several different e-mails from the same digest. Since they're all a reply to the same message(the digest) they all get threaded together. I generally overlook replies to digests. Overall I prefer Mutt's threading techniques. > Anyway, someone else pointed out that you can always set things up so you > can ssh into some location (e.g. your home computer) and run a > full-featured text-based MUA like mutt. With a little setup, this might > actually be faster than using a web MUA anyway. That's the kind of setup I've been using for years. It has served me well. Kevin http://www.RawFedDogs.net http://www.WacoAgilityGroup.org Bruceville, TX Si hoc legere scis nimium eruditionis habes. Longum iter est per praecepta, breve et efficax per exempla!!! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
