Bug 332953

Summary: "maildir: Not supported type" popup on mail receive: "Unable to deserialize payload part"
Product: [Frameworks and Libraries] Akonadi Reporter: Martin Steigerwald <Martin>
Component: serverAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: dvratil
Priority: NOR    
Version: 1.12.0   
Target Milestone: ---   
Platform: Debian unstable   
OS: Linux   
Latest Commit: http://commits.kde.org/akonadi/50495dcbad84799af23bd24dfbbbefd99bc32afb Version Fixed In: 1.12.1
Sentry Crash Report:

Description Martin Steigerwald 2014-04-02 09:38:54 UTC 
I am setting this to critical, as I am not sure whether this causes data loss. Please verify and lower the priority if the error message does not indicate data loss. Thanks. I will now log out and do a clean reboot and filter / sort mails. If they are still there then I will lower the severity myself again.

I upgraded from Akonadi 1.11.0 (from Debian Sid) to Akonadi 1.12.0 (from Debian Experimental) to see whether it gives improvement regarding some issues I have. I let the database migration complete.

On the first mail download / filtering I get some "Maildir: Nicht unterstützter Typ" (translated: "Maildir: not supported type") popups and "Unable to deserialize payload part" errors in ~/.xsession-errors

Reproducible: Always

Steps to Reproduce:
1. Upgrade from Akonadi 1.11.0 to 1.12.0.
2. Receive mails for a POP3 account which are to be locally stored in Maildir
3. Filter them. I think this step is not even needed.
Actual Results:  
"Maildir: Nicht unterstützter Typ" (translated: "Maildir: not supported type") popup and errors like the following in ~/.xsession-errors:

kontact(24024)/libakonadi Akonadi::EntityTreeModelPrivate::monitoredItemChanged: Got a stale notification for an item which was already removed. 865405 "139642
8793.R520.merkaba" 
kontact(24024)/libakonadi Akonadi::ItemSerializer::deserialize: Unable to deserialize payload part: "HEAD" 
kontact(24024)/libakonadi Akonadi::ItemSerializer::deserialize: Payload data was:  "Return-Path: <kde-pim-bounces@kde.org>
X-Original-To: Martin@lichtvoll.de
Delivered-To: martin@mondschein.lichtvoll.de
X-policyd-weight: using cached result; rate:hard: -4.5
Received: from postbox.kde.org (postbox.kde.org [IPv6:2a01:4f8:140:8302::4]) by mail.lichtvoll.de (Postfix) with ESMTPS id 533685D for <Martin@lichtvoll.de>; Wed,  2 Apr 2014 09:53:14 +0200 (CEST)
Received: from postbox.kde.org (localhost [IPv6:::1]) by postbox.kde.org (Postfix) with ESMTP id 9605AB37E98; Wed,  2 Apr 2014 07:53:54 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=kde.org; s=default; t=1396425235; bh=2z0Neusftk6aGyOSy1jsYu7k39l1SOETeNV2vyz9b+I=; h=Date:From:To:Message-ID:In-Reply-To:References:MIME-Version: Subject:Reply-To:List-Id:List-Unsubscribe:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=G8 z2z+1dMIzq0VAUB4m9DHj/2sdgCYSjrfRTe4dBBKZEqlWgLbO5hZfFjg3o3bV+8wK9p Kk3TtM7JUpauc+Ks9tiTyQy7k8t+RF0CyDoZ7kOFw1kYVq+8qZGDeo0yIUsUMMpL/bk NmEuuIUEsSjtygTxR70QzQMoNE5yeGz6LIo=
X-Original-To: kde-pim@kde.org
Delivered-To: kde-pim@localhost.kde.org
Received: from build.kde.org (build.kde.org [IPv6:2a01:4f8:160:9363::5]) by postbox.kde.org (Postfix) with ESMTP id D5E88B37D3E for <kde-pim@kde.org>; Wed,  2 Apr 2014 07:53:29 +0000 (UTC)
Received: from localhost ([127.0.0.1]) by localhost with esmtp (Exim 4.72) (envelope-from <null@kde.org>) id 1WVFzF-0007UB-Bm for kde-pim@kde.org; Wed, 02 Apr 2014 07:53:29 +0000
Date: Wed, 02 Apr 2014 07:53:29 +0000
From: KDE CI System <null@kde.org>
To: kde-pim@kde.org
Message-ID: <766110984.224.1396425209074.JavaMail.jenkins@build>
In-Reply-To: <1511974366.223.1396424232427.JavaMail.jenkins@build>
References: <1511974366.223.1396424232427.JavaMail.jenkins@build>
MIME-Version: 1.0
X-Jenkins-Job: kdepim_stable
X-Jenkins-Result: SUCCESS
X-Scanned-By: MIMEDefang 2.71 on 46.4.96.248
Subject: [Kde-pim] Jenkins build is back to stable : kdepim_stable #1754
X-BeenThere: kde-pim@kde.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: KDE PIM <kde-pim@kde.org>
List-Id: KDE PIM <kde-pim.kde.org>
List-Unsubscribe: <https://mail.kde.org/mailman/options/kde-pim>, <mailto:kde-pim-request@kde.org?subject=unsubscribe>
List-Post: <mailto:kde-pim@kde.org>
List-Help: <mailto:kde-pim-request@kde.org?subject=help>
List-Subscribe: <https://mail.kde.org/mailman/listinfo/kde-pim>, <mailto:kde-pim-request@kde.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kde-pim-bounces@kde.org
Sender: kde-pim-bounces@kde.org
" 
kontact(24024)/libakonadi Akonadi::ItemSerializer::deserialize: Unable to deserialize payload part: "ENVELOPE" 
kontact(24024)/libakonadi Akonadi::ItemSerializer::deserialize: Payload data was:  "("Wed, 02 Apr 2014 07:53:29 +0000" "[Kde-pim] Jenkins build is back to stable : kdepim_stable #1754" (("KDE CI System" NIL "null" "kde.org")) ((NIL NIL "kde-pim-bounces" "kde.org")) (("KDE PIM" NIL "kde-pim" "kde.org")) ((NIL NIL "kde-pim" "kde.org")) NIL NIL "<1511974366.223.1396424232427.JavaMail.jenkins@build>" "<766110984.224.1396425209074.JavaMail.jenkins@build>" "<1511974366.223.1396424232427.JavaMail.jenkins@build>")" 



