Bug 263829

Summary: first connect with existing imap account yields numerous "Unable to create flag" errors
Product: [Applications] kmail2 Reporter: Robert Schöftner <rmu>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED NOT A BUG    
Severity: normal CC: carrai.marco, tokoe
Priority: NOR    
Version: 2.0.89   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Robert Schöftner 2011-01-21 09:51:51 UTC 
Version:           2.0.89 (using KDE 4.5.95) 
OS:                Linux

akonadi-backend: postgresql 8.4
imap-server: cyrus-imapd 2.2

I believe that earlier version of kmail reported some SQL-Error.

Reproducible: Always

Steps to Reproduce:
connect to ny existing imap e-mail account, contains ca. 10gb of e-mails

Actual Results:  
hundreds/thousands of error notifications

Expected Results:  
no error

makes further testing of kmail2 impossible.
Comment 1 Tobias Koenig 2011-06-04 13:43:18 UTC 
Hej,

is this still reproducible with the most recent version of KMail2?

Ciao,
Tobias
Comment 2 Marco Carrai 2011-07-16 11:22:32 UTC 
I am experiencing the same problem with a pop3\smtp account while sending an email. I got: 
could not send the message: Could not save result into the element. Unknown error. (NO Unable to create flag )
 I can receive mail from pop3 without problem ( could not test imap because i don't have an imap account )
I am using kmail : 2.1.96
Postgresql : 9.0.3
Opensuse 11.4 x64

The interesting thing is that using mysql as backend solves the issue. It seems a problem related to a query which saves the sent message!
Comment 3 Marco Carrai 2011-07-26 19:34:48 UTC 
I found a workaround:
http://dbaspot.com/postgresql/251026-many-warning-pg-logs-nonstandard-use-string-literalat-character.html

Set in postgresql.conf : standard_conforming_strings = on

Now it works. it seems to be a new option that will be available on postgresql. However i am still not able to understand if it's better to make a better query or activate this option. It seems that older version of postgresql ( prior to 9 ), this option is not present, and the problem should be not present!
Comment 4 Christophe Marin 2011-07-27 08:59:53 UTC 
> It seems that older version of postgresql ( prior to 9 ), this option is not present

This setting was already there in 8.2 (and so was the message about this option being enabled by default in a future release)

The real issue here is that you use an external server (which is not what Akonadi does by default) but didn't configure it (which Akonadi cannot change the server settings when using an external one)
Comment 5 Marco Carrai 2011-07-27 12:26:07 UTC 
What do you mean as external server? a remote server ( not in the same host ).
Comment 6 Christophe Marin 2011-07-27 19:45:51 UTC 
external server as in 'you changed the default configuration' (in that case, the Akonadi server starts its own postgres instance and enables standard_conforming_strings)
Comment 7 Marco Carrai 2011-07-28 17:22:10 UTC 
Ah okay!