Link to home
Start Free TrialLog in
Avatar of ToddSWagner
ToddSWagner

asked on

The message cannot be delivered due to a configuration error on the server. Please contact your Administrator.

I am perplexed at this error message when someone tries to send a email to our Exchange server.  1/4 of their employee's can send email and the other 3 get this bounce back.  ORDB has not been around since 2006.  DNS and RDNS is setup correctly on the receiving side and the wspharr domain is the only domain that is having a problem.  I am running Groupshield 6.0.1 with a Sonicwall firewall.  I can telnet through to the Exchange server through port 25.  If someone has seen this, please let me know.              

The message cannot be delivered due to a configuration error on the server. Please contact your Administrator.
            <mail.wspharr.com #5.3.0 smtp;553 5.3.0 Spam blocked see: http://ordb.org/lookup/?host=65.88.93.130>
Avatar of kieran_b
kieran_b
Flag of Australia image

>>DNS and RDNS is setup correctly on the receiving side and the wspharr domain is the only domain that is having a problem.

You are the receiver and they are wspharr.com?  That error is your server bouncing to them?

'cause they don't have a reverse DNS entry, so you could check and see if that is why Groupshield is rejecting them - that isn't an Exchange error, so there is something else at work here.

Kieran
Avatar of ToddSWagner
ToddSWagner

ASKER

WSPharr is the client domain trying to send to my domain.  Their server is producing the bounce back because it states their mail server name.  I am the receiving domain.  I am stumped on this one because I cannot find anything on the internet for a solution.  Their IT person said that I should turn off Groupshield for a week to see if that helps.  Would any sane person turn the anti-virus and spam filter off for a week?   I know Groupshield doesn't use RBL, but webshield does.  We are not using webshield, so I am trying to figure out what is causing the NDR with the ORDG.org list.
>>Their server is producing the bounce back because it states their mail server name.

Not always, that is just the last server to touch it - if my server rejects your server instantly because of your IP, your server will notify you.  So yes, their server is producing the error, but that isn't to say it has nothing to do with your server...

>>Their IT person said that I should turn off Groupshield for a week to see if that helps.

AHAHAHAHAHAHA, I would politely point out that people who don't know how to configure a simple PTR record are in no position to recommend anything to anyone :)

Is groupshield doing any kind of PTR lookups?
I would need to check the config to see if it is looking at RDNS. Why would his server throw up an error message that refers to ordb.org.
>>Why would his server throw up an error message that refers to ordb.org.

All I know is that it isn't an Exchange error - I can't see how it is his server, as that would affect ALL outbound mail.  Do you have a backup MX record at all?  Perhaps your backup MX record is pointing to an outdated mailserver?

>>1/4 of their employee's can send email and the other 3 get this bounce back.

Is it always 3 users who get a bounce?  Can you ensure they are manually typing out the whole address?  What access do you have to the sending server?
Our MX, Public DNS and RDNS are correct.  That is the first thing I checked.  I only have 1 MX record as well.  I only have 1 mail server.  It is the same 3 who get the bounce and 1 person can send and get emails through.  I don't have any access to the sending server.  Their domain is the only domain with sending issues.
If 1 person can send, and three can't, then it is going to be something at their end - I mean, if one gets through, it works, right?

As the recipient, it is mighty hard to troubleshoot - you need to see the message tracking logs on the sending server to find out what happened, which you don't have access to.
I am going to upgrade McAfee Groupshield next week to appease their IT person.  
Here is what you will have to do. Remove  ordb.org from your filter on your exchange server

One your Exchange Server Manage go to your message Delivery and select properties.
I checked my settings on the Exchange server and they are all correct. Nothing on my side points to that domain for spam.  I also went through and checked other settings again and everything looks ok.

Their IT consultant was nice enough to open up relay on my exchange server when he went through it.  I am sure this guyis a real asset to the company that he supports, especially if he would advise them  to turn off spam and virus filtering for a week and to open up relaying on an Exchange server.  I put the settings back and I asked the person to try and send another email to test.  
Outstanding, thid guy is my new hero
Solution is/was?
ASKER CERTIFIED SOLUTION
Avatar of ToddSWagner
ToddSWagner

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial