bamthomas / aioimaplib

Python asyncio IMAP4rev1 client library
GNU General Public License v3.0
138 stars 59 forks source link

aioimaplib.py”, line 560, in capability, not following RFC rules #45

Open FDumarey opened 5 years ago

FDumarey commented 5 years ago

There seems to be in bug in the aioimaplib library, it expects the “IMAPrev1” to be the first capability (index 0):

https://github.com/bamthomas/aioimaplib/blob/9670d43950cafc4d41aab7a36824b8051fa89899/aioimaplib/aioimaplib.py#L558

However, for example imap.telnet.be returns capabilities in roughly alphabetical order: $ telnet imap.telenet.be 143 Trying 2a02:1800:100:3::3... Connected to imap.telenet.be. Escape character is '^]'.

which seems to be acceptable by the IMAP RFC 3501: The server MUST send a single untagged CAPABILITY response with “IMAP4rev1” as one of the listed capabilities before the (tagged) OK response.

bamthomas commented 5 years ago

Thanks for the issue I will have a look soon (or if you want it to be implemented faster don't hesitate to make a PR).

lunitic commented 4 years ago

Was this ever solved? Having the same issue.

FDumarey commented 4 years ago

Hello,

Not yet no. But what I really wanted was to have a function template to set variables based upon email content. So now I’m using the imap_email_content integration, and I could solve my “case”.

Regards, Frederik.

Sent from Mail for Windows 10

From: Mathias Johansson Sent: maandag 18 mei 2020 21:38 To: bamthomas/aioimaplib Cc: FDumarey; Author Subject: Re: [bamthomas/aioimaplib] aioimaplib.py”, line 560, in capability, not following RFC rules (#45)

Was this ever solved? Having the same issue. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.