Autoconnect requests for hey-mail

I’d like to request these autoconnections for the email app hey-mail, for using a hardware security key to log in to the app and accessing common directories for reading/writing attachments:

  • hardware-observe
  • u2f-devices
  • removable-media

[previous discussion]

1 Like

+1 for hardware-observe and u2f-devices

For removable-media, hey-mail doesn’t precisely fit the current policies for removable-media. Have you read through that section?

In a lot of ways, email clients are like browsers: they typically have web renderers and they have a need for attaching documents, so I think perhaps we should extend our processes to include ‘major email clients’? @pedronis - what do you think?


  • what is your relationship to hey-mail? Are you the official upstream?
  • what is the maturity level of hey-mail? How many users do you have or OSes/distributions do you support (exact numbers not required of course, just trying to gauge maturity)?

I suppose they also don’t write or read from non-scratch/non-application disk parts without user confirmation usually? Do they get the same maintenance attention that browsers get? Also OTOH is it common and frequent to ingest or save attachments to removable media? it might be.

@jdstrand, yes, I’m from Basecamp (makers of HEY) and the official upstream. hey-mail is an Electron app, and across OSes there are >10k users.

+1 from me too for auto-connect of u2f-devices and hardware-observe to support hardware security keys in hey-mail. I also tend to agree this is very similar to the web-browsers use-case for auto-connect of removable-media, so FWIW since this is being published officially by the upstream project, +1 from me too for removable-media as well.