Re: setting limit in .muttrc

2000-02-16 Thread Frank Joerdens

That works!

Thanks,

Frank


On Tue, Feb 15, 2000 at 11:20:10AM -0500, Mike Markowski wrote:
 On Tue, Feb 15, 2000 at 05:03:05PM +0100, Frank Joerdens wrote:
  Hmm, doesn`t work here. Upon launching mutt, I get the error
  
  /home/frank/.muttrc, line 1: too few arguments
 
 Sorry.  I could've sworn that worked when I tried it...  Well, in the
 past few minutes multiple tests of the following seem to work in 1.0.1i:
 
   folder-hook /var/mail/mm "push 'l ! ~f \"Mail System Internal Data\"'\\n"
 
 (Note that I changed the '.' to my mail spool file.)
 
  Wouldn't it be nice to do this directly, e.g. via
  
  set limit ! ~f "Mail System Internal Data"
  
  or is there another way to do it?
 
 I used a folder-hook so that when returning to my main folder, it
 would again execute the 'push'.  But I'm 2 weeks new to mutt, so I
 expect there are probably better solutions...
 
   Mike
 
  Cheers, 
  Frank
  
  
  On Mon, Feb 14, 2000 at 01:29:26PM -0500, Mike Markowski wrote:
   I use this:
   
 folder-hook . ;push 'l ! ~f "Mail System Internal Data"'\n
   
   and it seems to do the job.
   
   Maybe someone can explain why it doesn't work without that initial
   semicolon, though!  :-)
   
 Thanks,
 Mike
   
   
   On Mon, Feb 14, 2000 at 06:56:41PM +0100, Frank Joerdens wrote:

Is it possible to configure mutt to not show the message  DON'T DELETE
THIS MESSAGE -- FOLDER INTERNAL DATA which is generated by my IMAP/POP3
server?

-- 
frank joerdens   

joerdens new media  e: [EMAIL PROTECTED]
heinrich-roller str. 16/17  t: +49 30 44055470
10405 berlinf: +49 30 44055475
germany h: http://www.joerdens.de

pgp fingerprint: 
73D0 C6C1 931D 9E0E D94B  1CB5 6A31 B70E 9907 3D95



Re: subscribe vs. lists

2000-02-16 Thread Charles Cazabon

Thomas Roessler [EMAIL PROTECTED] wrote:
 
 Sorry, the new subscribe command is equivalent to what was formerly
 known as "lists".  "lists" is essentially a weaker version now which
 only affects the list-reply function.
 
 (Partially, the naming is due to the fact that I couldn't think
 about a better name than "lists" for known, but unsubscribed lists -
 "unsubscribe" would have been against the systematic of the un*
 commands.)

What about 'nonsubscribe'?

Charles
-- 

Charles Cazabon  [EMAIL PROTECTED]
Any opinions expressed are just that -- my opinions.




Re: GPG problem

2000-02-16 Thread Sean F Rima

Hi Edmund!

On Wed, 16 Feb 2000, Edmund GRIMLEY EVANS wrote:

 I attach a public key with Esck, then I sign the message (with the
 same key). Why is the signature then bad? Attaching an ordinary file
 doesn't cause the same problem.
 
 Is it because I replace gpg-2comp by gpg in gpg.rc? If so, where was I
 supposed to get gpg-2comp from?
 
 Edmund
 

I got my gpg-2comp via the Mutt home page. And yes I tested your sig with
the key you sent and it was a bad sig. I tested sending mine the same way
and it worked okay. 

Sean
-- 
Linux User: #124682 ICQ: 679813
My Current Uptime is 10d, 12h and 14m on Linux 2.2.14
It said "Needs Windows 95 or better". So I installed Linux...

 PGP signature


gpg: Can't check signature: unknown digest algorithm

2000-02-16 Thread Adam Sherman

I still cannot figure out why this is happening. I tried setting
pgp-micalg to all three of the possible algorithyms and I still get
this wierd error:

gpg: Can't check signature: unknown digest algorithm

What am I doing wrong? (mutt 1.1.3) I'm not using the gpg-comp
script...

I don't even know where to start, what information should I send to
the list?

Thanks,

A.

-- 
Adam Sherman
[EMAIL PROTECTED]
+1 (613) 223-5746
 PGP signature


Re: only show new mails / remove new tag

2000-02-16 Thread Mikko Hänninen

Thomas Mueller [EMAIL PROTECTED] wrote on Wed, 16 Feb 2000:
 No, I only see really new messages, and not the whole thread where the
 new message is in  :-/

Oh, I misunderstood you originally.  As far as I know, you can't limit
the view to specific but full threads only.  All the limits work
per-message, not per-thread.

The only thing that I could think of that might help you is the
collapse-thread functionality, esc-v and esc-V by default.  Threads with
new messages in them are shown with a "n".


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 /
Woe unto them that rise up early in the morning -- Isaiah 5:11



Re: gpg: Can't check signature: unknown digest algorithm

2000-02-16 Thread Adam Sherman

On Wed, Feb 16, 2000 at 04:34:19PM -0500, Bennett Todd wrote:
 2000-02-16-16:22:11 Adam Sherman:
  I still cannot figure out why this is happening. I tried setting
  pgp-micalg to all three of the possible algorithyms and I still
  get this wierd error:
 
  gpg: Can't check signature: unknown digest algorithm
 
  What am I doing wrong? (mutt 1.1.3) I'm not using the gpg-comp
  script...
 
  I don't even know where to start, what information should I send
  to the list?
 
 I still don't know what's going wrong with your sigs, but I think
 it's more basic than choice of algorithm. Leave that default. Your
 problem seems to be that your sigs aren't getting encoded. I
 attach the last message from you. Compare the way your sig looks
 (like a little barf of binary bits) with e.g. my sigs, which are
 ascii-armour encoded. Note that I'm letting mutt default in its
 attaching of your message, so the whole attachment is getting
 quoted-printable encoded, because mutt saw non-ASCII bits in it.

I have --armor in the gpg sign command... Why is this happening?

 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 ˆ?¨ávB-· ¨™ø#¶Jǽ
 

Thanks,

A.

-- 
Adam Sherman
[EMAIL PROTECTED]
+1 (613) 223-5746
 PGP signature


Re: gpg: Can't check signature: unknown digest algorithm

2000-02-16 Thread Thomas Roessler

On 2000-02-16 16:22:11 -0500, Adam Sherman wrote:

 What am I doing wrong? (mutt 1.1.3) I'm not using the gpg-comp
 script...

Your problem certainly doesn't have anything to do with the micalg
value.  Most probably, the gpg-comp script is at fault with this,
since the signature seems to be a bit strange by itself.

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




How to change enviornment variables while in mutt

2000-02-16 Thread auto15764

Hi, I basically need to be able to alter QMAILHOST, QMAILUSER and QMAILNAME 
to change the appearence of out going mail. No amount of header altering 
overwrites those variables.
I tried using set signature="~/profiles/user1|" but that didn't work. I 
figured it was due to the shell script only setting the varibles for that 
shell and not the shell I am using. I tried using set signature="'source 
~/profiles/user1|'" but it complains about being unable to find source (its 
a bash shell command). So does anyone have any solutions to this tricky 
problem. I am using folder-hooks to use the set variable.

Thanks


IMPORTANT NOTICE:  If you are not using HushMail, this message could have been read 
easily by the many people who have access to your open personal email messages.
Get your FREE, totally secure email address at http://www.hushmail.com.





Re: BUFFY_SIZE option

2000-02-16 Thread Thomas Roessler

On 2000-02-16 15:28:43 +0800, Sverre Slotte wrote:

 I remember having read ("Life with Unix" by somebody Ressler?)
 that Biff was a dog who lived with its owner in Berkeley (in the
 beginning of the 1980s?). Biff used to bark at the mailman.
 Further down the hall from lived some of the BSD-hackers, and
 they dedided to call the mail-notification program "biff".

From the jargon file:

| :biff: /bif/ /vt./  To notify someone of incoming mail.  From
|the BSD utility `biff(1)', which was in turn named after a
|friendly golden Labrador who used to chase frisbees in the halls
|at UCB while 4.2BSD was in development.  There was a legend that
|it had a habit of barking whenever the mailman came, but the
|author of `biff' says this is not true.  No relation to {B1FF}.

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




Save, but don't delete.

2000-02-16 Thread Scott A . McIntyre

Hi.

What's the best way of telling mutt that when I save a message that I
don't want it to mark it as deleted?  I'm most interested in setting
this per folder.

Short of perhaps rebinding "s" such that it does a toggle-unlink before
save-message within a folder-hook (if that's even possible) is there a
better way?

Thanks.

Scott




Re: Save, but don't delete.

2000-02-16 Thread Mikko Hänninen

Scott A . McIntyre [EMAIL PROTECTED] wrote on Wed, 16 Feb 2000:
 What's the best way of telling mutt that when I save a message that I
 don't want it to mark it as deleted?  I'm most interested in setting
 this per folder.

Rebind the s key to copy-message.

 Short of perhaps rebinding "s" such that it does a toggle-unlink before
 save-message within a folder-hook (if that's even possible) is there a
 better way?

I don't see how $toggle-unlink comes to play here, that's related to
message sending, but I think you have the right idea here.

Create a set of folder-hooks which bind s to either save-message or
copy-message as desired, and you've got the functionality that you want,
I think.


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 /
This signature is not here. (There are no hidden messages on this line.)



Re: Save, but don't delete.

2000-02-16 Thread Marco Goetze

On Wed, Feb 16 2000, at 09:44 -0500, Scott A . McIntyre wrote:
What's the best way of telling mutt that when I save a message that I
don't want it to mark it as deleted?  I'm most interested in setting
this per folder.

How about the copy-message function, bound to C (by default)?


Marco



edit from

2000-02-16 Thread Brian

In mutt-1.1.2 I am no longer able to edit my from field with Escf

the binding is there, and the same binding works in mutt-1.0, so i am
quite confused.

Did it break, or am I doing something wrong?

-Brian



Re: edit from

2000-02-16 Thread Mikko Hänninen

Brian [EMAIL PROTECTED] wrote on Wed, 16 Feb 2000:
 In mutt-1.1.2 I am no longer able to edit my from field with Escf

 Did it break, or am I doing something wrong?

I'm using 1.1.3 and it works with that, and likewise with my copy of
the 1.1.2 binary.  It *sounds* like it's a local setting issue...


What happens when you press Escf, do you get "key not bound" or what?
Have you tried binding the function to some other key, in the way of
testing?


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 /
"How long is this Beta guy going to keep testing our stuff?"



GPG problem

2000-02-16 Thread Edmund GRIMLEY EVANS

I attach a public key with Esck, then I sign the message (with the
same key). Why is the signature then bad? Attaching an ordinary file
doesn't cause the same problem.

Is it because I replace gpg-2comp by gpg in gpg.rc? If so, where was I
supposed to get gpg-2comp from?

Edmund

Here's the key, in case it helps:

-BEGIN PGP PUBLIC KEY BLOCK-
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org

mQGiBDiprYkRBACRAOocTtWEkIkfMf2Oan2J5zzpaye/Lw5Fn7QwZGkJsDbo94bO
PMIwjrJA6GBRhuiVfLnxt5+W8ndSRGIVtjaEiNgTB0tPdSpZmM8bkN70SgzH/zQM
Ftj//hyLEYH8Y4XP3ghTQOzeoT5iCXhBuvYqZ8HwGe0wCqNXXDCgkbsgBwCgr/I9
dPLHUsTLjSRVCz848uXZsJ0D/05A9sOT6XYEepfjOQ+gRpdxUNMYiIOJvViv9iqG
vWma0DI5Av5nUDD9O4OAbxb7ODVVS/MiRvZ8DmyFX6o+IPLojVFRLvntOK+b2ex3
6bwHo6PLw1iXgNsvPi5ZBrqLe15xwxssI1J5+jvN85UNDBxc3UpwErufb0MOWj5t
SeijA/97tP++Gq75g8thjdScDH7HqhqxpdKle7NYoQYCWde4GJJdVIpVcbznH/k0
w18KdB3ENOxRyFG/7ZGlHv5sGk4lDmDPYbNyXpj22Tt0rqIcyaokLFRlNWawdyWm
Ixm3aPYEbxrYGkc3DJqW1HdZZDgU9g/IDxllB2om8RS8M0OVq7QnRWRtdW5kIEdS
SU1MRVkgRVZBTlMgPGVkbXVuZG9AcmFuby5vcmc+iFYEExECABYFAjiprYkECwoE
AwMVAwIDFgIBAheAAAoJEOjmZ3IkX3H6tZAAn0Bl3jURufeUIDHc6MRXcyX1FO4Q
AJ9WRA37vrvHVGyAMgfo4WXFh7cnl7kBDQQ4qa2YEAQA0/yjHv17R+A+ao35FygC
oBDWpPhzo+q2+YaRq4uvvt+SqXeMIV7g2FYOxAG90ZxBfVxKd5EdoPvWuewSYC3z
o9FUVictVnYXuydDqGsX4HfeCfsEwP5amWhEMRM6ApIqr217r5NUmqHGp+jMTTI4
1rEbBYd+UdGOtaUbjs4Cc/cABAsD/RQdwJI+iiCfluMt4gvNmH8sU60e3cN94HqF
XRMxx1Y017/mjd7nVuQw1xcHTjXEnn2GZuZcD/ZZ0KomoIk5h6n4YjkR904hLVBO
l3EpeDi5/pZWW6T64/2/tPsF8w/L6YjW+9+VI1V1bzayjD8xdKCYdNIkKT21RXrx
+fwKfLSViEUEGBECAAYFAjiprZgACgkQ6OZnciRfcfreeQCfdMfWZBNwnrONbbJx
SZY01/3lkNAAmJfLZaHwk7MCwKgWkboXJxxW26o=
=Qnz+
-END PGP PUBLIC KEY BLOCK-

 =?utf-8?Q?PGP-=C5=9Dlosilo_0x245F71FA=2E?=
 PGP signature


Re: only show new mails / remove new tag

2000-02-16 Thread Thomas Mueller

Hi Mikko!

  That is why I only want to see threads with new
  messages! How can I tell mutt to hide all mails that are not marked as
  new?
 
 Limit to new only:
 
   l~Nenter
 
 However I'm not sure if that will help you, Mutt might still thread even
 the hidden messages.

No, I only see really new messages, and not the whole thread where the
new message is in  :-/

  My other problem is that I couldn't find out how to remove the 'new'
  flag from all mails.
 
 Tag all new messages and then use toggle-new on them.
   T~Nenter;N

Yes, that's it! Thanks!


-- 
mfg Thomas Mueller - http://tmueller.home.pages.de



Re: gpg: Can't check signature: unknown digest algorithm

2000-02-16 Thread Brendan Cully

On Wednesday, 16 February 2000 at 16:51, Adam Sherman wrote:
 On Wed, Feb 16, 2000 at 04:34:19PM -0500, Bennett Todd wrote:
  2000-02-16-16:22:11 Adam Sherman:
  
  I still don't know what's going wrong with your sigs, but I think
  it's more basic than choice of algorithm. Leave that default. Your
  problem seems to be that your sigs aren't getting encoded. I
  attach the last message from you. Compare the way your sig looks
  (like a little barf of binary bits) with e.g. my sigs, which are
  ascii-armour encoded. Note that I'm letting mutt default in its
  attaching of your message, so the whole attachment is getting
  quoted-printable encoded, because mutt saw non-ASCII bits in it.
 
 I have --armor in the gpg sign command... Why is this happening?
 
  Content-Type: application/pgp-signature
  Content-Disposition: inline
  
  ˆ?¨ávB-· ¨™ø#¶Jǽ

Maybe it's your key. Have you successfully encoded/decoded anything
from the command line with gpg? From your last message I get the
following:

[-- PGP output follows (current time: Wed Feb 16 17:36:38 2000) --]
gpg: standalone signature of class 0xff
gpg: Signature made Wed 31 Dec 1969 06:59:59 PM EST using ? key ID

gpg: Can't check signature: unknown digest algorithm
[-- End of PGP output --]

which looks like gpg handling a lot of null data. If you can encode
from the command line, then maybe you've got a file-descriptor passing
problem in gpg.rc?

-Brendan
 PGP signature


Re: GPG problem

2000-02-16 Thread Edmund GRIMLEY EVANS

Thanks for telling me where to get gpg-2comp from, but it doesn't
solve the problem.

As far as I can tell, gpg-2comp is for PGP-compatibility. I'm only
using GPG.

It's odd that no one can reproduce my problem. I would guess that
perhaps something is getting confused by the presence of an attached
public key while trying to verify the signature ...

Edmund



Re: gpg: Can't check signature: unknown digest algorithm

2000-02-16 Thread Matthew Hawkins

On 2000-02-16 16:22:11 -0500, Adam Sherman wrote:
 I still cannot figure out why this is happening. I tried setting
 pgp-micalg to all three of the possible algorithyms and I still get
 this wierd error:
 
 gpg: Can't check signature: unknown digest algorithm

Well your key isn't being ascii armoured, for starters.  The other
tricky thing I found out is that you _must_ set pgp_strict_enc or your
GPG key will not verify.  It defaults to set, but naturally can be
overridden.  One sample muttrc out there overrides it to unset...

With GPG you'll want the sha1 micalg.

-- 
Matt



moving to pine line dated folders

2000-02-16 Thread Jason Helfman

I remember seeing this in the manual or a faq somewhere, but I am
looking how I could move older messages to a date like folder that pine
does?

-- 
/helfman

"At any given moment, you may find the ticket to the circus that has always been
in your possession."



No Subject

2000-02-16 Thread Jason Helfman




Re: moving to pine line dated folders

2000-02-16 Thread Mikko Hänninen

Jason Helfman [EMAIL PROTECTED] wrote on Wed, 16 Feb 2000:
 I remember seeing this in the manual or a faq somewhere, but I am
 looking how I could move older messages to a date like folder that pine
 does?

Use something like:

set mbox=+mailbox-`date '+%Y-%b'`
set move=ask-yes

Adjust name and the format of the date command according to your
preferences...


I hope that's what you were looking for,
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 /
Happiness is always just a remembrance away.



Re: How to change enviornment variables while in mutt

2000-02-16 Thread Mikko Hänninen

[EMAIL PROTECTED] [EMAIL PROTECTED] wrote on Wed, 16 Feb 2000:
 Hi, I basically need to be able to alter QMAILHOST, QMAILUSER and QMAILNAME 
 to change the appearence of out going mail. No amount of header altering 
 overwrites those variables.

Create a wrapper shell script which sets the variables and then calls
qmail-inject (or the qmail sendmail wrapper if you prefer that).  That's
the only way to change those environment variables from the values that
they had when Mutt started.

 I tried using set signature="~/profiles/user1|" but that didn't work. I 
 figured it was due to the shell script only setting the varibles for that 
 shell and not the shell I am using.

That is correct.  The settings don't affect the environment that Mutt
runs in.  There is no way, that I know of, to change environment
variables of a process from a sub-process.  So that approach can't
really work.

 So does anyone have any solutions to this tricky 
 problem. I am using folder-hooks to use the set variable.

Well, look above.  However, I think there's an easier way than using
QMAILHOST, QMAILUSER and QMAILNAME.  The qmail-inject man page says
that if a From header is supplied, it is *not* overwritten by default.
So it would be simpler to just specify the From you want in Mutt, and
not worry about the environment variables at all.  If your From header
is getting overwritten, then the only reason that can happen as far as
I can tell is that you also have the variable QMAILINJECT containing
a "f".  Remove that to get rid of the rewriting.  If you require that
for something else, you may just create a wrapper script for Mutt that
unsets the variable for Mutt sessions only.

In any case, I suggest man qmail-inject, it's good reading.


Hope this helps,
Mikko
PS. Please use [EMAIL PROTECTED] (not the gbnet.net address) when
posting to the list, thanks.
-- 
// 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 sentence does, in fact, not have the property it claims not to have.