cancel
Showing results for 
Search instead for 
Did you mean: 

5.4.7 - Delivery expired (message too old) 'timeout'

paulcobb
Grafter
Posts: 146
Registered: ‎30-07-2007

5.4.7 - Delivery expired (message too old) 'timeout'

I have tried sending a message to a supanet.co.uk address but consistenly get
5.4.7 - Delivery expired (message too old) 'timeout'
Anyone like to comment on the cause please~?
9 REPLIES 9
Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: 5.4.7 - Delivery expired (message too old) 'timeout'

Send the message where you copy yourself as well, preferably to several addresses, ie your PN one + eg.Hotmail etc. See if any or only the supanet one is a problem. It would not surprise me if it was just supanet. I always had problems a while back with 2 people who were on supanet, thankfully they moved, they got fed up with problems as well. Supanet have a cruddy reputation.
paulcobb
Grafter
Posts: 146
Registered: ‎30-07-2007

Re: 5.4.7 - Delivery expired (message too old) 'timeout'

Yes the message I sent was to at least 6 including me and only the Supanet one was a problem.
I'm curious though as to what is happening to cause the error
Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: 5.4.7 - Delivery expired (message too old) 'timeout'

Could I suggest you post "sanitised" headers of the returned message presumably attached to the 'Delivery expired' mail.
Also you could just check that you computer date and time are correct.
paulcobb
Grafter
Posts: 146
Registered: ‎30-07-2007

Re: 5.4.7 - Delivery expired (message too old) 'timeout'

Headers show below
X-MSK: CML=1.502000
Return-path: <>
Envelope-to: me@mydomain.co.uk
Delivery-date: Fri, 20 Mar 2009 17:11:49 +0000
Received: from [212.159.7.97] (helo=mx.pcl-ipin01.plus.net)
  by pih-sunmxcore09.plus.net with esmtp (PlusNet MXCore v2.00) id 1LkiG5-0007Ba-5r
  for me@mydomain.co.uk; Fri, 20 Mar 2009 17:11:49 +0000
Authentication-Results: mx.pcl-ipin01.plus.net; dkim=neutral (message not signed) header.i=none
Received-SPF: None identity=pra; client-ip=84.92.2.65;
  receiver=mx.pcl-ipin01.plus.net;
  envelope-from="";
  x-sender="MAILER-DAEMON@pcl-ipout02.plus.net";
  x-conformance=sidf_compatible
Received-SPF: None identity=mailfrom; client-ip=84.92.2.65;
  receiver=mx.pcl-ipin01.plus.net;
  envelope-from="";
  x-sender="postmaster@relay.pcl-ipout02.plus.net";
  x-conformance=sidf_compatible
Received-SPF: None identity=helo; client-ip=84.92.2.65;
  receiver=mx.pcl-ipin01.plus.net;
  envelope-from="";
  x-sender="postmaster@relay.pcl-ipout02.plus.net";
  x-conformance=sidf_compatible
X-SBRS: 5.3
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: ApIDAANrw0lUXAJBmWdsb2JhbACNKgGIOwEBAQEBBg0KBxFDthiMOw
X-IronPort-AV: E=McAfee;i="5300,2777,5558"; a="57927789"
X-IronPort-AV: E=Sophos;i="4.38,396,1233532800";
  d="scan'208";a="57927789"
Received: from mx.ironport.plus.net (HELO relay.pcl-ipout02.plus.net) ([84.92.2.65])
  by mx.pcl-ipin01.plus.net with ESMTP; 20 Mar 2009 17:11:47 +0000
Received: from localhost by relay.pcl-ipout02.plus.net;
  20 Mar 2009 17:11:47 +0000
Date: 20 Mar 2009 17:11:47 +0000
To: me@mydomain.co.uk
From: "Mail Delivery System" <MAILER-DAEMON@pcl-ipout02.plus.net>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status; boundary="1UXmP.4PP0343Xz.1E1zlR.5i6Ioem"
Message-ID: <E1LkiG5-0007Ba-5r@pih-sunmxcore09.plus.net>
X-PN-Virus-Filtered: by PlusNet MXCore (v5.00)
X-PN-Spam-Filtered: by PlusNet MXCore (v5.00)
Subject: Delivery Status Notification (Failure)
--1UXmP.4PP0343Xz.1E1zlR.5i6Ioem
content-type: text/plain;
    charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
