Auth and Email Sending Issues
I'm using Wasp's built-in auth system, but when my user signs up using email and password, sometimes they cannot receive a verification email and therefore cannot signup.
- I'm using Mailgun as the email provider
- In most cases, they are using outlook and I've already seen many complains about the email deliverability when sending to outlook addresses since outlook rejects many emails (not even showing them in spam) if you are using a new domain.
Therefore, I'm wondering:
1. What do you guys use for sending transactional emails? Does it has issues when sending to outlook addresses?
2. An alternative is Don't verify email address when sign up. As far as I know many web apps are already doing this to increase their sign-up conversion (although there're some security issues). Is that possible using custom sign-up actions? (I don't want to use the username-and-password sign-up)https://wasp.sh/docs/auth/advanced/custom-auth-actions
- I'm using Mailgun as the email provider
- In most cases, they are using outlook and I've already seen many complains about the email deliverability when sending to outlook addresses since outlook rejects many emails (not even showing them in spam) if you are using a new domain.
Therefore, I'm wondering:
1. What do you guys use for sending transactional emails? Does it has issues when sending to outlook addresses?
2. An alternative is Don't verify email address when sign up. As far as I know many web apps are already doing this to increase their sign-up conversion (although there're some security issues). Is that possible using custom sign-up actions? (I don't want to use the username-and-password sign-up)https://wasp.sh/docs/auth/advanced/custom-auth-actions
If you need to deeply hook into the sign-up process, you can create your own sign-up action and customize the code to, for example, add extra validation, store more data, or otherwise call custom code at registration time.
