-
-
Notifications
You must be signed in to change notification settings - Fork 270
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
outgoing not working with atlas mongodb #767
Comments
Sorry, but this not enough information to give any useful answer |
I changed the MongoDB connection string in the dbs.toml file to an Atlas MongoDB connection string. After this change, outgoing emails are not being delivered to destination users. |
Did you do any troubleshooting? Did you check any logs? Any database contents? |
i have below logs when restart zone-mta |
Your logs are cut off |
Dbs are not created in mongo atlas . i have below warning when change mongo atlas url |
That's just a deprecation warning, doesn't have any effect on anything.
Maybe create the dbs? How are they supposed to authenticate and connect to databases that don't exist? I'm sorry if I seem unhelpful, but there's barely any information to work with here. Even after asking multiple times, I haven't seen any relevant logs or troubleshooting from your side. |
The dbs.toml file exists in two locations: /etc/wildduck/dbs.toml and /opt/wildduck/dbs.toml. Replacing 'mongodb' in both will resolve the issue. |
I switched MongoDB to the cloud. After migrating to the cloud, outgoing messages are not being delivered.
The text was updated successfully, but these errors were encountered: