[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[cobalt-users] RaQ3 Bugs: Can we have a fix this year please?



The RaQ3 has been out for well over 6 months now, and there is
still no "official" fix to the username/alias bug, ie:

  If you have a user named "joe" with an alias of "info",
  and someone else has a user named "info", then that user
  gets *ANY* and *ALL* email addressed to info@whatever

I've got 6 RaQ3s, and I'm getting sick and tired of having to
comb the /etc/group file on each to discover the latest fiasco
my users have (inadvertently) created - not to mention all the
email that is going astray...

I'm sure I'm not the only one in this predicament, as I know
for a fact most RaQ owners setup their clients as site admins
with the full ability to create new user accounts.

Cobalt's response: they're focusing on security issues, and
"feature" enhancements aren't a consideration!
--

And what about the entire Cobalt Postgres GUI database just
dumping itself, ie:

  You go to access your server admin and you get a blank
  GUI screen; no websites, no users - nothing.

I've spoken with at least 6 other people to whom this happened
to, and in every instance we all had to contact Cobalt tech
support to get them to rebuild it. No apology - no explanation.

Cobalt's response: if enough people complain, they might even
acknowledge there is a problem and look at the Postgres code.
--

So I ask: "What will it take to resolve these bugs/issues and
address the issue of Cobalt's lackluster customer service?!!"

Frustrated,
--

Jay Tingley
BlackSun | info@xxxxxxxxxxx