Hi. I'm using the qmail-qfilter program to call qmail-queue. qmail-scanner is calling qmail-qfilter. As the qmail program is written, it supports the return code of 31 to indicate permanent failure. (I direct you to the ending lines of qmail.c source. Also, the docs of qmail-qfilter are helpful here). http://www.mit.edu/afs/sipb/service/mail/src/qmail-1.03/qmail-1.03/qmail.c http://untroubled.org/qmail-qfilter/
qmail-scanner does not support the fatal failure supportive handing of exit code 31 which would permit the usual chaining of these programs.
if ($status != 0) { &tempfail ("Unable to queue message ($status). (#4.3.0) -\
$!" )}
Has anyone modified qmail-scanner for robust general use with qmail-qfilter? I'd think of two possible ways to do this.
1) add exit code 31 as a condition handled and returned by qmail-scanner
or
2) have qmail-scanner use sysin and sysout in the general way that filters do in the qmail-qfilter world.
Any thoughts?
Thanks, John
Hi again.
Since qmail-scanner can not return the same codes that qmail.c can handle, and since qmail-qfilter functionality is desired, my solution will be to have qmail-qfilter's interlude call qmail-scanner rather than the other way around. I can then return a failure to qmail.c if conditions warrant it during qfilter processing.
It would be nice for me if qmail-scanner could be such a filter. (sysin/sysout rather than fd's as presently used).
Thanks, John
------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
