A reliable VPS mail server is more than an SMTP package. You need a stable public identity, correct forward and reverse DNS, Postfix for SMTP, Dovecot for mailbox access, trusted TLS, authenticated submission, SPF/DKIM/DMARC, a closed relay configuration, and continuous monitoring. Build and test those layers in that order; otherwise messages may be rejected, deferred, or classified as spam even when the server itself appears to work.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
What a production mail server on a VPS actually includes
Mail delivery is a chain of independently enforced controls:
As an Amazon Associate I earn from qualifying purchases.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- VPS and network identity: a stable public IPv4 address, a hostname, usable mail ports, and provider-controlled reverse DNS (PTR).
- Postfix: the Mail Transfer Agent (MTA) that accepts mail from other servers, queues it, and delivers outgoing mail.
- Dovecot: the IMAP service (and, if you choose, POP3) that lets users read mail and integrates local mailbox delivery.
- DNS authentication: A/AAAA, PTR, SPF, DKIM, and DMARC records that let receiving systems verify who sent a message.
- TLS and authentication: encryption for server connections and SMTP AUTH for users submitting mail.
- Operations: firewall rules, updates, backups, queue review, log retention, and reputation monitoring.
Removing one layer creates a specific failure. A valid mailbox cannot compensate for a missing PTR record; SPF cannot fix an expired certificate; and a correctly signed message can still be rejected if Postfix is an open relay.
Prerequisites to verify before installing anything
Infrastructure requirements
- A VPS provider that explicitly permits mail traffic and does not block outbound TCP port 25.
- A stable public IPv4 address. Add IPv6 only when it has equivalent routing, firewalling, forward DNS, and reverse DNS.
- Control of the DNS zone for your sending domain.
- Provider access to set the IP’s PTR (reverse-DNS) record.
- A hostname dedicated to mail, such as
mail.example.com. - A certificate authority that can issue a trusted certificate for that hostname.
Ports and their roles
| Port | Use | Exposure and security rule |
|---|---|---|
| 25/TCP | Server-to-server SMTP | Allow only the public SMTP service; never permit unauthenticated relaying. |
| 587/TCP | Authenticated message submission | Require TLS and SMTP AUTH; this is the normal port for mail clients. |
| 465/TCP | Implicit-TLS submission, when needed by clients | Enable only if your client mix requires it and apply authentication and relay restrictions. |
| 993/TCP | IMAP over TLS | Expose the encrypted service; avoid unencrypted IMAP on the public Internet. |
Before proceeding, ask the provider whether port 25 is filtered and whether PTR changes require a support request or a control-panel setting. A technically correct configuration cannot deliver mail if the network blocks the SMTP path.
#1 Best Overall
- [Ultra-Lightweight Ear Buds Designed for Small Ears] Each earbud weighs only 3.7g and features a compact, ergonomic in-ear design made especially for small ears. Secure, low-profile, and comfortable for workouts, all-day wear or overnight sleeping.The ultra-slim profile sits flush in your ear with no hard edges poking or rubbing, so you can even sleep on your side without discomfort.
- [Immersive Stereo Sound with TOZO OrigX Technology] TOZO OrigX tuning delivers clear vocals, balanced mids, and natural stereo sound for music, podcasts, and videos.
- [Long Battery Life for Daily Use] Get up to 7 hours of playtime on a single charge, with up to 32 hours total using the charging case—ideal for workdays, commuting, and extended listening sessions.
- [Bluetooth 5.3 & Stable Connection] Bluetooth 5.3 provides fast pairing, stable wireless performance, and reduced dropouts as you move around home or office.
- [Deep Bass with Clear Vocals] High-performance drivers produce punchy bass while keeping vocals clean and detailed for everyday listening.
Choose the operating model deliberately
| Decision | Control-oriented choice | Operational trade-off |
|---|---|---|
| Mail transport | Direct delivery from your VPS | You control queueing and policy, but your IP reputation and recipient-specific requirements are your responsibility. |
| Mail transport | Authenticated relay | A relay can help with reputation and queue management, while adding a dependency and recurring service cost. |
| Software packaging | Distribution-native Postfix and Dovecot packages | They integrate with the operating system’s updates and service manager. |
| Software packaging | Containerized or suite-based deployment | Isolation and automation can improve repeatability, but troubleshooting crosses container and host boundaries. |
| Topology | Single VPS | Lowest complexity and cost; one failure affects SMTP, IMAP, and administration together. |
| Topology | Separated roles | Better fault isolation and scaling, with more DNS, monitoring, and maintenance work. |
For a small domain, one well-hardened VPS is usually the simplest starting point. Move outbound delivery to a relay or separate roles when reputation management, volume, or availability requirements exceed what you can operate reliably.
Step 1: establish a hostname and matching DNS
Set the system hostname
Use one canonical mail name everywhere. On a Debian or Ubuntu-style system, an example is:
Recommended Free Tools
sudo hostnamectl set-hostname mail.example.com
hostname --fqdn
The second command should return the same fully qualified name. Configure the local hosts file only as a supplement; public DNS must still resolve correctly.
Create forward DNS
Create an A record for mail.example.com pointing to the VPS’s public IPv4 address. Publish an AAAA record only after IPv6 connectivity is fully working. Your domain’s MX record should point to the mail hostname, for example example.com MX 10 mail.example.com.
Set reverse DNS (PTR)
At the VPS provider, set the public IP’s PTR to mail.example.com. Then verify both directions:
dig +short A mail.example.com
dig +short -x 198.51.100.10
Replace the documentation address above with your real IP. The A lookup should return the sending address, and the reverse lookup should return the same hostname. Google states: “The public IP address of a sending SMTP server must have a corresponding PTR record that resolves to a hostname.” Gmail also checks forward and reverse DNS consistency, so do this before sending production mail.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #2
- 【IP68 Waterproof Multifunctinal Smart Watch】Torjalph fitness activity tracker smart watch is IP68 waterproof technology ,you can wear it when swimming,handwashing,it's rain-proof which means that you perform multiple exercise modes outside without worrying about sweat or rain corroding your fitness smart watch,and this watch equipped with a 230 mAh large capacity battery magnetic charging ,and this sports activity tracker watch can be used 5-7 days If fully charged.
- 【Larger 1.83'' Full Screen Watch & Multi-dial Selection】1.83 inch full HD color touch screen smart watch for men / women provides excellent 240*284 resolution image quality ,This Bluetooth smart watch offers a better touch experience and remarkable immersion and ,more than 200 watch faces for you to choose from App"Da Fit ", you can change the dial style according to your mood to wear keeping the world on your wrist
- 【Accurate Activity Tracker Smart Watch 】sports watch activity tracker uses sweat and dust resistant breathable silicone strap, our Fitness Tracker Smart Watch for Android iOS Phones supports 12 sports modes,walking,running,bicycle,swimming,badminton,basketball,football,rope skipping. This bluetooth calls smart watch for men women is lightweight and stylish, bringing more convenient and relaxing sports experience while also providing more protection.
- 【Your 24 Hour Personal Daily Health Monitor】Fitness watch for women men full touch screen IP67 waterproof bluetooth smartwatch for Android iOS Phones with heart rate blood pressure monitor multifunction Andriod smart watch with steps counter sleep monitor sports fitness watch, monitoring blood oxygen saturation allows you to understand your physical condition in real time to track fitness progress ,to know your health status in time.
- 【More Functions Bluetooth Call Smart Watch】This fitness activity smart watch full screen for iPhone and Android phones includes a bunch of new features including:The bluetooth smart watch can hang up the phone, receive and display WhatsAPP /Text /Facebook /Twitter /Messenger reminder.Support sedentary reminder, alarm clock, stopwatch, timer,weather information,music control, remote camera control compatible with Android 5.0 and above or iOS 9.0 and above smartphones.
Step 2: install Postfix and Dovecot
Package names and configuration paths vary by distribution. The following illustrates a Debian/Ubuntu installation; use your distribution’s supported packages and service manager on other systems.
sudo apt update
sudo apt install postfix dovecot-core dovecot-imapd
When the Postfix installer asks for a mail configuration type, select an Internet-facing configuration and use your domain as the system mail name. Confirm that the resulting myhostname is the VPS hostname and that mydestination contains only domains for which this server is authoritative.
Connect local delivery to Dovecot
Choose one mailbox format and configure both services consistently. Maildir is common for virtual or system users. Dovecot must read the same location where Postfix delivers messages. For LMTP delivery, expose Dovecot’s LMTP socket to Postfix and set Postfix’s virtual_transport (or the corresponding local-delivery setting) to that socket. For a simpler system-user setup, ensure Postfix’s local delivery path matches Dovecot’s mail_location.
Red Hat’s mail-server guidance emphasizes using a secure Postfix-to-Dovecot delivery integration and reducing the network exposure of Dovecot. Do not publish administrative or plaintext mailbox protocols unnecessarily; expose only the encrypted access service your users need.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteStep 3: install trusted TLS and automate renewal
Obtain a certificate whose name includes mail.example.com, and keep the private key readable only by the service processes that need it. A typical ACME client invocation is:
sudo certbot certonly --standalone -d mail.example.com
Standalone issuance temporarily uses port 80, so stop any conflicting web service or use a web-root/DNS challenge instead. Configure Postfix with the certificate chain and private key, and configure Dovecot with the same certificate and key. Ubuntu’s Postfix documentation covers settings such as smtp_tls_security_level, smtpd_tls_security_level, TLS logging, and certificate-chain files.
Rank #3
- [Low Noise High Fidelity] New bee guitar cord with 22AWG oxygen-free-copper center conductors provides enhanced signal transfer, the PVC insulation material and the high-density stranded copper double shield provide noise rejection for quiet operation
- [Ideal for Choice] New bee 1/4 straight and right angle metal connectors, ensures a secure connection in any instrument, pedal, or amp jack. L shape great fro on stage guitar stands
- [Wide Compatible] Suitable for mixer, power amplifier, microphone, effector, decoder, equalizer, electoronic organ, electric guitar, electric bass and other electronic equipments. Widely used in the installation of smart home, karaoke speaker, professional stage audio, etc
- [Easy Disassemble] Making incidental repairs quick and easy! Very nice, flexible cable
- [Dont Hesite to Order] 24 hours customer services and professional technology team are standing by
Postfix’s TLS documentation notes that modern TLS operation requires a certificate and private key; its blunt warning is: “To run without certificates you’d have to disable the TLS 1.3 protocol…” Treat an untrusted, expired, or hostname-mismatched certificate as a production outage, not a cosmetic warning.
Reload safely after renewal
Use the certificate client’s renewal hook to reload both services after a successful renewal:
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchessystemctl reload postfix
a systemctl reload dovecot
Remove the accidental leading a if you paste the example; the actual commands are:
sudo systemctl reload postfix
sudo systemctl reload dovecot
Test renewal in a staging or dry-run mode offered by your ACME client, then verify the live certificate’s expiry and SANs. Never leave renewal dependent on a manual calendar reminder.
Step 4: separate public SMTP from authenticated submission
Keep port 25 for server-to-server traffic
Port 25 must accept mail addressed to domains hosted on this server and reject unauthorised destinations. In Postfix, the critical safety control is a relay restriction such as:
smtpd_recipient_restrictions =
permit_mynetworks,
permit_sasl_authenticated,
reject_unauth_destination
The exact setting can differ by Postfix version and existing policy, but the outcome must be the same: unauthenticated Internet clients may not use your server to deliver to arbitrary domains.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →Rank #4
- Digital Family Calendar: BSIMB digital calendar wall touch screen puts an end to your chaotic life. Designed for busy families, the digital calendar keeps you organised and in step with your family. Assign different colours and tasks to each family member to make family scheduling easier and more intuitive.
- Easy Setup and Auto-Sync: Plug in, connect to WLAN and auto-syn your electric calendar in minutes. Digital wall calendar compatible with Google calendar, iCloud calendar, Outlook calendar, Cozi calendar and Yahoo calendar. Add events directly on the device or through the ecalendar app. Electronic calendar stays current whether you're at work or traveling—no manual updates needed.
- All-In-One Home Assistant: Smart calendar builds habits and encourage independence with personalised chores. Display daily meal plan to reduce the daily ‘What's for dinner?’ stress. To-do lists keep track of everything you want. Turning chores into valuable achievements with stars and rewards, making life easier and more enjoyable.
- Manage Anytime Anywhere: BSIMB electronic calendar for family stay connected with the powerful ecalendar app. Access and manage your digital wall calendar anytime, anywhere with free features like stars & rewards, photo screensaver, chore charts, meals plans, to-do lists etc. Electronic planner paid features like Magic Import tailor advanced tools for users with special needs.
- Stay in Touch with Loved Ones: Share photos or videos from your phone to electronic wall calendar with app, instantly update your life moment, and keep in touch with your family, especially those who are far away; you can also surprise your smart calendar digital wall by sending him a wish card; it's also great for keeping tech-illiterate elders in touch with the youngsters.
Require TLS and AUTH on port 587
Define a dedicated submission service in Postfix’s service configuration. Require encryption before authentication, enable SMTP AUTH backed by Dovecot, and apply the same destination restriction. Use a separate service stanza so a policy intended for users does not accidentally weaken port 25.
Port 465 uses implicit TLS from the first byte and can be enabled for clients that require it. It is not a replacement for port 25 server-to-server SMTP. Whichever submission ports you expose, test that authentication fails before TLS and that an authenticated account can send only within your intended policy.
Protect Dovecot authentication
Configure Dovecot to use a supported password database, disable plaintext authentication unless it is protected by TLS, and create the Postfix-Dovecot authentication socket with restrictive ownership and permissions. Use separate service accounts where possible and avoid granting mailbox services shell access.
Step 5: publish SPF, DKIM, and DMARC
SPF
Publish one SPF TXT record at the envelope-from domain that lists every legitimate sending system. A single-IP example is:
example.com. TXT "v=spf1 ip4:198.51.100.10 -all"
Use your real address and include any approved relay or service. Keep one SPF record per domain; multiple SPF TXT records cause a permanent error.
DKIM
Generate a DKIM key pair, keep the private key on the server, and publish the public key under a selector such as selector1._domainkey.example.com. Sign every legitimate outbound message. Google requires at least a 1,024-bit DKIM key for personal Gmail delivery and recommends 2,048 bits when supported.
Best Value
DMARC and alignment
Start with monitoring so you can discover legitimate senders:
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →_dmarc.example.com. TXT "v=DMARC1; p=none; rua=mailto:[email protected]"
After reviewing aggregate reports and correcting failures, move deliberately to p=quarantine or p=reject. DMARC checks that the visible From: domain aligns with the domain authenticated by SPF or DKIM. Google recommends DMARC reporting, and direct mail should align the From domain with at least one authenticated domain.
Step 6: harden the VPS
- Allow inbound TCP 25, 587, optional 465, and 993 only as required; restrict SSH to administration networks where practical.
- Enable a host firewall and rate-limit repeated authentication failures.
- Apply unattended security updates, but schedule controlled reboots and verify mail services afterward.
- Use least-privilege service accounts and protect configuration files, DKIM keys, TLS keys, and mailbox data.
- Back up mailboxes, configuration, DNS exports, DKIM keys, and the database or password source used for authentication.
- Perform a restore test. A backup that has never been restored is not a recovery plan.
- Retain logs long enough to investigate bounces, abuse, and account compromise while respecting your privacy and retention requirements.
Step 7: test before accepting real users
- DNS: verify A/AAAA, MX, PTR, SPF, DKIM, and DMARC from more than one resolver.
- TLS: inspect the certificate name, chain, expiry, and negotiated protocol on ports 587 and 993.
- SMTP AUTH: confirm valid credentials succeed only after TLS and invalid credentials are rejected.
- Relay control: attempt delivery to an external domain without authentication; it must be refused.
- Local delivery: send between two local mailboxes and confirm Dovecot sees the message.
- Remote delivery: send to test recipients at multiple providers and inspect Authentication-Results headers.
- Replies and bounces: verify that return paths reach the correct mailbox and that unknown recipients generate a controlled bounce.
- Queue behavior: stop a destination temporarily, confirm the message becomes deferred, then restore delivery and confirm the queue drains.
- Recovery: restore a mailbox and service configuration on a separate instance or test location.
Deliverability rules that matter most at Gmail
Google’s current sender guidance requires all senders to use SPF or DKIM, valid forward and reverse DNS, TLS, correctly formatted RFC 5322 messages, and a spam rate below 0.3%. Senders that transmit more than 5,000 messages in 24 hours to Gmail must use SPF, DKIM, and DMARC. The 5,000-message threshold is measured per 24-hour period, and the 0.3% spam figure is a sender guideline, not an inbox-placement guarantee.
Compliance improves the chance of acceptance but cannot guarantee inbox placement. Reputation, recipient complaints, message content, sending patterns, and receiver-specific policies still influence filtering. Never buy or import lists, and remove persistently bouncing or complaining recipients.
Use Gmail’s feedback signals
Register the sending domain in Gmail Postmaster Tools when eligible. Review authentication results, delivery errors, spam-rate trends, TLS usage, and domain/IP reputation. Treat a rising complaint rate as an incident: pause questionable campaigns, investigate compromised accounts, and correct list-acquisition or unsubscribe problems before resuming.
Monitoring and routine operations
Daily or automated checks
- Postfix and Dovecot service health and recent error logs.
- Deferred and active queue size, oldest queued message, and repeated destination failures.
- SMTP AUTH failures, unusual submission volume, and password-spraying patterns.
- Certificate expiry and successful renewal events.
- Disk space, inode usage, memory pressure, and backup freshness.
Useful Linux checks include journalctl -u postfix, journalctl -u dovecot, and postqueue -p. Alert on sustained queue growth rather than a single transient defer. A sudden outbound spike can indicate a stolen password or web application abuse; disable the account, rotate credentials, and inspect logs before clearing the queue.
Monthly or quarterly checks
- Review DMARC aggregate reports and update SPF for every authorised sender.
- Confirm PTR, A, MX, and certificate values still match after provider or DNS changes.
- Verify firewall rules, package updates, backup restores, and account inventory.
- Check reputation and blocklist status using reputable monitoring services, then investigate the cause rather than treating removal as the solution.
- Send controlled test messages to major recipient networks and archive their authentication headers.
Common failures and precise fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Remote servers reject immediately | Missing or mismatched PTR/A records, blocked port 25, or invalid hostname | Correct reverse DNS at the VPS provider, verify forward resolution, and confirm port-25 policy with the provider. |
| TLS warning in a mail client | Certificate expired, untrusted, or issued for a different name | Renew the certificate, install the full chain, use the exact mail hostname, and reload both services. |
| Users can read mail but cannot send | Submission service disabled, AUTH unavailable, or TLS required before AUTH | Check the port-587 service, Dovecot auth socket, client port/security mode, and service logs. |
| Server becomes a spam source | Open relay, compromised credentials, or an abused local application | Enforce reject_unauth_destination, disable compromised accounts, rotate passwords, inspect the queue, and restrict local senders. |
| Messages remain deferred | Destination throttling, DNS failure, reputation issue, or network outage | Read the exact Postfix defer reason, fix the underlying condition, and allow retries; do not repeatedly flush a queue without diagnosis. |
| DMARC reports show failures | SPF/DKIM domain misalignment or an unlisted sender | Align the visible From domain, publish the sender’s SPF authorization, sign with DKIM, and identify forgotten applications from reports. |
| Mail reaches spam despite passing authentication | Complaints, poor reputation, content, or receiver-specific filtering | Reduce complaint sources, send only to opted-in recipients, monitor reputation, and improve content and list hygiene; authentication alone is not an inbox guarantee. |
When a hosted relay is the better engineering choice
Self-hosting is appropriate when you need control over data, policy, and mailbox infrastructure and can operate DNS, security, queues, and reputation monitoring. A hosted relay is often safer for transactional or bulk sending when you cannot continuously manage IP reputation, complaint handling, feedback loops, and delivery retries. You can still keep Dovecot and inbound mail on your VPS while routing outbound mail through an authenticated relay; publish the relay’s SPF authorization and ensure DKIM and DMARC alignment remain intact.
Do not choose direct delivery solely because the software is free. The ongoing work—patching, abuse response, backups, certificate renewal, queue analysis, and reputation recovery—is part of the system’s real cost.
Quick Recap
Final production checklist
- Static public IP and provider permission for mail traffic.
- Hostname, A/AAAA, MX, and matching PTR verified in both directions.
- Postfix installed with relay restrictions and separate submission policy.
- Dovecot mailbox access protected by TLS and integrated with local delivery.
- Trusted, automatically renewed certificate installed on Postfix and Dovecot.
- SPF and DKIM published for every legitimate sender.
- DMARC reporting enabled, alignment verified, and enforcement tightened only after review.
- Firewall, updates, least privilege, backups, restore tests, and log retention in place.
- DNS, TLS, AUTH, local/remote delivery, bounces, queue retries, and recovery tested.
- Postfix/Dovecot logs, deferred mail, authentication failures, DMARC reports, Gmail Postmaster Tools, complaints, and reputation monitored continuously.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.




