14 messages in net.sourceforge.lists.courier-maildropRe: AW: [maildropl] Help! got stuck.....
FromSent OnAttachments
Andreas VogtNov 10, 2004 11:51 pm 
Andreas VogtNov 11, 2004 1:13 am 
p dont thinkNov 11, 2004 1:18 am 
p dont thinkNov 11, 2004 1:35 am 
p dont thinkNov 11, 2004 1:35 am 
Tony EarnshawNov 12, 2004 1:45 am 
Petri RiihikallioNov 12, 2004 9:08 am 
Tony EarnshawNov 13, 2004 2:36 am 
p dont thinkNov 13, 2004 2:27 pm 
Tony EarnshawNov 13, 2004 5:19 pm 
p dont thinkNov 13, 2004 9:19 pm 
Tony EarnshawNov 14, 2004 9:49 am 
p dont thinkNov 19, 2004 4:40 pm 
Jeremy KitchenNov 19, 2004 6:23 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:Re: AW: [maildropl] Help! got stuck...(user unknown. Command output: Invalid user specified. )Actions...
From:p dont think (pdon@angrynerds.com)
Date:Nov 11, 2004 1:35:41 am
List:net.sourceforge.lists.courier-maildrop

Andreas Vogt wrote:

P dont think wrote:

did you compile with --enable-maildirquota?

No. Is it necessary? I'll do

um, well, you said you want quota support, right?

virtual_transport = maildrop maildrop_destination_recipient_limit = 1 maildrop_destiantion_concurrency_limit = 1

I've never seen the concurrency need to be changed from its default for maildrop to work right.

I read that in any howto. Does maildrop support multiple rcpts?

I said concurrency, meaning only the last line is unnecessary. You MUST use maildrop_destination_recipient_limit, or you will have problems, mostly with messages going to multiple recipients. Maildrop does not have problems with concurrent delivery, however. It's smarter than that.

master.cf:

maildrop unix - n n - - pipe -v flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${user}@${nexthop} ${extension} ${recipient} ${user} ${nexthop}

woa. ever done a man maildrop? what are you expecting all those args to do?

This is how it's done in MANY howto's. yes this made me really confused. Because I read the maildrop manual. :o))

No it's not done that way in any howto's. Maildrop doesn't accept that many arguments.

try something like this: maildrop unix - n n - - pipe flags=uR user=vmail argv=/usr/local/bin/maildrop -d $recipient -w 90

What is the value of recipient? Is it the users full email-address?

yah

I think maildrop nead this variable to find the maildir of the user.

yah, most systems worth their salt, this is the case. that's why i suggested it

I have: /var/vmail/d/domain.tld/uid/

maildrop doesn't care yet. it will get that information when it queries LDAP

I don't think that this is tha value of $recipient

uh, no, $recipient doesn't have a directory path in it! why would it be called "recipient"? postfix can't give you any paths to a virtual user's home directory!

. Or does maildrop use recipient to do an ldap lookup? (I never saw anything from maildrop in ldap-logs.

- did you compile with --enable-maildropldap? - did you edit and copy maildropldap.config into the right place? - did you *really* read the documentation?