316788 - On migrating Eudora mail (In box) to Thunderbird JS.KakWorm.G is mis-reported and migration halts although this virus is NOT present on the machine.

Status: RESOLVED DUPLICATE of bug 229235

(Thunderbird :: Migration, defect)

Description

[dbrook]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Firefox/1.0.7

Migrating mail From Eudora to Thunderbird, JS.KakWorm.G is mis-reported and migration stops at the 'In' box. A full virus scan (Norton Internet Security 2004, fully updated) does not disclose the presence of Kakworm. Both of the available Microsoft removal tools also report no virus present. Symantic manual removal procedures have been followed precisely, finding nothing and making no difference. There is no other evidence of the virus whatsoever.
Eudora data can only be migrated to Thunderbird by temporarily disabling Norton antivirus, after which a full virus scan of Thunderbird (and Eudora)discloses no infection.

Reproducible: Always

Steps to Reproduce:
1.Uninstalled Thunderbird and re-installed it (twice). Same result.
2.
3.

Actual Results:  
To migrate Eudora 7.0.0.16 mail ('In' box) to Thunderbird it deems to be necessary to disable Norton anti-virus. Both before and after migration, however, full virus scans using up-to-date definitions disclose no virus infection at all. Ditto with Spybot and MS Giant anti-spyware.

Expected Results:  
I can see no reason why the Eudora 7 mail should not migrate. No problem with migrating the settings from Eudora 7.

Microsoft Outlook may seem to be a natural suspect. However, it is a part of a recently installed Office 2003; it is known to be patched against KakWorm and I do not use it for email. Nor do I Use Microsoft Outlook Express. TYo the best of my knowledge my Eudora mail has never been troubled by any virus infection.

Comment 1

[Ray Booysen]

To be honest, this is a Norton issue, not TB.  It is reporting the virus and although you say it is not on your machine, something is causing it to say it is there.  I would doubt it is TB that is causing this.