Vincenzo Gianferrari Pini ha scritto: > Ok, if we want to connect to a gateway server. > > I was instead talking about connecting to the final SMTP receiver based > on the MX records, not to the gateway. This way RemoteDelivery will > *always* use TLS and connect on port 465, isn't it? What happens if the > peer server works only on plain port 25 without TLS? There should be a > fallback behaviour, that I think is not yet implemented.
Hi Vincenzo, I think that if we do SMTP delivery then we MUST NEVER use port 465 as the port to be used with MX servers is 25. The user was asking for a solution for "ISP gateways", so I hope the proposed attributes will make the trick! The only things we can do on standard SMTP delivery is enabling STARTTLS support: I think this can be done by using <mail.smtp.starttls.enable>true</mail.smtp.starttls.enable>. This way everytime the server will announce STARTTLS support javamail SHOULD (never tried) try to encrypt the conversation. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
