From a reader who wanted to comment on the ICANN Budget. No wonder the comment page is still blank after two weeks.
--
Date: 24 May 2006 18:17:52 -0000From: MAILER-DAEMON@yahoo.com
Subject: failure notice
Hi. This is the qmail-send program at yahoo.com.
I'm afraid I wasn't able to deliver your message to the followingaddresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<budget-comments@icann.org>:
192.0.34.36 does not like recipient.
Remote host said: 550 5.1.1 <budget-comments@icann.org>... Userunknown. Giving up on 192.0.34.36.
|
||||||
What ICANN Does With Public Comments on the Budget...
Keywords:
icann
Comments
Re: Time to Delete .IR?
Not that it matters - but how come that George Kirikos has left two comments before the time you've put in your blog? And did you try to see if it is working on your own? What was the result?
Re: What ICANN Does With Public Comments on the Budget...
The message failure was at 18:17 GMT (i.e. -0000), note the time zone. Since I was the one that sent/discovered the bouncing email, I know for a fact it wasn't working. Convert the failure time to Pacific time by subtracting 7 hours, i.e. 18:17 minus 7 hours = 11:17 Pacific time. Bret's post was at 12:27 Pacific time. The first email that made it through, after ICANN fixed it, was at 15:20 -0700 (i.e. Pacific time zone). Thus we have the message failure at 11:17 Pacific time, Bret's post at 12:27 Pacific time, and the first successful comment at 15:20 Pacifc time. The question "how come that George Kirikos has left two comments before the time you've put in your blog" obviously has a fatal flaw in it. When ICANN Board Members can't do simple timezone math, the staff doesn't have to worry very much about scrutiny of the Budget math... Trackbacks
TrackBack URL: |
Recent Comments
Recent Entries
Search
Month Archive
Login
|
|||||
