[kleopatra] [Bug 358392] Key could not be certified. Certificate expired, but NOT!

2016-03-04 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=358392

--- Comment #10 from rigel3925-w...@yahoo.com ---
There seems to be a subkey in the key I created for myself; however, the "good
through date" is the same as the main key. They are both good forever with no
expiration date. 

I couldn't decide when to expire my key so I selected forever. Is that
something not usually done? Well, that's what I did it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Akonadi] [Bug 360097] New: Getting 401 error when synchronizing Baikal resource after upgrading to baikal 0.3.5

2016-03-04 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360097

Bug ID: 360097
   Summary: Getting 401 error when synchronizing Baikal resource
after upgrading to baikal 0.3.5
   Product: Akonadi
   Version: unspecified
  Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
  Severity: major
  Priority: NOR
 Component: DAV Resource
  Assignee: kdepim-bugs@kde.org
  Reporter: martc...@gmx.net

My basic Baikal setup seems to work. I'm able to use the web interface and to
synchronize from Android using the DavDroid app and from Thunderbird using SOGO
and Lightning.

As the summary already says, I'm unable to synchronize with Akonadi using the
latest release of Baikal (0.3.5). However, with the previous version of Baikal
(0.2.7) everything worked fine. I didn't test the 0.3.x Baikal versions before
0.3.5. I'm always getting a 401 error when synchronizing.

As you can see from the log I supplied under additional information Akonadi
never tries to send the password, so it is no wonder that always 401 is
returned.

Reproducible: Always

Steps to Reproduce:
1. Create a new CardDAV or CalDAV resource using the manual setup.
2. Enter credentials and server URL.
3. Checking out the collections from the server.

Actual Results:  
An error message is shown (HTTP error 401).

Expected Results:  
Calendar/address book is shown and can be added.

My config:
- Baikal 0.3.5, nginx-custom 1.8.1 from the AUR
- Akonadi version: 15.12.2 and 15.12.1 from the official Arch Linux repository
(Both produce the same error.)
- tested protocols: HTTP, HTTPS (Both produce the same error.)
- tested authentication methods: Basic, Digest (Both produce the same error.)
But as already mentioned, my Baikal setup works with other clients.

Here's the traffic captured with Wireshark (I removed SSIDs):
PROPFIND /baikal/cal.php/ HTTP/1.1
Host: martchus.no-ip.biz
Connection: keep-alive
User-Agent: Mozilla/5.0 (X11; Linux x86_64) KHTML/5.19.0 (like Gecko)
Konqueror/5.19
Pragma: no-cache
Cache-control: no-cache
Accept: text/html, text/*;q=0.9, image/jpeg;q=0.9, image/png;q=0.9,
image/*;q=0.9, */*;q=0.8
Accept-Encoding: gzip, deflate, x-gzip, x-deflate
Accept-Charset: utf-8,*;q=0.5
Accept-Language: de-DE,en;q=0.9
Content-Type: text/xml
Depth: 0
Content-Length: 239



 
  
  
  
 


HTTP/1.1 401 Unauthorized
Server: nginx
Date: Fri, 04 Mar 2016 21:16:17 GMT
Content-Type: application/xml; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
X-Powered-By: PHP/7.0.3
Set-Cookie: PHPSESSID=---; path=/; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
WWW-Authenticate: Digest
realm="BaikalDAV",qop="auth",nonce="56d9fb21ed880",opaque="d66d5f0524036afcb61420e358f990ce"

# another request

PROPFIND /baikal/cal.php/ HTTP/1.1
Host: martchus.no-ip.biz
Connection: keep-alive
User-Agent: Mozilla/5.0 (X11; Linux x86_64) KHTML/5.19.0 (like Gecko)
Konqueror/5.19
Pragma: no-cache
Cache-control: no-cache
Accept: text/html, text/*;q=0.9, image/jpeg;q=0.9, image/png;q=0.9,
image/*;q=0.9, */*;q=0.8
Accept-Encoding: gzip, deflate, x-gzip, x-deflate
Accept-Charset: utf-8,*;q=0.5
Accept-Language: de-DE,en;q=0.9
Content-Type: text/xml
Depth: 0
Content-Length: 239



 
  
  
  
 


HTTP/1.1 401 Unauthorized
Server: nginx
Date: Fri, 04 Mar 2016 21:16:20 GMT
Content-Type: application/xml; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
X-Powered-By: PHP/7.0.3
Set-Cookie: PHPSESSID=---; path=/; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
WWW-Authenticate: Digest
realm="BaikalDAV",qop="auth",nonce="56d9fb244485e",opaque="d66d5f0524036afcb61420e358f990ce"

# yet another request

PROPFIND /baikal/cal.php/ HTTP/1.1
Host: martchus.no-ip.biz
Connection: keep-alive
User-Agent: Mozilla/5.0 (X11; Linux x86_64) KHTML/5.19.0 (like Gecko)
Konqueror/5.19
Pragma: no-cache
Cache-control: no-cache
Accept: text/html, text/*;q=0.9, image/jpeg;q=0.9, image/png;q=0.9,
image/*;q=0.9, */*;q=0.8
Accept-Encoding: gzip, deflate, x-gzip, x-deflate
Accept-Charset: utf-8,*;q=0.5
Accept-Language: de-DE,en;q=0.9
Content-Type: text/xml
Depth: 1
Content-Length: 392



 
  
  
  http://apple.com/ns/ical/"/>
  
  
  http://calendarserver.org/ns/"/>
 


HTTP/1.1 401 Unauthorized
Server: nginx
Date: Fri, 04 Mar 2016 21:16:20 GMT
Content-Type: application/xml; charset=utf-8
Transfer-Encoding: chunked
Connection: keep-alive
X-Powered-By: PHP/7.0.3
Set-Cookie: PHPSESSID=---; path=/; HttpOnly
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate
Pragma: no-cache
WWW-Authenticate: Digest
realm="BaikalDAV",qop="auth",nonce="56d9fb24544c7",opaque="d66d5f0524036afcb61420e358f990ce"

# the problem also occurs when using basic auth:

PROPFIND /baikal/cal.php/ HTTP/1.1
Host: martchus.no-ip.biz
Connection: 

[kmail2] [Bug 360071] New: Setting separate dictionary for different identity doesn't "stick"

2016-03-04 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360071

Bug ID: 360071
   Summary: Setting separate dictionary for different identity
doesn't "stick"
   Product: kmail2
   Version: 4.14.10
  Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: config dialog
  Assignee: kdepim-bugs@kde.org
  Reporter: d...@newtech.fi

Trying to change the Dictionary language (tab Advanced in Identity setting)
different for the different identities doesn't work. The dialog will accept the
new value, but when you allpy it - Step out of the settings and get back in it
is back as it was before setting it.

Reproducible: Always

Steps to Reproduce:
1.Go to Identity -> Advanced
2.Set something else as Dictionary 
3.Jump ot of settings
4. Get back in and the original value will be back

Actual Results:  
Dictionary for identity not changed

Expected Results:  
Dictionary will be permanently set to new value for the identity

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[kmail2] [Bug 359964] "Kmailleaks", or what to improve to make Kmail more privacy friendly.

2016-03-04 Thread eemantsal via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359964

--- Comment #7 from eemantsal  ---
Sorry if I'm being too insistent, but it has come to mind that for that
hypothetical Message-ID suffix could be a per-account or per-identity setting
that, by default, would use the mail sender's domain, so, if someone uses a
Protonmail, Gmail, whatever account, Kmail may set as prefix protonmail.com,
gmail.com, and so on; all without any need for the user to touch anything, and
not adding any extra info ince the mail sender's domain is already known in the
From header. i think it'd be an elegant and efficacious solution. What do you
think?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[ktnef] [Bug 360054] File collisions between ktnef and kdepim/ktnef

