Mail problems - 554 mail server permanently rejected message

[Deanvz]

I have repeatedly found this error with our mail server. (Some background info, mediocre IT knowledge still busy learning) I need some help with this problem:

[email protected]<mailto:[email protected]>
An error occurred while trying to deliver this message to the recipient's e-mail address. Microsoft Exchange will not try to redeliver this message for you. Please try resending this message, or provide the following diagnostic text to your system administrator.

The following organization rejected your message: mail.ourmailserver.net.

Generating server: bigfish.com

[email protected]<mailto:[email protected]>
mail.ourmailserver.net #<mail.ourmailserver.net #5.0.0 smtp;554 mail server permanently rejected message> #SMTP#

[email protected]<mailto:[email protected]>
mail.mailserver.net #<mail.ourmailserver.net #5.0.0 smtp;(10.9.99.132) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 21 Mar
2012 08:30:05 +0000
Received: from NASLSWAMG040.na.domainx.com ([10.21.35.46]) by
NASLSWAMS052.na.domainx.com ([10.21.29.11]) with mapi; Wed, 21 Mar 2012
04:30:07 -0400
F
Date: Wed, 21 Mar 2012 04:30:06 -0400
Subject: WG: {Disarmed} PRE ALERT: Decotrade AG ex userdomain - Approval of
sample o.ref. 59-23365 / 395-11633 - Booking Ref - 863644237
Thread-Topic: {Disarmed} PRE ALERT: Decotrade AG ex userdomain - Approval of
sample o.ref. 59-23365 / 395-11633 - Booking Ref - 863644237
Thread-Index: Ac0GqGaBuLuN5EZnTjWP6WCs/DQIEAAk5magAAAxTzA=
Message-ID: <E092440E9321E744A62E4279E8E957F20194E5982(10.9.99.132) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 21 Mar
2012 08:30:05 +0000
Received: from NASLSWAMG040.na.domainx.com ([10.21.35.46]) by
NASLSWAMS052.na.domainx.com ([10.21.29.11]) with mapi; Wed, 21 Mar 2012
04:30:07 -0400

Date: Wed, 21 Mar 2012 04:30:06 -0400
Subject: WG: {Disarmed} PRE ALERT: Decotrade AG ex userdomain - Approval of
sample o.ref. 59-23365 / 395-11633 - Booking Ref - 863644237
Thread-Topic: {Disarmed} PRE ALERT: Decotrade AG ex userdomain - Approval of
sample o.ref. 59-23365 / 395-11633 - Booking Ref - 863644237
Thread-Index: Ac0GqGaBuLuN5EZnTjWP6WCs/DQIEAAk5magAAAxTzA=
Message-ID: <E092440E9321E744A62E4279E8E957F20194E5982C16@NASLSWAMG040.na.domainx.com<mailto:E092440E9321E744A62E4279E8E957F20194E5982C16@NASLSWAMG040.na.domainx.com>>

Return-Path:
X-OriginatorOrg: domainx.com
[email protected]<mailto:E092440E9321E744A62E4279E8E957F20194E5982C16@NASLSWAMG040.na.domainx.com>>

Return-Path: [email protected]<mailto:[email protected]>
X-OriginatorOrg: domainx.com
554 mail server permanently rejected message> #SMTP#

[email protected]<mailto:[email protected]>
mail.ourmailserver.net #<mail.ourmailserver.net #5.0.0 smtp;554 mail server permanently rejected message> #SMTP#

Original message headers:

Received: from mail83-tx2-R.bigfish.com (10.9.14.238) by
TX2EHSOBE007.bigfish.com (10.9.40.27) with Microsoft SMTP Server id
14.1.225.23; Wed, 21 Mar 2012 08:30:08 +0000(10.9.99.132) with Microsoft SMTP Server (TLS) id 14.1.225.23; Wed, 21 Mar
2012 08:30:05 +0000
Received: from NASLSWAMG040.na.domainx.com ([10.21.35.46]) by
NASLSWAMS052.na.domainx.com ([10.21.29.11]) with mapi; Wed, 21 Mar 2012

Date: Wed, 21 Mar 2012 04:30:06 -0400
Subject: WG: {Disarmed} PRE ALERT: Decotrade AG ex userdomain - Approval of
sample o.ref. 59-23365 / 395-11633 - Booking Ref - 863644237
Thread-Topic: {Disarmed} PRE ALERT: Decotrade AG ex userdomain - Approval of
sample o.ref. 59-23365 / 395-11633 - Booking Ref - 863644237
Thread-Index: Ac0GqGaBuLuN5EZnTjWP6WCs/DQIEAAk5magAAAxTzA=
Message-ID: <E092440E9321E744A62E4279E8E957F20194E5982C16@NASLSWAMG040.na.domainx.com<mailto:E092440E9321E744A62E4279E8E957F20194E5982C16@NASLSWAMG040.na.domainx.com>>
S
x-exclaimer-md-config: c5a3f742-9dc9-4dd9-9539-5e407d231d79
Content-Type: multipart/alternative;
boundary="_000_E092440E9321E744A62E4279E8E957F20194E5982C16NASLSWAMG04_"
MIME-Version: 1.0
Return-Path: [email protected]
X-OriginatorOrg: domainx.com

I have read and found that most of these types of problems were caused by DrWeb, we do not have DrWeb on our server. It doesnt even seem like our mail server is being contacted as there are none of our IP's present.

Some help and input in this regard would be greatly appreciated

 

[Jeff Knapp]

I had the same issue. The greylising service has an over-riding blacklist of:

*[0-9][0-9]-[0-9][0-9]-[0-9][0-9]*
*[0-9][0-9].[0-9][0-9].[0-9][0-9]*
*[0-9][0-9][0-9]-[0-9][0-9][0-9]-[0-9][0-9][0-9]*
*[0-9][0-9][0-9].[0-9][0-9][0-9].[0-9[0-9]][0-9]*
dsl|pool|broadband|hsd
dynamic|static|ppp|dyn-ip|dial-up


Microsoft, in their infinite wisdom, has included the word pool in their exchange relay. If you watch your mail queue in real time, you will see something like: db3outboundpool.messaging.microsoft.com whenever there is inbound exchange messages.

The fix I found (and works for me) is:

# /usr/local/psa/bin/grey_listing --update-server -domains-whitelist "add:*messaging.microsoft.com"

I am able to leave greylisting and all other spam/virus protection enabled and receive any exchange mail.

Hope it helps you. Go Microsoft (sarcasm implied)

Jeff

PS - From what I understand, you may have to apply this command every time you upgrade Plesk

 

[Deanvz]

Jeff thank you very much! Absolutely genius. This seemed to have sorted out the problem.

Yeah Go Mircargetwh

 

[IgorG]

http://kb.parallels.com/en/113722

 

[abdi]

Thanks alot, I hope this resolves the many complaints I get everyday too ..

 

[Knarf]

Jeff thanks!

Today I had the same issue with one of my clients, shortly after I enabled greylisting. Mail from server bigfish.com rejected with message:
#5.0.0 smtp;554 mail server permanently rejected message
Your solution solved the problem immediately.

 

[VivekK]

You are a Jem!!!

Its working with your suggestion...

I was not able to find and fix this problem from long time, and today i found your forum which solved the problem immediately...

You are great!!!