The following message to <Target email address@supanet.co.uk> was undeliverable.
The reason for the problem:
5.4.7 - Delivery expired (message too old) 'timeout'
--1UXmP.4PP0343Xz.1E1zlR.5i6Ioem
content-type: message/delivery-status
Reporting-MTA: dns; pcl-ipout02.plus.net
Final-Recipient: rfc822;targetemailaddress@supanet.co.uk
Action: failed
Status: 5.0.0 (permanent failure)
Diagnostic-Code: smtp; 5.4.7 - Delivery expired (message too old) 'timeout' (delivery attempts: 0)
--1UXmP.4PP0343Xz.1E1zlR.5i6Ioem
content-type: message/rfc822
Received: from pih-relay08.plus.net ([212.159.14.20])
  by relay.pcl-ipout02.plus.net with ESMTP; 17 Mar 2009 16:35:35 +0000
Received: from pih-relay08.plus.net ([212.159.14.20])
  by relay.pcl-ipout02.plus.net with ESMTP; 17 Mar 2009 16:35:50 +0000
Received: from [myIPaddress] (helo=MyPC)
by pih-relay08.plus.net with smtp (Exim) id 1LjcGZ-0008Kk-P0; Tue, 17 Mar 2009 16:35:49 +0000
Message-ID: <A1137072A4B3499E8C374CF9B92D9FE0@MyPC>
Reply-To: "Me" <me@mydomain.co.uk>
From: "Me" <me@mydomain.co.uk>
To: "Me" <me@mydomain.co.uk>,
address1>,
address2>,
address3>,
"Target Name" <Target Email Address@supanet.co.uk>,
address5>,
address6>
Subject: CENSORED
Date: Tue, 17 Mar 2009 16:35:31 -0000
MIME-Version: 1.0
Content-Type: multipart/mixed;
boundary="----=_NextPart_000_0064_01C9A71E.6393AE10"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.5512
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579
X-Plusnet-Relay: 4e2247f0835627789bbb77086063f87b
--1UXmP.4PP0343Xz.1E1zlR.5i6Ioem--
Anotherone
Champion
Posts: 19,107
Thanks: 457
Fixes: 21
Registered: ‎31-08-2007

Re: 5.4.7 - Delivery expired (message too old) 'timeout'

Well my interpretation of those headers is that the PN Ironports have tried to deliver the message for 3 days and failed, at which point they've given up and returned a Delivery Status Notification (Failure) message. (but I'm no expert). A few things you could check - No typos in the intended recipients e-mail address, Recipient not changed e-mail address, recipients mailbox not full?
There could be a problem at the recipients end, are they getting mail from anyone else?
bobpullen
Community Gaffer
Community Gaffer
Posts: 16,886
Thanks: 4,977
Fixes: 316
Registered: ‎04-04-2007

Re: 5.4.7 - Delivery expired (message too old) 'timeout'

Can you send an email to the Supanet address via a non-Plusnet server? You could try using a Webmail account like Gmail to do this.

Bob Pullen
Plusnet Product Team
If I've been helpful then please give thanks ⤵

paulcobb
Grafter
Posts: 146
Registered: ‎30-07-2007

Re: 5.4.7 - Delivery expired (message too old) 'timeout'

Headers from a Googlemail sent mail
X-MSK: CML=0.002000
Return-path: <myusername+caf_=myemailaddress@googlemail.com>
Envelope-to: myemailaddress
Delivery-date: Mon, 23 Mar 2009 14:17:00 +0000
Received: from [212.159.7.33] (helo=mx.ptn-ipin01.plus.net)
  by fhw-inmx02.plus.net with esmtp (PlusNet MXCore v2.00) id 1LlkxY-0001pt-0Q
  for myemailaddress; Mon, 23 Mar 2009 14:17:00 +0000
Authentication-Results: mx.ptn-ipin01.plus.net; dkim=neutral (message not signed) header.i=none
Received-SPF: None identity=pra; client-ip=72.14.220.154;
  receiver=mx.ptn-ipin01.plus.net;
  envelope-from="myusername+caf_=myemailaddress@googlemail.com";
  x-sender="mailer-daemon@googlemail.com";
  x-conformance=sidf_compatible
Received-SPF: Pass identity=mailfrom; client-ip=72.14.220.154;
  receiver=mx.ptn-ipin01.plus.net;
  envelope-from="myusername+caf_=myemailaddress@googlemail.com";
  x-sender="myusername+caf_=myemailaddress@googlemail.com";
  x-conformance=sidf_compatible
Received-SPF: None identity=helo; client-ip=72.14.220.154;
  receiver=mx.ptn-ipin01.plus.net;
  envelope-from="myusername+caf_=myemailaddress@googlemail.com";
  x-sender="postmaster@fg-out-1718.google.com";
  x-conformance=sidf_compatible
