R
Ralph Page
My webhost recently changed email servers and since that time I've
noted that emails larger than roughly 100K seldom get through.
I used a packet sniffer to examine the exchange and it appears to be
identical to that for smaller emails that work.
When the final packet from the server arrives, I (Outlook) ACKs it
with the expected sequence and acknowledgement values but it does
nothing further. After 5 minutes the server times out.
After several (up to 20-30) tries spanning a few hours to a few days,
the large email typically gets through and the exchange looks
identical except that Outlook responds with the expected request to
retrieve the next email rather than just sitting quietly after the
final packet is received.
How does Outlook determine when the data has been completely sent?
I noted that the server provides the size in octets and I also noticed
that the final packet from the email server always has the push (PSH)
flag set in the TCP portion of the header. The final ACK from me
contains the expected sequence and acknowledgement values.
Thanks for any light anyone can shed on this, the webhost has been
less than helpful in helping to track this down.
-Ralph Page
noted that emails larger than roughly 100K seldom get through.
I used a packet sniffer to examine the exchange and it appears to be
identical to that for smaller emails that work.
When the final packet from the server arrives, I (Outlook) ACKs it
with the expected sequence and acknowledgement values but it does
nothing further. After 5 minutes the server times out.
After several (up to 20-30) tries spanning a few hours to a few days,
the large email typically gets through and the exchange looks
identical except that Outlook responds with the expected request to
retrieve the next email rather than just sitting quietly after the
final packet is received.
How does Outlook determine when the data has been completely sent?
I noted that the server provides the size in octets and I also noticed
that the final packet from the email server always has the push (PSH)
flag set in the TCP portion of the header. The final ACK from me
contains the expected sequence and acknowledgement values.
Thanks for any light anyone can shed on this, the webhost has been
less than helpful in helping to track this down.
-Ralph Page