My custom POP3 client uses the Winsock control, and has a (not so) funny bug. Messages are not getting deleted from the server.
The client issues the 'DELE n', and gets the +OK response. When all done, it issues the 'QUIT' command, then waits until the winsock.State property DOES NOT equal sckOpen, like such:
Winsock1.SendData "QUIT" & vbCrLf
Do While (Winsock1.State = sckOpen)
DoEvents
Loop
End If
In my Winsock1_DataArrival() routine, I am retrieving the response with 'Winsock1.GetData strData', but not actually using it. My idea is to wait until the server closes the connection, which the client can detect with the .State property.
If I telnet to my mailserver and issue the commands manually, it works exactly as expected.
All I can think is that the client is *breaking* the connection before the server is done, in which case the server may abort writing the updated mailbox file.
Any insight appreciated.
-mike
The client issues the 'DELE n', and gets the +OK response. When all done, it issues the 'QUIT' command, then waits until the winsock.State property DOES NOT equal sckOpen, like such:
Winsock1.SendData "QUIT" & vbCrLf
Do While (Winsock1.State = sckOpen)
DoEvents
Loop
End If
In my Winsock1_DataArrival() routine, I am retrieving the response with 'Winsock1.GetData strData', but not actually using it. My idea is to wait until the server closes the connection, which the client can detect with the .State property.
If I telnet to my mailserver and issue the commands manually, it works exactly as expected.
All I can think is that the client is *breaking* the connection before the server is done, in which case the server may abort writing the updated mailbox file.
Any insight appreciated.
-mike
