HIB - 400 4.4.7 Message Delayed

Identity: ABCMAIL\17784\420993
Subject: Liability
Internet Message ID: <722870AAA4AD584F82D99BA37C6AFDCA4D755B47C8@zibmail>
From Address: sender@senderemail.com
Status: Ready
Size (KB): 50
Message Source Name: FromLocal
Source IP: 255.255.255.255
SCL: -1
Date Received: 09-Sep-2015 2:02:24 PM
Expiration Time: 11-Sep-2015 2:02:24 PM
Last Error: 400 4.4.7 Message delayed
Queue ID: ZIBMAIL\17784
Recipients:  recipient@recipient.com

Why is this message delayed?

I went to Queue Viewer, I have 26 messages delayed
LVL 1
Anonymous KHIT EngineerAsked:
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.

Mal OsborneAlpha GeekCommented:
Sounds like someone you are sending too has implemented Greylisting. This is an antispam mechanism.  When the server sees a new email (new IP, new sender), it responds with a  temporary failure. After a while, (typically a few hours) it will accept the email, and from then on not delay it.

Spammers usually do  not retry sending mail, but "real" mail servers do. Give it a day or so and see if your queues clear.

More here:
https://en.wikipedia.org/wiki/Greylisting

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
Amit KumarCommented:
It happens sometime when recipient's SMTP server is not reachable so message is also get delayed.

Obviously there is a default limit to message get expired by queued transport server "Expiration Time: 11-Sep-2015 2:02:24 PM" so if that message will not be delivered then it will be failed.

for more troubleshooting you can try one thing. check MX record of recipient's domain and try telnet on 25 port and check if it accepts your EHLO packet. if not then issue is clear your transport server is not able to connect it.
Anonymous KHIT EngineerAuthor Commented:
My boss did something and all the emails were sent in one shot, any idea what was done to send out all the "stuck" emails?
Amit KumarCommented:
not sure there are many things to do

suspend and retry queue
checked connectivity which I suggested to you
or may be something else
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.