modern-email / defects

Collection of real-world email defects

MIT License

7 stars 1 forks source link

FETCH RFC822 response lacks RFC822 information in icloud IMAP server #36

Open epilys opened 3 months ago

epilys commented 3 months ago

Server replies successfully, but the untagged FETCH line lacks RFC822 part. A workaround is to fetch BODY[] instead.

Found in the wild: snapshot at archive.org | original

existing MUA workarounds

meli fixed in v0.8.7 https://github.com/meli/meli/commit/197132cca0901aac4c3204fd2f7691baf02b6edf https://git.meli-email.org/meli/meli/commit/197132cca0901aac4c3204fd2f7691baf02b6edf

duesee commented 2 months ago

I tried to find something quotable but gave up. NO - fetch error: can't fetch that data indicates it's an error. But I feel we could miss something... Best bet is that it's an error, though.

epilys commented 2 months ago

What do you mean by "something quotable"?

duesee commented 2 months ago

I'm scared by IMAP and not sure if responding with less data items than requested could still be valid.

Maybe the "NO" response is reserved for the case when no data items at all could be constructed but the server knows they exist.

I hoped to find a sentence in the RFC like "a server MUST respond with all data items that were requested" but there is no clear answer so far.

I know this is a stretch but I don't trust IMAP :P

epilys commented 2 months ago

There was no "NO" response actually according the user, but a successful one. It must be a bug