And to show you what I mean by not having luck with it, here is what
happened when I just now tried it again.
@400000003a2d28b53959f7fc new msg 190570
@400000003a2d28b5396de1a4 info msg 190570: bytes 695 from
<[EMAIL PROTECTED]> qp 67426 uid 89
@400000003a2d28b602836ccc delivery 17872: success: did_0+0+1/
@400000003a2d28b6030f2654 status: local 0/10 remote 1/20
@400000003a2d28b6031348ec starting delivery 17873: msg 190570 to local
[EMAIL PROTECTED]
@400000003a2d28b60314bc04 status: local 1/10 remote 1/20
@400000003a2d28b6031859cc end msg 190568
That is only the FIRST of several delivery attempts.. which would've kept
on going if I hadn't of moved my .qmail file to a new name.
Here is contents of my .qmail file:
|/usr/local/bin/maildrop
/usr/local/vpopmail/domains/oregonfast.net/1/daemus/.mailfilter
And the contents for Maildir/maildirfilterconfig:
MAILDIRFILTER=../.mailfilter
MAILDIR=./Maildir
James writes:
>
> But at least it would serve as an example.
> I'll tell you my setup. All domains are virtual domains. All are owned by
> vpopmail:vchkpw. vpopmail is in /usr/local/vpopmail. Both vpopmail and
> sqwebmail are installed from the FreeBSD ports collection. vpopmail was
> configured with large site support. I'm using the (default?) vpasswd file
> in each domain's directory for authentication. sqwebmail is version 1.0.3,
> and vpopmail is version 4.9.4. Is there any other info that you need that
> may affect the maildirfilterconfig file that someone posts? I just need a
> working example, as I haven't really had any luck with it in the past.
