Búsquedas recientes
No hay búsquedas recientes

henrik
Incorporación 15 abr 2021
·
Última actividad 05 nov 2024
Seguimientos
0
Seguidores
0
Actividad total
8
Votos
3
Suscripciones
2
RESUMEN DE LA ACTIVIDAD
INSIGNIAS
ARTÍCULOS
PUBLICACIONES
COMENTARIOS DE LA COMUNIDAD
COMENTARIOS DE ARTÍCULOS
RESUMEN DE LA ACTIVIDAD
Última actividad de henrik
henrik creó una publicación,
Hi
It would be great if it were possible to configure a BIMI selector for outgoing email.
It would require adding a custom SMTP header to all outgoing email.
Here is an example:
From: support@example.org
BIMI-Selector: v=BIMI1; s=customersupport
Ref:
https://bimigroup.org/
https://bimigroup.org/how-and-why-to-implement-bimi-selectors/
Publicado 03 nov 2024 · henrik
2
Seguidores
1
Voto
1
Comentario
henrik hizo un comentario,
Years ago, Zendesk customers were asked to create a collection of new hostnames as preparation for migrating to Amazon SES I think.
zendesk1.
zendesk2.
zendesk3.
zendesk4.
What happened to those migration plans? Can we delete those records again ?
Ver comentario · Editado 04 ene 2023 · henrik
0
Seguidores
0
Votos
0
Comentarios
henrik hizo un comentario,
You should update this part of the documentation:
Having multiple SPF records will invalidate the SPF configuration for the domain. The part from Zendesk MUST be merged with the existing SPF record.
If you've already set up an SPF record for another purpose, you can simply add a reference to Zendesk to it. The SPF specification requires that you only have one SPF record on your domain. If you have multiple records, it may cause issues, and cause rejections of your email.
For example, instead of having two separate records, such as
v=spf1 include:_spf.google.com ~all
andv=spf1 include:mail.zendesk.com ~all
, you can combine them into one, like this:
Ver comentario · Publicado 04 ene 2023 · henrik
0
Seguidores
1
Voto
0
Comentarios