- Welcome to IDNetters Forums.
Recent posts
#71
Broadband, Internet & General Computer News & Discussion / Re: Is it possible to reject e...
Last post by zappaDPJ - Aug 19, 2025, 16:17:23Thanks that's exactly what I want. I'll give it a go 
#72
Broadband, Internet & General Computer News & Discussion / Re: Is it possible to reject e...
Last post by Simon - Aug 19, 2025, 15:24:35Assuming this is an IDNet email, if you log in to the Customer Portal, find the settings for your email, you can create custom filters for just about every imaginable trigger. By using * as a wildcard you can ban a whole domain or any such other configuration, and you can set it to immediately delete without going into a spam folder.
#73
Broadband, Internet & General Computer News & Discussion / Is it possible to reject email...
Last post by zappaDPJ - Aug 19, 2025, 14:17:03Due to a number of data breaches my main email address attracts a massive amount of spam. During the last few months the majority of it written in Japanese originates from .cn.
As every email is sent from a disposable address it's pointless marking it as spam and it would be equally pointless blocking the domain as I would still have to check the spam folder for genuine mail.
Is there anyway at all of rejecting an entire domain or at least sending it to a unique folder?
As every email is sent from a disposable address it's pointless marking it as spam and it would be equally pointless blocking the domain as I would still have to check the spam folder for genuine mail.
Is there anyway at all of rejecting an entire domain or at least sending it to a unique folder?
#74
IDNet Help / Re: OpenReach woes
Last post by Simon - Aug 19, 2025, 13:57:27It does seem as though whenever there's a problem, the various providers of the associated services have a compulsory obligation to first blame the end user's equipment, then each other, before looking closer to home for what the issue may be.
#75
IDNet Help / Re: OpenReach woes
Last post by zappaDPJ - Aug 19, 2025, 13:53:51Quote from: nowster on Aug 19, 2025, 13:38:11Ever been in a situation where you know far more than the repair person that was sent out to fix a problem?
I get that feeling every time I visit my GP
Fingers crossed someone stumbles into the issue and gets it fixed!
#76
IDNet Help / OpenReach woes
Last post by nowster - Aug 19, 2025, 13:38:11Ever been in a situation where you know far more than the repair person that was sent out to fix a problem?
The story so far...
At 06:25:15.8 on Saturday morning, the router here got a PPPoE LCP TermReq packet from the OpenReach end. That's the equivalent of the far end saying it's hanging up the connection.
Our router then periodically sent out PPPoE Discovery packets (PADI) and got no response at all.
I noticed things were wrong at 8am and rang IDNet who agreed that the session had died and their RADIUS (authentication and session accounting server) logged a weird error.
I'd done all the kit swapping dance, changing everything to a previously "known good" setup. No dice.
IDNet raised a fault with OpenReach who duly sent an engineer this morning (Tuesday). Engineer wanted to know where the BT HomeHub was and whether it was showing a blue light.
Eventually he swapped out the ONT (which I knew would be pointless) and declared it not his problem. Second level said they could see a trickle of activity (but not what it was).
Interestingly they let slip we're the only user on that PON circuit (ie. uncontended access to that fibre).
So, it's back with IDNet's network people to find out what's wrong.
The daft thing is that this sort of thing used to be my job. I used to run an ISP and have done everything from liaising with BT management to pulling an all-nighter to find (and fix) a bug in the LCP (Link Control Protocol) layer programming of a PPP-over-L2TP Network Server.
That bit of tech hasn't changed in the 16 years since I've been out of it. It's PPPoE on VDSL or FTTP nowadays rather than PPPoA on ADSL.
I've even got better kit than them to diagnose the problem at this end. The OpenReach engineer really ought to have been provided with an Ethernet protocol sniffer box as standard kit.
They had no means of checking anything beyond the self-diagnostics provided by the ONT, and were completely thrown by anything that didn't look like a BT Homehub.
Anyway, spleen vented. The ball's back in IDNet's court for their network team to diagnose the problem.
The story so far...
At 06:25:15.8 on Saturday morning, the router here got a PPPoE LCP TermReq packet from the OpenReach end. That's the equivalent of the far end saying it's hanging up the connection.
Our router then periodically sent out PPPoE Discovery packets (PADI) and got no response at all.
I noticed things were wrong at 8am and rang IDNet who agreed that the session had died and their RADIUS (authentication and session accounting server) logged a weird error.
I'd done all the kit swapping dance, changing everything to a previously "known good" setup. No dice.
IDNet raised a fault with OpenReach who duly sent an engineer this morning (Tuesday). Engineer wanted to know where the BT HomeHub was and whether it was showing a blue light.
Eventually he swapped out the ONT (which I knew would be pointless) and declared it not his problem. Second level said they could see a trickle of activity (but not what it was).
Interestingly they let slip we're the only user on that PON circuit (ie. uncontended access to that fibre).
So, it's back with IDNet's network people to find out what's wrong.
The daft thing is that this sort of thing used to be my job. I used to run an ISP and have done everything from liaising with BT management to pulling an all-nighter to find (and fix) a bug in the LCP (Link Control Protocol) layer programming of a PPP-over-L2TP Network Server.
That bit of tech hasn't changed in the 16 years since I've been out of it. It's PPPoE on VDSL or FTTP nowadays rather than PPPoA on ADSL.
I've even got better kit than them to diagnose the problem at this end. The OpenReach engineer really ought to have been provided with an Ethernet protocol sniffer box as standard kit.
They had no means of checking anything beyond the self-diagnostics provided by the ONT, and were completely thrown by anything that didn't look like a BT Homehub.
Anyway, spleen vented. The ball's back in IDNet's court for their network team to diagnose the problem.
#77
Windows News & Discussion / Re: Microsoft Defender/365 sub...
Last post by nowster - Jul 31, 2025, 15:16:12Quote from: zappaDPJ on Jul 30, 2025, 23:01:59Wordstar I remember well. I was responsible for deploying it across a regional health authority at a time when all the admin staff were using manual typewriters. It still make me shudder to think back on it.WOW! Today I learned.
I believe this is the product I recall https://www.cpcwiki.eu/index.php/Star-Writer
#78
Windows News & Discussion / Re: Microsoft Defender/365 sub...
Last post by zappaDPJ - Jul 30, 2025, 23:01:59Quote from: nowster on Jul 30, 2025, 18:38:38You're thinking of WordStar, I suspect.
Wordstar I remember well. I was responsible for deploying it across a regional health authority at a time when all the admin staff were using manual typewriters. It still make me shudder to think back on it.
I believe this is the product I recall https://www.cpcwiki.eu/index.php/Star-Writer
#79
Windows News & Discussion / Re: Microsoft Defender/365 sub...
Last post by nowster - Jul 30, 2025, 18:38:38Quote from: zappaDPJ on Jul 30, 2025, 17:43:24I remember StarWriter, we used to run it on CP/M based computers. That would have been about 40 years ago!You're thinking of WordStar, I suspect.
#80
Windows News & Discussion / Re: Microsoft Defender/365 sub...
Last post by zappaDPJ - Jul 30, 2025, 17:43:24Quote from: nowster on Jul 30, 2025, 17:38:05I've been using it since it was called StarOffice.
I remember StarWriter, we used to run it on CP/M based computers. That would have been about 40 years ago!