cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Aspiring Contributor
29,792 Views
Message 13 of 166

BTinternet rejecting all our emails

Go to solution

I am the technical contact for Castweb. We distribute email bulletins of work and casting opportunities for actors to subscribers who have paid for the service. Our email is not spam.

Among our actor and agent subscribers are a dozen BTinternet mail users who, since 16 October, are unable to receive our bulletins because they are now being falsely identified as spam by BT. Previous to that date, there was no problem, for many years.

 

These BT customers are now unable to receive what they have paid us to send. Moreover it appears the missing messages are not placed into any spam folder, they are bounced to us without any notification to the recipient.

 

We can't now send a single email to any BTinternet address.

Our emails are returned:


Reporting-MTA: dns; doris.castweb.co.uk
Remote-MTA: dns; btinternet.com
Final-Recipient: rfc822;[redacted]@btinternet.com
Original-Recipient: rfc822;[redacted]@btinternet.com
Action: failed
Status: 5.2.2 (IP REPUTATION BAD  (please check for IP address listing on reputation services))

This is false! Our mailserver IP 217.146.109.224 (doris.castweb.co.uk)  is NOT blacklisted by any RBL that I can find. EG http://whatismyipaddress.com/blacklist-check comes up clean on all 80 services it knows about. Our IP appears to be blacklisted by BTinternet alone. Mail delivers fine to all other networks including customers who use Yahoo addresses.

 

We have DNS reverse lookup and SPF policies in place that should make it crystal clear that this is legitimate email.


Can someone please tell me who at BT I need to contact to resolve this issue on behalf of our and their customers? Alternatively, what can our BTinternet customers do to ensure they receive the information they have paid us for, and BTinternet to receive?

0 Ratings
165 REPLIES 165
Highlighted
5,421 Views
Message 1 of 166

failure notice - 550 SPF CHECK FAILED

Go to solution

I tried sending an email to my personal account from my work email and got the below message;

 

Hi. This is the qmail-send program at yahoo.com.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<  >:
Connected to 65.20.0.49 but sender was rejected.
Remote host said: 550 SPF CHECK FAILED

--- Below this line is a copy of the message.

Return-Path: <  >
Received: (qmail 83757 invoked by uid 1000); 25 Oct 2013 12:51:13 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1382705472; bh=MnZopVtj12NO/oIQ4z/0qYDvnqQ8UXxOYjnxwh66WOk=; h=X-Yahoo-ForwardOnly:X-Yahoo-Forwarded:Received-SPF:X-YMailISG:X-Originating-IP:Authentication-Results:Received:Received:Received:Received:To:Subject:Message-ID:From:Date:Content-Type:MIME-Version:X-KeepSent:X-Mailer:X-Disclaimed; b=gk5yoxsjNhIASABlFpwM8jAOdzYUsVoec6Z0EvDZCv2cx4i8cNKmB2LLd/sKFH21JHG9Lldpr40ApVTsou/0c/rxtN4iMfxM6j98eBHjofczALA3S5eiuCSZu5Y5hh9QCWOiLRti8cu/oGkxCAtCe7aI4bEJDr7un5hu++FoG9Y=
X-Yahoo-ForwardOnly: from   to

X-Yahoo-Forwarded: from   to