X-SBRS: 4.7
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AnUEAEM2x0lIDtyak2dsb2JhbACNLQGIBD8CAQEJCQoJEQOzAYg4hARi
X-IronPort-AV: E=McAfee;i="5300,2777,5561"; a="54042385"
X-IronPort-AV: E=Sophos;i="4.38,408,1233532800";
  d="scan'208";a="54042385"
Received: from fg-out-1718.google.com ([72.14.220.154])
  by mx.ptn-ipin01.plus.net with ESMTP; 23 Mar 2009 14:16:56 +0000
Received: by fg-out-1718.google.com with SMTP id e21so451827fga.22
        for <myemailaddress>; Mon, 23 Mar 2009 07:16:56 -0700 (PDT)
Received: by 10.86.1.1 with SMTP id 1mr3720805fga.0.1237817816355;
        Mon, 23 Mar 2009 07:16:56 -0700 (PDT)
X-Forwarded-To: me@mydomain.co.uk
X-Forwarded-For: myusername@gmail.com myemailaddress
Delivered-To: myusername@gmail.com
Received: by 10.86.9.19 with SMTP id 19cs419360fgi;
        Mon, 23 Mar 2009 07:16:55 -0700 (PDT)
Received: by 10.220.97.213 with SMTP id m21mr2429246vcn.27.1237817812602;
        Mon, 23 Mar 2009 07:16:52 -0700 (PDT)
Received: by 10.220.97.213 with SMTP id m21mr3380685vcn.27;
        Mon, 23 Mar 2009 07:16:52 -0700 (PDT)
Message-ID: <0016e64eca3804472e0465c9eb6a@googlemail.com>
From: Mail Delivery Subsystem <mailer-daemon@googlemail.com>
To: myusername@gmail.com
Date: Mon, 23 Mar 2009 07:16:52 -0700 (PDT)
X-PN-Virus-Filtered: by PlusNet MXCore (v5.00)
X-PN-Spam-Filtered: by PlusNet MXCore (v5.00)
Subject: Delivery Status Notification (Delay)
This is an automatically generated Delivery Status Notification
THIS IS A WARNING MESSAGE ONLY.
YOU DO NOT NEED TO RESEND YOUR MESSAGE.
Delivery to the following recipient has been delayed:
    targetemailaddress@supanet.co.uk
Message will be retried for 2 more day(s)
Technical details of temporary failure:
The recipient server did not accept our requests to connect. Learn more at http://mail.google.com/support/bin/answer.py?answer=7720
[supanet.co.uk (1): Connection timed out]
  ----- Message header follows -----
MIME-Version: 1.0
Received: by 10.220.97.213 with SMTP id m21mr2235147vcn.27.1237708624852; Sun,
22 Mar 2009 00:57:04 -0700 (PDT)
Date: Sun, 22 Mar 2009 07:57:04 +0000
Message-ID: <87497b9b0903220057o71b91f4cu1e9efce4aed1f338@mail.gmail.com>
Subject: Censored
From: Me<myusername@googlemail.com>
To: targetemailaddress@supanet.co.uk
Cc: myemailaddress
Content-Type: multipart/mixed; boundary=0016e64eca38eb7a260465b07ec3
  ----- Message body suppressed -----
itsme
Grafter
Posts: 5,924
Thanks: 3
Registered: ‎07-04-2007

Re: 5.4.7 - Delivery expired (message too old) 'timeout'

Go here to test the email address you are sending to. I tried test@supanet.com and the following was returned.
Quote
[Contacting manchester.sin1.netline.net.uk [213.40.66.235]...]
[Connected]
220 methuselah.sin1.netline.net.uk ESMTP Exim 4.69 Tue, 24 Mar 2009 14:38:47 +0000
EHLO hexillion.com
250-methuselah.sin1.netline.net.uk Hello hexillion.com [70.84.211.98]
250-SIZE 10485760
250-PIPELINING
250 HELP
MAIL FROM:<HexValidEmail@hexillion.com>
250 OK
RCPT TO:<test@supanet.com>
550 This email address is not known to this system
[Address has been rejected]
RSET
250 Reset OK
QUIT
221 methuselah.sin1.netline.net.uk closing connection
[Connection closed]

itsme
Grafter
Posts: 5,924
Thanks: 3
Registered: ‎07-04-2007

Re: 5.4.7 - Delivery expired (message too old) 'timeout'

After rereading the post I see that the domain failing is supanet.co.uk. This domain has no MX records so that's the reason for the failures. I believe that you should be using mailbox@supanet.net