'lo We sent out notification of all the changes in this update quite recently. The problem here was something larger than we announced was actually promoted (which we fixed, and there we have it)...
Charles Daminato OpenSRS Product Manager Tucows Inc. - [EMAIL PROTECTED] > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of ST > Sent: October 24, 2001 1:14 PM > To: [EMAIL PROTECTED] > Subject: RE: email address same as domain = problem > > > Hi, > > I noticed this new error checking as well. While it is a good idea for > new domains, I personally would prefer some kind of warning about any > new error checking that's going to happen when the register routine is > called from reg_system.cgi. All that checking should really be done > during the verify routine. This gives the customer a chance to correct > the errors before their card is charged. When the error checking > doesn't happen until the register routine, it results in duplicate > credit card charges, and much more confusion and frustration. > > I'd just like a bit of warning so I can update my scripts to do the new > error checking during the verify routine. You could even provide a patch > for XML_Client.pm whenever you add new error checking so RSPs can easily > update the verify routine before the changes become active. > > ST > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of genie > Sent: Monday, October 22, 2001 5:52 PM > To: [EMAIL PROTECTED] > Subject: email address same as domain = problem > > > Hi - this is probably a result of new and improved error checking, we > just > tried to register > > web-domain-name.com = but received this error message > > Registration attempt for web-domain-123.com failed: Invalid data. > > Email address '[EMAIL PROTECTED]' for owner contact can't be in > the > scope on new domain > Email address '[EMAIL PROTECTED]' for billing contact can't be in > the scope on new domain > Email address '[EMAIL PROTECTED]' for tech contact can't be in the > scope on new domain > > > so the new system does not allow email address to be the same as the > domain > name... > we have potentially several hundred domains a week going in - which > worked > untill now... > so I assume it is the new-and-improved error checking - is there any way > we > can turn this off? perhaps an input type hidden field those of us who > need > it could employ?? Otherwise we are now faced with extra labour > to have to go into several hundred domains per month and change the > email > address! > > also - is this error checking affecting domain transfers??? I can > perhpas > understand registry > not wanting email address of domain that does not yet exist but on > domain > transfers [EMAIL PROTECTED] should be a valid email address for > web-domain-123.com > > Genie > Magi Inc > > >
