Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Thunderbird 52 64 bit is not working #5

Open
ahmedmonem1981 opened this issue Feb 3, 2018 · 7 comments
Open

Thunderbird 52 64 bit is not working #5

ahmedmonem1981 opened this issue Feb 3, 2018 · 7 comments

Comments

@ahmedmonem1981
Copy link

Dear all,
I have downloaded your plug in and tried to add my company exchange server mail on it but every time it gave me error message, what can I do?
the detailed error is below:
Failed to add account

If you feel like you should not experience this issuse please open
the error console (CTRL + SHIFT + J), filter mexint and report the
error to Issues on 'www.github.com/guderkar/mexint' or send it to
'[email protected]'. Thank you.

weather it's basic or NTLM security
can you help?

@guderkar
Copy link
Owner

guderkar commented Feb 4, 2018

Hi, did you try to enter credentials in domain\username or domain\email format? Some Exchange servers require that.

@woile
Copy link

woile commented Feb 9, 2018

I'm having the same issue. Linux 64 with tb 52.
Tried these options:
domain\username
domain\email
username
email

Thanks btw!

@guderkar
Copy link
Owner

guderkar commented Feb 9, 2018

I updated Node.js binaries as they were pretty old. I don't know if its gonna solve the problem. Can you provide information from error console?

@woile
Copy link

woile commented Feb 12, 2018

Still not working, this is what I see in the errors console:

mexint - node

stdout:
ERROR

stderr:
  AddAccountWindow.js:95
	addAccount chrome://mexint/content/AddAccountWindow.js:95:3
	oncommand chrome://mexint/content/AddAccountWindow.xul:1:1
	oncommand chrome://messenger/content/AccountManager.xul:1:1
	MsgAccountManager chrome://messenger/content/accountUtils.js:255:9
	oncommand chrome://messenger/content/messenger.xul:1:1

@guderkar
Copy link
Owner

Its authentication issue. Can you also provide ews url so i can try to inspect http headers?

@woile
Copy link

woile commented Feb 12, 2018

sorry, is internal from the company and I cannot share it :( thanks a lot anyway!

@guderkar
Copy link
Owner

That's bad, you might ask some IT guy from your company which authentication methods are allowed for EWS. You might be using OAuth which is not supported by this plugin. Also next thing that comes to my mind is that sometimes you have 2 SMTP adresses like [email protected] and [email protected] and only one of them works for authentication.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants