Re: Three kinds of IMAP extensions
"Adrien de Croy" <[email protected]> Mon, 19 Oct 2015 21:23:28 +0000
| Newsgroups | gmane.ietf.imapext |
|---|---|
| Message-ID | <emc3c62000-f95d-4c1e-acb9-a8850406592d@bodybag> |
------ Original Message ------ From: "Stu Brandt" <[email protected]> >For client dev, I'd think the simplest is to look for "APPENDLIMIT=" >capability and steer users away from trying to do operations that would >require appending oversized messages -- "Your draft/note is too large >to save" or "Sorry, that message is too large to copy from AccountA to >AccountB. AccountB only accepts messages less than <appendlimit> >bytes." I think the UX for this needs to be thought through a bit more. I'm pretty sure if I had just been working on a huge email with attachments etc, and at the time I tried to save it it told me it was too big, I'd be pretty unhappy about it. Substitute "your draft/note is too large to save" with "your provider sucks, get a new one". Is the problem with me, or is the problem with the person that set the (IMO) too-small limit? And what are they really trying to achieve? Keep my disk-usage down? I could save a million tiny messages but not one big one? It doesn't make much sense to me to limit this. Adrien > >Perhaps I'm oversimplifying, though :) > >> >>Arnt >> >>_______________________________________________ >>imapext mailing list >>[email protected] >>https://www.ietf.org/mailman/listinfo/imapext > >_______________________________________________ >imapext mailing list >[email protected] >https://www.ietf.org/mailman/listinfo/imapext _______________________________________________ imapext mailing list [email protected] https://www.ietf.org/mailman/listinfo/imapext