2016-03-04 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360054

andreas.sturmlech...@gmail.com changed:

   What|Removed |Added

 CC||andreas.sturmlechner@gmail.
   ||com

--- Comment #2 from andreas.sturmlech...@gmail.com ---
As these are live packages, when did you last rebuild kde-apps/ktnef-:5?

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[ktnef] [Bug 360054] File collisions between ktnef and kdepim/ktnef

2016-03-04 Thread Elias Probst via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360054

Elias Probst  changed:

   What|Removed |Added

Summary|File collisions between kt  |File collisions between
   ||ktnef and kdepim/ktnef

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[Akonadi] [Bug 354056] Deleted emails stay, but greyed out

2016-03-04 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=354056

--- Comment #25 from naworsk...@gmail.com ---
(In reply to naworski98 from comment #24)

> Speaking about tags: When the bug started to affect me, I was able to make
> the undead mails appear as "normal" in by changing the status from unread to
> read. So I could delete them (again), but after refreshing it just
> reappeared with an additional undead mail. Changing the Status is now (kmail
> 5.0.3, akonadi 5.0.51) not possible anymore.

O.k. an update for this behaviour: "reanimating" the "undead" mails by changing
the read/unread status works as long there is at least one normal ("living")
mail present in the directory. However, the "reanimated" mails still just
generates additional "undead" copys of itself by moving/deleting them.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[kmail2] [Bug 359964] "Kmailleaks", or what to improve to make Kmail more privacy friendly.

2016-03-04 Thread eemantsal via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359964

--- Comment #6 from eemantsal  ---
I was yesterday having a look to all those options and thought that perhaps
this user Message-ID issue was related to this Headers tab you mention, but I
didn't understand what a "suffix" could be -of course I know what it means in
lingüistics, but remember that most of us aren't informatics nor are really
accustomed to informatic terminology- and didn't pay much attention to it. Now
I see that effectively that was the key. Thank you.
Nevertheless, probably a little tooltip reading something like «This is the
identifier that will be shown in the Message-ID header» when hovering the
pointer would sensitively improve the user friendliness.
Also, probably a suffix, as common and widespread as possible, should be preset
by default, so the average user doesn't have to search on the Internet how to
do it. Don't you agree?

Anyway, then there's only the user agent leak. All in all Kmail is not such a
"blabbermouth", hehe, but see how an average user like me has had to ask to
you, developers and try a couple of things that most users aren't willing to
try. I sincerely believe this is way afar from user friendly. If you allow me
the suggestions, please add a default preset, and consider an option to see
truly sent headers, not excluding the actual option to see all that extra info
that Laurent said in comment 4, but adding one more perhaps in the View/Headers
menu, «Real headers», or whatever you think is more descriptive and accurate.

Again, all this surely sounds obvious and silly to you, but, once again,
remember that the majority of users don't know/want to have to read and write
in forums nor fiddle and dig amoung not so clear options, tabs, menues, etc. A
couple of simple things would make users' life way easier.


Regards, and I think that once the user agent issue is solved this bug report
can be closed.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[kmail2] [Bug 339887] KMail shows pictures in html messages as attachments.

2016-03-04 Thread via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=339887

lampus.la...@gmail.com changed:

   What|Removed |Added

 CC||lampus.la...@gmail.com

--- Comment #17 from lampus.la...@gmail.com ---
Same problem.
ArchLinux

KMail 15.12
KF5 5.19
Qt5  5.5.1

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs


[ktnef] [Bug 360054] File collisions between kt

2016-03-04 Thread Laurent Montel via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=360054

Laurent Montel  changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED
 CC||mon...@kde.org

--- Comment #1 from Laurent Montel  ---
??
I don't know what gentoo does but kdepim/ktnef doesn't provide theses file.
Totally invalid this bug report

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs