Last week I had to diagnose an email failure. There it was, right in the log of the handshake with the email server -- despite repeatedly being told that the user had to login to the email server (since it's sending emails that will result in financial transactions), they failed to set up the server to do so. "Logon authentication not supported" or something like that. Saved me much time.

The other thing about Chilkat: the one license gets you all versions, for ActiveX, .Net, Java, Python, etc., and even Lianja (where the chilkat objects become native Lianja objects, and are available as such on Win/Mac/Linux). Had a project where a Java developer couldn't get encryption in Java to play nice: they had Chilkat Java, and in 15 minutes the problem was solved.

good luck,

Hank

>>Google Apps does in fact have limits: https://support.google.com/a/answer/166852?hl=en
>>
>>If you need to do more than that, use MailChimp or the like.
>>
>>One of the many reasons I use ChilKat for all kinds of connectivity (email, ftp, sftp, ftps, http) is the detail error messages that pinpoint the exact cause of the connectivity error.
>>
>>hth,
>>
>>Hank
>
>
>It's not a rate limit issue; we're well under those.
>
>If the damn control would timeout I could retrieve the error message and/or could try sendingt again. That it completely freezes and has to be end-tasked tells me the control has a major bug.
>
>I have used ChilKat controls for other things and have been very impressed. Guess I have to dump CDO for ChilKat on this.