MDN bug

[nexus]

Every message with \Recent flag and message delivery notification tries to send notification in defiance of RFC 3503. MDN must be sent only one time.

There is a bug in program/include/rcube_imap_generic.php in line 1733.

Please replace

} else if ($flag == '$MDNSENT') {

with

} else if ($flag == 'MDNSENT') {

Thanks

[alec]

$MDNSENT is a proper flag, so the fix is wrong. I don't understand the issue. Enable imap_debug and provide the log. Does your server support $MDNSENT flag?

[nexus]

Please look at the 99 line

'MDNSENT' => '$MDNSent',

and 1733

} else if ($flag == '$MDNSENT') {

There is one superfluous dollar sign, so the condition never became true.

[nexus]

Yes, my server supports $MDNSent flag and now it works fine

[alec]

In line 1733 the flag from FETCH response is checked. So, your "fix" makes that rcube_mail_header::mdn_sent is never set, because server returns "$MDNSent" value in FLAGS item of the FETCH response. Please, describe tour problem once again, because I don't understand it. Works for me.

[nexus]

Yes, server returns "$MDNSent" value in Flags but at line 99 creates an array $flags with key = 'MDNSENT' and value '$MDNSent'. Condition checks $flags keys! And key = 'MDNSENT' but not '$MDNSENT'.

It leads to client tries to send notifications over and over again when message Flag == \Recent because conditions is never meet

[alec]

Replying to nexus:

Yes, server returns "$MDNSent" value in Flags but at line 99 creates an array $flags with key = 'MDNSENT' and value '$MDNSent'. Condition checks $flags keys! And key = 'MDNSENT' but not '$MDNSENT'.

This array is not used in fetchHeaders(). You're wrong!!!!

It leads to client tries to send notifications over and over again when message Flag == \Recent because conditions is never meet

No it isn't. And \Recent flag has nothing to this. See steps/mail/show.inc ca. line 73.

[nexus]

I'm sorry, I'm wrong. It is really not a bug.

Please close the ticket.