On Jan 26, 2009, at 10:14 PM, J.R. Oldroyd wrote: > On Mon, 26 Jan 2009 21:52:34 -0800, Scott Haneda > <[email protected]> wrote: >> >> Very nice, does this mean ASSP can not act as a way to bring SSL to >> email servers that do not support it? >> >> SSL client -> ASSP -> non SSL server >> >> If that is the case, I am very appreciative. >> > > That should work right now on a direct SSL socket: the one specified > in the config for listenPortSSL (normally 465). > > If you also want to support SSL after STARTTLS, as things stand > right now, your mailserver needs to generate a "250-STARTTLS" > response to "EHLO". ASSP now passes this through to the client, > which lets the client know it can send the STARTTLS command. A > non-SSL mailserver would not include the "250-STARTTLS". You > would therefore need a further (pretty trivial) change to ASSP > so that ASSP inserts this into the EHLO response. > > If this is something a lot of folk would want, it could be added > as an additional config checkbox option "insertSSLResponse" or > something like that.
I need to get my assp server online first, I am still learning. Once I get it in place, I will revisit this, sounds very cool to take all the features away from my email server, and let the proxy deal with it all. -- Scott ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
