AWS SES Advisor can't verify BIMI
Hi,
I have set a record for BIMI in my domain, and can verify it using BIMI Group's own inspector: https://bimigroup.org/bimi-generator. I already have a working DMARC config, so that also is not the problem.
Even though Advisor checks every hour, cannot verify BIMI and the messages says : BIMI record not found or configured without default selector.
Any ideas how to resolve this?
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
So the docs say you need only one MX and it's for mail.yourdomain.com, since I used mail for MAIL FROM subdomain it was the only one I had.
And BIMI wants to see it on main domain, not any subdomains. Ignoring the rule above, I added the same MAIL FROM DNS Records to both main domain and MAIL FROM subdomain, then BIMI started working.
In summary, I have 4 records in DNS Records for this to work;
TXT | name: mail.mydomain.com | value: "v=spf1 include:amazonses.com ~all"
MX | name: mail.mydomain.com | value: feedback-smtp.my-region.amazonses.com
TXT | name: mydomain.com | value: "v=spf1 include:amazonses.com ~all"
MX | name: mydomain.com | value: feedback-smtp.my-region.amazonses.com
Hi,
As per documentation,
Enabling your emails to display a BIMI logo requires some prerequisites to be in place within SES
—in the following procedure, these prerequisites are generalized and will reference dedicated sections
that cover these topics in detail. The steps specific to BIMI and what is necessary to configure it in SES
will be detailed here.
So, please, follow exactly the following guidance to successfully implement BIMI for SES: https://docs.aws.amazon.com/ses/latest/dg/send-email-authentication-bimi.html
Best,
Didier
The SPF record is not needed on the From header domain.
TXT | name: mydomain.com | value: "v=spf1 include:amazonses.com ~all"
This is the wrong record value. Please read the documentation for setting up SES for receiving inbound mail.
MX | name: mydomain.com | value: feedback-smtp.my-region.amazonses.com
Contenuto pertinente
AWS UFFICIALEAggiornata 3 anni fa- AWS UFFICIALEAggiornata un anno fa
Hi Didier, thank you for your reply.
I am aware of the documentation and been through it multiple times. All the details and fields in my domain configs are there and can verify that they are correct by BIMI's own validator, there audit result is all green. However the error still persists in Advisor.
I really have been through every step, diligently, however nothing has changed. Can not find out what is missing or wrong at this point.