Re: Fetching short text snippet for mails

Jamie Nicolson (倪志明) <[email protected]>
Newsgroups gmane.ietf.imapext
Message-ID <CACU8CfRNffYRZo7rpeM_KpBabg_rhV3=mDqk1cSKB166xDDWqg@mail.gmail.com>
Just weighing in from Gmail. We have snippets generated by our proprietary
algorithm, the ones we show in the web UI. We could implement proposal a),
returning our snippet as a new FETCH attribute, with the understanding that
snippet content is unspecified and determined by the server. We're not
likely to implement ANNOTATE or CONVERT.

On Mon, Dec 1, 2014 at 10:39 PM, Timo Sirainen <[email protected]> wrote:
>
> Nowadays many mail clients want to show about 100 chars of the beginning
> of mail, so there should be a nice and efficient way for clients to request
> this. I'm now wondering what would be a nice IMAP way of implementing this.
> Does anyone have some suggestions? There's what I've come up with so far:
>
> a) FETCH n (SNIPPET)
>  - Would require writing a new RFC (or just use X-SNIPPET for internal use)
>
> b) FETCH n (ANNOTATION (/vendor/vendor.dovecot.snippet))
>  - Would require implementing ANNOTATE, which is a lot of work. But it
> could also be implemented just minimally for this specific command.
>  - Standardizing vendor.dovecot.snippet would probably require new RFC
>
> c) CONVERT n ("text/vnd.dovecot.snippet" ("length" "100")) BINARY[BODY]
>  - Would require implementing CONVERT, which is a lot of work. But it
> could also be implemented just minimally for this specific command.
>  - Standardizing vnd.dovecot.snippet would probably require new RFC
>
> d) CONVERT n ("text/plain") BINARY[BODY]<0.100>
>  - CONVERT RFC says it's legal to convert entire multiparts, but doesn't
> say exactly what should be done with them. This is probably a valid use
> case though.
>  - Downside to this compared to others is that this always fetches the
> first 100 chars, while the others could also be smarter and skip over
> quoted text and such.
>
> I think I'm leaning towards b)
>
> _______________________________________________
> imapext mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/imapext
>

_______________________________________________
imapext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/imapext
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.