The organisation I work for has changed the way we deliver mail so we now use our exchange server to deliver through our message security service, instead of sending through our ISP's smarthost - a change that is working very well for most of our needs.
We send out newsletters to organisations who subscribe to them but since changing our mail delivery system, we are getting lots of NDR's (non delivery reports)
One common NDR with a 4.4.7 (The message in the queue has expired. The sending server tried to relay or deliver the message, but the action was not completed before the message expiration time occurred.) where the header includes the following:
Received: from mailx.bemtaxx.messagelabs.com ([193.109.xxx.xxx]) by exfe2.theirexample.org.uk over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Thu, 5 Jan 2012 17:08:15 +0000 Return-Path: <adminsname@ourexample.org.uk> Received: from [193.xxx.xxx.xxx:15511] by server-x.bemta-xx.messagelabs.com id xx/E2-xx84-DF8D50F4; Thu, 05 Jan 2012 17:08:13 +0000 X-Env-Sender: adminsname@ourexample.org.uk X-Msg-Ref: server-x.tower-xx.messagelabs.com!1xxxxx195!72xxxx3!1 X-Originating-IP: [207.xxx.xxx.xxx] X-SpamReason: No, hits=0.0 required=7.0 tests=Mail larger than max spam size
I need to know whether this translates as " your email has too high a spam count for message labs to deliver it"
or " The message has an attachment that is too large" or "we aren't going to deliver this as we think its spam as it was sent BCC instead of TO a recipient"
Many thanks for any insight