E-mails from O2 take A LOT of time to reach my e-mail address

[litos81]

Hi,

Any e-mail sent by O2 to my e-mail address takes literally almost a day to reach my e-mail address. Who should I complain about this? I had a chat with Customer Services but the only thing they could say is that the system sends the e-mails automatically... and can't do anything about it. Sure there msut be someone I can pass more 'technical' details about the issue?

For instance:

Received: from ukmlwmsw003.uk.pri.o2.com (unknown [158.230.100.102])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by mx6.messagingengine.com (Postfix) with ESMTPS
	for <xxx@myaddress.com>; Sat, 21 Nov 2020 22:36:27 -0500 (EST)
Received: from RESMLWHTS002.res.pri.o2.com (resmlwhts002.res.pri.o2.com [10.173.249.112])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits))
	(No client certificate requested)
	by ukmlwmsw003.uk.pri.o2.com (MTA) with ESMTPS id 4CdTPR6BmZznW5v
	for <xxx@myaddress.com>; Sat, 21 Nov 2020 09:58:03 +0000 (GMT)
Received: from cologne (10.173.249.120) by resmlwhts002.res.pri.o2.com
 (10.173.249.112) with Microsoft SMTP Server id 14.3.487.0; Sat, 21 Nov 2020
 09:57:56 +0000
Date: Sat, 21 Nov 2020 09:57:56 +0000

As you can see, the e-mail was originally sent on Saturday, 21 Nov 2020 at 09:57 AM GMT, and arrived to my address the early morning of Sunday 22 Nov 2020 at 03:36:27 GMT (21 Nov 2020 22:36:27 EST). Most of the time was idling around in the O2 server ukmlwmsw003.uk.pri.o2.com

Can anybody help? Today is happening the same, so it is not a one-off hiccup.

Thanks,

Carlos

[madasaf1sh]

@litos81

Do you have the full message header and not just the cut and paste issue

Email isnt a guaranteed method of communication.

Looking at the mail header the email was passed to UKMLWMSW003.uk.pri.o2.com within 7 seconds.

The mail was sat connecting to mx6.messagingengine.com (fastmail) for 18hrs before that mail server accepted the message over TLS

So could be a service issue.

Check here for Service Status:
https://www.fastmailstatus.com/

They have had issues today.

[litos81]

@madasaf1sh 

Thanks for your prompt reply. This is the full message header:

Return-Path: <noreply@o2mail.co.uk>
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43])
	 by sloti2d3t19 (Cyrus 3.3.0-622-g4a97c0b-fm-20201115.001-g4a97c0b3) with LMTPA;
	 Sat, 21 Nov 2020 22:36:25 -0500
X-Cyrus-Session-Id: sloti2d3t19-1606016185-3122187-2-7368247767309007500
X-Sieve: CMU Sieve 3.0
X-Spam-known-sender: no
X-Spam-sender-reputation: 500 (none)
X-Spam-score: 2.4
X-Spam-hits: DCC_CHECK 1.1, HTML_MESSAGE 0.001, ME_SENDERREP_NEUTRAL 0.001,
  MIME_HTML_ONLY 0.1, RCVD_IN_MSPIKE_H3 -0.01, RCVD_IN_MSPIKE_WL -0.01,
  RDNS_NONE 1.274, SPF_HELO_NONE 0.001, SPF_PASS -0.001, LANGUAGES en,
  BAYES_USED none, SA_VERSION 3.4.2
X-Backscatter: NotFound1
X-Backscatter-Hosts: 
X-Spam-source: IP='158.230.100.102', Host='noreverse', Country='GB', FromHeader='uk',
  MailFrom='uk'
X-Spam-charsets: html='ISO-8859-1'
X-Resolved-to: xxx@myaddress.com
X-Delivered-to: xxx@myaddress.com
X-Mail-from: noreply@o2mail.co.uk
Received: from mx6 ([10.202.2.205])
  by compute3.internal (LMTPProxy); Sat, 21 Nov 2020 22:36:27 -0500
Received: from mx6.messagingengine.com (localhost [127.0.0.1])
	by mailmx.nyi.internal (Postfix) with ESMTP id 73C0BEC0086
	for <xxx@myaddress.com>; Sat, 21 Nov 2020 22:36:27 -0500 (EST)
Received: from mx6.messagingengine.com (localhost [127.0.0.1])
    by mx6.messagingengine.com (Authentication Milter) with ESMTP
    id 967C8BEB8F2;
    Sat, 21 Nov 2020 22:36:27 -0500
