need 587 TLS incoming and outgoing mail setup on server - 25 and 446 port are close our server by DC

@atikullx

I can configure Exim to use Google Workspace as SMTP Relay to send your emails. I'm an expert in Email Server, DNS, SPAM filters, Linux Administration.

@dyjibran

With my extensive technical expertise and a profound understanding of IT Infrastructure, Linux, and Network Engineering, I am confident in my ability to tackle the multi-faceted issue you are facing with your server's incoming and outgoing mail setup. My **14+ years of hands-on experience** implementing and managing secure and scalable IT environments, including **email systems**, comes into play in this case. I have an in-depth knowledge of the Google Workspace ecosystem, thoroughly versed in authentication protocols like **STARTTLS, AUTH PLAIN/LOGIN**, and remain gravely familiar with remedying port issues in case of a DC blockage. Building on these skills and certifications (MCSA, CCNA), I can successfully set up a **587 TLS mail** for your server whilst meticulously securing the environment with any necessary **certificates, CA bundles,** or **OAuth-related settings**. Moreover, it is important to mention that I bring with me a passion for identifying the root cause of problems which allows me to deliver not just quick fixes, but end-to-end solutions that are **secure**, **reliable**, and easy to *maintain*. A synergy like that is crucial when dealing with complex issues such as SMTP relay as we can never be too cautious about data security. Rest assured, you're in capable hands; give me a go-ahead and let's restore your server's fully-functional email notification system.

@vps8

Hi, I can help configure your Linux server to send mail through Google Workspace using SMTP port 587 with STARTTLS and authentication. I’ll check and adjust the Exim configuration, certificates/CA settings, and Google Workspace SMTP authentication. I’ll also test incoming/outgoing mail, admin notifications, and cron jobs to make sure automated emails are delivered successfully to Gmail and an external mailbox. You can provide SSH access and remote access through Google Meet/TeamViewer. I’ll troubleshoot the current issue and make sure everything is working properly. Kindly chat once. Thanks!

@humairsaeed

Hi i am an cloud system engr with expertise over 15 years i can do this and setup STMP relay as your requiements

@souravsasmal14

I can configure Exim to relay all server/cron notifications through Google Workspace SMTP over port 587 with STARTTLS and the required authentication/certificates, then test live delivery and verify the headers show Google’s mail servers. We’ll also troubleshoot the current notification failures caused by your DC blocking ports 25/446 and ensure outbound/incoming mail flow is working correctly.

@erincguray

Greetings I am Erinc I am a Web Developer since 2020 knowledgeable in PHP and Linux. I can confirm I will fix your smtp error strictly under your budget. I am available to start right now and regularly on desk everyday. Looking forward to hear from you. Thanks for your consideration.

@Abror86

Hi-Abror Here From Uzbekistan. "Restore Reliable Google Workspace SMTP Delivery" - I can configure Exim for authenticated STARTTLS delivery through Google Workspace on port 587 securely. I can diagnose the SMTP handshake, configure Exim authentication, CA certificates, TLS settings, and Google Workspace requirements while preserving existing mail functionality. I will test server notifications, Gmail and external delivery, verify headers, and confirm cron-triggered emails work reliably without port 25. Are you using a Google Workspace account with SMTP AUTH enabled, or should we configure OAuth2 instead? Looking forward to working with you.

@nakabirik

Hello Mathura, The handshake failure usually means Exim isn't presenting the right auth mechanism or the certificate chain isn't complete. I'll reconfigure Exim to use STARTTLS on port 587 with AUTH LOGIN against Google Workspace, verify the CA bundle is valid, and test the full flow. Once it works, I'll set up the relay so PHP mail() and cron jobs route through the same authenticated SMTP — no more blocked notification emails. I can also add a simple health check that alerts you if the relay drops. Do you have the Google Workspace app password ready, or should I set that up during the session? Looking forward to working with you

@bojans9

Hello, I can troubleshoot and configure your Linux Exim mail setup to use Google Workspace SMTP over port 587 with STARTTLS and proper authentication. I have 10+ years of software development experience and solid experience working with Linux based systems, APIs, automation and server integrations. I would first inspect the current Exim routing and TLS handshake, then configure the Google relay, certificates and authentication, followed by delivery and header verification. I can also check your cron jobs so automated notifications work normally without port 25 dependency. Is your Google Workspace account using OAuth or an SMTP app password? What Exim version is running on the server? Is incoming mail handled by this same server or only outbound relay is required? I can work within your budget and focus on getting the live Gmail and external mailbox tests working reliably.

@nabilpevekar

I can help with the Exim and Google Workspace SMTP setup. I understand that port 25 is blocked by your DC, so the server needs to relay mail through Google over 587 with STARTTLS. I can check the current Exim configuration, TLS/CA setup and Google Workspace authentication, then test outbound mail to both Gmail and an external mailbox. I’ll also check the cron jobs so automated notifications work normally instead of requiring manual runs. I have 4+ years of hands-on IT experience with Linux, networking, email/SMTP troubleshooting and server support. I can start right away.

@xcubeits

With over a decade of development experience, including an emphasis on PHP and Laravel architecture, I have the skills and expertise to tackle your Linux server's mail setup challenges. I understand that it's not just a matter of making things work. The **importance of implementing secure, maintainable, and scalable solutions that are ready for real-world use** cannot be overstated. Additionally, my comprehensive knowledge and experience with Linux and server management includes adjusting the Exim configuration for optimal performance as well as adding necessary certificates, CA bundles, or OAuth-related settings. Getting your mail to pass through Google's servers via port 587 is squarely within my capabilities. Lastly, clear and consistent communication is something I take seriously. I am known for **keeping clients well-informed of progress and finding solutions** that align with business requirements donc you won't be met with any nasty surprises or delays along the way. By choosing me, you're not just choosing someone who will get the job done, but someone who will get it done right.

@solokbaba

Port 587 is the correct path for authenticated outbound SMTP when port 25 is blocked; inbound mail should be handled separately through Google Workspace MX/routing. I can configure Exim/Postfix to relay through Google Workspace using STARTTLS and the appropriate SMTP authentication method, verify CA/TLS certificates, and correct the routing/auth configuration causing the current handshake failure. I’ll also ensure server notifications and cron-generated emails use the Google relay correctly, then test delivery to Gmail and an external mailbox and verify the message headers confirm Google handled the relay. I can troubleshoot and configure this directly over SSH and am ready to start.

@dhananjays055

Hi there, I can set up secure TLS email on ports 587 for incoming and outgoing mail, bypassing the closed 25 and 446 ports as per your server’s DC restrictions. I’ve handled custom mail server configurations and can ensure smooth, encrypted email flow tailored to your infrastructure.

@mahdisaoudia

I can setup postfix smtp server for not paid google mail quotas Contact me chat.