Quantcast
Channel: ImapX 2
Viewing all articles
Browse latest Browse all 1952

Commented Unassigned: Body.Text doesn't decode links correctly [1873]

$
0
0
Given this email:
```
Welcome to the Fedarated Identity Repository using the The Internal Ducot Service service.

Click this link, https://ducot.netdocuments.com/neWeb2/docCent.aspx?whr=CA%2DH3GSM67W, to access your The Internal Ducot Service account. After you login, use your browser's Favorites option to save this link for future access.

You can use this account to securely access, share and collaborate on documents. For instructions on using the service, please consult the online Help documentation after you have logged in.
```
Gets decoded by Body.Text to this
```
Welcome to the Fedarated Identity Repository using the The Internal Ducot Service service.Click this link, https://ducot.netdocuments.com/neWeb2/docCent.aspx?whr?%2DH3GSM67W, to access your The Internal Ducot Service account. After you login,use your browser's Favorites option to save this link for futureaccess.You can use this account to securely access, share and collaborate on documents. For instructions on using the service, please consult the online Help documentation after youhave logged in.
```

Notice the spaces that are lost and part of the link becomes "whr?%" instead of "whr=CA%".
Comments: ** Comment from web user: pavel_azanov **

Hi Phasze,

happy to hear the links get decoded well!

To your note about the new line characters - in a plain text body it's not possible to restore the original line breaks due to some limitation of the Internet Message Format.

Outlook tries to restore line breaks by analysing the text, however it also has problems. (e.g try to send a long text, more than 78 characters, without spaces and line breaks, and you'll see that outlook will break it when displaying)


Viewing all articles
Browse latest Browse all 1952

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>