cancel
Showing results for 
Search instead for 
Did you mean: 

NTL bouncing emails back to sender

jellielli
On our wavelength

I am administrator fir a local u3a. We send out bulk emails to our members. 
Two members have email accounts with ntlworld.com. The emails which I send to them bounce back with the following message:

This is an email abuse report for an email message with the message-id of 010b017ba2b1b903-f93bb76f-e3e1-4774-8bef-c63c1a66cfbb-000000 received from IP address 46.32.240.39 on Wed, 01 Sep 21 18:49:21 UTC.
This is the list of the complaint emails:

I have removed their email address for protection. I have asked both members to add my admin email address to their Contacts so the emails shouldn’t bounce back. 
Any ideas please?
24 REPLIES 24

Hi @ABealing

Welcome back to the community!
Sorry to hear you're having some issues with your email at this time. If you add the sender to your webmail address book, it'll add it to an allow-list or  whitelist, this should prevent this issue happening as it'll recognise the email as a known and safe sender. Please let me know if this resolves your issue. 

Here to help 🙂
Virgin Media Forums Agent
Carley

ABealing
On our wavelength

Thanks for the response.

I had already done as you have suggested and added the Beacon email address as a contact in my Virginmedia email accounts:  noreply@u3abeacon.org.uk  which is the address which appears on the messages concerned.  Presumably this would prevent such messages being diverted to Spam but the issue is that some, not all, are not being received at all, but are now being received to my gmail account following duplicating the email forwarding to both virgin and gmail.  This would appear to indicate to me that the issue is with Virgin's servers rejecting the messages rather than sending them to my mailbox as spam.  This is causing an issue as these messages are important to me.

 

Thanks for getting back to us @ABealing.  

I will have a look into this to see if we can find a resolution on your behalf.  I hope your work around with the gmail account is helping you in the mean time?

Regards


Lee_R

ABealing
On our wavelength

Thanks for the further response.  Yes the gmail duplicate forwarder has captured a message not received to Virgin (Spam carefully checked) so reasonably confident that this is working but its not ideal.  I have several Virgin email addresses on my account to which this issue may apply.  I will be away now for a week so may not be able to respond during this time.  I hope you are able to identify and eliminate the problem.  Thanks again.

Glad you have a workaround although I appreciate it isn't ideal @ABealing

I understand Lee is looking into this as per his previous message so he will follow up with you on this thread as soon as there's any updates. 

Cheers

Ayisha_B
Forum Team

New around here? Check out the do's and don'ts, in our Community FAQs


ABealing
On our wavelength

Just to let you know I received another of these Beacon emails into my gmail account but not the Virgin one (spam checked carefully) on Wednesday, so the issue remains.

coenoby
Very Insightful Person
Very Insightful Person

@ABealing wrote:

Just to let you know I received another of these Beacon emails into my gmail account but not the Virgin one


Just a thought but it might help VM if you could post a redacted version of the email headers for one of those emails you have received in Gmail but not  your VM email account.

Here is a quick outline of how to get the email headers from Gmail. https://www.lifewire.com/how-to-see-full-email-headers-in-gmail 

Note the part VM needs are the pages below the first section that's headed "Original message". Scroll down from that and you'll see a long block of text that starts

Delivered-To: @myaddress@gmail.com
Received: by xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Copy all that document from Gmail into a text document and then edit all occurrences of your email address, for example to "myaddress@gmail.com", and redact your IP address to "8x.x.xx.106" for example. Then paste that redacted version into you post here.  By the way, there will probably be a big block at the end of the headers which will just be the contents of the email - no need to post that here.😉

Hopefully that will help to identify what would have caused VM to reject or delete that email when it was received by them. Without an example I would image VM are working in the dark to identify the cause..

Coenoby

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media.

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

Hi @ABealing

Sorry to hear this issue is still ongoing for you. 

If you follow the steps @coenoby has kindly mentioned about posting the message header. We can certainly look into this further for you and see if this is something we can raise an IT ticket for to resolve. 

Here to help 🙂
Virgin Media Forums Agent
Carley

ABealing
On our wavelength

Thanks.  This makes sense to me and I have been expecting a request from Virgin for such information.  Thanks for the instructions.

ABealing
On our wavelength

I thought it was already under investigation?

Details of one of the messages below.  Please note that specific addresses have been amended as XXXXXXXXXXXX

Not all such messages are being rejected by Virgin but we are loosing a number of them.

Thanks

 

 

