> Do you have just maildrop or /usr/local/bin/maildrop? That might
> not be on vpopmail's path. Is /usr/local/bin/maildrop actually there?
> If you cd into the sofast.net domain then cd .. and do an ls,
> do you see mailfilter in the listing?
>
As already stated, this solution has been working fo
> Benjamin Tomhave wrote:
>
> >>Where is maildrop being called? In the .qmail-default file of the
> >>sofast.net domain? What's it look like?
> > .qmail-default in the sofast.net domain root -- it's the
> standard call of
> > maildrop ../mailfilter within that file.
>
> Ok. Can we see the mailfi
Benjamin Tomhave wrote:
Where is maildrop being called? In the .qmail-default file of the
sofast.net domain? What's it look like?
.qmail-default in the sofast.net domain root -- it's the standard call of
maildrop ../mailfilter within that file.
Ok. Can we see the mailfilter?
Jeff
--
/\ /\
> Where is maildrop being called? In the .qmail-default file of the
> sofast.net domain? What's it look like?
>
.qmail-default in the sofast.net domain root -- it's the standard call of
maildrop ../mailfilter within that file.
> And is the test message you sent in the [EMAIL PROTECTED] mailbox?
Benjamin Tomhave wrote:
I just setup a test account, [EMAIL PROTECTED], and then logged into
qmailadmin and setup a forward to go to my work account,
[EMAIL PROTECTED] I sent an email from my work account to my test
account, and I see the below information. Possibly of interest is that the
.Spa
> What's your qmail log file say?
>
> If the contents are just a forward, no mail is going to be saved locally
> for that account, are you sure the remote account (&[EMAIL PROTECTED]) is
> *not* receiving the mail?
>
I just setup a test account, [EMAIL PROTECTED], and then logged into
qmailadmin an
Benjamin Tomhave wrote:
It works for me, although I'm using vpopmail 5.3.23. I don't know if
it was broken in some earlier versions. Are you sure the contents of the
.qmail file are sensible?
Yep, the file appears to be created correctly (vpopmail:vchkpw chmod 600)
and the contents appear to be c
> It works for me, although I'm using vpopmail 5.3.23. I don't know if
> it was broken in some earlier versions. Are you sure the contents of the
> .qmail file are sensible?
>
Yep, the file appears to be created correctly (vpopmail:vchkpw chmod 600)
and the contents appear to be correct (&[EMAIL