Okay then. Anyone for collaborating on setting one up, with a unified accessor syntax similar to what we have for "notes" ?
http://advenge.com/2009/products/downloads/qpsmtpd/plugins/verp is a working plugin that uses DirDB persistence library to rewrite the envelope return addresses of all traffic except traffic that is exempt due to relaying-okay or the verp_no note getting set. a persistent notes -- maybe "pnotes" like notes, but persistent -- would be more general and could be replaced with a backend as needed. As for lasting between two and three weeks, well, what all is needed? On Fri, Feb 20, 2009 at 1:35 PM, Robert Spier <rsp...@pobox.com> wrote: > > Yes. I did. > > The answer to your question is "No. There is no standard persistence > mechanism" > > -R > > David Nicol wrote: >> >> No. Did you? >> >> On Fri, Feb 20, 2009 at 12:30 AM, Robert Spier <rsp...@pobox.com> wrote: >> > >> > Did you mean to reply to the list? >> > >> > David Nicol wrote: >> >> >> >> between those three I'd have to go with "forever" for both VERP >> >> addresses and per-recipient database things. Other existing things >> >> that we would want to bring into the fold of a general persistence >> >> framework would include greylisting database, which is also in the >> >> forever choice of those three. >> >> >> >> On Thu, Feb 19, 2009 at 12:37 AM, Robert Spier <rsp...@pobox.com> wrote: >> >> > >> >> > >> >> > David Nicol wrote: >> >> >> is there a standard way for a qpsmtpd plugin to maintain persistent >> >> >> state? >> >> >> I'm using DirDB, but having a framework-provided DBI handle would be >> >> >> better >> >> > >> >> > What kind of persistence? >> >> > >> >> > Per connection? >> >> > Per transaction? >> >> > Forever? >> >> > >> >> > -R -- Freedom's colors are red, white and black and blue.
