Re: [OpenStack-Infra] Ask.o.o Email not getting through?
On 01/05/17 23:36, James E. Blair wrote: Tom Fifield writes: Hello infra, Exploratory question here, no idea what's actually going on. We have a prospective new user on Ask OpenStack, who despite trying multiple auth methods (Launchpad & Google) multiple times did not receive a confirmation email. I checked and there have been several new users created within the same day, so it does not seem like a general email problem. May I ask if there is anything revealing in the logs around m...@tiferrei.com ? The MTA reports a DNS failure for that domain. The problem appears to be related to DNSSEC on that domain. It looks like the domain previously had invalid signing keys, but they have been removed. However, DNS resolvers may still have those keys cached. The caching resolver that ask.o.o is using indicates it has a bit over 8 hours remaining. Google's public DNS servers indicate almost 24 hours remaining in their cache. Assuming the user's DNS configuration is and remains correct, the problem should be corrected on ask.o.o within 9 hours, and they should see other DNS related failures abate as they reach the original expiration time of the erroneous DS records. Thank you very much!! ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] Ask.o.o Email not getting through?
Tom Fifield writes: > Hello infra, > > Exploratory question here, no idea what's actually going on. > > We have a prospective new user on Ask OpenStack, who despite trying > multiple auth methods (Launchpad & Google) multiple times did not > receive a confirmation email. > > I checked and there have been several new users created within the > same day, so it does not seem like a general email problem. > > > May I ask if there is anything revealing in the logs around > m...@tiferrei.com ? The MTA reports a DNS failure for that domain. The problem appears to be related to DNSSEC on that domain. It looks like the domain previously had invalid signing keys, but they have been removed. However, DNS resolvers may still have those keys cached. The caching resolver that ask.o.o is using indicates it has a bit over 8 hours remaining. Google's public DNS servers indicate almost 24 hours remaining in their cache. Assuming the user's DNS configuration is and remains correct, the problem should be corrected on ask.o.o within 9 hours, and they should see other DNS related failures abate as they reach the original expiration time of the erroneous DS records. -Jim ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] Ask.o.o Email not getting through?
Hello infra, Exploratory question here, no idea what's actually going on. We have a prospective new user on Ask OpenStack, who despite trying multiple auth methods (Launchpad & Google) multiple times did not receive a confirmation email. I checked and there have been several new users created within the same day, so it does not seem like a general email problem. May I ask if there is anything revealing in the logs around m...@tiferrei.com ? Regards, Tom ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
