What's the guts with xtra's email?
Chris Sherlock
We've had a number of emails sent from ihug to xtra addresses failing. This
what arrives back here.
The following message to <nob...@xtra.co.nz> was undeliverable.
The reason for the problem:
5.4.7 - Delivery expired (message too old) 'timeout'
Anyone know whats happening?
Regards, Chris
RL
> The following message to <nob...@xtra.co.nz> was undeliverable.
> The reason for the problem:
> 5.4.7 - Delivery expired (message too old) 'timeout'
>
>
> Anyone know whats happening?
You'd need to post more of the message to give an indication of exactly
where the problem was (Ihug to Xtra, or within Xtra itself). The error
message suggests it was stuck on a mail server for a while, and for one
reason or another it was not possible to send the mail upstream to
another SMTP server, and the sending server has simply given up.
Normally the expiration period would be set to around 5 days.
RL
Chris Sherlock
"RL" <r...@null.void.test> wrote in message
news:fvh03n$tqi$1...@lust.ihug.co.nz...
G'day RL,
OK here's the lot, what are we looking for? No point hiding my own email
address, I've been using it for ten years and it's on EVERY spammers list.
Regards, Chris
Return-path: <>
Envelope-to: raw...@es.co.nz
Received: from pub.filter1.content.ihug.net.nz (mx.mailfilter1.ihug.co.nz)
[10.80.49.1]
by mx6.content.ihug.net.nz with esmtp
(Exim 4.60 #1 (Debian); Ihug conf #216)
id 1JsAnt-0006pO-Ng; Sat, 03 May 2008 18:01:01 +1200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: An8AAIqbG0jLbYcxnWdsb2JhbACRZwEBAQEBCA0HB1M
X-IronPort-AV: E=Sophos;i="4.27,430,1204455600";
d="scan'208";a="95982730"
Ironport-Content-Filter: in-world
Ironport-ICF: in-world
Received: from zuul.ihug.co.nz (HELO mx.mailfilter1.ihug.co.nz)
([203.109.135.49])
by mx.mailfilter1.ihug.co.nz with ESMTP; 03 May 2008 18:01:00 +1200
Received: from localhost by mx.mailfilter1.ihug.co.nz;
03 May 2008 18:01:00 +1200
Date: 03 May 2008 18:01:00 +1200
To: raw...@es.co.nz
From: "Mail Delivery System" <MAILER...@akl-grafton-ironport1.ihug.net>
Subject: Delivery Status Notification (Failure)
X-Rcpt-To:raw...@es.co.nz
X-Antivirus: AVG for E-mail 7.5.524 [269.23.8/1412]
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=======AVGMAIL-481C00A454C6======="
X-Bayesian-Result: Clean (0)
X-Bayesian-Words: 203-109-161-114 0 delivery 4 glenda 0 home 0 julia 0 kate
11 kevin 0 normal 3 notification 0 rawhiti 10 reason 0 ryan 5 tim_ryan 0
windows 8 xtra 0
X-SpamPal: PASS
--=======AVGMAIL-481C00A454C6=======
Content-Type: multipart/report; report-type=delivery-status;
boundary="5gWSi.4J4qv46kb.1B/Brz.FDzzgmU"
--5gWSi.4J4qv46kb.1B/Brz.FDzzgmU
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
The following message to <nob...@xtra.co.nz> was undeliverable.
The reason for the problem:
5.4.7 - Delivery expired (message too old) 'timeout'
--5gWSi.4J4qv46kb.1B/Brz.FDzzgmU
Content-Type: message/delivery-status
Reporting-MTA: dns; akl-grafton-ironport1.ihug.net
Content-Type: text/plain
Final-Recipient: rfc822;nob...@xtra.co.nz
Action: failed
Status: 5.0.0 (permanent failure)
Diagnostic-Code: smtp; 5.4.7 - Delivery expired (message too old) 'timeout'
(delivery attempts: 0)
--5gWSi.4J4qv46kb.1B/Brz.FDzzgmU
Content-Type: message/rfc822
Received: from 203-109-161-114.dsl.dyn.ihug.co.nz (HELO Lounge)
([203.109.161.114])
by smtp.mailfilter1.ihug.co.nz with SMTP; 30 Apr 2008 17:05:34 +1200
Received: from 203-109-161-114.dsl.dyn.ihug.co.nz (HELO Lounge)
([203.109.161.114])
by smtp.mailfilter1.ihug.co.nz with SMTP; 30 Apr 2008 17:05:21 +1200
Message-ID: <6254DBC20D0A405EB7BA80BB5E078446@Lounge>
Reply-To: "Chris & Kate" <raw...@es.co.nz>
From: "Chris & Kate" <raw...@es.co.nz>
To: "Sherlocks" <nob...@paradise.net.nz>,
"Boo" <nob...@xtra.co.nz>,
"edens" <nob...@xtra.co.nz>,
"Glenda & Kevin" <nob...@actrix.co.nz>,
<nick...@paradise.net.nz>,
"Tim and Julia home" <nob...@paradise.net.nz>
Subject: Fw: Clever advertising
Date: Wed, 30 Apr 2008 17:05:35 +1200
MIME-Version: 1.0
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Windows Mail 6.0.6001.18000
X-MIMEOLE: Produced By Microsoft MimeOLE V6.0.6001.18000
Content-Type: multipart/related;
boundary="----=_NextPart_000_0037_01C8AAE4.688EE600";
type="multipart/alternative"
------=_NextPart_000_0037_01C8AAE4.688EE600--
--5gWSi.4J4qv46kb.1B/Brz.FDzzgmU--
--=======AVGMAIL-481C00A454C6=======
Content-Type: text/plain; x-avg=cert; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Content-Description: "AVG certification"
No virus found in this incoming message.
Checked by AVG.
Version: 7.5.524 / Virus Database: 269.23.8/1412 - Release Date: 2/05/2008
4=
:34 p.m.
--=======AVGMAIL-481C00A454C6=======--
David Empson
> "RL" <r...@null.void.test> wrote in message
> news:fvh03n$tqi$1...@lust.ihug.co.nz...
> > Chris Sherlock wrote:
> >> The following message to <nob...@xtra.co.nz> was undeliverable.
> >> The reason for the problem:
> >> 5.4.7 - Delivery expired (message too old) 'timeout'
> >>
> >>
> >> Anyone know whats happening?
> >
> > You'd need to post more of the message to give an indication of exactly
> > where the problem was (Ihug to Xtra, or within Xtra itself). The error
> > message suggests it was stuck on a mail server for a while, and for one
> > reason or another it was not possible to send the mail upstream to another
> > SMTP server, and the sending server has simply given up.
> >
> > Normally the expiration period would be set to around 5 days.
>
> OK here's the lot, what are we looking for? No point hiding my own email
> address, I've been using it for ten years and it's on EVERY spammers list.
[Detailed report retained below]
The error report says that the message timed out after about 3 days
sitting on Ihug's mail server.
> Reporting-MTA: dns; akl-grafton-ironport1.ihug.net
> Content-Type: text/plain
>
> Final-Recipient: rfc822;nob...@xtra.co.nz
> Action: failed
> Status: 5.0.0 (permanent failure)
> Diagnostic-Code: smtp; 5.4.7 - Delivery expired (message too old) 'timeout'
> (delivery attempts: 0)
The puzzling detail is that last line, which said it made no attempt to
send the message.
I suspect the problem here is Xtra's new association with Yahoo and its
extremely bad handling of messages sent to multiple recipients. Yahoo is
apparently dropping connections when another mail server attempts to
send mail to more than five Xtra customers in a single connection. The
originating mail server would treat this as a failed connection attempt
and might not even count it as a "delivery attempt", so would just try
again on a regular basis.
Were there other recipients on Xtra which you have omitted from the
list, including any for whom you used the Bcc field rather than the To
field? If not, it only looks like this was addressed to two Xtra
customers and shouldn't have triggered Yahoo's automatic drop.
It could be a related issue, such as you personally or Ihug in general
being regarded by Yahoo as a potential source of spam, and blocking all
attempts to send mail to anyone at Xtra unless you jump through some
hoops and register with Yahoo. Are you able to send normal messages to a
single Xtra address without problems?
The other possibility is a local problem at Ihug.
Your best option might be to try to contact Ihug customer support and
see if they can assist further.
I've left the full message below in case anyone wants to look closer.
--
David Empson
dem...@actrix.gen.nz
Reg
FWIW
I had the same experience sending from ihug the other day.
The mail contained 3 jpg files totalling about 1600KB.
3 recipients - all returned as undeliverable
But sent off successfully when addressed to each individually.
None of the recipients were on xtra.
Chris Sherlock
"Reg" <r...@nospam.com> wrote in message
news:7r8q14l5534t3mqf0...@4ax.com...
> On Sat, 3 May 2008 19:56:25 +1200, dem...@actrix.gen.nz (David
> Empson) wrote:
content snipped...
>
> FWIW
> I had the same experience sending from ihug the other day.
> The mail contained 3 jpg files totalling about 1600KB.
> 3 recipients - all returned as undeliverable
> But sent off successfully when addressed to each individually.
> None of the recipients were on xtra.
Thanks for that info, much the same here except only emails addressed to
xtra accounts were affected, all the other addresses seemed to go OK
regardless. The emails to xtra addresses went fine when each was sent to a
single recipient. Isn't technology wonderful?
Regards, Chris
Lawrence D'Oliveiro
> The emails to xtra addresses went fine when each was sent to a
> single recipient. Isn't technology wonderful?
$%&@!&* big corporations who think they can $%&@!&* introduce hamfisted
policies without $%&@!&* thinking their implications through ...
Craig Shore
wrote:
They might bounce back at you yet.
I've just has one I sent on Thursday to business using Xtra bounced
back to me with the same error. My message only contained text and
was only to the one address.
Wonder if it's Xtra or ihug that is the problem?
Robin Halligan
I just got one back today sent to a Gmail account
The reason for the problem:
5.4.7 - Delivery expired (message too old) 'timeout'
and this was a simple 5 line text message no attachments or anything