Weird email address received from email sent from an iPhone

Discussion in 'Networking & Security' started by vsboxerboy, Nov 7, 2012.

Thread Status:
Not open for further replies.
  1. vsboxerboy

    vsboxerboy 2[H]4U

    Messages:
    3,696
    Joined:
    Oct 17, 2005
    My friend has an iPhone (the 2G I think ... yeah super old) and when she sends a reply, I get a weird email address for her sender. It shows up as:

    Code:
    Q-2 zzqqzzzz122 Q1a2., E Q. Eye Qw
     
    Last edited: Nov 8, 2012
  2. evilsofa

    evilsofa [H]ardForum Junkie

    Messages:
    10,088
    Joined:
    Jan 1, 2007
    I would guess that she created her gmail account on a desktop computer, and at some point was attempting to play a game in one window while the text she was generating was being entered into her gmail account profile name field.

    Edit: removed the person's email address.
     
    Last edited: Nov 8, 2012
  3. vsboxerboy

    vsboxerboy 2[H]4U

    Messages:
    3,696
    Joined:
    Oct 17, 2005
    Ha! That's possible - I'll ask about that. I guess that is the name fileld, not the email field so that could make sense.
     
  4. Jay_2

    Jay_2 2[H]4U

    Messages:
    3,584
    Joined:
    Mar 20, 2006
    it could also be that she has odd characters in her name field as well.
     
  5. vsboxerboy

    vsboxerboy 2[H]4U

    Messages:
    3,696
    Joined:
    Oct 17, 2005
    Good point, her name is spelled with the dots over the ë. Maybe some weird encoding issue then?
     
    Last edited: Nov 8, 2012
  6. schnell

    schnell Gawd

    Messages:
    763
    Joined:
    Jul 22, 2005
    Yup. Sounds like a unicode translation issue.
     
  7. Jay_2

    Jay_2 2[H]4U

    Messages:
    3,584
    Joined:
    Mar 20, 2006
    Post removed
     
    Last edited: Nov 8, 2012
  8. vsboxerboy

    vsboxerboy 2[H]4U

    Messages:
    3,696
    Joined:
    Oct 17, 2005
    This was the problem. Not sure how it happened, but she either inadvertently set it to something odd or it pulled her name from elsewhere and didn't encode it properly like Jay_oasis said.which is probably more likely
     
Thread Status:
Not open for further replies.