gnus-gcc-mark-as-read sometimes marks wrong message

gnus-gcc-mark-as-read sometimes marks wrong message

[Andrew J. Korty]

I use Gcc: INBOX on most of my outgoing mail, and I have
gnus-gcc-mark-as-read set.  Normally, it works as expected, but
sometimes my outgoing message does not get marked as read.  Instead,
an incoming, unread message gets marked as read.  My INBOX is an
nnimap group.

I haven't been able to reproduce this behavior at will, but I think it
happens when a message has arrived but hasn't been noticed by Gnus.
I'll try to reproduce it and post details, but for now I'm wondering
if anyone else has noticed this problem.

-- 
Andrew J. Korty, Principal Security Engineer, GCIA, GCFA
Office of the Vice President for Information Technology
Indiana University

Re: gnus-gcc-mark-as-read sometimes marks wrong message

[Simon Josefsson]

ajk@iu.edu (Andrew J. Korty) writes:

> I use Gcc: INBOX on most of my outgoing mail, and I have
> gnus-gcc-mark-as-read set.  Normally, it works as expected, but
> sometimes my outgoing message does not get marked as read.  Instead,
> an incoming, unread message gets marked as read.  My INBOX is an
> nnimap group.
>
> I haven't been able to reproduce this behavior at will, but I think it
> happens when a message has arrived but hasn't been noticed by Gnus.
> I'll try to reproduce it and post details, but for now I'm wondering
> if anyone else has noticed this problem.

No, but I suspect your suspicion may be correct.  Try GCC another
mailbox.  It should be possibly to fix this, I believe nnimap goes
through some trouble to get the proper UID of the article it appended,
and it is given to Gnus -- perhaps Gnus doesn't use it, but rather
takes the next larger integer in the group.  Hm. OTOH, the nnimap
implementation use the UIDPLUS extension for this, although I think it
contains a workaround for servers that doesn't support it, but perhaps
it is incomplete.

Re: gnus-gcc-mark-as-read sometimes marks wrong message

[Andrew J. Korty]

Simon Josefsson <jas@extundo.com> writes:

> ajk@iu.edu (Andrew J. Korty) writes:
>
>> I use Gcc: INBOX on most of my outgoing mail, and I have
>> gnus-gcc-mark-as-read set.  Normally, it works as expected, but
>> sometimes my outgoing message does not get marked as read.  Instead,
>> an incoming, unread message gets marked as read.  My INBOX is an
>> nnimap group.
>>
>> I haven't been able to reproduce this behavior at will, but I think it
>> happens when a message has arrived but hasn't been noticed by Gnus.
>> I'll try to reproduce it and post details, but for now I'm wondering
>> if anyone else has noticed this problem.
>
> No, but I suspect your suspicion may be correct.  Try GCC another
> mailbox.  It should be possibly to fix this, I believe nnimap goes
> through some trouble to get the proper UID of the article it appended,
> and it is given to Gnus -- perhaps Gnus doesn't use it, but rather
> takes the next larger integer in the group.  Hm. OTOH, the nnimap
> implementation use the UIDPLUS extension for this, although I think it
> contains a workaround for servers that doesn't support it, but perhaps
> it is incomplete.

I've just confirmed my suspicion.  If I send myself mail from outside
Gnus (I used /usr/bin/mail) and then immediately send mail to someone
else from inside Gnus, the first message automatically gets marked as
read.  *imap-debug* available on request.

-- 
Andrew J. Korty, Principal Security Engineer, GCIA, GCFA
Office of the Vice President for Information Technology
Indiana University

Re: gnus-gcc-mark-as-read sometimes marks wrong message

[Simon Josefsson]

ajk@iu.edu (Andrew J. Korty) writes:

> Simon Josefsson <jas@extundo.com> writes:
>
>> ajk@iu.edu (Andrew J. Korty) writes:
>>
>>> I use Gcc: INBOX on most of my outgoing mail, and I have
>>> gnus-gcc-mark-as-read set.  Normally, it works as expected, but
>>> sometimes my outgoing message does not get marked as read.  Instead,
>>> an incoming, unread message gets marked as read.  My INBOX is an
>>> nnimap group.
>>>
>>> I haven't been able to reproduce this behavior at will, but I think it
>>> happens when a message has arrived but hasn't been noticed by Gnus.
>>> I'll try to reproduce it and post details, but for now I'm wondering
>>> if anyone else has noticed this problem.
>>
>> No, but I suspect your suspicion may be correct.  Try GCC another
>> mailbox.  It should be possibly to fix this, I believe nnimap goes
>> through some trouble to get the proper UID of the article it appended,
>> and it is given to Gnus -- perhaps Gnus doesn't use it, but rather
>> takes the next larger integer in the group.  Hm. OTOH, the nnimap
>> implementation use the UIDPLUS extension for this, although I think it
>> contains a workaround for servers that doesn't support it, but perhaps
>> it is incomplete.
>
> I've just confirmed my suspicion.  If I send myself mail from outside
> Gnus (I used /usr/bin/mail) and then immediately send mail to someone
> else from inside Gnus, the first message automatically gets marked as
> read.  *imap-debug* available on request.

*imap-log* would be more useful.  Does your server support UIDPLUS?

Re: gnus-gcc-mark-as-read sometimes marks wrong message

[Andrew J. Korty]

Simon Josefsson <jas@extundo.com> writes:

>> I've just confirmed my suspicion.  If I send myself mail from outside
>> Gnus (I used /usr/bin/mail) and then immediately send mail to someone
>> else from inside Gnus, the first message automatically gets marked as
>> read.  *imap-debug* available on request.
>
> *imap-log* would be more useful.  Does your server support UIDPLUS?

Ah, looks like my IMAP server configuration was botched such that
UIDPLUS didn't show up in the CAPABILITY list (which I suppose means
it was disabled).  I'll do some more testing with it enabled.

-- 
Andrew J. Korty, Principal Security Engineer, GCIA, GCFA
Office of the Vice President for Information Technology
Indiana University