Hosting Issues

[Flibnipktz]

Besides the blacklisting issue, it's still worrying that your site was offline due to a database crash.
They also mentioned "We had restarted the server due to some technical issues.", I would always expect the host to tell me exactly what was going wrong, not a vague description.

Agree. I had to push to get that much, and it's not the first time. Routine maintenance implies a scheduled server reboot (if necessary) and some kind of heads-up to those affected.

RB67, here's the response to my forward earlier today...

Hello,

The Ip address (edit) on our shared server is only using for your email accounts. The att network here black listed emails from your account, it may due to the presence of spam looking words or content on it.

Or it may due to recent bulk amount of emails that sent from your forum site to the customers on their network and some of clients in there may complained about this. So they black listed that ip.

You can delist the ip through the url http://rbl.att.net/end_user_request1.html .

Also check http://www.att.net/general-info/521.html

If you purchase a vps server here, Email service on the server will only used for your email accounts.

That Ip already has a rDNS which pointed to our server. However to avoid the forward lookup (PTR) related issue I've informed our network team to change the rDNS to your domain name.

The initial rationale is possible, but we're a small board, I'd estimate around 50-75 emails a week or less. Part of that is a scheduled "Happy Birthday" to those few members it applies to... and the rest is mostly logon issues, PM notifications and thread subscriptions. There are no bulk mailouts. Someone may be complaining, however it seems unlikely.

Followed by the pitch for VPS once again. As far as I understand it, this would be serious overkill in our case, and I'm already questioning the current $50.00/month, nevermind additional charges. And issues.

Finally at the end, an acknowledgement of what they seem to have missed. Thanks to you RB67 for the advice.

Migrating to another host... not thrilled at the prospect but it's something to think about more seriously now. Meantime hoping that today's fix is the real problem with att.net.