Bug 1062

I tested this using the latest GIT. I created two different filters using the format matching on "shuang@{domain}.com" using two of my own email addresses. My test mails filtered correctly.

As you are using CentOS and 3.5.13, Francois Andriot maintains 3.5.13 package sets for Fedora and RedHat with backported patches. I think you can find those packages here:

http://git.trinitydesktop.org/viewgit/index.php?a=tree&p=Trinity%20Desktop%20Environment%20Packaging&h=1c499027a354a38bea9028120924cc4cba641f92&hb=279af91bd102f7416c1b74f16c715b3bc0f65b2b

I will ask Francois in the developer's mail list where to find a patched RedHat kdepim package for 3.5.13.

Hello, I've just tried the Kmail filter on Centos 6.2

My package version is:
$ rpm -qf /opt/trinity/bin/kmail
trinity-kmail-3.5.13-6.el6.opt.x86_64

Are you using this version (3.5.13-6) or an older one ?


I have no problem when testing on my mailbox (it's an IMAP folder).
I'm doing the same test as you:
- incoming mail was sent to "Francois Andriot <francois.andriot@xxxxxx.com>"
- Kmail filter is set to match "francois.andriot@xxxxxx.com"
=> the message is processed correctly

Maybe your real filter is more complex than your example, and it does not work because of another filter criteria ?

(In reply to comment #2)
> Hello, I've just tried the Kmail filter on Centos 6.2
> 
> My package version is:
> $ rpm -qf /opt/trinity/bin/kmail
> trinity-kmail-3.5.13-6.el6.opt.x86_64
> 
> Are you using this version (3.5.13-6) or an older one ?

[michael@localhost ~]$ which kmail
/opt/trinity/bin/kmail
[michael@localhost ~]$ rpm -qf /opt/trinity/bin/kmail
trinity-kdepim-3.5.13-5.el6.opt.x86_64
[michael@localhost ~]$ 

[root@localhost ~]# yum install trinity-desktop
{snip}
Package trinity-desktop-3.5.13-4.el6.opt.noarch already installed and latest version
Nothing to do
[root@localhost ~]#

Hi Francois,

It looks like you're not using the current stable release.  I'll guess you're using a -dev version?  If not, and you are using stable, can you update the http://trinitydesktop.org/installation.php#redhat section with how to keep the full Trinity package in sync w/ stable?

If you are using a -dev, is there a way to only update kmail to the -dev version?  (And can you also place instructions for updating a specific package to the -dev version on the Installation page?)


> I have no problem when testing on my mailbox (it's an IMAP folder).
> I'm doing the same test as you:
> - incoming mail was sent to "Francois Andriot <francois.andriot@xxxxxx.com>"
> - Kmail filter is set to match "francois.andriot@xxxxxx.com"
> => the message is processed correctly
> 
> Maybe your real filter is more complex than your example, and it does not work
> because of another filter criteria ?

Nope, it was the first filter and it was the only rule in that filter, with a stop processing.  I'm also using maildir not IMAP.  Both do seem mute based upon the different versions, but here's the kmailrc entry:

[Filter #0]
Applicability=0
AutomaticName=false
ConfigureShortcut=false
ConfigureToolbar=false
Icon=
StopProcessingHere=true
accounts-set=
action-args-0=trash
action-name-0=transfer
actions=1
apply-on=check-mail,manual-filtering
contentsA="Shih Huang" <shuang@{domain}.com>
fieldA=To
funcA=contains
name=<To>:"Shih Huang" <shuang@{domain}.com>
operator=or
rules=1

An odd note is the "" around the name.  This rule was created from the menu "Message >> Create Filter > Filter on To..."  Not sure this makes a difference, as shuang@{domain}.com should have caught it in any event.



TL:DR:  How do I upgrade kmail to version (3.5.13-6)?

Best,
Michael

Hello, 3.5.13-6 is in the stable repository.
You can do a "yum update" to perform a full update of all installed packages (it is not Trinity-specific).

Note that kdebase, kdepim, kdenetwork and kdeutils packages have all been split in several smaller packges, so the update may install many new packages, this is normal.

After updating, you'll have the trinity-kmail-3.5.13-6 package.


BTW I confirm the following working behaviour in kmail:

I send an email to myself, to the following address (including quotes):
"Francois Andriot" <francois.andriot@xxxxxxx.com>
When viewing the mail as raw text, I see the following line:
To: "Francois Andriot" <francois.andriot@xxxxxxx.com>

Now I create a filter in kmail from this mail, that matches the exact entire recipient of the mail (right-click, create filter ...). The action is to mark the message as unread:
In kmailrc I have:

[Filter #0]
Applicability=0
AutomaticName=false
ConfigureShortcut=false
ConfigureToolbar=false
Icon=
StopProcessingHere=true
accounts-set=
action-args-0=U
action-name-0=set status
actions=1
apply-on=check-mail,manual-filtering
contentsA="Francois Andriot" <francois.andriot@xxxxxxx.com>
fieldA=To
funcA=contains
name=<To>:"Francois Andriot" <francois.andriot@xxxxxxx.com>
operator=and
rules=1

And the filter works as expected. Whenever I apply it, the mail becomes unread.


Now I modify the filter in kmail so that the recipient address is only francois.andriot@xxxxxxx.com (no quotes or any special caracter).
In kmailrc I get:

[Filter #0]
Applicability=0
AutomaticName=false
ConfigureShortcut=false
ConfigureToolbar=false
Icon=
StopProcessingHere=true
accounts-set=
action-args-0=U
action-name-0=set status
actions=1
apply-on=check-mail,manual-filtering
contentsA=francois.andriot@xxxxxxx.com
fieldA=To
funcA=contains
name=<To>:"Francois Andriot" <francois.andriot@xxxxxxx.com>
operator=and
rules=1

As expected, the only modified line is "contentsA".
And the filter still works ...

I cannot reproduce what you describe.

(In reply to comment #4)
> Hello, 3.5.13-6 is in the stable repository.
> You can do a "yum update" to perform a full update of all installed packages
> (it is not Trinity-specific).
> 
> Note that kdebase, kdepim, kdenetwork and kdeutils packages have all been split
> in several smaller packges, so the update may install many new packages, this
> is normal.
> 
> After updating, you'll have the trinity-kmail-3.5.13-6 package.

I see the problem.  I'm a web developer (Drupal PM), most of my clients use Rackspace, and I can't willy-nilly update my base system to software versions that don't match Rackspace's.

So, I tried:

[root@localhost ~]# yum update trinity-desktop
Setting up Update Process
No Packages marked for Update
[root@localhost ~]#

Then as a swag:

[root@localhost ~]# yum update trinity-kdepim
{snip}
Install      35 Package(s)
{snip}

Dependency Installed:
{huge list}

Replaced:
  trinity-kdepim.x86_64 0:3.5.13-5.el6.opt

Complete!
[root@localhost ~]#

I'll update the rest[1]:

trinity-kdebase
trinity-kdepim
trinity-kdenetwork
trinity-kdeutils

But, (And I understand this is outside the boundaries of this ticket.)

a) why doesn't "update trinity-desktop" update these?  And,
b) what are the other sub-packages that need to be manually updated, so that the whole of Trinity is in sync?

When I get Trinity updated to the latest, I'll re-test the original problem.


[1] Extracting from the bug system, is this the complete list?

trinity-tdeaccessibility
trinity-tdeaddons
trinity-tdeadmin
trinity-tdeartwork
trinity-tdebase
trinity-tdeedu
trinity-tdegames
trinity-tdegraphics
trinity-tdelibs
trinity-tdemultimedia
trinity-tdenetwork
trinity-tdepim
trinity-tdesdk
trinity-tdetoys
trinity-tdeutils
trinity-tdewebdev
trinity-tqtinterface


PS: These all 404.

Error Downloading Packages:
  trinity-ark-3.5.13-6.el6.opt.x86_64: failure: trinity-ark-3.5.13-6.el6.opt.x86_64.rpm from trinity-3.5.13-el6: [Errno 256] No more mirrors to try.
  trinity-kfloppy-3.5.13-6.el6.opt.x86_64: failure: trinity-kfloppy-3.5.13-6.el6.opt.x86_64.rpm from trinity-3.5.13-el6: [Errno 256] No more mirrors to try.
  trinity-klaptopdaemon-3.5.13-6.el6.opt.x86_64: failure: trinity-klaptopdaemon-3.5.13-6.el6.opt.x86_64.rpm from trinity-3.5.13-el6: [Errno 256] No more mirrors to try.
  trinity-kwalletmanager-3.5.13-6.el6.opt.x86_64: failure: trinity-kwalletmanager-3.5.13-6.el6.opt.x86_64.rpm from trinity-3.5.13-el6: [Errno 256] No more mirrors to try.
  trinity-ktimer-3.5.13-6.el6.opt.x86_64: failure: trinity-ktimer-3.5.13-6.el6.opt.x86_64.rpm from trinity-3.5.13-el6: [Errno 256] No more mirrors to try.

Edit:

yum -y update trinity-kdeaccessibility
yum -y update trinity-kdeaddons
yum -y update trinity-kdeadmin
yum -y update trinity-kdeartwork
yum -y update trinity-kdebase
yum -y update trinity-kdeedu
yum -y update trinity-kdegames
yum -y update trinity-kdegraphics
yum -y update trinity-kdelibs
yum -y update trinity-kdemultimedia
yum -y update trinity-kdenetwork
yum -y update trinity-kdepim
yum -y update trinity-kdesdk
yum -y update trinity-kdetoys
yum -y update trinity-kdeutils
yum -y update trinity-kdewebdev

Okay, that doesn't work?

It's starting to replace trinity-kdelibs with tdelibs (from Trinity repo), so is there a different naming convention being used?  If so, please stick with the trinity- nomenclature, it's reasonably easy to understand.

Stopping now, will check back later.

Best,
Michael



[root@localhost ~]# yum -y update trinity-kdelibs
Loaded plugins: aliases, changelog, downloadonly, fastestmirror, presto, priorities, refresh-packagekit, security, tmprepo, verify,
              : versionlock
Loading mirror speeds from cached hostfile
 * base: centos.omnispring.com
 * epel: fedora-epel.mirror.lstn.net
 * extras: mirrors.gigenet.com
 * puias-addons: www.puias.princeton.edu
 * puias-addons-updates: www.puias.princeton.edu
 * puias-computational: www.puias.princeton.edu
 * russianfedora-free: mirror.nl.as6453.net
 * updates: mirror.steadfast.net
918 packages excluded due to repository priority protections
Setting up Update Process
Resolving Dependencies
--> Running transaction check
---> Package tdelibs.x86_64 0:3.5.13-9.el6.opt will be obsoleting
---> Package trinity-kdelibs.x86_64 0:3.5.13-8.el6.opt will be obsoleted
--> Finished Dependency Resolution

Dependencies Resolved

====================================================================================================================================
 Package                   Arch                     Version                              Repository                            Size
====================================================================================================================================
Installing:
 tdelibs                   x86_64                   3.5.13-9.el6.opt                     trinity-3.5.13-el6                    17 M
     replacing  trinity-kdelibs.x86_64 3.5.13-8.el6.opt

Transaction Summary
====================================================================================================================================
Install       1 Package(s)

Total download size: 17 M
Downloading Packages:
Setting up and reading Presto delta metadata
Processing delta metadata
Package(s) data still to download: 17 M
tdelibs-3.5.13-9.el6.opt.x86_64.rpm                                                                          |  17 MB     00:58     
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : tdelibs-3.5.13-9.el6.opt.x86_64                                                                                  1/2 
  Erasing    : trinity-kdelibs-3.5.13-8.el6.opt.x86_64                                                                          2/2 

Installed:
  tdelibs.x86_64 0:3.5.13-9.el6.opt                                                                                                 

Replaced:
  trinity-kdelibs.x86_64 0:3.5.13-8.el6.opt                                                                                         

Complete!
[root@localhost ~]#

Hello, if can tell yum to get every updates, but only from the Trinity repository, no other repositories.

Just type:
yum update --disablerepo="*" --enablerepo="trinity*"

The Trinity project is currently renaming its components to remove references to KDE. So new packages will be called "tde" instead of "kde".
In the future R14 release, there will no KDE reference at all.

I'm also changing the way TDE is packaged for RHEL/Fedora, so that there is no more "big monolithics packages" like kdebase, kdeutils, etc ... Now, there will be one small package for each program. So users can choose to install (or not install) every program they want to.
But there are still meta-packages that install everything, like before.