A Windows XP help forum. PCbanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » PCbanter forum » Microsoft Windows 7 » Windows 7 Forum
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Problems with Mac.com



 
 
Thread Tools Rate Thread Display Modes
  #1  
Old November 2nd 18, 06:09 PM posted to alt.windows7.general
T
external usenet poster
 
Posts: 4,600
Default Problems with Mac.com

Hi All,

I have a customer with two Windows (w7 & w8.1) computers
running Thunderbird 52.9.1 access the same eMail account
on mac.com.

Problem, they time out on "send" a lot. If send goes through,
they then time out a lot copying to the "sent" folder.

I am using these settings:

Mac.com (Apple iCloud)
IMAP Server imap.mail.me.com
IMAP port 993
IMAP security SSL / TLS
IMAP username Your full email address
IMAP password Your Mac.com password

Mac.com (Apple iCloud)
SMTP Server smtp.mail.me.com
SMTP port 587
SMTP security STARTTLS
SMTP username Your full email address
SMTP password Your Mac.com password

Any words of wisdom?

Many thanks,
-T

Me thinks it is Mac.com as it works well after hours.

Ads
  #2  
Old November 2nd 18, 10:25 PM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Problems with Mac.com

T wrote:
Hi All,

I have a customer with two Windows (w7 & w8.1) computers
running Thunderbird 52.9.1 access the same eMail account
on mac.com.

Problem, they time out on "send" a lot. If send goes through,
they then time out a lot copying to the "sent" folder.

I am using these settings:

Mac.com (Apple iCloud)
IMAP Server imap.mail.me.com
IMAP port 993
IMAP security SSL / TLS
IMAP username Your full email address
IMAP password Your Mac.com password

Mac.com (Apple iCloud)
SMTP Server smtp.mail.me.com
SMTP port 587
SMTP security STARTTLS
SMTP username Your full email address
SMTP password Your Mac.com password

Any words of wisdom?

Many thanks,
-T

Me thinks it is Mac.com as it works well after hours.


It could be that the connection times out too quickly
on the mac.com end.

The modern Thunderbird software is a marvel of asynchronous
and illogical behavior. When you set a max connection count
on the client end, it could easily use all the max number
of connections while it is fiddling and diddling. You would
want to make sure the Thunderbird client is set for
fewer connections, than the Mac.com end is attempting
to enforce. (A connection could time out on the Mac.com
end, Thunderbird could immediately open a new one, the Mac.com
could reject it because "too many connections". Being a greedy
gus could have its disadvantages.)

Older versions of Thunderbird tended to do things
more sequentially. The reason we're forced into newer
versions, is to get the benefits of TLS for transport.

Due to the asynchronous nature of the modern Thunderbird,
you'd be hard pressed to "study" the thing with Wireshark,
and make sense of what it's doing. Wireshark is available
for all three platforms (Windows,Mac,Linux) if you need
to use it. When operated on the plaintext port on the
mail server, you should be able to read the packet
content and make sense of it. While using TLS, not
so much...

In the past, we had the opportunity to use telnet
to carry out a fake session with a mail server and debug it.
I don't know what the "TLS version" of such an adventure
would look like (stelnet?). The only reason for doing that, would
be if you thought the immediately delivered error messages
had some significance.

Paul
  #3  
Old November 2nd 18, 11:35 PM posted to alt.windows7.general
T
external usenet poster
 
Posts: 4,600
Default Problems with Mac.com

On 11/2/18 2:25 PM, Paul wrote:
T wrote:
Hi All,

I have a customer with two Windows (w7 & w8.1)Â* computers
running Thunderbird 52.9.1 access the same eMail account
on mac.com.

Problem, they time out on "send" a lot.Â* If send goes through,
they then time out a lot copying to the "sent" folder.

I am using these settings:

Mac.com (Apple iCloud)
IMAP ServerÂ*Â*Â*Â* imap.mail.me.com
IMAP portÂ*Â*Â* 993
IMAP securityÂ*Â*Â* SSL / TLS
IMAP usernameÂ*Â*Â* Your full email address
IMAP passwordÂ*Â*Â* Your Mac.com password

