From: Matthias Vallentin <vallentin@icsi.berkeley.edu>
To: Tero Tilus <tero@tilus.net>
Cc: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Maildir sent_source
Date: Wed, 22 Dec 2010 09:14:44 -0800 [thread overview]
Message-ID: <20101222171444.GH60419@icsi.berkeley.edu> (raw)
In-Reply-To: <1292928629-sup-4367@tilus.net>
On Tue, Dec 21, 2010 at 12:56:23PM +0200, Tero Tilus wrote:
> Judging by the code it looks like you also need to sup-add your
> maildir in addition to adding it to config.
Yup, the following configuration works for me:
- !masanjin.net,2006-10-01/Redwood/Maildir
uri: maildir:~/.mail/sent
usual: false
archived: true
id: 1
labels:
- sent
This works only if the source is added before the first launch. As you
mentioned earlier, the cleanest solution would be to patch bin/sup such
that it respects the sent_source configuration (and in particular the
URI scheme and location).
Matthias
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2010-12-22 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 7:12 Matthias Vallentin
2010-12-21 10:56 ` Tero Tilus
2010-12-22 14:34 ` Matthias Vallentin
2010-12-22 17:14 ` Matthias Vallentin [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=20101222171444.GH60419@icsi.berkeley.edu \
--to=vallentin@icsi.berkeley.edu \
--cc=sup-talk@rubyforge.org \
--cc=tero@tilus.net \
/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