
Thunderbird seems to send o/g mail details twice?
I have a slow internet connection which has become even slower, otherwise I wouldn't have noticed all these details or be bothered about them.
My upload speed is painfully slow – typically when I test it reports being around 100 – 200Kbs. Sending a 2Mb email can take 20 minutes, but that's a separate issue.
I use IMAP, I've set it to place a copy of the mail in the sent folder of my account. When I send I can see the following ongoing in a dialog box, in this order:
Status: Connected to smtp.1and1.com Status: Delivering mail Status: Sending login information Status: Copying message to Sent folder
My query is, why does Thunderbird need to sent the email twice – once sending the email itself, then again to put it in the sent folder? Surely sending it once would be enough, my mailserver should just copy the first mail into my sent folder without pointlessly uploading it a second time? Items 2,3,4 above, when the progress bar eventually reaches 100%, then it still hangs there for usually two minutes, before moving on to the next stage. I don't what it's waiting for at that point? Have I made an error in the way I've configured my email account?
ఎంపిక చేసిన పరిష్కారం
IMAP is not an ideal choice for your situation, precisely because there is more traffic between the client and the server.
An SMTP server sends your email, an IMAP server saves the Sent copy. In general it must be assumed these are two different machines, possibly in different locations and conceivably run by two separate organizations. So you can't assume there is a link between the two that could be used to copy the message between the two servers. The software has to be written to cope with all situations and doesn't necessarily offer any optimisations for configurations, say like Google Mail, where we could be pretty sure the two servers are co-located. But even when we think this is the case, there's no guarantee that it's actually arranged thus.
IMAP works best with an always-on and bidirectional connection. It's a poor fit to dial-up, or slow connections, or connections where there is a high cost per bit, such as satellite based services.
POP would be a better match to your slow connection. Each message makes just one journey between server and client. All copies are stored locally, on your computer. Or even webmail, where all these transactions take place at the server end of the connection.
ఈ సందర్భంలో ఈ సమాధానం చదవండి 👍 1ప్రత్యుత్తరాలన్నీ (2)
ఎంపిక చేసిన పరిష్కారం
IMAP is not an ideal choice for your situation, precisely because there is more traffic between the client and the server.
An SMTP server sends your email, an IMAP server saves the Sent copy. In general it must be assumed these are two different machines, possibly in different locations and conceivably run by two separate organizations. So you can't assume there is a link between the two that could be used to copy the message between the two servers. The software has to be written to cope with all situations and doesn't necessarily offer any optimisations for configurations, say like Google Mail, where we could be pretty sure the two servers are co-located. But even when we think this is the case, there's no guarantee that it's actually arranged thus.
IMAP works best with an always-on and bidirectional connection. It's a poor fit to dial-up, or slow connections, or connections where there is a high cost per bit, such as satellite based services.
POP would be a better match to your slow connection. Each message makes just one journey between server and client. All copies are stored locally, on your computer. Or even webmail, where all these transactions take place at the server end of the connection.
Zenos said
IMAP is not an ideal choice for your situation, precisely because there is more traffic between the client and the server. An SMTP server sends your email, an IMAP server saves the Sent copy. In general it must be assumed these are two different machines, possibly in different locations and conceivably run by two separate organizations. So you can't assume there is a link between the two that could be used to copy the message between the two servers. The software has to be written to cope with all situations and doesn't necessarily offer any optimisations for configurations, say like Google Mail, where we could be pretty sure the two servers are co-located. But even when we think this is the case, there's no guarantee that it's actually arranged thus. IMAP works best with an always-on and bidirectional connection. It's a poor fit to dial-up, or slow connections, or connections where there is a high cost per bit, such as satellite based services. POP would be a better match to your slow connection. Each message makes just one journey between server and client. All copies are stored locally, on your computer. Or even webmail, where all these transactions take place at the server end of the connection.
Right, thanks very much for the explanation. That's clear to me now as to what's happening, and why. My ISP tells me that there should be an FTTH fiber connection available "soon", so I think I'll hang on with the IMAP for a while longer.