IMAP / SMTP Setup not working about nylas-mail HOT 77 CLOSED

Similar issue. I've tested several email clients (Thunderbird, Geary Mail, Apple Mail, Mutt) and N1 is the only one that's not working so far.

Following my settings from Geary Mail:

IMAP Settings:
Server: mail.company.com.au
Port: 993
User: first [email protected]
Password: ???
Encryption: SSL/TLS

SMTP Settings:
Server: mail.company.com.au
Port: 587
User: first last
Password: ???
Encryption: STARTTLS

Probably it's not important, but my username is my first and last name, including the space between them.

from nylas-mail.

Left and went to Polymail. Needed to connect two email's with GoDaddy's workspace. The UX isn't as clean as Nylas, but 90% of the functionality is there + support for far more IMAP/SMTP providers.

from nylas-mail.

Hey folks—if you're still having trouble getting your email account to work with Nylas Mail, you should try the new Mailspring client. Nylas sunset Nylas Mail back in August and I've been working on Mailspring since then. Instead of Javascript-based email sync, it uses Mailcore2 (the same IMAP and SMTP library used by Airmail and Sparrow), and I've found that the switch fixed a lot of connection issues with different mail providers. Hope that helps!

from nylas-mail.

Your going to need to provide a LOT more information than just saying its not working.

from nylas-mail.

What kind of information do you require?

As i stated on the OP

it always says that i need to check the credentials.

from nylas-mail.

What provider/imap server are you using? Are you using SSL? Are you using plaintext passwords or encrypted of some sort? just to name a few.

from nylas-mail.

Hi, I have also tried to setup imap/smtp on N1 till it decided not to try and connect to my local sync-engine instance and I gave up. I can give a little light though.

I run my own mail server, uses postfix + courier imap. The imap credentials passed fine but when it got to SMTP it wouldn't authenticate. I have my SMTP server set up to use STARTTLS and at no point did the sync-engine even attempt to contact my mail server.

p.s. At the end of the day the client looks pretty but having a MITM between my mail client and my mail server just isn't worth it. Especially if I'd be forced to bounce my email through a third party server. Better look next time.

from nylas-mail.

Hey @brunogaspar — we've tested the IMAP support with a range of different settings (under the hood, we use our IMAP support for Yahoo / AOL / iCloud, etc.) Could you give me your connection settings sans any sensitive info (username/password)? I can create an issue for our backend team to investigate and we'll figure out what the issue is.

from nylas-mail.

@bengotow Sorry for the late reply.

I've tried with another email account, and it's working. But not entirely sure why it's not working for the other email accounts since they work perfectly fine on other email clients.

I can create a temporary email account and give you the credentials so you can help us debug what might be wrong.

Both servers have cPanel.

Let me know how you want to proceed.

from nylas-mail.

@brunogaspar can you reproduce this with a temporary email account?

from nylas-mail.

Same problem here.
{"message": "Please check that your SMTP settings are correct.", "type": "auth_error", "error": "further_action_required"}

the SMTP server working on Apple mail.

Some details (except password ofc.)
curl -X POST -d '{"settings":{"imap_port":993,"imap_ssl_enabled":false,"smtp_port":587,"smtp_ssl_enabled":false,"imap_host":"wdgwv.nl","imap_username":"[email protected]","imap_password":"MYPASSWORD","smtp_host":"wdgwv.nl","smtp_username":"[email protected]","smtp_password":"MYPASSWORD"},"name":"Wesley de Groot","email":"[email protected]","provider":"imap"}' "https://:@api.nylas.com/auth?client_id=MYCLIENTID"

