Re: maildrop feature request
Sam Varshavchik <[email protected]> Thu, 17 Dec 2015 07:05:09 -0500
| Newsgroups | gmane.mail.maildrop |
|---|---|
| Message-ID | <[email protected]> |
Philippe Cerfon writes: > Don't understand what you mean. > > E.g. (F)lagging a message may simply be desired, regardless of which folder. > Denoting that an answer has already been written, as e.g. in the > example above, cannot be done by moving mail to specific folder. It's > simply what the A flag is for. > And as for the last example, even when you move it to some folder, the > mail would still show up as unseen in the user's MUA, which is just > what's not desired in the above example. If your maildrop recipe chooses to handle a particular message, in some way – say send an autoreply, or set it aside for some special handling – all that needs to happen is to deliver the message to the appropriate folder; say a folder called "Replied", or "To Do". And now, instead of having one flat Inbox, that you have to search for, to find all of your flagged or replied messages, all of them are easily found in a separate folder. They'll certainly be seen as unread in their dedicated folder, but so what? If you want to find all of the autoreplied messages, you open the "Replied" folder, and there they are. If you want to find all of the flagged messages, you open the "To Do" folder. Mission accomplished. > > Cheers, > Philippe > > On Tue, Dec 15, 2015 at 2:20 AM, Sam Varshavchik <[email protected]> > wrote: > > Philippe Cerfon writes: > > > >> On Mon, Dec 14, 2015 at 1:00 PM, Sam Varshavchik <[email protected]> > >> wrote: > >> >> Have there been any news over the years on this front? I.e. the > >> >> problem on how to flag mail's as (S)een, (A)nswered, (D)eleted, etc. ? > >> >> That seems to pop up every now and then again here, there are probably > >> >> countless of blog entries where people complain about that issue :-( > >> > Haven't seen that topic come up in a number of years, actually. I still > >> > think that this is a solution in search of a problem. > >> There's for example, "[maildropl] Marking a message read when > >> delivering to a Maildir" right here on the list, from e.g. 2014 > >> > >> And as I've said, countless of blog posts, etc. which deal with that > >> issue. > >> > >> Also I don't know how you come to idea that this should be the search > >> of a problem. > >> Setting these flags seem to be one of the most basic featurs, > >> supported by sieve, or any MUA's internal filtersystem. > >> And it makes perfectly countless of use cases: > >> - e.g. automatically (f)lagging messages, based on e.g. From > >> - when maildrop is e.g. used to automatically reply to certain mails > >> (via passing them on to some scripts or so), may be desired to have > >> them marked (A)nswered > >> - when having high volume mailing lists subscribed, one may want to > >> mark most messages (S)een since one isn't interested in them, except > >> those which are e.g. directly To:ed to one self, or which include > >> certain keywords, etc. pp > > > > > > Why would delivering messages to the appopriate folder, instead, be a > > problem? > > > > Simply delivering the messages to the appropriate folder seems to be a more > > useful disposition. > > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > > Courier-maildrop mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/courier-maildrop > > ------------------------------------------------------------------------------ _______________________________________________ Courier-maildrop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/courier-maildrop
signature.asc
(application/pgp-signature, 819 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAABAgAGBQJWcqT1AAoJEGs6Yr4nnb8ly74P/i0NqCdUkaa6jfZMABw09klW O9Osk9cIh9I1ocUbxaxhl037iZhDxCFNBqSPzllHR5GvvlQ1MWYJd9+uccSPuvlo z+V8EYq/fY/K0KrMsbptCxvt4TlLzDltj6OiEJZ0+a+Mh8jt7TAgT2Ja8RNT66SP EP5ivQ1CSzlQNaSsvFWb3PRQ/EqJheeCBOKGuGvk4GiCi9ASb+eQf1pT9FBpb8+P 9aYpdr9svPP+AgejCGLq2/OFJEV8vzyt1stUcruWCYIHYc8I67ktfpI1yU71cSRb tevUYoCxJ5QYrBpoT/5rMsf0ObHHjpNTaCzw9Jq8A9iSK5TJ1gJQdwX1k3/QTc3s ZppSorT5s3Z+DZrTfHSbWE+jH2CX1yBH3jnhCaTW2FRnLfccJbgSVAXDD3vACP+u JbkTVuNiNAXFCUhCUibq6WPNUjUAb6Mk8ljLoGD85zXnJFLpI+bTi2RpforNatxu cn8DE4uFk8ZOg8D6CAo47P/kuP5xzfw/+XaMAHqpZOMHRWk/YGDQdnWnYB8y6VPD kgEY7ffI9KQfEaLkTQfNDn9CU3zXYM1/NFC+i96BMjy/TLcWksLgaD22Af2Ghd60 HsbQzpdyM2udIt7yOz1GbJ4cUXCH6GD3t5/NJJ2MOD9Mkj0lpkDLzN02+D8gcnym DEeSb4qO/DV1ZpFFIQSS =DS1a -----END PGP SIGNATURE-----