IMAP SMTP connection problem with Exchange 2010 #130
Comments
|
Hey there—this looks like a certificate error. The logs aren't much use because the client hangs up due to the certificate error before even trying to log in. Can you look at #144 and see if the file paths that are referenced there are valid for you? I'm surprised this is happening on Ubuntu actually. |
|
hmm, in |
|
That's probably unrelated. Can you see if any of these paths are valid on your system? Mailspring needs to be able to find the |
|
ca-certificates.crt is in |
|
Sorry been to busy at work today, hopefully I can check tomorrow. |
|
Certs seems to be at the given ubuntu path as expected:
Also when I use curl I get no cert errors at all. And a more verbose check: |
|
Been having the same issue with school and work accounts. Running Ubuntu 16.04, and had no trouble finding the cert file at the given paths. |
|
let me add that I had no issues with Linux Mint 18.2 (Mate) and Ubuntu 16.04, only on LM 17.3 i get the error |
|
Then I am suspecting that it does not have to do with Ubuntu versions. Did you get the same mailsping versions to work with mint 18.2 and ubuntu 16.04 as you had fail with mint 17.3? |
|
@bengotow is it possible to download older build versions? |
|
Probably I faced the same issue on macOS when trying to connect to my company's Exchange server via IMAP and SMTP protocol. The app said 'Authentication Error - Check your username and password. (SMTP)View Log'. In my case, the SMTP server doesn't require authentication. BTW, would it be possible to bypass SMTP configuration? I would like to see my inbox as a first step. What operating system are you using?OS X El Capitan 10.11.6 What version of Mailspring are you using?1.0.6 |
|
I can confirm what DaichiUeura is telling. IMAP (Exchange) works fine, but SMTP-Setup against an Unix/Linux SMTP Server (no auth, white-listed source IP address) prevents me from finishing setup. Error message is the same (mailsmtp Last Error Code: 17). |
|
|
|
|
|
@DaichiUeura maybe, @bengotow pointed me towards certificates, however this has not lead me to any conclusive results as of now. Other people who added to my report have all reported different variables in their exposure to the same error message. This makes me think that the error code is a very common one. I would like to do more detailed research to better pin point the exact cause. However I have no idea where to check further, my knowledge of the codebase is practically none and my knowledge of the SMTP protocol is rudimentary. If anyone with better knowledge knows where to check further I would gladly do so, any help appreciated! |
|
I am having similar issues on latest version running on Fedora 26. I can confirm that original Nylas Mail is working. |
|
Ok I followed the following tutorial to test the connection from the command line: https://halon.io/blog/how-to-test-smtp-servers-using-the-command-line/. Everything is working fine with the exact same credentials and server info as I use in Mailspring so I think it is save to assume there is something bugged in Mailspring. @bengotow is there anything I can supply to help fix this issue? Please let me know because I would really like to use this client, I loved Nylas so I must have the same love for its offspring :). EDIT Added below part |
|
I have the same problem on Ubuntu 17.10, but Geary is working. |
|
@bengotow, please some feedback on my questions? I would happily fix it with a pull request but no idea where to begin. Where does the IMAP authentication take place? |
|
Hey folks—sorry for the delay. Yeah—it looks like there are several different issues being reported here. Support for SMTP without authentication (re @DaichiUeura and @thomaswieland's comments) was added in 1.0.3—file a separate issue if you're still having trouble with that. It's not really documented anywhere, but the Could you try ruling out any certificate / SSL issues by checking the "Allow Insecure SSL" box in IMAP/SMTP config? If that /does/ fix the issue, it'll narrow it down quite a bit. |
|
This seems to be fixed in the latest release for me using Zoho Mail.
Andrew Allen
…On Nov 7 2017, at 5:20 am, Ben Gotow ***@***.***> wrote:
Hey folks—sorry for the delay. Yeah—it looks like there are several different issues being reported here. Support for SMTP without authentication (re @DaichiUeura (https://github.com/daichiueura?recipient=reply%2B00a7f7538282fe83b65e36b7e0c609cf5c5db58cd27d955292cf000000011619591092a169ce0fc643d8%40reply.github.com) and @thomaswieland (https://github.com/thomaswieland?recipient=reply%2B00a7f7538282fe83b65e36b7e0c609cf5c5db58cd27d955292cf000000011619591092a169ce0fc643d8%40reply.github.com)'s comments) was added in 1.0.3—file a separate issue if you're still having trouble with that.
It's not really documented anywhere, but the mailsmtp Last Error Code being printed by Mailspring corresponds to an enum index in this table: https://github.com/dinhviethoa/libetpan/blob/master/src/low-level/smtp/mailsmtp_types.h#L48 (https://github.com/dinhviethoa/libetpan/blob/master/src/low-level/smtp/mailsmtp_types.h?recipient=reply%2B00a7f7538282fe83b65e36b7e0c609cf5c5db58cd27d955292cf000000011619591092a169ce0fc643d8%40reply.github.com#L48). It looks like value 17 is MAILSMTP_ERROR_AUTH_LOGIN, which is consistent with your latest notes.
Could you try ruling out any certificate / SSL issues by checking the "Allow Insecure SSL" box in IMAP/SMTP config? If that /does/ fix the issue, it'll narrow it down quite a bit.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub (#130?recipient=reply%2B00a7f7538282fe83b65e36b7e0c609cf5c5db58cd27d955292cf000000011619591092a169ce0fc643d8%40reply.github.com#issuecomment-342452803), or mute the thread (https://github.com/notifications/unsubscribe-auth/AKf3U2kZerkw-Zg9pEDbLWXGpSeCtVZgks5s0D0QgaJpZM4P1wk2?recipient=reply%2B00a7f7538282fe83b65e36b7e0c609cf5c5db58cd27d955292cf000000011619591092a169ce0fc643d8%40reply.github.com).
|
|
@bengotow, "Allow Insecure SSL" makes no difference. As I said using the @aia832003, your issue is not the same (although the error message might be the same but it is a generic one). So no This seems to be fixed is incorrect for this issue. |
InfopactMLoos
changed the title
|
I can confirm this error using my own mail server. I have no problems using Thunderbird or Geary. But Mailspring wont connect to my SMTP-Server. Cencosored log: |
|
Since my company migrated to office 365 I don't have any problem connecting mailspring to my mailbox anymore. This makes debugging this issue a bit harder and since support on this issue is also non-existing I will just close it. |
|
I have the exact same issue, and if it helps, it's the same on windows as well. I can help test this if needed. |
|
Since I have no mailserver to reproduce this problem with anymore, no clue where to look for more debugging information, no way to differentiate between all the different issues above and mostly because there is no support or at the least pointers on where to look in the source code.... I closed this issue and feel no need to pursue this any further. If you want help to fix the issue please create a new issue, best of luck. |
|
Same problem. Would have loved to keep using mailspring otherwise... |
|
BTW, can use newton mail without any problems... Maybe mailspring only works with outlook 365 and not outlook.com ? Or outlook exchange? |
|
----------IMAP----------
|
|
----------IMAP----------
�dY |
|
im unable to turn on IMAP in my outlook.com account. I think that's the culprit. |
|
This issue is closed and not being pursuit anymore, please open a new issue. |
|
Hey everyone, good news (or bad news, it depends :-) I fixed the issue for me, and maybe that helps narrowing down the problem for others. I tried various things back and forth, and I set up a hMailServer just for debugging. And the magic bullet was to disable the "PLAIN" authentication, and use "LOGIN" only. So what I see is that if PLAIN is enabled, Mailspring will try to do PLAIN authentication and finally fail. Doesn´t matter what else is enabled, it will only try PLAIN when PLAIN is enabled. If PLAIN is disabled, it will try LOGIN, which works for me. At least I get beyond the initial setup dialog and can sync my emails. Maybe someone can fix the code with this information? Thanks, Thomas |
|
@thomaswieland I just tried to reproduce it using my own mail server. Do you use Linux? Because only in Linux (Fedora) I am able to reproduce it. In Windows everything works well. |
|
@fr3dm4n I am using Mailspring on Windows 7 Enterprise x64. As SMTP Server I failed to connect
hMailServer had PLAIN and LOGIN authentication enabled at first; I couldn´t set up Mailspring, I got stuck with the error messages (see above). After disabling PLAIN auth on hMailServer (offering only LOGIN auth), I could set up Mailspring successfully. Does that answer your question? |
I tried to enable the IMAP provider but I ran into issues somehow. I tried to connect to my works exchange server through IMAP protocol, which should work as it does so with other clients.
It seems the Incoming mail (IMAP) is ok, however the SMTP part apparently fails. I looked a bit into SMTP protocol and as far as I understand it seems to go as planned but then abruptly aborts. SMTP code 250 should be expected and ok. The only error I see is the message:
mailsmtp Last Error Code: 17. I cannot seem to find any information regarding this error code so any help is appreciated!Are there any related issues?
I first ran into issue #123. This however seems to be another issue so I created this new ticket.
What operating system are you using?
Ubuntu 16.04
What version of Mailspring are you using?
1.0.3-f82c8836 EDIT: still broken on 1.0.7-664204d8
--
Bug?
Do you have any third-party plugins installed? If so, which ones?
No
Is the issue related to a specific email provider (Gmail, Exchange, etc.)?
IMAP (with Exchange server 2010)
Is the issue reproducible with a particular attachment, message, signature, etc?
Reproduce steps are hard to supply as it seems something related to my setup.
This is my error log, I have redacted some info.
--
The text was updated successfully, but these errors were encountered: