11 messages in net.sourceforge.lists.courier-users[courier-users] Re: maildrop as local...
FromSent OnAttachments
Chris MacLeodAug 7, 2002 12:56 pm 
Sam VarshavchikAug 7, 2002 1:34 pm 
Chris MacLeodAug 7, 2002 1:46 pm 
Moshe GurvichAug 7, 2002 1:49 pm 
Moshe GurvichAug 7, 2002 2:51 pm 
Chris MacLeodAug 7, 2002 3:01 pm 
Moshe GurvichAug 7, 2002 3:07 pm 
Chris MacLeodAug 7, 2002 3:24 pm 
Sam VarshavchikAug 7, 2002 3:43 pm 
Moshe GurvichAug 7, 2002 3:52 pm 
Chris MacLeodAug 7, 2002 4:38 pm 
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:[courier-users] Re: maildrop as local deliveryActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Aug 7, 2002 3:43:43 pm
List:net.sourceforge.lists.courier-users

Chris MacLeod writes:

like I said, I'm using authdaemon.plain and all my users are stored in couriers internal userdb.

in the userdb mail and home are set to the same thing (/home/mail/domain.com/user) where user is the maildir

That's what I said before: the mail attribute overrides DEFAULTDELIVERY.

Accounts are created using userdb and maildirmake /home/mail/domain.com/user

This is not an "account" under any normal definition. An "account" is something that has a home directory, and perhaps some files in there. You do not have anything that resembles a home directory, hence you cannot use maildrop. You're dumping mail directly into a maildir directory, so you can't do anything much more to it.

To use mail filtering, and pretty much everything else, you need to have each mail account set up in a way that it somewhat resembles a real account: with a home directory, and $HOME/Maildir, where mail gets delivered to.

-- Sam