Was this bug closed by mistake perhaps ? I am asking because bug 815638 (`Delivery Status Notification (DSN) does not work using Send Later`) was fixed 3 months ago with a target milestone of `125 branch`. (And it obviously wouldn't make sense to fix DSN for send later while wontfixing DSN generally. Or am I missing something ?) Furthermore DSN was confirmed to be functioning properly as recently as 7 months ago in Thunderbird (in [bug 1864583#c1](https://bugzilla.mozilla.org/show_bug.cgi?id=1864583#c1)) and 6 months ago in Seamonkey (in [bug 1872513#c2](https://bugzilla.mozilla.org/show_bug.cgi?id=1872513#c2)). In any case, can I please ask kindly for a reevaluation of the bug status for the following reasons: * This feature request is among the most popular ones with 58 votes. * Good reasons and benefits have been brought forward by the reporter (in comment #12) and other users (e.g. comment #17 etc.) * This feature was **wanted** (by users and the team alike) for over 2 decades(!): from 2001 - 2021. * several open dependencies * parity with Outlook: see comments #24, comment #28, comment #39, comment #55 * relevance for enterprises and in the working world more generally In light of all this, it's unclear why this popular and longstanding request was suddenly wontfixed (defined as *"we don't ever want this feature, will never implement it and don't accept patches for it"*). No patch being available today doesn't prevent this feature from being implemented in the future. So would it be OK to reopen this bug ?
Bug 93085 Comment 90 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Was this bug closed by mistake perhaps ? I am asking because bug 815638 (`Delivery Status Notification (DSN) does not work using Send Later`) was fixed 3 months ago with a target milestone of `125 branch`. (And it obviously wouldn't make sense to fix DSN for send later while wontfixing DSN generally. Or am I missing something ?) Furthermore DSN was confirmed to be functioning properly as recently as 7 months ago in Thunderbird (in [bug 1864583#c1](https://bugzilla.mozilla.org/show_bug.cgi?id=1864583#c1)) and 6 months ago in Seamonkey (in [bug 1872513#c2](https://bugzilla.mozilla.org/show_bug.cgi?id=1872513#c2)). In any case, can I please ask kindly for a reevaluation of the bug status for the following reasons: * This feature request is among the most popular ones with 58 votes. * Good reasons and benefits have been brought forward by the reporter (in comment #12) and other users (e.g. comment #17 etc.) * This feature was **wanted** (by users and the team alike) for over 2 decades(!): from 2001 - 2021. * several open dependencies * parity with Outlook: see comment #24, comment #28, comment #39, comment #55 * relevance for enterprises and in the working world more generally In light of all this, it's unclear why this popular and longstanding request was suddenly wontfixed (defined as *"we don't ever want this feature, will never implement it and don't accept patches for it"*). No patch being available today doesn't prevent this feature from being implemented in the future. So would it be OK to reopen this bug ?
Was this bug closed by mistake perhaps ? I am asking because bug 815638 (`Delivery Status Notification (DSN) does not work using Send Later`) was fixed 3 months ago with a target milestone of `125 branch`. (And it obviously wouldn't make sense to fix DSN for send later while wontfixing DSN generally. Or am I missing something ?) Furthermore DSN was confirmed to be functioning properly as recently as 7 months ago in Thunderbird (in [bug 1864583#c1](https://bugzilla.mozilla.org/show_bug.cgi?id=1864583#c1)) and 6 months ago in Seamonkey (in [bug 1872513#c2](https://bugzilla.mozilla.org/show_bug.cgi?id=1872513#c2)). In any case, can I please ask kindly for a reevaluation of the bug status for the following reasons: * This feature request is among the most popular ones of all time with 59 votes. * Good reasons and benefits have been brought forward by the reporter (in comment #12) and other users (e.g. comment #17 etc.) * This feature was **wanted** (by users and the team alike) for over 2 decades(!): from 2001 - 2021. * several open dependencies * parity with Outlook: see comment #24, comment #28, comment #39, comment #55 * relevance for enterprises and in the working world more generally In light of all this, it's unclear why this popular and longstanding request was suddenly wontfixed (defined as *"we don't ever want this feature, will never implement it and don't accept patches for it"*). No patch being available today doesn't prevent this feature from being implemented in the future. So would it be OK to reopen this bug ?