I think we’re nearing the solution.
So I wrote Linode about opening the port 25 . Here is their response
Hello,
Before we can consider your request to remove SMTP restrictions, we’ll need some more information. Please provide us with the following:
Your name.
Your business or company name, if applicable.
A clear and detailed description of your email use case. Please include a description of how you’ll avoid sending unwanted emails.
The domain(s) that will be sending emails.
Links to public information (e.g. your business or application’s website, Twitter profile, GitHub, etc.)
We’ll review your request once you provide us with this information. If you have any additional questions or concerns that we can address for you, don’t hesitate to reach out to us. We’re always happy to help out however we can.
I have also responded to their message. Just waiting for them to approve and unblock.
Thank you all so much @cyberndt@Joe@shoulders@ID10T@jimr1
I will provide update once Linode gets back to me
Hello,
After taking another look at this, I can confirm that no restrictions were in place on your service. We had made a mistake on our end when asking for that relevant information. With that in mind, the likely issue lies with the internal configuration since we are not blocking your SMTP ports.
Our ability to troubleshoot this from our end is limited since we do not access the internal configurations of your services. However, we do have some valuable guides on how you can troubleshoot from your end. I will provide those below for reference.
They are having issues with their SASL connection because their script or client is not set up properly to connect to their email server. They are using mydomain.tld and not mail.mydomain.tld
@reigningking I had already mentioned above that your settings for your script is not set up properly.
Also make sure that mail.herbsofafrica.com is not being proxied in cloudflare and go direct to IP.
If you have IPV4 and IPV6 in your server? they should both be setup in your DNS for your mail server.
The title of this thread starts out with “Cant connect SMTP” but he had already shown above that his email had left the server through port 25. Yes, my mistake for not finishing my sentence about his script not being set up properly for SASL Connection. My apologies…
And cyberndt has also provided a solution to that problem (use an address that is not being proxied by Cloudflare).
You need to focus on one problem (and I need you to focus on one problem). Port 25 is unrelated to your SASL authentication problem, so let’s forget about port 25 for this thread.
I didn’t ignore it, in fact this may very well solve the problem. As soon as cloudflare gets involved I switch off. I just don’t see the point of cloudflare apart from ‘another thing’ to configure and maintain