Re: [courier-users] Postini problem w. Courier

2004-12-16 Thread Lindsay Haisley
I think Jerry or someone pointed this out yesterday. # addcr | TLS_VERIFYPEER=NONE couriertls -host=64.18.4.10 -port=25 -protocol=smtp 220 Postini ESMTP 127 y5_2_3c1 ready. CA Business and Professions Code Section 17538.45 forbids use of this system for unsolicited electronic mail

Re: [courier-users] Postini problem w. Courier

2004-12-16 Thread Lindsay Haisley
Thus spake Julian Mehnle on Wed, Dec 15, 2004 at 09:39:19AM CST Lindsay Haisley [EMAIL PROTECTED] wrote: Thus spake Jerry Amundson on Tue, Dec 14, 2004 at 11:44:21PM CST I've turned off security for their domains... psknet.com: psknet.com/SECURITY=NONE in etc/esmtproutes, as they seem

Re: [courier-users] Postini problem w. Courier

2004-12-16 Thread Sam Varshavchik
Lindsay Haisley writes: 221 Catch you later Unexpected SSL connection shutdown. ... no problems there :-) Actually, Unexpected SSL connection shutdown does tell you that their SSL implementation is not 100% kosher. This message is issued when the peer shuts down the network connection without

RE: [courier-users] Postini problem w. Courier

2004-12-15 Thread Julian Mehnle
Lindsay Haisley [EMAIL PROTECTED] wrote: Thus spake Julian Mehnle on Wed, Dec 15, 2004 at 09:39:19AM CST Why don't you do what Jerry did, i.e. contact Postini and get them fix their servers? I've already written [EMAIL PROTECTED] about it, and the other address I have for them, [EMAIL

RE: [courier-users] Postini problem w. Courier

2004-12-15 Thread Julian Mehnle
Lindsay Haisley [EMAIL PROTECTED] wrote: Thus spake Jerry Amundson on Tue, Dec 14, 2004 at 11:44:21PM CST I've turned off security for their domains... psknet.com: psknet.com/SECURITY=NONE in etc/esmtproutes, as they seem to have some kind of STARTTLS issue. For what it's worth, I'm