On 1999-12-19 10:17:02 -0800, Michael Elkins wrote:
Mutt saves an exact copy of what actually gets sent. You need to
use the `set pgp_encryptself' so that messages will additionally
be encrypted to yourself, allowed you to read saved outgoing
mail.
Actually, the unstable branch has an
-stable-19991220.tar.gz which I just downloaded? The problem
I don't know what that snapshot is.
is, er . . . this shapshot does not contain a ./configure script
so I don't know how to install it (I tried just copying the
./configure script from the mutt-1.1i.tar.gz into the mutt
Mutt apparently does not honor the [ALERT] IMAP server response code.
According to the IMAP RFC's, it must.
Here's a log of the IMAP dialogue between my mutt client and the IMAP
server. As you will see, the server is indeed issuing an ALERT on the
second-to-last line of the output.
--- BEGIN
On Sat, Dec 18, 1999 at 07:49:34AM -0500, Subba Rao wrote:
Is there anyway to delete this information with the
help of Mutt automatically?
---
You are currently subscribed to XYZ as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]
This is clearly a problem
Michael Elkins [EMAIL PROTECTED] wrote:
#!/usr/bin/perl
while () {
last if /^---/;
print;
}
This is a wonderful idea, but the above script could be dangerous...
it'll cut off any message to the list, with a row of dashes in it:
---
Better to search for an exact
Recently I downloaded mutt 1.0 and tried the configure command. This was the result:
loading cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make sets ${MAKE}... no
checking for working
Caldwell Warley [EMAIL PROTECTED] wrote:
Recently I downloaded mutt 1.0 and tried the configure command. This was the result:
loading cache ./config.cache
checking for a BSD compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking whether make
On Mon, Dec 20, 1999 at 01:23:19PM +0100, Jan-Benedict Glaw wrote:
This way I strongly recommend everybody to use 'set psp_encryptself' in
~/.muttrc (for PGP) or 'encrypt-to 0xKEYID' in ~/.gnupg/options (for GnuPG)
instead of saving (encrypted) mails in plaintext...
This is very dangerous
On Mon, Dec 20, 1999 at 01:48:19PM -0800, rex wrote:
On Mon, Dec 20, 1999 at 01:23:19PM +0100, Jan-Benedict Glaw wrote:
This way I strongly recommend everybody to use 'set psp_encryptself' in
~/.muttrc (for PGP) or 'encrypt-to 0xKEYID' in ~/.gnupg/options (for GnuPG)
instead of saving
Jan rex, et al --
...and then Jan-Benedict Glaw said...
% On Mon, Dec 20, 1999 at 01:48:19PM -0800, rex wrote:
% On Mon, Dec 20, 1999 at 01:23:19PM +0100, Jan-Benedict Glaw wrote:
%
... paraphrased to "use pgp_encryptself or encrypt-to settings"
%
% This is very dangerous if you ever
On Monday, 20 December 1999 at 13:22, Larry P . Schrof wrote:
Mutt apparently does not honor the [ALERT] IMAP server response code.
According to the IMAP RFC's, it must.
Here's a log of the IMAP dialogue between my mutt client and the IMAP
server. As you will see, the server is indeed
11 matches
Mail list logo
