Since you had a faulty RAM, the first target of corruption is the whole filesystem. It is a good point to have eliminated this possibility of huge trouble.

If your problem does only appears within Mail this could mean that one of the files Mail had to write back was corrupted (in RAM).

To confirm this hypothesis:

1. make a backup

2. quit Mail and make a local backup of your Mail library (the following are shell commands to type within Terminal):

   cd ~/Library
   mv Mail Mail.backup
   

3. start Mail, create you a minimal account configuration and send yourself an E-mail

   If Mail doesn't crash, the problem stands within one of your Mail library file

   If Mail still crashes, report it.

4. quit Mail and put back in place the library you backed up at step 2:

   cd ~/Library
   rm -rf Mail
   mv Mail.backup Mail
   

If step 3 confirms that the problem stands within your Mail library, and if your mailboxes aren't too big, you could then make a rebuild of them:

1. launch Mail
2. select Mailbox > Rebuild
3. be patient, don't corrupt its rebuilding task, open the activity window: Window > Activity

Since you had a faulty RAM, the first target of corruption is the whole filesystem. It is a good point to have eliminated this possibility of huge trouble.

If your problem does only appears within Mail this could mean that one of the files Mail had to write back was corrupted (in RAM).

To confirm this hypothesis:

1. make a backup

2. quit Mail and make a local backup of your Mail library (the following are shell commands to type within Terminal):

   cd ~/Library
   mv Mail Mail.backup
   

3. start Mail, create you a minimal account configuration and send yourself an E-mail

   If Mail doesn't crash, the problem stands within one of your Mail library file

   If Mail still crashes, report it.

4. quit Mail and put back in place the library you backed up at step 2:

   cd ~/Library
   rm -rf Mail
   mv Mail.backup Mail
   

If step 3 confirms that the problem stands within your Mail library, and if your mailboxes aren't too big, you could then make a rebuild of them:

1. launch Mail

2. select

   Mailbox > Rebuild
   

3. be patient, don't corrupt its rebuilding task, open the activity window:

   Window > Activity
   

Since you had a faulty RAM, the first target of corruption is the whole filesystem. It is a good point to have eliminated this possibility of huge trouble.

If your problem does only appears within Mail this could mean that one of the files Mail had to write back was corrupted (in RAM).

To confirm this hypothesis:

1. make a backup

2. quit Mail and make a local backup of your Mail library (the following are shell commands to type within Terminal):

   cd ~/Library
   mv Mail Mail.backup
   

3. start Mail, create you a minimal account configuration and send yourself an E-mail

   If Mail doesn't crash, the problem stands within one of your Mail library file

   If Mail still crashes, report it.

4. quit Mail and put back in place the library you backed up at step 2:

   cd ~/Library
   rm -rf Mail
   mv Mail.backup Mail
   

If step 3 confirms that the problem stands within your Mail library, and if your mailboxes aren't too big, you could then make a rebuild of them:

1. launch Mail

2. select

   Mailbox > Rebuild
   

3. be patient, don't corrupt its rebuilding task, open the activity window:

   Window > Activity
   

Since you had a faulty RAM, the first target of corruption is the whole filesystem. It is a good point to have eliminated this possibility of huge trouble.

If your problem does only appears within Mail this could mean that one of the files Mail had to write back was corrupted (in RAM).

To confirm this hypothesis:

1. make a backup

2. quit Mail and make a local backup of your Mail library (the following are shell commands to type within Terminal):

   cd ~/Library
   mv Mail Mail.backup
   

3. start Mail, create you a minimal account configuration and send yourself an E-mail

   If Mail doesn't crash, the problem stands within one of your Mail library file

   If Mail still crashes, report it.

4. quit Mail and put back in place the library you backed up at step 2:

   cd ~/Library
   rm -rf Mail
   mv Mail.backup Mail
   

If step 3 confirms that the problem stands within your Mail library, and if your mailboxes aren't too big, you could then make a rebuild of them:

1. launch Mail
2. select Mailbox > Rebuild
3. be patient, don't corrupt its rebuilding task, open the activity window: Window > Activity