java - JavaMail with IMAP getting “A1 NO LOGIN failed” exception -


this question related following question: using javamail connect imap getting "a1 no login failed" exception

i stumbled upon above thread since same problem using javamail 1.6.0. trying connect exchange mailbox imap. thunderbird connects , suppose cause other issue related javamail.

@bill shannon: have done things have highlighted above, except fact using starttls since ssl support disabled in exchange server (thunderbird uses starttls , connects correctly).

any on matter appreciated.

info   | jvm 1    | 2017/09/07 20:59:02 | debug: setdebug: javamail version 1.6.0 info   | jvm 1    | 2017/09/07 20:59:02 | debug: getprovider() returning javax.mail.provider[store,imap,com.sun.mail.imap.imapstore,oracle] info   | jvm 1    | 2017/09/07 20:59:02 | debug imap: mail.imap.fetchsize: 16384 info   | jvm 1    | 2017/09/07 20:59:02 | debug imap: mail.imap.ignorebodystructuresize: false info   | jvm 1    | 2017/09/07 20:59:02 | debug imap: mail.imap.statuscachetimeout: 1000 info   | jvm 1    | 2017/09/07 20:59:02 | debug imap: mail.imap.appendbuffersize: -1 info   | jvm 1    | 2017/09/07 20:59:02 | debug imap: mail.imap.minidletime: 10 info   | jvm 1    | 2017/09/07 20:59:02 | debug imap: enable starttls info   | jvm 1    | 2017/09/07 20:59:02 | debug imap: closefoldersonstorefailure info   | jvm 1    | 2017/09/07 20:59:02 | debug imap: trying connect host "mail.diversepower.com", port 143, isssl false info   | jvm 1    | 2017/09/07 20:59:02 | * ok microsoft exchange imap4 service ready. info   | jvm 1    | 2017/09/07 20:59:02 | a0 capability info   | jvm 1    | 2017/09/07 20:59:02 | * capability imap4 imap4rev1 logindisabled starttls uidplus children idle namespace literal+ info   | jvm 1    | 2017/09/07 20:59:02 | a0 ok capability completed. info   | jvm 1    | 2017/09/07 20:59:02 | debug imap: protocolconnect login, host=mail.abc.com, user=abc@def.com, password=<non-null> info   | jvm 1    | 2017/09/07 20:59:02 | a1 starttls info   | jvm 1    | 2017/09/07 20:59:02 | a1 ok begin tls negotiation now. info   | jvm 1    | 2017/09/07 20:59:02 | a2 capability info   | jvm 1    | 2017/09/07 20:59:02 | * capability imap4 imap4rev1 auth=plain uidplus children idle namespace literal+ info   | jvm 1    | 2017/09/07 20:59:02 | a2 ok capability completed. info   | jvm 1    | 2017/09/07 20:59:02 | debug imap: auth: plain info   | jvm 1    | 2017/09/07 20:59:02 | debug imap: mechanism plain disabled property: mail.imap.auth.plain.disable info   | jvm 1    | 2017/09/07 20:59:02 | debug imap: mechanism login not supported server info   | jvm 1    | 2017/09/07 20:59:02 | debug imap: mechanism ntlm not supported server info   | jvm 1    | 2017/09/07 20:59:02 | debug imap: mechanism xoauth2 disabled property: mail.imap.auth.xoauth2.disable info   | jvm 1    | 2017/09/07 20:59:02 | debug imap: login command trace suppressed info   | jvm 1    | 2017/09/07 20:59:02 | debug imap: login command result: a3 no login failed. 

@bill shannon: help. appreciate it.

thanks input. managed figure out problem. had enable plain , username has specified first part of email address (abc address of abc@def.com). believe exchange server in case exchange server 2013.

hope helps stumbles upon same issue.


Comments

Popular posts from this blog

angular - Ionic slides - dynamically add slides before and after -

minify - Minimizing css files -

Add a dynamic header in angular 2 http provider -