Le 28/03/2011 19:42, Simon Brereton a écrit :
>> [snip]
>>> So this is my attempt:
>>>
>>> deliverquota unix - n n - - pipe
>>> flags=DRhu user=vmail argv=/usr/bin/deliverquota
>> $domain/$recipient
>>>
>>> One concern - vmail is not a user on my system (and since I copied
>> this from the maildrop pipe, I'm now wondering how mail is delivered
>> at all.
>>>
>>
>> Not via maildrop, since the user does not exist.
>> The first message postfix tries to deliver to the maildrop transport
>> will crash it with a fatal error.
>>
>> For basic information on how (local) mail is delivered, read
>> http://www.postfix.org/OVERVIEW.html#delivering
>
> I agree with your diagnosis :) I'm just now confused as to what *is*
> delivering mail. I'll try to figure that out.
>
mail is delivered by whatever you define as a transport.
you can define 100 transports in master.cf without these being used at
all. in short
deliverquota unix - ..... pipe
...
in master.cf defines a transport. it doesn't say that transport will be
used.
that said, don't approach the quota problem until you have a good
confidence in understanding other stuff. quota is a hard problem.
>>> My first question is, is $domain/$recipient the way to deliver a
>> Maildir structure that is always domain.tld/user where user is the
>> portion before the @ - this is the way I've understood man pipe, but
>> I'd like to be sure.
in your example, postfix doesn't care what $domain/$recipient means. it
is passed as an argument to deliverquota.
You have a choice:
- you let postfix deliver, in which case this is defined via things like
virtual_recipient_maps.
- you deliver with something else (dovecot, maildrop, whatever) in which
case postfix doesn't care where your mail goes.
>>> Do I need it to be unpriv or not?
leave it to the default value: make it a '-'.
>>[snip]
