Subscribed messages

[Billx]

@nomfezeko-TT 

Subscribed messages are not being sent,

Is there a reason for this?

[siphosethu-TT]

Please call in so they can do that for you, the sooner you call in the faster they can have it looked into and escalated if must. Thanks

[Billx]

@nomfezeko-TT , @siphosethu-TT 

By the way, Support Team Staff, I would really like some help now.

Since I am still having a continuation of the problem, and TalkTalk is still unable to fix it, maybe it's now time to stop receiving TalkTalk Community messages via Gmail.com, and to receive them directly at my tiscali.co.uk email address.

Can you please dig deep, and see how we could do this?

Bill

[siphosethu-TT]

I understand that you are unable to send emails, and the server is blocking them. I'll need you to call in using the contact details below and they will assist you, as I'm unable to do this for you here. Thanks

03451720074

Opening Hours:

VOICE - Mon-Fri: 9am-7pm; Sat: 9am-6pm; Sun: closed

https://community.talktalk.co.uk/t5/FutureFibre/bd-p/FutureFibre

[Billx]

@Billx 

A copy of a representative of the error messages and a description of what a successful auto-forward looks like :

----------------------------------------------------------------------------------------------------------------------------------

Beginning of the error message

Subject: Delivery Status Notification (Failure)

From: Mail Delivery Subsystem <mailer-daemon@googlemail.com>

Date: 2025-07-14, 16:05

To: [an alias of Billx’s ......@gmail.com email address – see below] .

---

Message blocked

Your message to [Billx’s ......@tiscali.co.uk email address] has been blocked. See technical details below for more information.

LEARN MORE This link will take you to a third-party site.

The response from the remote server was:

550 5.7.1 Message rejected per sender's DMARC policy - OXSEU001_514 –

 https://postmaster-oxseu.vadesecure.com/inbound_error_codes/#_514

---

Reporting-MTA: dns; googlemail.com

Received-From-MTA: dns; no-reply@community-notifications.talktalk.co.uk

Arrival-Date: Mon, 14 Jul 2025 08:05:09 -0700 (PDT)

X-Original-Message-ID:

            <0a997952-9383-4f3b-8e91-c8420fc2df89.1752505506271@community.talktalk.co.uk>

Final-Recipient: rfc822; [Billx’s ......@tiscali.co.uk email address]

Action: failed

Status: 5.7.1

Remote-MTA: dns; mx003.tt.xion.oxcs.net. (135.125.7.163, the server for the domain tiscali.co.uk.)

Diagnostic-Code: smtp; 550 5.7.1 Message rejected per sender's DMARC policy - OXSEU001_514 -            https://postmaster-oxseu.vadesecure.com/inbound_error_codes/#_514

Last-Attempt-Date: Mon, 14 Jul 2025 08:05:11 -0700 (PDT)

---

ForwardedMessage.eml

Subject: Sent e mails are all being blocked (TalkTalk Help & Support Subscription Update)

From: TalkTalk Help & Support Community no-reply@community-notifications.talktalk.co.uk

Date: 2025-07-14, 16:05

To: [Billx’s ......@gmail.com email address]

Hi Billx,

Treble1999 (Newbie) posted a new topic in Email on 2025-07-14, 04:04 PM :

Sent emails are all being blocked

All of a sudden, my sent emails are all coming back blocked from SPAMHAUS. I can receive emails

TalkTalk Help & Support sent this message to  [Billx’s ......@gmail.com email address].
You are receiving this email because a new message matches your subscription to a board.

To control which emails we send you please go to, manage your subscription & notification settings or unsubscribe.

Attachments: Sent emails are all being blocked.eml    10.9 kB

End of the error message

--------------------------------------------------------------------------------------------------------------------------------------

When Gmail auto-forwards an email from my gmail.com address back to my tiscali.co.uk email address, it first creates what seems to be an alias email address of my gmail.com address.

The alias email address takes the following form:

[Billx’s ......@gmail.com email address, only the part before the @]+caf_= [Billx’s ......@tiscali.co.uk email address, only the part before the @]=tiscali.co.uk@gmail.com

