gpg fails

1999-11-10 Thread Christian v. Mueffling

Reply-To: 
Hi!

In the mutt versions after 1.0i (1.1i and 1.1.1i) the gpg call doesnt
work anymore. After the input of the passphrase mutt just says
'Invoking PGP ...' and doesnt do anything ...

any hints?

chris


 PGP signature


Re: gpg fails

1999-11-10 Thread Micha Holzmann

Hello Christian,

 n the mutt versions after 1.0i (1.1i and 1.1.1i) the gpg call doesnt
 work anymore. After the input of the passphrase mutt just says
 'Invoking PGP ...' and doesnt do anything ...
 
 any hints?

i posted a similar mail here. Concerning mutt and pgp 6.5.1i.
It seems not to be interest to someone here on the list.
Or there is no solution.

In your case i think it is an error in your .muttrc, gpg
works here.

kind regards,
Micha




Re: gpg fails

1999-11-10 Thread Sean Rima

Hi Micha!

On Wed, 10 Nov 1999, Micha Holzmann wrote:

 Hello Christian,
 
  n the mutt versions after 1.0i (1.1i and 1.1.1i) the gpg call doesnt
  work anymore. After the input of the passphrase mutt just says
  'Invoking PGP ...' and doesnt do anything ...
  
  any hints?
 
 i posted a similar mail here. Concerning mutt and pgp 6.5.1i.
 It seems not to be interest to someone here on the list.
 Or there is no solution.
 
 In your case i think it is an error in your .muttrc, gpg
 works here.
 
I found that GPG works better using gpg-2comp and gpg.rc. Maybe it will work
without them but I put them that way and they work so I ain't changing it. I
use 1.1i.

Sean
-- 
GPG ID (5.x) 92B9D0CF
To get my GPG (PGP 5.x) Key send me an empty
email with retrieve as the subject
Linux User: #124682 ICQ: 679813
My Current Uptime is 0d, 4h and 26m on Linux 2.2.13
...Internet?...whazzat?  Some sort of Irish fisherman's prayer?



Automatic CC adding

1999-11-10 Thread Denis Chapligin

Hi

I have some letters that comes to me with "To: [EMAIL PROTECTED]". Every time
i responding this message i need to add "CC: [EMAIL PROTECTED]". Now i do this
by hands. Is there any way to do it automatically?

--

Denis Chapligin



Re: mutt v1.1.1i and pgp

1999-11-10 Thread Christian v. Mueffling
 msg.pgp


Re: Automatic CC adding

1999-11-10 Thread Mikko Hänninen

Denis Chapligin [EMAIL PROTECTED] wrote on Wed, 10 Nov 1999:
 I have some letters that comes to me with "To: [EMAIL PROTECTED]". Every time
 i responding this message i need to add "CC: [EMAIL PROTECTED]". Now i do this
 by hands. Is there any way to do it automatically?

Does using g(roup reply) work for you?  It puts the To: address in the
To: field of the reply, and the original sender as Cc:.


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 /
This is a test signature.  Had it been for real, it would've been funny.



Re: mutt v1.1.1i and pgp

1999-11-10 Thread Sean Rima
 msg.pgp


Re: Vacation problem

1999-11-10 Thread Shane Castle

On Wed, 10 Nov 1999, Sean Rima wrote:

Seriously OT but maybe not. I went on holiday and left vacation to answer my
mail, however, it should not send any mail back to the list.

I was unsubscribed from the list and I wanted to know if my vacation sent an
auto-respond message.

I only ask as I plan on putting it back on again this weekend and don't want
it to send any messages back to the list/list-users.

IMNSHO, and speaking as a sysadmin, I'd love to remove the vacation
program from all my systems and give anyone that used it 50 lashes with
old brittle tri-leads.  It serves absolutely no useful purpose and causes
more problems that anything it was intended to solve.  PLEASE don't use
it!  Don't even try to fix it; it's too broken!

And I'm trying to use and like mutt but I just can't seem to wean myself
from the taste of turpentine.

-- 
Shane Castle | "Perfection, then, is finally achieved, not
Boulder County Info Svcs | when there is nothing left to add, but when
Boulder CO USA   | there is nothing left to take away."
 |- Antoine de Saint-Exupery



Re: Vacation problem

1999-11-10 Thread Claus Assmann

On Wed, Nov 10, 1999, Shane Castle wrote:

   It serves absolutely no useful purpose and causes
 more problems that anything it was intended to solve.  PLEASE don't use
 it!  Don't even try to fix it; it's too broken!

