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

Email does not work #90

Open
DominikWA opened this issue Aug 14, 2023 · 0 comments
Open

Email does not work #90

DominikWA opened this issue Aug 14, 2023 · 0 comments

Comments

@DominikWA
Copy link

When deploying Dataverse as described in the readme, and with basic email configuration (simple smtp server without authentication) sending emails will not work. While the fist time docker compose starts Dataverse I can verify in the Payara Administration Console on port 4848 that the correct JavaMail Session “mail/notifyMailSession” is created with the values provided via the config files. The strange thing is that the whole JavaMail Session disappears after the deployment is finished.

.env – config
........
system_email=dataverse@domain.org
mailhost=IP Address
#mailuser=mailuser
no_reply_email=no_reply_email_dataverse@domain.org
#smtp_password=smtp_password
smtp_port=25
#socket_port=socket_port
........

docker-compose.yml – config
........
"MAIL_SERVER=IP Address"
........

After the JavaMail Session is disappeard, I can docker exec in to the Dataverse container and recreate it with this asadmin command:

create-javamail-resource --mailhost=IP Address --mailuser=dataversenotify --fromaddress=dataverse@domain.org mail/notifyMailSession

The JavaMail Session then persists and I can successfully login with the default credentials and set the admin email address, and successfully send a verification email to it.

Do you have any idea how to proceed?

@pdurbin pdurbin changed the title Email dose not work Email does not work Aug 14, 2023
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

1 participant