BD AV2010 reports:
C:\Documents and Settings\rwilson\Desktop\SuspectFiles.zip=>Suspect3.msg=>(body)=>(Compressed Rtf)=>(Rtf2Html) Trojan.Exploit.Iframe.D (no action was taken)
C:\Documents and Settings\rwilson\Desktop\SuspectFiles.zip=>Suspect1.msg=>(body)=>(Compressed Rtf)=>(Rtf2Html) Trojan.Exploit.Iframe.D (no action was taken)
C:\Documents and Settings\rwilson\Desktop\SuspectFiles.zip=>Suspect2.msg=>(body)=>(Compressed Rtf)=>(Rtf2Html) Trojan.Exploit.Iframe.D (no action was taken)
Note that these are the results of a contextual scan after I found the originally identified messages in the Outlook Archive and saved them seperately on my Desktop.
I'm pretty sure this is a false alarm - the messages in question are part of the same thread and all have the same two embedded pictures (which may or may not be relevant) but the original came from an entirely trusted source.
The problem is I don't understand enough about "trojan.exploit.iframe.d" to know how to verify that it's a false alarm. From what I can interpret online this is a IE bug from a long time ago that could be exploited by tagging executables with different MIME types... so what is BitDefender telling me about these messages? Why are they being flagged?