{"thread":{"id":"56529","subject":"Test der CC","startedAt":"2021-09-18T12:23:12Z","lastAt":"2021-09-18T12:23:12Z","messageCount":1,"participants":["test.bentolor@xoxy.net"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"436302","messageId":"01d71649-456a-a4ff-e34d-3340bdc4ff42@gmx.net","threadId":"56529","inReplyTo":null,"subject":"Test der CC","fromName":"","fromEmail":"test.bentolor@xoxy.net","sentAt":"2021-09-18T12:23:07Z","receivedAt":"2021-09-18T12:23:12Z","isPatch":false,"sender":{"key":"test.bentolor@xoxy.net","avatar":null},"body":"\n\n    They can include slash / for hierarchical (directory) grouping, but\nno slash-separated component can begin with a dot . or end with the\nsequence .lock.\n\n    They must contain at least one /. This enforces the presence of a\ncategory like heads/, tags/ etc. but the actual names are not\nrestricted. If the --allow-onelevel option is used, this rule is waived.\n\n    They cannot have two consecutive dots .. anywhere.\n\n    They cannot have ASCII control characters (i.e. bytes whose values\nare lower than \\040, or \\177 DEL), space, tilde ~, caret ^, or colon :\nanywhere.\n\n    They cannot have question-mark ?, asterisk *, or open bracket [\nanywhere. See the --refspec-pattern option below for an exception to\nthis rule.\n\n    They cannot begin or end with a slash / or contain multiple\nconsecutive slashes (see the --normalize option below for an exception\nto this rule)\n\n    They cannot end with a dot ..\n\n    They cannot contain a sequence @{.\n\n    They cannot be the single character @.\n\n    They cannot contain a \\.\n\n\n"}]}