From: Rainer@krugs.de (Rainer M. Krug)
To: wgreenhouse@riseup.net (W. Greenhouse)
Cc: info-gnus-english@gnu.org
Subject: Re: How to deal with "Archive" and "delete" in gmail?
Date: Fri, 05 Apr 2013 10:46:44 +0200 [thread overview]
Message-ID: <87k3oh5pqj.fsf@krugs.de> (raw)
In-Reply-To: <874nfmgy53.fsf@riseup.net> (W. Greenhouse's message of "Thu, 04 Apr 2013 14:37:28 +0000")
wgreenhouse@riseup.net (W. Greenhouse) writes:
> Hi Rainer,
>
> Rainer@krugs.de (Rainer M. Krug) writes:
>
>> This looks like a good option. But I am still struggling with the regexp
>> for groups (maybe because I do not understand the naming of groups?).
>>
>> So I have my gmail account defined as primary source:
>>
>> (setq gnus-select-method
>> '(nnimap "gmail"
>> (nnimap-address "imap.gmail.com")
>> (nnimap-server-port 993)
>> (nnimap-stream ssl)
>> (nnimap-authinfo-file "~/.authinfo.gpg")
>> (nnmail-expiry-target "[Gmail]/Bin")
>> (nnmail-expiry-wait 2)))
>>
>> and I would like to set the default move target for all groups in this
>> primary source to "[gmail]/All Mail":
>>
>> (setq gnus-move-split-methods
>> '(("nnimap.*" "[gmail]/All Mail")))
>>
>> but it is not working.
>>
>> I assume it is something wrong with the regexp "nnimap.*" - my reasoning
>> was: match all groups which start with nnimap.
>>
>> This regexp also concerns other configuratios which are not working...
>>
>> Any suggestions?
>>
>> Thanks,
>>
>> Rainer
>
> From the config you posted here, it looks like all your Gmail mailboxes
> are so-called "native groups." "Native groups" are those which use
> `gnus-select-method' as opposed to one of the secondary select methods
> or a "foreign" server. All this "native" vs. "foreign" is perhaps all
> making Gnus sound rather ethnocentric, but the gist of it is that
> "native groups" do not have the server type prepended to their names.
> That is, because Gmail is your primary select method, Gmail groups on
> your system simply have names like "INBOX" or "[Gmail]/Important", and
> not names like "nnimap+imap.gmail.com:INBOX". So that's why your
> regexes went astray.
Ok - that is very useful information and it solves one more problem I
had - so brilliant info - Thanks!
>
> `gnus-move-split-methods' and `gnus-split-methods' and similar such
> rules in Gnus are applied such that more specific rules can override
> more general ones. If you are primarily using Gnus as a Gmail client,
> it might make a lot of sense to have the most general rule direct any
> re-filed message to the Gmail archive, and then make exceptions to this
> later on. So, perhaps try this:
>
> (setq gnus-move-split-methods
> '((".*" "[Gmail]/All Mail")))
Great - looks perfect. That's what I am using and it works like a charm.
Thanks a lot,
Rainer
>
> Good luck!
> Best,
> Will
<#secure method=pgpmime mode=sign>
--
Rainer M. Krug, PhD (Conservation Ecology, SUN), MSc (Conservation Biology, UCT), Dipl. Phys. (Germany)
Centre of Excellence for Invasion Biology
Stellenbosch University
South Africa
Tel : +33 - (0)9 53 10 27 44
Cell: +33 - (0)6 85 62 59 98
Fax : +33 - (0)9 58 10 27 44
Fax (D): +49 - (0)3 21 21 25 22 44
email: Rainer@krugs.de
Skype: RMkrug
next prev parent reply other threads:[~2013-04-05 8:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 11:04 Rainer M. Krug
2013-04-03 14:57 ` W. Greenhouse
2013-04-04 8:09 ` Rainer M. Krug
2013-04-04 14:37 ` W. Greenhouse
2013-04-05 8:46 ` Rainer M. Krug [this message]
[not found] <mailman.23374.1364987079.855.info-gnus-english@gnu.org>
2013-04-03 14:33 ` Cor
2013-04-04 8:12 ` Rainer M. Krug
[not found] ` <mailman.23488.1365063160.855.info-gnus-english@gnu.org>
2013-04-04 11:52 ` Cor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k3oh5pqj.fsf@krugs.de \
--to=rainer@krugs.de \
--cc=info-gnus-english@gnu.org \
--cc=wgreenhouse@riseup.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).