Recent searches
No recent searches

henrik
Joined Apr 15, 2021
·
Last activity Nov 05, 2024
Following
0
Followers
0
Total activity
8
Votes
3
Subscriptions
2
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by henrik
henrik created a post,
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/
Posted Nov 03, 2024 · henrik
2
Followers
1
Vote
1
Comment
henrik commented,
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 ?
View comment · Edited Jan 04, 2023 · henrik
0
Followers
0
Votes
0
Comments
henrik commented,
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:
View comment · Posted Jan 04, 2023 · henrik
0
Followers
1
Vote
0
Comments