On Sun, Jan 04, 2009 at 09:31:42PM +0100, Patrick Ben Koetter wrote:
> Maps in $relay_recipient_maps are evaluated as lists - only the LHS is
> examined to determine if a recipient is listed and therefore a valid
> recipient.
Only used in smtpd(8) where no rewriting takes place, just address
validation, so nothing useful can be done with the RHS.
> Does the same apply for local_recipient_maps,
Ditto.
> virtual_alias_maps
Well, in smtpd(8) the RHS is ignored, and the table is used across all
address classes. In cleanup(8), this is used for rewriting of all
recipient addresses and the RHS is clearly not ignored.
> and virtual_mailbox_maps
in smtpd(8) used only for address validation, in virtual(8) used to
select the right mailbox, but there in some cases virtual mailbox
delivery is handled by other delivery agents, and in that case the
table's RHS is not used.
> I'm asking because I am trying to figure out what I need to do to accept
> messages for local/virtual mumble domains and have them sent off to a LMTP
> server afterwards.
Only virtual(5) RHS values will be used.
If you rewrite from an external virtual alias domain to the LMTP server's
internal domain, you don't any tables other than virtual_alias_maps,
and the external domain is typically a virtual alias domain.
If the LMTP delivery domain is the same as the external domain, use
virtual_mailbox_maps with RHS values that are not used by Postfix.
> Sending them off to a LMTP server is a transport map job:
>
> recipi...@example.com lmtp:localhost
The correct syntax (if the default port is OK) is:
recipi...@example.com lmtp:inet:localhost
Why per-recipient transport lookups? Often better to rewrite to a domain
where the entire domain is handled by lmtp(8).
> But what do I do to tell Postfix recipi...@example.com is a valid recipient?
Use virtual_mailbox_maps.
> Can I reuse my transport map and add it to local_recipient_maps,
> virtual_alias_maps or virtual_mailbox_maps as required?
Don't add $transport_maps to virtual_mailbox_maps, but if per-recipient
transport entries are the right solution, use a common table that you
add to both:
lmtp_user_transport_maps = <maptype>:<mapname>
transport_maps = ... $lmtp_user_transport_maps
virtual_mailbox_maps = ... $lmtp_user_transport_maps
Provided the same users will never reach virtual(8), the fact that
the RHS is transport-valued rather than mailbox-path-valued is not
a problem.
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majord...@postfix.org?body=unsubscribe%20postfix-users>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
