Please give me more details on what you guys want added, etc. Since the two
functions are really the same it would be easiest just to add some extra
options to the code. And a sourceforge project is fine. Just was curious how
it got there. And whomever added the patch's can take over maintaining it
there and I can give them some updates or he can code. I have been very busy
with work so my extra time has gone to sleeping.
We essentially need a way to tell autorespond that it's acting as a vacation responder, or an auto responder.
In the case of a vacation responder, default behavior should be to exit so that .qmail processing continues. It shouldn't bounce mailing list messages, and it shouldn't ever exit(99). The version of autorespond I have in QmailAdmin's CVS goes this route.
As an autoresponder, it can bounce mailing lists and bulk mail, and the exit code is less important (because it typically exists in a .qmail file alone).
If it's going to continue to be a part of the QmailAdmin project, I'll add Brad as well.
Not sure if Inter7 is going to keep handling the dev. What is the story with
vpopmail and qmailadmin? Sourceforge is a great place. Use it almost daily.
Inter7 is still involved with qmailadmin and vpopmail development on SourceForge. Ken Jones has also put vqadmin up there. Email me with your SF id and I'll add you as a developer so you can make use of the autorespond CVS.
Unless I hear otherwise from Inter7, I'll keep autorespond in the qmailadmin project.
-- Tom Collins [EMAIL PROTECTED] QmailAdmin: http://qmailadmin.sf.net/ Vpopmail: http://vpopmail.sf.net/ Info on the Sniffter hand-held Network Tester: http://sniffter.com/
