I am running the Qmail Toaster as available from www.qmailtoaster.com. (vpopmail-toaster-5.3.8).


There's something about the behavior of the .qmail files in the individual vpopmail account directories that I don't understand.

If a program invoked from a .qmail file returns an exit status of 99 (per qmail-command man page) shouldn't it just stop processing the qmail file? It seems to be deferring the message and trying to redeliver it later.

I have a test domain "vpopmail.yml.com" and a user "test". The account directory I have is:

/home/vpopmail/domains/vpopmail.yml.com/test/

In it I have a ".qmail" file containing, for demonstration:

|/tmp/test.pl
/home/vpopmail/domains/vpopmail.yml.com/test/Maildir/

test.pl contains:

#!/usr/bin/perl
print "This is a test";
exit( 99 );

What I am noticing is that the message is being deferred and dropped into the queue:

@400000003fc81ac413506794 info msg 1491341: bytes 955 from <[EMAIL PROTECTED]> qp 6929 uid 89
@400000003fc81ac416462fc4 starting delivery 2560: msg 1491341 to local [EMAIL PROTECTED]
@400000003fc81ac4164656d4 status: local 1/10 remote 0/255
@400000003fc81ac4171b1b94 delivery 2560: deferral: This_is_a_test
@400000003fc81ac4171c020c status: local 0/10 remote 0/255


This doesn't seem right.

If I set the exit code to 100 in test.pl I get

@400000003fc81ddc253b3a24 new msg 1491355
@400000003fc81ddc253c3bf4 info msg 1491355: bytes 955 from <[EMAIL PROTECTED]> qp 7501 uid 89
@400000003fc81ddc28755e54 starting delivery 2605: msg 1491355 to local [EMAIL PROTECTED]
@400000003fc81ddc28759504 status: local 1/10 remote 0/255
@400000003fc81ddc2a86dd1c delivery 2605: deferral:
@400000003fc81ddc2a870814 status: local 0/10 remote 0/255


Shouldn't it bounce?

By comparison I tried the same experiment using the
/home/vpopmail/domains/vpopmail.yml.com/.qmail-defaults file.

test.pl with exit code of 100 yields:

@400000003fc81e2917a81954 new msg 1491361
@400000003fc81e2917a91b24 info msg 1491361: bytes 955 from <[EMAIL PROTECTED]> qp 7508 uid 89
@400000003fc81e291aa9c47c starting delivery 2606: msg 1491361 to local [EMAIL PROTECTED]
@400000003fc81e291aaa31dc status: local 1/10 remote 0/255
@400000003fc81e291b2011a4 delivery 2606: failure:
@400000003fc81e291b228a74 status: local 0/10 remote 0/255
@400000003fc81e291d220bc4 bounce msg 1491361 qp 7511
@400000003fc81e291d23405c end msg 1491361
@400000003fc81e291d26556c new msg 1491362
@400000003fc81e291d272c44 info msg 1491362: bytes 1454 from <> qp 7511 uid 506
@400000003fc81e2920be7c04 starting delivery 2607: msg 1491362 to remote [EMAIL PROTECTED]
@400000003fc81e2920beaecc status: local 0/10 remote 1/255
@400000003fc81e292b13f634 delivery 2607: success: 207.192.181.135_accepted_message./Remote_host_said:_250_2.0.0_hAT45hX4027171_Message_accepted_for_delivery/
@400000003fc81e292b16e81c status: local 0/10 remote 0/255
@400000003fc81e292b17b33c end msg 1491362


(and i get a failure notice as I would expect)

test.pl with an exit code of 99 yields:

@400000003fc81e6014fc100c new msg 1491355
@400000003fc81e6014fd67cc info msg 1491355: bytes 955 from <[EMAIL PROTECTED]> qp 7520 uid 89
@400000003fc81e601834b184 starting delivery 2610: msg 1491355 to local [EMAIL PROTECTED]
@400000003fc81e601834d894 status: local 1/10 remote 0/255
@400000003fc81e6018abfc94 delivery 2610: success: did_0+0+1/
@400000003fc81e6018ad312c status: local 0/10 remote 0/255
@400000003fc81e6018ad38fc end msg 1491355


which is also what I would expect.

I am not that familiar with vpopmail yet so correct me if I'm wrong but it's vdelivermail called from the domains/domain/.qmail-default file that actually processes the per-account .qmail files? Right?

Looking at run_command() in vqmaillocal.c it does not seem that the exit code of the launched process is being examined .. if a line it found it looks like it's exiting with a value of 0.

What am I missing?

thanks,

-- Yermo

P.S. BTW, the Vpopmail/qmail combo simply rocks.

---------------------------------------------------------------------
DTLink Software                                 http://www.dtlink.com
---------------------------------------------------------------------




Reply via email to