I've just gotten notification that many of your accounts on my server were disabled due to excessive bounces, and all of those bounce notices were from gmail addresses. I dug a little deeper, and it seems Google changed the auth requirements for sending email to any gmail.com http://gmail.com/ account.
I don't have time right now to spend on this, but I will try to update things soon. And yes, I know that the people who are affected won't be able to receive this post, but maybe they'll be curious and check the archives.
-- Ed Leafe
Funny, all the mail in the archive showed up in my gmail folder. Maybe it's another case of Google rolling out new rules but not hitting everyone with them yet.
On Tue, Jul 30, 2024 at 10:35 AM Ed Leafe ed@leafe.com wrote:
I've just gotten notification that many of your accounts on my server were disabled due to excessive bounces, and all of those bounce notices were from gmail addresses. I dug a little deeper, and it seems Google changed the auth requirements for sending email to any gmail.com < http://gmail.com/%3E account.
I don't have time right now to spend on this, but I will try to update things soon. And yes, I know that the people who are affected won't be able to receive this post, but maybe they'll be curious and check the archives.
-- Ed Leafe
[excessive quoting removed by server]
On Jul 30, 2024, at 09:34, Ed Leafe ed@leafe.com wrote:
I've just gotten notification that many of your accounts on my server were disabled due to excessive bounces, and all of those bounce notices were from gmail addresses. I dug a little deeper, and it seems Google changed the auth requirements for sending email to any gmail.com http://gmail.com/ account.
I *think* I figured out the issue, so this is a test to see if it worked.
I've re-enabled the addresses that were disabled because of excessive bounces, so I'm sending this to see if they go through. <fingers crossed>
-- Ed Leafe
On Aug 1, 2024, at 17:55, Ed Leafe ed@leafe.com wrote:
I've re-enabled the addresses that were disabled because of excessive bounces, so I'm sending this to see if they go through. <fingers crossed>
Looks like there are still issues. Back to the drawing board!
-- Ed Leafe
Received here Ed. Dave
On Thu, Aug 1, 2024 at 11:56 PM Ed Leafe ed@leafe.com wrote:
On Jul 30, 2024, at 09:34, Ed Leafe ed@leafe.com wrote:
I've just gotten notification that many of your accounts on my server
were disabled due to excessive bounces, and all of those bounce notices were from gmail addresses. I dug a little deeper, and it seems Google changed the auth requirements for sending email to any gmail.com < http://gmail.com/%3E account.
I *think* I figured out the issue, so this is a test to see if it worked.
I've re-enabled the addresses that were disabled because of excessive bounces, so I'm sending this to see if they go through. <fingers crossed>
-- Ed Leafe
[excessive quoting removed by server]
On Aug 1, 2024, at 20:09, Dave Crozier r.d.crozier@gmail.com wrote:
Received here Ed.
Ack. I see some going through, but others with a message like:
Jul 28 00:08:44 mail postfix/smtp[36630]: 703B01206BF: to=billand88@gmail.com, relay=alt1.gmail-smtp-in.l.google.com[209.85.202.27]:25, delay=267185, delays=267153/0.02/31/0.88, dsn=4.7.30, status=deferred (host alt1.gmail-smtp-in.l.google.com[209.85.202.27] said: 421-4.7.30 Your email has been rate limited because DKIM authentication didn't 421-4.7.30 pass for this message. Gmail requires all bulk email senders to 421-4.7.30 authenticate with DKIM. 421-4.7.30 421-4.7.30 Authentication results: 421-4.7.30 DKIM = did not pass 421-4.7.30 To set up DKIM for your sending domains, visit 421-4.7.30 https://support.google.com/a?p=turn-on-dkim 421-4.7.30 To learn more about Gmail requirements for bulk senders, visit 421 4.7.30 https://support.google.com/a?p=sender-guidelines. a640c23a62f3a-a7aca7b84c7si471869166b.34 - gsmtp (in reply to end of DATA command))
I don't know if that means that they are being slowed down or discarded. Either way I need to update the DKIM settings on my server.
-- Ed Leafe
I'm on Gmail as tedroche@gmail.com and am getting messages. Viewing "show original" claims that DKIM passes. I'm on the profox tech list, in case that makes a difference. Here are the headers I'm seeing; looks like the header passes, but the body hash has an issue:
Delivered-To: tedroche@gmail.com Received: by 2002:a05:6919:ad86:b0:24d:6d3:1c10 with SMTP id cc6csp1781537ysc; Fri, 2 Aug 2024 05:44:27 -0700 (PDT) X-Forwarded-Encrypted: i=2; AJvYcCUc54iXs4nfJEyR/FPs+8sk1Ix8IfuxIw4zAGuESP+q0D4fwoErN0u2ec6my1vDrEUUAqdPPJSh2gpKUZNrgjDhr6E= X-Google-Smtp-Source: AGHT+IEPUhy2x2CKzAlhBueg0afISka6hHjObfH9uvdx9DrP1CwxmLQDQes8TYH6LQiVLU7WM6Sg X-Received: by 2002:ac8:5710:0:b0:447:ed5a:a249 with SMTP id d75a77b69052e-4518920f7demr41591161cf.5.1722602667096; Fri, 02 Aug 2024 05:44:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1722602667; cv=none; d=google.com; s=arc-20160816; b=zt51f6zGmK19SyMlwM6k9ju0phh+6DdifW3yabXRuLy+zKwY4VHOaZtdzEHdTqbKU1
88c8yCfW8dOBKh00/XYHZLH6lpFQdMRWJGVFTsG3XUcu5TmUDoxq7ftkDUFRzbDKrwUh
QayHgr+LSQCuY6ZjT5KDXGZUl57UZ1itCaS0d6aXrh3FLJMha9K9s7zidSgapskSbpLQ
jrur5EAZ6vJnJ4e2waiSAFhn41HLrdMc34aKFpj7q66/JrqacqUGUK772cmDmfmvAJbA
VRf8UkYD+TpkG7AL6ylG5eblcR2PDjrTr+/b1s1XV87/9ykfIrYEhBth2jlIz/U6hw3Z 4sCg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=sender:errors-to:reply-to:list-subscribe:list-help:list-unsubscribe
:list-id:content-transfer-encoding:precedence:message-id:in-reply-to :to:references:date:subject:mime-version:from:dkim-signature :delivered-to:dkim-signature:delivered-to:dkim-signature; bh=1umBoICUJLIemNWVWXhpH0oAhkCZAr4nnkr/sp21Rfo=; fh=IEwNrSOZJ91Tz1Is7w5Lo+Vx2IucmZv2RM0GpG8iCb0=; b=ZitB9jU1SKfcIpLIgxdbqrH+8SS5tRkOmpt8MclpshQ7lqDgjnPTli9Nyw/HHNk2ll
Klc4tfasWsgxO9l/BtsLbCppvXRq53PDLvry41BhqWpvqLwWQoF4HpFHntLyyyxV3AT0
ZGMxdS98TnR/NipZDrgRSHPq/0ukBXMW1a6Awhk1ItgPxrPQBQh0Axn1YijsnA25Jcd6
A16MRFaMyU+NlipYhNVXHv7HiXuktdyAD9EdgFdg7yBfaO/CWTw2srUz4THsIBcTOOq9
LMJVqALkXD3DPpaMIjhwWMB8U7Hih/N8TtNRfwl98dUqxrn2DNN0ade270D/WeezO9QH SCLw==; dara=google.com ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@leafe.com header.s=mail header.b=S+h1A9Gr; dkim=fail header.i=@leafe.com header.s=mail header.b=YDSLPiYH; dkim=neutral (body hash did not verify) header.i=@leafe.com header.s=mail header.b=T9X23LaP; spf=pass (google.com: domain of profoxtech-bounces@leafe.com designates 209.97.148.170 as permitted sender) smtp.mailfrom= profoxtech-bounces@leafe.com Return-Path: profoxtech-bounces@leafe.com Received: from mail.leafe.com (mail.leafe.com. [209.97.148.170]) by mx.google.com with ESMTPS id d75a77b69052e-4518a79f9aasi22517161cf.613.2024.08.02.05.44.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 02 Aug 2024 05:44:27 -0700 (PDT) Received-SPF: pass (google.com: domain of profoxtech-bounces@leafe.com designates 209.97.148.170 as permitted sender) client-ip=209.97.148.170; Authentication-Results: mx.google.com; dkim=pass header.i=@leafe.com header.s=mail header.b=S+h1A9Gr; dkim=fail header.i=@leafe.com header.s=mail header.b=YDSLPiYH; dkim=neutral (body hash did not verify) header.i=@leafe.com header.s=mail header.b=T9X23LaP; spf=pass (google.com: domain of profoxtech-bounces@leafe.com designates 209.97.148.170 as permitted sender) smtp.mailfrom= profoxtech-bounces@leafe.com Received: from mail.leafe.com (localhost [127.0.0.1]) by mail.leafe.com (Postfix) with ESMTP id 06FAA120A8E; Fri, 2 Aug 2024 07:43:56 -0500 (CDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=leafe.com; s=mail; t=1722602636; bh=FS/DibWHQp37hDnCgHUPoh0wxHlcjPpzsN5zK+5VTMQ=; h=From:Subject:Date:References:To:In-Reply-To:List-Id: List-Unsubscribe:List-Help:List-Subscribe:Reply-To:From; b=S+h1A9GrBaja64yLamK8pxjBhVPBvoUvfjRRzcp9Ac1dhdiGdztccuXyD1+EW3iYx jWa3jqmGoaiMbMrchNe2lfhkgYx6QHCEtQ9BgeqovlySX/Vfg81fYCj/Erdgcqqmq+ e50BS6PYFKicOSouwFcv4ErPxLcX97o66NmKHGPY= X-Original-To: profoxxtproxynn7@leafe.com Delivered-To: profoxxtproxynn7@leafe.com Received: from mail.leafe.com (localhost [127.0.0.1]) by mail.leafe.com (Postfix) with ESMTP id 811B5120535; Fri, 2 Aug 2024 07:43:50 -0500 (CDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=leafe.com; s=mail; t=1722602630; bh=FS/DibWHQp37hDnCgHUPoh0wxHlcjPpzsN5zK+5VTMQ=; h=From:Subject:Date:References:To:In-Reply-To:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Reply-To:From; b=YDSLPiYHYRRhjW9BoiRSkwX90FM9w66oHf7fCNbvZStSqHhRTwNHAJd4AZc/6iuqH lQRMq1Vlm3K1IF82zuNalLSewCUmeazLTsEl7GMtvQjtB2a4YoTRO0oy5+iNiPQxIy Zz5TXI5WnTzWle2+cmljYfw7ij97yF/r0V6fbk7U= X-Original-To: profox@leafe.com Delivered-To: profox@leafe.com Received: from smtpclient.apple ( 108-205-7-108.lightspeed.snantx.sbcglobal.net [108.205.7.108]) by mail.leafe.com (Postfix) with ESMTPSA id 33607120311 for profox@leafe.com; Fri, 2 Aug 2024 07:43:47 -0500 (CDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=leafe.com; s=mail; t=1722602627; bh=5IJez7vn2cx/AcDUIkSCBAoPac+cv3+yto0FPRDPgaU=; h=From:Subject:Date:References:To:In-Reply-To:From; b=T9X23LaPIlLO3abxTNd+qdEfVeRifpcjNDUWVkfV+8j6D0ht+Z9r+DE4p+DVuSkbg uOvBwO54IiFb0gPEkjFTv5iwulnxtxjamQetxoM0oC9Fy7nygQ4zVm8JdtnuzYKCF9 1XFo/mmgGGDJzPQlYvKDlKQTdsgaNLDCEbeOv28Y= From: Ed Leafe ed@leafe.com Mime-Version: 1.0 (Mac OS X Mail 16.0 (3774.600.62)) Subject: Re: [ADMIN] Google blocking ProFox posts to gmail addresses Date: Fri, 2 Aug 2024 07:43:36 -0500 References: B1750ADE-1410-47E2-B637-F260A487DAFB@leafe.com < 51496871-DD87-46DB-8D2D-CF2575551770@leafe.com> <CA+= YCLUmJFNi9WMW_jhNqFmTM4d83tr3n-5bbcVMmMFTf-E_fw@mail.gmail.com> To: profoxtech@leafe.com In-Reply-To: <CA+= YCLUmJFNi9WMW_jhNqFmTM4d83tr3n-5bbcVMmMFTf-E_fw@mail.gmail.com> Message-Id: 397C03DA-33B6-46DF-A3F3-3C72B073B1B2@leafe.com X-Mailer: Apple Mail (2.3774.600.62) X-BeenThere: profox@leafe.com X-Mailman-Version: 2.1.20 Precedence: list X-Spambayes-Classification: ham; 0.00 X-Forwarded-By: OT filtering script Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" X-BeenThere: profoxtech@leafe.com List-Id: OT-free ProFox <profoxtech.leafe.com> List-Unsubscribe: https://mail.leafe.com/mailman/options/profoxtech, mailto:profoxtech-request@leafe.com?subject=unsubscribe List-Help: mailto:profoxtech-request@leafe.com?subject=help List-Subscribe: https://mail.leafe.com/mailman/listinfo/profoxtech, mailto:profoxtech-request@leafe.com?subject=subscribe Reply-To: profox@leafe.com Errors-To: profoxtech-bounces@leafe.com Sender: ProfoxTech profoxtech-bounces@leafe.com
On Fri, Aug 2, 2024 at 8:44 AM Ed Leafe ed@leafe.com wrote:
On Aug 1, 2024, at 20:09, Dave Crozier r.d.crozier@gmail.com wrote:
Received here Ed.
Ack. I see some going through, but others with a message like:
Jul 28 00:08:44 mail postfix/smtp[36630]: 703B01206BF: to=< billand88@gmail.com>, relay=alt1.gmail-smtp-in.l.google.com[209.85.202.27]:25, delay=267185, delays=267153/0.02/31/0.88, dsn=4.7.30, status=deferred (host alt1.gmail-smtp-in.l.google.com[209.85.202.27] said: 421-4.7.30 Your email has been rate limited because DKIM authentication didn't 421-4.7.30 pass for this message. Gmail requires all bulk email senders to 421-4.7.30 authenticate with DKIM. 421-4.7.30 421-4.7.30 Authentication results: 421-4.7.30 DKIM = did not pass 421-4.7.30 To set up DKIM for your sending domains, visit 421-4.7.30 https://support.google.com/a?p=turn-on-dkim 421-4.7.30 To learn more about Gmail requirements for bulk senders, visit 421 4.7.30 https://support.google.com/a?p=sender-guidelines. a640c23a62f3a-a7aca7b84c7si471869166b.34 - gsmtp (in reply to end of DATA command))
I don't know if that means that they are being slowed down or discarded. Either way I need to update the DKIM settings on my server.
-- Ed Leafe
[excessive quoting removed by server]
On Aug 2, 2024, at 07:43, Ed Leafe ed@leafe.com wrote:
I don't know if that means that they are being slowed down or discarded. Either way I need to update the DKIM settings on my server.
Found some errors in the opendkim configuration - fixed them, and it restarted without error. So let's see if that make Google happy.
-- Ed Leafe
Well, the good news is spf still works...
Authentication-Results: mx.google.com; dkim=fail header.i=@leafe.com header.s=mail header.b=Os6SioDN; dkim=fail header.i=@leafe.com header.s=mail header.b=md9xnSO+; dkim=neutral (body hash did not verify) header.i=@leafe.com header.s=mail header.b=F1FmdV5u; spf=pass (google.com: domain of profoxtech-bounces@leafe.com designates 209.97.148.170 as permitted sender)
On Sun, Aug 4, 2024 at 2:48 PM Ed Leafe ed@leafe.com wrote:
On Aug 2, 2024, at 07:43, Ed Leafe ed@leafe.com wrote:
I don't know if that means that they are being slowed down or discarded.
Either way I need to update the DKIM settings on my server.
Found some errors in the opendkim configuration - fixed them, and it restarted without error. So let's see if that make Google happy.
-- Ed Leafe
[excessive quoting removed by server]
On Aug 4, 2024, at 15:16, Ted Roche tedroche@gmail.com wrote:
Authentication-Results: mx.google.com; dkim=fail header.i=@leafe.com header.s=mail header.b=Os6SioDN; dkim=fail header.i=@leafe.com header.s=mail header.b=md9xnSO+; dkim=neutral (body hash did not verify) header.i=@leafe.com
Wonder if I need to switch DKIM to use `leafe.com http://leafe.com/` instead of `mail.leafe.com http://mail.leafe.com/`? I've just done that, so let's see how this message does.
-- Ed Leafe
I'm seeing 'em...
Bill
On Sun, Aug 4, 2024 at 2:03 PM Ed Leafe ed@leafe.com wrote:
On Aug 4, 2024, at 15:16, Ted Roche tedroche@gmail.com wrote:
Authentication-Results: mx.google.com; dkim=fail header.i=@leafe.com header.s=mail header.b=Os6SioDN; dkim=fail header.i=@leafe.com header.s=mail header.b=md9xnSO+; dkim=neutral (body hash did not verify) header.i=@leafe.com
Wonder if I need to switch DKIM to use `leafe.com http://leafe.com/` instead of `mail.leafe.com http://mail.leafe.com/`? I've just done that, so let's see how this message does.
-- Ed Leafe
[excessive quoting removed by server]
Looks about the same:
ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@leafe.com header.s=mail header.b=n1Hgn9+3; dkim=fail header.i=@leafe.com header.s=mail header.b=OPglFyhm; dkim=neutral (body hash did not verify) header.i=@leafe.com header.s=mail header.b=ZqWTtt2G; spf=pass (google.com: domain of profoxtech-bounces@leafe.com designates 209.97.148.170 as permitted sender)
On Sun, Aug 4, 2024 at 4:56 PM Ed Leafe ed@leafe.com wrote:
On Aug 4, 2024, at 15:16, Ted Roche tedroche@gmail.com wrote:
Authentication-Results: mx.google.com; dkim=fail header.i=@leafe.com header.s=mail header.b=Os6SioDN; dkim=fail header.i=@leafe.com header.s=mail header.b=md9xnSO+; dkim=neutral (body hash did not verify) header.i=@leafe.com
Wonder if I need to switch DKIM to use `leafe.com http://leafe.com/` instead of `mail.leafe.com http://mail.leafe.com/`? I've just done that, so let's see how this message does.
-- Ed Leafe
[excessive quoting removed by server]
-
Bill Anderson -
Dave Crozier -
Ed Leafe -
Ted Roche