Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win


Exchange 2003 SMTP communication problem

Posted on 2007-12-06
Medium Priority
Last Modified: 2010-04-21
I have a end user that is trying to email cplazola and we get this error message:
cplazola@terralindaservices.com on 12/6/2007 12:36 PM
            There was a SMTP communication problem with the recipient's email server.  Please contact your system administrator.
            <mail1.web4it.net #5.5.0 smtp;550-JunkMail rejected - 71-6-5-2.static-ip.telepacific.net (mail1.web4it.net)>

Is there a problem with my email server?  
Question by:Bulls-Eye
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3

Accepted Solution

notfuzzi earned 1000 total points
ID: 20423451
Looks to me like it was blocked as spam.  There are several reasons this may happen.  The first is that particular email may have looked like spam.  The more likely reason is that your domain is on a domain blacklist of some sort.  You can check for blacklisting at
Let us know the domain you are sending from and we'll try to help.

Author Comment

ID: 20423610
I purchase symantec Enterprise for my mail exchange server, I also have the spam premium installed.
I'm not sure why this is happening.  I did go to the link above and got this from spamcop.  I can dlist it but I want to make sure the server is OK.  Is it just a network problem with my ISP? listed in bl.spamcop.net (

If there are no reports of ongoing objectionable email from this system it will be delisted automatically in a short time.

Causes of listing
SpamCop users have reported system as a source of spam less than 10 times in the past week
Automatic delisting
If you are the administrator of 71-6-5-2.static-ip.telepacific.net. and you are sure it will not be the subject of any more reports of spam, you may cause the system to be delisted without waiting for us to review the issue.
You may only do this once per IP! So please be sure that the problem is really and truly resolved. If you delist your system and we get more spam reports about it, you will not be allowed to expedite delisting again. Delisting normally occurs 24 hours after spam reports have ceased.

You must be able to receive mail at one of the addresses below. Until you have received and confirmed your request, it will not take effect.

Looking for potential administrative email addresses for

Cannot find an MX for 71-6-5-2.static-ip.telepacific.net
Cannot find an MX for static-ip.telepacific.net is an MX ( 40 ) for telepacific.net
abuse@telepacific.net bounces (41 sent : 35 bounces)


Expert Comment

ID: 20423672
The way Spamcop works is that people report your domain as spam.  Either someone got into your Exchange server and sent out spam, or you just got reported a few times.  Check to make sure your Exchange server isn't set as an open relay, and secure as it can be, and then request it to be delisted.  Here is some information on checking to see if your Exchange server is an open relay:


The above link is for Small Business server, but the Open Relay works for Exchange 2003 (any version)  
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.


Author Comment

ID: 20424137
Thanks for the link.  I did check my email server and it is not relaying.  I am running symantec enterprise for exchange and corporate for the server.  All seems OK with  the server.  I staff person a few days ago brought over a heavily infected notebook.  Since my server and notebook are behind a firewall running NAT.  Well it looks like that system was acting as my email server.  I'm checking everything out and I'm going to request a delist of my server.  Ouch!

Author Closing Comment

ID: 31413309
thanks so much.  I found a DNS issue with my ISP where they needed to do a reverse DNS to my email servers.  Once I did that the blacklist started to clear up.  All is working.  I checked my systems for viruses and also the exchange data.  I also verified that my email server is not relaying.  All is well.  Thanks,

Expert Comment

ID: 20425161
Good luck!  They usually go through decently quick.  Update us on the status.

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Are you an Exchange administrator employed with an organization? And, have you encountered a corrupt Exchange database due to which you are not able to open its EDB file. This article will explain all the steps to repair corrupt Exchange database.
On September 18, Experts Exchange launched the first installment of the Help Bell, a new feature for Premium Members, Team Accounts, and Qualified Experts. The Help Bell will serve as an additional tool to help teams increase question visibility.
In this video we show how to create a Shared Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >> Sha…
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

604 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question