cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Contributor
1,860 Views
Message 1 of 11

BT rejecting emails sent to my btinternet.com email address

A problem occurred while delivering your message to this email address. Try sending your message again. If the problem continues, please contact your email admin.
The following organization rejected your message: mx.bt.lon5.cpcloud.co.uk.


Diagnostic information for administrators:
Generating server: atl4mhob13.registeredsite.com

mx.bt.lon5.cpcloud.co.uk
Remote Server returned '554 5.0.0

0 Ratings
Reply
10 REPLIES 10
Highlighted
Contributor
1,851 Views
Message 2 of 11

Re: BT rejecting emails sent to my btinternet.com email address

Also seen this...
You do not have the permission to send the message on behalf of the specified user. Error is [0x80070005-0x0004dc-0x000524].

It has been working fine for the last 5 years, what has changed at BT?
0 Ratings
Reply
Highlighted
Contributor
1,827 Views
Message 3 of 11

Re: BT rejecting emails sent to my btinternet.com email address

I have read other similar topics on this forum and as the rejected emails are forwarded from my domain to btinternet.com then it looks like it could be a SPF checking issue again.
0 Ratings
Reply
Highlighted
Contributor
1,821 Views
Message 4 of 11

Re: BT rejecting emails sent to my btinternet.com email address

Dear BT please read the following...

 

Local policy for SPF results must consider forwarders

Forwarding is only a problem for mail recipients who check SPF and do not make provisions for any forwarders they have set up. First of all, realize that the SPF result is deterministic and defined by the SPF specification. You do not get any choice in the matter. However, any decision your mail software makes based on the SPF result is your choice. This advice concerns your "local policy" – how you treat SPF results.

Forwarders are generally set up by the mail recipient – and thus are the responsibility of the mail recipient. Mail senders publishing SPF records should not have to worry about forwarding. (Unless you count greeting card sites that let users enter an arbitrary MAIL FROM and don't follow web generated best practices. This is the sender's choice, in which case they will have to list such greeting card sites they use to send mail – or use "?all".)

Even a large ISP can do it. They might complain that they do not know what forwarders their users have set up. Maybe so, but they can:
1.provide a web-based configuration page to list forwarders.
2.default to not reject messages that fail SPF for users who have not configured their forwarders (but still add the "Received-SPF" header).
3.give users who have configured their forwarders the option of rejecting messages that fail SPF.

If tracking forwarders is simply not possible, then the ISP should not reject emails only because of SPF fail. But they can still use the MAIL FROM domain and SPF result for reputation. For example, the reputation of "example.com: PASS" may be quite different from "example.com:FAIL", and if the reputation of "example.com: FAIL" is bad enough, and ISP may start rejecting - just as they do for IP addresses with bad reputation now.

When configuring a forwarder, all you need to know is whether the forwarder performs sender rewriting, e.g. SRS.
•For non-sender-rewriting forwarders, accept all mail without checking SPF (any SPF results are meaningless). Hopefully, you (or your user) have chosen a forwarder that checks SPF before forwarding. If your implementation allows it, also check SPF for a "pretend" MAIL FROM that your forwarder could use (the original recipient RCPT at the forwarder before the email was forwarded). This verifies that the forwarded mail really came from your trusted forwarder.
•For sender-rewriting forwarders, do check SPF.

For ISPs, it should be obvious that this configuration is per-user. The decision on whether to reject an SPF "fail" is delayed until after the RCPT TO SMTP transaction command, so that per-user configuration can be consulted.

SPF Friendly Options for Forwarders

