Labels Milestones

New Issue

Issue NOOP after IMAP NO response #48

Open

opened 1 year ago by epilys · 0 comments

epilys commented 1 year 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

easy

labels 1 year ago

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

async

embed

jmap

jmap-eventsource

lazy_fetch

master

memfd

sql

alpha-0.4.1

alpha-0.4.2

alpha-0.5.0

alpha-0.5.1

alpha-0.6.0

alpha-0.6.1

alpha-0.6.2

alpha-0.7.0

alpha-0.7.1

alpha-0.7.2

pre-alpha-0.0

pre-alpha-0.0.1

pre-alpha-0.2.0

pre-alpha-0.3.0

pre-alpha-0.3.1

pre-alpha-0.3.2

pre-alpha-0.4.0

Labels

Apply labels

Clear labels

bug
Something is not working contacts currently worked on
Stuff I am working on right now documentation 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 documentation 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

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Write Preview

Loading…

Cancel

Save

There is no content yet.