Re^2: Email delivery problems

Replies are listed 'Best First'.
Re^3: Email delivery problems by afoken (Chancellor) on Dec 28, 2024 at 10:26 UTC
The SPF records for perlmonks.org have been updated yesterday, so in theory Gmail should let that recovery email through again. That implies a short TTL (less than 1 day) on the DNS records for perlmonks.org. Usually, the TTL is longer, and thus changes to DNS records can take longer to propagate through the DNS. Alexander -- Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)	[reply]
Re^4: Email delivery problems (FIXED: DNS propagation completed) by LanX (Saint) on Dec 29, 2024 at 12:54 UTC
> changes to DNS records can take longer to propagate It's propagated now! a DNS check lists the correct MX IP in the SPF record a check with an account with a Gmail address worked (turn around in under a minute!) Cheers Rolf _{(addicted to the Perl Programming Language :) see Wikisyntax for the Monastery}	[reply]
Re^3: Email delivery problems (update x 2) by LanX (Saint) on Dec 27, 2024 at 15:37 UTC
I tried triggering a password reminder on perlmonks.org www.perlmonks.org perlmonks.com with an account with a Gmail address. I tried the same with perlmonks.org š and an account with CPAN.org address (which is more "tolerant" since I was able to register there a week ago) Not sure if there are any hidden limitations on emails per day, but so far I haven't received any emails. I'll update this node if they finally arrive with delay. Cheers Rolf _{(addicted to the Perl Programming Language :) see Wikisyntax for the Monastery} PS: since this already took me a nerve wracking hour, I triggered this thread: Password email round-trip monitoring PPS: see also Re^2: Problems getting e-mails from Perlmonks updates š) this @cpan.org request arrived `Fri, 27 Dec 2024 15:13:32 +0000` at cpan.org and the forward arrived `08:32:31 -0800 (PST)` at gmail, emphasize added. Received: from vps918.pairvps.com (vps918.pairvps.com `[216.92.237.59]` ) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384) by 100.108.111.106 (trex/6.10.3); Fri, 27 Dec 2024 15:13:32 +0000 Authentication-Results: inbound.mailchannels.net; spf=softfail smtp.mailfrom=noreply@perlmonks.org; dkim=none; dmarc=none; arc=none Received-SPF: softfail (dmarc-service-597c997457-j54gz: transitioning perlmonks.org does not designate 216.92.237.59 as permitted sender) client-ip=216.92.237.59; envelope-from=noreply@perlmonks.org; helo=vps918.pairvps.com; Received: by vps918.pairvps.com (Postfix, from userid 65534) id F0EA41A0E8B; Fri, 27 Dec 2024 10:13:28 -0500 (EST) I did SPF lookups for `(www.\|)perlmonks.(org\|com\|net)` at various sites (like https://kitterman.com/spf/validate.html ) and there still seems to be a problem, maybe related to caching? v=spf1 a mx ip4:216.92.34.251 ip4:66.39.54.27 ~all	[reply] [d/l] [select]
Re^3: Email delivery problems by LanX (Saint) on Dec 30, 2024 at 16:05 UTC
> There should be no delivery problems for perlmonks.com or perlmonks.net as these had correct SPF records all the time. I'm a bit puzzled. My tests show identical emails from all domains, with the same sender noreplyŠperlmonks.org From my understanding is the SPF check dependent on the FROM: and the corresponding DNS entry whitelisting the IP of the delivering mail exchange host. Hence entries for .com or .net shouldn't/didn't matter, (as long as they are not used in the FROM.) Please correct me if I'm wrong. Cheers Rolf _{(addicted to the Perl Programming Language :) see Wikisyntax for the Monastery}	[reply]
Re^4: Email delivery problems by Corion (Patriarch) on Dec 30, 2024 at 18:44 UTC
Yeah, now that you ask it this way, I understand it. This is correct - we had the SPF record missing for the only domain that matters, `perlmonks.org`.	[reply] [d/l]
Re^5: Email delivery problems by dda (Friar) on Jan 15, 2025 at 05:43 UTC
Thank you, Corion and LanX. This is fixed now, and I was able to recover my original account. --dda	[reply]

updates