Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Teemu Likonen <tlikonen@iki.fi>
To: info-gnus-english@gnu.org
Subject: Re: Mail-splitting confusion
Date: Wed, 14 Oct 2015 22:20:00 +0300	[thread overview]
Message-ID: <87lhb5jlzz.fsf@mithlond.arda> (raw)
In-Reply-To: <87k2qpldbe.fsf@mithlond.arda> (Teemu Likonen's message of "Wed,  14 Oct 2015 17:44:37 +0300")


[-- Attachment #1.1: Type: text/plain, Size: 399 bytes --]

Teemu Likonen [2015-10-14 17:44:37+03] wrote:

> I'm confused about Gnus's mail-splitting back-ends. How does Gnus
> decide which back-end to use?

I think I got it. Mail back-ends have get-new-mail variable and if it's
non-nil then that back-end fetches mail from mail-sources and possibly
splits mail to different groups within that back-end. I think this
should be made clear in the Gnus manual.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]



      reply	other threads:[~2015-10-14 19:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 14:44 Teemu Likonen
2015-10-14 19:20 ` Teemu Likonen [this message]

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=87lhb5jlzz.fsf@mithlond.arda \
    --to=tlikonen@iki.fi \
    --cc=info-gnus-english@gnu.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).