{"action":"created","issue":{"url":"https://api.github.com/repos/roundcube/roundcubemail/issues/5177","repository_url":"https://api.github.com/repos/roundcube/roundcubemail","labels_url":"https://api.github.com/repos/roundcube/roundcubemail/issues/5177/labels{/name}","comments_url":"https://api.github.com/repos/roundcube/roundcubemail/issues/5177/comments","events_url":"https://api.github.com/repos/roundcube/roundcubemail/issues/5177/events","html_url":"https://github.com/roundcube/roundcubemail/issues/5177","id":144568118,"number":5177,"title":"TLS indicator for received mails","user":{"login":"mschilt","id":10913091,"avatar_url":"https://avatars.githubusercontent.com/u/10913091?v=3","gravatar_id":"","url":"https://api.github.com/users/mschilt","html_url":"https://github.com/mschilt","followers_url":"https://api.github.com/users/mschilt/followers","following_url":"https://api.github.com/users/mschilt/following{/other_user}","gists_url":"https://api.github.com/users/mschilt/gists{/gist_id}","starred_url":"https://api.github.com/users/mschilt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mschilt/subscriptions","organizations_url":"https://api.github.com/users/mschilt/orgs","repos_url":"https://api.github.com/users/mschilt/repos","events_url":"https://api.github.com/users/mschilt/events{/privacy}","received_events_url":"https://api.github.com/users/mschilt/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-03-30T12:06:45Z","updated_at":"2016-03-30T13:28:58Z","closed_at":null,"body":"I would like to have an indicator whether an email was received over TLS.\r\n\r\nGMail recently introduced a similar feature on safer internet day that shows users potentially unsafe senders.\r\n\r\nFor this feature\r\n1. email header needs to be parsed for the right 'Received' line\r\n2. indicator tag (lock symbol) needs to be placed somewhere in the message \r\n3. Optional: displaying the used cipher suite would be a plus (can also be parsed from the header). Maybe as a mouse-over hint on the indicator tag.\r\n\r\nReferences:\r\nhttps://googleblog.blogspot.ch/2016/02/building-safer-web-for-everyone.html\r\nhttps://security.googleblog.com/2016/03/more-encryption-more-notifications-more.html"},"comment":{"url":"https://api.github.com/repos/roundcube/roundcubemail/issues/comments/203432622","html_url":"https://github.com/roundcube/roundcubemail/issues/5177#issuecomment-203432622","issue_url":"https://api.github.com/repos/roundcube/roundcubemail/issues/5177","id":203432622,"user":{"login":"sebix","id":199050,"avatar_url":"https://avatars.githubusercontent.com/u/199050?v=3","gravatar_id":"","url":"https://api.github.com/users/sebix","html_url":"https://github.com/sebix","followers_url":"https://api.github.com/users/sebix/followers","following_url":"https://api.github.com/users/sebix/following{/other_user}","gists_url":"https://api.github.com/users/sebix/gists{/gist_id}","starred_url":"https://api.github.com/users/sebix/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/sebix/subscriptions","organizations_url":"https://api.github.com/users/sebix/orgs","repos_url":"https://api.github.com/users/sebix/repos","events_url":"https://api.github.com/users/sebix/events{/privacy}","received_events_url":"https://api.github.com/users/sebix/received_events","type":"User","site_admin":false},"created_at":"2016-03-30T13:28:58Z","updated_at":"2016-03-30T13:28:58Z","body":"It is hard to determine which transport is relevant, if the underlying mail infrastructure is completely unknown. Roundcube does only know the first hop outgoing, but nothing about the ingoing queue, internal networks and hops etc.\r\n\r\nWhat could be done are heuristics based on FQDNs and IPs."}}