Hi Greg, I had a similar problem recently. It turned out that Norton Antivirus was proxying all smtp outbound and does not have support for STARTTLS. In the version I have, I could turn off virus checking on outbound connections and this fixed the problem. Hope this helps. Regards Jason
On Sat, 2002-03-02 at 02:32, Greg Owen wrote: > Gordon Messmer wrote: > > What firewalls/proxies/gateways lie between you and the Courier server? > > Anywhere from 0 to 2, depending - this has tested with multiple network > connections, including two hosts on a single hub with nothing but 'net > between them. That's not really an issue, though, because I've verified > with tcpdump that the "STARTTLS" command just isn't leaving the client PC > and going onto the network. > > I was jumping down the "must be a random hotfix" path earlier and > upgraded my "working" XP box, but couldn't break it. Tinfoil looking better > and better as we go. > > Telnet and tcpdump logs, along with other thoughts, are available at > http://www.swynwyr.com/xpssl/ if anyone wants to look. > > > It seems like someone recently noticed that some commands were reaching > > his courier server as XXXXXXX because a gateway was modifying the > > commands on the wire to "protect" the SMTP server. > > Sounds like Cisco PIX with "fixup smtp" in the config. PIX is a great > firewall... if you leave the fixup stuff off. > > -- > gowen -- Greg Owen -- [EMAIL PROTECTED] > 79A7 4063 96B6 9974 86CA 3BEF 521C 860F 5A93 D66D > > > > > > > _______________________________________________ > courier-users mailing list > [EMAIL PROTECTED] > Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
