Re: macros - is there any logic about when they work or not?

1999-11-30 Thread Chris Green

On Mon, Nov 29, 1999 at 08:57:42PM +0200, Mikko Hänninen wrote:
> Chris Green <[EMAIL PROTECTED]> wrote on Mon, 29 Nov 1999:
> > So, for example, the following macros in my .muttrc file *don't*
> > work (though they all appear OK on the help screen):-
> > 
> > macro generic ,s "s{mailandnews.co.uk}"
> > macro generic ,c "c{mailandnews.co.uk}"
> 
> Don't know about these two...  I'm not sure about the generic bindings,
> never played around with them.  I've always used just index/pager
> macros, they work well enough for me.
> 
> > macro generic ^X  ":source ~/.mutt/"
> > macro index ^X  ":source ~/.mutt/"
> 
> But here, I suspect you want to use \cX instead.  When I try the above
> commands, they work fine for me -- when I first type ^ followed by an X.
> 
Yes, you're right '\cX' works, for me '^X' definitely doesn't work, I
just tried it again.  Ah, I see what you mean, the '^X' case produces
a macro which is actually the two character sequence '^' and 'X'.

The manual however says:- "key and sequence are expanded by the same
rules as the key bindings, with the addition that control characters
in sequence can also be specified as ^x. In order to get a caret
(``^'') you need to use ^^. "   This is just plain wrong, the ^
character doesn't appear to have any special effect at all.


> > This all seems a bit unsatisfactory and vague to me, is there any way
> > to decide whether a particular macro will work or not other than
> > just trying it?
> 
> I've never had any problems with macros that I've not been able to
> (finally) determine a specific cause for, but admittedly finding the
> reason has not been easy in some places.
> 
Yes, I think this is basically what I've been saying, one can beat
one's way to success in the end but it's confusing.  The two main
problems seem to be that:-

1 - "generic" macros rarely seem to work as expected, this may well be
for valid (but obscure) reasons.  Maybe it would be a good idea for
the manual to point out that index and pager macros are more likely to
get the required effect.

2 - The manual is wrong about using ^ to indicate control characters.

-- 
Chris Green ([EMAIL PROTECTED])
  Home: [EMAIL PROTECTED]   Work: [EMAIL PROTECTED]
  WWW: http://www.isbd.co.uk/



selecting email-adresses from within a message

1999-11-30 Thread Jan Ulrich Hasecke

Hi!

Is it possible to select an e-email-address from within a message to
use it directly in the compose-window?

Something like Control-B for urls.

Ciao!
juh

-- 
Bekenntnisse eines Netzautoren
http://www.spiegel.de/netzwelt/nf/0,1518,40652,00.html




Re: macros - is there any logic about when they work or not?

1999-11-30 Thread Greg Matheson

On Tue, Nov 30, 1999 at 09:13:27AM +, Chris Green wrote:

> 1 - "generic" macros rarely seem to work as expected, this may well be
> for valid (but obscure) reasons.  Maybe it would be a good idea for
> the manual to point out that index and pager macros are more likely to
> get the required effect.


I was trying to write a generic macro (actually I think it was a
binding) to make  do next-page, rather than write separate
ones for the browser and index screens.

It seemed to work after I rewrote .muttrc and re-sourced it, but
then after leaving mutt and restarting it, it stopped working. I
wonder if this was connected to what the manual says about
changing settings:

> The generic menu is not a real menu, but specifies common
> functions (such as movement) available in all menus except for
> pager and editor.  Changing settings for this menu will affect
> the default bindings for all menus (except as noted).

I never saw any of these promised 'as noted' messages, but I had
other macros or bindings of  (or there is a default
binding which views the file (or mailbox) in the browser, which I
can't find in the list in 6.4 in the manual at the moment), and
these were I think the reason my generic binding wasn't working.
I think generic bindings will only work if the key isn't used
for a macro or binding anywhere else. 

Is the logic somewhat like that of folder-hooks not being reset,
but in the case of bindings, there is no looking at what is in
.muttrc again? That is the feel I got for it, anyway.

-- 
Greg Matheson   genius + soul = jazz
Chinmin College, Taiwan Mr_Bean on SchMOOze
[EMAIL PROTECTED]  & telnet://health.acor.org#



Can one show contents of mailboxes and lists?

1999-11-30 Thread Chris Green

Is there any way to find out the contents of the 'lists' and
'mailboxes' commands when running mutt?  I am using a command in `` to
generate these and I need to debug the result!  :-)

