Discussion Locked

550 Relay Prohibited..

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
My Exchange 5.5 (SP4) is sitting on the same m/c as MS Proxy 2.0. It have 2 NICs, one Internal IP and one external IP respectively. Exch svr enabled "Reroute Incoming SMTP Mail" and Routing Restrictions for "Hosts and clients that successfully authenticated". Internal client could send and receive mails. However NOT for external client or host even though they has entered their account id and pw in their Outlook->Tools->Accounts->Server Tab->Incoming/Outgoing Mail Server. How could I enabled remote client or host relay mail and yet restrict unsolicited host or client from using exch svr for relaying mail.

8 replies

by techdictator

I think you have to enable POP3 for that server, unless you're planning on using IMAP. I think even though they're on the same server the proxy has to be configured to do reverse proxying for POP3 or IMAP connections. Depending what equipment you have upstream (firewall/router) You may have to configure it for NAT or PAT.

by techdictator

Are we talking about Outlook 98/2000/20002 clients accessing the email server or through OWA? Are they accessing it over the internet or through a RAS server?

by techdictator

After re-reading your question I had a thought. If you pull up the properties page for the Internet Mail Service in Exchange Administrator. On the Connections tab, what settings do you have?

by kc the can-do

The external client/host could receive but not send. When send, they receive "550 Relaying is prohibited..." error msg.
I have enabled reverse Web Proxying in the machine for external client to access Web Outlook. Are you saying enabling POP3 and IMAP4 in WinSock Proxying in MS PRoxy ?

by kc the can-do

The problem has been solved by disabling the ESMTP inspection in the CISCO firewall router.
ESMTP of cisco firewall disconnect all ESMTP connect when Outlook try sending mail. Probably MS Outlook use ESMTP for authentication. So sending is always fail from office LAN protected by cisco firewall. It was realized when sending is ok by dial-up to ISP and confirm the problem.

This discussion is closed to new replies.