Mac.com (Apple iCloud)
SMTP ServerÂ*Â*Â*Â* smtp.mail.me.com
SMTP portÂ*Â*Â* 587
SMTP securityÂ*Â*Â* STARTTLS
SMTP usernameÂ*Â*Â* Your full email address
SMTP passwordÂ*Â*Â* Your Mac.com password

Any words of wisdom?

Many thanks,
-T

Me thinks it is Mac.com as it works well after hours.


It could be that the connection times out too quickly
on the mac.com end.

The modern Thunderbird software is a marvel of asynchronous
and illogical behavior. When you set a max connection count
on the client end, it could easily use all the max number
of connections while it is fiddling and diddling. You would
want to make sure the Thunderbird client is set for
fewer connections, than the Mac.com end is attempting
to enforce. (A connection could time out on the Mac.com
end, Thunderbird could immediately open a new one, the Mac.com
could reject it because "too many connections". Being a greedy
gus could have its disadvantages.)

Older versions of Thunderbird tended to do things
more sequentially. The reason we're forced into newer
versions, is to get the benefits of TLS for transport.

Due to the asynchronous nature of the modern Thunderbird,
you'd be hard pressed to "study" the thing with Wireshark,
and make sense of what it's doing. Wireshark is available
for all three platforms (Windows,Mac,Linux) if you need
to use it. When operated on the plaintext port on the
mail server, you should be able to read the packet
content and make sense of it. While using TLS, not
so much...

In the past, we had the opportunity to use telnet
to carry out a fake session with a mail server and debug it.
I don't know what the "TLS version" of such an adventure
would look like (stelnet?). The only reason for doing that, would
be if you thought the immediately delivered error messages
had some significance.

Â*Â* Paul


And tips on how to reduce the connections?

  #4  
Old November 3rd 18, 12:06 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Problems with Mac.com

T wrote:
On 11/2/18 2:25 PM, Paul wrote:
T wrote:
Hi All,

I have a customer with two Windows (w7 & w8.1) computers
running Thunderbird 52.9.1 access the same eMail account
on mac.com.

Problem, they time out on "send" a lot. If send goes through,
they then time out a lot copying to the "sent" folder.

I am using these settings:

Mac.com (Apple iCloud)
IMAP Server imap.mail.me.com
IMAP port 993
IMAP security SSL / TLS
IMAP username Your full email address
IMAP password Your Mac.com password

Mac.com (Apple iCloud)
SMTP Server smtp.mail.me.com
SMTP port 587
SMTP security STARTTLS
SMTP username Your full email address
SMTP password Your Mac.com password

Any words of wisdom?

Many thanks,
-T

Me thinks it is Mac.com as it works well after hours.


It could be that the connection times out too quickly
on the mac.com end.

The modern Thunderbird software is a marvel of asynchronous
and illogical behavior. When you set a max connection count
on the client end, it could easily use all the max number
of connections while it is fiddling and diddling. You would
want to make sure the Thunderbird client is set for
fewer connections, than the Mac.com end is attempting
to enforce. (A connection could time out on the Mac.com
end, Thunderbird could immediately open a new one, the Mac.com
could reject it because "too many connections". Being a greedy
gus could have its disadvantages.)

Older versions of Thunderbird tended to do things
more sequentially. The reason we're forced into newer
versions, is to get the benefits of TLS for transport.

Due to the asynchronous nature of the modern Thunderbird,
you'd be hard pressed to "study" the thing with Wireshark,
and make sense of what it's doing. Wireshark is available
for all three platforms (Windows,Mac,Linux) if you need
to use it. When operated on the plaintext port on the
mail server, you should be able to read the packet
content and make sense of it. While using TLS, not
so much...

In the past, we had the opportunity to use telnet
to carry out a fake session with a mail server and debug it.
I don't know what the "TLS version" of such an adventure
would look like (stelnet?). The only reason for doing that, would
be if you thought the immediately delivered error messages
had some significance.

Paul


And tips on how to reduce the connections?


Details will vary slightly with version. Interesting values
might be 1 or 2, instead of 10.

https://i.postimg.cc/wxSdqfdz/thunde...fig-editor.gif

Historically, changing connection count hasn't been a "big win",
but it's the only way I know of to cause a change in the
greedy gus behavior of modern Thunderbird.

Paul
  #5  
Old November 3rd 18, 12:20 AM posted to alt.windows7.general
T
external usenet poster
 
Posts: 4,600
Default Problems with Mac.com

On 11/2/18 4:06 PM, Paul wrote:
T wrote:
On 11/2/18 2:25 PM, Paul wrote:
T wrote:
Hi All,

I have a customer with two Windows (w7 & w8.1)Â* computers
running Thunderbird 52.9.1 access the same eMail account
on mac.com.

Problem, they time out on "send" a lot.Â* If send goes through,
they then time out a lot copying to the "sent" folder.

I am using these settings:

Mac.com (Apple iCloud)
IMAP ServerÂ*Â*Â*Â* imap.mail.me.com
IMAP portÂ*Â*Â* 993
IMAP securityÂ*Â*Â* SSL / TLS
IMAP usernameÂ*Â*Â* Your full email address
IMAP passwordÂ*Â*Â* Your Mac.com password

Mac.com (Apple iCloud)
SMTP ServerÂ*Â*Â*Â* smtp.mail.me.com
SMTP portÂ*Â*Â* 587
SMTP securityÂ*Â*Â* STARTTLS
SMTP usernameÂ*Â*Â* Your full email address
SMTP passwordÂ*Â*Â* Your Mac.com password

Any words of wisdom?

Many thanks,
-T

Me thinks it is Mac.com as it works well after hours.


It could be that the connection times out too quickly
on the mac.com end.

The modern Thunderbird software is a marvel of asynchronous
and illogical behavior. When you set a max connection count
on the client end, it could easily use all the max number
of connections while it is fiddling and diddling. You would
want to make sure the Thunderbird client is set for
fewer connections, than the Mac.com end is attempting
to enforce. (A connection could time out on the Mac.com
end, Thunderbird could immediately open a new one, the Mac.com
could reject it because "too many connections". Being a greedy
gus could have its disadvantages.)

Older versions of Thunderbird tended to do things
more sequentially. The reason we're forced into newer
versions, is to get the benefits of TLS for transport.

Due to the asynchronous nature of the modern Thunderbird,
you'd be hard pressed to "study" the thing with Wireshark,
and make sense of what it's doing. Wireshark is available
for all three platforms (Windows,Mac,Linux) if you need
to use it. When operated on the plaintext port on the
mail server, you should be able to read the packet
content and make sense of it. While using TLS, not
so much...

In the past, we had the opportunity to use telnet
to carry out a fake session with a mail server and debug it.
I don't know what the "TLS version" of such an adventure
would look like (stelnet?). The only reason for doing that, would
be if you thought the immediately delivered error messages
had some significance.

Â*Â*Â* Paul


And tips on how to reduce the connections?


Details will vary slightly with version. Interesting values
might be 1 or 2, instead of 10.

https://i.postimg.cc/wxSdqfdz/thunde...fig-editor.gif

Historically, changing connection count hasn't been a "big win",
but it's the only way I know of to cause a change in the
greedy gus behavior of modern Thunderbird.

Â*Â* Paul


Thank you!

I wonder if that will help with the smtp send issue?



  #6  
Old November 3rd 18, 03:30 AM posted to alt.windows7.general
Paul[_32_]
external usenet poster
 
Posts: 11,873
Default Problems with Mac.com

T wrote:

Thank you!

I wonder if that will help with the smtp send issue?


You would think it would be single-threaded, but hey,
this is Thunderbird we're talking about. I bet you could
see weird stuff even with Sysinternals "TCPView".

Paul
 




Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off






All times are GMT +1. The time now is 04:13 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 PCbanter.
The comments are property of their posters.