- osmAsked on March 30, 2015 at 01:38 PM
In my form's notification email, I have the "Sender Name" set to "JotForm". Yet, when my notification email is actually sent, garbage characters appear in the email "From" header (also see screenshot):
From: =?UTF-8?B?S29ucmFk?= <firstname.lastname@example.org>
• This error does still occur if I switch the "Sender Name" to the value from a field on the form.
• The email is sent via Gmail SMTP.
- JotForm SupportWelvinAnswered on March 30, 2015 at 03:09 PM
We have this issue in the past, but the reason is random. One is caused by the sender name being empty, one is caused by the email client character encoding settings. This one could be different so please try the above suggestion.
Also, try to re-create the whole settings. Delete the current notifier: http://www.jotform.com/help/132-How-to-Delete-Notifications-Autoresponder then re-create http://www.jotform.com/help/25-Setting-Up-Email-Notifications.
I hope this helps.
- osmAnswered on April 02, 2015 at 11:51 AMThanks for your reply.
I followed your two suggestions and (1) changed the Sender Email to JotForm (email@example.com) and (2) deleted the entire Notifier and re-created from scratch.
Unfortunately, neither of these two workarounds fixed the issue. The "From:" email header is still being sent by JotForm with errors (see screenshot below).
Lastly, if this is a character encoding issue, I'm not sure I'd be able to address that in my notifier wizard, as it does not give me any access to the actual raw email headers sent by JotForm during its SMTP transaction.
Sir, can you please ensure your "From:" headers are RFC 2822 compliant and see if that fixes the issue?
- JotForm SupportdavidAnswered on April 02, 2015 at 01:46 PM
I believe if the message was no compliant you would receive an error message stating as such. Something to this nature:
Other than using a custom SMTP such as Mandril:
Unfortunately I do not believe there is anything we can offer on our end to allow more control over how your notifications are sent. The default notification send from our services should be able to encoded properly by all major services.
- osmAnswered on April 02, 2015 at 04:29 PM
If you look at my screenshot, I did use your defaults for the notification sent in my example, just as Welvin suggested as a workaround, for both the Sender Name ("JotForm") and Sender Email ("firstname.lastname@example.org").
But still, in your sending of that notification email, you sent the following header, over which I have no control:
From: =?UTF-8?B?S29ucmFk?= <email@example.com>
- JotForm SupportdavidAnswered on April 02, 2015 at 05:41 PM
Though I am unable to replicate this on my end, I will forward this to our development team to see if they may be able to give you any further information as to why this is occurring. We will update you here as soon as we have any further information.
- osmAnswered on May 12, 2015 at 01:54 PM
Hi JotForm, it looks like your email sending program is still sending garbage characters in the "From:" field when sending form notifications via SMTP:
- BenAnswered on May 12, 2015 at 03:18 PM
The above seems to be correct by me. All it tells me is that your server did not bother to translate that part. The above says "Konrad".
I would actually not see this as a bug of jotform since that is not something that we can do.
Do you see that by some chance in the subject shown to everyone - not just in the source of your email?
- osmAnswered on June 11, 2015 at 01:02 PM
Ben, your answer makes perfect sense to me, thank you. Somebody reported the encoded text was visible in the email program they were using (without revealing source), which is what prompted me to report the "issue" here. But I personally have only seen the decoded text in my own email programs. Sorry to bug you.
- JotForm SupportdavidAnswered on June 11, 2015 at 02:07 PM
No worries at all, thank you for confirming this. I will go ahead and cancel this ticket. If the problem does ever pop up on your end, just let us know and we will be happy to open the ticket for you again.