Currently Being ModeratedJul 23, 2010 1:07 PM (in response to Demetrios)You're going to want to describe how you have your mail client configured in (far!) more detail, imap or pop, whether you're using authenticated (you should be), what your network connection looks like, whether this is on-LAN or remote, etc., and you'll also be checking your server logs in parallel.
That "(null)" as the name of the server is particularly interesting. Odd. In addition to the topology, what does your local DNS look like here?
Currently Being ModeratedJul 23, 2010 1:43 PM (in response to MrHoffman)OK, was hoping to spare you the gory details and hope it was an obvious problem...alas...Here ya go:
Authentication is handled at login (single sign-on) by Kerberos Version 5 (GSSAPI)
Very simple network. Clients connected to server through hub via Ethernet (LAN)
Router also connected to same hub (and DSL modem is connected to router)
Forward (& Reverse) DNS resolves for both Client & Server w/in the LAN.
Client is using the Leopard Server for all its DNS (was necessary to get Kerberos working ages ago).
Everything works fine except sometimes Mail.app throws this alert.
BTW - At least 8 different mail accounts handled in this Mail.app (3 POP, 5 IMAP (incl 1 MobileMe), but only this Leopard Server account throws the alert. (Well, there's a Tiger Server out there on the Interweb that throws an alert much less often but that's when that office has a power failure or something).
Message was edited by: DemetriosMB Pro, PowerMac, mini, iPhone, TV, Mac OS X (10.6.4), Leopard Server 10.5.8
Currently Being ModeratedJul 23, 2010 2:29 PM (in response to Demetrios)On no specific evidence, I'd move off Kerberos (for testing purposes), and you'll want to review the server logs around the time of the errors.
Currently Being ModeratedSep 2, 2010 5:44 AM (in response to MrHoffman)I'm getting the same problem as described above. Not getting any mail through either. It is a pop account, authenticated by password. I'm not sure about the answers to the other questions that MrHoffman asks because I don't understand them.
Any help appreciated.
Currently Being ModeratedSep 3, 2010 6:23 AM (in response to David Fee1)Um, my own problem seemed to be that the password had somehow been removed from the mail accounts settings.
Currently Being ModeratedNov 1, 2010 3:54 PM (in response to Demetrios)Most likely this is a limit on the maximum number of concurrent connections allowed to your mailserver.
Mail.app makes a lot of simultaneous connections (open the activity window and see). So you will need to set up your mailserver to accommodate this.
Also, when collecting mail on its regular schedule, mail.app attempts to access all your email accounts simultaneously. So every email address generates multiple connections to the server. So the problem multiplies.
If you are able to set the maximum number of connections (total) and the maximum number of connections per ip address to larger numbers, then the problem should disappear. The numbers will depend upon the the number of people who are accessing those email address, the number of email addresses and the number of unique IP addresses in use.
I needed 200 (max) and 50 (max per ip).
Hope this helps.MBP "17" Intel Core i7 8GB, Mac OS X (10.6.4)
Currently Being ModeratedNov 8, 2010 6:45 AM (in response to Expr3ss!)Expr3ss! how many mail accounts do you have? I've tried bumping my my connections up to seemingly insane numbers (600 daemons, 300 maxperip). I only have 9 mail accounts.
This hasn't made any difference. If I hit "get mail" quickly I'm able to get all the mail eventually, but I can't be needing to click get mail 20 times each time I want to check all.
These problems all surfaced when upgrading to snow leopard and ilife 11.Macbook Pro 17, 2 mac minis, Macbook, iPhone 3G, iPad 32 and so on..., Mac OS X (10.5.1)
Currently Being ModeratedNov 8, 2010 8:42 AM (in response to Tony K)MY SOLUTION REPOSTED FROM ANOTHER THREAD:
I've just solved a similar issue.
I have a dedicated server running Plesk 9.5 and when I upgraded to iLife 11 and Snow Leopard this error appeared. I could quickly click "get mail" and I'd get all my mail, but only 3-4 of my 9 mail accounts would connect. Theo others would have the error:
"The server error encountered was: The attempt to read data from the server..."
I found solutions for those using IMAP mail:
modify the /etc/courier-imap/imapd configuration file and change MAXDAEMONS from 40 to 80 and MAXPERIP from 4 to 40. This allows all the machines behind my home firewall to connect to multiple accounts on the e-mail server with mailbox caching enabled.
I'd made this change on my server but it didn't seem to have any effect. It dawned on me that I'm using POP, not IMAP. So I found in /etc/courier-imap/pop3d the same settings. I changed the MAXDAEMONS from 40 to 80 and MAXPERIP from 4 to 40 and voila, all my connections concurrently worked.
This has taken me more than two days to fix and I hope posting this helps someone else with the same issue.Macbook Pro 17, 2 mac minis, Macbook, iPhone 3G, iPad 32 and so on..., Mac OS X (10.5.1)
Currently Being ModeratedNov 15, 2010 6:30 AM (in response to Tony K)Tony -
Thank you, thank you, thank you.
This solution to IMAP issues has saved my sanity. I've been battling with irritating alert symbols in Mail and spotty connections for a year now and by chance I found this post of yours. I've logged into my server, changed the values, and all seems good so far.
All the best,
AndrewMacBook Pro and iPhone, Mac OS X (10.6.5)
Currently Being ModeratedJan 11, 2011 2:20 PM (in response to Tony K)You rock 'Tony K'. I've several IMAP accounts setup on MediaTemple (dv) servers and have struck this issue for too long to remember. Editing '/etc/courier-imap/imapd' as you described and re-starting the IMAP service using Plesk worked a treat and solved the problem. Genius, thanks for the post.MacBook Pro, Mac OS X (10.6.6), http://chopstik.net
Currently Being ModeratedFeb 23, 2011 8:26 AM (in response to Demetrios)We had the same type of errors with a dedicated server running WHM. We adjusted the Mailserver Configuration settings for IMAP and the issue was solved.iMac 2.93 11,3 8GB ATI Radeon HD 5750 2TB Windows 7, Mac OS X (10.6.6), MacBook Pro 2.6 4,1 4GB 8600M GT 500GB Windows 7 Mac OS X (10.6.6)
Currently Being ModeratedOct 26, 2011 8:26 AM (in response to Tony K)
much appreciated, TonyK!
Currently Being ModeratedNov 10, 2011 3:11 PM (in response to Tony K)
This sounds like the very same issue I'm having. Mail works fine until I add accounts 5, 6, and 7.
I'm also both a novice to the more technical side of computing and new to Mac's so can anyone point me in the right direction of where and how I change these settings?
Currently Being ModeratedDec 12, 2011 1:22 PM (in response to Tony K)
modify the /etc/courier-imap/imapd configuration file and change MAXDAEMONS from 40 to 80 and MAXPERIP from 4 to 40...
Can you please be more specific - modify using which tool?
The server I am trying to connect to always gives me this error message: