I experienced this back to the 1.5 stable releases. I never was able to get a pure transparent proxy of the remote MTA. I want whatever the remote offers, to be transparently sent through ASSP.
If my remote send out certain capabilities, I would think I can turn down ASSP to just pass those along. I've always felt TLS is handled on the destination device, and ASSP just proxies it back through. Let me know how you get along with the 1.6 suff, I'm about to bump myself up on a test machine. -- Scott * If you contact me off list replace talklists@ with scott@ * On Feb 12, 2010, at 7:19 AM, Greybear <[email protected]> wrote: > Hi all, > > I have a setup where I need to use TLS on ASSP. I have a server that > connects to the relayport, but does not handle TLS well (in 1 of 5 > handshakes fail, and in that case that server's SMTP daemon hangs up > - no > influence on that). > I added this buggy server's IP to the NoTLSIP setting, but even > after that > it keeps offering "250-STARTTLS" after EHLO. > > Can I do ANYTHING to make NoTLSIP work? I already use the latest > ASSP (just > upgraded to ASSP Version: 1.6.5.4(0.0.00)) ------------------------------------------------------------------------------ SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
