Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Brett Viren <brett.viren@gmail.com>
To: prad <prad@towardsfreedom.com>
Cc: info-gnus-english@gnu.org
Subject: Re: my vs maildir
Date: Sat, 1 Jan 2011 11:24:34 -0500	[thread overview]
Message-ID: <AANLkTimkCNCE4y3MLhBcCum0pVBS8UJX0tODO-UMKuJL@mail.gmail.com> (raw)
In-Reply-To: <87wrmpnfvm.fsf@towardsfreedom.com>

Two more things to consider:

On Sat, Jan 1, 2011 at 4:16 AM, prad <prad@towardsfreedom.com> wrote:

> (setq gnus-parameters
>      '(("^nnimap\\+Mail:INBOX"
>         (gcc-self . t))))
>
> this puts the sent mail right into my maildir ~/Mail/inbox/new something
> i couldn't figure out how to do with things like nnmaildir (nnml gives
> the wrong format of course).

Since I use procmail my INBOX is always pre-drained.  So, instead I use:

        ("myserv:.*" (gcc-self . t))

where "myserv" is the name given to nnimap when setting
gnus-secondary-select-methods.
With this, when I send mail while inside any group it will keep a copy
in that group and preserve threading.

The other tip I found (I think in the emacs wiki) was to avoid needing
an IMAP server to do IMAP:

(setq gnus-secondary-select-methods
      '(
        (nnimap "myserv"
                        (nnimap-stream shell)
    ... )

Then in your .emacs (and not .gnus) set:

; adjust as appropriate
(setq imap-shell-program '("MAIL=maildir:$HOME/Maildir /usr/lib/dovecot/imap"))

With this, gnus will execute IMAP directly.  It avoids needing to
provide authentication credentials and you don't need an IMAP server
listening on a port.

-Brett.

  parent reply	other threads:[~2011-01-01 16:24 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-30 21:59 prad
2010-12-31  0:35 ` Brett Viren
2010-12-31  8:50 ` Tassilo Horn
2011-01-01  6:21 ` prad
2011-01-01  9:16 ` prad
2011-01-01 13:06   ` Philipp Haselwarter
2011-01-06 16:37     ` Eric S Fraga
     [not found]   ` <mailman.0.1293887230.28475.info-gnus-english@gnu.org>
2011-01-01 13:52     ` Richard Riley
2011-01-01 22:35       ` Philipp Haselwarter
2011-01-01 16:24   ` Brett Viren [this message]
2011-01-01 20:56     ` prad
     [not found]     ` <mailman.12.1293915387.32515.info-gnus-english@gnu.org>
2011-01-02  9:04       ` Richard Riley
2011-01-02 10:38         ` Philipp Haselwarter
2011-01-02 18:38         ` prad
     [not found]         ` <mailman.4.1293993514.23049.info-gnus-english@gnu.org>
2011-01-02 20:02           ` Richard Riley
2011-01-02 21:03             ` Brett Viren
     [not found]             ` <mailman.0.1294002284.29417.info-gnus-english@gnu.org>
2011-01-02 21:10               ` Richard Riley
2011-01-03  2:54                 ` Philipp Haselwarter
2011-01-03  3:12                   ` Brett Viren
     [not found]                   ` <mailman.29.1294024360.15403.info-gnus-english@gnu.org>
2011-01-03 13:50                     ` Richard Riley
2011-01-03 16:42                       ` David Brown
2011-01-03 17:42                         ` Richard Riley
2011-01-03 19:38                           ` Dan Christensen
2011-01-03 17:21                       ` Brett Viren
     [not found]                 ` <mailman.27.1294023329.15403.info-gnus-english@gnu.org>
2011-01-03 13:44                   ` Richard Riley
2011-01-03  3:02             ` prad
     [not found]             ` <mailman.28.1294023762.15403.info-gnus-english@gnu.org>
2011-01-03 13:48               ` Richard Riley
2011-01-03 20:28                 ` prad
2011-01-03 23:10                   ` Brett Viren
2011-01-03 23:31                     ` Yuri D'Elia
     [not found]                   ` <mailman.20.1294096220.614.info-gnus-english@gnu.org>
2011-01-03 23:57                     ` Richard Riley
2011-01-04 11:30                       ` Adam Sjøgren
     [not found] <mailman.0.1293746291.12460.info-gnus-english@gnu.org>
2010-12-31  2:33 ` Richard Riley

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=AANLkTimkCNCE4y3MLhBcCum0pVBS8UJX0tODO-UMKuJL@mail.gmail.com \
    --to=brett.viren@gmail.com \
    --cc=info-gnus-english@gnu.org \
    --cc=prad@towardsfreedom.com \
    /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).