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:
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 cpanel by server.nuweb.co.uk with local (Exim 4.50)
for [email protected]; Mon, 30 May 2005 16:58:50 +0100
Received: from 22.214.171.124 ([126.96.36.199]) by www.nuweb.co.uk
(Horde) with HTTP for <firstname.lastname@example.org>; Mon, 30 May 2005 16:58:50
Date: Mon, 30 May 2005 16:58:50 +0100
From: "Admin - Mobile-focus.co.uk" <[email protected]>
To: [email protected]
User-Agent: Internet Messaging Program (IMP) H3 (4.0)
E-Mail: [email protected]
ANY IDEAS? .. worked yesterday, i am the onlyone with server setting change abilities... so i know nothing has changed..
finally, if every email you send bounces, then you probably have a different problem. Chances are your email client is misconfigured. Double check out outgoing or "SMTP" server settings, and double check with your ISP to ensure that you have them set correctly.
If you're wondering whether the type of message you're sending is a bounce message, and thus whether it should conform as described above, ask yourself these questions:
* Is the message I'm sending an original message to a known user, or email address, I already know about, rather than to an email address supplied by a potentially-unknown third party?
*Do I want to receive a bounce message back if the destination user, or email address, doesn't exist, or can't or won't accept the message for various reasons such as a full disk, or it looks like a possible virus or spam?
* Are the contents of the message I'm sending entirely under my control, rather than containing portions that can be supplied by a potentially-unknown third party?
If the answers to these questions are all "No", then you are sending a bounce message, so it should conform to the requirements for a bounce message.