Received-SPF: pass (domain of z  .com designates 194.175.223.136 as permitted sender)
Sy9OVFMgb24gMjUvMTAvMjAxMyAxMjoxOCAtLS0tLSBGcm9tOiBFbGxlIE1j
UGh1biA8ZWxsZUBsb25kb252aXNpb25jbGluaWMuY29tPiBUbzogImpvYW5u
YS5saXR0bGVjaGlsZEB6ZWlzcy5jb20iIDxqb2FubmEubGl0dGxlY2hpbGRA
emVpc3MuY29tPiBEYXRlOiAyMy8xMC8yMDEzIDE3OjI0IFN1YmplY3Q6IExv
bmRvbiBWaXNpb24gQ2xpbmljIERlYXIgSm8sIFRoYW5rIHlvdQEwAQEBAQNt
dWx0aXBhcnQvYWx0ZXJuYXRpdmUDAzEzAgN0ZXh0L3BsYWluAwMwAgN0ZXh0
L2h0bWwDAzgCTFZDIEJyb2NodXJlLnBkZgNhcHBsaWNhdGlvbi9vY3RldC1z
dHJlYW0DAzACVUsgR3VpZGUgdG8gTGFzZXIgRXllIFN1cmdlcnkucGRmA2Fw
cGxpY2F0aW9uL29jdGV0LXN0cmVhbQMDMA--
X-YMailISG: ubMYdLEWLDuvnJZUpzFipl86qI.38Ib.TiRarcS.q7ZFrCJM
f.u5zeWwmF_t0IjaXryqmHBWi5zrjiQKNAC4tNZ2o9FSIt5qYwdn8SHRTY44
yJ_x1e8427FdGMooB5em4OKIQ0YKs9MS12FfsW0Debisv6UehxBKs4R0F80_
H_IsFBQFuodwIUsZ14ESnriD36w6JB6TqmgpV010LS2GZjs6LGtpCWpuM8FM
oWiHfRZIIEEHxF3ShaNWBaRhig6u2FlewmoEK8m0s1H8XE_OO_qh9G14GTbY
iPZzwTx0WDgouUlApdl2jcOywE8ufMfKCby7LpzTMMjYUrtmY1KhQTOOCkAa
YMOxXlugWWrwA54Ep8tYW0FOE4ciKpgM17XCZLtOVhSt7gsGhrk_cDygB7Tb
G2iat_WQhtvI1H9jPP3oCjLRBPORI8drZuNXcxJ0OwtAy1zrnzEm4ZMQmiMp
eJJvz.zP38i_Msi1oGkQZEoK9D06Up2NCLR07Z7FbdVNY7fyCfMoNK6oCHC4
Do7c2PNa95y95G7KWwgZTdesK27aPdBUBe1RKPiyV7eBc55Bx8Tfr7e8.Zkx
JdUy3wnBYvIxzxN9sw8U9rL0w6aM3auFojz1.s2MB6c52QIeh8WOdkTT2beG
ZZPt7wN0W9Qp6rb3SrMg5IMwBwMaaqk_XCp.BZaLRJL_bK9JzQxs.EYLhsJ3
.sFKjuiCIM.1q67PtSfkNggJQK9vfzsk.44lDq4M7WmbmswuqWhIGJkCYjTP
mQFOHFVHg.RSJCLigsp0lusWPFIVlzi3aHOT.zgXWBzRs_NVmyVoiPJ8sWTt
anWnn76Bp3KqsVUWmgkyta3qei6umXc0zQPO_QO_EY5COgxtvh6dWzTqS.SH
YVmj2fws2z2CcnTkQinki9rn68RthrvZN9oIpHQ7BFeAA6RLgw6eeOcdsQsH
Jw.TwUFkxyJ.n6WWrs2Zqhgv24KMHjRGxEZsJ5_Bu8ErpLwpOcf3CCQ61jZS
fg6PFyR0KgLouEeM6qwzM2HVVADHHtbV7saQqX4KD31IuVP3L2_ByYgRE6A3
uhB2coaOgYEzPTw9SsuhBdrJ6YI6LlUvA.yvuTHmPakY_eZLw67fHFT.X02t
2suE78xEBUzIB6yTzPN3hXGcgivr3QYbYeAncHM.gkjLEQjG9JfJKPrvuIXz
sbJJ
X-Originating-IP: [194.175.223.136]
Authentication-Results: mta1067.mail.gq1.yahoo.com from=zeiss.com; domainkeys=neutral (no sig); from=zeiss.com; dkim=neutral (no sig)
Received: from 127.0.0.1 (EHLO dejenssmtpext2.zeiss.de) (194.175.223.136)
by mta1067.mail.gq1.yahoo.com with SMTP; Fri, 25 Oct 2013 05:50:59 -0700
Received: from bdejen03sapp07.zeiss.org ([10.2.32.38])
by dejenssmtpmail2.dmzmail.krz.org with ESMTP; 25 Oct 2013 14:50:51 +0200
Received: from bdejen03sapp07.zeiss.org (localhost.localdomain [127.0.0.1])
by bdejen03sapp07.zeiss.org (Postfix) with ESMTP id 2B34112A372
for <  >; Fri, 25 Oct 2013 14:50:51 +0200 (CEST)
Received: from dejensnotsmtp30.dejen.krz.org (dejensnotsmtp30.dejen.krz.org [10.2.34.154])
by bdejen03sapp07.zeiss.org (Postfix) with ESMTP id DBA9212A371
for <  >; Fri, 25 Oct 2013 14:50:50 +0200 (CEST)

 

I have no idea what all this means or why its doing it?

0 Ratings
Highlighted
Expert
5,412 Views
Message 2 of 166

Re: failure notice - 550 SPF CHECK FAILED

Go to solution

If only all problem reports included so much detail!

 

Your sending domain is zeiss.com

You are sending via yahoo's smtp server

The zeiss.com spf record does not allow this

 

So you need to speak to the admin for zeiss.com and get the spf record fixed.

