Version:           1.7.2 (using KDE 3.3.2,  (3.1))
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-13)
OS:                Linux (i686) release 2.6.8-2-386

This happens when using cascading configuration
http://www.kde.org/areas/sysadmin/config_file.php#cascading
with shell expansion to centrally provide all users in a network with a working config.

1)

When choosing a default Mail Identity or Transport kmail saves this object as first 
entry in the config file. On the next program startup the first entry will be overridden by the central configs first Identity. 

The default Identity etc. should probabaly be defined by an id# not list enumeration.

Workaround: Don't change the default Identity or Transport but specify a 
specific Transport for your alternate Identities and use the "sticky" Identity 
checkmark in the composer window Identity selection to stick to your main 
Identity.



2)

The KDE config cascading and/or Kmail prevents  
different stanzas like [Identity #n] to get merged corectly between cascades.  
  
The numbering is taken as hardcoded and overlap between different cascades.
I.e. wehn [Identity #0] exists in a user's  
config file and another [Identity #0] is provided in a layer above, the one from  
above overrides/writes the users one.  
  
Coruption happens when config files are moved or edited, or during updates when new central configs with new stanzas get installed.  
  
Workaround: You have to incrase all numberings of user stanzas in a users config 
file i.e. [Account n+1] and also accounts=N+1 under [General], before creating 
a central config file with one such stanza added to the beginning.


Downstream problem reports including example configs (see attatchments) can for example be found at:
http://bugs.skolelinux.no/show_bug.cgi?id=550