Friday, April 07, 2006

Curiouser & Curiouser ... more about the (916) 399-7992 number claiming to be Apple

(916) 399-7992


About 3 weeks ago I brought you the exclusive news and commentary on the strange (916) 399-7992 number that claims to be Apple Computer that has been calling people for years ... often with rude and aggressive sales people. I never got a "response" from Apple Support about it and now something weird has happened ... almost continuing this like some weird illuminati plot. My best guess is that this is a third party firm hired by Apple to push Applecare ... but I will get an answer by Monday.

More about the (916) 399-7992 number claiming to be Apple ...

Posted for your perusal:

----- The following addresses had permanent fatal errors -----

(reason: 550 5.1.6 Recipient no longer on server: les.d@apple.com)

----- Transcript of session follows -----
... while talking to sage.apple.com.:
DATA
<<< 550 5.1.6 Recipient no longer on server: les.d@apple.com
550 5.1.1 ... User unknown
<<< 554 5.5.0 No recipients have been specified.
Reporting-MTA: dns; relay3.apple.com
Received-From-MTA: DNS; mail-in2.apple.com
Arrival-Date: Fri, 7 Apr 2006 15:49:59 -0700 (PDT)

Final-Recipient: RFC822; les.d@apple.com
Action: failed
Status: 5.1.6
Remote-MTA: DNS; sage.apple.com
Diagnostic-Code: SMTP; 550 5.1.6 Recipient no longer on server: les.d@apple.com
Last-Attempt-Date: Fri, 7 Apr 2006 15:49:59 -0700 (PDT)

From: Philip Smith <>
Date: April 7, 2006 6:49:56 PM EDT
To: Les Dominguez
Subject: case #60408360


I never received a reply regarding this issue. It has almost been 30 days since the case was opened. What did "corporate escalation" have to say?


On Mar 9, 2006, at 1:33 PM, Les Dominguez wrote:

Hello Mr. Smith!

Here's the case number that I've escalated to Corporate.
It is 60408360.
Also, you can reach me at 800-275-2273, option 89, Ext. 40246.
E-mail me anytime
because I check my e-mail constantly!

Les
Apple Customer Relations


Of note in this returned email: Recipient no longer on server

Of note also: this extension no longer exists.

I'm going to place another call into customer service Monday ... it's time we got to the bottom of this issue.

No comments: