Incorrect sender display name in Email action - using Gmail (experimental) connector

Hello,

I’m sending e-mail using the Gmail (experimental) connector and I can’t get the Sender name to show the name of the Google Account (in the inbox of the recipient, it’s only showing as sender the part of the e-mail before the @).

For example, I have the Gmail account “Phil Hill”, with the following e-mail: phil@gmail.com. I’m sending e-mails from here through EasyMorph.

The name of the Google account is “Phil Hill”, and when I send an e-mail directly from Gmail (not EasyMorph), the recipient sees the senders whole name, which is correct:

image

However, when sending the e-mail through EasyMorph, this information is not kept, and I just see the e-mail address of the sender. And if I go to my inbox e-mail list, in the list of my e-mails, in the senders column I only see “phil” (the part of the e-mail before @), not “Phil Hill”.

Is there another way to connect to a Gmail account to be able to include the sender’s name correctly?

Thanks,

Roberto

Hello Roberto,

The “Phil Hill” in your example is a display name part of an email address. By default, Gmail adds your Google Account name as a display name of your email address in all the emails you send from the Gmail web interface.

EasyMorph doesn’t support display names in email addresses and doesn’t try to deduce display names from the specified email addresses. So it seems that it’s Gmail’s behavior to show the local (first part) of an email address as a display name when the actual display name is not specified in a message.

Unfortunately, it seems that there is no workaround for this issue.

Hello Andrew,

Ok thanks, understood. I sent a test e-mail to an Outlook account and in this case I see the whole e-mail address, not only the local, so as you said it depends on the email provider behavior.

Regarding display names, is this something that EasyMorph could support in the future? It would give more familiarity and trust to the recipient when receiving emails from EasyMorph.

Thanks,

Roberto

Hello Roberto,

We will do some research on display names. We may add support for display names as a hotfix for the current version.

1 Like

Hello Roberto,

Display names in email addresses are supported by EasyMorph starting from version 5.0.

In order to send an email from an address with a display name, you have to switch the “Sender’s email” setting to the “Other” option and specify an email address as follows: "Some name" <some.name@domain.com>.

image

1 Like

Hello @andrew.rybka,

I have tried this with the “Gmail” connector (there is the same option as in the “Email Server” connector) but it is not working, I keep seeing only the email address as the sender.

Thanks,

Roberto

Hello Roberto,

What version of EasyMorph you are using?

Hello,

I am using EasyMorph 5.1.1.1

Thanks,

Roberto

Roberto, it seems that we have to make some changes to make it work with the Gmail connector.

We’ll keep you posted.

Hi Roberto,

we’ve updated EasyMorph and fixed the problem. Get the updated version from our website.

1 Like

Hello,

I’ve been doing some tests and for the same email connector, sometimes I’m receiving the email with the correct sender display name, and sometimes I am not. I have several tasks sending emails and I have identified which task has displayed it wrong today and which one has displayed correctly - however, the task that is displaying it wrong today, displayed it correctly in emails sent yesterday, so I don’t know what could be going on.

What change in a task could influence the fact that the Sender display name is showing correctly or not?

Regards,

Roberto

Basically, it's Gmail who decides whether you have the right to impersonate specified sender or not. If Gmail decides that requested sender name is not valid or you have no right to claim it (for example, it is some other person's email entirely) it silently replaces sender with your 'default' sender email

I see. Then Gmail doesn’t seem to have taken a final decision, because it’s moving me back and forth!

What could influence Gmail’s decision?

Assuming the email itself matches logged in user email and sender name conforms to RFC822 you should be able to consistently set it, but we really can’t speak for Google here. I was not able to find any definite information from Google regarding this issue.

Ok, thanks for your help!