You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some cases imap-next is actively rejecting messages (e.g. imap-next is sending a BAD in case of Error::LiteralTooLong). In other cases the user is responsible for that. The responsibility is not well documented.
Another problem is that the user has no direct access to the tag. We could improve the situation by adding the tag to the error types. Maybe we could even use this for documentation: If the error type contains a tag, then the user is responsible for sending BAD.
The text was updated successfully, but these errors were encountered:
jakoschiko
changed the title
Make it clear who is resposible for rejecting messages
Make it clear who is responsible for rejecting messages
Jun 12, 2024
In some cases
imap-next
is actively rejecting messages (e.g.imap-next
is sending a BAD in case ofError::LiteralTooLong
). In other cases the user is responsible for that. The responsibility is not well documented.Another problem is that the user has no direct access to the tag. We could improve the situation by adding the tag to the error types. Maybe we could even use this for documentation: If the error type contains a tag, then the user is responsible for sending BAD.
The text was updated successfully, but these errors were encountered: