Mailing List Archive

On 20.04.23 11:20, White, Daniel E. (GSFC-770.0)[AEGIS] via users wrote:
>Is there any chance that SPF and DKIM records could be added to appear in the headers ?

>The gubba-mint folks are getting extremely medieval about email security.

SPF is only a DNS issue.

DKIM headers, yes, you should sign your outgoing mail with DKIM.

--
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Micro$oft random number generator: 0, 0, 0, 4.33e+67, 0, 0, 0...

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;

______________________________________________________________________________________________

Daniel E. White
daniel.e.white@nasa.gov<mailto:daniel.e.white@nasa.gov>
NASCOM Linux Engineer
NASA Goddard Space Flight Center
Office: (301) 286-6919
Mobile: (240) 513-5290

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

CAUTION: This email originated from outside of NASA. Please take care when clicking links or opening attachments. Use the "Report Message" button to report suspicious messages to the NASA SOC.




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.reindl@thelounge.net<mailto:h.reindl@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;
client-ip=3.227.148.255; helo=mxout1-ec2-va.apache.org

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;
>
> ______________________________________________________________________________________________
>
> Daniel E. White
> daniel.e.white@nasa.gov
>
> NASCOM Linux Engineer
> NASA Goddard Space Flight Center
> Office: (301) 286-6919
>
> Mobile: (240) 513-5290
>
> From: Reindl Harald <h.reindl@thelounge.net>
> Organization: the lounge interactive design
> Date: Thursday, April 20, 2023 at 07:50
> To: Daniel White <daniel.e.white@nasa.gov>,
> "users@spamassassin.apache.org" <users@spamassassin.apache.org>
> Subject: Re: [EXTERNAL] Re: Mailing list is being Spam Filtered by
> O-365
>
> CAUTION: This email originated from outside of NASA. Please take care
> when clicking links or opening attachments. Use the "Report Message"
> button to report suspicious messages to the NASA SOC.
>
> 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.reindl@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;
>
> client-ip=3.227.148.255; helo=mxout1-ec2-va.apache.org

--
Regards,
Noel Butler

This Email, including attachments, may contain legally privileged
information, therefore at all times remains confidential and subject to
copyright protected under international law. You may not disseminate
this message without the authors express written authority to do so.
If you are not the intended recipient, please notify the sender then
delete all copies of this message including attachments immediately.
Confidentiality, copyright, and legal privilege are not waived or lost
by reason of the mistaken delivery of this message.

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

From: Noel Butler <noel.butler@ausics.net>
Date: Thursday, April 20, 2023 at 08:19
To: "users@spamassassin.apache.org" <users@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.reindl@thelounge.net>
Organization: the lounge interactive design
Date: Thursday, April 20, 2023 at 07:50
To: Daniel White <daniel.e.white@nasa.gov>, "users@spamassassin.apache.org" <users@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.reindl@thelounge.net<mailto:h.reindl@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;

Forget I asked, please.
I got enough detail to know it is not the fault of the lists.

White, Daniel E. (GSFC-770.0)[AEGIS] via users skrev den 2023-04-20
13:20:
> Is there any chance that SPF and DKIM records could be added to appear
> in the headers ?

ARC-Authentication-Results i=1; mx.microsoft.com 1; spf=pass
smtp.mailfrom=nasa.gov; dmarc=pass action=none header.from=nasa.gov;
dkim=pass header.d=nasa.gov; arc=none

its already there ?

> The gubba-mint folks are getting extremely medieval about email
> security.

unknown here

Matus UHLAR - fantomas skrev den 2023-04-20 13:44:
> On 20.04.23 11:20, White, Daniel E. (GSFC-770.0)[AEGIS] via users
> wrote:
>> Is there any chance that SPF and DKIM records could be added to appear
>> in the headers ?
>
>> The gubba-mint folks are getting extremely medieval about email
>> security.
>
> SPF is only a DNS issue.

only true if domain is not dmarc protected

> DKIM headers, yes, you should sign your outgoing mail with DKIM.

dkim can in dkim spec have t=s; so ensured always aligned to make dkim
pass

White, Daniel E. (GSFC-770.0)[AEGIS] via users skrev den 2023-04-20
14:35:
> Forget I asked, please.
>
> I got enough detail to know it is not the fault of the lists.

+1, spamassassin does not break dkim like other maillists does !

>>On 20.04.23 11:20, White, Daniel E. (GSFC-770.0)[AEGIS] via users
>>wrote:
>>>Is there any chance that SPF and DKIM records could be added to
>>>appear in the headers ?
>>
>>>The gubba-mint folks are getting extremely medieval about email
>>>security.

>Matus UHLAR - fantomas skrev den 2023-04-20 13:44:
>>SPF is only a DNS issue.

On 20.04.23 17:48, Benny Pedersen wrote:
>only true if domain is not dmarc protected

I repeat. SPF is a DNS-only issue. It's not related to mail headers.

however, the OP has already confirmed that this problem was already explained.

>>DKIM headers, yes, you should sign your outgoing mail with DKIM.
>
>dkim can in dkim spec have t=s; so ensured always aligned to make dkim
>pass

--
Matus UHLAR - fantomas, uhlar@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Linux - It's now safe to turn on your computer.
Linux - Teraz mozete pocitac bez obav zapnut.