From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: Maybe encrypt message ?
Date: Wed, 25 Nov 2015 11:03:07 +0000 [thread overview]
Message-ID: <87ziy22vf8.fsf@mat.ucm.es> (raw)
In-Reply-To: <m0egffxgp2.fsf@kcals.intra.maillard.im>
> Uwe Brauer <oub@mat.ucm.es> writes:
> [ ... cut ... ]
> I remember that possibility now ! If I could sync my carddav with
> bbdb, maybe I could get back to using it.
> Isn't this too cumbersome ? For each of your outgoing message, you
> have to make a choice, right ?
At first yes, but I tried out all sort of rules and finally decided that
this is the most convenient. Other user might differ in their opinion. I
also have the difficulity that I use gpg with some users and smime with
others. And some of the users are not in my bbdb etc etc
next prev parent reply other threads:[~2015-11-25 11:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 6:10 Xavier Maillard
2015-11-24 12:18 ` Uwe Brauer
2015-11-24 20:53 ` Xavier Maillard
2015-11-25 11:03 ` Uwe Brauer [this message]
2015-11-24 16:22 ` Jens Lechtenboerger
2015-11-24 20:48 ` Xavier Maillard
2015-11-24 21:17 ` Peter Münster
2015-11-25 11:04 ` Uwe Brauer
2015-11-26 5:00 ` Xavier Maillard
2015-11-26 10:11 ` Peter Münster
2015-11-26 14:44 ` Xavier Maillard
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=87ziy22vf8.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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).