Re: Weird messages from IETF/Google Mailservers (WG: PALS WG Adoption poll draft-schmutzer-pals-ple)

[Tero Kivinen <[e-mail]>]

Andrew G. Malis writes:
> There's a difference between email sent to an IETF email list (which
> uses mailman to handle email authentication issues by acting as the
> email source) and to an IETF email expander like pals-chairs, which
> doesn't.
> 
> When you're using an email expander, the original source of the
> email doesn't change, which exposes the email to any issues the
> original sender of the email may have. In this case, the issue is
> that Google is rejecting the email to pals-chairs because
> the telecom.de domain apparently doesn't support DKIM or SPF. This
> is the same issue as pi.nu.

Gmail is just being gmail, and decided that it does not like the
message because of reasons it does not disclose.

At least the email [e-mail] sent to wgclist did have
DKIM-signature (actually it had 3, one from telekom.de and two from
ietf.org, but those two were added because of wgchairs is mailing list
and does get different processing than aliases). And at least my own
machine did verify all of the DKIM signatures and they were valid. SPF
of course will always fail as email went through another machine in
the middle (i.e. ietf.org).

I would have assumed that the original email did have similar DKIM
signature (or perhaps they added support for DKIM between the error
message and message to wgchairs).

I have noticed it that even if you do have DKIM signatures gmail will
still claim you don't and will fail the message with this same error
message. 

The [e-mail] email had this DKIM signature:

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1;
 t=1685610015; x=1717146015; h=from:to:subject:date:message-id:
 content-transfer-encoding:mime-version;
 bh=0Bs+x5myny2oj+qksvqz5G/kVnfxOs31iLC9um0E72I=;
 b=pRG7GjOOFxXYsXLb1R+TPdubajZg57EpzhedEx1R7/Qy+t4jKrNmetew
 cx1Nlpm2TCjzCjDn5X6QgZmr+LcLUWezOy9BDB/PANRAxwog5t65AQR1I
 0rYvCfR6jILJFvogLYIZ5oDJDitDNfb/+iiY/PumAKf3ngzSQ5cfvpZj4
 mUBhGQBYT4PdiiBckxwoAneq9TwQJ78NL8eCRaoJmDihk3solbg/F89NS
 TdycS0nhHvib44zjbYIoGghmPFbGgLC39ed691tbzNW8XMVLT/pv3P8uC
 dhzfp2P8/uoTxue4j9OK1FfNee0Mt8vD8CjIZojQ/l4URNy6fGpOQdVzI g==;

and at least my machine claimed it was valid:

Authentication-Results: fireball.acr.fi;
	dkim=pass (1024-bit key) header.d=ietf.org header.i=@ietf.org header.b=iJv4PSgb8WpqTIfvHatgsBBj+zp+T1ODGWogzIlB4BBTcN91Rc3QgEjSobKuqa4RQwtb9ay0OynCUYwNEjRDHDM++qXXz4gx3M9FIBEfB94R//h4ffM55KFsGwKt7SV1avpmvXtQ7FRh84CRGeex2Ec+a/TIVGq+i0XgE5Wqw28=;
	dkim=pass (1024-bit key) header.d=ietf.org header.i=@ietf.org header.b=iJv4PSgb8WpqTIfvHatgsBBj+zp+T1ODGWogzIlB4BBTcN91Rc3QgEjSobKuqa4RQwtb9ay0OynCUYwNEjRDHDM++qXXz4gx3M9FIBEfB94R//h4ffM55KFsGwKt7SV1avpmvXtQ7FRh84CRGeex2Ec+a/TIVGq+i0XgE5Wqw28=;
	dkim=pass (2048-bit key) header.d=telekom.de header.i=@telekom.de header.b=pRG7GjOOFxXYsXLb1R+TPdubajZg57EpzhedEx1R7/Qy+t4jKrNmetewcx1Nlpm2TCjzCjDn5X6QgZmr+LcLUWezOy9BDB/PANRAxwog5t65AQR1I0rYvCfR6jILJFvogLYIZ5oDJDitDNfb/+iiY/PumAKf3ngzSQ5cfvpZj4mUB
-- 
[e-mail]