| Summary: | When i receive a message from a specific person Kmail is not able to retrieve mail | ||
|---|---|---|---|
| Product: | [Unmaintained] kmail | Reporter: | Cedric Tardif <sysadmin> |
| Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | CC: | mironov |
| Priority: | NOR | ||
| Version: | 1.6.1 | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
kmail-bug.email.txt
email that causes this error for me same bug different sender |
||
|
Description
Cedric Tardif
2004-04-13 17:35:57 UTC
Could you please send the mail to me sanders@kde.org as an attachment (rather than copied in-line)? Interesting bug report. Don. Hi, there is the mail attached. Regards Le April 14, 2004 02:39 am, Don Sanders a écrit : > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=79569 > > > > > ------- Additional Comments From sanders kde org 2004-04-14 08:39 ------- > Could you please send the mail to me sanders kde org as an attachment > (rather than copied in-line)? > > Interesting bug report. > > Don. Created an attachment (id=5637) kmail-bug.email.txt I have a similar issue, however I wasn't able to recover the specific email that caused the problem. I have a secondary issue cause by this bug as well. After I close the error window kmail seems to continue along fine. However, it appears that this error also causes kmail to segfault when I exit instead of expiring/compacting everything. Created attachment 6511 [details]
email that causes this error for me
This email caused the LIST error for me today. My guess is the Message-ID
header could be the problem.
*** Bug 80190 has been marked as a duplicate of this bug. *** I got a message from someone else that cause the same problem There the message : ___________________________________________ Return-Path: <users-return-16117-sysadmin=destination.ca@spamassassin.apache.org> Received: from localhost (ns1.destination.ca [207.253.148.2] (may be forged)) by champlain.destination.ca (8.12.10/8.12.10) with ESMTP id i8KFwgrx017232 for <sysadmin@destination.ca>; Mon, 20 Sep 2004 11:58:42 -0400 Received: from thalassa.destination.ca ([127.0.0.1]) by localhost (thalassa.destination.ca [127.0.0.1]) (ANTISPAM-SMTP, port 10024) with LMTP id 32672-03 for <sysadmin@destination.ca>; Mon, 20 Sep 2004 11:58:39 -0400 (EDT) Received: from mail.apache.org (hermes.apache.org [209.237.227.199]) by thalassa.destination.ca (8.12.10/8.12.10) with SMTP id i8KFwZEm032704 for <sysadmin@destination.ca>; Mon, 20 Sep 2004 11:58:35 -0400 Received: (qmail 56151 invoked by uid 500); 20 Sep 2004 15:57:59 -0000 Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm Precedence: bulk list-help: <mailto:users-help@spamassassin.apache.org> list-unsubscribe: <mailto:users-unsubscribe@spamassassin.apache.org> list-post: <mailto:users@spamassassin.apache.org> List-Id: <users.spamassassin.apache.org> Delivered-To: mailing list users@spamassassin.apache.org Received: (qmail 55957 invoked by uid 99); 20 Sep 2004 15:57:58 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Received-SPF: unknown (hermes.apache.org: error in processing during lookup of lst_sa@bquest.org) Received: from [194.90.9.27] (HELO mxout4.netvision.net.il) (194.90.9.27) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 20 Sep 2004 08:57:57 -0700 Received: from bquest-srv.bquest-lan.bquest.org ([217.132.166.27]) by mxout4.netvision.net.il (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep 8 2003)) with ESMTP id <0I4C003LKKCEU1@mxout4.netvision.net.il> for users@spamassassin.apache.org; Mon, 20 Sep 2004 18:57:50 +0300 (IDT) Date: Mon, 20 Sep 2004 18:57:45 +0300 From: Avi Shatz <lst_sa@bquest.org> Subject: RE: SPF Fails on SA 3.0rc5 because of lack of HELO ? To: users@spamassassin.apache.org Message-id: <B54F74CD4401AA4DAB071943AD0CE7922426@bquest-srv.bquest-lan.bquest.org> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.3790.181 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-class: urn:content-classes:message Thread-topic: SPF Fails on SA 3.0rc5 because of lack of HELO ? Thread-index: AcSfKImuhz/Jx4GJR7mJMGmFq8wzRwAATz+w x-fsavag4mse-ts: dfeb32c2f67a7339 X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Virus-Checked: Checked X-Virus-Scanned: Par Destination Internet Inc. (http://www.destination.ca) X-Spam-Status: No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00 X-Spam-Level: > And since nothing is special about my own MS SMTPSVC (Win2k3 SMTP > Server), I believe the behavior of received.pm should be changed to > allow SA running on those machines to properly detect the EHLO > string, and thus allow SPF Detection to properly execute. So what *do* your mail headers look like when your HELO or EHLO argument is not the FQDN of the connecting host? Most MTAs will VERY carefully include these two pieces of information separately: sendmail for instance, will show something like: Well, lets say for instance the HELO string is "Hello_string" Remote IP is: "11.22.33.44" My mail server DNS is: "localmta.org" And the receiving time is: Sat, 18 Sep 2004 19:53:03 +0300 The resulting received line would be: Received: from Hello_string ([11.22.33.44]) by localmta.org with Microsoft SMTPSVC(6.0.3790.80); Sat, 18 Sep 2004 19:53:03 +0300 Actually Received.pm already includes support for this MTA with this line: # Received: from inet-vrs-05.redmond.corp.microsoft.com ([157.54.6.157]) by # INET-IMC-05.redmond.corp.microsoft.com with Microsoft SMTPSVC(5.0.2195.6624); # Thu, 6 Mar 2003 12:02:35 -0800 if (/^from (\S+) \(\[(${IP_ADDRESS})\]\) by (\S+) with /) { $helo = $1; $ip = $2; $by = $3; goto enough; } Problem is that its never triggered, because of a previous *incorrect* hit Created attachment 7596 [details]
same bug different sender
In KMail 1.7 message is shown ok. Which version are you using? Are you still seing this issue woith KMail 1.8 or newer? I'M still using kmail 1.6.1. I will update my OS in a few days and i will be able to test with a recent kmail. I just updated KDE and KMail. I'm now using KMAIL 1.9 and i still have the same problem with some e-mail. Do you want the header of the e-mail that are still not working of it ok with the old one you have ? *** This bug has been marked as a duplicate of 127696 *** |