email@address.com?subject=sub&body=bodytext

where sub and body are URL encoded strings. The URL encoding means, for example, you change spaces to %20 and newlines to %0A%0D, among others.

The problem with SharePoint is that if you paste the escaped string into the HTML view of a content editor web part, SharePoint, in all it’s wisdom, Converts the escaped strings back into normal text, which means all the newlines (and multiple spaces) are stripped.

This makes it seemingly impossible to create a mailto link with newlines.

Here’s the solution:

The solution is to use JavaScript instead, and paste the lines unescaped into the script. Then make a basic mailto: link as before, but give it an id (in this case, the id is mailtolink). Then the mailto link is overwritted with our desired link, complete with newlines, when the page loads.

<p>Please <a href="mailto:address@example.com" id="mailtolink">contact us</a>.</p>


<script type="text/javascript">
// <![CDATA[

var msgRec = 'address@example.com';
var msgSub = 'This is the message subject';
var msgBody = 'This is the full e-mail body\n\nThis is a new line\nAnd another line';

function modifyMailtoLink;
	document.getElementById('mailtolink').href = 'mailto:' + encodeURIComponent(msgRec) + '?subject=' + msgSub + '&body=' + encodeURIComponent(msgBody);
};

_spBodyOnLoadFunctionNames.push('modifyMailtoLink');

// ]]>
</script>

Getting something from inside one folder is easy — you just set the queryOptions parameter to be <QueryOptions><Folder>folderName</Folder></QueryOptions>.

This works and returns items fron within that folder. But what about subfolders?

One would expect it to be simple — but it is not, replacing folderName with folderName\subFolder does not work — it still returns items from within folderName.

The solution is simple but non-obvious. For sub-folders, you have to include the name of the list as the first path element — so the query becomes <QueryOptions><Folder>listName\folderName\subFolder</Folder></QueryOptions>

This doesn’t seem to be covered in any documentation, and is non-obvious, inconsistent behaviour. It resulted in a lot of wasted time for me. Unsurprising really for the over-complex, proprietary, non-standard mess that is SharePoint.