Blocked ports
To secure the Servercore infrastructure from malicious network activity, access to some TCP/UDP ports is restricted.
Only outgoing and incoming traffic is blocked when it passes border routers at the edge of the Servercore Internet network.For TCP port 25, only outgoing traffic is blocked.
If the port does not fall under the above restrictions, check its availability on the OS side using the Nmap
utility.
Mailings via port 25
To prevent unauthorized mailings, TCP port 25 is blocked for outgoing connections towards public IPv4 and IPv6 addresses.Alternatively, we recommend using mail connections on TCP ports 587 and 465 or mail sending services:
- Mailchimp;
- Brevo;
- Campaign Monitor;
- ActiveCampaign;
- Get Response;
- Microsoft Office 365 mail;
- Google Workspace mail.
If you need to send mail directly, and mail services are not suitable for you, you can create a request to unblock TCP port 25.
Create request to unblock 25 TCP-port
Each request will be considered individually, unlocking is not guaranteed.If we approve the request, we will remove the 25 port lock:
- for dedicated servers — from all public dedicated subnets of the account, as well as public shared IP addresses specified in the application;
- You can see if a public IP address is shared in the control panel: from the top menu, click Products → Cloud Servers → Networks → Public IP Addresses tab .
To create an application:
- Create a ticket requesting to unblock port 25 for the account.
- If you need to unblock the public IP addresses of dedicated servers, specify these IP addresses in the ticket.You can view the public IP address of a dedicated server in the control panel: in the top menu, click Products → Dedicated Servers → Server page → Network tab .If the address is in the
/32
subnet — this is the public IP address, which should be specified in the request. - Wait for technical support to reply that port 25 is unblocked.
- Check to see if mail is being sent through port 25.