> and lastly cname breaks dnssec,
Err, what?
CNAME works fine with DNSSEC. CNAME at zone apex with other RR types can break
DNSSEC since CNAME with other RRs at the same label (anywhere) isn’t supposed
to work. However, since people want to do it, some folks have come up with
solutions that
On 2024-02-29, Stefano Bagnara via mailop wrote:
> Today an italian mailvox provider started refusing our emails with this
> message
>> 550 5.1.0 sender rejected:
> domain does not have neither a valid MX or A record
>
> The "e.#customerdomain" is a CNAME record that points to app.mailvox.it and
On Thu, 29 Feb 2024 at 12:09, Benny Pedersen via mailop
wrote:
> > I think I wrote here too early: from further investigation seems like
> > the issue has gone and now those emails are not refused anymore.
>
> https://totaluptime.com/kb/cname-and-mx-for-the-same-host-name/
>
> dont use cname for
Stefano Bagnara via mailop skrev den 2024-02-29 11:09:
I think I wrote here too early: from further investigation seems like
the issue has gone and now those emails are not refused anymore.
https://totaluptime.com/kb/cname-and-mx-for-the-same-host-name/
dont use cname for email or even mx
Well,
I think I wrote here too early: from further investigation seems like the
issue has gone and now those emails are not refused anymore.
According to the logs the issue lasted around 5 hours from 28/02/2024 07:00
CET to 28/02/2024 11:40 CET.
I had no answer from their postmaster, so I don't
Hi,
we are an ESP (a very small italian alternative to Mailchimp).
Today an italian mailvox provider started refusing our emails with this
message
> 550 5.1.0 sender rejected:
domain does not have neither a valid MX or A record
The "e.#customerdomain" is a CNAME record that points to