Which version are you talking about?

IMHO it is a very useful program, there are just too many
broken versions around. That's why sendmail 8.10 comes
with a vacation program.



Re: mutt v1.1.1i and pgp

1999-11-10 Thread Gero Treuner

Hi!

On Wed, Nov 10, 1999 at 05:41:12PM +, Sean Rima wrote:
  But neverless: I use now the gpg.rc and the gpg-2comp. Signing works
  fine, but encrypting (with or without signing) doesnt. Mutt just says
  something like 'invoking PGP ...' but nothing happens ...
  
 I use both and I can encrypt and decrypt okay. A thought, try a sample of
 the gpg.rc line on the console to see what happens. Maybe that will throw
 some light on it.

gpg-2comp revisions before 1.3 had flaws with some option/setup
combinations. Please look at
http://muppet.faveve.uni-stuttgart.de/~gero/gpg-2comp/
for changes - er, probably that can't really be fixed, because there
are dozens of options interacting in multiple ways. For standard
configurations it should work, though, people who choose exotic
options should know what they so.

If it is still not working, please send me the output of the gpg
processing on the terminal that I can have a look at it.


Gero



Re: cannot change mailbox name

1999-11-10 Thread David DeSimone

sam rosenfeld [EMAIL PROTECTED] wrote:

 I have a single-user (me) box with two potential mail users -- root
 and user.  When I'm logged in as "user" and open mutt, I get an error
 message which reads:  "/var/spool/mail/root:  Permission denied
 (errno=13)".

The setting that controls this is called $spoolfile.  You should check
to see if it is getting set somewhere.  It probably isn't, because if
it's not set, Mutt will create a convenient default that probably points
to the right place.

The environment will come into play, though.  If there is a $MAIL
variable in your environment, it will be used as the default for
$spoolfile.  Otherwise, a default is constructed from the $USER
variable.

So I would presume that, either you have $MAIL set to
/var/spool/mail/root, or you have $USER set to root.  Both of these
mean there is some misconfiguration in your login-session scripts,
and probably not in any Mutt config scripts.

 And, I want to make my screen a bit more attractive and readable.  How
 do I set the COLORFGBG?  (The manual.txt is a bit obscure on this
 issue.)

This is a SLANG config variable, not exactly a Mutt config (though Mutt
might have been compiled with Slang on your system).  The COLORFGBG
variable defines the foreground and background colors that your terminal
has.  Slang has no way to know, for instance, that your terminal's
foreground color might be cyan, and the background might be black.  So
you can set this variable so that Slang can tell:

export COLORFGBG="cyan;black"

This does *NOT* mean that when you run a Slang program, it will make
your foregroudn be cyan, and your background black!  Instead it means
that, when Slang runs with this setting, it will assume that, if the
foreground is supposed to be cyan, and the background is supposed to be
black, that it can just print normal, uncolored spaces, or use screen-
clear and line-clear commands, because the proper colors will get used
by the terminal.

Now, that's probably clear as mud.  :(

-- 
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: Vacation problem

1999-11-10 Thread Russell Van Tassell

On Wed, Nov 10, 1999 at 01:25:52PM +, Sean Rima wrote:
 Hi Folks,
 
 Seriously OT but maybe not. I went on holiday and left vacation to answer my
 mail, however, it should not send any mail back to the list.

Ummm... simply put, use procmail/formail... you'll have less problems
with it.  (there are decent examples of making this work in the
procmailex man page)

Russell

-- 
Russell M. Van Tassell
[EMAIL PROTECTED]

 "I cannot conceive that anybody will require multiplications at the
  rate of 40,000 or even 4,000 per hour ..."   -- F. H. Wales (1936)



Re: Vacation problem

1999-11-10 Thread Sean Rima

Hi Russell!

On Wed, 10 Nov 1999, Russell Van Tassell wrote:

 On Wed, Nov 10, 1999 at 01:25:52PM +, Sean Rima wrote:
  Hi Folks,
  
  Seriously OT but maybe not. I went on holiday and left vacation to answer my
  mail, however, it should not send any mail back to the list.
 
 Ummm... simply put, use procmail/formail... you'll have less problems
 with it.  (there are decent examples of making this work in the
 procmailex man page)
 
There are, but I took over maintaining vacation and I was only wondering if
my disappearance from the list was related to a stray message from it.

Sean

-- 
GPG ID (5.x) 92B9D0CF
To get my GPG (PGP 5.x) Key send me an empty
email with retrieve as the subject
Linux User: #124682 ICQ: 679813
My Current Uptime is 0d, 13h and 14m on Linux 2.2.13
...Internet?...whazzat?  Some sort of Irish fisherman's prayer?



Re: Vacation problem

1999-11-10 Thread Sean Rima

Hi Shane!

On Wed, 10 Nov 1999, Shane Castle wrote:

 Seriously OT but maybe not. I went on holiday and left vacation to answer my
 mail, however, it should not send any mail back to the list.
 
 I was unsubscribed from the list and I wanted to know if my vacation sent an
 auto-respond message.
 
 I only ask as I plan on putting it back on again this weekend and don't want
 it to send any messages back to the list/list-users.
 
 IMNSHO, and speaking as a sysadmin, I'd love to remove the vacation
 program from all my systems and give anyone that used it 50 lashes with
 old brittle tri-leads.  It serves absolutely no useful purpose and causes
 more problems that anything it was intended to solve.  PLEASE don't use
 it!  Don't even try to fix it; it's too broken!
 
 And I'm trying to use and like mutt but I just can't seem to wean myself
 from the taste of turpentine.
 
For those who need such a thing it is handy. Yes there are broken versions
out there but if all systems updated to the newest version and reported
problems then it would not be such an issue.

Sean

-- 
GPG ID (5.x) 92B9D0CF
To get my GPG (PGP 5.x) Key send me an empty
email with retrieve as the subject
Linux User: #124682 ICQ: 679813
My Current Uptime is 0d, 10h and 43m on Linux 2.2.13
...Internet?...whazzat?  Some sort of Irish fisherman's prayer?



Re: Killing an xterm with mutt

1999-11-10 Thread Sven Guckes

* Jan Houtsma ([EMAIL PROTECTED]) [991109 18:33]:
 If i run mutt in an xterm (xterm -e mutt) and i read email
 then when i kill the window with the X in the right top
 corner of the window of course kills mutt also.
 
 But apparently mutt doesnt catch this signal cause it doesnt
 update the status of the messages i already read in that session.
 
 Would that be nice to have? I am lazy and pressing that X is easier
 then typing "q", "y" :-)

:set quit=yes

Now you just have to type 'q' -
from anywhere within the xterm.
Isn't that much easier than
reaching for the mouse and
place it on the "X" first?  ;-)

But you have a point there -
mutt does not exit gracefully.

Sven



Re: Killing an xterm with mutt

1999-11-10 Thread David DeSimone

Sven Guckes [EMAIL PROTECTED] wrote:

  I am lazy and pressing that X is easier then typing "q", "y" :-)
 
 :set quit=yes
 
 Now you just have to type 'q' - from anywhere within the xterm.

The "y" that he's referring to might be the "delete" prompt, so perhaps

:set delete=yes

would also help, and perhaps

:set move=no (or yes)

would help further.

 Isn't that much easier than reaching for the mouse and place it on the
 "X" first?  ;-)

I am inclined to agree that, in a mailer program, the hands are more
likely to be located closer to the keyboard, than the mouse.  :)

 But you have a point there - mutt does not exit gracefully.

This could be argued quite a bit, I imagine.  Suppose your X server blew
up, and took all your windows with it?  Mutt cannot tell the difference
between that condition, and closing the xterm with the [X] button.  In
both cases, the xterm disappears from around Mutt, and it has no idea
why.  In this case, Mutt errs on the side of caution, because it doesn't
want to lose information, unless it's sure that you are really quitting.

-- 
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: Killing an xterm with mutt

1999-11-10 Thread Mikko Hänninen

David DeSimone [EMAIL PROTECTED] wrote on Wed, 10 Nov 1999:
 This could be argued quite a bit, I imagine.  Suppose your X server blew
 up, and took all your windows with it?  Mutt cannot tell the difference
 between that condition, and closing the xterm with the [X] button.  In
 both cases, the xterm disappears from around Mutt, and it has no idea
 why.  In this case, Mutt errs on the side of caution, because it doesn't
 want to lose information, unless it's sure that you are really quitting.

What's different in the X server blowing up, why shouldn't Mutt exit
gracefully in that situation?

I agree that there should be caution taken in this situation, but I'm
not sure if exiting without saving anything is the right choice.  And
another point is that someone closing the xterm intentionally is a much
more common event than the X server crashing (I would hope!), even if
that doesn't mean the latter should be ignored as a possibility.

I wonder how feasible it would be to add some sort of option for this?
Or a configure option possibly?


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 /
"Yesterday was the deadline on all complaints."



Re: Can there be too many color definitions?

