This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

XG SFOS 19 Mail Relay MTA route to host with different port

We have an XGS cluster and we want to use the Email protection module in MTA mode.

When entering a static route to a mailserver, the emails are normally sent over port 25.

When using the Spam protection the normal procedure for blocking non existing recipients is a callout to the server.

In Exchange this doesn't work over Port 25 bacause, even with activated Recipient Address Filtering, the filter only works on the Hub Transport connector with port 2525.

On Port 25 Exchange accepts any address from a configured domain, regardless of its existence.

Therefore the best practice is to route the incoming emails to Port 2525.

Unfortunately I cannot find any setting in SFOS 19 tha allows me to change the port.



This thread was automatically locked due to age.
Parents
  • Hello ,

    Thank you for reaching out to the community, You can login to the putty session with SSH protocol with your admin credentials 
    And press 4 for the device console: 

    > For SMTP - console> set service-param SMTP add port 2525

    > SMTPS - console> set service-param SMTPS add  port <Port number> 

    Thanks & Regards,
    _______________________________________________________________

    Vivek Jagad | Team Lead, Global Support & Services 


    Sophos Community | Product Documentation | Sophos Techvids | SMS
    If a post solves your question please use the 'Verify Answer' button.

  • Hello Vivek,

    if I understand the setting correctly, this only adds port 2525 to the list of ports the MTA service listens to for incoming traffic.

    It does not make the MTA forward the emails over port 2525 to the internal server.

    Alexander Poettinger

    Sophos Certified Architect - XG
    Sophos Certified Technician - XG
    Sophos Certified Engineer - UTM

    xame gmbh
    Sophos Gold Partner

Reply
  • Hello Vivek,

    if I understand the setting correctly, this only adds port 2525 to the list of ports the MTA service listens to for incoming traffic.

    It does not make the MTA forward the emails over port 2525 to the internal server.

    Alexander Poettinger

    Sophos Certified Architect - XG
    Sophos Certified Technician - XG
    Sophos Certified Engineer - UTM

    xame gmbh
    Sophos Gold Partner

Children