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?