Cannot send mail to hotmail?

Andreas westvik <[email protected]>
Newsgroups gmane.mail.exim.vexim.devel,gmane.spam.detected
Message-ID <[email protected]>
This is probably not suited for vexim list, not sure. But I will try 
anyways.
I was going through the inbox for a [email protected] earlier 
today I a noticed a lot of "failed" warnings. All of the came from mail 
that was sent to users at hotmail.

And this is what I got:

"A message that you sent could not be delivered to one or more of its 
recipients. This is a permanent error. The following address(es) failed: 
[email protected]  retry timeout exceeded"

"X-Spam-Score: -1.4 (-) X-Spam-Report: Spam detection software, running 
on the system "server.net", has identified this incoming email as 
possible spam. The original message has been attached to this so you can 
view it (if it isn't spam) or label similar future email. If you have 
any questions, see the administrator of that system for details."

So I thought had to do with clamav/spamd. But I turned that service off 
and then I got this:

"This message was created automatically by mail delivery software.
 A message that you sent could not be delivered to one or more of its 
recipients. This is a permanent error. The following address(es) failed: 
[email protected] 
retry time not reached for any host after a long failure period
 ------ This is a copy of the message, including all the headers. ------ 
Return-path: <[email protected]> Received: from [x5.2x1.xxx.243] 
(port=57145 helo=server1.net) by server.net with esmtp (Exim 4.69 #1 
(Linux grus 2.6.8-1-386) id 1L789F-00042e-Qp for <[email protected]>; 
Mon, 01 Dec 2008 13:45:10 +0100 MIME-Version: 1.0 Date: Mon, 01 Dec 2008 
13:44:27 +0100"

So it still bounces for hotmail. Other external hosts works just fine. 
This problems stays on in both roundcube and local clients. And its only 
hotmail. Is this a exim4 rule problem?

-Andreas
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.