From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: dealing with separate accounts separately in gnus
Date: Mon, 08 Sep 2014 23:41:07 +0200 [thread overview]
Message-ID: <87k35d3i4s.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <87bnqp7sef.fsf@yun.yagibdah.de>
lee <lee@yun.yagibdah.de> writes:
> The server I already have is the mail-source:
> (setq mail-sources
> '((imap :server "jarl.yagibdah.de" :stream ssl)))
>
This is the "using IMAP as glorified POP"-way of using IMAP, which isn't
the usual mode.
(Although a perfectly fine thing to do, when you want your emails
locally.)
[...]
> The second account must not interfere in any way with this.
Just add nnimap servers to gnus-secondary-methods for the other
accounts, and you should be golden.
The mail from these accounts will stay on the IMAP-server, when you
configure Gnus like this.
[...]
> 'gnus-secondary-select-methods? IIRC that would interfere badly with
> what I have now.
How?
Best regards,
Adam
--
"Archbishop of anarchy" Adam Sjøgren
asjo@koldfront.dk
next prev parent reply other threads:[~2014-09-08 21:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 0:59 lee
2014-09-08 2:18 ` Eric Abrahamsen
2014-09-08 20:45 ` lee
2014-09-08 21:41 ` Adam Sjøgren [this message]
2014-11-10 0:06 ` lee
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=87k35d3i4s.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--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).