Sometimes (and very often for large emails) I get the "Could not queue message for sending" when clicking the Send button in the Compose window. Same happens when trying to save drafts.
After some debugging, the problem looks to originate from the libetpan library which doesn't handle the winsock2 "send" function's completion codes correctly. Specifically, "send" invoked from the end of mailstream_low_socket_write in libetpan/src/data-types/mailstream_socket.c sometimes returns -1 with WSAGetLastError() indicating error code WSAWOULDBLOCK. MSDN recommends some retries in this case:
Resource temporarily unavailable.
This error is returned from operations on nonblocking sockets that cannot be completed immediately, for example recv when no data is queued to be read from the socket. It is a nonfatal error, and the operation should be retried later. It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a nonblocking SOCK_STREAM socket, since some time must elapse for the connection to be established.
*** Bug 2289 has been marked as a duplicate of this bug. ***
*** Bug 2706 has been marked as a duplicate of this bug. ***
Does this still happen with new builds (which ship a newer libetpan) ?
The issue still exists in 3.9.0cvs98.
I have this issue with 3.8.1. Especially with attachments.
Ditto, except -only- when I include an attachment.
Same problem. The moment I add an attachment to the mail, I can't send it because of this error.
Version 3.13.2 on Windows 7 x64.
How does network log (look in Tools menu) from such a send attempt look like? Odds are there won't be anything useful, but for the sake of completeness, let's see it.
Also, have you reported this bug to libetpan developer?
Did anyone get this resolved? I use Ubuntu and Windows and would like to move away from Thunderbird and Outlook but without the ability to send attachments Claws won't work.
(In reply to comment #7)
> Same problem. The moment I add an attachment to the mail, I can't send it
> because of this error.
> Version 3.13.2 on Windows 7 x64.
(In reply to comment #9)
> Did anyone get this resolved? I use Ubuntu
It's a windows issue.
Also, it is an issue none of the developers are able to reproduce. Therefore it's not likely that a fix will be forthcoming. The source code is available, though, and I will gladly accept a patch - either for Claws Mail, or for libetpan - which fixes this issue for those who can reproduce it.
*** Bug 3674 has been marked as a duplicate of this bug. ***
*** Bug 3803 has been marked as a duplicate of this bug. ***
Fixed in commits
The patch is somewhat heavy-handed, but it should suffice.