Affected mails are from different mailing lists. I see some affected mails in "_Inbox" folder where I told POP3 resource to tell Maildir resource to store mails to. There are still in file_db_data tough for now.




Expected Results:  
Mails are received. No errors.

merkaba:~> apt-show-versions | egrep "(kdepim|kmail|akonadi|^mysql)"  
akonadi-backend-mysql:all/experimental 1.12.0-1 uptodate
akonadi-server:amd64/experimental 1.12.0-1 uptodate
akonadiconsole:amd64/experimental 4:4.12.3-1 uptodate
kdepim:all/experimental 4:4.12.3-1 uptodate
kdepim-kresources:amd64/experimental 4:4.12.3-1 uptodate
kdepim-runtime:amd64/experimental 4:4.12.3-1 uptodate
kdepimlibs-kio-plugins:amd64/experimental 4:4.12.3-1 uptodate
kdepimlibs5-dev:amd64/experimental 4:4.12.3-1 uptodate
kmail:amd64/experimental 4:4.12.3-1 uptodate
libakonadi-calendar4:amd64/experimental 4:4.12.3-1 uptodate
libakonadi-contact4:amd64/experimental 4:4.12.3-1 uptodate
libakonadi-dev:amd64/experimental 1.12.0-1 uptodate
libakonadi-kabc4:amd64/experimental 4:4.12.3-1 uptodate
libakonadi-kcal4:amd64/experimental 4:4.12.3-1 uptodate
libakonadi-kde4:amd64/experimental 4:4.12.3-1 uptodate
libakonadi-kmime4:amd64/experimental 4:4.12.3-1 uptodate
libakonadi-notes4:amd64/experimental 4:4.12.3-1 uptodate
libakonadi-socialutils4:amd64/experimental 4:4.12.3-1 uptodate
libakonadi-xml4:amd64/experimental 4:4.12.3-1 uptodate
libakonadiprotocolinternals1:amd64/experimental 1.12.0-1 uptodate
libkdepim4:amd64/experimental 4:4.12.3-1 uptodate
libkdepimdbusinterfaces4:amd64/experimental 4:4.12.3-1 uptodate
mysql-client:all/sid 5.5.35+dfsg-2 uptodate
mysql-client-5.5:amd64/sid 5.5.35+dfsg-2 uptodate
mysql-common:all/sid 5.5.35+dfsg-2 uptodate
mysql-server-core-5.5:amd64/sid 5.5.35+dfsg-2 uptodate
Comment 1 Martin Steigerwald 2014-04-02 09:56:35 UTC 
This looses data! And worse yet: Due to the database upgrade I bet I cannot downgrade to Akonadi 1.11.0!

I moved a Toyota newsletter from "_Inbox" folder to "Mobil" folder. I disappeared from "_Inbox" but never appeared in "Mobil" folder:

martin@merkaba:~/.local/share/akonadi/file_db_data> grep "Toyoda" *
2419626_r0:Toyota Pr=E4sident Akio Toyoda folgt der neue AYGO - mit einem frischen Des=
2419626_r0:verbessert werden: Diesem Wahlspruch von Toyota Pr&auml;sident Akio Toyoda =

martin@merkaba:~/.local/share/akonadi/file_db_data> grep "Toyoda" *
martin@merkaba:~/.local/share/akonadi/file_db_data#1

martin@merkaba:~/.local/share/local-mail/.Lichtvoll.directory/Mobil> grep -ir "Toyoda" .
martin@merkaba:~/.local/share/local-mail/.Lichtvoll.directory/Mobil#1>

I did look in the folder above and below as well, in case I´d misdragged.
Comment 2 Martin Steigerwald 2014-04-02 10:03:44 UTC 
Sorry, I found the mail. I accidentally put them two folders below the "Mobil" folder. The mail is definately still there. Downgrading bug severity. But I will keep a watch on my mails, as the error message seems quite scary to me.
Comment 3 Daniel Vrátil 2014-04-02 10:10:51 UTC 
This issue has already been fixed in 1.12 branch. We will do 1.12.1 release before KDE 4.13 final is out.

commit 50495dcbad84799af23bd24dfbbbefd99bc32afb
Author: Dan Vrátil <dvratil@redhat.com>
Date:   Sat Mar 29 14:26:24 2014 +0100

    Don't emit flagsChanged notifications from AKAPPEND handler
    
    We use DataStore::appendItemsFlags() to append flags to the newly created
    item, but we don't want it to send out change notification, because it's
    called before we actually send out the itemAdded notification, which can
    confuse clients (and resources).
Comment 4 Martin Steigerwald 2014-04-02 11:21:41 UTC 
Daniel, just to make sure: So this is just debugging noise and has no serious consequences? Thanks, Martin
Comment 5 Daniel Vrátil 2014-04-02 11:29:09 UTC 
It's an actual error message, but it has no consequences. It just generates unnecessary traffic between clients and Akonadi.