Le 19/05/2012 16:50, john a écrit :
> {snip]
> Thanks for the pointer to pipe document, I had Googled, but I got a mass
> of not very useful hits.
>
the official documentation of postfix can be found on
http://www.postfix.org/documentation.html
for the man pages, click on "All Postfix manual pages", which leads you to
http://www.postfix.org/postfix-manuals.html
and for all postfix parameters, click on "All main.cf parameters", which
leads you to
http://www.postfix.org/postconf.5.html
> OK, so if I got this right, were to continue using ${recipient} then I
> am passing /joe+extens...@example.com/ to the LDA which may not be good.
>
> I assume that ${domain} is extracted from the recipient address and
> therefor might possible be blank (null),
the domain is never empty. (unless you configure postfix not to append
@myroigin, which is highly discouraged).
> but in the case above should
> result in /example.com/. Therefore ${user}@${domain} could give me /joe
> /(assuming an address of just/jo/e) or /j...@example.com/ (assuming the
> example above).
>
> Whereas, it appears that ${nexthop} is either equals${domain} if the
> address is as above or ${mydomain} again assuming the the recipient
> address is just /joe,/ right?/
>
${nexthop} can be set by you in a transport entry.
> /If I am right, big if, then it would appear to be better to use
> ${domain} rather than ${nexthop}.
if using postfix 2.5 or higher (the variable didn't exist before).
> However, rereading the Dovecot LDA docs I might be better using
> ${recipient} as it appears that Dovecot parse the arguments anyway.
>
well, the risk is if you change the extension delimiter in postfix but
dovecot keeps using '+'. I prefer to handle the extension in postfix and
pass it via -m to dovecot.
> Oh well, back to the docs.
>
> Thanks for the help, but I think I am going to do a lot more reading!
>
> JohnA
>
>
