Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DKIM: Internal error / Cannot extract the list identifier from the List-Id header #262

Closed
SilmorSenedlen opened this issue May 15, 2021 · 3 comments
Assignees
Labels
Milestone

Comments

@SilmorSenedlen
Copy link

SilmorSenedlen commented May 15, 2021

Good day.
I got "Internal error" on that message:

Headers
Return-Path: <postmaster@spsndr.com>
Delivered-To: xxxxx@vivaldi.net
Received: from mxi-2.vivaldi.net ([10.10.10.99])
	by imap.viv.dc01 with LMTP
	id wGvMKti7m2ARRgAADDaM4Q
	(envelope-from <postmaster@spsndr.com>)
	for <xxxxx@vivaldi.net>; Wed, 12 May 2021 11:28:24 +0000
Received: from localhost (localhost [127.0.0.1])
	by mxi-2.vivaldi.net (Postfix) with ESMTP id AA0E9BD620
	for <xxxxx@vivaldi.net>; Wed, 12 May 2021 11:28:24 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at vivaldi.net
X-Spam-Flag: NO
X-Spam-Score: -2.087
X-Spam-Level:
X-Spam-Status: No, score=-2.087 tagged_above=-9999 required=6.31
	tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
	DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1,
	HEADER_FROM_DIFFERENT_DOMAINS=1, HTML_MESSAGE=0.001,
	MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_BLOCKED=0.001,
	SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_TVD_MIME_NO_HEADERS=0.01,
	URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mxi-2.vivaldi.net ([IPv6:::1])
	by localhost (mxi-2.viv.dc01 [IPv6:::1]) (amavisd-new, port 10024)
	with ESMTP id hfFK3QEimMwU for <xxxxx@vivaldi.net>;
	Wed, 12 May 2021 11:28:22 +0000 (UTC)
Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=213.109.77.167; helo=mx8.spsndr.com; envelope-from=postmaster@spsndr.com; receiver=<UNKNOWN> 
Authentication-Results: mxi-2.vivaldi.net; dmarc=pass (p=quarantine dis=none) header.from=intickets.ru
Authentication-Results: mxi-2.vivaldi.net; spf=pass smtp.mailfrom=postmaster@spsndr.com
DKIM-Filter: OpenDKIM Filter v2.11.0 mxi-2.vivaldi.net 670B0BD033
Authentication-Results: mxi-2.vivaldi.net;
	dkim=pass (1024-bit key; unprotected) header.d=intickets.ru header.i=@intickets.ru header.a=rsa-sha256 header.s=sign header.b=YgY2IFzc;
	dkim=pass (1024-bit key; unprotected) header.d=spsndr.com header.i=@spsndr.com header.a=rsa-sha256 header.s=sign header.b=LBCv0Wyd;
	dkim-atps=neutral
X-policyd-weight:  NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_SPAMCOP=-1.5 (only DNSBL check requested)
Received: from mx8.spsndr.com (mx8.spsndr.com [213.109.77.167])
	by mxi-2.vivaldi.net (Postfix) with ESMTPS id 670B0BD033
	for <xxxxx@vivaldi.net>; Wed, 12 May 2021 11:28:20 +0000 (UTC)
Content-Type: multipart/alternative;
 boundary="===============3495852810030413337=="
MIME-Version: 1.0
From: =?utf-8?q?INTICKETS=2ERU?= <info@intickets.ru>
Precedence: bulk
Feedback-ID: 14284362:6608875:es:SP
List-ID: 89268557@spsndr.com
Subject: =?utf-8?b?0JjQvdGC0LjQutC10YLRgSDRg9Cy0LXQtNC+0LzQu9GP0LXRgiDQviDQv9C10YDQtdC90L7RgdC1INC80LXRgNC+0L/RgNC40Y/RgtC40Y8u?=
Date: Wed, 12 May 2021 11:28:19 +0000 (GMT)
Sender: info@intickets.ru
X-Authenticated-User: 5c6e485063f081200d2c2ff9904a678d@intickets.ru
Errors-To: postmaster@spsndr.com
X-Complaints-To: abuse@spsndr.com
To: xxxxx@vivaldi.net
Message-Id: <qszrv7-1015bv-p4@spsndr.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intickets.ru; 
 i=@intickets.ru; q=dns/txt; s=sign; t=1620818899; 
 x=1620854899; h=subject : from : to : message-id : cc; 
 bh=m5hYdS7dS0ixsyOJXK3n/k46pRJJQasLYy0/RTcbRg4=; 
 b=YgY2IFzc4AsApolWKiMXxOuYwpkHAUMaim22DkCZjQJmKssBK1z/DMiW
 RX5J+/eTyvC+A578UqQ0Sndl3gXi3C6VFY+5fxTp5NYctEeZB5n/ZCwRpQ
 xxNORxsAUW9kro52J+tpUSTyNIam0djNQtJ7VORbMKadONEvGniBF4khY=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=spsndr.com; 
 i=@spsndr.com; q=dns/txt; s=sign; t=1620818899; 
 x=1620854899; h=subject : from : to : message-id : cc; 
 bh=m5hYdS7dS0ixsyOJXK3n/k46pRJJQasLYy0/RTcbRg4=; 
 b=LBCv0WydEQ0DM9pOXVJ0dk3mSumdLauuhABcRfphLrCla7bQjNyW+joI
 3zWUeNVJBW3Rhe/r8ZFTBd5pTZY6xfsmTudbE6ijBNG7q+c3Ei6FoxVRju
 ov9DAm79Zn+zePpIznb8KO4C/DvXfFNbkKL05coXrP4JBkTEsckIG/sKU=

Debug info:

DKIM_Verifier.background	FATAL	 Unexpected error during verifyMessage 
Error: Cannot extract the list identifier from the List-Id header.

parseListIdHeader moz-extension://3c77a0e6-0efe-4d74-859e-4604b92e340d/modules/msgParser.mjs.js:191
verify moz-extension://3c77a0e6-0efe-4d74-859e-4604b92e340d/modules/authVerifier.mjs.js:135
verifyMessage moz-extension://3c77a0e6-0efe-4d74-859e-4604b92e340d/content/background.mjs.js:133
	
background.mjs.js:133:7

Any clues what's the reason?

DKIM Verifier 4.0.0 / Thunderbird 78.10.1 x64 / Windows 10 (1809) x64

@SilmorSenedlen SilmorSenedlen changed the title DKIM: Internal error DKIM: Internal error / Cannot extract the list identifier from the List-Id header May 15, 2021
@lieser
Copy link
Owner

lieser commented May 15, 2021

Thanks a lot for reporting.

The List-Id header has an invalid format. Unlike the e.g. From address it must always be in angle-brackets (<, >) https://datatracker.ietf.org/doc/html/rfc2919#section-3.

Even if I am a big fan of strict parsing, depending on how common this violation is we may still need to accept that violation. But similar to #238, it definitely needs a better error message.

@lieser lieser added the bug label May 15, 2021
@lieser lieser added this to the 4.1.0 milestone May 15, 2021
@SilmorSenedlen
Copy link
Author

Understood.
Thanks for explanation.

lieser added a commit that referenced this issue Jul 3, 2021
@lieser lieser self-assigned this Jul 3, 2021
@lieser
Copy link
Owner

lieser commented Jul 3, 2021

The next version will simply ignore an invalid list id.

@lieser lieser closed this as completed Jul 3, 2021
dodmi added a commit to dodmi/dkim_verifier that referenced this issue Feb 7, 2022
lieser pushed a commit to dodmi/dkim_verifier that referenced this issue Feb 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants