> In my experience, Wi-Fi has been getting less and less reliable over the years, at least in the city. > You could also try to monitor his connection, even by simply running ping in a Terminal window in the background. > If at all possible I would try to convince him to work over an Ethernet connection for a while to rule out problems with his wireless connection. > On Jul 30, 2013, at 11:20 AM, Chris Ferebee > wrote: > I definitely agree he should try connecting hard wired as well as from a different location (wired and wireless) as he could be having an issue with his wireless card.
> Are you using SSL, I've had issues if I didn't force Apple Mail to use the ssl ports. > Additionally when your client is experiencing these issues can they browse the web, of use the surge mail web front end? > Apple mail in 10.8 has a connection doctor under the pull down item "Window" it's the 8th item down. > I would expect he is experiencing some sort of network connectivity issue. > I, and a number of my clients use 10.8 without issue. He's tried it at his dads wireless network and also has the same issue unless he changes his smtp to uses his dads service provider (ie. > He can still browse the web when the connection is down. > Hmm, based on that, what ports is he using for smtp, pop (if using pop, I know you commented in imap) and imap ports? 465/587 for smtp, 993 for iMap?
> On Jul 30, 2013, at 12:00 PM, Glenn Meadows wrote:
Beck" He should definitely be using 587 for SMTP as most ISP's block 25 > It's really best to use SSL and get a proper certificate. > It's convenient to set Apple Mail to "use standard ports" for SMTP, which will try ports 25, 465 and 587 as necessary, but if your server offers SSL with self-signed certificates, this will often cause SSL to be enabled automatically as well, which results in "untrusted certificate" errors later on. On Jul 30, 2013, at 12:21 PM, Chris Ferebee wrote: I have also had Apple Mail not use SSL when it was available.
0 kommentar(er)
