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

Sending Mails to Hitobito #33

Closed
maede97 opened this issue Nov 25, 2021 · 3 comments
Closed

Sending Mails to Hitobito #33

maede97 opened this issue Nov 25, 2021 · 3 comments

Comments

@maede97
Copy link

maede97 commented Nov 25, 2021

I managed to get everything up and running, and I currently want to test the mail features out (abo).
However, the email-adress is something like ...@localhost (which makes sense).
Mailcatcher does only catch incoming mails, which are sent for example when a user want's a password reset link. This does work.
However, is there a way to send a mail to the running hitobito application for it to be sent to the abo mailing lists?

@maede97 maede97 changed the title Sending Mails to a running docker-setup Sending Mails to Hitobito Nov 25, 2021
@carlobeltrame
Copy link
Member

carlobeltrame commented Nov 25, 2021

I don't think there is a way to do this yet. I also asked the same thing back on the predecessor of this project in nxt-engineering/hitobito-docker#1.
Hitobito itself cannot receive emails, you'd need a local mail server for that. Hitobito could then be configured (RAILS_MAIL_RETRIEVER_CONFIG) to fetch emails from a catch-all inbox on that local mail server, that's how we do it in production.

@mtnstar
Copy link
Member

mtnstar commented Nov 25, 2021

we do have a development test inbox (catch all) on our own mail server for development/testing.

maybe you could use something like https://greenmail-mail-test.github.io/greenmail/ or create a mail box on any mail server too. the challenge would be to have the mail headers set correctly.

https://github.com/hitobito/hitobito/blob/master/doc/e-mail/abo_mails.md

@olibrian
Copy link
Member

We will close this issue. No action needed. If not, feel free to reopen this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants