DELIVERY FAILURE and other errors get bounced to root email account

Hi,

In the past few weeks, I've literally been receiving hundreds of emails a day to my email account of my dedicated server. Just now, I've deleted 411 emails. Here are a few examples:

Subject:Mail delivery failed: returning message to sender

Code:

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:

  Karen1303@yahoo.com
    SMTP error from remote mail server after end of data:
    host b.mx.mail.yahoo.com [66.196.97.250]: 554 delivery error:
    dd Sorry your message to karen1303@yahoo.com cannot be delivered. This account has been disabled or discontinued [#103]. - mta185.mail.re3.yahoo.com

------ This is a copy of the message, including all the headers. ------

Return-path: <nobody@core.core-fusion.net>
Received: from nobody by core.core-fusion.net with local (Exim 4.63)
	(envelope-from <nobody@core.core-fusion.net>)
	id 1H9R4R-0003gw-Ih
	for Karen1303@yahoo.com; Tue, 23 Jan 2007 12:12:39 -0700
To: Karen1303@yahoo.com
Subject: RavensTurf.Com Blog Post Verify You Email
Message-Id: <E1H9R4R-0003gw-Ih@core.core-fusion.net>
From: Nobody <nobody@core.core-fusion.net>
Date: Tue, 23 Jan 2007 12:12:39 -0700

A message with a link here, my son.

Subject: Mail failure-no recipient address

Code:

A message that you sent contained no recipient addresses, and therefore no
delivery could be attempted.

------ This is a copy of your message, including all the headers. ------

To: 
Subject: RavensTurf.Com Blog Post Verify You Email
Message-Id: <E1H9U9w-0000nX-4F@core.core-fusion.net>
From: Nobody <nobody@core.core-fusion.net>
Date: Tue, 23 Jan 2007 15:30:32 -0700

A message with a link here, my son.

The from line says :Mailer-Daemon@core.core-fusion.net
Sender: hlfusion@core.core-fusion.net
To: nobody@core.core-fusion.net

Anyone know how to solve this problem?

 

No takers?

 

Guess not.

 

Yup, it was unticked.