Pesquisas recentes
Sem pesquisas recentes

henrik
Entrou em 15 de abr. de 2021
·
Última atividade em 05 de nov. de 2024
Seguindo
0
Seguidores
0
Atividade total
8
Votos
3
Assinaturas
2
VISÃO GERAL DA ATIVIDADE
MEDALHAS
ARTIGOS
PUBLICAÇÕES
COMENTÁRIOS NA COMUNIDADE
COMENTÁRIOS EM ARTIGOS
VISÃO GERAL DA ATIVIDADE
Atividade mais recente por henrik
henrik criou uma publicação,
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 de nov. de 2024 · henrik
2
Seguidores
1
Votos
1
Comentário
henrik comentou,
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 ?
Exibir comentário · Editado 04 de jan. de 2023 · henrik
0
Seguidores
0
Votos
0
Comentários
henrik comentou,
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:
Exibir comentário · Publicado 04 de jan. de 2023 · henrik
0
Seguidores
1
Votos
0
Comentários