From: Richard Riley <rileyrg@googlemail.com>
To: david.goldberg6@verizon.net (Dave Goldberg)
Cc: ding@gnus.org
Subject: Re: mail-sources versus select-methods
Date: Tue, 05 Apr 2011 12:52:32 +0200 [thread overview]
Message-ID: <9239lxm0lr.fsf@news.eternal-september.org> (raw)
In-Reply-To: <84oc4n5ysz.fsf@davestoy.home> (Dave Goldberg's message of "Sun, 03 Apr 2011 08:01:16 -0400")
david.goldberg6@verizon.net (Dave Goldberg) writes:
>> david.goldberg6@verizon.net (Dave Goldberg) writes:
>>>> Leonidas Tsampros <ltsampros@upnet.gr> writes:
>>>>> Richard Riley <rileyrg@googlemail.com> writes:
>>>>>> Undoubtedly an incredibly naive question but why would one use
>>>>>> mail-sources over select-methods?
>>>>>>
>>>
>>> One doesn't. They are two complementary things.
>>>
>> Hi,
>
>> But one can. And I'm not clear what is best.
>
> Apples and oranges. The two are complementary - there's no
> competition here.
But there is. You can achieve the same thing using both. My Q is what s
best and why.
>
>> One does not have to set up mail-sources. It can all be done in
>> secondary methods - e.g see the nnimap select-method in the manual for
>> gmail:-
>
> That's right, you don't need to set up mail-sources if you're not sucking mail
> into a local back end. If you are, then you need to tell Gnus from
> where to get
And you dont need to if you are either.
> it. That's the mail-source. The select method in that case would be the actual
> back end into which you're putting the mail.
>
>> (setq gnus-select-method
>> '(nnimap "imap.gmail.com"))
>
> Right so here you're talking IMAP, over the network, and interacting directly
> with the server. You don't need a mail-source because you're not pulling that
> mail into some local folder. If you did you might use nnml or similar as the
> back end (select method).
You can set up a mail-source with imap too. And a secondary select with
local backend too. I dont see where I ever "need" a mail-source which is
the core of my query really. Up until recently I never set mail-source
and am only doing so now because of issues I had with nnml as a
secondary select.
next prev parent reply other threads:[~2011-04-05 10:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 11:13 Richard Riley
2011-03-31 13:46 ` Leonidas Tsampros
2011-03-31 13:34 ` Richard Riley
2011-03-31 22:34 ` Dave Goldberg
2011-04-01 15:22 ` Richard Riley
2011-04-03 12:01 ` Dave Goldberg
2011-04-05 10:52 ` Richard Riley [this message]
2011-04-05 21:47 ` Dave Goldberg
2011-04-06 10:39 ` Richard Riley
2011-04-06 22:01 ` Dave Goldberg
2011-04-07 0:45 ` Richard Riley
2011-04-07 11:08 ` Dave Goldberg
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=9239lxm0lr.fsf@news.eternal-september.org \
--to=rileyrg@googlemail.com \
--cc=david.goldberg6@verizon.net \
--cc=ding@gnus.org \
/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).