On Fri, 01 Dec 2000 20:47:43 -0800, Seth Spitzer
<[EMAIL PROTECTED]> wrote:
>Oliver Thylmann wrote:
>
>> Hi Everyone,
>>
>> I just downloaded the latest build for windows just to be sure.
>
>was it a trunk mozilla build?
>
I have to admit I have no idea what a trunk build is :) I started with
m18 for windows, then upgrades several times. I am now running:
(from the about box)
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m18) Gecko/20001129
What might have caused this is that I had imported mail from Eudora
and then deleted the account and imported again and then set up 3
accounts. These 3 accounts are now wrong, or rather that they display
as Import Identity.
>> I have imported mail from Eudora. Set up 3 e-mail accounts and now in
>> the compose window it says
>
>did you import mail, or import settings?
I only imported mail.
>
>> From: Import Identity
>>
>> I can choose the drop down menu and see
>>
>> Import Identity <I>[EMAIL PROTECTED]</I>
>> Import Identity <I>[EMAIL PROTECTED]</I>
>> Import Identity <I>[EMAIL PROTECTED]</I>
>>
>>
>> Can I somehow change that so that I really see the Account name there
>> or the e-mail address or something? I have not found anything as of
>> yet.
>
>We used to leave import identities lying around, but I thought I fixed that.
>
>see http://bugzilla.mozilla.org/show_bug.cgi?id=58337
>
>Note, if you imported with an old build (before my fix for #58337)
>upgrading to a new build won't fix the problem. Is that what's going on?
>
As I explained above. I imported in M18. I am not sure at the moment
if I created the accounts first and then imported or imported and
then created the accounts. I remember that I once had a nice list
stating the account names. I changed the account names from the e-mail
address to names (STATSnet, BeNews, ...)
>>
>>
>> I already sent some messages with the wrong address :)
>>
>> If you can tell me the file where this is in I can also edit the file
>> with a text editor.
>
>edit your prefs.js and remove the bogus identities. Be *very* careful
>to make sure you remove the right prefs.
>
>This seems worthy of a bug and a release note, even though I think it is
>already fixed. Can you start a bug and attach your prefs.js file?
>
>As payment, I'll fix your prefs.js for you.
>
>-Seth
That sounds like a real deal then :) I will file my first bug report.
I will not edit mit prefs.js yet. I will wait for your edit and maybe
edit here to and save it to something like prefs_edit.js to see if I
did it right :)
So let's hope that I do this bug thing right :)
Oliver
