[exim-dev] [Bug 2029] DKIM verification segfaults on some ma…

https://bugs.exim.org/show_bug.cgi?id=2029

--- Comment #4 from Michael Fischer v. Mollard <lists@???> ---
(In reply to Jeremy Harris from comment #2)
> Please have a look with gdb at the received headers. They are on a list
> starting at the global "header_list" and chained on the "next" element; the
> actual line is pointed to by the "text" element. I'd like to know about any
> lines starting "DKIM-Signature:".

Here are the headers – slightly anonymized. Feel free to ask me again if this
is a problem.

Received: from host60.findorthodontistnearyou.com ([198.102.11.94])
    by relay.XXXX.de with smtp (Exim 4.88)
    (envelope-from <XXXX.1873010.rh@???>)
    id 1cX7q3-0006LR-3W
    for XX@???; Fri, 27 Jan 2017 15:49:19 +0100
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed;
    d=findorthodontistnearyou.com; s=s512; l=18997; x=1486135427;
    h=From:To:Subject:Content-Type:Date:Message-ID; b=S9ifH87iYb2tPH
    6sJbRwKAdE3E53IWaRH51DhmBH8pTOImACqQ85V2I+9agUEwxQQyUGY45RIQKOYC
    tpN0hKHQ==
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;
    d=findorthodontistnearyou.com; s=s512; l=18997; x=1486135427;
    h=From:To:Subject:Content-Type:Date:Message-ID; bh=zR3SL8nNSn8W4
    Hudv4XBaY9dYKU=; b=kSqzK43wpu0QNoD8emNHhN2j6iDmaHI6y8LaEJ1pSvBG3
    un54EBUMi01RraRQkj/7ft4w2BomADCDbLTUBLM1A==
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s512; d=findorthodontistnearyou.com;

b=SXpqSiVMPQ5g0ZEMYT8XNk1tMpnubxGl6xaL7sKmdLluTNOW/PVlg1nLCg95TXnInOkWKaSaPPjaNBMZSOU1jQ==;
Received: from findorthodontistnearyou.com [198.102.11.94] by
findorthodontistnearyou.com [198.102.11.94];
Thu, 26 Jan 2017 22:45:24 +0100
MIME-Version: 1.0
From: eleana<eleana@???>
To: XX@???
Reply-To: eleana<eleana@???>
Subject: Lets get you some wins!
Content-Type: multipart/alternative;
boundary="-=3ffad4f9976c41406977821147232517";
Date: Thu, 26 Jan 2017 22:45:24 +0100
Message-ID: <2-1873010-UGZuU2cpVGaugXaAhmcH@???>
X-Mailer: 4.2.8-134 [Aug 22 2012, 22:57:59]

>
> These crashes will be leaving orphan -D files in the spool; you'll need to
> manually clean them out.

Thanks for mentioning. I'll take a look at them

--
You are receiving this mail because:
You are on the CC list for the bug.