Email Smart Host not working?

I have tried to set up the outgoing email Smarthost in Email > General Settings and then tried to test it.

I configured one of the mail servers to use the XG box as a smart-host rather than the ISP smart host.  I also configured XG using the tickbox "use smarthost" and configured the smarthost as it was configured in the mail server.  I also remembered to update the device-access table so the mail server was allowed SMTP relaying.

I then sent a test email through the mail server which then tried to send it using XG.

The test email (tested 3 times), would sit in the Mail Spool as Queued and then change to Failed.  I tried retrying each email about 5 times before deleting it, each retry was no success. 

I then reverted the mail server outgoing smart host back to the ISP smart host (which it was on previously) and retried sending the email.  This worked perfectly.

My XG is in MTA mode, with 2 incoming SMTP profiles that are working well.
I upgraded from 16.05MR7 to 17-Beta1 without any issues and everything seems to be working as expected.

The smart-host only requires a connection to the host on port 25 and does not require any authentication (it is the ISP smarthost and they use other security to only allow relaying from systems connected to their services).

 

Thanks

Ian

 

 

 

 

 

 

 

  • Hi lan,

    Thank you for the logs. Detail logs would be great, already asked for the info on PM

    Thank you

  • Apologies for the delay. 

     

    Log files just sent.

  • Hello,

     

    Just an update:

    * I have tried with RC1 installed and there is no change.

    * I have installed another copy of the mail server temporarily to test the smart host/mail relay functionality.
    This was effectively configured as per the ISP (Allow Relay for specific IP on Port 25, no authentication required).  XG relayed the email correctly through this 'smarthost'

    * Device Access page is configured to allow SMTP from WAN and LAN addresses.

    * The main mail server happily delivers to the ISP SMTP relay using port 25, ISP IP pool authentication and FQDN address for the server bypassing the XG relay service. (there are no IPv6 Addresses for the ISP relay as I have HE tunnelbroker running for IPv6) 

     

    **EDIT**

    * I have just tried a different internet based SMTP smart host (I can access using a terminal connection), but I get the same failure message.  This was using port 25 and username/password authentication. They also allowed TLS on 587, and SSL on 465.  Neither of which worked either.

    * I have just tried the same Smart Host using its IP Address rather than FQDN with no luck.

     

    I hope this helps

    Ian

  • Hi Ian,

    Thank you for the sharing the details and extended help.

    We found that, in Email General Settings, for SMTP "Allow Invalid Certificate" is disabled, and the certificate coming from Smart host to Appliance is selfsigned certificate, which is getting denied as per configuration.

    You can import CA into the appliance to resolve the issue.

    The other thing, we found that, some of the mail server connecting to appliance MTA, is coming with TLS 1.0. We have disabled the TLS 1.0 by default  in SFOSv17, to make the security strong and remove week version compatibility NC-21678.

    Yes, we are doing improvement to make logging strong, so admin can come to know the mail drop reason,NC-17262 and this is planned to fix in SFOSv17 MR1.

     

    Regards,

    Deepti Bhavsar

  • Thank you for this.

     

    Is there a requirement to use SSL/TLS on this smart host?

     

    The previous smart host I tried did not allow any encryption at all and had to be a basic connection?

     

    Will there be any option to select what encryption is to be used for the smart host?

     

    Thanks

     

    Ian

  • I second Ian's concern that TLS1.0 or self signed certs shouldn't affect regular port 25 connections. However, I don't claim to be smarter than the folks at sophos so hopefully this is resolved correctly in the next MR release. Also, better logging is always welcome.