Incorrect warning on email spam management screen

[#1]

I have just sought to alter the email spam settings on my username.plus.com email domain in order to inspect any emails being received from parties outside of PlusNet in respect of the email addressed used solely for billing and support.
Though the "Block all incoming email to this domain" was not ticked, the bottom of the page states...

Quote

Domain Email Blocked You cannot set your spam settings because email to this domain has been blocked To renable email to this domain, simply uncheck the option above labeled 'Block all incoming email to this domain' then click 'Update Settings' below

Not only is the warning incorrect, "re-enable" and "labelled" are spelt incorrectly.
Can you please raise an internal error report for resolution at some future time?

Kevin

[#2]

And warning is spelt incorrectly in your title

[#3]

Thanks Peter,
I guess I asked for that!  I double read the post carefully, but completely forgot about checking the (now corrected) title. 

[#4]

I guess these problems stem from using these "low-tech" iPads 

[#5]

AO,
No that was done on a computer.
BTW, in answer to your question - it depends on how big your balls are!

[#6]

Well you must be all fingers and thumbs then

[#7]

You should watch what you say, otherwise he might give you the iFinger ! 

[#8]

iPM sent

[#9]

I do hope that jovial banter on here does not distract CRT from looking at the reported issue with seriousness!

[#10]

Do you have any entries in the 'Blocked Addresses' box at the bottom of the page Kevin?

[#11]

A bit off topic, other than your question is in relation to the reason for looking here!  From historical abuse events...

Blocked Addresses
margaret.kakel@hotmail.co.uk
allinaday.com.au
pokccarfntor@nbctifton.org
wohnstadtbau.de
platinumwedding.com
veenmagazines.nl
folia-fabrics.com
ekit.com
yourstayhome.com
24hr-loans.co.uk

And just took off discard obvious spam.

[#12]

I'm not seeing this warning message, but haven't tried altering anything to see if I can provoke it, it was more a case of seeing what things may cause it to be there in the first place.

[#13]

I've raised this internally with our web development team (84116).
We'll get this sorted when we can.

[#14]

Thank you.