Sending email directly from a VPS requires access to SMTP port 25.
To protect network reputation and ensure responsible email delivery, SMTP port 25 is blocked by default. Unblocking it requires all of the following conditions to be met:
The account must meet the eligibility requirements for port 25 access
The SMTP port 25 unblock request form must be completed in full
The request must be manually reviewed and approved by the LumaDock team
This article explains who is eligible, what information is required, and how email use cases are evaluated before approval.
Eligibility requirements
SMTP port 25 can only be requested 31 days after the first paid order on the account.
Requests made before the 31-day period has fully elapsed will not be approved.
The waiting period is tied to the account’s first purchase date, not to an individual VPS, upgrades, plan changes, cancellations, or refunds.
This rule exists to prevent abuse and refund-based spam activity and applies equally to all accounts, including newly created or previously refunded ones.
Required information
When submitting a port 25 unblock request, provide the following details exactly as listed below.
Hostname
You can find your server hostname in your client area under Dashboard.
Primary public IPv4 address
Your primary IPv4 address is available in the New product login information email or in your client area under IP addresses.
Providing accurate information helps us review and process your request without delays.
Email use case definition
You must specify how email will be used from your server. Choose the category that best matches your intended purpose.
Transactional email
Customer-facing messages triggered by user actions such as order confirmations, password resets, account activation emails, or billing notifications.
System alerts
Automated messages generated by applications or monitoring systems to report system status, errors, warnings, or operational events.
Internal corporate mail
Business communication intended for employees, partners, or internal stakeholders such as announcements, meeting invites, or internal updates.
Other
Use this option if your email purpose does not fit the categories above. You must clearly describe the use case in your own words.
Accurate classification helps ensure proper handling, compliance, and delivery optimization for different email types.
Email metrics
Email metrics describe the expected volume of email sent from your server. These values are required for all requests.
Provide the following estimates:
Estimated emails per hour
The average number of messages your server is expected to send within one hour.Estimated emails per day
The average total number of messages expected within a 24-hour period.
These metrics help establish normal sending behavior and allow us to detect abnormal traffic patterns. Accurate estimates improve deliverability and protect overall network integrity.
Reverse DNS configuration
Before sending email, your server should have a properly configured PTR record.
You can follow the Reverse DNS setup guide in LumaDock here:
https://lumadock.com/knowledgebase/articles/13532006-reverse-dns-setup-in-lumadock
Proper reverse DNS configuration is strongly recommended and may be required for reliable email delivery.