Order status change produces bounced emails

Hi all,

as the title suggests, when my client changes the status of customer's order the subsequent email which OC sends out to inform the customer is always bounced.

I wondered if it was maybe that if the customer checks out with creating an account this would happen.

any ideas?

Thanks

khinteriorsltd.co.uk

What do the bounce notices actually say? Look at their FULL headers. Were there no such mailboxes? Was the outbound mailserver dynamically blacklisted? Whatever, what were the actual reasons for the bounces? The headers show what the mailservers said to one another en route, and when it happens also round-trip.

Thanks for your response butte. I must admit i don't know enough about solving email problems. Here is what the headers look like:

-----Original Message-----
From: Mail Delivery System [mailto:Mailer-Daemon@hosts.co.uk]
Sent: 27 September 2013 11:51
To: **********@hosts.co.uk
Subject: Mail delivery failed: returning message to sender

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:

***********@ntlworld.com

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

Return-path: <*********@hosts.co.uk>
Received: from [192.168.0.78] (helo=basil.hosts.co.uk)
by outgoing-smtp.namesco.net with esmtp (Exim 4.72)
(envelope-from <***********@hosts.co.uk>)
id 1VPVa0-0006hw-NZ
for **************@ntlworld.com; Fri, 27 Sep 2013 11:47:24 +0100
Received: from custid476035+linux-sharedweb by basil.hosts.co.uk with local (Exim 4.63)
(envelope-from <custid476035+linux-sharedweb@hosts.co.uk>)
id 1VPVZx-0006ks-EZ
for *********@ntlworld.com; Fri, 27 Sep 2013 11:47:21 +0100
To: ************@ntlworld.com
Subject: =?UTF-8?B?S0ggSW50ZXJpb3JzIEx0ZCAtIE9yZGVyIFVwZGF0ZSAxMDQ3?=
X-PHP-Originating-Script: 476035:mail.php
MIME-Version: 1.0
Date: Fri, 27 Sep 2013 11:47:21 +0100
From: =?UTF-8?B?S0ggSW50ZXJpb3JzIEx0ZA==?=<*******@khinteriorsltd.co.uk>
Reply-To: KH Interiors Ltd<*******@khinteriorsltd.co.uk>
X-Mailer: PHP/5.3.27
Content-Type: multipart/related;
boundary="----=_NextPart_f3a5a93913444be48de9d76da76befb4"
Message-Id: <E1VPVZx-0006ks-EZ@basil.hosts.co.uk>
Sender: <**********@hosts.co.uk>
X-namescosender: 476035 102105
X-namesco: 192.168.0.150
X-ACL-Warn: Recipient address verification failure: recipient
X-Spam-Score: -0.9 (/)

------=_NextPart_f3a5a93913444be48de9d76da76befb4
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

Order ID: 1047
Date Ordered: 25/09/2013

Your order has been updated to the following status:
Canceled

Please reply to this email if you have any questions.
------=_NextPart_f3a5a93913444be48de9d76da76befb4--

It says, "could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed:" but does not say why (such as codes for no box, for dynamically blacklisted sender, etc.). That could mean that an address is good but YOUR mail for whatever reason is blocked -- Stateside bouncebacks normally tell WHY when reaching permanent error status. Retries when mailservers are down are in fairly quick, then increasingly slow succession before eventually delivery is no longer attempted, but you would not likely have any appreciable number of customers with down mailservers at once, unless they happen to share one.

For what (perhaps little) it might be worth at the moment, these lines seem to invite attention.

by outgoing-smtp.namesco.net with esmtp (Exim 4.72)
(envelope-from <khinteriorsltd.co.uk@hosts.co.uk>)
Subject: =?UTF-8?B?S0ggSW50ZXJpb3JzIEx0ZCAtIE9yZGVyIFVwZGF0ZSAxMDQ3?=
X-PHP-Originating-Script: 476035:mail.php
From: =?UTF-8?B?S0ggSW50ZXJpb3JzIEx0ZA==?=<sales@khinteriorsltd.co.uk>
X-Spam-Score: -0.9 (/)

Whether mail/smtp setting, mail.php, or a somehow diverted database lookup over the status change even contributes is hard to tell, but you might try looking at the first (mail/smtp setting) just to be sure it was supposed to be smtp. What mail.php or database might have to do with it will probably take some noodling unless somebody close to core has encountered it.

You should substitute something for the live e-mail link ("now"), the poor fellow might wonder why there's an influx of spam, if the address is good.

Thanks, i appreciate your help on this.
I haven't managed to solve it yet but when i do i will update this post.
cheers
DAZ