Forum Discussion
Microsoft To Do Flagged Email List has Created a New Attack Surface for Junk Email
- Update: On January 29, I finally got a response directly from a support engineer on the To Do team! He acknowledged that the issue was being addressed and asked me to keep in touch with any updates. Since then, I'm happy to report that the To Do Flagged and Important smartlists have been SPAM free. The only exception was a temporary, regression on Feb 19 that was repatched within 24 hours.
Now we can enjoy SPAM free To Do smartlists. Note: Any junk mail that made its way into To Do before this issue was fixed will have to be removed manually.
Mike GlennI have the same issue continuing. It is really frustrating and a huge time waster. If this can't be resolved it really takes away any value ToDo could bring. couldn't temporarily you set up a way that ToDo doen't create, or automatically deletes tasks created by email in the JunkMail folder?
As soon as the issue occurred it disappeared again (probably after an update - certainly on my android device)... I noticed that an email in junk had the "important" and "flagged" markers BUT it was NOT showing in my task list. My issue last week was that items identified as junk where still appearing in Task List (so I'm happy that the issue is resolved).
definedrisk I believe you are correct. After being free of junk email in my Flagged and Important smartlists for about a year, it suddenly started appearing again on April 9th, then suddenly stopped again two days ago (April 11). I also see junk emails marked as important and/or flagged on April 12 and 13 (today) and none appear in my To Do smart folders.
Hopefully it won't happen again. Meanwhile, three days of junk mail getting into To Do has left quite a mess behind for us to clean up. Having to delete 30-40 (in my case) junk tasks one-at-a-time while being careful not to delete legitimate tasks is a royal PITA! Deleting all the junk emails from Outlook still leaves all the tasks behind. 😞
My guess is someone forgot to include the patch for this issue in the previous update, then noticed and patched it again a couple days ago.