-
Notifications
You must be signed in to change notification settings - Fork 22
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
Panicked with Parse(Unexpected("MailboxData(Recent(1))"))
#81
Comments
Error:
|
Hmm, I wonder if this is a bug in |
@jonhoo can you tell me what the |
Is there a good way to capture the on-the-wire-data? |
|
Actually, on a closer look, I think this errors stems from here, which suggests that the A wire data trace would come in very handy here! EDIT: keep in mind that you may want to remove the |
Reading the RFC, I think this might be an untagged (unsolicited) server message. That is, I think the assumption that you'll only get FETCH responses in response to a FETCH command is wrong. |
What makes you say that? 6.4.5 says:
Which I take to mean that you should only get |
Thanks! Here is the ssl stream from wireshark (I hope it is ok, that I posted it as comment, if you prefer I can export it) Strangely, I get another error message today
|
@kper you can probably remove some of the intermediate
segments to make it harder to read. This seems like a different issue though? Specifically, here you get The
and I have a fix in mind for this that I'll push shortly. |
Great! Thanks, the minimal example seems to run fine again :) |
Hmm, that's so weird. This shouldn't fix the |
I can't even explained why the error message changed - same emails, same server, same code I'll run the patch on my test server for a few days. Let's see if I get any error message. If not I will close this issue after the weekend. Huge thanks to you guys! |
Ok, I managed to to reproduce the error from before. I replied on an email from the server several times, waited until the server printed it out and then replied again. This leads to the error:
|
Interesting... It looks like the response to your last
starts with
which is all good, but is then followed by:
before it ends with
@djc from the RFC, I don't believe this is possible. AFAICT, only untagged |
Ahh, on further inspection of Section 7:
|
Looks good to me :) |
@mattnenterprise this also requires a release, or #69. |
@jonhoo nice find! I figured it was something like that. |
Hello!
I wrote a minimal example of my code, which works totally fine when only one guy sends an email. However, when I try to send an email from two different email addresses to server at the same time, my server panics.
Cargo.toml
main.rs:
The text was updated successfully, but these errors were encountered: