Hi My dad is having intermittent problems with incoming email. The sender receives a delay warning email but ultimately the email doesn't arrive, and he has looked in Spam folder but not there. In one instance recently only the final email of a thread was affected, with emails successful going back and forth within a short space of time. We don't dont know the extent because we only know about the people who've told us the emails are delayed. Dad has missed some important emails due to the problem.
He spoke to VM offshore technical support, having sent a test email and asking me to send a test email, the advisors diagnosis was that there wasn't a problem because both emails were received. But this is intermittent and the whole issue is that we don't know what's causing it. There definitely is a problem. Please can someone offer advice on where to go from here. Thank you
All of this suggests to me that VM are rate limiting the incoming mail from this person's father's senders. Of course it would help to see the mail headers of a delayed mail. It is unlikely that the OP's father will ever be able to get the bounce message and the mail headers of a failed mail (where the rate limiting has delayed the incoming mail so much that the sending server gives up).
Superuser 2017/18 Use Kudos to say thanks Mark answer as "helpful" only when the problem is solved Please don't send me private messages unless I ask you to. I do not work for VM. The advice I give is based on my best understanding of VM policy and practice. You rely on it at your own risk.
As Howard has explained it would appear that your father's expected emails are subject to rate-limiting. This would result in either delayed delivery or a failed delivery message being returned to the sender.
For the former I'd need the Headerdata from one of the received emails where delivery was slow.
For the latter I'd need the Header from the failed sent mail - so your father would need to request that from the sender.
I've sent you a PM (purple envelope icon, top right of page) and the requested data can by copy/pasted into a reply to that. Once I have the requested information I can inspect it to determine what's happening here. If there is anything out of place then I can query it with Postmaster.
I'm having the same problem and it's getting really annoying - a message that I know was sent yesterday evening (because it reached another address) still hasn't arrived, and others have been delayed by 12 hours or more, while some have got through as normal. This means that sequences of messages can arrive out of order which can cause a lot of confusion. Here's an anonymised header from one delayed message (all personal email addresses removed); can someone please get this fixed once and for all, as it keeps happening despite many complaints on these forums. It would also help if VM published an email address to which such complaints could be directed, rather than users having to post on these forums.
Incidentally, although this message is from a mailing list, personal messages are affected in the same way.
Return-Path: <email@example.com> Delivered-To: firstname.lastname@example.org Received: from md25.tb.ukmail.iss.local ([126.96.36.199]) by mc24.tb.ukmail.iss.local (Dovecot) with LMTP id IDL8LOYIkFirQQAAsNwiEA for <email@example.com>; Tue, 31 Jan 2017 04:48:14 +0100 Received: from mx2.tb.ukmail.iss.as9143.net ([188.8.131.52]) by md25.tb.ukmail.iss.local (Dovecot) with LMTP id bduEArZhf1j1GgAARVaxXw ; Tue, 31 Jan 2017 04:48:14 +0100 Received: from mout.kundenserver.de ([184.108.40.206]) by mx2.tb.ukmail.iss.as9143.net with bizsmtp id ernz1u02W2sout801ro54o; Tue, 31 Jan 2017 04:48:11 +0100 X-SourceIP: 220.127.116.11 X-CNFS-Analysis: v=2.2 cv=GON4KqFK c=1 sm=1 tr=0 a=pO51TJzRmtPo282mSZN23Q==:117 a=5QEp2dGUwE1iF+XUehnhUA==:17 a=IgFoBzBjUZAA:10 a=54V8FjglJEe5w-i4kO8A:9 a=BrDiTsk0AAAA:8 a=aLFAKki5AAAA:20 a=4HOdOh6HAAAA:8 a=OdQhJ_uUAAAA:8 a=ktDEk6VYAAAA:8 a=v5347yTHUhqulS25VicA:9 a=U2ImjhTuCAg0kX09:21 a=g4f9cermIHObDj1M:21 a=QEXdDO2ut3YA:10 a=2WduZPHrFYoA:10 a=JtyCukcpeW8A:10 a=SSmOFEACAAAA:8 a=lzloa5mkAAAA:8 a=HIxhJnMaAAAA:20 a=3j4BkbkPAAAA:8 a=JqEG_dyiAAAA:8 a=WauQcD5LzMa2p8a6BDQA:9 a=XeqNa_10aWwzuhqm:21 a=XGqn3IuNCgC9k8AP:21 a=95_2vYz-qhRgqO0q:21 a=_W_S_7VecoQA:10 a=_Tg1yBZqekAA:10 a=p403mkujtbAA:10 a=Z27TPHgGRWoA:10 a=fK1jZSgjKPFatbRoI9mg:22 a=74BrXtsMU15uU1zEOF9z:22 a=9WIJVKLz5KThS2eAdXGu:22 a=n6yzXxB2y_9RtbUUhp59:22 a=zjWhRoSqWz9hl55Hdlzg:22 a=O41BpILyKXd2m_I6J2tP:22 a=sJh6Skxnaek_REti9G3X:22 a=U04FSIGNRx3ScUM3zguK:22 Received: from [18.104.22.168] ([22.214.171.124]) by mx.kundenserver.de (mxeue005 [126.96.36.199]) with ESMTPS (Nemesis) id 0MAXZm-1ceCG743Tu-00BbDC for <firstname.lastname@example.org>; Mon, 30 Jan 2017 14:27:26 +0100 Received: from a7-13.smtp-out.eu-west-1.amazonses.com ([188.8.131.52]) by mx.kundenserver.de (mxeue005 [184.108.40.206]) with ESMTPS (Nemesis) id 0MYpkc-1d2SJ541R4-00VTVu for <xxx@xxx>; Mon, 30 Jan 2017 14:27:25 +0100 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=ihchhvubuqgjsxyuhssfvqohv7z3u4hn; d=amazonses.com; t=1485782845; h=Date:From:Toubject:Reply-To:Message-ID:Mime-Version:Content-Type:Feedback-ID; bh=l8HLbIur6wIvvjVtn4LFhExvTpQiQIMS/5RsOpFF7xk=; b=Vk2fh+q7sirCauZ39gQ58jSyAYEDFP//YD7CJJj0Ygd0LQK7KAvHzBWS6d6uP4Zw Y7FSVG5Elku5LfQ+ajmgDX+jGXYjPnIxDx0D5Fp7TW1Jnk2qE6LoTLpU9Ff/jRWyb3n B7/UIvre4CW1KmD95MVelcE6BX1Na1mD9KRFqAQc= User-Agent: CodeIgniter Date: Mon, 30 Jan 2017 13:27:25 +0000 From: "Reading & Mid-Berks CAMRA" <email@example.com> To: xxx@xxx Subject: =?utf-8?Q?Ale_Trail_and_Pub_of_the_Year?= Reply-To: "Reading & Mid-Berks CAMRA" <firstname.lastname@example.org> X-Sender: email@example.com X-Mailer: CodeIgniter X-Priority: 3 (Normal) Message-ID: <firstname.lastname@example.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="B_ALT_588f3f3d03769" X-SES-Outgoing: 2017.01.30-220.127.116.11 Feedback-ID: 1.eu-west-1.nG4g0bTJHi9SeqWGDrBHmhLY8i084RLvggAMytR6RpE=:AmazonSES X-UI-Out-Filterresults: notjunk:1;V01:K0:0JZiykRIGgc=4zRZw3cNH3iMVW0CtldwQ 6JuSHX3oF/aUAQThpjHjmXPgA70Y1L10lRAqt7ylmxR1kmmSRztQjAXSTHx+LIe+0u8b++2mb q7aTW2x+YwQ9VuFQgr7zDDyq4LPPD7X6/1Colh4dCazMRJQnLvJXjcNOHFg9JHKc5e+7Wed1M yTAvZkgrw+Djyyut1dnsc7nFDR7DhFctZHXVBjsBlij5NZpJEpzM/LlImJIiyh4XvZZCkd/7q lfOe5Cd+4rh7JZ+Jvfw6TPIO/i2DueHsq6J808R8yR1UlA3iFwxOMOC2uTuztPQmVFS2jekCj q7DB4yybKDCB5f7lYpnMDTeXjyiqnODJZ9eEJxGmuE0Uir2WX/nE84scX+0zZlILoOuvhbHw7 rIqeHjGP2sqoGapEthjxxqblfOyn2iojQrExJPMGH7wDXqJ1apL3e0sDuBRBhyb8GzHrPyUd4 egJ2wRJ2l+mmi4vhNQpzJ+CZZVN/X3Qk4h+Yq1VJKo1QPenj8NLFnRldrNP2H0oLZIYHnJgJ9 rnFhD5iFR7/rAsTX8YQXSLn8V3kudAGV0ncCR0myHorfDxtgEvJ5wbL+VMNV+7+UgnOa4SMLx W840SW0jZJXrQ3/DUpg6kGzcr52j/ggXCjxHpdTug6V3RdBpaE85BBBvcJSXRGz690CMcHADQ fjGoagRivIed6AZ4WTC6kDBu4L10cmkpuTOBNXJkzUv6X3Ge9O0lDwOR2ShiedZY0xCzVZ6ey SaZnLaSnsFM0qe4elOPIq6ibXUApvDYuADEhHkx42mYqyj3HG5vXFW0aYnmW22IB7TqizTZ8Y HMPh5PwY8TEkT2n2FARgJO+oYgBRoSvW/mRyHU4ZcaTNIGjDe7RNL5ixuIIKn5+crs9cI1Sz4 PMgNQdQ0SeqC+GJHRCdk3rY7wgl8uHZP1hWcuopCuMTeMtYyrxZq5PG4DAiRJ34++F2M0xObb zgdy7t28H9xWh8l4XpV6auzx6Bj94zgcGUGFwXsMsTpT+dYcBJeRYwNph09GcneXjHYMldaOf F2490LxRr4n3+tJb3fgvxxdk3XOjOaHV4Tc11SC4b/IMnSQ+qaPU3qQ1LC19WFM5hgJMJMybh Av/ukNuZMgdq6yAY0iDfr7VqXd4hYCPNh5TAqyJN66ngcGWHFdR+63kNw== X-Antivirus: avast! (VPS 170130-0, 30/01/2017), Inbound message X-Antivirus-Status: Clean
This is a multi-part message in MIME format. Your email application may not support this format.
Sorry about the slow email, we are investigating a few problems at the moment and it may be down to that. Please keep an eye on this thread for updates Email: Sending and Receiving 30/01/17 and if you are still having problems after it is resolved please let us know.
Thanks; I'll monitor that link, but given you know there's a problem, why isn't the service status web page reflecting it? (I looked just now and it said broadband was fine, I'm pretty sure I checked before the original post as well). If you put up the fact that there was a known problem with email on that web page, we wouldn't need to post things here.