What the weird part about it is, is that in the GUI the smtp port is set to 25. (like normal SMTP's do)
If i'm running from the command line itself i got the same message.

Even if i manually set the smtp to 25 (in command line test)

So, i can't see anything, unless the Api send us more information.

from nylas-mail.

Folks, I think this is related to our backend system that uses imapclient. We should now be able to support STARTLS though, right @mjs ?

from nylas-mail.

I have version 0.3.19 and this is still not working this morning.

08:51:56 RunCopycurl -X POST -d '{"settings":{"imap_port":993,"imap_ssl_enabled":true,"smtp_port":587,"smtp_ssl_enabled":true,"imap_host":"mail.awke.co.uk","imap_username":"[email protected]","imap_password":"","smtp_host":"mail.awke.co.uk","smtp_username":"[email protected]","smtp_password":""},"name":"test","email":"[email protected]","provider":"imap"}' "https://:@api.nylas.com/auth?client_id=eco3rpsghu81xdc48t5qugwq7"

40308:51:10 RunCopycurl -X POST -d '{"settings":{"imap_port":993,"imap_ssl_enabled":true,"smtp_port":587,"smtp_ssl_enabled":true,"imap_host":"mail.awke.co.uk","imap_username":"[email protected]","imap_password":"£,"smtp_host":"mail.awke.co.uk","smtp_username":"[email protected]","smtp_password":""},"name":"test","email":"[email protected]","provider":"imap"}' "https://:@api.nylas.com/auth?client_id=eco3rpsghu81xdc48t5qugwq7"

Both return status 403

from nylas-mail.

Hi,
I have a similar problem.
SMTP: without SSL, port 25, annonymous authentication
Error message: Please provide your password and username

from nylas-mail.

not working for me either, for a custom imap setup with ssl and old certificates.
"Please check that your SMTP settings are correct."

works in Thunderbird, but only after i accept weak dh via config tweak, and works in gmail android client when i say "accept all certificates".
maybe there's an "issue" there with n1 being "too strict"?

from nylas-mail.

dont work for me the SMTP, the same problem, the IMAP mail is in godaddy, this data maybe help

from nylas-mail.

same problem here.

It works in Thunderbird after accepting weak certificates

from nylas-mail.

Same problem here with self-hosted smtp server (citadel) and self-signed certficates. from log (mail.err):

Oct 28 23:25:20 Server citserver[14625]: SSL_accept failed: retval=0, errval=1, err=error:00000001:lib(0):func(0):reason(1)
Oct 28 23:25:21 Server citserver[14625]: SMTP: client disconnected: ending session.

from nylas-mail.

+1

from nylas-mail.

Update: I got N1 IMAP/SMTP working by using signed SSL certificates so problem was (at least for me) self-signed cert.

from nylas-mail.

there should be an option to use self-signed certificates imho

from nylas-mail.

👍 Would be great to see, where the configuration was wrong instead of just showing the information which isn't helping the user. I double checked my configuration with Apple Mail and it all was correct, but still get the same error which is not helping me much.

from nylas-mail.

Apparently this is the same for me. SMTP with signed certificate is ok, but SMTP with self signed ones no. Using msmtp with mutt works with smtp 587 "auth login" as option.

from nylas-mail.

+1
Same problem here. I exactly rewrite configuration from Geary (where everything works fine) and I got error "Please check that your SMTP settings are correct."

from nylas-mail.

I think I'm having the same issue with TLS and self-signed certs.

In case it heps, my postfix says:

Nov 04 03:48:53 Tenshi postfix/smtpd[57136]: connect from ec2-52-32-74-203.us-west-2.compute.amazonaws.com[52.32.74.203]
Nov 04 03:48:54 Tenshi postfix/smtpd[57136]: SSL_accept error from ec2-52-32-74-203.us-west-2.compute.amazonaws.com[52.32.74.203]: 0
Nov 04 03:48:54 Tenshi postfix/smtpd[57136]: warning: TLS library problem: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca:s3_pkt.c:1294:SSL alert number 48:
Nov 04 03:48:54 Tenshi postfix/smtpd[57136]: lost connection after STARTTLS from ec2-52-32-74-203.us-west-2.compute.amazonaws.com[52.32.74.203]
Nov 04 03:48:54 Tenshi postfix/smtpd[57136]: disconnect from ec2-52-32-74-203.us-west-2.compute.amazonaws.com[52.32.74.203]

from nylas-mail.

Still doesn't work here either. Thunderbird works fine.

from nylas-mail.

I have not yet had a chance to make N1 connect to my SMTP account. I also get the "Please check that your SMTP settings are correct." error all the time. This is the only drawback for me to fully move all my email work to N1.

I hope this gets fixed soon.

from nylas-mail.

Hi, similar problem. Maybe my data can help :)

Secure SSL/TLS Settings

