Relaying Denied for Remote Users

[ramsvasanth]

I have a remote user who uses POP/SMTP with my exchange 2000 mail server. When he sends a message to any external domain, he gets a 550 5.7.1 Relaying Denied message. I have thoroughly checked up the Default Virtual Server configurations and it has a closed relay with the "Allow all computers which authenticate....." option enabled. There is no SMTP connector also. Can some help me to sort out this issue ?

 

[EdwinSKH]

Probably, for the user's mail program eg. Outlook Express, he needs to set the authentication. For OE, Open Tools->Accounts->Mail, and select the mail server properties. Under Server tab, select My Server requires authentication, and specify accordingly

 

[MichaelDay]

I think I have the same problem here. I got this error Code: #5.5.0 smtp;550

Even though my user did try this:"Under Server tab, select My Server requires authentication, and specify accordingly"
It still reject my user email from foreign host. No idea why

 

[ramsvasanth]

I have tried setting up authentication for outgoing mails in Outlook. The option "Log on to incoming server before sending mail" in the Outgoing Server tab is also selected. Still the same result. When I have a open relay (i.e) "All except the list below" radio button checked in Relay settings of the Default SMTP Virtual Server, the remote user is allowed relay. But open relay is causing lot of messages to be queued in the server and has also resulted in my domain getting blacklisted. How to accomplish a closed relay and still allow relay access for remote users.

The "Log on to incoming server before...." option is slightly ambiguous. I interpreted it in a different way like fetching the mails first and then sending a mail (i.e) using POP3 before SMTP. I tried this but still relaying was denied with closed relay settings.

Any guidance is appreciated.

 

[enigma174]

Personally i find the best option is to set their SMTP server to that of the ISP who they are connecting through.
This can be a bit of a pain if they are moving in and out of the office, but usually they are either allways out of the office, or accept having to come into the office (or VPN) to check their email.

 

[javatizer]

Hi,
I have almost a similar problem, I have my mail server CommuniGate behind a firewall that intercepts every incoming SMTP session, and act on behalf of the mail server, the FW MTA is SendMail, and its configured that if the mail is for local domain to forward it to the local mail server(s), if not it will send it outside to its destination.
All works fine for local users on the LAN, since the FW is treating LAN IP as trusted IPs, but the problem is when remote users try to send email, they cant, and enabling domain relay check and the reply to is not secure enough.
I have SMTP authentication enabled on CommuniGate and tested OK form inside the LAN, but when remote/mobile users try that they are actualy talking to the FW and not CommuniGate, which does not work.


Thanks in advance...
Javatizer

 

[ramsvasanth]

Hi Everyone,

The best option that I found out was to ask the remote user to use the SMTP server of the ISP that he is connecting to (as suggested by enigma174 user and thanks to him). This sounds a logical solution also because, to the ISP, the remote client has an IP assigned dynamically for which relay would be allowed for sure, because it is like a local segment for ISP.

This option worked yesterday and hope it continues to.

Thanks everyone for your suggestions.

 

[Hospodka2004]

This option will work fine of course but what if the user is outside of the UK? they cannot use some ISP dial up no.s due to the blocking by ISPs of dial ups from countries outside UK.

Only option then is to use different accounts in different coutries. Not cool.