This is just a suggestion, since the functionality is mainly for slightly retarded ppl like me.
Yesterday I searched all day why my service didn't run on the production server and ran perfectly fine on my dev machine.
The message I got in my eventlogging was "device not ready".
It took my an awfull lot of time to find out the message didn't come from the ftp protocol itself or winsock for that matter.
It merely was the logging I had set to a fixed path, way in the beginning of the production cycle, for initial testing purposes.
On the production machine it pointed to a CD-drive that wasn't accesible (off course) and spawned the exception "device not ready".
So I suggest that logging should suck up it's errors and fail silently.
It's a rather minor feature, but I just thought I'd put it up here for completeness' sake.
