On 09/24/01 12:50 PM, Ken Murchison sat at the `puter and typed:
>
> > Louis LeBlanc wrote:
> >
> > Yes, the permissions are set. I try to send to userid+folder@host,
> > where users.userid.folder has anyone p set. Procmail is calling
> >
> > deliver -q -m folder -- userid
> >
> > The procmail log shows deliver being called correctly, but the message
> > still gets dropped into the INBOX.
>
> Works for me (current CVS).
>
> localhost> lam user.test.sub
> test lrswipcda
> anyone p
>
> As the 'cyrus' user: deliver -q -m sub -- test < /tmp/foo
>
> The message ends up in test's 'sub' folder (INBOX.sub = user.test.sub)
Ok, so are there any ideas why it wouldn't work in the 2.0.16 release?
Or suggestions as to how to fix it? I will test your delivery test
this evening when I get home, but this is what I am calling from
procmail:
/usr/local/cyrus/bin/deliver -q -m root -- leblanc
Compared to the call I was using with Cyrus 1.6.24:
/usr/cyrus/bin/deliver -e -q -m procmail -- leblanc
Of course the path is different on different systems, and the -e flag
is left out, but it is the same, and complies with the documentation.
I'm not sure I'd care to run a cvs release. Not an issue of critical
services (though I'd like to think my own email is at least a little
important :), but I'd like to get this set up and have it work without
interference for long enough to forget all the little details (again).
Thanks
Lou
--
Louis LeBlanc [EMAIL PROTECTED]
Fully Funded Hobbyist, KeySlapper Extrordinaire :)
http://acadia.ne.mediaone.net ԿԬ
One can search the brain with a microscope and not find the
mind, and can search the stars with a telescope and not find God.
-- J. Gustav White
