RFC 3503:Message Disposition Notification (MDN) pr...
RFC-Ref

MDN


Click on the red underlined text to get to the source

... MDNs. The MUA will not send MDN twice because the MUA keeps track of sent notifications ...
... the server is capable of storing the $MDNSent keyword by examining the PERMANENTFLAGS response code. In order to support MDN in IMAP, a server MUST support either the $MDNSent keyword, or arbitrary message ...


... deleted", "denied" or "failed" disposition type with "automatic-action" and "MDN-sent- automatically" disposition modes) for messages that do not have ...
... -- MUA sets the $MDNSent keyword for every message that required an automatic MDN to be sent, whether or not the MDN was sent. ...
... MUA sets the $MDNSent keyword for every message that required an automatic MDN to be sent, whether or not the MDN was sent. -- MUA ...
... -- MUA performs requested action and, with user's permission, sends appropriate MDN ("displayed", "dispatched", "processed", "deleted", "denied" or "failed" disposition type ...
... deleted", "denied" or "failed" disposition type with "manual- action" and "MDN-sent-manually" or "MDN-sent-automatically" disposition mode ...
... disposition type with "manual- action" and "MDN-sent-manually" or "MDN-sent-automatically" disposition mode). If the generated MDN ...
... MDN-sent-automatically" disposition mode). If the generated MDN is saved to a mailbox with the APPEND command ...
... (*) Note: MUA MUST NOT use \Recent flag as an indicator that it should send MDN, because according to [IMAP4], "If multiple connections ...
... However, the client MAY use \Seen flag as one of the indicators that MDN must not be sent. The client MUST NOT use any other standard flags, like \Draft or \Answered, to indicate that MDN ...
... MDN must not be sent. The client MUST NOT use any other standard flags, like \Draft or \Answered, to indicate that MDN was previously sent, because they have different well known meaning. In any case, in the presence of the $MDNSent keyword, ...
... the client MUST ignore all other flags or keywords for the purpose of generating an MDN and MUST NOT send the MDN. ...
... client MUST ignore all other flags or keywords for the purpose of generating an MDN and MUST NOT send the MDN. When the client ...
... mailbox. A client SHOULD NOT send MDN if it fails to store the $MDNSent keyword. Once the $MDNSent keyword is set, it MUST NOT be unset by a client ...
... the notification. This prohibits all other MUAs from sending MDN for this message. ...
... The client MUST NOT send MDN if a message has the $MDNSent keyword set. It also MUST NOT send MDN if a message has \Draft flag, because ...
... client MUST NOT send MDN if a message has the $MDNSent keyword set. It also MUST NOT send MDN if a message has \Draft flag, because some clients use this flag to mark a message as incomplete. ...
... client MUST set the $MDNSent keyword to prevent another client from sending MDN for the message. ...
... client MUST set $MDNSent keyword to prevent another client from sending MDN for the message. ...


... even if the client does not have 'w' right. This will prevent the generation of a duplicated MDN for the same message. Note that the server MUST still check if the client has rights to perform the COPY ...



Google
Web
RFC-Ref