Oliver.
0 Ratings
Highlighted
5,533 Views
Message 3 of 166

Re: failure notice - 550 SPF CHECK FAILED

Go to solution

thanks for your response

 

so basically my work server isnt allowing me to send emails to my personal email address?

0 Ratings
Highlighted
Expert
5,529 Views
Message 4 of 166

Re: failure notice - 550 SPF CHECK FAILED

Go to solution

Your work domain does not allow sending via yahoo smtp. This will affect all outgoing mail and needs to be fixed asap.

Oliver.
0 Ratings
Highlighted
Distinguished Sage
Distinguished Sage
5,527 Views
Message 5 of 166

Re: failure notice - 550 SPF CHECK FAILED

Go to solution

I would edit out your e-mail addressed for your own security.

 

Which ISP does your work use, as you would have to use their own SMTP outgoing server setting to send mail, as you would not be able to use your BT Broadband one any more, unless you are actually connected to a BT Broadband connection.

0 Ratings
Highlighted
Expert
5,526 Views
Message 6 of 166

Re: failure notice - 550 SPF CHECK FAILED

Go to solution

Hang on, there may be another explanation.

Oliver.
0 Ratings
Highlighted
Expert
5,515 Views
Message 7 of 166

Re: failure notice - 550 SPF CHECK FAILED

Go to solution

I was a bit quick to blame your work email.

 

Critical Path is currently mail-forwarding all mail sent to BT Yahoo boxes. This breaks SPF and is something I reported a while ago. This issue will persist until the migration to CP completes.

 

All you can do is get your work email to "relax" their spf record to "softfail" (but they may refuse).

Oliver.
0 Ratings
Highlighted
Beginner
5,432 Views
Message 8 of 166

Re: failure notice - 550 SPF CHECK FAILED

Go to solution

Hi,

 

When will this be fixed by BT/Yahoo!?  I 'upgraded' to the premium mail package (I now live outside the UK, but I use my btinternet.com email address extensively, since it's used as my redirect my email from my own domain to XXX@btinternet.com.

 

This has now been in a huge mess for nearly one week.

 

For example, all emails from Amazon.co.uk are bounced (luckily I can check my email by other means due to it being sent to my own domain email address).  While emails from LinkedIn get through all the time via btinternet.com.

 

Example of SPF failure (from a friend today based in the Netherlands - my domain is based in Italy, hence aruba.it):

 

Hi. This is the qmail-send program at mxavas1.aruba.it.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<XXX@btinternet.com>:
Connected to 65.20.0.49 but sender was rejected.
Remote host said: 550 SPF CHECK FAILED

--- Below this line is a copy of the message.

Return-Path: <XXX@gmx.net>
Received: (qmail 4128 invoked by uid 89); 28 Oct 2013 12:32:37 -0000
Delivered-To: XXX@my_personal_domain.com
Received: (qmail 4124 invoked by uid 89); 28 Oct 2013 12:32:37 -0000
Received: from unknown (HELO mxcmd04.ad.aruba.it) (10.10.10.68)
by mxavas1.ad.aruba.it with SMTP; 28 Oct 2013 12:32:37 -0000
Received: from mout.gmx.net ([212.227.15.18])
by mxcmd04.ad.aruba.it with bizsmtp
id icYc1m05r0PNvLs01cYdVT; Mon, 28 Oct 2013 13:32:37 +0100
Received: from [192.168.178.12] ([83.81.129.51]) by mail.gmx.com (mrgmx102)
with ESMTPSA (Nemesis) id 0M3d9B-1VsiO40HhJ-00rDp8 for
<XXX@my_personal_domain.com>; Mon, 28 Oct 2013 13:32:37 +0100
Message-ID: <526E5964.5020905@gmx.net>
Date: Mon, 28 Oct 2013 13:32:36 +0100
From: XXX <XXX@gmx.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:25.0) Gecko/20100101 Thunderbird/25.0
MIME-Version: 1.0
To: <XXX@my_personal_domain.com>
Subject: This is not working
References: <526E52B1.7000609@gmx.net> <CALxDhNkLvM_JxE6LqScRtniWwEFiKvhXLEpAiQvbmjip25WEGQ@mail.gmail.com>
In-Reply-To: <CALxDhNkLvM_JxE6LqScRtniWwEFiKvhXLEpAiQvbmjip25WEGQ@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="------------020001030104070708050509"
X-Provags-ID: V03:K0:elkbueQBJnICPGzemGilFzIHX+F5zQdBSCkt/eNOFCVIGPAeQqW
8dO6IHoG1o1KkI4j/s4fYT9cwKOdj6aARA6Y6I26rZpW/XDvCnTypgZXV21KRRFSP2jfDbS
OdPZD4TplFLg3rCK0jIoFvBRK0rHYqeLD9Om6qyi0umwa9aNO7v8P6niRGGY/zOcuO9LoqG
WQAPJ++EQ84QU+ThuK7xQ==
X-Spam-Rating: mxavas1.ad.aruba.it 1.6.2 0/1000/N

This is a multi-part message in MIME format.
--------------020001030104070708050509
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

 

 

Example of a working message (LinkedIn):

 

From LinkedIn Mon Oct 28 12:46:39 2013
X-Apparently-To: XXX@btinternet.com via 188.125.85.228; Mon, 28 Oct 2013 12:46:44 +0000
Return-Path: <m-lzQjXaRNWRJOA2emQ_t4q7IbEoVZhp9O9BV0IG5yYgpZp27TP_iRzWhWUdzj@bounce.linkedin.com>
Received-SPF: softfail (transitioning domain of bounce.linkedin.com does not designate 65.20.0.12 as permitted sender)
S2xhdXMgUm90aCBoYXMgZW5kb3JzZWQgeW91IGZvciB0aGUgZm9sbG93aW5n
IHNraWxscyBhbmQgZXhwZXJ0aXNlOiBWZXJpbG9nIENvbnRpbnVlIFlvdSBh
cmUgcmVjZWl2aW5nIEVuZG9yc2VtZW50cyBlbWFpbHMuIFVuc3Vic2NyaWJl
LiBUaGlzIGVtYWlsIHdhcyBpbnRlbmRlZCBmb3IgRGF2ZSBGcmVlbWFuIChB
U0lDIERlc2lnbiBFbmdpbmVlciBhdCBDYXRlbmEgUmFkaW8gRAEwAQEBAQN0
ZXh0L3BsYWluAwMwAgN0ZXh0L2h0bWwDAzE3
X-YMailISG: z8es5ToWLDtos13QBk1j3btV25aLCDvrEBddrWtAhOqmtj94
_jbYhKtag8rgP1t8BbZEN6X9MAjk6OklQ_jQFIiLqC_GAQatcD6BeZXTc3r5
.OkmSilEU6eyMC8enSPURWW86WpJT3_3s4fUdaRuF_TdQ9khA0BVZfzsvcIN
d4BjqsqeECBsNtNwBo7enJ76qPJv4dTSHb2_PPkyv1OSB2ly.M6cVIf7huMu
HwsgA8WOgV1QrCg_s_vhobSFTOtW6fcWU9OluHgq6Y36T8rlC82WGO7xq6tY
7gt2e870iYEqKFQW.ckdalZjzKKbI7FY9LcvhWBSM0coAzyd5NltGk271ExL
SuxVJPIQcX3kTtt8RzHL6bjvSNmqYVCs.QEpSJfHVmGhpuQlKaXHBOyvjObI
b0DyP79HkP_34obhIlGHDTGh0Va3BvCZ_Zyu7lamDlHsFnqU5iNI9ewIgFdh
nUuDb5FaOJN7hjOZZnwxVI.WIPomj38xNmTLp_ipOlHNDehYiBTGrEN30QFF
Y3rrnW_Mpf3srrYk4LM.RHwUQsCqZt4O31KQO528jg2_igjXu3kH4aMWtQr2
WCFyQvufxug7l5HqHaG7_WV2zwGaaXQOL0qPc4Q86RU3Pr_Wib7WcHHWdR0s
in8GNWnMSuq6_2MmN4lB7jSXpi1rYHfo7bL_FmpXkgZhLStjuVBuAyyYpMPW
xXr17e2NvSmOj68NP0Y4QFx7b86TFMdd0QmklmPI9vFn1_.181BjFissyCet
w9slFBzGnzcuLbPRHlHntp8WBKYK.viPkcysIdtVquxAWoqQ6Gl3O_hl4h1.
NtKIz76Jr_TlCJaLAcVCB734Md1oV9kDq1NqRKl2tq3wa8ZLiyPQ5lu_jpRm
t0qib83Qyxms7ZezpFWpCBzu2tvC3p.iNonXG2u5o1cO5DIR44_4I7UHR9DV
AD44qTvHXddl.GfnJoj7d7hQQ5NKnzYAE7HtMFEZwiRFtVFuFeDYyhHP9rgt
hdyfc0He7jnYR1mj3bc2XGWY6tjxH9MuoWyPq.I43hRA85uF_9GxKhBP6aBX
.PtiuRM13v1qQG73P.1nk6vJKllPOCtmkFsb60GFJe.9i2_PvNoxVxdI7k4d
6IEC_y43Mv3d70i08WKcB35BnDC0SZKiu5h4ziuLdskzXWQfooDhreg28KA2
oHsyPP1dGd3oYVB0dnLra_9mFABg8xf9E0poSoffqhz3UAyH1iHSxnYCeNMN
GyB7LTMgOcC4Q2BB.5RYrciCBgsu7DEChk5bOTeCaVat5MCbIAmn4lrclZ7M
fVhMhdRum10vi2LmoO5bbc_DIuAXmX1VVWaPYqMznERwVP9WR5.HO1N_1DkH
HLG3bJMnx6Awa13Gtfh5xtg0_69IWRNIXFfxzGS0ILk-
X-Originating-IP: [65.20.0.12]
Authentication-Results: mta1038.bt.mail.ir2.yahoo.com from=bounce.linkedin.com; domainkeys=neutral (no sig); from=linkedin.com; dkim=pass (ok)
Received: from 127.0.0.1 (EHLO smtpin17.bt.ext.cpcloud.co.uk) (65.20.0.12)
by mta1038.bt.mail.ir2.yahoo.com with SMTP; Mon, 28 Oct 2013 12:46:44 +0000
X-CTCH-RefID: str=0001.0A090202.526E5CB4.00D1:SCFMA17354505,ss=1,re=-4.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
Received: from mxavas3.aruba.it (62.149.157.13) by smtpin17.bt.ext.cpcloud.co.uk (8.6.100.99.10161)
id 52670470018DDBD8 for XXX@btinternet.com; Mon, 28 Oct 2013 12:46:44 +0000
Received: (qmail 26139 invoked by uid 89); 28 Oct 2013 12:46:40 -0000
Delivered-To: XXX@my_personal_domain.com
Received: (qmail 26135 invoked by uid 89); 28 Oct 2013 12:46:40 -0000
Received: from unknown (HELO mxcmd06.ad.aruba.it) (10.10.10.74)
by mxavas3.ad.aruba.it with SMTP; 28 Oct 2013 12:46:40 -0000
Received: from maile-fc.linkedin.com ([199.101.162.91])
by mxcmd06.ad.aruba.it with bizsmtp
id icmf1m01G1ydT5j01cmfYx; Mon, 28 Oct 2013 13:46:40 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linkedin.com;
s=proddkim1024; t=1382964399;
bh=Jl0roAehKgRExmnfiexoqH4Exa1w+zHisdNp2F3shA8=;
h=Date:From:To:Subject:MIME-Version:Content-Type:
X-LinkedIn-Template:X-LinkedIn-Class:X-LinkedIn-fbl;
b=fZxjuoih0e9QJ8RhYo8TDgtUmoKBSVleG83obG55CRmH1YXJimj1h2ScizrzGP8ZQ
81FFweEkqej69F+hyLnuGCP9OrHjkSxX7IJ4//6ji248ToKgej3KI+rn8W6NJ9YIeQ
rh4Dj8ABylSdKAqHllNq9PiEhLm9b+z2LlOwnV5A=
Sender: messages-noreply@bounce.linkedin.com
Date: Mon, 28 Oct 2013 12:46:39 +0000 (UTC)
From: LinkedIn <messages-noreply@linkedin.com>
To: XXX <xxx@my_personal_domain.com>
Message-ID: <1943659873.105043897.1382964399366.JavaMail.app@ela4-app3486.prod>
Subject: LinkedIn Message
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="----=_Part_105043894_2077948838.1382964399361"
X-LinkedIn-Template: endorsements_multiple
X-LinkedIn-Class: TIK
X-LinkedIn-fbl: m-lzQjXaRNWRJOA2emQ_t4q7IbEoVZhp9O9BV0IG5yYgpZp27TP_iRzWhWUdzj
X-Spam-Rating: mxavas3.ad.aruba.it 1.6.2 0/1000/N
Content-Length: 18059

 

 

It's staggering that for a paid service it has been like this for almost one week.  I'm fortunate that I can check my emails due to the fact I have that personal domain name and virtually no one sends it to my XXX@btinternet.com email address.

 

Please update with an eta for this issue to be resolved.

 

Regards,

 

Dave

 

0 Ratings
Highlighted
Expert
5,426 Views
Message 9 of 166

Re: failure notice - 550 SPF CHECK FAILED

Go to solution

I agree, mail forwarding in this fashion has completely broken SPF for some time now. As a result, this will only be fixed when the BT Yahoo mailboxes are migrated.

 

BT (or CP) really should have discussed this SPF issue with Yahoo before implementing this method.

Oliver.
0 Ratings