[Users] [Bug 3701] New: Inconsistent mailbox updates
noreply at thewildbeast.co.uk
noreply at thewildbeast.co.uk
Wed Sep 28 23:10:57 CEST 2016
http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3701
Bug ID: 3701
Summary: Inconsistent mailbox updates
Classification: Unclassified
Product: Claws Mail (Windows)
Version: 3.14.0
Hardware: PC
OS: Windows 7
Status: NEW
Severity: major
Priority: P3
Component: default
Assignee: users at lists.claws-mail.org
Reporter: mrbass21 at gmail.com
I'm new to Claws, so maybe this is an email configuration problem. if someone
can offer a reason why I'm getting this behavior, all the better, but if not I
wanted to file the bug. I've marked this ticket as "Major" assuming it is a
bug.
I have two accounts added to Claws. A gmail account and my work account. Both
are IMAPv4. I've enabled automatic checks for every minute. I sent myself a
message from the gmail web interface, and Claws never finds it with automatic
updates. I even went to a dentist appointment and came back (around 2 hours)
and it still had not found any new mail (despite the web UI saying I have 15
unread messages). I clicked Get Mail and it didn't find it. I clicked off the
inbox into drafts, then re-selected inbox, now it finds that I have 15 unread
emails (including the test email I sent 2 hours ago).
Further, I don't get any notifications. I read in other bug reports that the
notification plugin only looks for mail flagged as "New", and these emails are
all flagged as "Unread", but not "New".
If there is no option to be alerted via the notification plugin for unread
emails, I'd appreciate a definition of the distinction between "Unread" and
"New". I'm at least somewhat technically inclined, but this is confusing to
general users and gives the impression that notifications just doesn't work.
Despite sending myself test emails, and others sending me emails, I've never
received a notification from Claws. Sometimes the UI will find an unread email,
most of the time I have to manually check.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Users
mailing list