Delivered-To: XXXXXXXXXXXXXX@gmail.com

Received: by 2002:ab3:dcca:0:b0:41c:8a6f:756e with SMTP id g10csp948975qnl;

        Fri, 20 May 2022 07:47:02 -0700 (PDT)

X-Google-Smtp-Source: ABdhPJzu0niC/aYwGzJu5xafm3fjBjsa6O44odTN81ZR/hAlR2V9Tt/BcKhbmYhc0oTEAVMFbzhP

X-Received: by 2002:a05:600c:a44:b0:38e:3ce3:3148 with SMTP id c4-20020a05600c0a4400b0038e3ce33148mr8364234wmq.26.1653058022328;

        Fri, 20 May 2022 07:47:02 -0700 (PDT)

ARC-Seal: i=1; a=rsa-sha256; t=1653058022; cv=none;

        d=google.com; s=arc-20160816;

        b=FMHwUHzk19k72sCyPlbBRceVtRMlc2g5G/TFvbIKSZTi4h/x58grqYOX5nkBOskoDc

         xLLyQYW1kyK+v3qP2aOo/otztqH6+E2Ujr1vuU+ykgUMiNNqcTog88oDIk0t84lE3qK+

         WDdbNhICmISh1Qb20rnbU4GEOM8Xl+jZ1eSlTjNZxnm1wHriCPlKsAlWbQ38AbpkACxP

         zSPoZe+n7YF2Q88xgbXOEtFky34f7t05ebCE2nnPn1nzXSARP0XAHgE+Iq2OTDFD+tEi

         VLDQ3AyQXjZu2n+m0tz5DTCzzdmIA6n4Jzie/bJ3Fh8PI1iolIRGiLFacHwt8Fhj0su9

         wxuA==

ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;

        h=to:reply-to:subject:message-id:mime-version:from:date

         :dkim-signature;

        bh=534NeI+FnMPbO4UMtNVUefSvZ1sRl6OZIuJQ1HdGi1Q=;

        b=XzaSG1QQFv+w/0xgpPiVqAFTSJ/8Xb51QvraSU1u3pMyQzzbmuC7ysOL3zcYZuQvXo

         XAzUUD7S6Fp1clKfJxR0FU4u2sdygzgzU2AdeKNsJnHV82hHchlKxza6Cxkj7LiHGAoh

         RrbyA86WfPF+wUy+Pn3RqknQzdJDQ4oo6nFHkc9sO6iSkBktAKRHQ3bKRF26taHF2/Ob

         1KFl9hly9ZunI36l5u9+23+JzzE7xBYA68hA+PYY2aYAYEDRhyTbWOtfJR3tmO6VtjtN

         Uy64j92ibLnPnIbRxtZdStHFiMiC95hiRuocdW+ob90byHFIPwkTvK4Y3pRgQIqyl+eI

         9q0Q==

ARC-Authentication-Results: i=1; mx.google.com;

       dkim=pass header.i=@u3abeacon.org.uk header.s=s1 header.b=EgYElrdT;

       spf=pass (google.com: domain of srs0=quok=v4=em.u3abeacon.org.uk=bounces+2125344-7690-XXXXXXXXXX.co.uk@clustered-mail-forwarding-05.uk designates 213.171.216.220 as permitted sender) smtp.mailfrom="SRS0=QUOK=V4=em.u3abeacon.org.uk=bounces+2125344-7690-XXXXXXXXXX.co.uk@clustered-mail-forwarding-05.uk";

       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=u3abeacon.org.uk

Return-Path: <SRS0=QUOK=V4=em.u3abeacon.org.uk=bounces+2125344-7690-XXXXXXXXXX.co.uk@clustered-mail-forwarding-05.uk>

Received: from forwarder.cmp.livemail.co.uk (deferred01.cmp.livemail.co.uk. [213.171.216.220])

        by mx.google.com with ESMTPS id g10-20020a05600c4eca00b00395b8e96eb0si3274535wmq.195.2022.05.20.07.47.02

        for <XXXXXXXXX@gmail.com>

        (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);

        Fri, 20 May 2022 07:47:02 -0700 (PDT)

Received-SPF: pass (google.com: domain of srs0=quok=v4=em.u3abeacon.org.uk=bounces+2125344-7690-XXXXXXXXXXXXXXXXXX.co.uk@clustered-mail-forwarding-05.uk designates 213.171.216.220 as permitted sender) client-ip=213.171.216.220;

