When sending a magic link to sign-in to our nhost instance, our links in emails are being flagged in Gmail as "suspicious".

For us this issue is pretty severe because we can't risk sending these. We have some thoughts on solutions:

1. Friendly word URLs. It's possible that the subdomain character arrangement looks really spammy to Google's inspection. (e.g. zzxhjsdjksdhfuybsk) so perhaps changing this to an approach similar to https://github.com/glitchdotcom/friendly-words might help?

2. Granular access to link segments in templates. Maybe if we could construct the links ourselves with a custom domain. Ideally the sender domain and link domain would match but we know that custom domains aren't currently on the roadmap. Right now the template can see {link} but if there was {host} or {path} or {params} or similar we could proxy to our nhost backend?

3. Server configuration. There might be some additional work that nhost could do to mollify Google etc via DKIM or something but my guess is y'all have done a lot of that work already

@massless That's some really good feedback. Would you mind opening a GitHub issue for this so it won't get lost here in Discord? https://github.com/nhost/nhost/issues/new