-
Notifications
You must be signed in to change notification settings - Fork 121
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
Please support the newest RFC #20
Comments
I see. I will fix that when I have time. |
It seems that Google's server doesn't return an OTHER-ADDRESS. Is there anything I missed?
|
For people interested in this, please check the |
@ccding why is this in a dev branch and when will this be moved onto master? And is there something I can do to help this progress faster? |
@GlenDC because the code doesn't seem to work. I am not sure what I did wrong |
@GlenDC In RFC5780, the CHANGED-ADDRESS has been replaced by OTHER-ADDRESS. But the problem is, Google's server doesn't return either CHANGED-ADDRESS or OTHER-ADDRESS, while one of them is required by any RFC. I am sure I did something wrong (either in the code or reading the RFCs), but I didn't mange to figure it out. |
Cool, I'll try to look into it, can't promise I will get further than you though! And I just noticed that your master branch seems to be on par with your dev branch, so I guess the dev branch is no longer needed? |
I guess I mistakenly pushed the patch to master when fixing the readme issue. Anyways, I don't think it matters. |
in RFC5780, the CHANGED-ADDRESS has been replaced by OTHER-ADDRESS.
something about issue9
The text was updated successfully, but these errors were encountered: