I've got to hold my hands up and admit I'm not an SSL expert, but hopefully somebody on here is.

In other words, I'm not certain if the /var/log/secure file is the correct one. Try a 'man -k ssl' or 'man -k SSL' and see what that throws up - might point you in the right direction.<br>
<br>
Hopefully, though, I can give you some general pointers as to where the problem might lie, maybe spark off a chain of thought for yourself.<br>
<br>
It's interesting that only around 10% of your users are affected. Do they have any other connectivity problems? It could be something entirely unrelated to POP3/SSL causing the problem. Do these users access any other applications over the network that are based on the same Linux server? Do they have any problems accessing these applications?<br>
<br>
From one of the PCs having the problem, try doing a 'ping -n 100 linux.box' and see if any packets are being dropped, or if your getting any high ping times. This might indicate a comms problem.<br>
<br>
Is there anything different about these PCs? ie, Are they Win98 where the rest are Win95? Are they using WinSock1 where the others are using WinSock2, or even a third party WinSock? Are they running any additional network services that the other PCs don't have? Are they using hosts files (c:\windows\hosts) that have incorrect IP addresses?<br>
<br>
I understand that these problems have only started occurring since you switched to the Linux box and SSL, but sometimes changing some kit on the network can highlight other comms issues.<br>
<br>
Sorry it's not a magic bullet, but hopefully I've given you some more things to look at/think about

<br>
<br>
Let us know how it goes.