Adds two variants of setStatusMsgTransmissionCompleted and setStatusMsgWithTimestamp to KMBroadcastStatus.
Based on a patch by Patrick S. Vogt <patrick.vogt@unibas.ch>
svn path=/trunk/kdepim/; revision=212674
kmacctmgr has 2 lists (currently checking and todo), the accounts care for the setting of the necessary flags.
All accounts show a transmission message, use -1 as newMailsProcessed argument to use your own message (e.g. in kmacctexppop)
svn path=/trunk/kdepim/; revision=210690
Please note that this port includes a bug fix which should be ported back to make_it_cool. I've sent the bug fix to the mailing list.
svn path=/trunk/kdenetwork/kmail/; revision=184866
to be called with dangling points with functions called with QChar
arguments, that are safer and easier to program too
svn path=/trunk/kdenetwork/kmail/; revision=179849
show the user a wrong number of mails loaded. Currently, it shows just the
number of mails in the last account, but with this patch, it shows the
total number of mails.
I haven't tested pop3 or maildir, but they should work as the patch is quite
simple. I also didn't find a way to make it work with imap, so in case there's
an imap account, it just turns back to the current (broken) behaviour.
I waited 4 days for comments for this patch, so I think it's enough.
Btw, this fixes#38403
svn path=/trunk/kdenetwork/kmail/; revision=140766
- Don't allow cancelling mail fetching from a local account, this eats the
remaining mails otherwise
svn path=/trunk/kdenetwork/kmail/; revision=128887
Use the account name instead of the host/file name in the "preparing
transmission..." status bar message.
The change in kmnewiostatuswdg.cpp is in dead code. It's there to keep the
number of i18n strings constant.
svn path=/trunk/kdenetwork/kmail/; revision=128732
Instead when checking for new mail sync just before expunging the local
account or just before deleting mail from the pop server. I guess syncing
isn't currently as issue for imap.
There is a question of whether/when sync should be called for other
operations such as moving messages between folders.
svn path=/trunk/kdenetwork/kmail/; revision=105142
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