Well the article is about me although I don't know exactly whats going on I have an idea. One of the companys involved, Vocel, responded to one of my emails suggesting maybe they were sending out messages with a blank as in "To:" field and they responded that yes they found a bug that caused just that. Their response between making contact and them fixing it was mere hours. Anyways I think that messages with a blank To: field either get converted to "To: (null)" or it just bitbuckets them somewhere in the code to "null". Here is an example messages that makes me think its the former:
Fr: (null) (null) CB#:
Notice that (null) is actually a string that Verizon must be filling in when a field is blank. Perhaps somewhere along the line they replces blank fields with "(null)" and later on when its actually being processed for the recipient the disallowed '(' ')' are removed and thus it ends up going to null@vtext.com.
Yeah well my text message box only holds 50 messages and is full so I won't be finding out until I empty it and I won't be doing that anytime soon. Plus disabling txt msgs from the internet and e-mail doesn't hurt either. Sorry to disappoint, although at some point I will enjoy reading some of them;)
I'm the one the article is written about and I chose the name just because it was the name I had been using in forums at the time. I never assumed for even a minute it would be a problem, nevermind a plague. Fortunately vtext.com gives you the ability not to recieve txt msgs from the internet or e-mail.
Well I'm the fool the article is written about and I got and forgot so many its hard to say. Not many of them were entertaining, more informative than anything else. I'd have to say though the wierdest and by far most annoying messages are:
Fr: (null) (null) CB#:
That's it. I've been getting them since the beginning, and the time I waste erasing empty messages from nobody always strikes me as odd.
Slashdot Mirror
Well the article is about me although I don't know exactly whats going on I have an idea. One of the companys involved, Vocel, responded to one of my emails suggesting maybe they were sending out messages with a blank as in "To:" field and they responded that yes they found a bug that caused just that. Their response between making contact and them fixing it was mere hours. Anyways I think that messages with a blank To: field either get converted to "To: (null)" or it just bitbuckets them somewhere in the code to "null". Here is an example messages that makes me think its the former:
Fr: (null)
(null)
CB#:
Notice that (null) is actually a string that Verizon must be filling in when a field is blank. Perhaps somewhere along the line they replces blank fields with "(null)" and later on when its actually being processed for the recipient the disallowed '(' ')' are removed and thus it ends up going to null@vtext.com.
Yeah well my text message box only holds 50 messages and is full so I won't be finding out until I empty it and I won't be doing that anytime soon. Plus disabling txt msgs from the internet and e-mail doesn't hurt either. Sorry to disappoint, although at some point I will enjoy reading some of them ;)
I'm the one the article is written about and I chose the name just because it was the name I had been using in forums at the time. I never assumed for even a minute it would be a problem, nevermind a plague. Fortunately vtext.com gives you the ability not to recieve txt msgs from the internet or e-mail.
Well I'm the fool the article is written about and I got and forgot so many its hard to say. Not many of them were entertaining, more informative than anything else. I'd have to say though the wierdest and by far most annoying messages are:
Fr: (null)
(null)
CB#:
That's it. I've been getting them since the beginning, and the time I waste erasing empty messages from nobody always strikes me as odd.