Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

400 4.4.7 message delayed

9 views
Skip to first unread message

Miha

unread,
Aug 13, 2009, 3:39:57 AM8/13/09
to
Hi

On Exchange 2007 we're dealing with the following problem: some of mail that
is send to external domains is not delivered. Sender gets the following
error: 400 4.4.7 message delayed.
But it's strange, because this happens only when sending mail to certain
domains, not all.
Any ideas what to look?
Regards,Miha

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4330 (20090812) __________

The message was checked by ESET NOD32 Antivirus.

http://www.eset.com


MeImNot

unread,
Aug 13, 2009, 5:51:01 AM8/13/09
to
Are you sure that u did not set up a send connector for those domains and
forgot to add the hub transport server , if not maybe u are being blacklisted
and your emails are being blocked, try this
http://www.mxtoolbox.com/blacklists.aspx

Miha

unread,
Aug 13, 2009, 8:48:57 AM8/13/09
to
No, it's configured right, also it's not on any black list.

"MeImNot" <MeI...@discussions.microsoft.com> wrote in message
news:EC8D1F3C-3E12-40A0...@microsoft.com...

> signature database 4331 (20090813) __________


>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4331 (20090813) __________

MeImNot

unread,
Aug 13, 2009, 10:20:01 AM8/13/09
to
Are the emails eventually received?

jamestechman

unread,
Aug 13, 2009, 10:47:40 AM8/13/09
to
The message delayed dsn can be caused by several reasons, your server
cannot contact their server for whatever reason or their server is
greylisting you "throttling" how much email\connections you can have
in a given period. Are you sending a large amount of emails to these
domains? You can also try telnetting directly their mail server and
send to postm...@theirdomain.com an email. Sometimes you will get a
more descriptive reason as to why you are being delayed.

Other reasons could be related to DNS verify that your Exchange server
is actually hitting their correct mx server. Get the MX ip for a
domain you're having issues from third party lookup then compare that
with your Exchange server's SMTP log to see if they match.

James Chong (MVP)
MCITP | EMA; MCSE | M+, S+
Security+, Project+, ITIL
msexchangetips.blogspot.com

Miha

unread,
Aug 14, 2009, 6:32:00 AM8/14/09
to
No, sender gets back report that the Exchange server will not try to deliver
messages any more... But this happens only to a few domains.
Sending from gmail works ok.

"MeImNot" <MeI...@discussions.microsoft.com> wrote in message
news:7F8C2107-648E-4FA7...@microsoft.com...
> signature database 4334 (20090814) __________

>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4334 (20090814) __________

Miha

unread,
Aug 14, 2009, 6:32:00 AM8/14/09
to
No, sender gets back report that the Exchange server will not try to deliver
messages any more... But this happens only to a few domains.
Sending from gmail works ok.
"MeImNot" <MeI...@discussions.microsoft.com> wrote in message
news:7F8C2107-648E-4FA7...@microsoft.com...
> signature database 4334 (20090814) __________

>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>

__________ Information from ESET NOD32 Antivirus, version of virus signature database 4334 (20090814) __________

0 new messages