1999-11-10 Thread Edmund GRIMLEY EVANS

 I've got a strange problem.  After I updated to Mutt v1.0 ((1999-10-22)
 (the Debian package 1.0.0-2) all my colors were mixed around.  After playing 
 around quite a bit I found that I have to comment out the following lines
 in /etc/Muttrc:

Debian's /etc/Muttrc is a complete disaster in my experience. It
almost put me off mutt when I first tried it.

It's probably a good idea to delete the file altogether.



Re: Vacation problem (non-list content)

1999-11-10 Thread Russell Van Tassell

On Wed, Nov 10, 1999 at 09:33:56PM +, Sean Rima wrote:
   [Did 'vacation' cause me to get bounced off the list?]
  
  Ummm... simply put, use procmail/formail... you'll have less problems
  with it.  (there are decent examples of making this work in the
  procmailex man page)

 There are, but I took over maintaining vacation and I was only wondering if
 my disappearance from the list was related to a stray message from it.

Well, quite honestly, I've "disappeared" from the list because of an
overloaded mail server or mis-behaving/looping upstream relay (there's
been a couple of weird ones that, all told, lasted an hour or two)...
so I think the person to ask is "[EMAIL PROTECTED]"

But, if, as you say, you 'maintain' the vacation program... you're
probably about the best person to ask if it actually misbehaves by
sending messages back to a mailing list (ie. it shouldn't, and I'm
pretty sure that some of Eric's later versions worked correctly).

So... *shrug*

Hope that helps, at least somewhat...


Russell

-- 
Russell M. Van Tassell
[EMAIL PROTECTED]

"We have always been quite clear that Win95 and Win98 are not the systems
 to use if you are in a hostile security environment. We recommend Windows
 NT for those environments."   -- Paul Leach [EMAIL PROTECTED]



Re: Alternates

1999-11-10 Thread Mikko Hänninen

Nathan Cullen [EMAIL PROTECTED] wrote on Wed, 10 Nov 1999:
 My question is, can I have multiple "alternates" (one for each email
 address), or do I have to bunch them all in to one big regex?

You bunch them all in one big regex.  It looks slightly ugly but
fortunately it doesn't need to be human-parseable most of the time.
:-)


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 /
Don't you hate it when life doesn't follow the manuals?



Re: Alternates

1999-11-10 Thread Fairlight

On Wed, Nov 10, 1999 at 05:55:08PM -0500, Nathan Cullen thus spoke:
 I am trying to figure out the syntax of the "alternates" option.  The
 mutt manual says "A regexp that allows you to specify alternate
 addresses where you receive email".
 
 My question is, can I have multiple "alternates" (one for each email
 address), or do I have to bunch them all in to one big regex?
 
 Thanks for any assitance you can give!

I assumed it should be a regex and wrote mine that way...you're right
though, it isn't clear...they should perhaps put [multiple] on settings
that may have multiple listings (ignore, lists, etc) as opposed to ones
that do not.

The giveaway may be whether it needs "set"...  Since it uses set, it
should just be one expression...I believe that was my rationale for doing
one regexp to begin with.  If it doesn't use "set", then it's probably a
multiple-capable setting.

mark-
-- 
Fairlight-   |||[EMAIL PROTECTED]  | Fairlight Consulting
  __/\__  ||| "I'm talking for free...   | http://www.fairlite.com
  |||   It's a New Religion..."  | [EMAIL PROTECTED]
\/||| PGP Public Key available via finger @iglou, or Key servers



Re: Alternates

1999-11-10 Thread Fairlight

On Thu, Nov 11, 1999 at 05:51:19AM +0200, Mikko Hänninen thus spoke:
 Nathan Cullen [EMAIL PROTECTED] wrote on Wed, 10 Nov 1999:
  My question is, can I have multiple "alternates" (one for each email
  address), or do I have to bunch them all in to one big regex?
 
 You bunch them all in one big regex.  It looks slightly ugly but
 fortunately it doesn't need to be human-parseable most of the time.
 :-)

I imagine it does look really confusing with lots of short things like
iki.fi in it.  :)  *grin*  No offense...but the shorter the strings, the
harder time I have reading the entire expression because you get no feel
for context without counting nestings carefully.

mark-
-- 
Fairlight-   |||[EMAIL PROTECTED]  | Fairlight Consulting
  __/\__  ||| "I'm talking for free...   | http://www.fairlite.com
  |||   It's a New Religion..."  | [EMAIL PROTECTED]
\/||| PGP Public Key available via finger @iglou, or Key servers