I have already alerted your Account Manager and the Technical Staff regarding your issue. I received your call at 6:45pm on a Friday Evening, and I did not have a definite answer for your question as majority of the staff had retired for the weekend. I followed up by sending an email to the appropriate parties which will be handled during regular business hours.
The domain in question is a Redemption Period domain. Batch.Opensrs.Net is not designed for redeeming domain names. You could have easily found more information at our FAQ at: https://rrc.tucows.com/support/faq/support_faq#Live_batch_transfer_browser_l imitations The discuss-list is designed to share information about OpenSRS features. If you have a complaint, please contact your Account Manager directly and it will be handled in professional manner. Oscar Wu OpenSRS Technical Support Happy New Year ----- Original Message ----- From: "Paul Chvostek" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Friday, January 02, 2004 7:21 PM Subject: batch system access limits > > <sigh> > > I've just had my first really bad experience with OpenSRS support. A > fellow who yelled over my questions, and eventually answered "I don't > know" to things which I kind of think he should have been able to find > out easily. Perhaps he's just having a bad day. :-( Or perhaps I've > just become too accustomed to the excellent support I've previously > received from OpenSRS. > > The question, which this support guy (after some threatening sounding > "I know who you are" lines) agreed that discuss-list might be able to > answer better than himself, was with regard to access limits on > batch.opensrs.net. > > My understanding from (long-ago) discussions on the matter here was that > using rr-n1-tor for batch access would warrant account suspension or > public hanging or something, but batch.opensrs.net was available for > what e're I'd like to do, since the same availability guarantees were > not in place on that host. A cron job should be run on batch, leaving > rr-n1-tor for human use. > > Now I'm told that running an action=process-pending once per minute for > the week-end will probably get my account shut off. And (here's the > part that really bugs me) OpenSRS tech support is unable to tell me what > sort of access limits exist on batch.opensrs.net. > > The only ways to find out what access limits exist are apparently to > check my contract (which predates the existence of batch.opensrs.net, > though I also see no mention of this matter in the contracts currently > at resellers.tucows.com) or to contact my sales rep, who of course isn't > available for escalation until Monday. > > What's the deal here? Will a once-per-minute cron job running a GET on > batch.opensrs.net get my service terminated without notice? How about > once every two minutes? Five? Where's the documentation that says so? > > And why can't a tech support guy answer a question like "what's the > default access limit on the restriction you just told me about?" > > Or was the support guy still suffering from new year's eve? > > -- > Paul Chvostek <[EMAIL PROTECTED]> > it.canada http://www.it.ca/ >