ARC-Seal: i=1; a=rsa-sha256; cv=none; d=messagingengine.com; s=fm1; t=
    1606016187; b=fRlR0qTIamBkk02uTcMLnma9XJHV2R92cv0BpaGEDKWhZ2zQ2I
    knnqWsE6bgX5eCmAILSgGRXc7LX3Oxp8gWgPGRrGOo5EtjmASkd9UhGf6sSjEipj
    6qoOcuTuH3eylDFCgnRGwLm2M1CIF1OzTLPKRBfNZ2dV6t0BeDQmW6j6s+V9tDrN
    rYEeWoloA/9HWussw0XBfIMDcbYDG7Q4Y7hoeV5hAz/jAizI9RseCTk9T8hXGCfj
    p7nKrHHlL0FCxwfYVQdcmAthIvqLCfYeD/GGldyG4e6j/kizc87Ydqh2M4nSdIpn
    wftU435pvCETE1ajFM7ZW0OtNPiR8469CiHw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=
    messagingengine.com; h=date:from:to:message-id:subject
    :mime-version:content-type:content-transfer-encoding; s=fm1; t=
    1606016187; bh=GWEldc7y8OzNBB9H6m9GMVdAJNFmRsp6uT+MkZkGPKs=; b=p
    3IOVsRi/ItW0Lrrl8JrdY8pmN18aQksg4DifohAcjlYNXdTOaB21pQZx2x7Zsx0K
    3ub0dZsnZ5jbq5pOx20YfqkfFyGRlco5vN+1YdzNoIP6QJAU9zcmfPIcESSnaJkL
    cm2ccz4NXE8ayU0QvRh+40Ee/Z3dMUJrB6H1x+yIHB4RP0qYrrE5AwfI/0/PV7qu
    bzuFFGD6RhwP+5y6L2I8uFVFqgA2OxQyPHHd5gGY/JppCXr00Jfr9T0aYUXhQlm7
    x7NyU9qpYgJv++xsW48IxYt2ypJxVegGSHMyBedbtAAr3O6/uH+o8eHK7pVLo6ee
    KNYE4B/RO/aIM2iWu13Mw==
ARC-Authentication-Results: i=1; mx6.messagingengine.com; arc=none (no signatures found);
    bimi=skipped (DMARC Policy is not at enforcement);
    dkim=none (no signatures found);
    dmarc=pass policy.published-domain-policy=none
    policy.applied-disposition=none policy.evaluated-disposition=none
    (p=none,d=none,d.eval=none) policy.policy-from=p
    header.from=o2mail.co.uk;
    iprev=fail smtp.remote-ip=158.230.100.102
    (Error NOERROR looking up 158.230.100.102 PTR,Error Error NXDOMAIN looking up cellgate.btcellnet.net. A looking up cellgate.btcellnet.net. A,Error Error NXDOMAIN looking up cellgate.btcellnet.net. AAAA looking up cellgate.btcellnet.net. AAAA);
    spf=pass smtp.mailfrom=noreply@o2mail.co.uk
    smtp.helo=ukmlwmsw003.uk.pri.o2.com;
    x-aligned-from=pass (Address match);
    x-ptr=fail smtp.helo=ukmlwmsw003.uk.pri.o2.com policy.ptr="";
    x-return-mx=pass header.domain=o2mail.co.uk policy.is_org=yes
    (MX Records found: dmmlw-seg-01.o2.com,dmmlw-seg-02.o2.com,dmell-seg-03.o2.com,dmell-seg-04.o2.com);
    x-return-mx=pass smtp.domain=o2mail.co.uk policy.is_org=yes
    (MX Records found: dmmlw-seg-01.o2.com,dmmlw-seg-02.o2.com,dmell-seg-03.o2.com,dmell-seg-04.o2.com);
    x-tls=pass smtp.version=TLSv1.2 smtp.cipher=ECDHE-RSA-AES128-GCM-SHA256
    smtp.bits=128/128;
    x-vs=clean score=0 state=0
