Re: SMTP returns sockXXX error when sending large emails

David Gravereaux wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Robert Joy wrote:

Also, I noticed that when I enable the -usetls option it does not
encrypt the message as it's sending so I'm also wondering if this may
have something to do with the issue.

That could be true.. To use tls with iocpsock, you either need to hack
the tls init script to call [socket2] instead of [socket] or allow it to
be set using a global variable or maybe use 'rename socket socket2'

I would have liked iocpsock to have returned more useful error messages
than the useless POSIX translations, but was limited by how the generic
channel layer interfaces with the OS layer drivers. There doesn't seem
to be a way around that limitation.

For example with a connect(), having only a choice to return EINVAL
instead of WSAHOST_NOT_FOUND or WSATRY_AGAIN makes a difference to me.

- --
David Gravereaux <davygrvy@xxxxxxxxx>
[species:human; planet:earth,milkyway(western spiral arm),alpha sector]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (MingW32)

iD8DBQFE9On6lZadkQh/RmERAmH/AJ9NzBGXQIuC3NlqrW0sYh1MAYYURwCeL+Jx
HWsfX0oN+IVvoc+DfY7ShD8=
=qEpN
-----END PGP SIGNATURE-----

I'm using:

interp alias {} socket {} socket2

per Pat Thoyts recommendation but just tried:

rename socket oldsocket
rename socket2 socket

to see if that would make any difference and it did NOT.

Robert Joy
.

Relevant Pages