Will Berry wrote:
Paul J Stevens wrote:
Whichever, through a build-in or external facility: it should be done
right in the end and should therefore adher to dbmail's inherently
distributed nature. (read: minimal filesystem dependancies)
Once 2.0 is officially released, then any changes to the DB structure
mandate a 2.1 version fork in my view. If auto-reply is a
significantly important feature for the users, then the changes should
probably be agreed upon and made now before the official 2.0 release,
even if the code above the database is skeletal or even downright
buggy in 2.0. My opinion.
Good idea about the database structure having to be fixed before 2.0. We
should compile a list of features that auto replies should have. I'm not
too familiar with the features of vacation. I'll do some reading on that
right away.
I think auto-replies should depend on the recipient address, and not
be linked to a mailbox at all. That is how vacation works, and that
is how I've setup my script.
OK, that makes sense. So how about this then?
alter table auto_replies drop column user_idnr;
alter table auto_replies add column flags set ('active') not null
default '' after auto_reply_idnr;
I'd go for a flag like we use elsewhere in DBMail (not because it's
better, but because we use it there)
alter table auto_replies add column active_flag tinyint(1) not null
default 0 after auto_reply_idnr;
alter table aliases add column auto_reply_idnr not null default 0
after client_idnr;
As for the other features in your script that use "repeating items",
such as ignoring certain senders, that would of course have to go
either in the dbmail config file as a delimited list or in accessory
tables. This, however, could probably be put off until 2.1 more
easily, since one could always configure a "mailing list only" alias
and never have an auto-reply activated for that address.
Does vacation have such a list, or does it use certain rules for not
sending auto_replies?
Ilja
--
Ilja Booij
IC&S B.V.
Stadhouderslaan 57
3583 JD Utrecht
www.ic-s.nl
T algemeen: 030 6355730
T direct: 030 6355739
F: 030 6355731
E: [EMAIL PROTECTED]
