Getting symbol ! in mail body

Hi,

I created a WFT. Through external task, Caalling an ipl file to send mail to users. Mail sending correctly only, But symbol ! is displaying in mail body.
I did not gave that symbol any where, Still its coming in mail body.

Ex:
mail body Smiley Tongue

lease refer to the attached link for Issues (This message i am setting as mail body in ipl file)

Result: Please refer to the attache link fo!r Issues (i am not understanding how this symbol is coming in between).

Please can any one give solution for this issue.

Thanks in advance

Find more posts tagged with

Comments

Adam Stoller

Here's a guess from past recollections.
Your IPL script is generating HTML formatted email without inserting many / any newlines in the HTML code.

Try making sure that each end-element in the HTML output is followed by a newline, and see if the exclamation marks (!) go away.

jagadesh

Hi,

I created a WFT. Through external task, Caalling an ipl file to send mail to users. Mail sending correctly only, But symbol ! is displaying in mail body.
I did not gave that symbol any where, Still its coming in mail body.

Ex:
mail bodylease refer to the attached link for Issues (This message i am setting as mail body in ipl file)

Result: Please refer to the attache link fo!r Issues (i am not understanding how this symbol is coming in between).

Please can any one give solution for this issue.

Thanks in advance

Mailservers have a 990-character limit on each line contained within an email message. If an email message is sent that contains lines longer than 990-characters, those lines will be subdivided by additional line ending characters(!), which can cause corruption in the email message, particularly for HTML content. To prevent this you have to add your own line-ending characters at appropriate locations within the email message to ensure that no lines are longer than 990 characters.

srilu

Hi Ghoti/Jagadeesh,

Thank you very much for your suggestion. I put new line character as you suggested, The issue is fixed now.

Thanks a lot.