Case Forwarding & Sending Email: Configuration and Troubleshooting
Last Updated -
How does Case Forwarding work?
When you forward cases out of Desk.com using the forward feature, the email is sent using the mailbox that is selected as the default mailbox at Admin → Channels → Email → Outbound Mailbox. The email is sent FROM the agent's login email address. You will see this in the email header as the From address.
You cannot select the mailbox that it goes out of, this is always the default mailbox on the site.
For example, Bob works for Desk.com support. If the agent Bob forwards a case, the email uses the email@example.com outbound mailbox, but the FROM address is firstname.lastname@example.org.
The reason for doing this is that when an agent forwards an email, it's usually to a 3rd party – Account manager, Executive, Vendor, IT, etc. In a lot of cases, things are discussed in the conversation that you would want to remain hidden from the customer. So Desk.com set’s the FROM address to be the agent's personal email address instead.
Can I change the FROM address to be my Desk.com site’s email address?
Proceed with caution! You can change it directly in the Case Forward Theme in Admin → Cases → Cases → Forward Themes → Your Theme. However, it is not recommended. If the email was actually replied back to the case, the conversation would be visible to the customer in the portal or the next email interaction that was sent to the customer. If you do this, you run the risk that at some point you may inadvertently display something to their customer that you didn’t want to. For this reason, we highly recommend that you do not do it.
The most common error is permissions related:
550 5.7.1 Client does not have permissions to send as this sender.
This is not Desk.com’s error, but it is from your mail server/host back to Desk.com and is saying that the client (Desk.com with the FROM address of email@example.com) does not have permission to send using that from an address in the firstname.lastname@example.org mailbox.
Here is an example of what you might see in your site's system logs in Admin → Settings → System Logs
Feb 8th, 2017 at 11:33AM - Fatal Error sending email (Case ID: 123456) from SMTP Server Desk.com Support (email@example.com) ."Fatal Error sending email on SMTP Server Desk.com Support(support@desk.=.com). The system will no longer attempt to send this email. (Case ID:123456) (Email Template: System Default) (Source: delayed-be-usw1c-02.internal.desk.com-22912)\r\n\r\nDATA: \r\n\r\n\r\nHEADER: \r\nDate: Wed, 8 Feb 2017 16:33:10 +0000\nFrom: Bob <firstname.lastname@example.org>\nReply-To: email@example.com\nTo: firstname.lastname@example.org\nMessage-Id: <email@example.com>\nSubject: Fwd: How do I forward emails\nMime-Version: 1.0\nContent-Type: multipart/mixed; boundary=mimepart_123456789012345678901234567890\nX-Mailer: Desk.com Support Platform\r\n\r\nDEBUG: \r\n\r\n\r\n"
Notice that the FROM address is firstname.lastname@example.org but it is sending from the email@example.com mailbox. When Desk.com tried to send this email, the mail server said that it did not have the permissions to do so. If your mail server checks the SENDER NAME, this could also be triggered if the name is incorrect. Make sure the name and character casing matches what you have on the server.
How do I correctly configure my permissions on my mail server?
Regardless of your mail server or host, you will need to repeat this for each agent email address that will be forwarding the email on your site.
In Gmail/Google Apps:
In your Gmail/Google account for your default mailbox, you need to allow “Send As” in Settings → Accounts and Import → Send Mail As. It is up to you as to whether you want to use the “Treat as an Alias” setting. Generally speaking, you can leave it on.
In Office 365:
There are three options to choose from. You should consult with your IT team to determine which one is the right setting based on your Office 365 configuration.
-Send on Behalf of
The most common one is Send As, but you might be able to use the other two depending on their Office 365 Policies and settings.
“Send As” will allow you to send emails from the mailbox with your agent email address as the FROM address.
This is the most common setting to use for the forwarding configuration and should work on a default Office 365 setup.
Delegate Access gives the user ownership permissions to the mailbox. And therefore it allows the user's email address to also be the FROM address on the mailbox.
This configuration would be used in a more advanced domain setup in Office 365.
Send on Behalf of is not commonly used. The email would say “Sent From firstname.lastname@example.org on behalf of email@example.com” in the FROM field.
This one is dependent on your security setup in Office 365 and is not recommended/suggested. If you do need help getting this configuration to work, you would need to consult your IT team of Office 365 support.
For Exchange Users, please review this Technet Article:
Additionally, for other mail server types/hosts, you would need to consult with your IT team or mail host for the similar configuration for that server type.
Additional notes about Case Forwarding:
- You cannot run rules on forwarded emails.
- You can edit the case forward theme at Admin → Cases → Cases → Forward Themes to change the look and feel of the theme.
- ALL case attachments are sent with a forwarded email. You cannot pick and choose. keep this in mind as this is important to note because of size/sending limits.
- When you forward a case, the body is added as a note directly in the case.
- The email address that you sent it to is only noted in the case timeline.