From: Richard Riley <rileyrg@googlemail.com>
To: Leonidas Tsampros <ltsampros@upnet.gr>
Cc: ding@gnus.org
Subject: Re: mail-sources versus select-methods
Date: Thu, 31 Mar 2011 15:34:44 +0200 [thread overview]
Message-ID: <w839m3o1l7.fsf@news.eternal-september.org> (raw)
In-Reply-To: <87lizv5ro9.fsf@bifteki.lan> (Leonidas Tsampros's message of "Thu, 31 Mar 2011 16:46:14 +0300")
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?
>>
>
> I think I have the same question my self. However, mail-sources is just
> a 'digest' method.
What does digest mean in this instance? It can be all sorts including
pop3 etc.
>
> Quoting the docs:
>
> mail-sources is a variable defined in `mail-source.el'.
> Its value is ((directory :path "~/Mail" :suffix ""))
>
Thats not the docs but rather its current value.
See
(gnus) Mail Source Specifiers
in the gnus manual for more info.
But you probably meant that ;)
> What I do not understand is which mail backend (if multiple are defined)
> is going to consume these mails ?
Me neither.
My setting is
,----
| mail-sources is a variable defined in `mail-source.el'.
| Its value is
| ((file :path "/var/spool/mail/shamrock"))
`----
I access it via nnml :
(add-to-list 'gnus-secondary-select-methods
'(nnml "spool"
))
You would have no idea how long it took me to get to that ;)
I still dont really really understand the connection. Gnus does so much
under the cover and makes some really clever guesses at what you want.
I think because nnml is a mail backend, it just assumes its fed from
mail-sources. A reasonable enough assumption. Which then begs your question.
>
>> Whats the history here? Is it just historical? Or are the select
>> methods simply another layer provided by Gnus to smooth over the
>> message.el package?
>
> I think message.el is just the glue part where mails are composed and
> sent out. I'm not source it has anything to do with mail-sources.
>
> Select methods on the other hand is the backends from which you READ
> email. (that's how I understand it, please someone correct me if I'm
> wrong)
and other stuff such as nntp or google "pseudo" groups (which doesnt
work in HEAD btw (G W)).
next prev parent reply other threads:[~2011-03-31 13:34 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 [this message]
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
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=w839m3o1l7.fsf@news.eternal-september.org \
--to=rileyrg@googlemail.com \
--cc=ding@gnus.org \
--cc=ltsampros@upnet.gr \
/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).