EXM headers adding bounce@spe.sitecoremail.com as the sender The Next CEO of Stack OverflowSitecore User Group April 2019 Meetup - Queen City, Manchester, NHEXM: Adding “List-Unsubscribe” header to emailsHow to configure the “message transfer agent” for EXM 3.4What is the difference between “clicked”, “browse”, and “productive” in the EXM report?EXM 3.4 - Subscription PageEXM issue with unsubscribeSend email with Segmented List - Skipped during message deliveryCustomizing the EXM subscription confirmation templateHow does Sitecore EXM track the Email Opens Rate?exm error pauses the sending of lettersGetting the email from a form in Sitecore EXM
Does the Idaho Potato Commission associate potato skins with healthy eating?
Prodigo = pro + ago?
Is it possible to create a QR code using text?
Could a dragon use its wings to swim?
Would a grinding machine be a simple and workable propulsion system for an interplanetary spacecraft?
My boss doesn't want me to have a side project
Cannot restore registry to default in Windows 10?
Find the majority element, which appears more than half the time
Do I need to write [sic] when including a quotation with a number less than 10 that isn't written out?
Is it reasonable to ask other researchers to send me their previous grant applications?
Why can't we say "I have been having a dog"?
Incomplete cube
How does a dynamic QR code work?
Compensation for working overtime on Saturdays
How do I secure a TV wall mount?
Why did early computer designers eschew integers?
Creating a script with console commands
Is it correct to say moon starry nights?
Can a PhD from a non-TU9 German university become a professor in a TU9 university?
Free fall ellipse or parabola?
Arrows in tikz Markov chain diagram overlap
Oldie but Goldie
Does int main() need a declaration on C++?
How can the PCs determine if an item is a phylactery?
EXM headers adding bounce@spe.sitecoremail.com as the sender
The Next CEO of Stack OverflowSitecore User Group April 2019 Meetup - Queen City, Manchester, NHEXM: Adding “List-Unsubscribe” header to emailsHow to configure the “message transfer agent” for EXM 3.4What is the difference between “clicked”, “browse”, and “productive” in the EXM report?EXM 3.4 - Subscription PageEXM issue with unsubscribeSend email with Segmented List - Skipped during message deliveryCustomizing the EXM subscription confirmation templateHow does Sitecore EXM track the Email Opens Rate?exm error pauses the sending of lettersGetting the email from a form in Sitecore EXM
As a precaution, our distribution groups have a limited number of email addresses that they will accept messages from. In anticipation of the EXM usage, the email used (e.g. SitecoreExm@domain.com) was added as a permited sender to the distribution group.
The assumption was the sending system would mark the email as coming from SitecoreExm@domain.com, however, these emails had bounce@spe.sitecoremail.com inserted into the headers. Since that was not the expected address, the email failed to reach the target audience.
Here is part of the header generated
Received: from emailserver.com (xxx.xxx.xxx.xxx) by
emailserver.com (xxx.xxx.xxx.xxx) with SMTP Server id
Fri, 8 Mar 2019 09:07:53 -0300
Received-SPF: Pass (emailserver.com: domain of
bounce@spe.sitecoremail.com designates xxx.xxx.xxx.xxx as
permitted sender) identity=mailfrom; client-ip=xxx.xxx.xxx.xxx;
receiver=emailserver.com;
envelope-from="bounce@spe.sitecoremail.com";
x-sender="bounce@spe.sitecoremail.com"**;
x-conformance=spf_only; x-record-type="v=spf1";
**x-record-text="v=spf1 exists:%i._spf.e.sparkpost.com
a:sitecore.mail.e.sparkpost.com ~all"**
exm
add a comment |
As a precaution, our distribution groups have a limited number of email addresses that they will accept messages from. In anticipation of the EXM usage, the email used (e.g. SitecoreExm@domain.com) was added as a permited sender to the distribution group.
The assumption was the sending system would mark the email as coming from SitecoreExm@domain.com, however, these emails had bounce@spe.sitecoremail.com inserted into the headers. Since that was not the expected address, the email failed to reach the target audience.
Here is part of the header generated
Received: from emailserver.com (xxx.xxx.xxx.xxx) by
emailserver.com (xxx.xxx.xxx.xxx) with SMTP Server id
Fri, 8 Mar 2019 09:07:53 -0300
Received-SPF: Pass (emailserver.com: domain of
bounce@spe.sitecoremail.com designates xxx.xxx.xxx.xxx as
permitted sender) identity=mailfrom; client-ip=xxx.xxx.xxx.xxx;
receiver=emailserver.com;
envelope-from="bounce@spe.sitecoremail.com";
x-sender="bounce@spe.sitecoremail.com"**;
x-conformance=spf_only; x-record-type="v=spf1";
**x-record-text="v=spf1 exists:%i._spf.e.sparkpost.com
a:sitecore.mail.e.sparkpost.com ~all"**
exm
are you using Sitecore Email Service Provider?
– Vlad Iobagiu
Mar 8 at 17:34
We are using Sitecore Email Cloud
– Vinicius Deschamps
Mar 8 at 18:23
add a comment |
As a precaution, our distribution groups have a limited number of email addresses that they will accept messages from. In anticipation of the EXM usage, the email used (e.g. SitecoreExm@domain.com) was added as a permited sender to the distribution group.
The assumption was the sending system would mark the email as coming from SitecoreExm@domain.com, however, these emails had bounce@spe.sitecoremail.com inserted into the headers. Since that was not the expected address, the email failed to reach the target audience.
Here is part of the header generated
Received: from emailserver.com (xxx.xxx.xxx.xxx) by
emailserver.com (xxx.xxx.xxx.xxx) with SMTP Server id
Fri, 8 Mar 2019 09:07:53 -0300
Received-SPF: Pass (emailserver.com: domain of
bounce@spe.sitecoremail.com designates xxx.xxx.xxx.xxx as
permitted sender) identity=mailfrom; client-ip=xxx.xxx.xxx.xxx;
receiver=emailserver.com;
envelope-from="bounce@spe.sitecoremail.com";
x-sender="bounce@spe.sitecoremail.com"**;
x-conformance=spf_only; x-record-type="v=spf1";
**x-record-text="v=spf1 exists:%i._spf.e.sparkpost.com
a:sitecore.mail.e.sparkpost.com ~all"**
exm
As a precaution, our distribution groups have a limited number of email addresses that they will accept messages from. In anticipation of the EXM usage, the email used (e.g. SitecoreExm@domain.com) was added as a permited sender to the distribution group.
The assumption was the sending system would mark the email as coming from SitecoreExm@domain.com, however, these emails had bounce@spe.sitecoremail.com inserted into the headers. Since that was not the expected address, the email failed to reach the target audience.
Here is part of the header generated
Received: from emailserver.com (xxx.xxx.xxx.xxx) by
emailserver.com (xxx.xxx.xxx.xxx) with SMTP Server id
Fri, 8 Mar 2019 09:07:53 -0300
Received-SPF: Pass (emailserver.com: domain of
bounce@spe.sitecoremail.com designates xxx.xxx.xxx.xxx as
permitted sender) identity=mailfrom; client-ip=xxx.xxx.xxx.xxx;
receiver=emailserver.com;
envelope-from="bounce@spe.sitecoremail.com";
x-sender="bounce@spe.sitecoremail.com"**;
x-conformance=spf_only; x-record-type="v=spf1";
**x-record-text="v=spf1 exists:%i._spf.e.sparkpost.com
a:sitecore.mail.e.sparkpost.com ~all"**
exm
exm
asked Mar 8 at 17:16
Vinicius DeschampsVinicius Deschamps
1,695423
1,695423
are you using Sitecore Email Service Provider?
– Vlad Iobagiu
Mar 8 at 17:34
We are using Sitecore Email Cloud
– Vinicius Deschamps
Mar 8 at 18:23
add a comment |
are you using Sitecore Email Service Provider?
– Vlad Iobagiu
Mar 8 at 17:34
We are using Sitecore Email Cloud
– Vinicius Deschamps
Mar 8 at 18:23
are you using Sitecore Email Service Provider?
– Vlad Iobagiu
Mar 8 at 17:34
are you using Sitecore Email Service Provider?
– Vlad Iobagiu
Mar 8 at 17:34
We are using Sitecore Email Cloud
– Vinicius Deschamps
Mar 8 at 18:23
We are using Sitecore Email Cloud
– Vinicius Deschamps
Mar 8 at 18:23
add a comment |
1 Answer
1
active
oldest
votes
This is by design when using Sitecore's Email Cloud Delivery Service through Sparkpost.
How Bounces (aka Delivery Status Notifications) Work in EXM
Email Cloud Delivery Service
The bounce@spe.sitecoremail.com
email address is used as the X-Sender
header so that Sparkpost knows where to email Bounces and Spam Complaints to. How that process works, is that when an email bounces, Sparkpost will forward the email, along with additional headers to the bounce@spe.sitecoremail.com
email address.
This is a POP3 account that Sitecore manages. When Email Experience Manager is configured to use EmailCloud
as the eds:define
variable in the web.config, this activates an Agent that runs every so often, which connects to the POP3 account and retrieves all messages from the server that were sent from the EXM Manager Root.
From there, Sitecore processes the email from the POP3 and adds analytical information for Bounces and Spam Complaints. This is not a process that you can adjust.
Advice and Summary
My advice is that if you are looking at the X-Sender
header for emails going through, you'll want to adjust your whitelisted email addresses and add that email to your list.
Custom SMTP Configuration
Bounces work differently in a Custom SMTP configuration. Out of the Box, Bounces are not handled without some setup and configuration. You'll need to bring your own POP3 mailbox and email address and config bounce by patching the Sitecore.EDS.Providers.CustomSmtp.Sync.config
configuration.
Additionally, there are fields in the Email Manager Root for configuring the POP3 as shown in the image below.
add a comment |
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "664"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f17333%2fexm-headers-adding-bouncespe-sitecoremail-com-as-the-sender%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
This is by design when using Sitecore's Email Cloud Delivery Service through Sparkpost.
How Bounces (aka Delivery Status Notifications) Work in EXM
Email Cloud Delivery Service
The bounce@spe.sitecoremail.com
email address is used as the X-Sender
header so that Sparkpost knows where to email Bounces and Spam Complaints to. How that process works, is that when an email bounces, Sparkpost will forward the email, along with additional headers to the bounce@spe.sitecoremail.com
email address.
This is a POP3 account that Sitecore manages. When Email Experience Manager is configured to use EmailCloud
as the eds:define
variable in the web.config, this activates an Agent that runs every so often, which connects to the POP3 account and retrieves all messages from the server that were sent from the EXM Manager Root.
From there, Sitecore processes the email from the POP3 and adds analytical information for Bounces and Spam Complaints. This is not a process that you can adjust.
Advice and Summary
My advice is that if you are looking at the X-Sender
header for emails going through, you'll want to adjust your whitelisted email addresses and add that email to your list.
Custom SMTP Configuration
Bounces work differently in a Custom SMTP configuration. Out of the Box, Bounces are not handled without some setup and configuration. You'll need to bring your own POP3 mailbox and email address and config bounce by patching the Sitecore.EDS.Providers.CustomSmtp.Sync.config
configuration.
Additionally, there are fields in the Email Manager Root for configuring the POP3 as shown in the image below.
add a comment |
This is by design when using Sitecore's Email Cloud Delivery Service through Sparkpost.
How Bounces (aka Delivery Status Notifications) Work in EXM
Email Cloud Delivery Service
The bounce@spe.sitecoremail.com
email address is used as the X-Sender
header so that Sparkpost knows where to email Bounces and Spam Complaints to. How that process works, is that when an email bounces, Sparkpost will forward the email, along with additional headers to the bounce@spe.sitecoremail.com
email address.
This is a POP3 account that Sitecore manages. When Email Experience Manager is configured to use EmailCloud
as the eds:define
variable in the web.config, this activates an Agent that runs every so often, which connects to the POP3 account and retrieves all messages from the server that were sent from the EXM Manager Root.
From there, Sitecore processes the email from the POP3 and adds analytical information for Bounces and Spam Complaints. This is not a process that you can adjust.
Advice and Summary
My advice is that if you are looking at the X-Sender
header for emails going through, you'll want to adjust your whitelisted email addresses and add that email to your list.
Custom SMTP Configuration
Bounces work differently in a Custom SMTP configuration. Out of the Box, Bounces are not handled without some setup and configuration. You'll need to bring your own POP3 mailbox and email address and config bounce by patching the Sitecore.EDS.Providers.CustomSmtp.Sync.config
configuration.
Additionally, there are fields in the Email Manager Root for configuring the POP3 as shown in the image below.
add a comment |
This is by design when using Sitecore's Email Cloud Delivery Service through Sparkpost.
How Bounces (aka Delivery Status Notifications) Work in EXM
Email Cloud Delivery Service
The bounce@spe.sitecoremail.com
email address is used as the X-Sender
header so that Sparkpost knows where to email Bounces and Spam Complaints to. How that process works, is that when an email bounces, Sparkpost will forward the email, along with additional headers to the bounce@spe.sitecoremail.com
email address.
This is a POP3 account that Sitecore manages. When Email Experience Manager is configured to use EmailCloud
as the eds:define
variable in the web.config, this activates an Agent that runs every so often, which connects to the POP3 account and retrieves all messages from the server that were sent from the EXM Manager Root.
From there, Sitecore processes the email from the POP3 and adds analytical information for Bounces and Spam Complaints. This is not a process that you can adjust.
Advice and Summary
My advice is that if you are looking at the X-Sender
header for emails going through, you'll want to adjust your whitelisted email addresses and add that email to your list.
Custom SMTP Configuration
Bounces work differently in a Custom SMTP configuration. Out of the Box, Bounces are not handled without some setup and configuration. You'll need to bring your own POP3 mailbox and email address and config bounce by patching the Sitecore.EDS.Providers.CustomSmtp.Sync.config
configuration.
Additionally, there are fields in the Email Manager Root for configuring the POP3 as shown in the image below.
This is by design when using Sitecore's Email Cloud Delivery Service through Sparkpost.
How Bounces (aka Delivery Status Notifications) Work in EXM
Email Cloud Delivery Service
The bounce@spe.sitecoremail.com
email address is used as the X-Sender
header so that Sparkpost knows where to email Bounces and Spam Complaints to. How that process works, is that when an email bounces, Sparkpost will forward the email, along with additional headers to the bounce@spe.sitecoremail.com
email address.
This is a POP3 account that Sitecore manages. When Email Experience Manager is configured to use EmailCloud
as the eds:define
variable in the web.config, this activates an Agent that runs every so often, which connects to the POP3 account and retrieves all messages from the server that were sent from the EXM Manager Root.
From there, Sitecore processes the email from the POP3 and adds analytical information for Bounces and Spam Complaints. This is not a process that you can adjust.
Advice and Summary
My advice is that if you are looking at the X-Sender
header for emails going through, you'll want to adjust your whitelisted email addresses and add that email to your list.
Custom SMTP Configuration
Bounces work differently in a Custom SMTP configuration. Out of the Box, Bounces are not handled without some setup and configuration. You'll need to bring your own POP3 mailbox and email address and config bounce by patching the Sitecore.EDS.Providers.CustomSmtp.Sync.config
configuration.
Additionally, there are fields in the Email Manager Root for configuring the POP3 as shown in the image below.
edited Mar 8 at 18:36
answered Mar 8 at 18:26
Pete NavarraPete Navarra
11.3k2675
11.3k2675
add a comment |
add a comment |
Thanks for contributing an answer to Sitecore Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsitecore.stackexchange.com%2fquestions%2f17333%2fexm-headers-adding-bouncespe-sitecoremail-com-as-the-sender%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
are you using Sitecore Email Service Provider?
– Vlad Iobagiu
Mar 8 at 17:34
We are using Sitecore Email Cloud
– Vinicius Deschamps
Mar 8 at 18:23