From: phillip.lord@russet.org.uk
To: Phillip Lord <phillip.lord@russet.org.uk>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>, help-gnu-emacs@gnu.org
Subject: Re: nnimap splitting
Date: Thu, 10 Dec 2020 19:22:13 +0000 [thread overview]
Message-ID: <9014e1d022c223fb63f7d503f8b298ec@russet.org.uk> (raw)
In-Reply-To: <1d30cad3346c3d955911198146a18148@russet.org.uk>
On 2020-12-10 18:58, phillip.lord@russet.org.uk wrote:
> On 2020-12-10 18:36, Pankaj Jangid wrote:
>> Phillip Lord <phillip.lord@russet.org.uk> writes:
>>
> I think
> I am looking in the wrong place and my configuration here is not the
> issue at all. I have no idea, unfortunately, what the issue is. If
> this is supposed to work in Gnus, I think, it is getting all the
> server information from somehwere else. NOt sure where!
And this turns out to be the problem. I tried changing
secondary-select-methods to this:
(setq gnus-secondary-select-methods
'(
(nnimap "localhost"
;;(nnimap-address "localhost")
;;(nnimap-server-port 143)
(nnimap-address "i-dont-exist")
(nnimap-server-port 'random-nonsense)
;; [...]
(nnimap-inbox "INBOX")
(nnimap-split-methods
(("temp" "^Subject: split-into-temp")
("INBOX" "")))
(nnml ""
(nnir-search-engine notmuch))))
And Gnus still works, still looks up the nnimap back end, still access
the email
despite the clearly incorrect address and server port. It doesn't appear
to be using
the information here at all. Confusing as it is using the nnml
information.
I am now officially very confused.
Phil
next prev parent reply other threads:[~2020-12-10 19:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 22:38 nnimap splitting Phillip Lord
2020-12-09 23:26 ` Eric Abrahamsen
2020-12-10 10:26 ` Phillip Lord
2020-12-10 17:41 ` Eric Abrahamsen
2020-12-10 18:48 ` phillip.lord
2020-12-10 18:36 ` Pankaj Jangid
2020-12-10 18:58 ` phillip.lord
2020-12-10 19:22 ` phillip.lord [this message]
2020-12-11 0:07 ` Eric Abrahamsen
2020-12-11 0:09 ` Eric Abrahamsen
2020-12-11 12:24 ` Leo Butler
2020-12-11 21:37 ` phillip.lord
2020-12-11 22:04 ` Leo Butler
2020-12-11 5:13 ` Pankaj Jangid
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9014e1d022c223fb63f7d503f8b298ec@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=eric@ericabrahamsen.net \
--cc=help-gnu-emacs@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 read-only IMAP folder(s) and NNTP newsgroup(s).