which has for some reason no X-UID header.
- Don't eat the X-UID header of every first message in a folder.
svn path=/trunk/kdenetwork/kmail/; revision=92524
to IMAP
- Don't crash, when deleting part of a thread in an IMAP folder
- Copying messages within the same IMAP account now also copies on the server
svn path=/trunk/kdenetwork/kmail/; revision=89913
Since I don't like a modal progress window as present in some other clients,
these cases need handling.
svn path=/trunk/kdenetwork/kmail/; revision=89245
many different huge folders that amount faster. Folder switching is 10% faster
with that.
Most time is still spent in QString::fromUtf8().
svn path=/trunk/kdenetwork/kmail/; revision=87274
I guess I spent already more time on waiting for the search to complete, that
it just took me to code that :-)
I hope the users can live with the fact that the number of messages are now
only updated every 100 messages, but that was a factor 2.
svn path=/trunk/kdenetwork/kmail/; revision=87032
Don't crash, when moving mouse over attachment or replying to a message after
searching in the folder and not clicking on a different message header in the
mean time.
svn path=/trunk/kdenetwork/kmail/; revision=77802
multiple child folders or higher nesting levels.
- Fix an off by one error when messages are marked unread or new manually.
svn path=/trunk/kdenetwork/kmail/; revision=76340
against mail loosing with procmail anyway.
The local account mailbox files are still locked as configured.
svn path=/trunk/kdenetwork/kmail/; revision=73104
- The headers are now decoded with the charset(s) specified it them and not
with the charset of the message.
- KMMsgBase::decodeRFC2047String now returns the string in unicode which
is compatible with encodeRFC2047String and makes some things easier.
- Also the address headers and all other headers are decoded, not only the
subject.
- The headers in the header list are displayed correctely.
- Editing mail in the outbox no longer corrupts non latin subjects.
- Reply and forward also keep non latin subjects.
- Indexfile version upgrade. Old indexes are converted.
svn path=/trunk/kdenetwork/kmail/; revision=71050
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
To fully experience the improvement you will need to remove your old .*.index
files. (But on the kde lists it's a big improvement).
Not verified by anyone else, but tested by myself and the person who reported
the bug.
svn path=/trunk/kdenetwork/kmail/; revision=61165
Note: kmfolder::removemsg is called by kmheaders::applyfilters, before a
message is filtered. At first glance this would suggest when can lose the
mail currently being filtered (when applying filters using Ctrl-J) if
KMail crashes while filtering a message. Actually I think we are saved by
a techinicality as there is no opportunity for the index file to be synced
to disk. (Yes I know kmfolder::close is called but the open count is greater
than 0 so the index won't be synced).
svn path=/trunk/kdenetwork/kmail/; revision=60492
Michael Haeckel
Stephan Kulow
Daniel Naber
Don Sanders
George Staikos
Jason Stephenson
Hans Petter Bieker
Mike Pilone