Hi Mark,
Found this on MacFixit.
Mail.app unable to connect to servers -- solution Several users have
reported an issue where Mail.app is unable to connect to POP and IMAP
mail servers after applying the Mac OS X 10.4.7 update.
In most cases, this issue can be solved via the following process:
Open System Preferences
Click on the "Network" pane
Select your current connection method (e.g. AirPort, etc.) and click
"Configure" (you may already be at the configuration screen)
Click the "Proxies" tab
Uncheck the "SOCKS Proxy" option from the "Select a proxy server to
configure:" menu
Click the "Apply Now" button
Cheers,
Ronni
On 30/06/2006, at 11:17 AM, Mark Secker wrote:
Googled this but found no helpful links maybe some on here can
suggest a solution...
we have a user who is using Apple's Mail program (against
recommendation ... but they are in an external support area so they
can go against recommendations as they get "charged" the same for
nonSOE issues as SOE issues).
when trying to POP or MAPI from any of his various mail account
servers gets the message:
"The connection to the server "{mailhost}" on port 0 timed out".
All his mail accounts work in Eudora.
All other user accounts on that machine gets the same problem.
Apple Mail works for him on other computers.
Pinging appropriate ports on mail hosts from his computer works as
does port scans on the local mail server.
putting mailhost address with port number so "mailhost.x.edu.au:
110" for POP account in Mail's settings also fails with exactly the
same "port 0" error.
when opening accounts preference in Apple Mail it was constantly
asking for "save changes" even when nothing had been changed so
first thought was permissions and second was corrupted preference
file.
Deleted mail preferences, ran repair permissions, FSCK and re
installed mail no joy with anything.
my guess is there may be a setting file somewhere separate from
the Mail.app bundle and com.apple.mail preference file that's
trying to hook in to Apple Mail (but only Apple Mail) to port zero?
anyone seen this - and more to the point got a solution or idea?
a system reinstall seems rather drastic solution for one errant app
but may come down to that I guess.
--
~
Mark Secker Computer Support Officer
ph# 61-8-6488 1855 (ECEL) <mailto:[EMAIL PROTECTED]>
University of Western Australia - CRICOS Provider No. 00126G
~
"It takes an idiot to do cool things.... that's why it's cool"
- Haruhara Haruka (FLCL)
Ubi fumus, ibi fumus
-- The WA Macintosh User Group Mailing List --
Archives - <http://www.wamug.org.au/mailinglist/archives.shtml>
Guidelines - <http://www.wamug.org.au/mailinglist/guidelines.shtml>
Unsubscribe - <mailto:[EMAIL PROTECTED]>
