On Wed, 2006-01-25 at 09:53 +0100, Paul J Stevens wrote:
> Don't worry about vacation for now. The auto_reply functionality in 2.1
> is doing just fine.
But it cannot be managed except by directly accessing the auto_reply
table. Vacation can be managed through the ManageSieve protocol.
Vacation requires a table to store some information, too. I'm thinking
of an interface like this:
db_vacation_{set/get}last(useridnr, msg_hash, ×tamp);
Something the Sieve vacation system does that the auto_reply table
appears not to do is allow the user to rate-limit their vacation
messages. That would be a nice feature for auto_reply, and the two could
reasonably share a table.
Aaron