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_processed/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 :)
but: is there a way to not have the full path in the valias_line field? so that 
'./postmaster/Maildir/' or so is enough...

criteria for valias:

if the line starts with a '|' -> execute a command
if the line starts with a './' or a '/' -> local delivery
if the value contains a @-sign -> it is a forward

the last criteria is maybe useless because if no one of the first two criterias match 
it must be a forward ... (at least i think so. maybe i'm wrong ;-)


thanks for reading :)

cheers,

blinky

PS: ohhh.. btw: another field called 'rang' or so would be nice so it is possible to 
define in which order delivery should happen. the sql-command in vdelivermail will 
than need something like 'order by rang' in addition.


Reply via email to