On Thu, May 10, 2007, Jake Anderson <[EMAIL PROTECTED]> said: > Paul J Stevens wrote: >> Aaron Stone wrote: >> >>> Looks interesting. >>> >>> As I just noted in bug #380, I think it would make a lot of sense for >>> dbmail-export to be able to delete the messages after export, and to >>> accept additional fine-grained message selection criteria. >>> >> >> Agreed. >> >> >>> I wonder if just adding an IMAP search string wouldn't make the most >>> sense, actually? You've added what is going to look like "-s 1:*" and we >>> could extend that to do date-based deletion like this: >>> >>> dbmail-export -s "1:* BEFORE 10-Apr-2007" >>> >>> That would export everything older than 30 days from 10, and with >>> another option flag also delete those message (perhaps '-d' for set >>> delete status, same as dbmail-util?) >>> >> >> The thought crossed my mind :-) >> >> The basic callflow would be >> >> char **build_args_array_ext(struct ImapSession *self, const char >> *originalString) >> >> int dbmail_mailbox_build_imap_search(struct DbmailMailbox *self, char >> **search_keys, u64_t *idx, search_order_t order) >> >> int dbmail_mailbox_search(struct DbmailMailbox *self) >> >> int dbmail_mailbox_dump(struct DbmailMailbox *self, FILE *file) >> >> >> Simple! But its time for bed here.... >> >> >> > something that might be handy is logging by domain. something like > apache with its vhosts. Such that i can farm off logs for a particular > domain to its admin.
How does this relate to the functionality of dbmail-export? Aaron _______________________________________________ Dbmail-dev mailing list [email protected] http://twister.fastxs.net/mailman/listinfo/dbmail-dev