Forwarders may choose to implement SRS for all senders, only senders with SPF records, or only senders whose messages would fail SPF checks if forwarded. Another option would be to do a prospective SPF check (check if the message would get an SPF Fail if sent from the forwarder's server) and reject the message to be forwarded with 551 User not local; please try <forward-path> (See RFC 821 paragraph 3.2 for details).

0 Ratings
Reply
Highlighted
Distinguished Guru
1,793 Views
Message 5 of 11

Re: BT rejecting emails sent to my btinternet.com email address


@mikedabikewrote:
I have read other similar topics on this forum and as the rejected emails are forwarded from my domain to btinternet.com then it looks like it could be a SPF checking issue again.

Hi.

Stock answer :-

Stop using btinternet.com email addresses, if you've not done so - set up a non ISP email address like Gmail.

The issue will NOT get fixed, BT don't investigate - otherwise this would not keep occuring.

Highlighted
Aspiring Contributor
1,770 Views
Message 6 of 11

Re: BT rejecting emails sent to my btinternet.com email address

I second your thought
0 Ratings
Reply
Highlighted
1,761 Views
Message 7 of 11

Re: BT rejecting emails sent to my btinternet.com email address

As a reciever of emails I have now been told verbaly by contacts that emails to me have been bounced.

These were emails sent to distribution lists and with attachments.

BT advice is to add their addresses to the 'Safe Senders' list.

Since these addresses are already in my Contacts, I find this ridiculous.

0 Ratings
Reply
Highlighted
Contributor
1,683 Views
Message 8 of 11

Re: BT rejecting emails sent to my btinternet.com email address

I have tried updating safe senders list, it does not fix the SPF rejections.
0 Ratings
Reply
Highlighted
Contributor
1,682 Views
Message 9 of 11

Re: BT rejecting emails sent to my btinternet.com email address

Dear BT why can't you fix this SPF email problem?

It is happening again today, here is the full reject message another person got sending to mydomain which forwards to my btinternet email (names changed, e.g. to "someone", "mydomain", etc) ...

Delivery has failed to these recipients or groups:
someone@btinternet.com
A problem occurred while delivering your message to this email address. Try sending your message again. If the problem continues, please contact your email admin.
The following organization rejected your message: mx.bt.lon5.cpcloud.co.uk.
Diagnostic information for administrators:
Generating server: atl4mhob02.registeredsite.com
someone@btinternet.com
mx.bt.lon5.cpcloud.co.uk
Remote Server returned '554 5.0.0 PABtAHgALgBiAHQALgBsAG8AbgA1AC4AYwBwAGMAbABvAHUAZAAuAGMAbwAuAHUAawAgACMANQAuADAALgAwACAAUwBNAFQAUAA7ACAANQA1ADQAIABNAGUAcwBzAGEAZwBlACAAcgBlAGoAZQBjAHQAZQBkACAAbwBuACAAMgAwADEAOAAvADAANwAvADEAOQAgADEAMQA6ADQANwA6ADEAOQAgAEIAUwBUACwAIABwAG8AbABpAGMAeQAgACgAMwAuADIALgAxAC4AMQApACAA4gCsIBwgIABZAG8AdQByACAAbQBlAHMAcwBhAGcAZQAgAGwAbwBvAGsAcwAgAGwAaQBrAGUAIABTAFAAQQBNACAAbwByACAAaABhAHMAIABiAGUAZQBuACAAcgBlAHAAbwByAHQAZQBkACAAYQBzACAAUwBQAEEATQAgAHAAbABlAGEAcwBlACAAcgBlAGEAZAAgAHcAdwB3AC4AYgB0AC4AYwBvAG0ALwBiAHUAbABrAHMAZQBuAGQAZQByAD4A'
Original message headers:
Received: from mail.hostingplatform.com (atl4qibmail13pod0.registeredsite.com [10.30.71.55])
 by atl4mhob02.registeredsite.com (8.14.4/8.14.4) with ESMTP id w6JAlH5C027812
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL)
 for <someone@btinternet.com>; Thu, 19 Jul 2018 06:47:17 -0400
Received: (qmail 9415 invoked by uid 78); 19 Jul 2018 10:47:17 -0000
Delivered-To: mydomain.com-mike@mydomain.com
Received: (qmail 9410 invoked by uid 0); 19 Jul 2018 10:47:17 -0000
Received: from unknown (HELO atl4mhib03.myregisteredsite.com) (209.17.115.138)
  by 0 with ESMTPS (DHE-RSA-AES256-GCM-SHA384 encrypted); 19 Jul 2018 10:47:17 -0000