Authentication-Results: mx6.messagingengine.com;
    arc=none (no signatures found);
    bimi=skipped (DMARC Policy is not at enforcement);
    dkim=none (no signatures found);
    dmarc=pass policy.published-domain-policy=none
      policy.applied-disposition=none policy.evaluated-disposition=none
      (p=none,d=none,d.eval=none) policy.policy-from=p
      header.from=o2mail.co.uk;
    iprev=fail smtp.remote-ip=158.230.100.102
      (Error NOERROR looking up 158.230.100.102 PTR,Error Error NXDOMAIN looking up cellgate.btcellnet.net. A looking up cellgate.btcellnet.net. A,Error Error NXDOMAIN looking up cellgate.btcellnet.net. AAAA looking up cellgate.btcellnet.net. AAAA);
    spf=pass smtp.mailfrom=noreply@o2mail.co.uk
      smtp.helo=ukmlwmsw003.uk.pri.o2.com;
    x-aligned-from=pass (Address match);
    x-ptr=fail smtp.helo=ukmlwmsw003.uk.pri.o2.com policy.ptr="";
    x-return-mx=pass header.domain=o2mail.co.uk policy.is_org=yes
      (MX Records found: dmmlw-seg-01.o2.com,dmmlw-seg-02.o2.com,dmell-seg-03.o2.com,dmell-seg-04.o2.com);
    x-return-mx=pass smtp.domain=o2mail.co.uk policy.is_org=yes
      (MX Records found: dmmlw-seg-01.o2.com,dmmlw-seg-02.o2.com,dmell-seg-03.o2.com,dmell-seg-04.o2.com);
    x-tls=pass smtp.version=TLSv1.2 smtp.cipher=ECDHE-RSA-AES128-GCM-SHA256
      smtp.bits=128/128;
    x-vs=clean score=0 state=0
X-ME-VSCause: gggruggvucftvghtrhhoucdtuddrgedujedrudegfedgieduucetufdoteggodetrfdotf
    fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu
    rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvkf
    fugggtgfeshheutgdttddtudenucfhrhhomhepoehnohhrvghplhihsehovdhmrghilhdr
    tghordhukheqnecuggftrfgrthhtvghrnhepjeehhefgteetfeegteekueevkeffjeeive
    ekledvtdeijeekuddvueefiedukedtnecuffhomhgrihhnpehovddrtghordhukhenucfk
    phepudehkedrvdeftddruddttddruddtvdenucevlhhushhtvghrufhiiigvpedunecurf
    grrhgrmhepihhnvghtpeduheekrddvfedtrddutddtrddutddvpdhhvghlohepuhhkmhhl
    fihmshiftddtfedruhhkrdhprhhirdhovddrtghomhdpmhgrihhlfhhrohhmpeeonhhorh
    gvphhlhiesohdvmhgrihhlrdgtohdruhhkqe
X-ME-VSScore: 0
X-ME-VSCategory: clean
Received-SPF: pass
    (o2mail.co.uk: 158.230.100.102 is authorized to use 'noreply@o2mail.co.uk' in 'mfrom' identity (mechanism 'ip4:158.230.100.102' matched))
    receiver=mx6.messagingengine.com;
    identity=mailfrom;
    envelope-from="noreply@o2mail.co.uk";
    helo=ukmlwmsw003.uk.pri.o2.com;
    client-ip=158.230.100.102
Received: from ukmlwmsw003.uk.pri.o2.com (unknown [158.230.100.102])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by mx6.messagingengine.com (Postfix) with ESMTPS
	for <xxx@myaddress.com>; Sat, 21 Nov 2020 22:36:27 -0500 (EST)
Received: from RESMLWHTS002.res.pri.o2.com (resmlwhts002.res.pri.o2.com [10.173.249.112])
	(using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits))
	(No client certificate requested)
	by ukmlwmsw003.uk.pri.o2.com (MTA) with ESMTPS id 4CdTPR6BmZznW5v
	for <xxx@myaddress.com>; Sat, 21 Nov 2020 09:58:03 +0000 (GMT)
Received: from cologne (10.173.249.120) by resmlwhts002.res.pri.o2.com
 (10.173.249.112) with Microsoft SMTP Server id 14.3.487.0; Sat, 21 Nov 2020
 09:57:56 +0000
Date: Sat, 21 Nov 2020 09:57:56 +0000
From: <noreply@o2mail.co.uk>
To: <xxx@myaddress.com>
Message-ID: <157283087.9215.1605952676450.JavaMail.wlapp@cologne>
Subject: Your O2 username
MIME-Version: 1.0
Content-Type: text/html;
    charset=ISO-8859-1
