Security function for side conversations

3 Commentaires

  • Toby Sterrett
    Zendesk Product Manager

    Thanks for the suggestion Lelia Wencke, I've written it down. Drafts should be saved, but it could be much better.

    As for the email address, do you mean an address that is not already a user in the system?

    0
  • Lelia Wencke

    Hello Toby, thanks for taking my suggestion. For the mail I mean that if I have for example the address Example@examplemail.org and then I accidentally use example@exxxamplemail.org instead of the actual address no warning comes that the second mail address does not exist. It would be nice if there was a message like "Mail could not be delivered, address invalid".

    1
  • Toby Sterrett
    Zendesk Product Manager

    I see, thanks for the details. This is tricky because, technically, example@exxxamplemail.org is a valid email address as far as we know (it's a valid email address that could be valid). We'd only know if it's invalid if a bounce from a server is received. However, we don't receive those bounces due to some underlying technicalities deep in the Zendesk code base that we don't have the ability to change.

    One signal, though, would be to only use addresses that autocomplete, rather than typing in new addresses. If you're confident that all the addresses you're sending to should already be in your users database, autocompleting everything should work. But, if you need to add new recipients on the fly, that doesn't work.

    One thing I've heard folks talking about is building a more advanced delivery status indicator on emails. That would be done by a different team, and I don't have any sort of confirmation that it will happen, but if it does we'd try to take advantage of that for side conversations as well.

    0

Vous devez vous connecter pour laisser un commentaire.

Réalisé par Zendesk