How to request unblocking of Port 25 (SMTP)

By default, NeevCloud blocks inbound and outbound traffic on TCP port 25 on all Cloud Instance types to prevent spam and protect the IP reputation of our shared network.

If your application requires sending email directly via SMTP on port 25, you may submit a formal unblock request for compliance review.


Prerequisites

Ensure your infrastructure meets all of the following before submitting a request:

Requirement
Details

Reverse DNS (rDNS)

A valid rDNS record must be configured for your Elastic IP

Email Authentication

Valid SPF, DKIM, and DMARC records must be set up for your domain

Compliance

Email is only permitted with explicit opt-in consent. No Bulk email Allowed,


How to Submit a Request

Open a Support Ticket with the following information. Our compliance team will review your request within 24–48 hours.

Use Case / Purpose     : [Why do you need port 25? e.g., transactional alerts, password resets]
Email Type & Templates : [Describe email content; attach or link to a sample template]
Sender Type            : [User-generated (e.g., forum notifications) or system-initiated (e.g., alerts)?]
Sending Domain(s)      : [Primary domain(s) you will send from]
Expected Volume        : [Estimated emails per day / per month]

Modern email delivery is more reliable through the following:

  • Port 587 / 465 — Open by default on NeevCloud; the standard for authenticated SMTP submission.

  • External SMTP Providers — Using a dedicated email delivery service offers higher deliverability, built-in analytics, and removes the need for port 25 entirely.

circle-exclamation

Why Is Port 25 Blocked?

Spam monitoring organizations blacklist IP ranges that send unsolicited mail. A single bad actor on a shared network can cause NeevCloud's entire IP block to be flagged, preventing all customers from delivering mail to providers like Gmail or Outlook. This restriction protects everyone on the platform.

Last updated