Content-Transfer-Encoding: BASE64
SOAPAction: ""
x-msw-jemd-newsletter: false
x-msw-jemd-refid: [1]1,0,0,,d41d8cd98f00b204,noreply@o2mail.co.uk,xxx@myaddress.com,RULES_HIT:41:72:355:375:379:962:967:978:979:983:988:989:1189:1208:1224:1252:1261:1311:1313:1314:1345:1381:1431:1437:1515:1516:1517:1534:1541:1589:1593:1594:1711:1730:1747:1777:1792:2084:2393:2525:2559:2563:2682:2685:2693:2859:2890:2902:2933:2937:2939:2942:2945:2947:2951:2954:3000:3022:3138:3139:3140:3141:3142:3167:3352:3362:3865:3867:3868:3870:3871:3872:3873:3874:3934:3936:3938:3941:3944:3947:3950:3953:3956:3959:4042:4321:4383:4648:5007:6248:6261:6674:6678:7903:7976:8828:9025:9080:9164:9344:10044:11658:11967:12043:12219:12297:12555:12760:12903:12955:13311:13357:13439:13870:13972:14037:14096:14180:14181:14384:14408:14571:14777:14818:21080:21347:21433:21450:21451:21611:21622:21819:21898:21939:21984:30001:30003:30019:30022:30034:30052:30054:30069:30070,0,RBL:04y8y1ao3zmz9oydxxgg1oq8h1xr1ycgbf16ggoopqciizrcbd7wjahphipefo3.65tjd
x-msw-jemd-refid: [2]5r16uiubodkgn3trs58mz5e1xnyu5anogi9wgzibuee1nrpcuanept18aq.h-lbl8.mailshell.net-223.238.255.100,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:,MSBL:0,DNSBL:neutral,Custom_rules:0:1:0,LFtime:14,LUA_SUMMARY:none;newsletter:no;phishing:no

I'm not sure it is a service issue, because I just received the notification of your reply just fine; by looking at the headers of that e-mail I could see the route is totally different... different o2 servers involved. After reading your answer I tried to get a 'verification e-mail' -those you are supposed to get when changing a password or username in MyO2-  from O2 and I'm still waiting.

[madasaf1sh]

@litso

The problem is all these emails come from different email services.

Customer Service emails to you will come usually via a CRM Tool

Password resets will normally come via a webserver linked to post fix and usually have an in built delay depending on volume of traffic

The forum comes out of Khoros-Mail which is the forum software.

I would have a chat with Fastmail Support, as from my opinion when we see things like this is its the 2 mail gateways trying to talk to each other .

And for the hop in the Mail headers it does look like a connection issue.

[litos81]

@madasaf1sh Thanks. I will contact Fastmail again with your suggestion about the 2 mail gateways trying to stablish a connection. The first time they told me to contact O2 because they saw that gap from O2 mail to Fastmail servers and suggested it could be a problem in O2 servers.
I'll post back once they reply...

[madasaf1sh]

@litso

I don't work for o2, but as an email administrator we are very possessive about our own email infrastructures 🙂

[litos81]

Hi,

I got an answer from my e-mail provider and they said:

"...our servers have been deferring emails from the sending server of O2.

We aggressively rate limit certain classes of sending servers, especially those that match certain criteria to stem the large number of spam we see from them, and this is whats happening here. You can read more about this here:

https://www.fastmail.com/help/technical/smtpchecks.html

In this specific case, the sending IP is 158.230.100.102 however the forward lookup of the server "cellgate.btcellnet.net" doesn't match that IP. This indicates that the FcrDNS for the sending server is not proper:

https://en.wikipedia.org/wiki/Forward-confirmed_reverse_DNS

This is a sign of poor configuration and matches the behavior of spamming servers which is why our servers are greylisting them. Just pass this along to the admin/helpdesk of O2 and they should be able to rectify this from their end."

@madasaf1shor anyone, is there any way I can make this message to arrive to the 'e-mail admins' in O2 for them to review?

Thanks.

[MI5]

@O2Emma was already looking into a different email issue where O2's ip addresses were being marked as spam and preventing customers from sending emails off mobile data.

She may know more and who to send this info to.

[madasaf1sh]

@litos81

Good old PTR records and fcrDNS, and isnt a sign a poor configuration, (its just what happens in very large enterprises with multiple acquistions and name changes )we have the same problem with one of our subsidiaries overseas.

fcrDNS is a weak form of Authentication (and not part of the DNS standard) RFC1912 is a discussion RFC for emails. better to use PTR or rDNS for this.

This isnt going to be fixed quickly (if at all) as that is a rename of a server and change of the DNS name.

This is more for the Internal IT team at o2.

Interestingly enough btcellnet.net doesnt have an mxrecord any more either but this is a dead domain.

[O2Emma]

Hi @MI5 I will pass this info on as it maybe linked to the ip address issue if our emails we are sending are coming up as spam with email providers.