> SVN commit 706446 by bvirlet:
>
> Forward port r706174 and r706425
This commit caused a crash when checking mail for the second time.
AFAIK, this was also reverted in the enterprise branch.
Forward port of:
> SVN commit 709145 by tokoe:
>
> compile++
svn path=/trunk/KDE/kdepim/; revision=709448
Now, we use enums instead of strings.
Add the names of the types to KAccount. They can now be translated.
Also, provide an update script for easy config migration.
BUG: 90509
svn path=/trunk/KDE/kdepim/; revision=689148
KMail's file locking implementation uses the fcntl system calls by default.
This has problems in situations where your mail account folders are mounted
over nfs. There is a new hidden option where you can change the locking
implementation for local mail accounts. This will enable you to use a local
mail account which is mounted over nfs.
There are four different locking options you can use:
procmail_lockfile
mutt_dotlock
mutt_dotlock_privileged
none
procmail_lockfile will use a small utility that comes with procmail called
lockfile. You can use this if your mail folder is in a directory where you
have write permissions. This will not work on your /var/spool/mail/user file
in most cases. It will create .lock files on your account when kmail is
checking for new mail. Please note that this will only work if procmail is
installed on your system.
mutt_dotlock and mutt_dotlock_privileged will both use a small utility that
comes with mutt called mutt_dotlock. mutt_dotlock can be used in the same
way as the procmail_lockfile option, with the same limitation with regards to
the /var/spool/mail/ folders. However, the mutt_dotlock_privileged option
can create lock files in the /var/spool/mail directory. mutt_dotlock is a
setgid program and this option will run mutt_dotlock in setgid mode. Please
note that these options will only work if mutt is installed on your system.
If you don't want to use any locking, the none option is what you want.
However, there are risks of losing mail when no locking is used.
In your kmailrc, there are group sections for each of your mail accounts-
These will typically look like:
[Account 1]
Folder=inbox
Location=/net/ns/home/wynnw/.newmail
Name=Work
Type=local
check-exclude=false
check-interval=10
precommand=
To change the account to use the locking mechanism you want, change it to:
[Account 1]
Folder=inbox
Location=/net/ns/home/wynnw/.newmail
Name=Work
Type=local
check-exclude=false
check-interval=10
precommand=
LockType=<value>
where <value> is procmail_lockfile, mutt_dotlock, mutt_dotlock_privileged, or
none. So an actual working account group would look like:
[Account 1]
Folder=inbox
Location=/net/ns/home/wynnw/.newmail
Name=Work
Type=local
check-exclude=false
check-interval=10
precommand=
LockType=mutt_dotlock
Please make the changes exactly as you see them here- case sensitivity is
very important, as is spelling:)
svn path=/trunk/kdenetwork/kmail/; revision=66768
pop account type won't work until I check in an updated pop3 kioslave
(which won't be for a few more days at least). But everything should still
compile and run fine(ish) anyway.
Email me sanders@kde.org cc'ing the kmail list if something is screwed.
svn path=/trunk/kdenetwork/kmail/; revision=42010