function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
SurpriseSurprise 

Email to salsforce error

Hi All,

 

While Sending an email to the salesforce.We got the following error.Does anybody has any idea what could cause the below given error.

 

This message was created automatically by the mail system.

A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:

>>> emailtosalesforce@jdm6g0a8jnln9wgahzdjsbwj.8dea8eae.c.le.salesforce.
>>> com (Undelivered): 551 Failed due to: SenderAuthorization

 

 

Sonam_SFDCSonam_SFDC

Hi,

 

Could you please provide the email header of the mail you sent to the Email to Salesforce address.

 

It must be appended to the bouce back message you recieved..should be after the lines:

 

This message was created automatically by the mail system.

A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:

>>> emailtosalesforce@jdm6g0a8jnln9wgahzdjsbwj.8dea8eae.c.le.salesforce.
>>> com (Undelivered): 551 Failed due to: SenderAuthorization

 

Past the header here or private message me - anything is fine.

Deepak Kumar ShyoranDeepak Kumar Shyoran

Hi,

 

Please check the Accept email criteria for you email service. It might be possible that your email service have some limited by using accept email from selected email Address and your email address is not listed in that. If that is the problem then add your email address from which you are sending email to salesforce separating using a comma.

 

If this post helps you then hit kudus by clicking on star and accept my post as a solution to your question.

JasonGonzalesJasonGonzales

Hi Sonam,

 

