I’ve been using this service for a couple of days now, and it’s made my internet access so much faster. That alone is a plus, and I never thought there would be a contender for Cloudflare in this area.
Tutorial for secure emailing with personal domain,Cloudflare, virtualmin and postfix
Unsolved
Linux
-
@DownPW said in Tutorial for secure emailing with personal domain,Cloudflare, virtualmin and postfix:
For example, I am login to virtualmin on adm.xxxx.fr (hostname of my server) so my mx field should be adm.xxxx.fr and not root.xxxx.fr right?
Yes, correct.
@DownPW said in Tutorial for secure emailing with personal domain,Cloudflare, virtualmin and postfix:
For DKIM, I don’t quite understand. Once generated in the tools you gave, I understand for the DNS entry in CF but what do I do with the private and public key?
The private and public key can simply be stored. You do not have to do anything with these.
-
@DownPW said in Tutorial for secure emailing with personal domain,Cloudflare, virtualmin and postfix:
Seems port 25 OK
Not sure about that - see below from your server. When sending a
telnetrequest on port 25, there is no response. This typically means the port is closed on your side.
What SHOULD happen is this
However, it DOES respond on port 587
From recollection, your VPS is being hosted by Hetzner. Although you have no firewall rules in place to prevent outbound connections on port 25, Hetzner by default will block this port until you’ve paid at least one month’s billing, and will only release the block if you formally request it. You’ll need to get the port unblocked before you can proceed - see below
https://docs.hetzner.com/cloud/servers/faq/#why-can-i-not-send-any-mails-from-my-server
Unfortunately, email spammers and scammers like to use cloud hosting providers. And we at Hetzner naturally want to prevent this. That’s why we block ports 25 and 465 by default on all cloud servers. This is a very common practice in the cloud hosting industry because it prevents abuse. We want to build trust with our new customers before we unblock these mail ports. Once you have been with us for a month and paid your first invoice, you can create a limit request to unblock these ports for a valid use case. In your request, you can tell us details about your use case. We make decisions on a case-by-case basis.
As an alternative, you can also use port 587 to send emails via external mail delivery services. Port 587 is not blocked and can be used without sending a limit request.
-
OUPS
Ok so I think it’s Hetzner who is blocking.
I will make them an unblocking request.PW and WS Spirit alive
-
@DownPW Yep
-
Indeed. +1 for telnet.
I just trusted the netstats which told me that everything is OK which is certainly the case on the server.
since I didn’t have Telnet on hand I tested a website which told me OK
PW and WS Spirit alive
-
@DownPW said in Tutorial for secure emailing with personal domain,Cloudflare, virtualmin and postfix:
since I didn’t have Telnet on hand I tested a website which told me OK
I have to confess, I installed the
telnet-clienton your server for diagnostic purposes.Author of OGProxy, Swatch, Threaded, Card, and most of Sudonix's bugs…
-
@DownPW said in Tutorial for secure emailing with personal domain,Cloudflare, virtualmin and postfix:
I will make them an unblocking request.
Curious to know how you got on with this…
-
sorry for the late response my friends. They unblocked port 25 very quickly and I can send emails;
Just that the domains in caramail.com refused my sending of email for obscure reasons and protonmail, I receive them but in spam with an error message
I will share all its errors with you to see and I would like to deepen that the DMARC, and DKIM puts the private/public key which I do not really understand (see my request above)
PW and WS Spirit alive
-
@DownPW emails are going to junk because of missing DNS records as I mentioned previously. You won’t need to use the public and private keys unless you need extended and/or advanced functions.
-
I have the DNS pointers present
PW and WS Spirit alive
-
@DownPW not all are there. The
SPFrecord is missing. That’s enough to place email you sent into junk at the recipient end. -
Spf is on the screenshot
PW and WS Spirit alive
-
@DownPW sorry, yes, it is. Completely missed that.
-
@DownPW Can you PM me your domain name so I can run a few tests?
-
Yep no problem
PW and WS Spirit alive
-
@DownPW thanks. See PM. You can validate your domain in terms of its email suitability by using the checker below
https://emailhealthcheckup.com/
In addition, there are some great generators and checkers here
-
@DownPW any update?
