Aaron Stone wrote:
typedef struct sieve2_vacation_context {
int min_response; /* 0 -> defaults to 3 */
int max_response; /* 0 -> defaults to 90 */
Are these for loop protection?
/* In Sieve 2, send_response is right here */
struct {
char *addr;
char *fromaddr;
char *subj;
char *msg;
int mime;
} send;
/* In Sieve 2, check_response is right here */
struct {
unsigned char *hash;
int len;
int days;
} check;
What's this about?
} sieve2_vacation_context_t;
If we can build the foundation of vacation support that provides the
necessary checks for whether or not a message should get a vacation reply,
then we can plug it right into libSieve and put together a big piece of
the sieve puzzle.
I'm not quite sure what you mean here, but I gather that if we manage to provide
a solid api for auto_reply handling we can later defer parts of that code to the
sieve subsystem, right?
--
________________________________________________________________
Paul Stevens [EMAIL PROTECTED]
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands_______________________________________www.nfg.nl
