• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Block port 25 outbound only

Cordal

Basic Pleskian
Server operating system version
Debian 11
Plesk version and microupdate number
18.0.52 Actualización 2
Estoy creando una regla en el firewall de plesk que bloquea el puerto 25 solo para salida, pero falta algo ya que puedo continuar enviando correo usando ese puerto, adjunto una captura de pantalla.

2023-05-15_10h04_50.jpg
 
We use the English language on this forum. Please translate your question using deepl.com before posting.
We use the English language on this forum. Please translate your question using deepl.com before posting.
Sorry I forgot to put the translation:

I am creating a rule in plesk firewall that blocks port 25 for outbound only, but something is missing since I can continue to send mail using that port, I am attaching a screenshot.

2023-05-15_13h02_52.jpg
 
The rule shown in the screenshot only block outbound traffic on port 25 for the 192.168 range. Which is an private IP address range. There usually isn't a whole lot of activity on that IP range unless you have a local network running. Which makes me wonder why you want to block this IP range specifically?
 
I have put that range because it is the one that came in the example, what I want to block is all the outgoing traffic through port 25, what should I put in that case?
 
The problem now comes to me because when closing the output port 25, it does not send through 587 or 465 either
 
I assume you want to block port 25 so email apps (Thunderbird, Outlook, Apple mail, ect) cannot use it to send e-mail because it's an insecure connection?

However port 25 is also used by a sever for talking to other (mail) servers. So if you want send email to an Gmail email address (for example) your server cant connect to to the Gmail servers to send the email. So if you block 25 no email can be send at all.
 
Back
Top