IT Employment

Ask something
Discussion Locked

Exchange SMTP error

0 helpful
4 replies

by rjackson

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am having a problem with SMTP (I believe).
My exchange server only receives about every third email sent to it from the outside world. It was working fine but we just recently switched ISP's and we are now using QWEST. QWEST is telling me that I need to set SMTP up to authenticate with them using the login they provided. I believe I have this done correctly but it didn?t seem to help.
My Exchange Server is version 5.5 with latest SP?s. Below is the error that the sender receives when it fails.

Hi. This is the qmail-send program at mpls-qmqp-03.inet.qwest.net.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

:
63.231.195.101 does not like recipient.
Remote host said: 553 relaying denied.
Giving up on 63.231.195.101.

4 replies

by lordinfidel

If you have set up your own exchange server and you have a static IP,

You should not have to relay anything thru qwest.

If they are in control of your DNS zone, have them point the MX record to your mail server. Have your mail server send outthe e-mail itself. It does not have to relay e-mail thru the qwest servers.

by jellimonsta

You have probably found that you are receiving some messages due to their being an MX record entry for your server. You want your ISP to make sure your Internal Email server has the lowest cost. Some ISP's do not retry to a higher costing MX entry and therefore they will permanantly fail if your main (lowest cost) MX record is incorrect.

by rjackson

I told them I have my own Exchange server and I needed them to point the MX record to my exchange server. Are you saying that the error looks like I am relaying through their SMTP server?

by slacker

However... You might also check with whoever might be hosting your domain if you have a website. Sometimes this can cause a mix up as well. Make sure both locations have the MX record for your Exchange server correctly pointed to your IP.

This discussion is closed to new replies.