> On 19 Apr 2022, at 16:11, Michael Peddemors via mailop <mailop@mailop.org> > wrote: > > And we also see that they have not yet 'hard enforced', but it looks like > some trigger on a domain results in requiring SPF for that domain. > > Of course, we don't expect Google to reveal their secrets, but we can assume > things like new IP(s), new domains, sudden traffic surges, or customers > clicking on 'this is spam' all might cause the requirement for SPF on a > certain domain.
These were sent from a consumer DSL line with no reverse DNS that’s listed on at least one widely used “never accept mail from this IP” list, that has virtually no history of IP traffic and zero history of sending email. The mail was sent with no SPF, and no DKIM. One of them was sent with no valid return path, no valid Message-ID, no valid From: header. Short of my including an EICAR test string and an animated gif of me waving a flag saying “DON’T ACCEPT THIS MAIL” I can’t think of much else I could do to look less trustworthy. They both were accepted for delivery just fine. If you’re being blocked by Google, or “Google is requiring SPF to be accepted” or “I had to add DKIM to get mail accepted" then your sending infrastructure, history and mailstream reputation is worse than this test setup. Cheers, Steve > > > > On 2022-04-19 07:57, Laura Atkins via mailop wrote: >> Short version: google is not hard enforcing SPF presence. Copies of emails >> delivered to my google spam folder are attached. >>> On 19 Apr 2022, at 14:54, Lichtinger, Bernhard via mailop >>> <mailop@mailop.org <mailto:mailop@mailop.org>> wrote: >>> >>> Hi, >>> >>>> Well i have no SPF records. See [doraji.xyz <http://doraji.xyz>]. And all >>>> incoming emails go >>>> to Gmail(soyeo...@gmail.com <mailto:soyeo...@gmail.com>) by forwarding. >>>> The Gmail is my final inbox >>>> provider. Really there are no troubles, at least, to me... >>> >>> My observation is that Gmail enforces authentication via SPF or DKIM since >>> the first days of march 2022. >>> One of SPF or DKIM is sufficient to get mails delivered to Gmail. >>> It looks like Gmail imposes a DMARC policy of reject for every sender >>> domain ignoring the actual DNS entries for DMARC or their absence. >> We just did 2 tests, one with an email that violated half a dozen best >> practices and one that has a SPFSoftfail (with no DKIM). >> SPF SoftFail delivered to spam: >> Delivered-To: wttwla...@gmail.com <mailto:wttwla...@gmail.com> >> Received: by 2002:a05:6a20:54a6:b0:7d:b75e:81cc with SMTP id >> i38csp2956940pzk; >> Tue, 19 Apr 2022 07:44:59 -0700 (PDT) >> X-Google-Smtp-Source: >> >> ABdhPJznmP9P9y29YlGiaLzZTxw0NXW8HUbBKmVBAeegvyAXSFlmXFYoYl/b2Xkgh7yVLnt6UuK7 >> X-Received: by 2002:a5d:6d03:0:b0:20a:7af0:380f with SMTP id >> e3-20020a5d6d03000000b0020a7af0380fmr11823278wrq.148.1650379498973; >> Tue, 19 Apr 2022 07:44:58 -0700 (PDT) >> ARC-Seal: i=1; a=rsa-sha256; t=1650379498; cv=none; >> d=google.com <http://google.com>; s=arc-20160816; >> >> b=oAA3r/bEkAyRjN7ZL7C2R9PNSNlehAqTYFpiww5W9ojBBIcPeXwmLRZiMZr3B/Ug5d >> >> BiJezi7mylKI+UO2ywcAG7h1jmTAeizH3j1ghCzukMp2uh3w3oHZ64R+3JAAajACtRcH >> >> lc1BkI/RLdsj7uv7tU3ECElQPX80PC1/hPzxYzc8Si/U761BLX3gVgK+QBeie1HX81JO >> >> HJFtAqVxp/AaVFH4qZuScWJGC23wN5C2Q0pNIytEAc3xk2momvTNrNvYERAqPlYfz32c >> >> 9Li7Yh330SYhCfGwNrCM0tWZJN7/G9YFDPRyWbWh8j71Xqnx3M7XiNrXGPIbcBrvpoNw >> INbg== >> ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; >> d=google.com <http://google.com>; s=arc-20160816; >> h=message-id:subject:from:to:date; >> bh=ecGWgWCJeWxJFeM0urOVWP+KOlqqvsQYKOpYUP8nk7I=; >> >> b=P1PMZlNCzI7TENQ2QO8kaSWDTckbB3jDkrrzxUbjxzgJ/SfGFjHSJpyFttLPHKnatk >> >> pTDj/P5r07tRG7lQ4msWgKZocbyj3y5j6ZNqWRgs189MgDCAb1u533ZJlmRyzWZi2n/3 >> >> u50p14IatncLBfPrcxOwMACDBzPRd8P2h72VGcG5V9cRz27WziJmVOxtVEUJk5Hd+c2Z >> >> KoQ+Uzf/lRkGwcKo0MDcQ6qMG3swCdMioHmG4N26/VVOBSNDVbRJZ4J0KR+4TZNO4NlT >> >> gZZKMuWeQvr54C+rtg8ht/OekVrhbksGrKWNoicG78FwORNoUINzJVMAdxhVAWzvWAPq >> Vv2g== >> ARC-Authentication-Results: i=1; mx.google.com <http://mx.google.com>; >> spf=neutral (google.com <http://google.com>: 185.97.236.152 >> is neither permitted nor denied by best guess record for domain of >> steve@sliver) smtp.mailfrom=steve@sliver >> Return-Path: <steve@sliver> >> Received: from sliver ([185.97.236.152]) >> by mx.google.com <http://mx.google.com> with ESMTP id >> p7-20020adfe607000000b00203e90194c2si8108892wrm.582.2022.04.19.07.44.58 >> for <wttwla...@gmail.com <mailto:wttwla...@gmail.com>>; >> Tue, 19 Apr 2022 07:44:58 -0700 (PDT) >> Received-SPF: neutral (google.com <http://google.com>: >> 185.97.236.152 is neither permitted nor denied by best guess record >> for domain of steve@sliver) client-ip=185.97.236.152; >> Authentication-Results: mx.google.com <http://mx.google.com>; >> spf=neutral (google.com <http://google.com>: 185.97.236.152 >> is neither permitted nor denied by best guess record for domain of >> steve@sliver) smtp.mailfrom=steve@sliver >> Date: Tue, 19 Apr 2022 15:44:58 +0100 >> To: wttwla...@gmail.com <mailto:wttwla...@gmail.com> >> From: steve@sliver >> Subject: test Tue, 19 Apr 2022 15:44:58 +0100 >> Message-Id: <20220419154458.051019@sliver> >> X-Mailer: swaks v20201014.0 jetmore.org/john/code/swaks/ >> <http://jetmore.org/john/code/swaks/> >> This is a test mailing >> This message probably shouldn’t have been accepted. The number of spec and >> best practice violations is extremely high. But it, too, ended up in my spam >> folder. >> Delivered-To: wttwla...@gmail.com <mailto:wttwla...@gmail.com> >> Received: by 2002:a05:6a20:54a6:b0:7d:b75e:81cc with SMTP id >> i38csp2956940pzk; >> Tue, 19 Apr 2022 07:44:59 -0700 (PDT) >> X-Google-Smtp-Source: >> >> ABdhPJznmP9P9y29YlGiaLzZTxw0NXW8HUbBKmVBAeegvyAXSFlmXFYoYl/b2Xkgh7yVLnt6UuK7 >> X-Received: by 2002:a5d:6d03:0:b0:20a:7af0:380f with SMTP id >> e3-20020a5d6d03000000b0020a7af0380fmr11823278wrq.148.1650379498973; >> Tue, 19 Apr 2022 07:44:58 -0700 (PDT) >> ARC-Seal: i=1; a=rsa-sha256; t=1650379498; cv=none; >> d=google.com <http://google.com>; s=arc-20160816; >> >> b=oAA3r/bEkAyRjN7ZL7C2R9PNSNlehAqTYFpiww5W9ojBBIcPeXwmLRZiMZr3B/Ug5d >> >> BiJezi7mylKI+UO2ywcAG7h1jmTAeizH3j1ghCzukMp2uh3w3oHZ64R+3JAAajACtRcH >> >> lc1BkI/RLdsj7uv7tU3ECElQPX80PC1/hPzxYzc8Si/U761BLX3gVgK+QBeie1HX81JO >> >> HJFtAqVxp/AaVFH4qZuScWJGC23wN5C2Q0pNIytEAc3xk2momvTNrNvYERAqPlYfz32c >> >> 9Li7Yh330SYhCfGwNrCM0tWZJN7/G9YFDPRyWbWh8j71Xqnx3M7XiNrXGPIbcBrvpoNw >> INbg== >> ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; >> d=google.com <http://google.com>; s=arc-20160816; >> h=message-id:subject:from:to:date; >> bh=ecGWgWCJeWxJFeM0urOVWP+KOlqqvsQYKOpYUP8nk7I=; >> >> b=P1PMZlNCzI7TENQ2QO8kaSWDTckbB3jDkrrzxUbjxzgJ/SfGFjHSJpyFttLPHKnatk >> >> pTDj/P5r07tRG7lQ4msWgKZocbyj3y5j6ZNqWRgs189MgDCAb1u533ZJlmRyzWZi2n/3 >> >> u50p14IatncLBfPrcxOwMACDBzPRd8P2h72VGcG5V9cRz27WziJmVOxtVEUJk5Hd+c2Z >> >> KoQ+Uzf/lRkGwcKo0MDcQ6qMG3swCdMioHmG4N26/VVOBSNDVbRJZ4J0KR+4TZNO4NlT >> >> gZZKMuWeQvr54C+rtg8ht/OekVrhbksGrKWNoicG78FwORNoUINzJVMAdxhVAWzvWAPq >> Vv2g== >> ARC-Authentication-Results: i=1; mx.google.com <http://mx.google.com>; >> spf=neutral (google.com <http://google.com>: 185.97.236.152 >> is neither permitted nor denied by best guess record for domain of >> steve@sliver) smtp.mailfrom=steve@sliver >> Return-Path: <steve@sliver> >> Received: from sliver ([185.97.236.152]) >> by mx.google.com <http://mx.google.com> with ESMTP id >> p7-20020adfe607000000b00203e90194c2si8108892wrm.582.2022.04.19.07.44.58 >> for <wttwla...@gmail.com <mailto:wttwla...@gmail.com>>; >> Tue, 19 Apr 2022 07:44:58 -0700 (PDT) >> Received-SPF: neutral (google.com <http://google.com>: >> 185.97.236.152 is neither permitted nor denied by best guess record >> for domain of steve@sliver) client-ip=185.97.236.152; >> Authentication-Results: mx.google.com <http://mx.google.com>; >> spf=neutral (google.com <http://google.com>: 185.97.236.152 >> is neither permitted nor denied by best guess record for domain of >> steve@sliver) smtp.mailfrom=steve@sliver >> Date: Tue, 19 Apr 2022 15:44:58 +0100 >> To: wttwla...@gmail.com <mailto:wttwla...@gmail.com> >> From: steve@sliver >> Subject: test Tue, 19 Apr 2022 15:44:58 +0100 >> Message-Id: <20220419154458.051019@sliver> >> X-Mailer: swaks v20201014.0 jetmore.org/john/code/swaks/ >> <http://jetmore.org/john/code/swaks/> >> This is a test mailing >>> >>> >>> Regards, >>> Bernhard >>> >>> >>> _______________________________________________ >>> mailop mailing list >>> mailop@mailop.org <mailto:mailop@mailop.org> >>> https://list.mailop.org/listinfo/mailop >> -- >> The Delivery Experts >> Laura Atkins >> Word to the Wise >> la...@wordtothewise.com <mailto:la...@wordtothewise.com> >> Email Delivery Blog: http://wordtothewise.com/blog >> <http://wordtothewise.com/blog> >> _______________________________________________ >> mailop mailing list >> mailop@mailop.org >> https://list.mailop.org/listinfo/mailop > > > > -- > "Catch the Magic of Linux..." > ------------------------------------------------------------------------ > Michael Peddemors, President/CEO LinuxMagic Inc. > Visit us at http://www.linuxmagic.com @linuxmagic > A Wizard IT Company - For More Info http://www.wizard.ca > "LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd. > ------------------------------------------------------------------------ > 604-682-0300 Beautiful British Columbia, Canada > > This email and any electronic data contained are confidential and intended > solely for the use of the individual or entity to which they are addressed. > Please note that any views or opinions presented in this email are solely > those of the author and are not intended to represent those of the company. > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://list.mailop.org/listinfo/mailop _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
