Skip to main contentSkip to navigation
[email protected]
Client AreaSupport
Hosting Mammoth
HostingMammothYour Data, Our Responsibility
Home
Solutions
Hosting Services
Store
Pricing
About
Blog
API
Contact

Stay Ahead of the Curve

Get the latest insights on cybersecurity, AI innovations, and enterprise data solutions delivered to your inbox.

Hosting Mammoth
HostingMammothEnterprise Solutions

Enterprise-grade data solutions. Hosting, recovery, cybersecurity, and AI-powered services for businesses worldwide.

[email protected]
Sun - Fri, 9:00am - 5:00pm

Services

  • Cloud Hosting
  • Data Recovery
  • Cybersecurity
  • Legal Support
  • MSP Services
  • Web Development
  • AI Services
  • Free Server Migration

Hosting

  • VPS Hosting (NVMe SSD)
  • VDS Hosting (NVMe)
  • Storage VPS (High SSD)
  • GPU Servers
  • Managed Services
  • Cloud Firewall
  • Load Balancer
  • One-Click Apps
  • n8n Hosting
  • Object Storage
  • FAQ

Company

  • Store
  • Pricing
  • About Us
  • Locations
  • Blog
  • Testimonials
  • Contact
  • Affiliate Program
  • White-Label
  • Terms of Service
  • Privacy Policy
  • Browser Cookies
  • SLA

Support

  • Client Area
  • Submit Ticket
  • Knowledge Base
  • Server Status
  • API Documentation

© 2026 Hosting Mammoth. All rights reserved.

Knowledge Base
Getting StartedAccount ManagementVPS HostingGPU ServersStorage VPSCloud FirewallLoad BalancerServer ManagementBilling & PaymentsSupport & TicketsAffiliate ProgramReseller ProgramMarketplace & Appsn8n HostingManaged ServicesServer MigrationAPI & DevelopersSecurityTroubleshootingGlossaryInstall Guides
  1. Home
  2. /
  3. Support
  4. /
  5. Troubleshooting
  6. /
  7. Email Not Sending
GUIDETroubleshooting

Email Not Sending from Server

4 min read

If email sent from your server is not being delivered, the problem usually lies in SMTP configuration, DNS records, or IP reputation. This guide walks through the most common causes and solutions.

Common Causes

  • Missing or incorrect DNS records — SPF, DKIM, and DMARC records not configured.
  • SMTP not configured — The mail service is not installed or configured.
  • Port 25 blocked — Some networks block outgoing SMTP traffic by default.
  • IP reputation — Your server IP may be on a blocklist.
  • Reverse DNS mismatch — PTR record does not match the sending hostname.
  • Firewall blocking — Outgoing mail ports are blocked.
  • Step 1 — Check if SMTP Is Running

    bash
    # Check if a mail service is installed
    sudo systemctl status postfix    # or sendmail, exim

    If no mail service is installed:

    bash
    sudo apt install postfix -y    # Ubuntu/Debian
    sudo dnf install postfix -y    # CentOS/AlmaLinux
    sudo systemctl enable postfix
    sudo systemctl start postfix

    Step 2 — Send a Test Email

    bash
    echo "Test email from server" | mail -s "Test" [email protected]

    Check the mail log:

    bash
    sudo tail -50 /var/log/mail.log      # Ubuntu/Debian
    sudo tail -50 /var/log/maillog       # CentOS/AlmaLinux

    Look for error messages that explain why delivery failed.

    Step 3 — Check DNS Records

    SPF Record

    SPF tells receiving servers which IPs are authorized to send email for your domain:

    bash
    dig example.com TXT +short

    You should see something like:

    text
    "v=spf1 ip4:203.0.113.10 -all"

    If missing, add a TXT record to your DNS:

    • Type: TXT
    • Name: @
    • Value: v=spf1 ip4:203.0.113.10 -all

    Reverse DNS (PTR Record)

    bash
    dig -x 203.0.113.10 +short

    The result should match your mail hostname (e.g., mail.example.com). Set up reverse DNS through your Data Mammoth dashboard.

    DMARC Record

    Add a DMARC record for email authentication reporting:

    • Type: TXT
    • Name: _dmarc
    • Value: v=DMARC1; p=quarantine; rua=mailto:[email protected]

    Step 4 — Check Port Connectivity

    Test if port 25 (SMTP) is open outbound:

    bash
    telnet smtp.gmail.com 25

    If it times out, outgoing SMTP may be blocked. Try ports 587 or 465 instead by configuring your application to use an external SMTP relay.

    Using an SMTP Relay

    If direct sending is blocked or unreliable, use an external SMTP service:

    Configure your application to send through an SMTP relay:

    • Host: Your SMTP provider's server
    • Port: 587 (TLS) or 465 (SSL)
    • Authentication: Your SMTP credentials

    Step 5 — Check IP Reputation

    Your server's IP may be on a blocklist if it was previously used for spam:

  • Check blocklists using online tools (search for "email blocklist check").
  • If listed, follow the blocklist's delisting process.
  • Consider using a dedicated IP for email. See Adding Additional IP Addresses.
  • Step 6 — Check Firewall Rules

    Ensure outgoing SMTP ports are not blocked:

    bash
    # UFW
    sudo ufw allow out 25/tcp
    sudo ufw allow out 587/tcp
    sudo ufw allow out 465/tcp

    firewalld

    sudo firewall-cmd --permanent --add-port=25/tcp sudo firewall-cmd --permanent --add-port=587/tcp sudo firewall-cmd --reload

    Step 7 — Check Application Configuration

    If using PHP:

    bash
    # Test PHP mail function
    php -r "mail('[email protected]', 'Test', 'PHP mail test');"

    If using WordPress or another CMS, install an SMTP plugin that sends through an authenticated SMTP server instead of the PHP mail() function.

    Prevention

  • Always set up SPF, DKIM, and DMARC before sending email.
  • Use authenticated SMTP instead of the PHP mail() function.
  • Monitor deliverability by checking bounce rates and delivery logs.
  • Set up reverse DNS to match your sending hostname.
  • Use a dedicated sending IP for email-heavy applications.
  • What to Do Next

    • Server Networking — IPs, DNS, Reverse DNS — Configure DNS and PTR records.
    • DNS Not Resolving — Fix DNS configuration issues.
    • Adding Additional IP Addresses — Get a dedicated email IP.
    • How to Submit a Support Ticket — Get help with email issues.

    Was this article helpful?

    ← Back to TroubleshootingBrowse all categories →

    Still have questions?

    Contact Support →Submit a Ticket