better auth `sendVerificationEmail` jwt token detected as spam by gmail
I've narrowed down my email templates getting detected as spam by gmail address. When the email contains a URL with the
?token=eyJWTToken.Like.This -- starting today the email always gets flagged as spam. I've tried sending the emails through both ses and sendgrid with same results on my tests. When replacing the token string param on the url in sendVerificationEmail before putting it in my email template -- for example, swapping eyJWTOKen value with perhaps a number 918273981723897123, EG: ?token=1298731928739812731&callbackURL=/ the email will NOT get flagged as spam by gmail. My theory is that google just "learned this" and is now reporting any email with URLs looking like these as spam, wondering if anyone else has hit this yet. As far as workaround goes, I don't see any other way to verify emails or if we can customize the token ? Perhaps enter a 6 digit OTP code to verify the email? (not log in)0 Replies