Username:   [email protected]
Password:   pass
Incoming Server:    server4.something.com
IMAP Port: 993
POP3 Port: 995
Outgoing Server:    server4. something.com
SMTP Port: 465

Authentication is required for IMAP, POP3, and SMTP.

Cheers!

from nylas-mail.

Is there going to be a fix for this so the product is actually usable ? :)

from nylas-mail.

same issue, server using TLS on port 587 for SMTP

from nylas-mail.

Was hoping this last update would solve this, unfortunately that isn't the case. It's pretty early days for N1, so Im still quite confident in it's future, but please fix this so we can help testing it out. Thanks.

from nylas-mail.

Hello,

I don t really understand your strategy with code for trying an "open source" software, i think is for making the "buzz". But i DL N1 yesterday and i have the same problèm it just don't work with smtp with starttls (my own server).
And without repo how can i manage update ?
Shall i request a new code ....
just put a repo and let everybody try, n1 seems to be really nice.

from nylas-mail.

Same here... Own server (Axigen Server).

from nylas-mail.

SMTP still not working (internal work server, so can't really provide more info)

from nylas-mail.

Started it in Developer-Mode now. Got the following error:

[SECURITY] node-uuid: crypto not usable, falling back to insecure Math.random()

Checked my login credentials and they're correct. Can we have a fix here anytime soon? I really want to give N1 a try, but with the current state it's not possible.

from nylas-mail.

Hello.
I wasn't able to add my IMAP account as well, after setting up the SMTP info the submit button was loading without any result. But after restarting the app I had the surprise to see that my account was finally set up!
Don't know how to provide data to help.
My IMAP account is a Fastmail email address.

from nylas-mail.

We've added support for self-signed SSL certificates in nylas/sync-engine@c5981d5

from nylas-mail.

Im assuming this is not in build 0.3.25 because using that version I still get the same error.

from nylas-mail.

Me2, I am still getting the same error as before after updating N1.
If there are some steps we should follow to fix it, please share with us.

from nylas-mail.

I am hugely excited about N1, but I am unable to even add the account because it doesn't even have the most basic auth features other clients(thunderbird, sylpheed, gyazmail) have.

I am not sure why would anyone build a software which fails for anyone whose email servers aren't set up in the one and only way the software's authors think is "enough"?

I need unencrypted, TLS, STARTTLS, SSL all versions... I mean sure, there is some which is seriously leaky and unsecure, but that doesn't mean it shouldn't be supported at all. Even my browser let me access websites which have self-signed certificates..

from nylas-mail.

I am not sure why would anyone build a software which fails for anyone whose email servers aren't set up in the one and only way the software's authors think is "enough"?

@ashnur Because it's beta.

I'm still not able to add my companies email account though. We use an unsigned certificate, hope that helps you with fixing.

from nylas-mail.

Same here. Just tried to connect with the same settings as my Thunderbird uses, and got SMTP error. Thunderbird was configured automatically by domain provider and these settings are the sam what was provided in mail configuration page in domain hosting.

from nylas-mail.

me too. console.log:

[SECURITY] node-uuid: crypto not usable, falling back to insecure Math.random()

my smtp needs:

Relaying via SMTP AUTH 587 (SMTP Submit) with STARTTLS (RFC 4409);

from nylas-mail.

@visualcookie fair enough, however it should be then made clear to the early adopters what features are and aren't implemented, so we do not waste time trying out something which lacks the minimum features we need to even install it.

from nylas-mail.

Tried 13 different smtp accounts, it's not working, I give up.

from nylas-mail.

Although the recent update has resolved one of my IMAP accounts, I still consistently receive request time out errors when adding an IMAP account from my university, it uses an internal server and plain text pass and ssl for both IMAP and SMTP. What more details are required to help me troubleshoot? I am certain that the account configuration is correct as I have it working in Thunderbird

from nylas-mail.

All IMAP Servers you want to connect to must have valid SSL certificates. Check the sync engine source code.

from nylas-mail.

I thought that self-signed certs were now accepted?

from nylas-mail.

@xeaon So N1 won't be usable for people who haven't signed their certificates? This sucks.

from nylas-mail.

@visualcookie i've testet N1+Sync Engine couple weeks ago. I don't follow the commits anymore, so i don't know if anything has changed.

I would never connect to my mail servers through a third party and running the sync engine to be able to use N1 as 'standonle' mail client is a bit too much. :)

