gnus-inews-mark-gcc-as-read has no effect for nnimap backend

gnus-inews-mark-gcc-as-read has no effect for nnimap backend

[Niklas Morberg]

Now that I finally got my Gcc to work properly (thanks Kai)
over imap there is one minor thing that is bugging me:
Gcc:ed items are marked as unread whereas I would prefer to
have them marked as read.

I thought that setting gnus-inews-mark-gcc-as-read to `t'
would do the trick (doc says any non-nil value will do), but
this does not help.

My Gcc value is:

Gcc: "nnimap+PROPER.IMAP.SERVER:Sent Items"

I've tried using a folder name without spaces and excluding
the quotes from the Gcc field, but the result is the same:
Sent messages are stored properly, but marked as unread.

Is there something I have misunderstood about the
gnus-inews-mark-gcc-as-read variable?

Niklas

Re: gnus-inews-mark-gcc-as-read has no effect for nnimap backend

[Kai Großjohann]

Niklas Morberg <niklas.morberg@axis.com> writes:

> Now that I finally got my Gcc to work properly (thanks Kai)
> over imap there is one minor thing that is bugging me:
> Gcc:ed items are marked as unread whereas I would prefer to
> have them marked as read.
>
> I thought that setting gnus-inews-mark-gcc-as-read to `t'
> would do the trick (doc says any non-nil value will do), but
> this does not help.

I think it should.  I used to use this variable, a long time ago, and
it worked that way.

Maybe it works for nnml groups but not for nnimap groups?  You can
manually put a Gcc header pointing to an nnml group in a message.

kai
-- 
Simplification good!  Oversimplification bad!  (Larry Wall)

Re: gnus-inews-mark-gcc-as-read has no effect for nnimap backend

[Niklas Morberg]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Maybe it works for nnml groups but not for nnimap groups?  You can
> manually put a Gcc header pointing to an nnml group in a message.

I tested with Gcc to an nnml group and it did mark the sent
message as read.

Oh well, I'll give edebug a shot and see if I can understand
what's going on -- I guess I need to learn lisp sooner or
later anyway :)

I'm off to `C-h i' world for a while now...

Niklas

Re: gnus-inews-mark-gcc-as-read has no effect for nnimap backend

[Simon Josefsson]

Niklas Morberg <niklas.morberg@axis.com> writes:

> Now that I finally got my Gcc to work properly (thanks Kai)
> over imap there is one minor thing that is bugging me:
> Gcc:ed items are marked as unread whereas I would prefer to
> have them marked as read.
>
> I thought that setting gnus-inews-mark-gcc-as-read to `t'
> would do the trick (doc says any non-nil value will do), but
> this does not help.
>
> My Gcc value is:
>
> Gcc: "nnimap+PROPER.IMAP.SERVER:Sent Items"
>
> I've tried using a folder name without spaces and excluding
> the quotes from the Gcc field, but the result is the same:
> Sent messages are stored properly, but marked as unread.
>
> Is there something I have misunderstood about the
> gnus-inews-mark-gcc-as-read variable?

No.  This works fine for me.  Can you frob `imap-log' and see if if
the flag is being set in the *imap-log* buffer when you send something?

Re: gnus-inews-mark-gcc-as-read has no effect for nnimap backend

[Niklas Morberg]

Simon Josefsson <jas@extundo.com> writes:

>> Is there something I have misunderstood about the
>> gnus-inews-mark-gcc-as-read variable?
>
> No. This works fine for me. Can you frob `imap-log' and
> see if if the flag is being set in the *imap-log* buffer
> when you send something?

I'm not quite sure what I'm looking for here, but I'm
guessing that these are the rows in the *imap-log* that
seems to be marking messages as read (these show up when
catching up messages in a group):

1151 UID STORE 1096:1098 +FLAGS (\Seen)

I see nothing like this when I'm sending messages, though...

Does this information help?

Niklas

Re: gnus-inews-mark-gcc-as-read has no effect for nnimap backend

[Simon Josefsson]

Niklas Morberg <niklas.morberg@axis.com> writes:

> Simon Josefsson <jas@extundo.com> writes:
>
>>> Is there something I have misunderstood about the
>>> gnus-inews-mark-gcc-as-read variable?
>>
>> No. This works fine for me. Can you frob `imap-log' and
>> see if if the flag is being set in the *imap-log* buffer
>> when you send something?
>
> I'm not quite sure what I'm looking for here, but I'm
> guessing that these are the rows in the *imap-log* that
> seems to be marking messages as read (these show up when
> catching up messages in a group):
>
> 1151 UID STORE 1096:1098 +FLAGS (\Seen)
>
> I see nothing like this when I'm sending messages, though...
>
> Does this information help?

You should see a similar line when sending messages. Maybe you can
edebug `gnus-group-mark-article-read' and see why it fails?  It should
be called from `gnus-inews-do-gcc'.

Hm.  Is the mailbox subscribed in Gnus?  E.g., is there a entry for it
in the group buffer?  My sent mail box is subscribed in Gnus, maybe it
is required.

Re: gnus-inews-mark-gcc-as-read has no effect for nnimap backend

[Niklas Morberg]

Simon Josefsson <jas@extundo.com> writes:

> You should see a similar line when sending messages. Maybe
> you can edebug `gnus-group-mark-article-read' and see why
> it fails? It should be called from `gnus-inews-do-gcc'.

I'll give it a shot. I don't know edebug yet, so this may
take a while...

> Hm. Is the mailbox subscribed in Gnus? E.g., is there a
> entry for it in the group buffer? My sent mail box is
> subscribed in Gnus, maybe it is required.

Yes, the mailbox is subscribed.

Niklas