9 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] Yikes! default rule d...
FromSent OnAttachments
up...@3.amApr 23, 2004 9:38 am 
Sean DelkApr 23, 2004 10:01 am 
up...@3.amApr 23, 2004 10:31 am 
up...@3.amApr 23, 2004 11:35 am 
up...@3.amApr 23, 2004 1:11 pm 
up...@3.amApr 24, 2004 6:55 am 
Ron JohnsonApr 24, 2004 9:40 am 
Sam VarshavchikApr 24, 2004 11:31 am 
up...@3.amApr 25, 2004 6:21 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [maildropl] Yikes! default rule doesn't work after upgradeActions...
From:up...@3.am (up@3.am)
Date:Apr 23, 2004 11:35:50 am
List:net.sourceforge.lists.courier-maildrop

On Fri, 23 Apr 2004 up@3.am wrote:

That's basically my question. I'm trying to figure out whether or not something changed in the newer version of maildrop that would affect the default delivery. There are no .qmail files in the userdirs, because that caused maildrop to be ignored in the past. qmail is being invoked like this:

exec env - PATH="/var/qmail/bin:$PATH" \ qmail-start '|preline maildrop' splogger qmail

uh...I figured it out (so it appears). It seems the new server was including "./" in the root user's path (the old one was not), and that was enough to cause this problem. I'm not precisely sure why, but it seems to have fixed the problem.

Thanks!