On Thu, August 10, 2006 3:31 pm, Steve wrote:
I've compiled this 3 times on different systems, and used the default,
procmail, and maildrop.
You've compiled what? What are you trying to do? What are you using?
What I get is mail delivered to a file in the user directory called
"Maildir"
If a Maildir does not exist for a specified folder, maildrop will assume
you were referring to a mbox folder and will create it for you if it
doesn't exist. You can get around this by specifying a closing / on the
folder name so that maildrop is forced to assume it is a Maildir.
If I use the maildirmake utility, the mails will sit in the queue forever
(or until they expire.)
Are there delivery attempts? What does /var/log/maillog say? Are the
permissions on the Maildir correct?
I've read in the courier documentation about using the mailfiles or
maildirs, and I know that this is not what is intended.
Not sure what your even referring to here...
Systems are CentOS, RHEL3AS, RHEL4AS
Have a RHEL4 box myself and RHEL3 before that. Works great, more details
of what you're trying to do and what your config files look like are
needed to give you any real help here...
Jay
7 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Maildir - creates...
