What you need to do is use the registry method of setting up imsext.dll, as opposed to 
the field at the bottom of the IMS routing tab. Then, use the preferred method of 
stopping open relaying contained in that article, which is going into Routing 
Restrictions and checking Hosts and clients with these IP Addresses, but then not 
putting in any IP addresses. That's how we have it set up for both the imsext.dll, and 
for stopping relaying, and it works well.

-Peter


-----Original Message-----
From: Earl, Daniel [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 30, 2002 5:49
To: Exchange Discussions
Subject: IMSext / Mail Relaying


Hello list,

We use the IMSext.dll to add the disclaimer you see at the bottom of this
mail, but I am finding it difficult to find any clear information about how
to use it and not expose the mail server to relaying.

I have noticed that there are some odd failed delivery messages appearing
overnight in the admin mailbox for various domains.  These messages usually
contain something like this in the main body:
050048056046050053052046053055046050058078079084058049052054051054058049058 

There are a couple of good articles by Joseph Neubauer up on the
exchangeadmin.com website: "Is Your Exchange Server Relay-Secure?", "Using
the IMS Extension DLL" and "The Advantage Of Installing Imsext.dll Through
The Registry",  but nothing that tells me exactly how I can get the IMS to
give the '550 Relaying Prohibited' for all mail which doesn't match our
domain whilst still using the IMSext.dll which I don't think it currently
does - just 250 OK to any address.
I have searched Technet, Exchtool.chm from the BORK and this lists archives
but haven't been able to find anything.

It's Exch 5.5, Sp4, NT4SP6a.

I wondered if anyone on the list has managed to do this successfully?

Thanks as always for any ideas.

Dan.


This email and all attachments it may contain is confidential and intended
solely for the use of the individual to whom it is addressed. Any views or
opinions presented are solely those of the author and do not necessarily
represent those of Heal's. If you are not the intended recipient, be advised
that you have received this email in error and that any use, dissemination,
printing, forwarding or copying of this email is strictly prohibited.

Please contact the sender if you have received this email in error.



_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

______________________________________________
This message is private or privileged.  If you are not the
person for whom this message is intended, please delete it
and notify me immediately, and please do not copy or send
this message to anyone else. 



_________________________________________________________________
List posting FAQ:       http://www.swinc.com/resource/exch_faq.htm
Archives:               http://www.swynk.com/sitesearch/search.asp
To unsubscribe:         mailto:[EMAIL PROTECTED]
Exchange List admin:    [EMAIL PROTECTED]

Reply via email to