This was caused by a temporary issue reaching the DNS servers. Let me pass
this along to see if it can be turned into a temporary (4xy) error.
On Tue, Feb 27, 2024 at 9:56 PM Marco Moock via mailop
wrote:
> Am Tue, 27 Feb 2024 16:54:31 -0600
> schrieb Jarland Donnell via mailop :
>
> > Is it
Am Tue, 27 Feb 2024 16:54:31 -0600
schrieb Jarland Donnell via mailop :
> Is it plausible that Google had a temporary issue reaching your DNS
> servers?
If so they should give an error message that says that.
___
mailop mailing list
mailop@mailop.org
On Tue, Feb 27, 2024, Matt Palmer via mailop wrote:
> > 550-5.7.26 DKIM = did not pass 550-5.7.26 SPF [nagler.me] with ip:
> Any chance of a transient/intermittent DNS failure on nagler.me? On
That should not result in a permanent (550) error but
just cause a temporary (4xy) error.
--
Thanks everybody!
It's odd. Some messages are getting through. It's just this particular
domain and MTA. Other domains and other mail servers are not having any
issues sending to gmail..com.
Intermittent DNS failures are always a possibility. We have a 3rd party
DNS/HTTP/SMTP monitor, which
On 2024-02-27 15:01, Tim C via mailop wrote:
On 28/2/24 09:30, Rob Nagler via mailop wrote:
a mx ip4:139.177.203.52
You could try removing the redundant A/MX as they all point to
139.177.203.52.
___
mailop mailing list
mailop@mailop.org
On Tue, Feb 27, 2024 at 03:30:03PM -0700, Rob Nagler via mailop wrote:
> gmail.com started failing messages from domains which are correctly setup
> for SPF (and have been for some years):
>
> 550-5.7.26 Gmail requires all senders to authenticate with
> either SPF or DKIM. 550-5.7.26
On 28/2/24 09:30, Rob Nagler via mailop wrote:
a mx ip4:139.177.203.52
You could try removing the redundant A/MX as they all point to
139.177.203.52.
___
mailop mailing list
mailop@mailop.org
https://list.mailop.org/listinfo/mailop
Oh sry after rereading yeah looks like you’re impacted by gmail guidelines
(dmarc required)
On Tue, Feb 27, 2024 at 6:04 PM Opti Pub wrote:
> I’m seeing some (inaccurate) 0% logging on the 26th across some domains.
> I’ve also seen a bunch of others reporting the same so that maybe what
>
I’m seeing some (inaccurate) 0% logging on the 26th across some domains.
I’ve also seen a bunch of others reporting the same so that maybe what
you’re experiencing.
On Tue, Feb 27, 2024 at 6:02 PM L. Mark Stone via mailop
wrote:
> I believe you need a DMARC record...
>
> Regards,
> Mark
>
Is it plausible that Google had a temporary issue reaching your DNS
servers?
On 2024-02-27 16:30, Rob Nagler via mailop wrote:
gmail.com [1] started failing messages from domains which are
correctly setup for SPF (and have been for some years):
550-5.7.26 Gmail requires all senders to
I believe you need a DMARC record...
Regards,
Mark
_
L. Mark Stone, Founder
North America's Leading Zimbra VAR/BSP/Training Partner
For Companies With Mission-Critical Email Needs
- Original Message -
From: "Rob Nagler
gmail.com started failing messages from domains which are correctly setup
for SPF (and have been for some years):
550-5.7.26 Gmail requires all senders to authenticate with
either SPF or DKIM. 550-5.7.26 550-5.7.26 Authentication results:
550-5.7.26 DKIM = did not pass 550-5.7.26 SPF
It appears that Support 3Hound via mailop said:
>About the hostedmail.com domain, I searched a bit before ask here.
>The owner/registrant is redacted for privacy.
>No web redirect.
>No TXT records.
>Abuse info was ab...@hostedmail.com ( on abuse.net )
>The registrar is Tucows (as thousand of
The issue has been solved.
I'm not sure if someone read my first e-mail and silently operates to
verify/solve without reply (google style) or if it's a natural update
over a false positive or even if the recipient comply with them as a
customer.
I would like just to puntualize I'm not sure I
14 matches
Mail list logo
