Re: [exim] Mark messages as read

Top Page
Delete this message
Reply to this message
Author: Michael Haardt
Date:  
To: exim-users
Subject: Re: [exim] Mark messages as read
> > I wouldn't like to see code in Exim for half-baken attempts like "deliver
> > to cur instead of new", because that is just a fraction of a real solution
> > to this problem.
>
> Wouldn't the marking of a message as Read, then, be better implemented
> at the filter command level? Perhaps another parameter to the save
> command, or a new command (so as not to break old filters).


Put simple, filters can only use what transports offer. Sure, if
transports could process message flags, filters could easily use
them.

> Or something like that, leaving the mechanism open to future expansion
> for flags other than Read (savemark RXYZ... $foo). Since the 'save'
> command already understands if it's delivering to Maildir, mbox, etc it
> could add the appropriate info at that time instead. Maybe?


Save knows nothing about the transport. It generates a file address,
thus requiring a file transport to process it.

First hack the transports for message flags, then add code for filters
to use them. And in order to hack transports, first find out how each
daemon implements message flags for each message store it can use, and
find a structure to represent all that.

I don't say it can't be done. It just requires some work, reading IMAP
server sources to begin with.

Michael