What is the actual content of the message/delivery-status section of your test email?

See attached screenshot of my test results and also delivery-status-example.eml which hopefully you can use in your testing?

Not sure if it makes a difference, but there is a text/plain section before the message/delivery-status section.

I checked this ticket with Lucee version 6.1.0.127-SNAPSHOT. Now the deliverystatus attribute is displayed in cfpop/cfimap. However, in my scenario, it returns an empty result for that particular column, even when I set the content-type to message/delivery-status. could you please share here what you got for the delivery status column?

thank you for the clarifications which answer my original question whether there was any failure on my part.

I don’t want to step on any QA toes so I’ll leave the more extended test to .

I’ll be patient and wait for 6.1 release. I’m already stoked enough just having a developers conversation with the Lucee dev team!

Resolved means it’s passed QA, QA means it’s already in the latest 6.1 snapshots, i.e. since v 6.1.0.127, i.e ready for testing

6.1 is in still in development, there is still a RC process before it becomes a stable release, so a stable 6.1 is a while off

was asking to independently verify it’s working

Given that testcase only checks if the column is present in the result, not whether the column is correctly populated, if you could create a test which actually checks that the implementation works, that would be great see

The pop/imap stuff is a bit quirky in some environments, github actions has all the services configured for testing tho i believe added green mail in a different fashion for some other testcase recently

That said, I say stick with the services approach (as seen in imap.cfc) as that then allows testing against any (real) pop3 / imap / smtp servers, but it might be only practical to implement a test using greenmail

Right well that was my point re: eager to see it deployed, and my post was in response to re: “please give this PR merge a try and add a test case for it, if all is good in your opinion, please set to resolved (even the PR for the test case is hanging)”. Perhaps we can get clarification from Michael what is meant re: “PR for the test case is hanging”? And is a separate test case still required since I updated the unit test and it passed? And finally, when a ticket is “resolved”, does that mean it is deployed?