mirror of
https://git.sr.ht/~rjarry/aerc
synced 2025-02-22 14:53:57 +01:00
985ce7a92b
When requesting the bodyStructure email property, the spec says that the default returned body part properties are: ["partId", "blobId", "size", "name", "type", "charset", "disposition", "cid", "language", "location"]. Specifically, the "subParts" property is *NOT* expected by default. Fastmail servers seem to use a different default "bodyProperties" list and implicitly return "subParts" even if not requested. Other JMAP server implementations (e.g. Apache James) do use the RFC default "bodyProperties" and therefore omit returning "subParts" unless explicitly asked to. Change the requested "bodyProperties" to include "subParts" as well. Aerc needs them to display messages. NB: for later, we should probably change our message abstraction not to include any body structure. This makes very little sense to expose that to users. In fact, aerc has code to explicitly prevent users from selecting multipart/* parts. Not requesting that information to the server would make it easier. Link: https://datatracker.ietf.org/doc/html/rfc8621#section-4.2 Reported-by: Benoit Tellier <btellier@linagora.com> Signed-off-by: Robin Jarry <robin@jarry.cc> Reviewed-by: Tim Culverhouse <tim@timculverhouse.com> |
||
|---|---|---|
| .. | ||
| cache | ||
| configure.go | ||
| connect.go | ||
| directories.go | ||
| fetch.go | ||
| jmap.go | ||
| push.go | ||
| search.go | ||
| send.go | ||
| set.go | ||
| threads.go | ||
| worker.go | ||