Same thing is happening on our end. We recently acquired a new company so not familiar with their email server. Read about it online and it appears that it has something to do with SPF (not really sure though if it's us or SF). Anyway, here's the complete header from the bounce back message the sender received:

 

Return-Path: <JeffreySherry@deltek.com>

X-SFDC-Original-RCPT: emailtosalesforce@b-424rf1eh0mto5yhuhrucezj8a.8c8kgeaq.c.le.salesforce.com

X-SFDC-Binding: coremailprocessor

X-SFDC-DOMAINKEYS: None

X-SFDC-TLS-VERIFIED: no

X-SFDC-TLS-CIPHER: None

X-SFDC-TLS-STATUS: false

X-SFDC-SENDERID-PRA: None

X-SFDC-SENDERID: None

X-SFDC-SPF: None

X-SFDC-Interface: external

Received: from [64.18.3.96] ([64.18.3.96:58338] helo=exprod8og108.obsmtp.com)

                by mx2-sjl.mta.salesforce.com (envelope-from <JeffreySherry@deltek.com>)

                (ecelerity 2.2.2.45 r()) with ESMTP

                id 19/7F-20418-F3BAB725; Thu, 07 Nov 2013 15:01:21 +0000

Received: from ASHEXP01.ads.deltek.com ([199.188.134.47]) by exprod8ob108.postini.com ([64.18.7.12]) with SMTP

                ID DSNKUnurP6zPPeoYp0pff+frZ1xOiB499LYa@postini.com; Thu, 07 Nov 2013 07:01:20 PST

Received: from ASHEXP03.ads.deltek.com ([10.2.4.3]) by ASHEXP01.ads.deltek.com

 ([10.2.20.11]) with mapi id 14.03.0123.003; Thu, 7 Nov 2013 10:01:19 -0500

From: Jeff Sherry <JeffreySherry@deltek.com>

To: "wgross@nurturhealth.com" <wgross@nurturhealth.com>

Subject: WMG | Deltek - Consultant Agreement

Thread-Topic: WMG | Deltek - Consultant Agreement

Thread-Index: Ac7byjJt8Zuf8BJ9Qf6fKG0poTg0XQ==

Disposition-Notification-To: Jeff Sherry <JeffreySherry@deltek.com>

Return-Receipt-To: <JeffreySherry@deltek.com>

Date: Thu, 7 Nov 2013 15:01:18 +0000

Message-ID: <77E899F594D4B54BAA9A311A11F2CD4C205F7718@ASHEXP03.ads.deltek.com>

Accept-Language: en-US

Content-Language: en-US

X-MS-Has-Attach: yes

X-MS-TNEF-Correlator:

x-sfdc-client: Outlook 2.0.2.1065

x-originating-ip: [10.5.150.100]

Content-Type: multipart/mixed;

                boundary="_011_77E899F594D4B54BAA9A311A11F2CD4C205F7718ASHEXP03adsdelt_"

MIME-Version: 1.0

 

--_011_77E899F594D4B54BAA9A311A11F2CD4C205F7718ASHEXP03adsdelt_

Content-Type: multipart/related;

                boundary="_010_77E899F594D4B54BAA9A311A11F2CD4C205F7718ASHEXP03adsdelt_";

                type="multipart/alternative"

 

--_010_77E899F594D4B54BAA9A311A11F2CD4C205F7718ASHEXP03adsdelt_

Content-Type: multipart/alternative;

                boundary="_000_77E899F594D4B54BAA9A311A11F2CD4C205F7718ASHEXP03adsdelt_"

 

--_000_77E899F594D4B54BAA9A311A11F2CD4C205F7718ASHEXP03adsdelt_

Content-Type: text/plain; charset="us-ascii"

Content-Transfer-Encoding: quoted-printable

 

 

Let me know if you find something.

 

 

Thanks!

Jason

JasonGonzalesJasonGonzales
Also found out that this was a known issue addressed with a patch back in Summer '13. On that posted issue, it says something about the PRSV in the envelope-from. In the header I posted, the email is not posted in its PRSV format.
AdelchiAdelchi

Same error here, same header, where is the PRSV envelope-from?

 

>>> emailtosalesforce@1j3c5f15xarvkooj20ekeubgmh37jhikjn7ngm6j7485ajp08z.d-n3zimay.eu1.le.salesforce.com(Undelivered): 551 Failed due to: SenderAuthorization

------ This is a copy of the original message, including all headers. ------

Return-Path: <streamsalesforce+caf_=emailtosalesforce=1j3c5f15xarvkooj20ekeubgmh37jhikjn7ngm6j7485ajp08z.d-n3zimay.eu1.le.salesforce.com@gmail.com>
X-SFDC-Original-RCPT: emailtosalesforce@1j3c5f15xarvkooj20ekeubgmh37jhikjn7ngm6j7485ajp08z.d-n3zimay.eu1.le.salesforce.com
X-SFDC-Binding: coremailprocessor
Authentication-Results:  mx1-sjl.mta.salesforce.com x-tls.subject="/C=US/ST=California/L=Mountain View/O=Google Inc/CN=smtp.gmail.com"; auth=pass (cipher=RC4-SHA)
X-SFDC-DOMAINKEYS: None
X-SFDC-TLS-VERIFIED: yes
X-SFDC-TLS-CIPHER: RC4-SHA
X-SFDC-TLS-STATUS: true
X-SFDC-SENDERID-PRA: None
X-SFDC-SENDERID: Pass
X-SFDC-SPF: Pass
X-SFDC-Interface: external
Received: from [209.85.214.179] ([209.85.214.179:57741] helo=mail-ob0-f179.google.com)
        by mx1-sjl.mta.salesforce.com (envelope-from <streamsalesforce+caf_=emailtosalesforce=1j3c5f15xarvkooj20ekeubgmh37jhikjn7ngm6j7485ajp08z.d-n3zimay.eu1.le.salesforce.com@gmail.com>)
        (ecelerity 2.2.2.45 r()) with ESMTPS (cipher=RC4-SHA
        subject="/C=US/ST=California/L=Mountain View/O=Google Inc/CN=smtp.gmail.com")
        id 53/74-00977-A76FCA25; Sun, 15 Dec 2013 00:23:22 +0000
Received: by mail-ob0-f179.google.com with SMTP id wm4so3426173obc.38
        for <emailtosalesforce@1j3c5f15xarvkooj20ekeubgmh37jhikjn7ngm6j7485ajp08z.d-n3zimay.eu1.le.salesforce.com>; Sat, 14 Dec 2013 16:23:21 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-original-authentication-results:delivered-to:message-id
         :content-type:from:to:subject:date:importance:mime-version;
        bh=tNUqGZiPfbZdjSLmAG9qQttWwBjfH4Iq89ZfS+rbR9o=;
        b=mv13rOA0IgiNqDa54dE/S3F4Xwz942V+PDFcuaIJpq5kutmSkYOACDi2X6tzPWbiRG
         JGDv+ummmrCuQCUodznLZnrjdOxZHGwyFaJ5iJo5ZlhRySV0STqVr8Q7nRuOTdo1n6HI
         SJJovMk0Jq2VNb0JPwXq9Q44XKCbvnazWs7rKbfQE329GbGg6Yo91XcnsERhNGqAsZyD
         EKNb6wih0Ahogw7lgRu5INylISfPG729Bc1lU4S13ikE9OL3iZRBHm6Xc47ITRWdlaA5
         qgdJI0LU4h3dSTe7ik1ixu/E2ntxGRiwAPclGx85pw7sbeBd7mgFmfrE8Z6O82w1a3Q3
         NUvA==
X-Original-Authentication-Results: mx.google.com;       spf=pass (google.com: domain of adpeliz@hotmail.comdesignates 157.55.2.86 as permitted sender) smtp.mail=adpeliz@hotmail.com
X-Received: by 10.60.174.167 with SMTP id bt7mr1718301oec.54.1387067001543;
        Sat, 14 Dec 2013 16:23:21 -0800 (PST)
X-Forwarded-To: emailtosalesforce@1j3c5f15xarvkooj20ekeubgmh37jhikjn7ngm6j7485ajp08z.d-n3zimay.eu1.le.salesforce.com
X-Forwarded-For: streamsalesforce@gmail.com emailtosalesforce@1j3c5f15xarvkooj20ekeubgmh37jhikjn7ngm6j7485ajp08z.d-n3zimay.eu1.le.salesforce.com
Delivered-To: streamsalesforce@gmail.com
Received: by 10.182.49.66 with SMTP id s2csp48034obn;
        Sat, 14 Dec 2013 16:23:21 -0800 (PST)
X-Received: by 10.194.243.170 with SMTP id wz10mr1149818wjc.74.1387067000576;
        Sat, 14 Dec 2013 16:23:20 -0800 (PST)
Received: from dub0-omc4-s11.dub0.hotmail.com (dub0-omc4-s11.dub0.hotmail.com. [157.55.2.86])
        by mx.google.com with ESMTP id dv4si1599771wib.59.2013.12.14.16.23.20
        for <streamsalesforce@gmail.com>;
        Sat, 14 Dec 2013 16:23:20 -0800 (PST)
Received-SPF: pass (google.com: domain of adpeliz@hotmail.com designates 157.55.2.86 as permitted sender) client-ip=157.55.2.86;
Authentication-Results: mx.google.com;
       spf=pass (google.com: domain of adpeliz@hotmail.com designates 157.55.2.86 as permitted sender) smtp.mail=adpeliz@hotmail.com
Received: from DUB126-W29 ([157.55.2.71]) by dub0-omc4-s11.dub0.hotmail.com with Microsoft SMTPSVC(6.0.3790.4675);
         Sat, 14 Dec 2013 16:23:19 -0800
X-TMN: [idQHCKTNvtydEra3k7EztSEVj8UqzZ7A]
X-Originating-Email: [adpeliz@hotmail.com]
Message-ID: <DUB126-W294075C348DB65ECCD392BA0D90@phx.gbl>
Content-Type: multipart/alternative;
        boundary="_2251d6f0-fb8c-43db-aec2-5014abdda303_"
From: Adelchi Pelizzo <adpeliz@hotmail.com>
To: "streamsalesforce@gmail.com" <streamsalesforce@gmail.com>
Subject: fghfdgh
Date: Sun, 15 Dec 2013 01:23:19 +0100
Importance: Normal
MIME-Version: 1.0
X-OriginalArrivalTime: 15 Dec 2013 00:23:19.0541 (UTC) FILETIME=[DB1E0250:01CEF92B]

--_2251d6f0-fb8c-43db-aec2-5014abdda303_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

fghfdghdfg                                        =

--_2251d6f0-fb8c-43db-aec2-5014abdda303_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<style><!--
.hmmessage P
{
margin:0px=3B
padding:0px
}
body.hmmessage
{
font-size: 12pt=3B
font-family:Calibri
}
--></style></head>
<body class="3D"'hmmessage'><div dir=3D'ltr'>fghfdghdfg                                     </div></bo=
dy>
</html>=

--_2251d6f0-fb8c-43db-aec2-5014abdda303_--

lukas.wallisch1.3903815994810598E12lukas.wallisch1.3903815994810598E12
Hi,

same problem here. Does anyone has a solution yet? I'm not able to find a prvs envelope-from either...
Siddharth MadhavSiddharth Madhav
Solution Senario1:
- Ask the affected user to Login to Salesforce > on your Click on "Name" (top right side) Select "My Settings".
- On the left side panel select Emails > My Emails to Salesforce > under My Acceptable Email Addresses you need to add the email addresses to allow emails through Salesforce.
Accepting emails communication from Salesforce.

Senario 2: Raise request for Email logs for the affected user and check Emails Logs for RCA,
- "Requesting an Email Log": https://help.salesforce.com/apex/HTViewHelpDoc?id=email_logs_edit.htm&language=en_US
- "Viewing Email Logs": https://help.salesforce.com/apex/HTViewHelpDoc?id=email_logs_format.htm&language=th
- "What Are Email Logs?" https://help.salesforce.com/apex/HTViewHelpDoc?id=email_logs.htm&language=th

Senario 3:
- Whitelist Salesforce IP's.
https://help.salesforce.com/apex/HTViewSolution?urlname=What-are-the-Salesforce-IP-Addresses-to-whitelist&language=en_US
- Sender Policy Frame work for whitelisting Salesforce.
https://help.salesforce.com/apex/HTViewSolution?urlname=Sender-Policy-Framework-SPF-Salesforce-com-SPF-Record-1327365203011&language=en_US

Senario 4:
- Configuring Deliverability Settings: https://help.salesforce.com/apex/HTViewHelpDoc?id=emailadmin_deliverability.htm&language=en_US

Senario 5:
- Setting Up Email Relaying: https://help.salesforce.com/apex/HTViewHelpDoc?id=email_relay.htm&language=en_US

Log a case with Salesforce support team.. hope this helps :(