-- 
Chris Green ([EMAIL PROTECTED])
  Home: [EMAIL PROTECTED]   Work: [EMAIL PROTECTED]
  WWW: http://www.isbd.co.uk/



Problem with using commands in ` in .muttrc

1999-11-30 Thread Chris Green

I have the following in my .muttrc file:-

mailboxes `find /home/d/cgreen/Lists -type f -printf '%h/%f '` \
~/Mail/inbox

But it appears not to work, mutt can't find new mail in the files in
my Lists directory.  However if instead I execute the command on the
command line and put the result in my .muttrc file as shown below it
works correctly:-

mailboxes /home/d/cgreen/Lists/kde /home/d/cgreen/Lists/snaffle 
/home/d/cgreen/Lists/vile /home/d/cgreen/Lists/xm /home/d/cgreen/Lists/mutt 
/home/d/cgreen/Lists/qmail /home/d/cgreen/Lists/speed_dragon /home/d/cgreen/Lists/ukr 
/home/d/cgreen/Lists/xfce ~/Mail/inbox

Does anyone have any ideas what might be wrong?

-- 
Chris Green ([EMAIL PROTECTED])
  Home: [EMAIL PROTECTED]   Work: [EMAIL PROTECTED]
  WWW: http://www.isbd.co.uk/



Re: color problem

1999-11-30 Thread Eugene Lee

On Mon, Nov 29, 1999 at 06:36:20PM -0600, David DeSimone wrote:
:
:  set quote_regexp="^([ \t]?[ \t]?[>:|])+"

I'm curious, I don't quite understand the logic behind setting your
quote matching to this kind of pattern instead of using the default:

set quote_regexp="^([ \t]*[>|#:}])+" 


-- 
Eugene Lee
[EMAIL PROTECTED]



Re: uncolor index *

1999-11-30 Thread Andy Spiegl

Hi!
Does anyone have any new theories on this problem?
Thanks, 
 Andy.


Here a few tests:
eule:~>echo test | mutt -F /dev/null -s foo spiegl

eule:~>echo test | mutt -F .mutt/color -s foo spiegl
Error in .mutt/color, line 79: *: unknown command
source: Error in .mutt/color

eule:~>echo "uncolor index *" > abc

eule:~>echo test | mutt -F abc -s foo spiegl
Error in abc, line 1: *: unknown command
source: Error in abc

eule:~>echo test | mutt -n -F abc -s foo spiegl
Error in abc, line 1: *: unknown command
source: Error in abc

This is really strange!

Thanks,
 Andy.

-- 
 E-Mail: [EMAIL PROTECTED] URL: http://andy.spiegl.de
 Finger [EMAIL PROTECTED] for my PGP key
o  _ _ _
  - __o   __o  /\_   _ \\o  (_)\__/o  (_)
  --- _`\<,__`\<,__>(_) (_)/<_\_| \   _|/' \/
  -- (_)/ (_)  (_)/ (_)  (_)(_)   (_)(_)'  _\o_
 ~~~
 The function of an expert is not to be more
 right than other people, but to be wrong
 for more sophisticated reasons.  (David Butler)



running mutt as batch?

1999-11-30 Thread Mike Zimmerman

Ok, from a perl point of view this may be bad form, but I want to
send some attachment files as the result of a script.

I note that I can lauch mutt

mutt -a file -s Subject

but I do not see that I can put an addr in and have mutt execute this
ala

mail user < file

(I was hoping to cheat and use mutt for its attachment capabilities).

So I guess my question is whether mutt can do this in a batch
(non-interactive)
mode?

Thanks,
Mike



Re: running mutt as batch?

1999-11-30 Thread michael d. ivey

On Tue, Nov 30, 1999 at 10:22:31AM -0500, Mike Zimmerman wrote:
> mutt -a file -s Subject
> 
> but I do not see that I can put an addr in and have mutt execute this
> ala
> 
> mail user < file

never hurts to try it...go ahead...you might like it:

$ mutt -a Foo.mp3 -s "Here's the file" user@host < message.txt

-- 
-- michael d. ivey, chief thinker  --- <[EMAIL PROTECTED]> ---
-- gweezle bur poetry manufacturing   ---

"The thing that bothers me is someone keeps moving my chair."-- TMBG



Re: running mutt as batch?

1999-11-30 Thread Frank Altpeter


Hello !

michael d. ivey wrote on 30.11.1999 15:36:47 +:
> On Tue, Nov 30, 1999 at 10:22:31AM -0500, Mike Zimmerman wrote:
> > mutt -a file -s Subject
> > 
> > but I do not see that I can put an addr in and have mutt execute this
> > ala
> > 
> > mail user < file
> 
> never hurts to try it...go ahead...you might like it:
> 
> $ mutt -a Foo.mp3 -s "Here's the file" user@host < message.txt

RTFM 'mutt -h':

  -xsimulate the mailx send mode

So try this:echo | mutt -x -a file -s 'subject'

With kind regards,

Frank Altpeter

-- 
DAU at work, Real Life Cuts (Teil 18):
"Subject: Bitte Lesen 
 Endlich mal einen echt wichtige Mail !!!
 Diese Mail bitte an alle Bekannte weiterleiten !!!
 Ein Freund von mir braucht dringend Hilfe !"



Re: PGP support in Mutt

1999-11-30 Thread Thomas Roessler

This sounds like mutt doesn't know where to find PGP on your system.
Try setting the "pgp" configuration variable.

On 1999-11-30 10:18:09 +0100, Alexandre K. Golovanivsky wrote:
> Date: Tue, 30 Nov 1999 10:18:09 +0100
> From: "Alexandre K. Golovanivsky" <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: PGP support in Mutt
> 
> 
> Excuse me for bothering you :-)
> 
> I saw your message about PGP2 support in Mutt, and
> I just can't get it working (in lusermode, I admit).
> 
> I have 2.6.2 installed on my box (FreeBSD 3.3), with mutt 1.0i,
> and when I type (p) then (e) or (s) to PGP encrypt or sign
> my email message, mutt creates a file in /tmp/ like mutt-nawak-36341-1
> (nawak being my hostname), and fills it with +language=en.
> It just adds +language=en one on a line, until it fills the filesystem :(
> 
> Any clues?  Thanks in advance for help :)
> 
> Excuse for luserness, I am just hoping someone fixed that
> problem so I don't have to hack into mutt source.
> 
> -- 
> -akg.
> 
> 

-- 
http://www.guug.de/~roessler/



Re: Mutt/IMAP & new mail

1999-11-30 Thread Brendan Cully

On Wednesday, 24 November 1999 at 11:43, John P . Looney wrote:
> On Tue, Nov 23, 1999 at 08:04:57PM -0500, Brendan Cully mentioned:
> > In short, does mutt put all folders that have unread mail in the "new
> > mail" list, or only those that have mail that has arrived since you last
> > opened the folder?
> 
>  It seems that neither is 100% satisfactory. The way that it is in 1.1.1,
> is that when mutt scans the folders for new mail, it'll mark the folders as
> RECENT. If you don't read the folders, and twenty seconds later mutt polls the
> folders - they are now marked as UNSEEN - even though you have not opened
> the folder etc.
> 
>  A folder should be considered "New" if the user hasn't looked at the index
> of that folder since new mail has arrived. So, strictly speaking that
> change I mentioned isn't quite right either (It'll mark the folder as new,
> as long as there is a single unread mail in it). 
> 
>  The folder should be set to "New" if the server considers it to contain
> RECENT messages, but this "New" flag should not be cleared until you
> actually view the folder through the "index" screen - it should not be
> cleared as soon as the folder status changes to UNSEEN.

That makes perfect sense. In fact, that is what is does happen on most
IMAP servers (eg I use UW-IMAP - that's why I never had a problem with
the behaviour of "New" myself). Can you tell me which one you're
using? It doesn't behave the same as most others - it seems to expect
the mail client to cache \Recent information once it's been
given. Doing that would be a big change.

Sorry for the lag - I get busy sometimes.

-Brendan

PS you can find out which IMAP server you're using by just telnetting
to port 143 of your mailhost. The first line of greeting should give
you the version string.

-- 
Brendan Cully <[EMAIL PROTECTED]> | OLD SKOOL ROOLZ
"I'll level with you:  |  .-_|\ 
 Please let me on your show, I'd   | / \
 Like a day off school"| Perth ->*.--._/



Re: color problem

1999-11-30 Thread David DeSimone

Eugene Lee <[EMAIL PROTECTED]> wrote:
>
> :  set quote_regexp="^([ \t]?[ \t]?[>:|])+"
> 
> I'm curious, I don't quite understand the logic behind setting your
> quote matching to this kind of pattern instead of using the default:
> 
>   set quote_regexp="^([ \t]*[>|#:}])+" 

Hmm, I didn't know that my regexp was so close to the default.  You're
right, the default will do the right thing, but in this case, the
original poster was using Sven's muttrc, which has this very simple
setting:

set quote_regexp="^> "

This regexp will always match the same length of text, so it will only
recognize one quote level, or none.

The chief difference between my regexp and the default, is that mine
gives fewer false-positives.  If someone sends me a nice ASCII-drawing
chart of some kind, Mutt doesn't go crazy colorizing it.  :)

-- 
David DeSimone   | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED]   |  that there is no man really clever who has not
Hewlett-Packard  |  found that he is stupid." -- Gilbert K. Chesterson
UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D  AB A6 15 F1 BB BE 8C 44



Re: Mutt/IMAP & new mail

1999-11-30 Thread John P . Looney

On Tue, Nov 30, 1999 at 11:49:37AM -0500, Brendan Cully mentioned:
> >  The folder should be set to "New" if the server considers it to contain
> > RECENT messages, but this "New" flag should not be cleared until you
> > actually view the folder through the "index" screen - it should not be
> > cleared as soon as the folder status changes to UNSEEN.
> That makes perfect sense. In fact, that is what is does happen on most
> IMAP servers (eg I use UW-IMAP - that's why I never had a problem with
> the behaviour of "New" myself). Can you tell me which one you're
> using? It doesn't behave the same as most others - it seems to expect
> the mail client to cache \Recent information once it's been
> given. Doing that would be a big change.

> PS you can find out which IMAP server you're using by just telnetting
> to port 143 of your mailhost. The first line of greeting should give
> you the version string.

oracle1 [0]  telnet gpo imap
Trying 192.168.1.2...
Connected to hercules.fv.digiserve.ie.
Escape character is '^]'.
* OK hercules.fv.digiserve.ie IMAP4rev1 v12.250 server ready
^]
telnet> quit

 That's the same as you are using, yes ? Actually, it's unlikely to be.
This IMAP server has been patched to use Maildir format to store the
mailboxes. This could just be another artifact of Maildir/IMAP being
unhappy together. D'oh. So much for an easy solution.

John

-- 
Microsoft. The best reason in the world to drink beer.
http://www.redbrick.dcu.ie/~valen



Re: Can one show contents of mailboxes and lists?

1999-11-30 Thread Mikko Hänninen

Chris Green <[EMAIL PROTECTED]> wrote on Tue, 30 Nov 1999:
> Is there any way to find out the contents of the 'lists' and
> 'mailboxes' commands when running mutt?  I am using a command in `` to
> generate these and I need to debug the result!  :-)

I don't know any way for lists, but you can get a list of your
mailboxes with the key-sequence c? (provided you're using the
default keybindings).


Mikko
-- 
// Mikko Hänninen, aka. Wizzu  //  [EMAIL PROTECTED]  //  http://www.iki.fi/wiz/
// The Corrs list maintainer  //   net.freak  //   DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
"I'll be Bach."  -- Johann Sebastian Schwarzenegger



Re: running mutt as batch?

1999-11-30 Thread Mikko Hänninen

Frank Altpeter <[EMAIL PROTECTED]> wrote on Tue, 30 Nov 1999:
> RTFM 'mutt -h':
> 
>   -xsimulate the mailx send mode
> 
> So try this:  echo | mutt -x -a file -s 'subject'

Actually, that's not what -x does.  The -x option is used when starting
a new email from the command line interactively.  I guess it doesn't
affect anything if you use batch mode, which seems to work the same
regardless of whether you use -x or not.  Perhaps a bit surprisingly,
since I'd expect that if you used -x then mutt would expect a line
with "." to end the body text.

The man page says:

-x Emulate the mailx compose mode.

... which IMHO is a better phrasing than "simulate the mailx send mode"
used in mutt -h.


Anyway, the point is that batch mode works equally well with or without
the -x. :-)


All this is based on my own testing, so hopefully someone will correct
me if I'm wrong. :-)

Mikko
-- 
// Mikko Hänninen, aka. Wizzu  //  [EMAIL PROTECTED]  //  http://www.iki.fi/wiz/
// The Corrs list maintainer  //   net.freak  //   DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
Favourite MS-DOS error message: "Drive C: not ready, close door."



Re: Problem with using commands in ` in .muttrc