Authentication-Results: mx.google.com;

       dkim=pass header.i=@u3abeacon.org.uk header.s=s1 header.b=EgYElrdT;

       spf=pass (google.com: domain of srs0=quok=v4=em.u3abeacon.org.uk=bounces+2125344-7690-XXXXXXXXXXXXXXXX.co.uk@clustered-mail-forwarding-05.uk designates 213.171.216.220 as permitted sender) smtp.mailfrom="SRS0=QUOK=V4=em.u3abeacon.org.uk=bounces+2125344-7690-XXXXXXXXXXXXXX.co.uk@clustered-mail-forwarding-05.uk";

       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=u3abeacon.org.uk

Received: from localhost (unknown [127.0.0.1]) by forwarder.cmp.livemail.co.uk (Postfix) with ESMTP id E753AC8789; Fri, 20 May 2022 14:47:01 +0000 (UTC)

X-Virus-Scanned: amavisd-new at smtp-forwarder-out-05.cmp.livemail.co.uk

X-Spam-Flag: NO

X-Spam-Score: 2.644

X-Spam-Level: **

X-Spam-Status: No, score=2.644 tagged_above=2 required=6.3 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FORGED_REPLYTO=2.503, HEADER_FROM_DIFFERENT_DOMAINS=0.248, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001] autolearn=disabled

Authentication-Results: smtp-forwarder-out-05.cmp.livemail.co.uk (amavisd-new); dkim=pass (2048-bit key) header.d=u3abeacon.org.uk

Received: from forwarder.cmp.livemail.co.uk ([127.0.0.1]) by localhost (smtp-forwarder-out-05.cmp.livemail.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TyWkXh6L3d_g; Fri, 20 May 2022 15:47:01 +0100 (BST)

Received: from mailserver.cmp.livemail.co.uk (smtpin-04.cmp.livemail.co.uk [10.44.166.67]) by forwarder.cmp.livemail.co.uk (Postfix) with ESMTP id 1B9E7C878B for <XXXXXXXXXXXXXX.co.uk>; Fri, 20 May 2022 15:47:01 +0100 (BST)

Received: from o1678987x144.outbound-mail.sendgrid.net (o1678987x144.outbound-mail.sendgrid.net [167.89.87.144]) by mailserver.cmp.livemail.co.uk (Postfix) with ESMTPS id C0E82C5A53 for <XXXXXXXXXXXXXX.co.uk>; Fri, 20 May 2022 15:47:00 +0100 (BST)

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=u3abeacon.org.uk; h=content-type:from:mime-version:subject:reply-to:to; s=s1; bh=534NeI+FnMPbO4UMtNVUefSvZ1sRl6OZIuJQ1HdGi1Q=; b=EgYElrdT6+JpCVsQ4JmbBWMa8U9lUn8p48hQopIJgFuBnwJJMqH4lFgFdjeoL+2e9XVR TJM4jG/Fd+G2I3p9/Gm7TNSqTCf3wU+C7ltAkVOw3m+RVWOQ/114lPqAS0br6NzlvHV8JH 5AKy0ZutA7Sj5Ds8HuZnWS0lScc+jT0IU7mSHjgN1ZjkjpHMWh43vkQW8mlKuZFYRNBPJv VTy80UGrU/NgoPggMjIYwvEEr3MDKTn2zuyZ0PCZWsP8GC88Web6OPh/8BEFYMJ02g5eVL EDNgaBM+3uH3MoQ/gkOzwF9dSWyOn4CsIouPmUblNEZSNa53gQefiPNIc7PaSR/w==

Received: by filterdrecv-5645d9c87f-x5shg with SMTP id filterdrecv-5645d9c87f-x5shg-1-6287A9E2-54

        2022-05-20 14:46:59.068295557 +0000 UTC m=+3776570.657882910

Received: from MjEyNTM0NA (unknown) by geopod-ismtpd-2-1 (SG) with HTTP id 88chiBegS8uyvowr73rk4w Fri, 20 May 2022 14:46:58.806 +0000 (UTC)

Content-Type: multipart/alternative; boundary=fe714cdf3b61c8fc4881ad9da7849dcb578341c61907afdbb91413aa2c07

Date: Fri, 20 May 2022 14:46:59 +0000 (UTC)

From: XXXXXXXXXXXX via XXXXXXXXXXXX U3A <noreply@u3abeacon.org.uk>

Mime-Version: 1.0

Message-ID: <88chiBegS8uyvowr73rk4w@geopod-ismtpd-2-1>