Gnus development mailing list
 help / color / mirror / Atom feed
From: Peter Weiss <Peter.Weiss@class.de>
Cc: ding@gnus.org
Subject: Re: Problems using 5.8.3
Date: 11 Feb 2000 16:00:26 +0100	[thread overview]
Message-ID: <ycawvob2391.fsf@devil.class.de> (raw)
In-Reply-To: Simon Josefsson's message of "11 Feb 2000 15:25:23 +0100"

Hallo Simon

>>>>> On 11 Feb 2000 15:25:23 +0100, Simon Josefsson <jas@pdc.kth.se> said:

Simon> Peter Weiss <Peter.Weiss@class.de> writes:
>> o I'm unable to delete messages in nndraft folders (don't know how to do
>> this, usually killing and expiring it with 'C-k' and 'B
>> M-C-e' works)

Simon> `B DEL' on the article doesn't work?

Thanks, that's what I was looking for.

>> o Mail splitting doesn't work as it used to in v5.5,, when setting 
>> 
>> (setq nnimap-split-fancy nnmail-split-fancy)

Simon> Could you be more specific, what doesn't work?

No splitting is done, but I'm fiddling around with
nnimap-split-rule and nnmail-split-fancy as Kai suggested.

>> (setq mail-sources '((imap :server  "mailhost"
>> :user    "weiss"))
>> gnus-secondary-select-methods '((nnimap "mailhost")))

Simon> This looks wrong, it's usually nonsensical to have a IMAP mail-source
Simon> and a nnimap backend pointing at the same IMAP server.

Simon> If you want to use a IMAP mail-source, ie downloading all articles to
Simon> your local hard disk and deleting them on the server, you need a mail
Simon> backend to hold them, such as nnml. Also, having a nnimap server too
Simon> would serve little purpose.

Simon> OTOH if you want to remotely access IMAP mail with nnimap, you
Simon> shouldn't have a IMAP mail-source since it would remove all articles
Simon> from the server and store them locally in your nnml (or whatever)
Simon> backend.

Simon> I think this explains your first problem with your IMAP mailbox.

Thanks for the hints. I think the point is that I haven't understood the
differences between mail-sources and gnus-secondary-select-methods. If i've
got it right mail-sources is used to specify mail servers where mail is
downloaded to local disk space.

In this case how do I specify the nnml backend to hold the articles?

I'll have to read mail from different places: at work, from the customers
location or from my laptop. So I think leaving mail on the IMAP server is the
best idea.

In this case: how do I set up gnus? Using the nnimap-* variables or is it
sufficient to setup gnus-secondary-select-methods?

    Thanks so far -- Peter

-- 
Peter Weiss 

CLASS Firmengruppe           phone  +49 (0)8151 / 991 - 512
Moosstrasse 7                fax    +49 (0)8151 / 991 - 229
D-82319 Starnberg            mobil  ??
http://www.class.de          mailto:Peter.Weiss@Class.de



  reply	other threads:[~2000-02-11 15:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-11 11:05 Peter Weiss
2000-02-11 13:20 ` Kai Großjohann
2000-02-11 14:08 ` David S. Goldberg
2000-02-11 14:25   ` David S. Goldberg
2000-02-11 14:25 ` Simon Josefsson
2000-02-11 15:00   ` Peter Weiss [this message]
2000-02-11 15:29     ` Simon Josefsson
2000-02-11 16:27       ` Peter Weiss
2000-02-11 17:12         ` Simon Josefsson

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=ycawvob2391.fsf@devil.class.de \
    --to=peter.weiss@class.de \
    --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).