You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by "White, Daniel E. (GSFC-770.0)[AEGIS] via users" <us...@spamassassin.apache.org> on 2023/04/20 12:25:50 UTC

Re: [EXTERNAL] [BULK] Re: Mailing list is being Spam Filtered by O-365

Thanks for the detail.
This is good ammunition to go after the techno-pinheads that probably did this to us.

From: Noel Butler <no...@ausics.net>
Date: Thursday, April 20, 2023 at 08:19
To: "users@spamassassin.apache.org" <us...@spamassassin.apache.org>
Subject: [EXTERNAL] [BULK] Re: Mailing list is being Spam Filtered by O-365


Ohhhhh, same IP again in this message, you are forwarding your mail via verizon business aren't you, no, there is nothing wrong with SA, FR lists nor Harrys setup.... when you forward, you risk breakage, only you can deal with this.



On 20/04/2023 22:08, White, Daniel E. (GSFC-770.0)[AEGIS] via users wrote:

Sorrry.

Mixing up lists



Received: from BL0GCC02FT027.eop-gcc02.prod.protection.outlook.com

(2a01:111:f400:7d05::201) by CY4PR09CA0046.outlook.office365.com

(2603:10b6:903:c0::32) with Microsoft SMTP Server (version=TLS1_2,

cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6319.25 via Frontend

Transport; Thu, 20 Apr 2023 11:50:41 +0000

Authentication-Results: spf=fail (sender IP is 63.88.93.251) <------------------------------

smtp.mailfrom=thelounge.net; dkim=none (message not signed) <------------------------------

header.d=none;dmarc=none action=none header.from=thelounge.net;compauth=fail

reason=001

Received-SPF: Fail (protection.outlook.com: domain of thelounge.net does not

designate 63.88.93.251 as permitted sender) receiver=protection.outlook.com;

client-ip=63.88.93.251; helo=vsmtpx-e100-03.localdomain;



From: Reindl Harald <h....@thelounge.net>
Organization: the lounge interactive design
Date: Thursday, April 20, 2023 at 07:50
To: Daniel White <da...@nasa.gov>, "users@spamassassin.apache.org" <us...@spamassassin.apache.org>
Subject: Re: [EXTERNAL] Re: Mailing list is being Spam Filtered by O-365

 Am 20.04.23 um 13:47 schrieb White, Daniel E. (GSFC-770.0)[AEGIS] via users:

How about this:



how about realize that "@lists.freeradius.org" has nothing to do with

"@spamassassin.apache.org"?



Received: from BL0GCC02FT019.eop-gcc02.prod.protection.outlook.com

   (2a01:111:f400:7d05::201) by CYXPR09CA0020.outlook.office365.com

   (2603:10b6:930:d4::27) with Microsoft SMTP Server (version=TLS1_2,

   cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.6319.25 via Frontend

   Transport; Thu, 20 Apr 2023 11:27:54 +0000

Authentication-Results: spf=fail (sender IP is 63.88.93.251)  <-------------------------

   smtp.mailfrom=lists.freeradius.org; dkim=none (message not signed)

   header.d=none;dmarc=fail action=oreject

   header.from=lists.freeradius.org;compauth=none reason=452

Received-SPF: Fail (protection.outlook.com: domain of lists.freeradius.org  <-------------------------

   does not designate 63.88.93.251 as permitted sender)

   receiver=protection.outlook.com; client-ip=63.88.93.251;

   helo=vsmtpx-e100-01.localdomain;



From: Reindl Harald <h....@thelounge.net>>

Organization: the lounge interactive design

Date: Thursday, April 20, 2023 at 07:36

Subject: [EXTERNAL] Re: Mailing list is being Spam Filtered by O-365



Am 20.04.23 um 13:20 schrieb White, Daniel E. (GSFC-770.0)[AEGIS] via users:

Is there any chance that SPF and DKIM records could be added to appear in the headers ?



what makes you believe that SPF is part of mail-headers?



dig +short TXT spamassassin.apache.org;

"spf2.0/pra ?all"

"v=spf1 include:_spf.apache.org -all"



Received-SPF: Pass (mailfrom) identity=mailfrom;