Q.: T-Mo text messages arriving for another's handle ...

Need help formulating for the T-Mo CC reps the nature of this problem:

Three times today -- at 1:17 pm EST, at 1:47 pm EST, and again around 2:15 EST,
my handset received an MMS that was originated from TWITTER and directed to a
NICKNAME@tmomail.net address, NICKNAME being an eight-character username of the
sort that T-Mo permits use of instead of the subscriber's 10-digit phone number.

Only problem is, while I *do* have such a username, this NICKNAME wasn't it
(eight's not even the right number of characters to be mine :-) ).

I tried to get a T-Mo CC rep today to understand the problem well enough to
look into the T-Mo username-to-subscribernumber database, and expunge the
incorrect lookup entry linking NICKNAME with my number.

I failed -- CC rep suggested instead that *I* change something in my TWITTER settings
-- huh? I have no TWITTER settings: I have no account at, nor dealings with, TWITTER,
not now, nor ever did have, nor probably will ever have in future.

So: how do I explain better what I'm upset at, and what I need fixed?

TIA; and cheers, -- tlvp

PS: again today, a solid hour on hold before a CC rep materialized -- sounding like
a spirit-waif from Manila. Snow still shutting down all the State-side call centers?
--
Avant de repondre, jeter la poubelle, SVP

In message <op.vrd0piteitl47o@acer250.gateway.2wire.net> someone
claiming to be tlvp <tPlOvUpBErLeLsEs@hotmail.com> typed:

>Need help formulating for the T-Mo CC reps the nature of this problem:
>
>Three times today -- at 1:17 pm EST, at 1:47 pm EST, and again around 2:15 EST,
>my handset received an MMS that was originated from TWITTER and directed to a
>NICKNAME@tmomail.net address, NICKNAME being an eight-character username of the
>sort that T-Mo permits use of instead of the subscriber's 10-digit phone number.
>
>Only problem is, while I *do* have such a username, this NICKNAME wasn't it
>(eight's not even the right number of characters to be mine :-) ).
>
>I tried to get a T-Mo CC rep today to understand the problem well enough to
>look into the T-Mo username-to-subscribernumber database, and expunge the
>incorrect lookup entry linking NICKNAME with my number.
>
>I failed -- CC rep suggested instead that *I* change something in my TWITTER settings
>-- huh? I have no TWITTER settings: I have no account at, nor dealings with, TWITTER,
>not now, nor ever did have, nor probably will ever have in future.
>
>So: how do I explain better what I'm upset at, and what I need fixed?
>
>TIA; and cheers, -- tlvp
>
>PS: again today, a solid hour on hold before a CC rep materialized -- sounding like
>a spirit-waif from Manila. Snow still shutting down all the State-side call centers?

The easiest fix might be to see if you can determine the nickname.

I've never used T-Mobile's nicknames or their MMS, but assuming it's
available, you can probably deal with the problem from the Twitter side
of things more easily than you can get through to T-Mobile.

I take it you have a nickname already? The reason I ask, with Rogers
(in Canada)'s nickname system, if you assign a new one it unassigns the
old one, so the fix for this type of problem is to assign a new
nickname.

On Thu, 24 Feb 2011 21:24:10 -0500, DevilsPGD <Still-Just-A-Rat-In-A-Cage@crazyhat.net> wrote:

> In message <op.vrd0piteitl47o@acer250.gateway.2wire.net> someone
> claiming to be tlvp <tPlOvUpBErLeLsEs@hotmail.com> typed:
>
>> Need help formulating for the T-Mo CC reps the nature of this problem:
>>
>> Three times today -- at 1:17 pm EST, at 1:47 pm EST, and again around 2:15 EST,
>> my handset received an MMS that was originated from TWITTER and directed to a
>> NICKNAME@tmomail.net address, NICKNAME being an eight-character username of the
>> sort that T-Mo permits use of instead of the subscriber's 10-digit phone number.
>>
>> Only problem is, while I *do* have such a username, this NICKNAME wasn't it
>> (eight's not even the right number of characters to be mine :-) ).
>>
>> I tried to get a T-Mo CC rep today to understand the problem well enough to
>> look into the T-Mo username-to-subscribernumber database, and expunge the
>> incorrect lookup entry linking NICKNAME with my number.
>>
>> I failed -- CC rep suggested instead that *I* change something in my TWITTER settings
>> -- huh? I have no TWITTER settings: I have no account at, nor dealings with, TWITTER,
>> not now, nor ever did have, nor probably will ever have in future.
>>
>> So: how do I explain better what I'm upset at, and what I need fixed?
>>
>> TIA; and cheers, -- tlvp
>>
>> PS: again today, a solid hour on hold before a CC rep materialized -- sounding like
>> a spirit-waif from Manila. Snow still shutting down all the State-side call centers?
>
> The easiest fix might be to see if you can determine the nickname.

That's no problem, it shows up right in the To:-line of the MMS on my handset.

> I've never used T-Mobile's nicknames or their MMS, but assuming it's
> available, you can probably deal with the problem from the Twitter side

Perhaps I could, *if* I had a twitter account. But I *don't*, never did,
and don't really mean to get one just to "fix" this T-Mo problem.

> of things more easily than you can get through to T-Mobile.
>
> I take it you have a nickname already?

I certainly *did* have a T-Mo nickname before these MMSes came in, I should
check whether it's still valid ... [checks] ... yup, test email to *my* T-Mo
nickname arrives as SMS on *my* handset. So at least that's not broken :-) .

> ... The reason I ask, with Rogers
> (in Canada)'s nickname system, if you assign a new one it unassigns the
> old one, so the fix for this type of problem is to assign a new
> nickname.

I need to convince T-Mo that messages for someone *else*'s nickname are
mistakenly getting routed to *my* handset. They ought to want to fix that.
But I can't get them even to understand that's what's going on.

Cheers, -- tlvp
--
Avant de repondre, jeter la poubelle, SVP

In <op.vrfw8efyitl47o@acer250.gateway.2wire.net> tlvp <tPlOvUpBErLeLsEs@hotmail.com> writes:

>I need to convince T-Mo that messages for someone *else*'s nickname are
>mistakenly getting routed to *my* handset. They ought to want to fix that.
>But I can't get them even to understand that's what's going on.

Have you tried writing to their corp hq? I've found
that letters to:

Office of Robert Dotson
CEO, T-Mobile
12920 SE 38th Street.
Bellevue, WA 98006

tend ot get a response from someone who usually
has a reasonable amount of knowledge.


--
__________________________________________________ ___
Knowledge may be power, but communications is the key
dannyb@panix.com
[to foil spammers, my address has been double rot-13 encoded]

On Thu, 24 Feb 2011 23:00:33 -0500, danny burstein <dannyb@panix.com> wrote:

> In <op.vrfw8efyitl47o@acer250.gateway.2wire.net> tlvp <tPlOvUpBErLeLsEs@hotmail.com> writes:
>
>> I need to convince T-Mo that messages for someone *else*'s nickname are
>> mistakenly getting routed to *my* handset. They ought to want to fix that.
>> But I can't get them even to understand that's what's going on.
>
> Have you tried writing to their corp hq? I've found
> that letters to:
>
> Office of Robert Dotson
> CEO, T-Mobile
> 12920 SE 38th Street.
> Bellevue, WA 98006
>
> tend ot get a response from someone who usually
> has a reasonable amount of knowledge.

From your keyboard, danny, to my Rol-O-Dex :-) ! Thank you!

Cheers, -- tlvp
--
Avant de repondre, jeter la poubelle, SVP

In message <op.vrfw8efyitl47o@acer250.gateway.2wire.net> someone
claiming to be tlvp <tPlOvUpBErLeLsEs@hotmail.com> typed:

>On Thu, 24 Feb 2011 21:24:10 -0500, DevilsPGD <Still-Just-A-Rat-In-A-Cage@crazyhat.net> wrote:
>
>> The easiest fix might be to see if you can determine the nickname.
>
>That's no problem, it shows up right in the To:-line of the MMS on my handset.

Excellent.

>> I've never used T-Mobile's nicknames or their MMS, but assuming it's
>> available, you can probably deal with the problem from the Twitter side
>
>Perhaps I could, *if* I had a twitter account. But I *don't*, never did,
>and don't really mean to get one just to "fix" this T-Mo problem.

Having a Twitter account wouldn't help. Rather, my suggestion would be
to attempt to do a password recovery for the Twitter account (from your
computer), retrieve the password, post what a complete moron the guy is
on his Twitter feed and disable the notifications.

On Sat, 26 Feb 2011 00:20:17 -0500, DevilsPGD <Still-Just-A-Rat-In-A-Cage@crazyhat.net> wrote:

> In message <op.vrfw8efyitl47o@acer250.gateway.2wire.net> someone
> claiming to be tlvp <tPlOvUpBErLeLsEs@hotmail.com> typed:
>
>> On Thu, 24 Feb 2011 21:24:10 -0500, DevilsPGD <Still-Just-A-Rat-In-A-Cage@crazyhat.net> wrote:
>>
>>> The easiest fix might be to see if you can determine the nickname.
>>
>> That's no problem, it shows up right in the To:-line of the MMS on my handset.
>
> Excellent.
>
>>> I've never used T-Mobile's nicknames or their MMS, but assuming it's
>>> available, you can probably deal with the problem from the Twitter side
>>
>> Perhaps I could, *if* I had a twitter account. But I *don't*, never did,
>> and don't really mean to get one just to "fix" this T-Mo problem.
>
> Having a Twitter account wouldn't help. Rather, my suggestion would be
> to attempt to do a password recovery for the Twitter account (from your
> computer), retrieve the password, post what a complete moron the guy is
> on his Twitter feed and disable the notifications.

One problem: what does *not* show up is the *Sender* of this MMS.

Two names ("Julia", in a sentence "I am Julia, 22 y.o."; and "JAIME Dawkins" (with no further detail) in a From: line) and that NICKNAME appear in the context of the message, no idea which to think to do a password recovery against -- nor how to proceed with such.

(Sigh!) At least there've not been any more of these MMSes :-) .

Cheers, -- tlvp



--
Avant de repondre, jeter la poubelle, SVP