Brian, thank you for bringing this to our attention. Because this issue does not necessary impact SmarterMail performance, I am going to change this from a Problem thread to an Idea thread. I have added it to our feature requests list for further discussion with the dev. team.