<html><head></head><body><div class="ydpc70e06d8yahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:13px;" dir="ltr" data-setdir="false"><div></div><div dir="ltr" data-setdir="false">In reading Google's <a href="https://support.google.com/mail/answer/81126?hl=en" rel="nofollow" target="_blank">https://support.google.com/mail/answer/81126?hl=en</a> on this issue, I submitted a request to have them stop blocking our email. From that url reference, it states the requirement for SPF <b><font size="3">or</font></b> DKIM is for new senders rather than existing ones. See quote below<br></div><blockquote><div dir="ltr" data-setdir="false"><span><br></span></div><div><div><span>"Important:<strong> </strong>Starting November 2022, new senders who send email to personal Gmail accounts must set up either <a href="https://support.google.com/mail/answer/81126?hl=en#spf" rel="nofollow" target="_blank" class="">SPF</a> or <a href="https://support.google.com/mail/answer/81126?hl=en#dkim" rel="nofollow" target="_blank" class="">DKIM</a>.
Google performs random checks on new sender messages to personal Gmail
accounts to verify they’re authenticated. Messages without at least one
of these authentication methods will be rejected or marked as spam. <b><font size="3">This
requirement doesn’t apply to you if you’re an existing sender.</font></b> However,
we recommend you always set up SPF and DKIM to protect your
organization’s email and to support future authentication requirements."</span></div><div><br><span></span></div></div></blockquote><div><div dir="ltr" data-setdir="false"><font size="3">Also, I "think" we do have DKIM implemented (their note says SPF <b>OR</b> DKIM) if I interpret further down on the "Original Message Header" where it says:</font></div></div><div dir="ltr" data-setdir="false"><div dir="ltr" data-setdir="false"><br></div><div dir="ltr" data-setdir="false"><span><pre class="ydp24f2109fraw_message_text" id="ydp24f2109fraw_message_text">X-Google-<b>DKIM</b>-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=tC7A9s8TYaZ/CGSJrVYNtkOfA1/MYvlOmV3tooyZOs4=; </pre></span><div><br></div><div dir="ltr" data-setdir="false"><font size="3">But anyway, I will see if I can figure out how to implement SPF like they suggest. A lot of the things I am trying to do is quite difficult for me and beyond my skill set. ...Phyllis<br></font></div></div><div><font size="3"><br></font></div><br></div><div><br></div>
</div><div id="ydpadbbd2ecyahoo_quoted_9402885215" class="ydpadbbd2ecyahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Friday, March 10, 2023 at 12:56:53 AM MST, Georgy Salnikov via Cin <cin@lists.cinelerra-gg.org> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">On Fri, 10 Mar 2023, Andrea paz via Cin wrote:<br clear="none"><br clear="none">> Do you know a way to set gmail to recognize our mailing list? I don't<br clear="none">> know how to do it.<br clear="none"><br clear="none">Andrea, it is because of DMARC authentication failure, see mail headers:<br clear="none"><br clear="none">Return-Path: <<a shape="rect" href="mailto:cin-bounces@lists.cinelerra-gg.org" rel="nofollow" target="_blank">cin-bounces@lists.cinelerra-gg.org</a>><br clear="none">.......<br clear="none">Authentication-Results: nioch.nioch.nsc.ru; dmarc=fail (p=none dis=none) header.from=lists.cinelerra-gg.org<br clear="none"> ^^^^^^^^^^<br clear="none">Authentication-Results: nioch.nioch.nsc.ru; spf=none smtp.mailfrom=cin-bounces@lists.cinelerra-gg.org (client-ip=94.16.115.56)<br clear="none">.......<br clear="none">Received: from lists.cinelerra-gg.org (v22018103128575622.happysrv.de [94.16.115.56])<br clear="none">.......<br clear="none">X-Received-SPF: none receiver=nioch.nioch.nsc.ru client-ip=94.16.115.56 envelope-from=<<a shape="rect" href="mailto:cin-bounces@lists.cinelerra-gg.org" rel="nofollow" target="_blank">cin-bounces@lists.cinelerra-gg.org</a>><br clear="none"><br clear="none">@lists.cinelerra-gg.org has neither its own DKIM nor DNS SPF record.<br clear="none"><br clear="none">Either the admin of the @lists.cinelerra-gg.org mail server has to implement<br clear="none">generation of DKIM signatures and attaching them to emails submitted from<br clear="none">this mailing list,<br clear="none"><br clear="none">Or the admin of the lists.cinelerra-gg.org DNS domain has to add the proper<br clear="none">SPF records to the DNS zone file.<br clear="none"><br clear="none">Only the corresponding admin can do that, for us, users, this is not<br clear="none">possible.<br clear="none">_______________________________________________________________________________<br clear="none"><br clear="none">Georgy Salnikov<br clear="none">NMR Group<br clear="none">Novosibirsk Institute of Organic Chemistry<br clear="none">Lavrentjeva, 9, 630090 Novosibirsk, Russia<br clear="none">Phone +7-383-3307864<br clear="none">Email <a shape="rect" href="mailto:sge@nmr.nioch.nsc.ru" rel="nofollow" target="_blank">sge@nmr.nioch.nsc.ru</a><div class="ydpadbbd2ecyqt7725283755" id="ydpadbbd2ecyqtfd29058"><br clear="none">_______________________________________________________________________________<br clear="none"><br clear="none"><br clear="none"><br clear="none">-- <br clear="none">Cin mailing list<br clear="none"><a shape="rect" href="mailto:Cin@lists.cinelerra-gg.org" rel="nofollow" target="_blank">Cin@lists.cinelerra-gg.org</a><br clear="none"><a shape="rect" href="https://lists.cinelerra-gg.org/mailman/listinfo/cin" rel="nofollow" target="_blank">https://lists.cinelerra-gg.org/mailman/listinfo/cin</a><br clear="none"></div></div></div>
</div>
</div></body></html>