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

1.4.2 Gmail Inbox = null #383

Closed
m1dst opened this issue Aug 15, 2016 · 6 comments
Closed

1.4.2 Gmail Inbox = null #383

m1dst opened this issue Aug 15, 2016 · 6 comments
Labels
bug Something isn't working

Comments

@m1dst
Copy link

m1dst commented Aug 15, 2016

I just upgraded to 1.4.2 and found that I was getting a null exception when requesting the inbox.

var inbox = client.Inbox;
inbox.Open(FolderAccess.ReadWrite);

I rolled back to version 1.4.1 and it works as usual.

@m1dst m1dst changed the title 1.4.2 Gmail Inbox 1.4.2 Gmail Inbox = null Aug 15, 2016
@jstedfast
Copy link
Owner

I can't seem to reproduce this with 1.4.2 and there have been no patches that I can find that would affect this between 1.4.1 and 1.4.2.

Do you have a test case I can use to reproduce this problem?

@m1dst
Copy link
Author

m1dst commented Aug 16, 2016

Just tried the upgrade again and confirmed it still fails. It doesn't fail with a non Google IMAP though.

I will try to create something standalone to repro.

@m1dst
Copy link
Author

m1dst commented Aug 16, 2016

OK, managed to repro the problem in a console app using the following code.

using (var client = new ImapClient())
{

    var host = "imap.gmail.com";
    var port = 993;
    var username = "";
    var password = "";

    client.Connect(host, port, true);
    client.Authenticate(username, password);

    var inbox = client.Inbox;
    inbox.Open(FolderAccess.ReadWrite);
}   

MailKit42GmailNullRepro.zip

Confirmed that 1.4.2 fails and 1.4.1 works.

What I did notice is I deliberately supplied an incorrect password and the authentication section passed silently in 1.4.2 but in 1.4.1 it warned of incorrect password.

So something has definitely changed.

James

@jstedfast
Copy link
Owner

Okay, so supplying an invalid password is broken now in that it doesn't properly emit an exception.

That sounds plausible because I did change some of that logic recently. I'll take a look.

@jstedfast
Copy link
Owner

Yep! Found and fixed the issue! Thanks for reporting. I'll try to push a new nuget release soon.

@jstedfast jstedfast added the bug Something isn't working label Aug 16, 2016
@m1dst
Copy link
Author

m1dst commented Aug 16, 2016

I confirm it fixed my issue.

Thanks

On Tuesday, 16 August 2016, Jeffrey Stedfast notifications@github.com
wrote:

Yep! Found and fixed the issue! Thanks for reporting. I'll try to push a
new nuget release soon.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#383 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA6h-NBxOKp-FG8yJjb_nTcwyoqtWjKTks5qga0UgaJpZM4JklCc
.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants