OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Postfix Archives: Re: mydestination questions...

Re: mydestination questions...

Subject: Re: mydestination questions...
From: Andrew McNamara (andrewmconnect.com.au)
Date: Thu Jan 20 2000 - 23:12:53 CST

>Per the release notes, the transport map overrides mydestination.

Yep - which is new.

>> The way I had been imagining mydestination to work was as a sort of
>> implicit "$mydestination local:" entry in transports - clearly it's
>> not. Which leaves me asking what it is?
>
>It's what's local when you don't have a transport map. :-) I'm not
>sure what else it means either.

There's a comment in qmgr_message.c around line 522, which explains why
the queue name is showing up as the local user part:

    /*
     * Queues are identified by the transport name and by the next-hop
     * hostname. When the destination is local (no next hop), derive the
     * queue name from the recipient name. XXX Should split the address
     * on the recipient delimiter if one is defined, but doing a proper
     * job requires knowledge of local aliases. Yuck! I don't want to
     * duplicate delivery-agent specific knowledge in the queue manager.
     */

The above condition kicks in when the domain name is in mydestionation,
or is an ip address (in the form [1.2.3.4]) that matches one of our
local interfaces.

Which raises another question: we do this fiddle with the queue name
for mydestination locals, but not for transport local: deliveries. So -
is the fiddle necessary, is it being applied for local:, and I just
missed the code, or can we remove this behaviour?

 ---
Andrew McNamara (System Architect)

connect.com.au Pty Ltd
Lvl 3, 213 Miller St, North Sydney, NSW 2060, Australia
Phone: +61 2 9409 2117, Fax: +61 2 9409 2111

This archive was generated by hypermail 2b27 : Thu Jan 20 2000 - 23:13:53 CST