Hi,
David Wright wrote:
> I'm subscribed, but I don't receive that badge of honour.
> This is from my other post in this thread—no LDOSUBSCRIBER:
>
> > X-Spam-Status: No, score=-4.9 required=4.0 tests=CAPINIT,FOURLA,
> > HEADER_FROM_DIFFERENT_DOMAINS,LDO_WHITELIST,RCVD_IN_DNSWL_LOW,
> > T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no
> > version=3.4.2
This is known to happen if the mail is sent from an address that is different
from the subscribed mail address. Maybe you discovered a new cause.
> I'm guessing your last example is Curt's.
> > X-Spam-Status: No,
> > score=-10.5 required=4.0 tests=FREEMAIL_FORGED_FROMDOMAIN,
> > FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS,LDOSUBSCRIBER,
> > LDO_WHITELIST,T_SCC_BODY_TEXT_LINE autolearn=unavailable
> > autolearn_force=no version=3.4.2
Yes. It's from:
Subject: Re: rhs time out error?
Date: Sun, 26 Nov 2023 16:30:02 -0000 (UTC)
Message-ID: <slrnum6ska.1gl.cu...@einstein.electron.org>
> The only occurrence of
> the From: address in the entire email is in the From: line.
> That's no different from my own post, except for the lines at the
> very top, which show my post being delivered to me.
>
> I had thought the server was using the envelope-from in order to
> identify subscribers, yet Curt's posts, like mine, have different
> envelope-from and From: addresses, which is presumably the reason
> behind HEADER_FROM_DIFFERENT_DOMAINS.
HEADER_FROM_DIFFERENT_DOMAINS would have been my first suspicion, too.
But i see no "envelope-from" Curt's mail and yours.
Only
Envelope-To: <scdbac...@gmx.net>
(If "envelope-from" is a typo and "Envelope-To:" differs from "From:",
then we'd probably have the situation of different sender and receiver.)
It would be interesting to see all "Received:" headers of your own
mail when it arrives back to you. I see in your mail to which i now reply:
Received: from bendel.debian.org ([82.195.75.100]) by mx-ha.gmx.net
(mxgmx109
[212.227.17.5]) with ESMTPS (Nemesis) id 1MZzsi-1qmfcQ0kRo-00R0wN for
<scdbac...@gmx.net>; Sun, 03 Dec 2023 05:24:06 +0100
Received: from localhost (localhost [127.0.0.1])
by bendel.debian.org (Postfix) with QMQP
id 0F8C9209D5; Sun, 3 Dec 2023 04:23:55 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by bendel.debian.org (Postfix) with ESMTP id 0413D20837
for <lists-debian-u...@bendel.debian.org>; Sun,
3 Dec 2023 04:23:42 +0000 (UTC)
Received: from bendel.debian.org ([127.0.0.1])
by localhost (lists.debian.org [127.0.0.1]) (amavisd-new, port 2525)
with ESMTP id 1Ym_tsLfWzf6 for <lists-debian-u...@bendel.debian.org>;
Sun, 3 Dec 2023 04:23:33 +0000 (UTC)
Received: from omta012.uswest2.a.cloudfilter.net
(omta012.uswest2.a.cloudfilter.net [35.164.127.235])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(Client CN "Client", Issuer "CA" (not verified))
by bendel.debian.org (Postfix) with ESMTPS id 1A7BD209C6
for <debian-user@lists.debian.org>; Sun,
3 Dec 2023 04:23:32 +0000 (UTC)
Received: from cxr.smtp.a.cloudfilter.net ([10.0.16.145])
by cmsmtp with ESMTP
id 9deErTpHpaga99e0vrCJA8; Sun, 03 Dec 2023 04:23:29 +0000
Received: from axis.corp ([68.102.133.185])
by cmsmtp with ESMTPSA
id 9e0srwhHYTywR9e0urtWnm; Sun, 03 Dec 2023 04:23:29 +0000
All these headers except the first were added on the sender side, i.e
on the list server bendel.debian.org and in your mail provider's realm.
In a mail of mine to this list i see:
Received: from bendel.debian.org ([82.195.75.100]) by mx-ha.gmx.net
(mxgmx009
[212.227.15.9]) with ESMTPS (Nemesis) id 1MMYsv-1qsRpG2aBT-00SPIm for
<scdbac...@gmx.net>; Fri, 01 Dec 2023 21:11:45 +0100
Received: from localhost (localhost [127.0.0.1])
by bendel.debian.org (Postfix) with QMQP
id 869AC20BB3; Fri, 1 Dec 2023 20:11:33 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by bendel.debian.org (Postfix) with ESMTP id 920DB20B9A
for <lists-debian-u...@bendel.debian.org>; Fri,
1 Dec 2023 20:11:22 +0000 (UTC)
Received: from bendel.debian.org ([127.0.0.1])
by localhost (lists.debian.org [127.0.0.1]) (amavisd-new, port 2525)
with ESMTP id g1fSuxvi8ZX9 for <lists-debian-u...@bendel.debian.org>;
Fri, 1 Dec 2023 20:11:19 +0000 (UTC)
Received: from mout.gmx.net (mout.gmx.net [212.227.15.15])
(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits)
server-digest SHA256)
(Client did not present a certificate)
by bendel.debian.org (Postfix) with ESMTPS id 14F4520A27
for <debian-user@lists.debian.org>; Fri,
1 Dec 2023 20:11:19 +0000 (UTC)
Received: from scdbackup.webframe.org ([91.8.169.164]) by mail.gmx.net
(mrgmx005 [212.227.17.190]) with ESMTPSA (Nemesis) id
1Mqs0R-1reJbZ24e1-00mwgO for <debian-user@lists.debian.org>; Fri,
01 Dec 2023 21:11:16 +0100
So there is one mail relay hop more on your side, before the mail reaches
the Debian list server. I wonder whether this earns you the spam test
attribute HEADER_FROM_DIFFERENT_DOMAINS which i don't get in my mails:
X-Spam-Status: No, score=-12.0 required=4.0 tests=DKIM_SIGNED,DKIM_VALID,
DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,LDOSUBSCRIBER,LDO_WHITELIST,
RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H4,RCVD_IN_MSPIKE_WL,
T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no
version=3.4.2
Whatever, if i see no LDOSUBSCRIBER in a thread-starting mail from somebody
who not frequently replys to list mails, then i mildly violate the rules
by adding a Cc: to my reply. Just to be sure that it reaches the thread
starter.
But since this mail i'm currently writing is a tangent to the original
thread topic, i refrain from Cc-ing Pocket.
Have a nice day :)
Thomas
