headers
mal content | 1 Apr 18:46

Save encrypted-to-self or plain copy of sent message

Hello.

Currently, when I send a PGP encrypted message to a recipient,
it is encrypted and readable only by them. I'd like to automatically
save a plain copy of the sent message (or alternatively one
encrypted with my own public key) for my 'sent' outbox.

I used to do this years ago, but have forgotten how. Anybody
know? I think I used to use a 'pgp_encryptself' option, but it looks
like mutt doesn't support this anymore.

MC
Permalink | Reply | 4 comments |
headers
Michael Pobega | 1 Apr 15:24
Picon

GPG Keys and Signing

I've just recently learned about PGP/GPG keys and encryption, but I
can't figure out how to get it to work alongside Mutt.

I don't know if this is off-topic for mutt-users, but this is the only
place that I know of to ask.

I set up GPG and a default key, in ~/.gnupg/gpg.conf added a
keyserver, with my own registered key. I just want to be able to sign
my mails in Mutt, and verify other people's keys (Half verify and half
don't).
Permalink | Reply | 9 comments |
headers
Todd Zullinger | 1 Apr 21:02
Picon
Favicon

Re: Save encrypted-to-self or plain copy of sent message

mal content wrote:
> Currently, when I send a PGP encrypted message to a recipient, it is
> encrypted and readable only by them. I'd like to automatically save
> a plain copy of the sent message

You can use fcc_clear to achieve this.  From the manual:

3.53. fcc_clear

   Type: boolean
   Default: no

   When this variable is set, FCCs will be stored unencrypted and
   unsigned, even when the actual message is encrypted and/or signed.
   (PGP only)

> (or alternatively one encrypted with my own public key) for my
> 'sent' outbox.

You can do this in your gpg.conf using the encrypt-to option.

--

-- 
Todd        OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
======================================================================
Diplomacy is the art of saying 'Nice doggie!'... till you can find a
rock
Permalink | Reply | 2 comments |
headers
mal content | 1 Apr 21:38

Re: Save encrypted-to-self or plain copy of sent message

On 01/04/07, Todd Zullinger <tmz <at> pobox.com> wrote:
> mal content wrote:
> > Currently, when I send a PGP encrypted message to a recipient, it is
> > encrypted and readable only by them. I'd like to automatically save
> > a plain copy of the sent message
>
> You can use fcc_clear to achieve this.  From the manual:
>
> 3.53. fcc_clear
>
>    Type: boolean
>    Default: no
>
>    When this variable is set, FCCs will be stored unencrypted and
>    unsigned, even when the actual message is encrypted and/or signed.
>    (PGP only)

Ah, nice.

Is there any way to indicate that a message was signed or encrypted in
the cleartext copy? I can imagine looking at my outbox in a years time and
thinking "Argh, did I really send that unencrypted?" or something.

MC
Permalink | Reply | 1 comment |
headers
Sander Smeenk | 1 Apr 23:37

Re: GPG Keys and Signing

Quoting Michael Pobega (pobega <at> gmail.com):

> I've just recently learned about PGP/GPG keys and encryption, but I
> can't figure out how to get it to work alongside Mutt.

This works for me!

<esc>:r .mutt/crypto
--------------------

# How many seconds will mutt remember the gpg-passphrase. This is a potential
# security risk. since the phrase needs to be stored somewhere -> memory!
set pgp_timeout=0

# Reply with encryption enabled to encrypted mails.
set pgp_replyencrypt

# Reply with signing enabled to signed mails.
set pgp_replysign

# See /usr/share/doc/mutt/manual.txt.gz for explanation of stringexpansion
set pgp_decode_command="/usr/bin/gpg   --status-fd=2 %?p?--passphrase-fd 0? --no-verbose --quiet 
--batch  --output - %f"
set pgp_verify_command="/usr/bin/gpg   --status-fd=2 --no-verbose --quiet  --batch  --output -
--verify %s %f"
set pgp_decrypt_command="/usr/bin/gpg   --status-fd=2 --passphrase-fd 0 --no-verbose --quiet 
--batch  --output - %f"
set pgp_sign_command="/usr/bin/gpg    --no-verbose --batch --quiet   --output - --passphrase-fd 0
--armor --detach-sign --textmode %?a?-u %a? %f"
set pgp_clearsign_command="/usr/bin/gpg   --no-verbose --batch --quiet   --output - --passphrase-fd 0
(Continue reading)

Permalink | Reply | 8 comments |
headers
Michael Pobega | 2 Apr 01:10
Picon

Re: GPG Keys and Signing

