On Wed, Apr 09, 2003 at 01:37:47PM -0600, Benjamin Tomhave wrote:
Problem solved (sort of)! I found a diff. list archive and, from January,
found the following posting:
http://www.riverside.org/archive/html/maildrop/2003-01/msg00008.html
In that posting, it says that maildrop uses the shell of the calling user.
In my case, this user is vpopmail, and had a shell of /sbin/nologin listed.
As soon as I changed it to /bin/bash, then all was well. Unfortunately,
this opens up a potentially glaring security hole, too. I don't think I
want vpopmail to have a valid shell, though, do I? Anyway... that leads me
to the following...
FEATURE REQUEST:
I would like a configuration option (or patch, I guess, though I wouldn't
know where to begin with that) to choose whether maildrop uses the calling
account's shell or if it uses a hardcoded shell. I personally would prefer
to have a hardcoded shell since this seems safer than using the calling
account's shell.
Thoughts? Flames?
You could just add the line:
SHELL="/bin/sh"
to the top of the mailfilter.
4 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] maildrop 1.5.2 + vpop...
