Hi Ken, To get specific/technical, if you view the raw source for the first mail I sent in this tread, you will see it has in its headers
Message-Id: <d4945c1e-c0ce-4acc-b916-43bce243a...@hep.phy.cam.ac.uk> thats the unique identifier for that mail. Then, if you look at Joshua’s reply, it has References: <d4945c1e-c0ce-4acc-b916-43bce243a...@hep.phy.cam.ac.uk> Message-ID: <d60e75a6-f684-f564-3748-beb07bfb4...@macports.org> Its that Reference line that Mail applications use to know that that mail is a reply to another mail, and exactly which mail it is. The then use these fields to correct thread all the messages in a discussion in the right way. Now, if you look at your reply, it is missing the Reference field from its headers, even though it is a reply to another message. Whatever emailer you are using is failing to add this. cheers Chris > On 19 Jun 2021, at 4:22 pm, Chris Jones <jon...@hep.phy.cam.ac.uk> wrote: > > Hi Ken, > > I think you miss understand my point. I was not suggesting you where > subscribed to digest or anything.Your mails indeed come in for me as you send > them, just like everyone elses. > > When you send an email to the macports mailing list, for some reason your > mailer screws up the header information in the mail such that if you are > replying to an on going thread my mailer at least (Apple Mail) fails to > recognise your mail as a reply to that thread, and thus does not correctly > include the message in that thread. It appears as if you have started a brand > new mail thread, such as when you compose a new mail rather than reply to > one. No one elses mails seem to have this problem, only yours. > > Mailers use specific fields in the header of each mail to decide if a mail > belongs to a specifiv thread, and thus for some reason this information is > not being correctly set in your emials. > > Cheers Chris > >> On 19 Jun 2021, at 4:02 pm, Ken Cunningham <ken.cunningham.web...@gmail.com> >> wrote: >> >> I don't subscribe to any of MacPorts' email lists, or any others. >> >> So any comments come in new. Didn't realize that was troubling anyone, but >> thank for letting me know it is. >> >> K >> >> On Saturday, June 19, 2021, Chris Jones <jon...@hep.phy.cam.ac.uk >> <mailto:jon...@hep.phy.cam.ac.uk>> wrote: >> Hi Ken, >> >> OT, but whenever you reply to a thread on these lists your emailer always >> seems to screw up the headers such that your reply starts a new thread. We >> get the messages but it makes following the discussion harder. I don’t know >> what emailer you use, but maybe you could look into it ? >> >> Chris >> >> > On 19 Jun 2021, at 3:43 pm, Ken Cunningham >> > <ken.cunningham.web...@gmail.com <mailto:ken.cunningham.web...@gmail.com>> >> > wrote: >> > >> > Hey, maybe we will finally start bundling curl (there is a years-old >> > ticket about this, and someone already laid out the autotools changes to >> > do it). >> > >> > I have been building MacPorts against a custom libcurl on most systems >> > 10.10 and older for years and years. >> > >> > It's trivially simple to do, but to make it easy and resilient I keep a >> > "default" MacPorts installed in /opt/bootstrap and install curl in that, >> > then use that for the primary MP in /opt/local. >> > >> > >>
smime.p7s
Description: S/MIME cryptographic signature
