Editing headers in Vim + clear text GPG signing

2001-10-01 Thread mutt
I'm trying out some ways to clear text sign a message in mutt, using :%!gpg -eas Unfortunately, all headers (including "to") are signed, effectively making these headers useless. Is there a way to specify to this filter only to sign/encrypt the actual message body? -- Frederik Vanrenterghem

mailinglist not accepting mail from not-subscribed users

2001-10-01 Thread mutt
Hi, it seems like the mailinglist is not accepting mail when I use the standard from address (since I'm subscribed with an address specifically for this list). Currently I just change the from-address, but I'm wondering why the list is set up this way. A lot of people don't subscribe to every mai

Re: mailinglist not accepting mail from not-subscribed users

2001-10-01 Thread David T-G
Frederik -- ...and then [EMAIL PROTECTED] said... % Hi, % % it seems like the mailinglist is not accepting mail when I use the Yep. % standard from address (since I'm subscribed with an address specifically % for this list). Currently I just change the from-address, but I'm You can use a sen

Re: Editing headers in Vim + clear text GPG signing

2001-10-01 Thread Suresh Ramasubramanian
[EMAIL PROTECTED] [01/10/01 11:47 +0200]: > I'm trying out some ways to clear text sign a message in mutt, using > :%!gpg -eas Instead, use macro compose S "Fgpg -a --clearsign -u 0xEDEDEFB9" and when you have hit :wq and come back to mutt (and are supposed to hit "y" for the mail to go out),

Re: Hiding read messages in a newsgroup?

2001-10-01 Thread Ailbhe Leamy
On (30/09/01 14:33), Benjamin Smith wrote: > On Sat, Sep 29, 2001 at 10:14:19PM -0400, Matej Cepl wrote: > > Maybe, that I am asking too much, but my experience with mutt is > > that everything is possible -- one just has to know, what to put > > in .muttrc. So, > > > > would it be possible to hi

Re: strange 1.3.22 to 1.3.22.1 compile problem

2001-10-01 Thread Thomas Roessler
The only thing this patch does is to fix a compilation problem. If you successfully built and installed 1.3.22 (as it seems you did), there's no need to upgrade to 1.3.22.1. On 2001-10-01 12:33:44 +0800, Rino Mardo wrote: >Date: Mon, 1 Oct 2001 12:33:44 +0800 >From: Rino Mardo <[EMAIL PROTECTE

resend-message (esc e) not honouring $record

2001-10-01 Thread Andre Majorel
When I send a new message using an older one as a template (esc e), the new message is not saved to $record. Is that deliberate or an overlook ? -- André Majorel http://www.teaser.fr/~amajorel/> (Not speaking for my employer, etc.)

Problems building mutt

2001-10-01 Thread Viktor Rosenfeld
Hi, I'm trying to build mutt from sources to include the pgp_outlook_compat patch. This works fine, the problem is that the compressed folder support is not included. I've traced the problem to a call of autoheader in the makefile. After `./configure --enable-compressed` the file config.h cont

Mutt and NNTP on Debian

2001-10-01 Thread mutt
Hi, it seems there are a few possibilities to enable mutt to read newsgroups, but these require patching the source. Since I'm a Debian user, I'd like to be able to make a .deb from the patched version. If I apply the patch http://mutt.kiev.ua/download/mutt-1.3.22.1/patch-1.3.22.1.vvv.nntp.gz to

Re: Problems building mutt

2001-10-01 Thread David T-G
Viktor -- ...and then Viktor Rosenfeld said... % Hi, Hello! % % I'm trying to build mutt from sources to include the pgp_outlook_compat % patch. This works fine, the problem is that the compressed folder % support is not included. Forgive me for aasking such a basic question, but did you ap

Error sending message, child exited 1 ().

2001-10-01 Thread Philipp Boksberger
Hi, I intalled mutt and exim some days ago ane everything worked fine. But now I have problems in sending mails. I get the following error-message: Error sending message, child exited 1 (). What does this mean? Thanks, Philipp

Re: Hiding read messages in a newsgroup

2001-10-01 Thread Matěj Cepl
On Sun, Sep 30, 2001 at 18:23:40PM +0200, Rene Clerc wrote: > You could put the following in your .muttrc: > folder-hook "push \"l~N\n\"" > and probably extend it to show old messages to (i have mark_old > unset). Yes!!! folder-hook ^nntp "push ' ~N'" folder-hook . "push ' '" seem to make a t

editing headers in vim + clear text signing

2001-10-01 Thread Frederik Vanrenterghem
I'm trying out some ways to clear text sign a message in mutt, using :%!gpg -eas Unfortunately, all headers (including "to") are signed, effectively making these headers useless. Is there a way to specify to this filter only to sign/encrypt the actual message body? -- Frederik Vanrenterghem

Re: mailinglist not accepting mail from not-subscribed users

2001-10-01 Thread Suresh Ramasubramanian
David T-G [01/10/01 06:17 -0400]: > % Hi, > % standard from address (since I'm subscribed with an address specifically > % for this list). Currently I just change the from-address, but I'm > You can use a send-hook for that to make things easier, BTW :-) Also, set envelope_from -suresh

Mutt and NNTP on Debian

2001-10-01 Thread Frederik Vanrenterghem
Hi, it seems there are a few possibilities to enable mutt to read newsgroups, but these require patching the source. Since I'm a Debian user, I'd like to be able to make a .deb from the patched version. If I apply the patch http://mutt.kiev.ua/download/mutt-1.3.22.1/patch-1.3.22.1.vvv.nntp.gz to

Re: Mutt and NNTP on Debian

2001-10-01 Thread Niels den Otter
Frederik, On Monday, 1 October 2001, [EMAIL PROTECTED] wrote: > it seems there are a few possibilities to enable mutt to read > newsgroups, but these require patching the source. Since I'm a Debian > user, I'd like to be able to make a .deb from the patched version. If I > apply the patch > http

Re: Problems building mutt

2001-10-01 Thread Viktor Rosenfeld
David T-G wrote: > Viktor -- > > ...and then Viktor Rosenfeld said... > % Hi, > > Hello! > > > % > % I'm trying to build mutt from sources to include the pgp_outlook_compat > % patch. This works fine, the problem is that the compressed folder > % support is not included. > > Forgive me for

Re: Problems building mutt

2001-10-01 Thread Dave Ewart
On Monday, 01.10.2001 at 17:19 +0200, Viktor Rosenfeld wrote: > ... > Yes, the patch is included in the Debian source distribution and is > correctly applied. `mutt -v` gives me (among other things) -COMPRESSED, > which wouldn't be there, if there was no compressed-folder patch. Shouldn't it be

Re: Problems building mutt

2001-10-01 Thread René Clerc
* Viktor Rosenfeld <[EMAIL PROTECTED]> [01-10-2001 17:22]: | Yes, the patch is included in the Debian source distribution and is | correctly applied. `mutt -v` gives me (among other things) -COMPRESSED, | which wouldn't be there, if there was no compressed-folder patch. Perhaps a very stupid qu

Re: Error sending message, child exited 1 ().

2001-10-01 Thread Suresh Ramasubramanian
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philipp Boksberger [01/10/01 00:52 +0200]: > I intalled mutt and exim some days ago ane everything worked fine. But > now I have problems in sending mails. I get the following error-message: > Error sending message, child exited 1 (). > What does

Re: resend-message (esc e) not honouring $record

2001-10-01 Thread Justin R. Miller
Thus spake Andre Majorel ([EMAIL PROTECTED]): > When I send a new message using an older one as a template (esc e), > the new message is not saved to $record. Is that deliberate or an > overlook ? Yeah, I've noticed that with both mbox and IMAP setups in Mutt. -- | Justin R. Miller / [EMAIL PR

Re: editing headers in vim + clear text signing

2001-10-01 Thread David Champion
On 2001.10.01, in <[EMAIL PROTECTED]>, "Frederik Vanrenterghem" <[EMAIL PROTECTED]> wrote: > I'm trying out some ways to clear text sign a message in mutt, using > :%!gpg -eas > > Unfortunately, all headers (including "to") are signed, effectively > making these headers useless. Is there

Re: Encrypt and mailing lists

2001-10-01 Thread Dave Goodrich
There was a thread on the gnupg maillist about this last week. Off the top of my head it involved signing/encrypting with multiple recipients, this allows 'any' of the recipients to verify/decrypt on their own. I'd think you could add a command to do what you want. DAve http://lists.gnup

Re: Hiding read messages in a newsgroup

2001-10-01 Thread Ailbhe Leamy
On (01/10/01 00:12), Mat?j Cepl wrote: > seem to make a trick. Thanks a lot. I am now really persuaded > that mutt is able to do everything (except for that buttered > bread, I know)! And help on this list is really terrific. Thanks > again. And for your next trick, you can learn to send message

Re: Problems building mutt

2001-10-01 Thread Viktor Rosenfeld
Okay, it appears that the compressed-folder patch supplied with Debian doesn't do what it's supposed to do. Somehow it messes up source configuration. Anyway, copying the actuall patch by rr to debian/patches solved my problems. Now I finally have compressed-folder support and outlook-compati

Re: Mutt and NNTP on Debian

2001-10-01 Thread Waldemar Brodkorb
>From the keyboard of Frederik, > Hi, > > it seems there are a few possibilities to enable mutt to read > newsgroups, but these require patching the source. Since I'm a Debian > user, I'd like to be able to make a .deb from the patched version. If I > apply the patch > http://mutt.kiev.ua/downlo

Re: Error sending message, child exited 1 ().

2001-10-01 Thread Petr Hlustik
On Mon, Oct 01, 2001 at 09:01:34PM +0530, Suresh Ramasubramanian wrote: > Hash: SHA1 > > Philipp Boksberger [01/10/01 00:52 +0200]: > > I intalled mutt and exim some days ago ane everything worked fine. But > > now I have problems in sending mails. I get the following error-message: > > Erro

Re: Error sending message, child exited 1 ().

2001-10-01 Thread Will Yardley
Philipp Boksberger wrote: > I intalled mutt and exim some days ago ane everything worked fine. But > now I have problems in sending mails. I get the following error-message: > > Error sending message, child exited 1 (). what do your mail logs say it means? w -- GPG Public Key: http://in

Re: resend-message (esc e) not honouring $record

2001-10-01 Thread Ben Reser
On Mon, Oct 01, 2001 at 03:37:42PM +0200, Andre Majorel wrote: > When I send a new message using an older one as a template (esc > e), the new message is not saved to $record. Is that deliberate > or an overlook ? It's deliberate. Search the archives this discussion has been had several times.

Solved somewhat [was: Re: Can't get the vvv-nntp-patch working...]

2001-10-01 Thread Piet Delport
On Tue, 25 Sep 2001 at 06:20:33 +0200, Piet Delport wrote: [snip mutt and leafnode not working] > I think the problem is leafnode related, as mutt works perfectly on my > ISP's news server. > > Version info: > Mutt 1.3.22.1i (2001-08-30) > Leafnode+ NNTP Daemon, version 2.14 > > Any

Re: editing headers in vim + clear text signing

2001-10-01 Thread Piet Delport
On Mon, 01 Oct 2001 at 11:19:43 -0500, David Champion wrote: > On 2001.10.01, in <[EMAIL PROTECTED]>, > "Frederik Vanrenterghem" <[EMAIL PROTECTED]> wrote: > > I'm trying out some ways to clear text sign a message in mutt, using > > :%!gpg -eas > > > > Unfortunately, all headers (including

Re: editing headers in vim + clear text signing

2001-10-01 Thread Dave Price
thanks for the great one-liner, piet ... that is why i read these lists aloha, dave On Tue, Oct 02, 2001 at 12:20:49AM +0200, Piet Delport wrote: > On Mon, 01 Oct 2001 at 11:19:43 -0500, David Champion wrote: > > On 2001.10.01, in <[EMAIL PROTECTED]>, > > "Frederik Vanrenterghem" <[EMAIL PRO

Re: editing headers in vim + clear text signing

2001-10-01 Thread Wayne Chapeskie
On Tue, Oct 02, 2001 at 12:20:49AM +0200, Piet Delport wrote: > You can do it a bit more elegantly[1] with this ex one-liner: > > 1;/^$/+1,$!gpg --clearsign Back in the old days days of PGP 2.x, someone pointed out that you can use a couple of macros to handle common PGP operations within vi. U

Re: strange 1.3.22 to 1.3.22.1 compile problem

2001-10-01 Thread Rino Mardo
On Mon, Oct 01, 2001 at 02:55:48PM +0200 or thereabouts, Thomas Roessler wrote: > The only thing this patch does is to fix a compilation problem. If > you successfully built and installed 1.3.22 (as it seems you did), > there's no need to upgrade to 1.3.22.1. > so it means that my copy of 1.3.