It then adds 3 or 4 new headers above the existing headers of the originally received email and sends the email back to tiscali.co.uk. These new headers include the new alias address.

When viewed at tiscali.co.uk, the successful auto-forwarded email looks exactly as it looked immediately after it was first received at gmail.com. I.E. Both at gmail.com and at tiscali.co.uk, it shows the following:

From: TalkTalk Help & Support Community <no-reply@community-notifications.talktalk.co.uk>

To: Billx’s ......@gmail.com email address

So, the effect was, as if it had arrived directly to my tiscali.co.uk email address.

Now, after the start of problem, the original of an email from TalkTalk Community and the error response to it from ‘Mail Delivery Subsystem <mailer-daemon@googlemail.com>' remain in the Inbox folder at gmail.com.

Bill

[siphosethu-TT]

Please call in so they can run checks on that for you. Thanks

[Billx]

I don't understand outage, that's new to me.

Is a faulty TalkTalk server an outage?

[siphosethu-TT]

Please call in so they can fill you in on whether it's an outage or something fixable. Thanks

[Billx]

If the Full Fibre people are not already aware of the issue, then there really IS something wrong.

[siphosethu-TT]

Please call in so we can have the issue looked into for you. Thanks 😇

[siphosethu-TT]

Hence you are a full fibre customer please contact the number below and they will have the issue looked into for you as soon as possible. Thanks

03451720074

Opening Hours:

VOICE - Mon-Fri: 9am-7pm; Sat: 9am-6pm; Sun: closed

https://community.talktalk.co.uk/t5/FutureFibre/bd-p/FutureFibre

[Billx]

Ok resolve things. Why pester people? The problem is at the TalkTalk incoming email server, not here.

[siphosethu-TT]

Please note that will run checks on this, hopefully will get a resolution as soon as possible as the issues we've been getting lately have been escalated. 

[Billx]

Off course the internet is working.

How would I already have all the information, if the internet was not working?

[Billx]

Hi, @siphosethu-TT 

I am not playing this game.

[siphosethu-TT]

Hi there @Billx, will just run checks on this please confirm if the internet is working perfectly as it should. Thanks

[Billx]

But let's see what TalkTalk comes up with.

[Billx]

No, @fr8ys , I haven't done all of those.

But I did delete the auto-forward rule for TalkTalk Subscriptions. and then recreated it, but without closing Gmail, or dealing with cookies.

Thanks

Bill

[fr8ys]

@Billx probably stating the obvious, but have you tried deleting the autofoward rule and then adding it again (after closing Gmail and opening it again)?

I've never found it helps, but also clear Gmail cookies and cache?

[Billx]

Yes, @nameunknown , I fully agree.

If I manually forward, the To: is my tiscali.co.uk email address

I gmail auto-forwards. the To: remains my gmail.com email address.

And that could cause the problem.

But as I said this distinction started only on 1-7-2025.

So who has changed, TalkTalk, or Gmail?

If this has really changed, then Gmail must find a way of replacing the To: contents from my gmail.com address to my tiscali.co.uk address, when auto-forwarding

But thanks very much for pointing that out to me.

Bill

[nameunknown]

@Billx 

There is a difference between you manually forwarding and email and Gmail's auto-forwarding.

Look at the email that you manually forwarded to your Tiscali account, and you see that that the To entry has your Tiscali email address in it, i.e. this matches the expected email address for the account, the recipient email address.

When Gmail auto-forwards your email, the message arriving in your Tiscali email account has your Gmail address in the To entry, i.e. it does not match the expected expected email address for the account.

A mismatch such as that can cause emails to be rejected. However, it did not ought to be rejected when Gmail auto-forwards your email. I am assuming there is something in the hidden header of the email that should allow it to successfully pass authentication when it arrives in your Tiscali account.

This needs to be investigated by those responsible for managing the TalkTalk/Tiscali email servers. They should be able to identify the cause of the problem, and deal with it.