On Sunday, 26 November 2017 10:00:40 GMT Ralph Seichter wrote: > On 26.11.2017 03:30, Peter Humphrey wrote: > > I get duplicate messages, which are a known problem and easily worked > > around, but the latest version of KMail whinges about more than one > > candidate for display and just gives up. > > For debugging purposes it might help you to know that you actually sent > the message I am currently quoting twice, according to the header data. > Message #1: > > Received: from [82.69.80.10] (helo=peak.localnet) > by smarthost03d.mail.zen.net.uk with esmtps > (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) > (envelope-from <pe...@prh.myzen.co.uk>) > id 1eImhw-0000IJ-SK > for gentoo-user@lists.gentoo.org; Sun, 26 Nov 2017 02:30:12 +0000 > > Message #2: > > Received: from [82.69.80.10] (helo=peak.localnet) > by smarthost03a.mail.zen.net.uk with esmtps > (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) > (envelope-from <pe...@prh.myzen.co.uk>) > id 1eImhw-0002XH-8v > for gentoo-user@lists.gentoo.org; Sun, 26 Nov 2017 02:30:12 +0000 > > Note the different host names and different IDs, these are two distinct > emails sent by you.
Indeed. Thanks for the info. It looks as though KMail did that; at least, I can't imagine how finger trouble could have done it, even at 02:30. I have only the one outgoing mail account set up in KMail, and that's directly to my ISP, so my fetchmail fiddling isn't implicated. I haven't heard of KMail duplicating /outgoing/ emails before, though. Maybe I did do something stupid - it wouldn't be the first time. I'll have to keep an eye on this one, and I hope someone will tell me if it happens again. -- Regards, Peter.
