Look in syslog (/var/log/messages) when that problem happens.
Look for vdelivermail. Do you see any vdelivermail coredumps?
If yes, then this is the same problem I had, which is most likely related to
vdelivermail not handling certain maildrop exit codes (I dont recall them off
hand)
So as a workaround, try this:
SHELL="/bin/sh"
import EXT
import HOST
VHOME=`~vpopmail/bin/vuserinfo -d [EMAIL PROTECTED]
`test -d $VHOME/Maildir`
if ( $RETURNCODE == 1 )
{
echo "Sorry, no mailbox here by that name. (#5.1.1)"
EXITCODE=100
exit
}
# Default delivery
exception {
to "$VHOME/Maildir/"
}
Quoting Leto Tokarev <[EMAIL PROTECTED]>:
> Hi!
>
>
> vpopmail 5.2.1+seekable
> maildrop 1.5.1
> (same results with mdrop1.6, 1.6.1, vpop5.3.27)
>
> .qmail-default:
> | preline /usr/local/bin/maildrop mailfilter
>
> ----
> very simple mailfilter:
> logfile x
> import EXT
> import HOST
> VPOP="| /var/vpopmail/bin/vdelivermail '' bounce-no-mailbox"
> to "$VPOP"
>
> ----
>
> [EMAIL PROTECTED] is a Maildir.
>
> valias [EMAIL PROTECTED] -> [EMAIL PROTECTED] comes from mysql table.
>
> Out of 10 mails sent to "[EMAIL PROTECTED]" usually 4 lose, 6 gets
> delivered.
>
> What should I look for?
>
> I debugged what's happening with vdelivermail:
>
> It always gets the mail, and looks up the valias.
> When things okay, it runs a second delivery, but this time to the final
> Maildir.
> Sometimes this step missing.
>
> More strange: 100% success when an alias comes from dot-qmail file, or
> when the valias points to a different domain (no matter if local or
> remote).
>
>
>
> Leto
>
>
>
Respectfully,
Tim Hasson