Received: from lonmail9.anotherdomain.com (lonmail9.anotherdomain.com [155.140.133.144])
 by atl4mhib03.myregisteredsite.com (8.14.4/8.14.4) with ESMTP id w6JAlEJg024843
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL)
 for <mike@mydomain.com>; Thu, 19 Jul 2018 06:47:15 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
  d=uk.anotherdomain.com; i=@uk.anotherdomain.com; l=13153;
  q=dns/txt; s=20151010; t=1531997235; x=1563533235;
  h=from:to:subject:date:message-id:references:in-reply-to:
   mime-version;
  bh=uskZNmzyh9uYcl3bVX19xE7j/rIPdbJEMLqwxcsaZAg=;
  b=e3aIq2j+notV8iB0qnMIK7MDxZpMHdOyomEb11wNN0AQXnqSv1/HVf5W
   RNHJnogkOq2+fg5jmkgIdaCOdCTz/UTdV3SKHEUrAvTexbs8KKOHEZZz2
   DTWsUyYaClw5BnvLi4zQvegcLcK3PN2ETGhvy6c6heRQeCkvCZcY2Uw3D
   2lnmMrqjPC3oVWrVmpblLxwIFfP7yYZXNaDlxIoi+T2kqQ40TdVLxfoGV
   ajPUf/Y6vcGHf3yVeqiQ7VmxcVjCwbQCa6UJHnzWLbAbVUhW0wSEDiyYn
   CyTdwesR+xENM1YLOTdKa36lYxgJ976Xv4yfbRGkLLXgZRDnldDZqKeA3
   w==;
X-IronPort-AV: E=Sophos;i="5.51,374,1526338800";
   d="jpg'145?scan'145,208,217,145";a="56351072"
X-HopCount: *
X-Attachment-filename: image001.jpg
X-IronPort-AV: E=Sophos;i="5.51,374,1526338800";
   d="jpg'145?scan'145,208,217,145";a="294110663"
X-IronPort-AV: E=Sophos;i="5.51,374,1526335200";
   d="jpg'145?scan'145,208,217,145";a="292443378"
From: Simon XXXXXX <Simon.xxxxxx@uk.anotherdomain.com>
To: "'mike@mydomain.com'" <mike@mydomain.com>
Subject: FW: [EXTERNAL] RE: Thunder Fri Dec 21st Roundhouse Chalk Farm
Thread-Topic: [EXTERNAL] RE: Thunder Fri Dec 21st Roundhouse Chalk Farm
Thread-Index: AdQfOSIA46M0LUvgQXSPZ1MlJakKEQADqrUgAAGCkaA=
Date: Thu, 19 Jul 2018 10:47:13 +0000
Message-ID: <3ff2252f1bb94bd9a6d974f3357e35a2@uk.anotherdomain.com>
References: <ac1dda8b23d1407491d4891ba012fecf@uk.anotherdomain.com>
 <A14E5B24D51A489B8C47194368584D70@BOB1>
In-Reply-To: <A14E5B24D51A489B8C47194368584D70@BOB1>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-country: GB
Content-Type: multipart/related;
 boundary="_004_3ff2252f1bb94bd9a6d974f3357e35a2ukanotherdomaincom_";
 type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-CFilter-Loop: Forward
X-Custom-SpamThreshold: 16
X-SpamScore: 5.9
X-MailHub-Apparently-To: mike@mydomain.com
X-MailHub-Forwarded: Yes

 

0 Ratings
Reply
Highlighted
Distinguished Guru
1,660 Views
Message 10 of 11

Re: BT rejecting emails sent to my btinternet.com email address

Hi.

BT will not do anything, they are in complete denial. The mail team do not see it as their problem, and I'm aiming this at Simon-D.

The thing to do is stop using btinternet mail. Set the forwarding to a gmail account instead.

This problem only manifests itself when sending to btinternet accounts, not others. It is therefore obvious where the fault lies, but BT will not fix it.

0 Ratings
Reply