1999-11-30 Thread Mikko Hänninen

Chris Green <[EMAIL PROTECTED]> wrote on Tue, 30 Nov 1999:
> mailboxes `find /home/d/cgreen/Lists -type f -printf '%h/%f '` \
> ~/Mail/inbox
> 
> But it appears not to work, mutt can't find new mail in the files in
> my Lists directory.  However if instead I execute the command on the
> command line and put the result in my .muttrc file as shown below it
> works correctly:-

Try adding a newline at the end of that find, eg. with adding a
;echo "" to the end (or something like that).  I remember seeing some
reports of Mutt not parsing the lines from `` substituations correctly
if there was no trailing newline, though I'm not sure if that was with
some older Mutt versions.  Worth a try.

Incidentally, assuming your $spool is set correctly (to ~/Mail/inbox),
you may replace that last entry with just the '!' char.  Also, you
should note that the order in which the mailboxes are listed does matter
in some cases (eg. when scrolling through mailboxes with new mail with
space after a 'c' command, or using the "unsorted" sort in mailboxes
index), so I'd put that first.


Regards,
Mikko
-- 
// Mikko Hänninen, aka. Wizzu  //  [EMAIL PROTECTED]  //  http://www.iki.fi/wiz/
// The Corrs list maintainer  //   net.freak  //   DALnet IRC operator /
// Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs /
  "Save it for a rainy day..." -- The Corrs



