From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Using TLS instead of ssl
Date: Mon, 02 Nov 2009 07:57:50 -0800 [thread overview]
Message-ID: <1257177347-sup-2023@masanjin.net> (raw)
In-Reply-To: <2b29d9f30910270434k65550eaqf5187d048b604020@mail.gmail.com>
Reformatted excerpts from k.v.ramakrishna reddy's message of 2009-10-27:
> What are the changes that i need to make so that sup uses TLS instead
> of ssl when connecting to my source ?
Honestly I'm not sure. I'm not that familiar with IMAP. Is that
something that's negotiated during setting up a connection?
> Further more how can i delete a source ?
There's not a great way right now. You can remove it from
~/.sup/sources.yaml manually, and then you can remove the messages from
the index with something like this:
$ sh devel/console.sh
>> q = Index.parse_query "source_id:4"
=> # ...
>> Index.each_id(q) { |id| Index.delete id }
=> nil
>> Index.save
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2009-11-02 15:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-27 11:34 k.v.ramakrishna reddy
2009-11-02 15:57 ` William Morgan [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=1257177347-sup-2023@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-talk@rubyforge.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