meli
/
meli
3
7
Fork 1
Code Issues 39 Projects 3 Releases 14 Activity
Labels Milestones
New Issue

#48 Issue NOOP after IMAP NO response

Open
opened 6 months ago by epilys · 0 comments
epilys commented 6 months ago
Owner

After receiving a tagged NO [FETCH] response, the client SHOULD issue a NOOP command...

RFC 2180

> After receiving a tagged NO [FETCH] response, the client SHOULD issue a NOOP command... [RFC 2180](https://www.ietf.org/rfc/rfc2180.txt)
epilys added the
IMAP
label 6 months ago
epilys added the
easy
label 6 months ago
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Apply labels
Clear labels
bug
Something is not working contacts currently worked on
Stuff I am working on right now duplicate
This issue or pull request already exists easy
Non-complex issues enhancement
New feature help wanted
Need some help IMAP
Related to the IMAP backend invalid
Something is wrong JMAP
Related to the JMAP backend Maildir
Related to the Maildir backend mbox
Related to the mbox backend notmuch
Related to the notmuch backend question
More information is needed wontfix
This won't be fixed
No Label
bug
contacts
currently worked on
duplicate
easy
enhancement
help wanted
IMAP
invalid
JMAP
Maildir
mbox
notmuch
question
wontfix
Milestone
Set milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Assign users
Clear assignees
No Assignees
1 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Write Preview
Loading…
Cancel
Save
There is no content yet.
Delete Branch '%!s(MISSING)'

Deleting a branch is permanent. It CANNOT be undone. Continue?

No
Yes