Tom,
On Wed, Oct 23, 2002 at 01:43:19PM +0200, Thomas Baker wrote:
> On Wed, Oct 23, 2002 at 07:16:14AM -0400, Jason Tishler wrote:
> > What *exactly* does procmail.log indicate happened to the misfiled
> > messages?
>
> Attached is the entire procmail.log -- i.e., the log
> captures the file tested with "cat test.mbox | procmail -m
> e:/.procmailrc" (above), but does not register any of the
> incoming mail that is constantly arriving, which all simply
> goes to the default /var/spool/mail/tbaker.
See below...
On Wed, Oct 23, 2002 at 10:56:48AM +0200, Thomas Baker wrote:
> On Tue, Oct 22, 2002 at 08:14:52AM -0400, Jason Tishler wrote:
> > I would check the permissions of $PMDIR, $PMDIR/procmail.log, and
> > your entire $MAILDIR tree.
>
> [snip]
>
> $PMDIR:
> drwxr-xr-x 2 tbaker None 4096 Oct 23 10:44 e:/u/procmail
>
> Are these permissions set as they should be?
Is fetchmail running under the LocalSystem account? If so, then perform
the following:
chmod 777 e:/u/procmail
Can procmail write to e:/u/procmail/procmail.log when driven by
fetchmail now? If so, does it indicate why procmail can't write to your
mail folders?
If fetchmail is running under your account, then I'm at a loss to explain
your observed behavior.
Jason
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
