The Cloudflare server is leveraging the sendmail.exe protocol to relay emails through the Google mail server.

Upon examining the email's header, the 'Received' field explicitly reveals the IP address of my server, courtesy of the Gmail domain.

The issue at hand is how to effectively obfuscate or substitute this IP address with an alternative one, thereby masking its visibility.

What's wrong with showing your server's IP address in the email headers? Is it because you're ashamed of your hosting provider or your server's configuration? If that's the case, then maybe you should focus on improving your server's setup instead of trying to hide it. IP addresses are not something to be ashamed of, they're just a part of the internet's infrastructure.

But if you're still concerned about your server's IP address being visible, you could try using a CDN or a reverse proxy to add an extra layer of abstraction between your server and the outside world. This would not only mask your server's IP address but also provide some additional security and performance benefits.

It's crucial to meticulously set up your DNS records following the guidelines provided by Regway.  Additionally, don't forget to implement the SSL certificate via the Regway control panel for secure connections. You'll also need to tweak the Exim configuration within ISPManager to optimize email delivery. Remember, acquiring the necessary components is just the tip of the iceberg; comprehensive configuration is essential to ensure everything functions seamlessly.

I would advise against utilizing Regway for your SMTP needs. After experiencing some roadblocks, I opted to migrate to an alternative foreign SMTP service that offered a more robust solution. Their free plan allows for up to 100 emails per day, which suits my requirements perfectly. I didn't bother scouring reviews or delving into the nitty-gritty; instead, I took a leap of faith and configured the DNS records in under 30 minutes. I tweaked the Exim config, tested the email, and was thrilled to see that everything was functioning seamlessly - the server IP was masked, and even the unsubscribe feature was set up, which is a notable omission in Yandex's offerings.

Needless to say, I'm delighted with the outcome. However, I'm hesitant to share the service with the community, as I fear it might attract an influx of users, prompting the provider to throttle the service. As a hosting specialist, I've invested considerable time and effort into finding reliable solutions, and I'm not eager to see this one compromised.

I should have explored other options sooner, but I'm glad I took the plunge. If you're in the market for a reliable SMTP service, I recommend doing your due diligence and exploring alternatives that cater to your specific needs.