• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 488
  • Last Modified:

Exchange Reputation

Exchange Server 2003:

I have a dedicated server at a data center that I terminal services into.  I recently installed Exchange Server 2003 Standard from my licensing.  When the hosting company setup the server the name of the server was "sls-ce10p12" and they had a DNS Suffix of sls-ce10p12.dca2.superb.net

Well, in doing other things I found this out but AFTER the fact that I promoted this server to a DC to run my Exchange.

I removed the DNS Suffix but the outside is still seeing me at sls-ce10p12.dca2.superb.net and appliances like Barracuda are rejecting me like so.  How can I fix this?

There was a SMTP communication problem with the recipient's email server.  Please contact your system administrator.
    <sls-ce10p12.dca2.superb.net #5.5.0 smtp;554 Service unavailable; Client host [sls-ce10p12.dca2.superb.net] blocked using Barracuda Reputation; http://www.barracudanetworks.com/reputation/?r=1&ip=66.36.240.70>
0
chrisryhal
Asked:
chrisryhal
1 Solution
 
MesthaCommented:
Properties of the SMTP virtual server in ESM.
ESM, Servers, <your server>, Protocols, SMTP. Right click on the Default SMTP VS and choose Properties, then Delivery, then Advanced. Change the FQDN field. Apply/Ok out.

Although that will not get you off the Barracuda list, you will need to apply to them directly to get off that.

Simon.
0
 
chrisryhalAuthor Commented:
Awesome.  Changed and confirmed Header based on a test email.  Worked out GREAT!!!  
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now