6 messages in net.sourceforge.lists.courier-maildropRe: [maildropl] couple of questions
FromSent OnAttachments
Cristian GrigoriuMar 5, 2003 9:21 am 
Gregor LawatscheckMar 5, 2003 10:46 am 
gp...@mpex.netMar 5, 2003 11:58 am 
Gregor LawatscheckMar 5, 2003 1:05 pm 
Gregor LawatscheckMar 6, 2003 10:49 pm 
Gregor LawatscheckMar 7, 2003 5:44 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] couple of questionsActions...
From:Gregor Lawatscheck (gp@mpex.net)
Date:Mar 5, 2003 1:05:56 pm
List:net.sourceforge.lists.courier-maildrop

At 20:44 05/03/2003, you wrote:

What you need to do is to specify the MailDir of your secretary's account. Whereever that might be... For example: to "/home/secretary/Maildir/".

The qmail-inject or !email@address is only useful in the maildrop when forwarding to an external account.

Hmm. Think again. If this would be true, there would be no security on that machine, don't you agree?

Well, but you do agree hat injecting the mail again and again will loop? With the current setup the mail will come in, be forwarded to the secretary, go through the filter again and again...

Concering security: I use a vpopmail setup. All accounts are owned by a single vpopmail user. Maildrop is run as this user and puts mail in people's maildir with this uid. The POP3 server authenticates users then reads mail with the vpopmail uid.

In your setup, I'm assuming maildrop should be running as the uid of the user that gets mail as to be able to write to that directory. I don't know where your maildir directories are and who they are owned by and who should have access to them apart from the MUAs. Maildrop is a local mail delivery replacement with a good filtering engine. A local mail delivery agent needs to be able to write mail somewhere and needs adequate permissions to do so. Some LDAs run as root... which is obviously not optimal.