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: LaMont Jones (lamontsecurity.hp.com)
Date: Thu Jan 20 2000 - 22:43:14 CST

> What I was hoping to be able to do is put the local hostname in
> mydestination, and use the transports table to forward the rest to the
> local server. I.e., with local machine melang.off.connect.com.au,
> mydestination = melang.off.connect.com.au
> transport:
> connect.com.au smtp:[wawura.off.connect.com.au]
> .connect.com.au smtp:[wawura.off.connect.com.au]

> Putting "melang.off.connect.com.au local:" in transports fixes things,
> but I was hoping to share the transports file between multiple
> machines. I realise this is sort of a "doctor, it hurts when I do
> this... well don't do that then" situation, but I'd still like to
> understand what's happening inside qmgr to cause this (I've been pawing
> through the code without reaching enlightment so far).

Per the release notes, the transport map overrides mydestination.

> 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.

> What I'd *really* like to do is have a standard config that I put on
> all the desktop client machines without having to make changes from
> machine to machine.

You could use the prog map for a transport map, and have the program
return 'local:' when the key is equal to the hostname, and nothing
when it's not... Whatever you figure out, I'm curious as well, although
my situation is the reverse of yours.

lamont

This archive was generated by hypermail 2b27 : Thu Jan 20 2000 - 22:45:55 CST