from nylas-mail.

Same here, university email address gets refused for "Invalid credentials". Trust me, they aren't. How is this possible? Come on you guys, N1 deserves a breakthrough, but this ain't the way you're gonna get it...

from nylas-mail.

+1, I can configure my SMTP account without SSL, but event then it doesn't allow sending email.

from nylas-mail.

+1, my university email account is also getting "Invalid Credentials" using fairly standard IMAP/SMTP settings. It requires password authentication (yes I know, insecure) but there's no option for it. The same credentials work on clients (Mail.app, iOS mail) with this explicit option. Funny enough, the Windows 10 Mail app has a similar problem.

from nylas-mail.

+1 a HUGE issue. Three email accounts under Webfaction using the SSL information.. it works everywhere else, but here it gives me an "Invalid Credentials" warning.

This must be fixed.

from nylas-mail.

Hey folks—please check out the limitations of our IMAP/SMTP support here: https://nylas.zendesk.com/hc/en-us/articles/216118977-What-are-the-limitations-of-IMAP-SMTP-support-

There are a couple things we don't plan to support, including IMAP/SMTP servers on private networks (inaccessible from the public internet) and servers that send passwords in plaintext. The "username must be your email address" restriction is one we'll probably fix in the near future!

from nylas-mail.

@bengotow so any thoughts on why the webfaction smtp doesn't work? It meets all the requirements.

from nylas-mail.

@afturner I couldn't authenticate in the webfaction smtp too

from nylas-mail.

I have same problem. I'ts working with Outlook acc but fail with SMTP AOL "Error conecting to the server" and I'm sure I'ts all right.

from nylas-mail.

Same here, pop and smtp via powweb.com says it cannot connect to server, yet works fine in thunderbird.

This host uses connection security: STARTTLS on port 110 for pop.powweb.com
and smtp.powweb.com port 587

Full details here: http://www.powweb.com/knowledgebase/beta/article.bml?ArticleID=180

from nylas-mail.

I used to have the same problem. Then I tried to disable country restriction settings at my mail/smtp provider and Nylas added my account without any issue. Apparently it calls some service that checks SMTP settings outside my region.

from nylas-mail.

+1 for smtp settings are incorrect - on host freenet (mx.freenet.de)

from nylas-mail.

+1

I am having the same problem. My email account used to be with Google, but has since moved to a normal IMAP provider which uses STARTTLS. I even tried deleting my account and creating a new one with no luck. Tried SSL and without and confirmed that all settings are correct.

from nylas-mail.

I don't think they will ever fix this. I was never able to use it because of this specific issue.

from nylas-mail.

Same here

from nylas-mail.

Same issue. Had to switch to another client because of this.

from nylas-mail.

+1

from nylas-mail.

+1

from nylas-mail.

+1

This app had been working fine for weeks and this just started happening with my connected Google Accounts. I tried hitting the "Re-Authenticate with Google" button in preferences under Accounts, and doing that combined with a full restart seemed to fix it for a little while. I can't help but notice that this has, for me, coincided with the launch of Google's new Sign-In page; any possible connection there?

from nylas-mail.

+1 Having this problem with Outlook.com
The SMTP username and password are correct.

Incorrect SMTP username or password.
Some providers require an app password. Learn more.

from nylas-mail.

+1 to this

from nylas-mail.

+1 for godaddy workspace

from nylas-mail.

+1 for outlook, yahoo, and godaddy's workspace

from nylas-mail.

+1 is not working on hotmail account neither on private smtp account.

from nylas-mail.

I am having problems to connect too, my mail server is in the domain of xolo.conabio.gob.mx

from nylas-mail.

@bengotow thanks for the Mailspring and it works fine with the IMAP and SMTP plus the messages rule is also working good.

from nylas-mail.

+1
Still having this issue when moving out of EMClient. Had to install and use Thunderbird.

from nylas-mail.

Hi @MarkMacheta, I struggled a bit first before landing on the right settings. If you want to share more about your current settings, I'd be happy to help troubleshoot. Mailspring (formerly Nylas) is one of the better mail clients out there.

from nylas-mail.