[kmail2] [Bug 347740] Encrypted message not detected as encrypted message

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=347740

--- Comment #13 from Rewarp  ---
Created attachment 99662
  --> https://bugs.kde.org/attachment.cgi?id=99662=edit
Message as plain text

By full message, I assume you mean the entire source view of the message. I
have included it in this attachment, and would also like to confirm that this
correspondence also uses Apple Mail, as mentioned in the bug report you
attached.

-- 
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 358501] New: New Message shortcut not working correctly

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=358501

Bug ID: 358501
   Summary: New Message shortcut not working correctly
   Product: kmail2
   Version: 5.1
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: commands and actions
  Assignee: kdepim-bugs@kde.org
  Reporter: rew...@thestrayworld.com

After successfully moving my KMail4 to KMail5, I discovered the Ctrl+N shortcut
threw up an error.

"The key sequence 'Ctrl+N' is ambiguous. Use 'Configure Shortcuts' from the 
'Settings' menu to solve the ambiguity. No action will be triggered."

The shortcut settings had not been changed from the default setting and no
other application was in conflict with it.

After assigning nothing to the custom shortcut to New Message, the actual
shortcut for New Message worked again. Attempts to reassign the shortcut back
to the default setting threw up this error:

"The 'Ctrl+N' key combination is already used by the New Message... action.
Please select a different one."

It is possible that remnants of the shortcuts in KMail4 are still being run,
hence resulting in a conflict.

Reproducible: Always

Steps to Reproduce:
1. Tries to use (default setting) Ctrl+N in KMail5 after upgrading from KMail4

Actual Results:  
Error message given.

Expected Results:  
New message window should have launched.

The computer is running openSUSE Tumbleweed with subscriptions to the
Frameworks, Applications, and Extras repositories taking priority over stock
repositories.

-- 
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 347740] Encrypted message not detected as encrypted message

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=347740

--- Comment #7 from Rewarp  ---
I am now running KMail 5.1.2, and the workaround method no longer works.

I am back to downloading the message separately before I am able to decrypt the
message.

Here's a screenshot as proof.

https://imgur.com/sY3XrQl

-- 
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

[akregator] [Bug 360448] New: Visual artefact appearing in Akregator

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360448

Bug ID: 360448
   Summary: Visual artefact appearing in Akregator
   Product: akregator
   Version: unspecified
  Platform: Other
   URL: http://imgur.com/OWAZySV
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: kdepim-bugs@kde.org
  Reporter: rew...@thestrayworld.com

A short period after I launch Kontact, visual artefacts with seemingly random
snippets of whatever has been on the screen previously will cover up a portion
of Akregator in Kontact.

A screenshot illustrating the problem is included.

Reproducible: Always

Steps to Reproduce:
1. Launch Kontact
2. Switch to Akregator

Actual Results:  
Visual artifact blocking part of the screen.

Expected Results:  
Visual artefact should not be there.

Problem disappears after restarting Kontact in the same session. But will
reoccur.

-- 
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 347740] Encrypted message not detected as encrypted message

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=347740

--- Comment #10 from Rewarp  ---
(In reply to tomaggio from comment #8)
> Hi;
> With kmail 5.1.3 it works again. So  for me, this Bug is solved.

Thanks. I will wait and see if it works on 5.1.3.

-- 
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 345992] Keyboard shortcut assigned to "archive mail" works once, unconfigures itself

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=345992

Rewarp  changed:

   What|Removed |Added

 CC||rew...@thestrayworld.com

--- Comment #4 from Rewarp  ---
Since this is a keyboard shortcut issue, I am adding my own custom shortcut
problem here as well.
 I have assigned the "Right" and "Left" key to Next and Previous message
respectively.

For some odd reason, The shortcut for "Focus on Next Message" is not the
default Alt+Right, but is Right. This conflicts with my custom key for "Next
Message".

After changing "Focus on Next Message" to the default Alt+Right, the Right key
works once to move to the next message, but on the second tap is suddenly
reassigned to "Focus on Next Message again"

Steps to reproduce:

1. Reassign shortcut for "Focus on Next Message" to default Alt+Right
2. Assign shortcut for "Next Message" to Right.
3. Press Right.

Expected:

The next email message should be selected.

Instead:

1. The next message is selected.
2. The custom shortcut fails and is reassigned to "Focus on Next Message".

-- 
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 347740] Encrypted message not detected as encrypted message

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=347740

--- Comment #11 from Rewarp  ---
I have confirmed that messages sent with the attachment above are still not
being decrypted. I am at a loss as what is wrong here.

-- 
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 350059] Filters in kmail no longer functional

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=350059

Rewarp  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|UNCONFIRMED |RESOLVED

--- Comment #7 from Rewarp  ---
Since this issue is no longer occurring, I am closing this report. Thanks for
all the help!

-- 
You are receiving this mail because:
You are the assignee for the bug.

[akregator] [Bug 360448] Visual artefact appearing in Akregator

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=360448

Rewarp  changed:

   What|Removed |Added

 Status|CONFIRMED   |RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from Rewarp  ---
I don't see this issue anymore in Kontact 5.3, so I presume it has been
properly fixed.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[kmail2] [Bug 339360] offline accounts should try to reconnect automatically

[Rewarp via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=339360

Rewarp  changed:

   What|Removed |Added

 CC||rew...@thestrayworld.com

--- Comment #2 from Rewarp  ---
I am experiencing this error with KMail 5.3.0. nd in prior versions.

When I login, I have a cryptographic key setup to unlock kwallet, which means
there is a delay in the credentials for signing onto the available networks.

This delay means autoconnect usually fails unless I unlock my wallet fast
enough. The failure to connect stops KMail from retrieving new messages. After
connecting, KMail fails to detect the change in the network status, and will
remain so until I manually restart the IMAP connection.

Prior to noticing this issue, I went for days without receiving or responding
to emails, simply because I was trying to connect to networks requiring
authentication.

-- 
You are receiving this mail because:
You are the assignee for the bug.