Problem with archiving and nnimap

Problem with archiving and nnimap

[Niklas Morberg]

Hi,

I just upgraded to the latest CVS gnus after my vacation and
found something weird. I have:

(setq gnus-message-archive-group "\"nnimap\+my.mail.server:Sent Items\"")

which has always worked perfectly. (My IMAP server is MS
Exchange and it is nice to have the same folder for items
sent irregardless of the client I'm using.)

But not now.

Now gnus creates one folder called "Sent" and one called
"Items" and puts one copy of the sent messages in each
folder.

Any ideas why this is happening now? My previous gnus
version where this worked was ~2 months old.

Niklas

Re: Problem with archiving and nnimap

[Frank Schmitt]

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

> (setq gnus-message-archive-group "\"nnimap\+my.mail.server:Sent Items\"")
> Now gnus creates one folder called "Sent" and one called
> "Items" and puts one copy of the sent messages in each
> folder.

No idea why it used to work but doesn't now, but how about escaping the
blank with a backslash?

-- 
One Ring to rule them all, One Ring to find them,
One Ring to bring them all and in the darkness bind them
In the Land of Mordor where the Shadows lie.

Re: Problem with archiving and nnimap

[Niklas Morberg]

Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:

> No idea why it used to work but doesn't now, but how about
> escaping the blank with a backslash?

If you mean:

(setq gnus-message-archive-group "\"nnimap\+my.mail.server:Sent\ Items\"")

the result is pretty weird:

"\"nnimap+my.mail.server:SentItems\""

Hm. Maybe I should do without the quotes? Like so:

(setq gnus-message-archive-group "nnimap\+my.mail.server:Sent\ Items")

Nope. The result of that is:

"nnimap+my.mail.server:SentItems"

Or did you mean something else?

Niklas

Re: Problem with archiving and nnimap

[Simon Josefsson]

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

> Hi,
>
> I just upgraded to the latest CVS gnus after my vacation and
> found something weird. I have:
>
> (setq gnus-message-archive-group "\"nnimap\+my.mail.server:Sent Items\"")
>
> which has always worked perfectly. (My IMAP server is MS
> Exchange and it is nice to have the same folder for items
> sent irregardless of the client I'm using.)
>
> But not now.
>
> Now gnus creates one folder called "Sent" and one called
> "Items" and puts one copy of the sent messages in each
> folder.
>
> Any ideas why this is happening now? My previous gnus
> version where this worked was ~2 months old.

The GCC handling was modified recently.  That variable result in a GCC
header in the message buffer, does it not?  How does that header look
like?

Re: Problem with archiving and nnimap

[Niklas Morberg]

Simon Josefsson <jas@extundo.com> writes:

> That variable result in a GCC header in the message buffer,
> does it not? 

Sure.

> How does that header look like?

Gcc: ""nnimap+my.mail.server:Sent Items""

Niklas

Re: Problem with archiving and nnimap

[Kai Großjohann]

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

> Simon Josefsson <jas@extundo.com> writes:
>
>> That variable result in a GCC header in the message buffer,
>> does it not? 
>
> Sure.
>
>> How does that header look like?
>
> Gcc: ""nnimap+my.mail.server:Sent Items""

THat's one pair of double quotes too many.  Maybe the modification
adds its own double quotes automatically, so you can remove your
double quotes from the variable.

kai
-- 
~/.signature is: umop 3p!sdn    (Frank Nobis)

Re: Problem with archiving and nnimap

[Niklas Morberg]

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

>> Gcc: ""nnimap+my.mail.server:Sent Items""
>
> THat's one pair of double quotes too many.  Maybe the modification
> adds its own double quotes automatically, so you can remove your
> double quotes from the variable.

Ah, of course. I took the extra quotes out (which were
necessary previously). Now it works as it should.

Should this be documented somewhere? Maybe it already is?

Niklas

Re: Problem with archiving and nnimap

[Kai Großjohann]

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

> Should this be documented somewhere? Maybe it already is?

I think it's not documented, but it should be.

kai
-- 
~/.signature is: umop 3p!sdn    (Frank Nobis)

Re: Problem with archiving and nnimap

[Simon Josefsson]

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

> Niklas Morberg <niklas.morberg@axis.com> writes:
>
>> Simon Josefsson <jas@extundo.com> writes:
>>
>>> That variable result in a GCC header in the message buffer,
>>> does it not? 
>>
>> Sure.
>>
>>> How does that header look like?
>>
>> Gcc: ""nnimap+my.mail.server:Sent Items""
>
> THat's one pair of double quotes too many.  Maybe the modification
> adds its own double quotes automatically, so you can remove your
> double quotes from the variable.

Yup, I've improved the NEWS entry.  I hope this breach of backwards
compatibility is worth it, opinions?

** Group Carbon Copy (GCC) quoting

To support groups that contains SPC and other weird characters, groups
are quoted before they are placed in the Gcc: header.  This means
variables such as `gnus-message-archive-group' should no longer
contain quote characters to make groups containing SPC work.  Also, if
you are using the string "nnml:foo, nnml:bar" (indicating Gcc into two
groups) you must change it to return the list ("nnml:foo" "nnml:bar"),
otherwise the Gcc: line will be quoted incorrectly.  Note that
returning the string "nnml:foo, nnml:bar" was incorrect earlier, it
just didn't generate any problems since it was inserted directly.

Re: Problem with archiving and nnimap

[Niklas Morberg]

Simon Josefsson <jas@extundo.com> writes:

> Yup, I've improved the NEWS entry. I hope this breach of
> backwards compatibility is worth it, opinions?

I think the new functionality is way better than the old one. I
remember when I first tried to set the gnus-message-archive-group
variable; it was a pain (especially since nnmail-expiry-target
worked in a different way, now the two entries are similar).

Niklas