Thanks very much for that Levente - I had seen the more complex bits of code that set the port etc but not really noticed them. Looks like I'll need to extend the squeaksource settings page bit to try to handle at least setting the port number. Maybe I can add SecureSMTP support too.
Of course, nothing is a simple as it looks like it should be. I just lost most of a morning trying to work out why I couldn't connect to the relevant server; try from home... no, well maybe the port isn't exported, try running one of the images on the office server, hmph, have to use Chris' Smalltalk run:[]/filein stuff... wait, why does it simply sit there? Build trivial test file, no problem... add bit by bit... wait, simply setting the client password locks things up? What?
Aargh! The password has a ! in the middle. Sigh. Happily, doubling it up works around it (even results in the correct single ! in the client password) and now we can prove that ... the smpt server doesn't want to play nice.
Turns out you can try sending mail with curl, too, which at least supports the theory that the server is the problem and not me/us. Ah, the joys of software.
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Fractured Idiom:- J'Y SUIS, J'Y PESTES - I can stay for the weekend