Hello,
there are many PGP-signed messages in this mailing-list. I don't have
the public keys from all that senders.
Can I shrink the 15 lines of useless (every time the same) PGP
information? One line like "key unavailable", "sign OK" or "sign not
OK" looks better on a 80x25 display...
Jens
On Fri, Jun 25, 1999 at 06:37:11AM +0200, Jens Tautenhahn wrote:
Hello,
there are many PGP-signed messages in this mailing-list. I don't have
the public keys from all that senders.
Can I shrink the 15 lines of useless (every time the same) PGP
information? One line like "key
Warning
Could not process message with given Content-Type:
multipart/signed; boundary=EuxKj2iCbKjpUGkD; micalg=pgp-sha1;protocol="application/pgp-signature"
Warning
Could not process message with given Content-Type:
multipart/signed; boundary=xyF51EaUT3XiWnZP; micalg=pgp-sha1;protocol="application/pgp-signature"
On Fri, Jun 25, 1999 at 07:30:39AM -0400, David Thorburn-Gundlach wrote:
Hi, folks --
I know that I can use tab to jump to the next new message, but is
there a key or binding that I can use to jump to the next old message?
I have a mailbox with some old-and-unread messages that I'd like to
On Thu, Jun 24, 1999 at 08:37:00PM -0700, Brian D. Winters wrote:
I have the following in a script:
ssh -f -L 4143:imapserver:143 sshhost 'sleep 5 /dev/null /dev/null'
mutt $*
What happens when 5 seconds have elapsed? Would port 4143 in the sshhost
still forward to port 143 of the
Brian D. Winters [EMAIL PROTECTED] typed:
Under Navigator, yes a mailto will bring up mutt, but as I failed to
observe yesterday, it doesn't actually pass the address. This
obviously isn't incredibly useful behavior. If I figure out a
workaround I'll post it here, but otherwise it looks
And this change makes xmutt work properly with navigator 4.61:
[root@lhe unixpost-mutt]# diff xmutt.c xmutt_old.c
132c132
char* argv[16] = {XMUTT, to, NULL};
---
char* argv[16] = {XMUTT, NULL};
Thanks Chris.
--
(T.) Michael Sanders internet: [EMAIL PROTECTED]
Physics Department
Hi
Many months of fiddling and I have not managed to get send-hooks to work.
Here is my muttrc - can you see why?
#send-hook '~A' 'my_hdr From: Mutt User user@winkle'
send-hook '~A' 'my_hdr Subject: THIS IS VERY IMPORTANT'
#send-hook . 'my_hdr From: [EMAIL PROTECTED]'
#send-hook eric
Thank you for your answer, forward_decrypt makes sense to me now.
BTW, the subject line should have read: forward_decrypt, as it does now,
sorry about it.
Mark Bainter dixit:
~
~
~ Also, about encrypted mail, is there a way of having non-mime encrypted
~ (just as you would with digitally
Eric Smith [EMAIL PROTECTED] wrote:
In what way do they fail to work?
Well, they do not set the headers or whatever, they just do not have
any effect.
The only un-commented send-hook in the huge muttrc file you sent was one
that tries to set the subject header. I believe there is a
On Fri, Jun 25, 1999 at 04:29:18PM -0700, Paul M. Lambert wrote:
I've gone over the code, and there's a simple fix. I'm too lazy to do
a diff, but here's a description:
Thanks! That is way too obvious. ;)
I guess this means that in Navigator 4.6x Netscape is actually
following their own
If I read the docs right, the line
mbox-hook in.foo read.foo
should move all read messages in in.foo to read.foo when I quit or
change folders. Am I missing something? This does not seem to work.
Cheers...
--
Alex Lane mailto:[EMAIL PROTECTED]
Seabrook, Texas,
13 matches
Mail list logo
