Bug 3687 - Missing new addresses
Summary: Missing new addresses
Status: NEW
Alias: None
Product: Claws Mail
Classification: Unclassified
Component: Plugins/AddressKeeper (show other bugs)
Version: 3.14.0
Hardware: PC Linux
: P3 trivial
Assignee: users
URL:
Depends on:
Blocks:
 
Reported: 2016-09-08 12:28 CEST by Ralf Mardorf
Modified: 2018-06-19 16:20 CEST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ralf Mardorf 2016-09-08 12:28:07 CEST
Hi,

sometimes new addresses are only shown in the address book after
restarting Claws.

I noticed it for versions <= 3.14. Currently for 3.14.0-2-ge48b73.

Regards,
Ralf
Comment 1 Andrej Kacian 2016-09-08 12:34:18 CEST
What do you consider "new address" in this context? Address added in past X minutes? Address added using some mechanism/feature during current session? How exactly does one reproduce what you're describing?
Comment 2 Andrej Kacian 2016-09-08 12:46:58 CEST
Neve(In reply to comment #1)
> What do you consider "new address" in this context? Address added in past X
> minutes? Address added using some mechanism/feature during current session?

Nevermind, I haven't noticed that this is for the Address Keeper plugin. Sorry. :)

I still would like to know how exactly to reproduce this. I tried several times, with various "kinds" of e-mail addresses, but they seem to always be added just fine.
Comment 3 Ralf Mardorf 2016-09-08 13:13:59 CEST
This happens randomly. Today after closing Claws and reopening it, a new mailing list address was shown. I don't remember if always a mailing list is involved. I don't think so, but it at least happens very often for mailing list addresses. A mail was send "To:" a mailing list that isn't available in the address book. Perhaps an address that once was already in the address book, but then deleted, because I seldom use this mailing list. After the mail was sent, it wasn't shown in the address book, but it was displayed, as soon as Claws was restarted.

I never reported it as a bug, since I consider the severity _very_ trivial.
Comment 4 Ricardo Mones 2018-06-19 16:20:56 CEST
Reported also as https://bugs.debian.org/901785.