Customer Issue P3
Status Update
Comments
mi...@biepa.online <mi...@biepa.online> #2
Automated by Blunderbuss job honestdns_tickets_blunderbuss_autoassigner for 2nd config honestdns_defects_customer_issues for component 191657.
mi...@biepa.online <mi...@biepa.online> #3
Hello,
We are reviewing your request and need to verify it is from the organization which owns this address block. I have reached out to the owner of the address block,
Alternatively, if you can reply or send me an email from
Thanks!
mi...@biepa.online <mi...@biepa.online> #4
Hello
We have already answered the email with the mail j.medrano@libertycr.com
Thank you for contacting us.
Let's continue the process from the other email account.
Regards
We have already answered the email with the mail j.medrano@libertycr.com
Thank you for contacting us.
Let's continue the process from the other email account.
Regards
pu...@google.com <pu...@google.com> #5
Yes, I heard back from
We've moved forward with this request and the changes (increasing client QPS to 5,000) will roll out next week.
Description
I have a domain biepa.online managed by Wix and used for our Google Workspace. Incoming emails are mostly working fine for users in that domain, but one person reported an error (attached) when sending from their
According to the Wix instructions the DNS records appear to be updated everywhere.
How do I fix this error?
From: postmaster@outlook.com <postmaster@outlook.com>
Sent: Monday, 4 July 2022 1:07 pm
To: mike@beipa.online <mike@beipa.online>
Subject: Undeliverable: Re: Thank you to Madeleine and Kay for $6,000 donation
Delivery has failed to these recipients or groups:
mike@beipa.online (mike@beipa.online)
Your message couldn't be delivered. The Domain Name System (DNS) reported that the recipient's domain does not exist.
Contact the recipient by some other means (by phone, for example) and ask them to tell their email admin that it appears that their domain isn't properly registered at their domain registrar. Give them the error details shown below. It's likely that the recipient's email admin is the only one who can fix this problem.
For more information and tips to fix this issue see this article: