mydestination questions...

Subject: mydestination questions...
From: Andrew McNamara (andrewmconnect.com.au)
Date: Thu Jan 20 2000 - 22:26:30 CST

• Next message: Andrew McNamara: "Re: Port of sendmail SUNET_ID_HASH fn for LDAP map?"
• Previous message: Jason Hoos: "Re: Port of sendmail SUNET_ID_HASH fn for LDAP map?"
• Next in thread: LaMont Jones: "Re: mydestination questions..."
• Reply: LaMont Jones: "Re: mydestination questions..."
• Reply: Liviu Daia: "Re: mydestination questions..."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I'm trying to set things up so that desktop machines forward mail for
*.connect.com.au addresses to their local mail server (which knows how
to route local users), but perform direct smtp delivery for all other
address, and local delivery for their own address.

This was working prior to the lastest snapshots, but the changes in the
way mydestination is handled have caused things to brake in strange
ways.

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]

Somehow, this confuses qmgr, and it strips off the domain part and
passes the user part to the selected transport as the next hop. So, if
I tried to send mail to andrewmconnect.com.au, smtp would attempt to
connect to andrewm (queue->name == "andrewm", when it should be
"connect.com.au" in qmgr).

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

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?

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.

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

• Next message: Andrew McNamara: "Re: Port of sendmail SUNET_ID_HASH fn for LDAP map?"
• Previous message: Jason Hoos: "Re: Port of sendmail SUNET_ID_HASH fn for LDAP map?"
• Next in thread: LaMont Jones: "Re: mydestination questions..."
• Reply: LaMont Jones: "Re: mydestination questions..."
• Reply: Liviu Daia: "Re: mydestination questions..."
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

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