The e-mail system was unable to deliver the message... but only on certain addresses.

A user is complaining that she cannot send email to a few people.  I have noticed that the two email addresses we are having problems sending to are using Juno and Netzero. (not sure if that makes a difference)

We host our own Exchange 2003 server on our network, and can send and receive email to and from various accounts.  (both internal and external)

There are only a few people having this issue, and we have tried sending email to this user from various internal addresses on the same Exchange server, and from a gmail account.  Only the email sent from gmail was received by the address that is causing us trouble.

The complete error message is:

"The following recipient(s) could not be reached:

      *****@juno.com on 3/28/2007 2:54 PM
            The e-mail system was unable to deliver the message, but did not report a specific reason.  Check the address and try again.  If it still fails, contact your system administrator.
            < ****.*****.org #4.0.0 X-Spam-Firewall; connect to mx.nyc.untd.com[64.136.20.83]:    server refused mail service>"

Exchange 2003 running on Windows Server 2003 SP2 Standard
LVL 1
OneSeventeenAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SembeeCommented:
The server is refusing your message.
Put your domain in to dnsreport.com and see if it flags any errors.

Simon.
0
OneSeventeenAuthor Commented:
the two mail issues are:

1: Fail: Connect to mail servers
"mail servers      ERROR: I could not complete a connection to one or more of your mailservers:
mail.calvaryabq.org: The mailserver terminated the connection before the transaction was complete (state 1). This is not RFC compliant, and therefore either due to an error, or it may be the result of a non-RFC-compliant mailserver or non-RFC-compliant anti-spam program."

And:

2: Warn: SPF Record
"Your domain does not have an SPF record. This means that spammers can easily send out E-mail that looks like it came from your domain, which can make your domain look bad (if the recipient thinks you really sent it), and can cost you money (when people complain to you, rather than the spammer). You may want to add an SPF record ASAP, as 01 Oct 2004 was the target date for domains to have SPF records in place (Hotmail, for example, started checking SPF records on 01 Oct 2004)."

Could either of these be the culprit?
0
SembeeCommented:
SPF record not too bothered about.

The first error is classic firewall interference. You also have two MX records - the one that is working doesn't look like it is an Exchange server answering. Does your email come in through a different server?

Simon.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

OneSeventeenAuthor Commented:
The email all comes in through a spam firewall first.
0
SembeeCommented:
In that case you need to look at the firewall configuration. If the firewall is misbehaving with inbound connections then you will be unable to email certain ISPs and other large email sites because it will fail their antispam techniques.

Simon.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
OneSeventeenAuthor Commented:
Apparently it is intentional to have the spam firewall be the only mail server that responds to requests.  The problem was with the spam firewall.  (We just resolved the issue 2 days ago)

Our spam firewall blocks mail servers that send large quantities of mail in a short period of time... including our internal one.  When a department decided to send out a mass email to the outside world our spam firewall marked us as spam and blocked us from sending mail.  We have whitelisted our sever and will be monitoring it for abuse.

Thanks for the troubleshooting tips though.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.