On Sun, Apr 01, 2007 at 11:37:46PM +0200, Sander Smeenk wrote:
> Quoting Michael Pobega (pobega <at> gmail.com):
> 
> > I've just recently learned about PGP/GPG keys and encryption, but I
> > can't figure out how to get it to work alongside Mutt.
> 
> This works for me!
> 
> <esc>:r .mutt/crypto
> --------------------
> 
> # How many seconds will mutt remember the gpg-passphrase. This is a potential
> # security risk. since the phrase needs to be stored somewhere -> memory!
> set pgp_timeout=0
> 
> # Reply with encryption enabled to encrypted mails.
> set pgp_replyencrypt
> 
> # Reply with signing enabled to signed mails.
> set pgp_replysign
> 
> # See /usr/share/doc/mutt/manual.txt.gz for explanation of stringexpansion
> set pgp_decode_command="/usr/bin/gpg   --status-fd=2 %?p?--passphrase-fd 0? --no-verbose --quiet 
--batch  --output - %f"
> set pgp_verify_command="/usr/bin/gpg   --status-fd=2 --no-verbose --quiet  --batch  --output -
--verify %s %f"
> set pgp_decrypt_command="/usr/bin/gpg   --status-fd=2 --passphrase-fd 0 --no-verbose --quiet 
--batch  --output - %f"
> set pgp_sign_command="/usr/bin/gpg    --no-verbose --batch --quiet   --output - --passphrase-fd 0
--armor --detach-sign --textmode %?a?-u %a? %f"
(Continue reading)

Permalink | Reply | 7 comments |
headers
Michael Tatge | 2 Apr 11:40
Picon

Re: Save encrypted-to-self or plain copy of sent message

* On Sun, Apr 01, 2007 mal content (artifact.one <at> googlemail.com) muttered:
> Currently, when I send a PGP encrypted message to a recipient,
> it is encrypted and readable only by them. I'd like to automatically
> save a plain copy of the sent message (or alternatively one
> encrypted with my own public key) for my 'sent' outbox.
> 
> I used to do this years ago, but have forgotten how.

Either set fcc_clear or configure gpg to always encrypt with your key
too.
See encrypt-to in the gpg man page.

HTH,

Michael
--

-- 
BOFH excuse #354:

Chewing gum on /dev/sd3c

PGP-Key-ID: 0xDC1A44DD
Jabber:     init[0]@amessage.de
Permalink | Reply | 0 comments |
headers
Shaochun Wang | 3 Apr 06:40
Picon

a suggestion about shell expanding

I think it's a good idea to have a facility like shell expansion when
adding attachments to mail.

For example, I have files named 1.zip 2.zip and so on. I want adding all
of them to a mail as attachments when composing the mail. It will be
good to specify things like *.zip when pressing the 'a' key to add
attachments.

Maybe, there exists the same functionality in Mutt now. If so, let me
know how to let Mutt behavior like this.

--

-- 
Shaochun Wang <scwang <at> ios.ac.cn>

Jabber:	fungusw <at> jabber.org
Permalink | Reply | 1 comment |
headers
Sander Smeenk | 3 Apr 08:46

Re: GPG Keys and Signing

Quoting Michael Pobega (pobega <at> gmail.com):

> Should I make the .mutt folder and a crypto file, or should I put this
> in my ~/.muttrc file? I am currently using:

My config is 'split up' a bit. So certain parts relating to eachother
are in their own configuration file which i 'include' from my .muttrc.

You can do that, or put the lines in your .muttrc directly.

-Sander.
--

-- 
| OK, so what's the speed of dark?
| 1024D/08CEC94D - 34B3 3314 B146 E13C 70C8  9BDB D463 7E41 08CE C94D
Permalink | Reply | 6 comments |
headers
Christian Ebert | 3 Apr 08:52
X-Face
Picon
Gravatar

compiling against libs + headers from fink (was: adventures in coloring lines of the index view)

Hi Greg,

* Greg Novack on Thursday, March 29, 2007 at 13:29:52 -0500:
> No, I don't use fink's Mutt.  I got the source and built it
> myself.  The only ./configure flags I used were ones to enable
> imap, header caching, body caching, ssl,

Sorry to get back so late, but I only now happened to stumble
over a link I wanted to post the other day. If you want to
compile your own stuff in connection with libs and headers from
fink, the following gives you a basic idea:

<http://www.finkproject.org/faq/usage-general.php?phpLang=en#compile-myself>

> and one flag about the location of BerkeleyDB (and this last
> one only because the suggested libraries wouldn't work no
> matter what I did).

BTW, qdbm is available from fink as well.

c
--

-- 
Python Mutt utilities <http://www.blacktrash.org/cgi-bin/mercurial/muttils/>
Permalink | Reply | 0 comments |

Gmane