Not signed in (Sign In)

Tech Support: Changing "To:" field when replying does not take

Bottom of Page

1 to 11 of 11

  1.  
  1.  
    I just ran across a bug in 1.09.18. When you "reply" to an email, erase the address, and enter another, the Peek uses the original.

    For example:
    I had a Facebook email update that my wife had replied to a comment of mine. This email came from noreply@facebook.com, or something similar. So after I selected "reply", I erased all of the address bits in the To: field, and replaced them with her info. A few minutes later, I get a bounce notice saying that my email to noreply@facebook.com was undeliverable. Weird. The email in my Sent folder on my Peek says it was sent to my wife; the Sent folder on the web interface of gmail says it was sent to noreply@facebook.com.

    Just wanted to make sure you guys had something to work on for 1.10!
    •  
      CommentAuthortmel
    • CommentTimeOct 13th 2009
     
    Just replicated this on my device using Gmail.

    Going to investigate with another email provider, it's possible that we ignore any address entered in when replying and sending to the original sender only.
    •  
      CommentAuthortmel
    • CommentTimeOct 13th 2009 edited
     
    So, here is what I did if anyone is curious!

    1. Sent test email to account A
    2. Email is received on Peek from account A
    3. Reply to email > change "to:" address to account B
    4. Reply is received on account A, not B.

    We currently ignore any address other then the original senders address when replying to an email. Best solution I can offer right now is to reply to the original sender, and cc your wife. Forwarding could work as well!
    • CommentAuthorgabe
    • CommentTimeOct 13th 2009
     
    @minimicrite - unfortunately, we broke it. We're going to patch it in the next couple of days. The issue is not on the device side, it's on the Peek backend systems.

    Thanks for pointing it out. We found out about the issue late last week from some routine testing.
  5.  
    No worries, and thanks for the quick update. It wasn't a massive deal; I've just gotten into the habit of changing the To: field rather than forwarding because of all the inane >'s that email clients insist on putting on forwards.
    • CommentAuthordarkxsun
    • CommentTimeOct 17th 2009
     
    @gabe et al, could you check if this is related?

    http://boards.getpeek.com/discussion/1436/10918-possible-bug/
    • CommentAuthorgabe
    • CommentTimeOct 18th 2009
     
    Yeah it's all related. It will be fixed in the next week or so.
    • CommentAuthordarkxsun
    • CommentTimeOct 26th 2009
     
    Is this patch pushed? I had heard 10/26.
    • CommentAuthorgabe
    • CommentTimeOct 26th 2009
     
    We're still testing a few other things that are going into the release. We are shooting for this week.

    Thanks
    • CommentAuthordarkxsun
    • CommentTimeOct 26th 2009
     
    Will there be some notification or should i just keep trying test mails regarding this issue?
    • CommentAuthorgabe
    • CommentTimeOct 26th 2009
     
    We will let you know. I'll post it on the boards once the fix is in.

1 to 11 of 11

  1.