Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How do I configure & test email for reminders #860

Closed
fmcpherson opened this issue Jan 27, 2018 · 9 comments
Closed

How do I configure & test email for reminders #860

fmcpherson opened this issue Jan 27, 2018 · 9 comments

Comments

@fmcpherson
Copy link

I am trying to configure my install of Monica to send me reminders. I have obtained credentials for AWS SES and I believe I have my .env file configured correctly. However, there are a couple of things I am uncertain about. Is there any specific expectation for MAIL_PORT? What are the expected options for MAIL_ENCRYPTION? I have just changed it to yes.

My biggest issue is how to test my configuration. It seems I have to wait 24 hours for a reminder, it doesn't look like a new reminder set for today will immediate fire an email reminder.

I tried inviting a user, which would seem would immediately generate an email, gut when I click Invite a user by email, I get a "Whoops , looks like something went wrong" message, and the URL http://mycontacts.review/settings/users/save is in my address bar.

I don't know of the outbound email settings I have configured are wrong OR I am hitting a bug in monica.

@djaiss
Copy link
Member

djaiss commented Jan 27, 2018

@fmcpherson the way to test your notifications is to set a reminder with the date of the day, then run php artisan monica:sendnotifications in your terminal.

This will try to send the email using your credentials.

The Amazon SES driver requires a special treatment. You can read more on the official Laravel documentation, but basically you need to install a new package with composer, and update three keys in your config/services.php file.

According to AWS SES documentation, it seems that you can use 25 as the value for MAIL_PORT.

@djaiss
Copy link
Member

djaiss commented Jan 27, 2018

Also, if you still have problems after having tried the thing above, put APP_DEBUG=true in your .env file and try again in your browser. This will display the logs so we can help debug.

@fmcpherson
Copy link
Author

fmcpherson commented Jan 27, 2018 via email

@fmcpherson
Copy link
Author

fmcpherson commented Jan 27, 2018 via email

@fmcpherson
Copy link
Author

I've got it working using SES as an SMTP endpoint. I am going to write up a How-To for this, if you create a How-To folder under docs, I will contribute upon completion.

@djaiss
Copy link
Member

djaiss commented Jan 28, 2018

@fmcpherson great!

I use https://postmarkapp.com/ on .com personally. Locally I'm using the default SMTP server in Homestead.

If you could write up an How to about this, that would be awesome. Feel free to add a paragraph at the bottom of https://github.com/monicahq/monica/blob/master/docs/installation/generic.md.

@TomGranot
Copy link

@fmcpherson Did you end up writing something down? I wrote one that unfortunately doesn't work now. I'd be happy to move over to SES and would appreciate some pointers.

@akhiljalagam
Copy link

@fmcpherson the way to test your notifications is to set a reminder with the date of the day, then run php artisan monica:sendnotifications in your terminal.

This will try to send the email using your credentials.

The Amazon SES driver requires a special treatment. You can read more on the official Laravel documentation, but basically you need to install a new package with composer, and update three keys in your config/services.php file.

According to AWS SES documentation, it seems that you can use 25 as the value for MAIL_PORT.

its php artisan send:notifications

@github-actions
Copy link

This issue has been automatically locked since there
has not been any recent activity after it was closed.
Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 15, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants