Stay on top of everything that's important with Gmail's new interface. Learn more about the new layout.

/mail/community?hl=en
/mail/community?hl=en
1/25/18
Original Poster
Abhishek Malwankar

Mailto URL Scheme cannot handle line breaks in email body (Gmail and Google Inbox)

Hello,

The Mail to URL scheme in the Gmail and Google Inbox apps on iOS does not follow the RFC 2368 protocol. As per the protocol the email body needs to be encoded with ASCII hex 20 for space and %0D%0A for line breaks. I am doing exactly that in the following URL (gmail example) and I am still missing new lines in the email body. The gmail app converts all the new lines just to spaces. I have tried several different ways to include the new line, that includes the whole HTML message content and variety of different ASCII characters but none of them work. The outlook, yahoo and iOS mail app can handle line breaks with a <br> but that does not work on the gmail or google inbox apps either. I will appreciate any help with this issue as this linking is critical for one of the product features that I am working on. I have posted a similar feedback using the gmail app. The url in RFC 2368 format is as below:

"googlegmail:///co?to=abh...@gmail.com&subject=Support%20Needed&body=%0D%0A%0D%0AUser%20Name:%20SomeName%0D%0A%0D%0A%0D%0AServer:%20SomeServer%0D%0A%0D%0A%0D%0AVersion%20Number:%201.2.3%0D%0A%0D%0A%0D%0AExtra%20information%0D%0A"        
Community content may not be verified or up-to-date. Learn more.
All Replies (1)
Rocky - Community Specialist
1/26/18
Rocky - Community Specialist

Hi Abhishek,


Welcome to the Gmail Help Forum.


You can submit feature requests in Gmail by providing us feedback. I'd suggest you please use the feedback option through “Help & feedback” in the iOS Gmail App menu within the app to report this.


As the Gmail team is tracking these reports directly. Sending in-product feedback allows Google to automatically collect some additional account/app/device information that will allow our Engineers to debug each case-by-case issue.


Although you will not receive a reply, they're using this feedback to fix and improve the overall product experience.


Best,

Rocky


Was this reply helpful?
How can we improve it?
 
This question is locked and replying has been disabled. Still have questions? Ask the Help Community.

Badges

Some community members might have badges that indicate their identity or level of participation in a community.

 
Google Employee — Google product team members and community managers
 
Community Specialist — Google partners who help ensure the quality of community content
 
Platinum Product Expert — Community members with advanced product knowledge who help other Google users and Product Experts
 
Gold Product Expert — Community members with in-depth product knowledge who help other Google users by answering questions
 
Silver Product Expert — Community members with intermediate product knowledge who help other Google users by answering questions
 
Product Expert Alumni — Former Product Experts who are no longer members of the program
Community content may not be verified or up-to-date. Learn more.

Levels

Member levels indicate a user's level of participation in a forum. The greater the participation, the higher the level. Everyone starts at level 1 and can rise to level 10. These activities can increase your level in a forum:

  • Post an answer.
  • Having your answer selected as the best answer.
  • Having your post rated as helpful.
  • Vote up a post.
  • Correctly mark a topic or post as abuse.

Having a post marked and removed as abuse will slow a user's advance in levels.

View profile in forum?

To view this member's profile, you need to leave the current Help page.

Report abuse in forum?

This comment originated in the Google Product Forum. To report abuse, you need to leave the current Help page.

Reply in forum?

This comment originated in the Google Product Forum. To reply, you need to leave the current Help page.

false
Search
Clear search
Close search
Google apps
Main menu
Search Help Center
true
17
false