on 8/19/01 4:36 PM, blinky at [EMAIL PROTECTED] spake:
> hi.
>
> i've just put this line into the valias-mysql-table
>
> +--------+----------+-------------------------------------------------+
> | alias | domain | valias_line |
> +--------+----------+-------------------------------------------------+
> | bla | test.com | /var/qmail/domains/test.com/postmaster/Maildir/ |
> +--------+----------+-------------------------------------------------+
>
> now i tried to send a message to [EMAIL PROTECTED] and got the maillog-line below
> because i made a mistake in the directory-line ('/vpopmail/' is missing,
> correct is: /var/qmail/vpopmail/domains/test.com/postmaster/Maildir/
>
> Aug 19 22:53:57 s1 qmail: 998254437.166753 delivery 7: success:
> can_not_open_new_email_file_errno=2_file=/var/qmail/domains/test.de/postmaster
> /Maildir/tmp/998254437.6002.s1.mystic.org,S=191/vdelivermail:_valiases_process
> ed/did_0+0+1/
>
> the bug is that vdelivermail/valias wasn't able to successfully write the mail
> to disk but it reports 'sucess' to qmail. this is why it is deleted in the
> qmail-queue... at least i think so. shouldn't it bounce or at least stay in
> the queue? i think just 'deleting' a not deliverable message isn't that good
> ;-)
>
>
> ... i corrected the valias_line so the path is correct and now everything
> works :)
This is not the case in the development version (as of 4.10.32). It returns
an error of -2 and qmail-local properly sees it as a failure:
@400000003b85ec112c7add1c delivery 1: failure:
can_not_open_new_email_file_errno=2_file=/home/vpopmail/domains/test/testuse
r0/Maildir/tmp/998632455.21910.data.shupp.org,S=213/
It's useful to all to check the latest development release before reporting
a bug.
Cheers,
Bill Shupp
