SMTP Transmission Failure has occurred - Diagnostic code: smtp;550 5.7.1

Windows Server 2k, SP1, Exch Svr 2003, SP2:

I have one external user from a partticular domain who receives this error when he tries to email us.  Gere's the full monte...

Your message cannot be delivered to the following recipients:

 Recipient address: creynolds@ourdomainname.org
 Reason: SMTP transmission failure has occurred
 Diagnostic code: smtp;550 5.7.1 Requested action not taken: message
refused
 Remote system: dns;mail.ourdomain.org

(TCP|206.46.252.44|24414|ouroutsideip|25)

 Recipient address: LTWAdmin@ourdomain.org
 Reason: SMTP transmission failure has occurred
 Diagnostic code: smtp;550 5.7.1 Requested action not taken: message
refused
 Remote system: dns;mail.ourdomain.org

(TCP|206.46.252.44|24414|ouroutsideip|25)




Original-recipient: rfc822;creynolds@ourdomain.org
Final-recipient: rfc822;creynolds@ourdomain.org
Action: failed
Status: 5.7.1 (SMTP transmission failure has occurred)
Remote-MTA: dns;mail.ourdomain.org (TCP|206.46.252.44|24414|ouroutsideip|25)
Diagnostic-code: smtp;550 5.7.1 Requested action not taken: message refused

Original-recipient: rfc822;ltwAdmin@ourdomain.org
Final-recipient: rfc822;ltwadmin@ourdomain.org
Action: failed
Status: 5.7.1 (SMTP transmission failure has occurred)
Remote-MTA: dns;mail.ourdomain.org (TCP|206.46.252.44|24414|ouroutsideip|25)
Diagnostic-code: smtp;550 5.7.1 Requested action not taken: message refused
LTWadminAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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:
What else is on the machine?
Any filtering applied to the Exchange server to block this user's domain?

Simon.

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
LTWadminAuthor Commented:
Symantec Mail Security for Exchange, Symantec AV Corporate Edition Client (for 2003 Server), Symantec Anti-SPAM.  Would the filtering you're referring to be located in the SMTP connector, General Tab/Advanced by any chance?  (That may be totally off...),  Thanks.
SembeeCommented:
Oh dear. You are using the Symantec products.

Sender filtering is in ESM, Global Settings, Message Delivery on the Sender Filtering tab.

However, based on previous experience I would expect the problem is caused by your Symantec products. If they are installed on an Exchange server then they would be the first and the only place I would look as the cause of any problems. Unfortunately due to the way that they integrate with Exchange, the only way to test that they are the cause is to remove them totally (which actually isn't just the case with Symantec AV - any Exchange based AV has to be removed as they use the AV API). Disabling them isn't enough as the application still scans the message, it just doesn't do anything about it.

Simon.
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

LTWadminAuthor Commented:
Simon -

Thanks.  I seem to have no Sender or Recipient filters in place in Message Delivery properties...

I must admit hearing an Anti-Symantec wail from someone at your expertise level is somewhat.. unsettling?...and I totally respect your opinion.  However, I am happy to announce that this server (WITHit's suite of Symantec products) has been running happily along for nearly two years now - without much intervention or maintenance I might hesitate to say (all true -all tongue in cheek).

Yes - I don't think I will be uninistalling the Symantec suite (withdrawing my Bradleys, tanks, barbed wire and claymors) to see if this one little guy from this one little domain can then send us email but I will comb back through it on your suggestion.  

SembeeCommented:
My opinion of Symantec products is not something that I hide. Search this forum and you will find that I have been very consistent with that approach. I have seen too many server with problems that are fixed by removing Symantec's bloatware. The amount of resources that their AV takes is just mind boggling. And you can guarantee that when there is a major outbreak of a virus you cannot get updates from their server because it is overloaded. It also happens to be one of the most expensive AV applications on the market as well.

I almost cried when I found out they were buying Veritas - Backup Exec was my favourite backup application. It doesn't look like they have ruined it too much - yet.

Hence, based on experience, if there are any Symantec products the first thing that has to be done is that they are removed. Your server will behave a lot better without it.

Simon.
LTWadminAuthor Commented:
Points awarded for 1st respnder and good avice only.  The problem went away on it's own for the moment...  
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.