Conference chefs::ms-exchange

Geoff,

   If I understand your question, yes, you should be able to change the SMTP
Site Addressing (found under Configuration, Site Addressing, Site Addressing
Tab) to change the SMTP address for ALL recipients on the server to "@ali".

But, assuming that this Exchange server might be connected to the Internet or
and intranet, you probably need to add SMTP aliases.  The out-of-the-box defaults
for most UNIX sendmail configurations like to strip the domain name off of the
host name when making a local host (one that is in the same domain).  I have
this problem at my customer site where the Reply TO: address is
[email protected].  If a user on a UNIX host in the same domain sends mail to
this address, the hosts's rewriting rules change the address to username@host
and sends it off to Exchange which rejects it since its not equal to
[email protected].  The way to solve this problem is either change the
rewriting rules on every UNIX box in the domain (yuck!) or tell Exchange that
the user has an alias address of username@host. 

Whether this is your problem or not, the following Knowledge Base articles have 
information regarding SMTP addressing and Exchange:

http://www.microsoft.com/kb/articles/q148/9/85.htm
http://www.microsoft.com/kb/articles/q153/2/70.htm

Regards,

Dave

Sorry I was a little short on details in my base note. I entered the note just
as I was walking out the door to go home.

The customer currently address's mail to user@COMPANY1 or user@COMPANY2.
In realility mail addressed to both domains will go to the same mailhub. 
The mailhub then distributes the mail to the required company based
on the domain specified in the To: field. All simply and straightforward.

eg. geoff on node WS1 in mail domain COMPANY1 wants to send mail to 
kienny@COMPANY2. The sendmail file on WS1 is configured to send mail to 
MAILHUB.LOC.COM (the mailhub gateway). The MAILHUB.LOC.COM forwards mail
based on the destination (To:) DOMAINNAME which in this case is COMPANY1.

COMPANY1 is just as written and contains no periods "."

Now with Exchange, users would like to continue to address mail to
"user@COMPANYx". Unfortunately for exchange to recognize this as an SMTP
address it expects the domainname to contain at least one period "."

I have configured the Internet Mail Connector, Connections, E-Mail Domain
to forward the domain COMPANY1 and COMPANY 2 to the same mailhub.
If at the To: prompt I specifically tell exchange that this is an SMTP mail
[SMTP:user@COMPANYx] then it works fine. Furthermore if I add an SMTP user to
my address book it also works fine. 

What I really need is for Exchange to automatically recognize user@COMPANYx 
as an SMTP address even though the domainname does not contain a period "."

Any ideas?

Thanks,
Geoff.. 

Geoff,

  I see what you mean.  The Exchange client appears not to accept SMTP
addresses without the period.  However, I was able to create a Custom Recipient 
with the SMTP address of just USER@DOMAIN (no period).  I selected the 
recipient's name at the TO: prompt and sent the message successfully.  This
might be your only workaround until (unless) you can get Microsoft to change
this "feature" on the client. 

Knowledge Base article Q156997 describes some of the interaction between the IMC
and DNS when an Internet address is null.  This might give you some ideas.  It 
looks like to me that need to populate the Exchange directory with Custom
Recipients for everyone not on Exchange.  You were going to do this 
anyway, correct?

Regards,

Dave 

Dave,
    Thanks for the reply. Yes, I knew that I could add a custom recipient
however its not feasible to do this for every user. I was hoping that I'd
missed something - maybe not. How do you submit feature requests to Microsoft?


Thanks,
Geoff..

Geoff,

  No, I don't think you've missed anything.  This dysfunction appears to be by 
design.  I'm not sure how one goes about submitting product suggestions.  Maybe 
someone else monitoring this notesfile can provide some input?

Regards,

Dave