If you leave your mail on the server, then it will eventually fill up, and when people try to e-mail or reply, they’ll get “the mailbox is over quota” or something similar as a bounce-back message.
There’s a set of “requirements” called Payment Card Industry Data Security Standards (PCI DSS) that was developed by the PCISSCÂ Payment Card Industry Security Standards Council.
I first heard of these “requirements” in the bar on the last day at Pubcon Vegas 2008, where someone said “Trust me, you’d BETTER learn about it, because they’ll make your life miserable if you don’t…”, and they were sure right.
I need to officially announce some recent changes to the e-mail configuration of our servers that may have caused some distress for our hosting clients, and I’d like to clear that up right now.
One of our mail servers has again been added to a spam blacklist, meaning that we are banned from sending e-mail, undoubtedly due to one of our hosting customers who has been sending bulk e-mail.
Technically, we can still send, but the users at Yahoo, MSN, and dozens of other providers will temporarily not accept mail from that mail servers IP address.
We’ve had another web hosting customer screw things up for everyone else on their shared mail server by sending unsolicited e-mail, which is against our terms of service.
I’ve written about this before, more than once, and this user has received no warnings, gets no second chances, and their web hosting account, including all e-mail service has been permanently removed from our system.
PDXTC Hosting will be performing emergency maintenance on the LINUX6 Web Server (linux6.pdxtc.com) starting immediately.
During the past seven days users that host websites and web applications on this server may have noticed frequent outages due to a hardware configuration issue on this server.
I’ll bet you $1000 that if we took an existing and well established default site installation today, and first upgraded it to WP 2.82, then we set WP up correctly with our chosen SEO plug-ins, correct permalinks, etc. that we would LOSE rankings in the search engines within 90 days.
I’ve had my share of issues with Comcast in the past, and this one is just as frustrating.
Just like many of my issues with them so far, it’s completely inconsistent from market to market, so their support department seems to know nothing about it.
We got hit today with another 48 hours of Microsoft spam blacklisting, this time because a brand new hosting client sent out 30,000 e-mails in one day.
When I looked at the website of this new client, I did have just the slightest hesitation when I saw that he was an Internet marketer, however it never occurred to me that he could be a complete idiot.
This morning, email and website access is sporadic (at best) on the PDXTC servers, and it is slowly being restored.
For what it’s worth, the problem was not actually on our end, but in the middle, with one of Portland’s primary bandwith providers making a stupid mistake. i know that’s of little consolation, but it’s the truth.
A dozen years ago or so, I had one password that I used for everything, and it wasn’t until some bad experiences that I understood the wisdom of having stronger passwords.
That said, to this day, I have some very simple passwords for literally dozens of online accounts I have in various places, because there’s really only so much need for security on certain accounts, but they’re not common words from the dictionary.
If you’re one of our 900 hosting customers having sporadic trouble with email for the past 36 hours, here’s the deal, and we’re pretty sure it’s totally unrelated to my public criticism of Linux Magic.
At approximately 7:45AM Pacific, one of the PDXTC shared mail servers (mail2.pdxtc.com) was determined to be in a critical state by our server monitoring system.
