ContributionsMost RecentMost LikesSolutionsRe: Your account is locked for safety-- and again and again... Now this is really weird. I got one of these notes at 1:17PM MST today. So far however, the account doesn't seem to be locked. I can use my e-mail client to retrieve and send messages. I'm looking up to see if the sword of Damocles is waiting to drop. Sigh. Re: Your account is locked for safety-- and again and again... This just happened again today! Totally ridiculous. Cox is so lame not to be able to solve this. Every other company I deal with does not have this issue. Re: Your account is locked for safety-- and again and again... haveibeenpwned shows my e-mail addresses were detected in some old breaches, but my password has been changed many times since then. I would just like Cox to find a better way of protecting their users than to force them to continually have to change their passwords. If other companies which deal with sensitive customer data can do it, Cox should be able to as well. Re: Your account is locked for safety-- and again and again... Yes they do. But the ones I'm getting are only received after I've changed the password for my account. That's because Cox had already locked my account. The e-mails I'm seeing are not phishing attacks. They are a result of Cox locking my account. Your account is locked for safety-- and again and again... This is really getting irritating. Over the last 9 or so months, I've occasionally gotten an e-mail from Cox with the subject "Your account is locked for safety", and the text states it's because "security flagged some odd behavior". I know these are valid e-mails from Cox since when I attempt to log into my Cox account, it fails, and I have to reset my password. Most of the time, I do not see the e-mail until my e-mail client fails to authenticate before attempting to download mail. Cox support tells me it is because repeated login attempts with an incorrect password were observed. I know these attempts are not coming from me because the account lock out happens in the middle of the night when my computer is shut down. I got one again yesterday, and then again today. I'm ticked. I understand, and even appreciate, that Cox is trying to protect my account. But, really, I never see this on my financial accounts, and I'm sure bad actors are attempting to hack into them as much as my Cox account. Is it not possible for Cox to protect my account without the inconvenience of me having to change my password every time they detect multiple failed attempts to hack in? Thanks, Tim Re: STOP SENDING MYPILLOW TO SPAM!!!!!!! More generally, does sending a spam-tagged e-mail to ThisIsNotSpam@cox.net have any effect at all? I have not noticed any change in the Cox spam filter behavior. The same seems to be true for users identifying spam e-mail to SpamReport@cox.net. I think it is more likely that these e-mail addresses are pacifiers for Cox's users, and have no real effect. Re: spam and not spam reports bouncing Still no bounces for SpamReport@cox.net or ThisIsNotSpam@cox.net, nor for phishingreport@cox.net in the last five days. I've been using each many times a day. I think we can consider this issue fixed. Re: spam and not spam reports bouncing Allan, I haven't seen any bounces for SpamReport@cox.net or ThisIsNotSpam@cox.net, nor for phishingreport@cox.net in the last day or two, and that from simply forwarding the subject e-mail as I've always done in the past. Maybe this problem has been fixed. I'll give it a few more days, and report again. Re: spam and not spam reports bouncing Allan, I'll give that a try. But now I'm curious. I thought that forwarding a note was essentially creating a new note with the forwarded e-mail as an attachment. Your suggestion implies there is a difference, and I'm wondering what it is. Thanks, Re: spam and not spam reports bouncing FYI, ThisIsNotSpam@cox.net forwards are still being bounced. Along these lines, I just tried forwarding a phishing e-mail spoofing it was from COX to phishingreport@cox.net, and it was bounced because it was suspected to be SPAM! Interestingly, the sender had a cox.net domain.