mutt 1.1.1 : make error

1999-11-30 Thread J Horacio MG

Hi,

I'm trying to compile mutt 1.1.1, and am getting the following error
while running make:

In file included from mutt_menu.h:23,
 from addrbook.c:20:
keymap.h:112: keymap_defs.h: No such file or directory
make[2]: *** [addrbook.o] Error 1
make[2]: Leaving directory `/usr/local/mutt-1.1.1'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/mutt-1.1.1'
make: *** [all-recursive-am] Error 2

Then I `make clean', copy mutt-1.0/keymap_defs.h into mutt-1.1.1/, and
`make' again, but:

compose.c:1217: `OP_COMPOSE_MIX' undeclared (first use this function)
make[2]: *** [compose.o] Error 1
make[2]: Leaving directory `/usr/local/mutt-1.1.1'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/usr/local/mutt-1.1.1'
make: *** [all-recursive-am] Error 2

The configure flags I'm using are:

--with-sharedir="/usr/local/share/mutt" --with-slang
--with-mailpath="/var/spool/mail" --enable-pop --with-regex
--enable-locales-fix --enable-exact-address
--with-charmaps="/usr/share/i18n/charmaps" --enable-PGP2 --enable-PGP5
--enable-PGP6 --enable-GPG --with-mixmaster="/usr/local/Mix"
--enable-compressed

Can anyone help, please?

Also, how could I tell mutt to enable pgp 2, 5, and 6 altogether
(binaries are pgp2, pgp5 and pgp6, and pgp is just a link to pgp6).


TIA

-- 
Horacio LC_mutt=es_ES
mailto:[EMAIL PROTECTED]http://carlotha.ciberia.es/mutt/
~ Spain ~ Spanje ~ Spanien

Key fingerprint = F4EE AE5E 2F01 0DB3 62F2  A9F4 AD31 7093 4233 7AE6



Re: mutt 1.1.1 : make error

1999-11-30 Thread Lars Hecking


> Then I `make clean', copy mutt-1.0/keymap_defs.h into mutt-1.1.1/, and
> `make' again, but:
 
 Arghh, no.

 make keymap_defs.h ; make

> Also, how could I tell mutt to enable pgp 2, 5, and 6 altogether
> (binaries are pgp2, pgp5 and pgp6, and pgp is just a link to pgp6).
 
 configure should pick them up if they're in PATH. Not sure how it
 handles pgp5/6, if at all.



Re: running mutt as batch?

1999-11-30 Thread Frank Altpeter


Hello !

Mikko Hänninen wrote on 30.11.1999 20:54:38 +0200:
> Anyway, the point is that batch mode works equally well with or without
> the -x. :-)

Hmmm... i didn't test it before, but ... you're right :-)

With kind regards,

Frank Altpeter

-- 
Fachbegriffe der Informatik einfach erklaert, Teil 48:
"Nutzt die neuen Moeglichkeiten von Windows'95!"
  == "Haben Sie unser anderes Update schon gekauft?" (Kristian Koehntopp)



Possible bug/feature involving PGP

1999-11-30 Thread David W. Bettis

Greetings, all.

Just recently, I've been messing around with PGP, trying to get
everything set up correctly, and such.  I've had problems trying to
send out encrypted messages with another person's public key.  When
trying to send a message to myself, here is what I get:


Pretty Good Privacy(tm) Version 6.5.1
(c) 1999 Network Associates Inc.
Uses the RSAREF(tm) Toolkit, which is copyright RSA Data Security,
Inc.
Export of this software may be restricted by the U.S. government.


Key for user ID: David W. Bettis <[EMAIL PROTECTED]>
1024-bit DSS key, Key ID 0xBC6219B0, created 1999/11/21
Key can sign. 
WARNING:  Because this public key is not certified with a trusted
signature, it is not known with high confidence that this public key
actually belongs to: "David W. Bettis <[EMAIL PROTECTED]>".

Are you sure you want to use this public key (y/N)?Ok, skipping userid
David W. Bettis <[EMAIL PROTECTED]>
Encryption error

For a usage summary, type:  pgp -h
For more detailed help, consult the PGP User's Guide.
Press any key to continue...


This output is identical to what I would get if I tried to encrypt a
file with my public key normally, and at the prompt "Are you sure you
want to use this public key (y/N)?", I hit a simple  instead
of y or n.  If I do, in fact, respond "y," the file (or STDIN) will be
encrypted, and everything is fine.

I noticed a note or two in the list archives describing a problem such
as this.  I'm rather a newbie at this, so I could be wrong in my
assumption that somehow this "y" isn't getting fed to mutt.  Aside
from that, I have no clue how one would go about doing something like
that.  Is there a "force" option in pgp that I'm unaware of, maybe?

The encrypt command I have in my ~/.muttrc is:

# create a pgp/mime encrypted attachment
set pgp_encrypt_only_command="pgp +verbose=1 +encrypttoself +batchmode -eaft %r < %f"

I'm using PGP v6.5.1.


Many thanks!

DWB


-- 
/* David W. Bettis <[EMAIL PROTECTED]> \ "Life is a little explosion in
 * pgp id: 0xBC6219B0 /   between two huge silences."
 *web: http://www.enthalpy.net\-- Facundo Cabral, poet
 */



Re: Possible bug/feature involving PGP

1999-11-30 Thread David Ellement

On 991130, at 22:42:19, David W. Bettis wrote:
> [...]  I've had problems trying to
> send out encrypted messages with another person's public key.  When
> trying to send a message to myself, here is what I get:
> 
> Key can sign. 
> WARNING:  Because this public key is not certified with a trusted
> signature, it is not known with high confidence that this public key
> actually belongs to: "David W. Bettis <[EMAIL PROTECTED]>".
> 
> Are you sure you want to use this public key (y/N)?Ok, skipping userid
> David W. Bettis <[EMAIL PROTECTED]>
> Encryption error
> 
> [...]
> I noticed a note or two in the list archives describing a problem such
> as this.  [...] my
> assumption that somehow this "y" isn't getting fed to mutt.  Aside
> from that, I have no clue how one would go about doing something like
> that.  Is there a "force" option in pgp that I'm unaware of, maybe?
> Encryption error
> 
> I'm using PGP v6.5.1.

For PGP 5, setting "NoBatchInvalidKeys = off" in pgp.cfg prevents this
problem.  Perhaps there's a similar option for PGP 6.

-- 
David Ellement



Re: macros - is there any logic about when they work or not?

1999-11-30 Thread Rejo Zenger

++ 30/11/99 09:13 + - Chris Green:
>2 - The manual is wrong about using ^ to indicate control characters.

I guess it depends from system to system (and possibly the way of
quoting). Could people on different systems try this?

-Rejo.

-- 
= Rejo Zenger  [Sister Ray Crisiscentrum]   [EMAIL PROTECTED]
= http://mediaport.org/~sister  PGP: see headers