|
FastMail Forum All posts relating to FastMail.FM should go here: suggestions, comments, requests for help, complaints, technical issues etc. |
|
Thread Tools |
13 Aug 2013, 12:44 AM | #1 |
Junior Member
Join Date: Aug 2013
Posts: 1
|
fastmail connection problems
Hi,
Since Aug 9th, have not been able to Fastmail via email client, I can access mail via web site. I re-checked settings on email client with no success, have been using secure settings with imap 993, pop 995,smtp 465. Today, I did a temporary test using "insecure.messagingengine.com for both imap and pop settings and was able to access mail and download it. Is there a recent problem with secure settings at fastmail server? Chris |
13 Aug 2013, 02:11 AM | #2 |
Junior Member
Join Date: Aug 2013
Posts: 7
|
Me too!
I have had exactly the same problem from exactly the same date.
I have been subscribed to fastmail.net for three years and using it without any problems. Then beginning after 8/8/2013 I can no longer access POP or SMTP. I have posted support tickets at the fastmail site, but it appears that they do not actually answer any such help requests. Making every test I know how to do, I have not been able to find anything wrong except my client (Pegasus) indicates: A network error occurred during connection to the host. <<no trace information available>> Perhaps we can share information and solve this problem. It looks like fastmail will not be of any help but I really don't want to have to change my email provider/address. Last edited by CCS : 13 Aug 2013 at 02:17 AM. |
13 Aug 2013, 03:32 AM | #3 |
The "e" in e-mail
Join Date: Feb 2006
Location: EU
Posts: 4,945
|
A change has been made on exactly the same date. Coincidence??
|
13 Aug 2013, 07:11 AM | #4 | |
Junior Member
Join Date: Aug 2013
Posts: 7
|
Quote:
I read that as having to do with webmail access via a browser. Would it have any bearing on POP and SMTP access? I am using an XP machine but I am not wanting to use webmail. However, now that I am being forced to use webmail (via Firefox or Opera) it works fine. It sucks that there seems to be no way to get any information from Fastmail, who should know about the issue. |
|
13 Aug 2013, 10:03 AM | #5 |
Junior Member
Join Date: Aug 2008
Posts: 7
|
|
14 Aug 2013, 12:01 AM | #6 | |||||
Junior Member
Join Date: Aug 2013
Posts: 2
|
Quote:
Quote:
So much for Quote:
Quote:
Quote:
Last edited by Pcar : 14 Aug 2013 at 05:08 AM. Reason: Remove support ticket url for opsec |
|||||
14 Aug 2013, 03:45 AM | #7 | ||
Junior Member
Join Date: Aug 2013
Posts: 7
|
Quote:
Quote:
|
||
14 Aug 2013, 11:22 PM | #8 |
Junior Member
Join Date: Aug 2013
Posts: 5
|
What email client are you using? I just connected to my FastMail account using Mozilla Thunderbird using the following server settings.
Incoming Server Address: mail.messagingengine.com Server Port: 995 Connection Security: SSL/TLS (When using STARTTLS, I am unable to download mail). Outgoing Server Address: mail.messagingengine.com Server Port: 465 Connection Security: SSL/TLS I hope this helps! |
14 Aug 2013, 11:34 PM | #9 |
The "e" in e-mail
Join Date: Feb 2006
Location: EU
Posts: 4,945
|
There is no general problem with IMAP access, using the setting you quote.
But one of the users who reported problems runs Pegasus Mail V4.41, which is 7 years' old .... |
15 Aug 2013, 02:48 AM | #10 |
Junior Member
Join Date: Aug 2013
Posts: 1
|
No good on latest Pegasus either.
IMAP doesn't work with Pegasus 4.63 (latest) either....can't connect. Works okay on my iPad/Phone though. Hope fix comes soon. I have years of email stored via Pegasus locally as well as on IMAP server.
|
15 Aug 2013, 03:45 AM | #11 | |
Junior Member
Join Date: Aug 2013
Posts: 7
|
It seems like the problem may be incompatibility with Pegasus. I use version 4.63 (Dec. 2011) which is less than 2 years old.
My ticket was updated today. Quote:
Last edited by CCS : 15 Aug 2013 at 03:50 AM. |
|
15 Aug 2013, 03:47 AM | #12 | ||
Junior Member
Join Date: Aug 2013
Posts: 2
|
Quote:
Quote:
If all versions of Pegasus and Mercury are affected, I'm sure other software will be too. Disappointing that admin haven't updated the SSL blog post and the status page with this fix for Pegasus/Mercury users |
||
18 Aug 2013, 02:50 AM | #13 |
Junior Member
Join Date: Aug 2013
Posts: 1
|
Pegasus 4.63
In my case IMAP using the regular settings was working just fine in Pegasus 4.63 until some point in the last 7 days, with August 9 being the obvious candidate day. I found this forum and changed the server to insecuressl.messagingengine.com and now I am connecting.
So the fallback to the older protocol when the revised one does not work does seem to be an issue. |
21 Aug 2013, 08:40 AM | #14 |
Junior Member
Join Date: Aug 2013
Posts: 7
|
Just thinking ...
Probably the thing that is new about the revised SSL standards is that a backdoor has been inserted for the NSA. So, it might be a good idea for anyone concerned with possibly having a semblance of security to use insecuressl.messaging engine.com so that they can continue to make use of the old SSL standards which might lack a backdoor. |
21 Aug 2013, 02:39 PM | #15 | |
Master of the @
Join Date: May 2012
Location: Melbourne, Australia
Posts: 1,007
Representative of:
Fastmail.fm |
Quote:
http://blog.fastmail.fm/2009/11/18/s...r-old-clients/ If your client works with the standard access methods and ciphers, then use them. If it doesn't then use insecuressl, but be aware that it is what it says: insecure. Consider switching clients and/or contacting the developers of your client to request an update. |
|