kmail crashing again in thread mode
Hi, I have the same problems as about a week ago that kmail is crashing when a message is being deleted and kmail is used in thread mode. Anyone else encountering this problem? It started after attempting to delete a message that was posted at Sunday evening around 2300 hours. -- Richard Bos Without a home the journey is endless
On Sunday 01 December 2002 23.44, Richard Bos wrote:
Hi,
I have the same problems as about a week ago that kmail is crashing when a message is being deleted and kmail is used in thread mode.
Anyone else encountering this problem? It started after attempting to delete a message that was posted at Sunday evening around 2300 hours.
Someone is using a broken MUA. I have three messages with the same message ID Dec 1 15:20:25 message-id=<20021130T184245.GA13187.pat@wahoo.no-ip.org> Dec 1 23:24:56 message-id=<20021130T184245.GA13187.pat@wahoo.no-ip.org> Dec 2 00:06:36 message-id=<20021130T184245.GA13187.pat@wahoo.no-ip.org> Fortunately, my cyrus-imap deletes all such broken mail, and so do the archives at geocrawler and lists.suse.com, so I never have to see them. Maybe you should look into using some software that filters out such broken mail, if kmail can't handle them.
On Mon, 2 Dec 2002, Anders Johansson wrote:
On Sunday 01 December 2002 23.44, Richard Bos wrote:
Hi,
I have the same problems as about a week ago that kmail is crashing when a message is being deleted and kmail is used in thread mode.
Anyone else encountering this problem? It started after attempting to delete a message that was posted at Sunday evening around 2300 hours.
Someone is using a broken MUA. I have three messages with the same message ID
Even though a MUA should never send out 2 messages with the same ID, any MUA should happily accept having more than one mail with the same ID in a mailbox, because that can easily happen in legal ways. One possible scenario: I am subscribed to 2 low-volume mailing lists. Their subjects are related, so they get the same types of questions. Because of their low volume, I have them in the same mail folder. Now, one guy is desparate for a solution to a problem, so he sends To: list1, list2. Result: I have 2 messages with the same ID in the same folder. Regards Ole
On Monday 02 December 2002 03.46, Ole Kofoed Hansen wrote:
Even though a MUA should never send out 2 messages with the same ID, any MUA should happily accept having more than one mail with the same ID in a mailbox, because that can easily happen in legal ways.
One possible scenario: I am subscribed to 2 low-volume mailing lists. Their subjects are related, so they get the same types of questions. Because of their low volume, I have them in the same mail folder. Now, one guy is desparate for a solution to a problem, so he sends To: list1, list2. Result: I have 2 messages with the same ID in the same folder.
I'm aware, and it has been noted as a bug in kmail. But until that gets sorted there is a need for a work-around, such as deleting mails with identical message IDs. As a side note, it's a good idea to do that anyway. If people select "reply all" you'll still only get one mail.
On Sunday 01 December 2002 8:49 pm, Anders Johansson wrote:
I'm aware, and it has been noted as a bug in kmail. But until that gets sorted there is a need for a work-around, such as deleting mails with identical message IDs.
As was pointed out to me when I filed the bug report, it isn't the duplicate IDs that are causing the problem, it is the fact that the Message ID and In-Reply-To are identical that causes this. I don't know if this is cause in Richard's case, as I have not received any mail on the list that fits this pattern since then.
Op maandag 2 december 2002 06:02, schreef Scott Jones:
On Sunday 01 December 2002 8:49 pm, Anders Johansson wrote:
I'm aware, and it has been noted as a bug in kmail. But until that gets sorted there is a need for a work-around, such as deleting mails with identical message IDs.
As was pointed out to me when I filed the bug report, it isn't the duplicate IDs that are causing the problem, it is the fact that the Message ID and In-Reply-To are identical that causes this. I don't know if this is cause in Richard's case, as I have not received any mail on the list that fits this pattern since then.
And that seems to be case here too: From: Graham Smith <gqs@iinet.net.au> From: SuSEnixER <WideGlide@MyRealBox.com> From: SuSEnixER <WideGlide@MyRealBox.com> From: Togan Muftuoglu <toganm@dinamizm.com>
In-Reply-To: <20021130T184245.GA13187.pat@wahoo.no-ip.org> In-Reply-To: <20021130T184245.GA13187.pat@wahoo.no-ip.org> In-Reply-To: <200212011339.22290.gqs@iinet.net.au> In-Reply-To: <20021201145125.GE17190@dinamizm.com>
Message-ID: <20021130T184245.GA13187.pat@wahoo.no-ip.org> Message-ID: <20021130T184245.GA13187.pat@wahoo.no-ip.org> Message-ID: <20021201145125.GE17190@dinamizm.com> Message-Id: <200212020253.57877.gqs@iinet.net.au>
Subject: Re: [SLE] [SOLVED] firewall blocks xntp system time maintenance Subject: Re: [SLE] [SOLVED] firewall blocks xntp system time maintenance Subject: [SLE] [SOLVED ALL] firewall blocks xntp system time maintenance Subject: [SLE] [SOLVED] firewall blocks xntp system time maintenance -- Richard Bos Without a home the journey is endless
participants (4)
-
Anders Johansson -
Ole Kofoed Hansen -
Richard Bos -
Scott Jones