Checklist
[ Y] I have read intro post: About the Installation Issues category
[ Y] I have read the tutorials, help and searched for similar issues
[ Y] I provide relevant information about my server (component names and versions, etc.)
[Y ] I provide a copy of my logs and healthcheck
[ Y] I describe the steps I have taken to trouble shoot the problem
[ Y] I describe the steps on how to reproduce the issue
Hey guys I know I had a thread going yesterday but here is a new one. So yesterday I tried passbolt on docker, and bare Debian 11. In both cases I was completely unable to send SMTP. Test emails work great but as far as verifying people it is no good. Today I booted it up in rocky linux, honestly the smoothest installation yet and I am a big fan of RHEL so this was right up my alley. However I have the same damn issue with SMTP. I have gone through just about everything at this point, any basic troubleshooting has been completed. The only thing that I can imagine is that when sending via test email it is accepting your inputs and making that smtp query therefore it works flawlessly, however whenever it is saved it has got to be stored somewhere incorrectly or inaccessible. This seems to be a frequent issue amongst others as well so what gives? Any input would be greatly appreciated, could I even go as far as to disable SMTP verification? Would it be an option to be solely reliant on Pass + TOTP?
It may be hard to believe but email issues are predominantly about settings, and then the rest are about simple things. Rarely is passbolt not able to do email.
If the manual test works, that’s great news. There is a cron job which runs the queued mail each minute. Nothing else to it, really.
It doesnt make sense just trying to figure out what is different. I cant even send a verify to the email that it is coming from, yet the test emails work great. So what would be the difference here that is leading to the verify to be labeled as spam? The links by chance? Also in this case it is showing in the db as sent 0. It isnt even making it to spam, it is not sending at all. Additionally I already have dkim and spf configured.
When you use passbolt to send an email via your Titan mail account, it then turns and sends it to the receiving mail service. If the receiving mail service is saying 550, then passbolt gets a 550.
The test email goes to no-reply@passbolt as a way to verify your SMTP settings without complicating the matter. However, in practice the end receiver of emails may be stricter.
If you are not able to send a verification email to your account at Titan, what is the result of the test command when you do that?
See this discussion for how the test email (at least in the past) was different than actual emails. This is the intent of my questions.
The good news is that the issues are all resolvable. But it’s important to understand that the passbolt app has no control (obviously) over external mail provider settings or requirements.
Here is an example of my test emails getting through great no problem. Functions sending to Titan, Gmail, Yahoo, Outlook, and ZOHO. 0 problems. but verification or new user emails all return 550 no matter what.
I believe you. Can you provide actual logs or something more specific? It’s a technical matter.
Please check /var/log/mail.log or other system logs for additional errors we can work with.
Can you also provide your passbolt mail config settings (change what you need, but make it meaningful enough so we understand it). You may have provided it before, but that was another thread, thanks.
