[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] RaQBaQ
- Subject: Re: [cobalt-users] RaQBaQ
- From: MistaAviB@xxxxxxx
- Date: Mon Oct 23 15:09:01 2000
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
In a message dated 10/23/00 2:41:20 PM Eastern Daylight Time,
clist@xxxxxxxxxxxxxxx writes:
<< I recommend you do not install this until the makers fix the DNS problem
and
a few other bugs
1. The maker set's up CNAMES for the domain, i ran into a problem on my RAQ3
when i was trying to send a message to a user, i got this:
The message could not be sent because one of the recipients was
> rejected by
> the server. The rejected e-mail address was
> 'admin@xxxxxxxxxx> Subject '', Account: 'Gary', Server: 'www-hosting.net',
Protocol:
> SMTP,
> Server Response: '554 rewrite: excessive recursion (max 50),
> ruleset 3',
> Port: 25, Secure(SSL): No, Server Error: 554, Error Number:
> 0x800CCC79
Thanks to a posting in the archives, i found it was due to using CNAMES, i
changed the dns and it worked fine. I emailed the maker and told them that
if they want the program to work, they must create ARECORDs instead.
2. If you try setting up a sub domain, and deselect the allow email and
allow domain checkmarks, it still wont work, i thinks the checkmarks are
still there
3. I noticed for the DNS, after you setup a account, you have to go into the
dns server and "save changes to dns server" before that sites dns will
work...
--------------------------
If you are using this software, which is a great and faster way to setup
accounts, i recommend stop asap until the makers post a fix for these
issues. I setup 5 accounts and thankfully found the problem before i setup
more. Or your new clients are going to complain they are getting a weird
error in their email program....or no email at all...
PS: The response to the bugs i been sending this company is "Thanks for your
emails. We will look into this :-)" >>
Yes, we are going to release a fix for this in the next update. We do not
work in seconds and we only received this email this morning. (Unlike
cobalt), we will get the fix out in a timely fashion :-)
Avi.