Random Signature

[Daniel Gerber]

This might just be an old one...

I tried to set mutt (1.0.1/1.1.8/1.1.9) up for random signatures but it didn't work. 
Following the manual I made a '.sigfixed' file in $HOME and a directory '.Sig' with 
the alternating parts. I had to manually insert the line '#define ENABLE_RANDOM_SIG' 
in config.h (compile time option --enable-random-sig didn't do anything). Still not 
working. Do I miss a patch or something like that..?

Thanks!

(OS is S.U.S.E. Linux 2.0.36 and 'mutt -version' doesn't indicate a RANDOM_SIG option 
being present)

-- 
__
DANIEL GERBER
___http://www.cx.unibe.ch/~dgerber

Re: I liked the old "weed" behavior (was [Announce] mutt-1.1.9 ...)

[Thomas Roessler]

On 2000-03-14 15:53:27 -0500, Eric Boehm wrote:

> I am assuming the reason for the change was consistency.

Precisely.  You reply to or forward what you are seeing.

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

Re: Mutt 1.1.9 about 3-4x slower than mutt 1.0 (was Re: [Announce] mutt-1.1.9 is out - RELEASE CANDIDATE!)

[Thomas Roessler]

On 2000-03-14 21:23:36 -0500, Eric Boehm wrote:

>> I have found that mutt 1.1.9 is about 4x slower
>> reading a 7.4 MB mail file with 1451 messages in it
>> than mutt 1.0.

You are transferring almost 8 MBit/s with the new mutt
versions.  This looks like the bottleneck is really NFS
and your Ethernet, not mutt.  With the old mutt, you get
more than 34 MBit/s, which looks like your system's local
NFS cache.

> -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL
> -USE_FLOCK

This output confirms Brendan's suspicion.  More precisely,
you have one of the few system configurations which get
into locking hell with old mutt versions.

What happens is this: Your system has a mail spool which
doesn't require additional privileges to set up
(-USE_SETGID).  This means that dotlocking (+USE_DOTLOCK)
is done within mutt, and not in an external program.
However, this actually breaks fcntl locking by opening and
closing the spool file _after_ doing the fcntl lock,
thereby actually releasing it.

All this affects performance due to the fact that fcntl
locking is supposed to invalidate any data the NFS client
may have cached for the file in question.  While this may
seriously reduce performance, it's important for
reliability: If the cache isn't invalidated, mutt has no
possibility to reliably know whether or not a folder it's
going to synch has been modified by an external program,
e.g., by new mail which was delivered.  

That is, you are actually in a situation in which you may
lose mail under certain circumstances with the old
versions of mutt.

Note that maildir folders may actually lead to a
performance improvement for you:  This folder format
doesn't require any locking, that is, mutt will fully
benefit from the NFS client's cache.

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

Re: mutt shouldn't write back unchanged mh messages

[Thomas Roessler]

On 2000-03-14 15:51:08 -0500, Scott Schwartz wrote:

> In my experience mh works well enough, but mutt makes
> some incorrect assumptions that have painful
> consequences.

Please look at the unstable branch (i.e., the
just-released 1.1.9).  It should behave much better.

However, you may wish to notice that there is still a
problem with message flags.  From the mh point of view (as
far as I understand it), these flags should be stored in
the .mh_sequences file - which is in paricular true for
the unseen sequence. However, there doesn't seem to be a
well-defined locking mechanism for that file, which means
that we can't update it safely.  Ups.

Thus, I'd really suggest you change from mh folders to
maildirs which can do essentially _everything_ (with the
exception of attachment deletion ;-) without changing the
underlying files, and without locking.

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

Re: Q: new mail

[Marc van Dongen]

Mikko Hänninen ([EMAIL PROTECTED]) wrote:

: Marc van Dongen <[EMAIL PROTECTED]> wrote on Tue, 14 Mar 2000:
: > Is there any way to tell mutt to inform me if new
: > mail has arrived? At the moment I am using xbiff
: > for that purpose but I would like to get rid of it.
: 
: Sure.  List your incoming mailboxes with the "mailboxes" command in
: your .muttrc.
: 
: For more info, look up the command's entry in the manual.

I'll have a look at it. Thanks!


Regards,


Marc

Re: Certificates update?

[Thomas Roessler]

On 2000-03-15 08:17:42 +0200, [EMAIL PROTECTED] wrote:

> Over the past few months I've seen the odd message on
> the list concerning the use of certifcates with Mutt.
> I also remember someone posting about the use of
> OpenSSL and potentially calling this from within Mutt.
> I was wondering whether anything further has come of
> this and what the future holds?

Recent Mutts can do IMAP over SSL.

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

Re: Mutt 1.1.9 about 3-4x slower than mutt 1.0 (was Re: [Announce] mutt-1.1.9 is out - RELEASE CANDIDATE!)

[Lars Hecking]

> I have found that mutt 1.1.9 is about 4x slower reading a 7.4 MB mail
> file with 1451 messages in it than mutt 1.0.
> 
> I tried this several times to eliminate the effects of caching. It took mutt
> 1.0 about 7.8 seconds to bring up the file, it took mutt 1.1.9 about 28.8
> seconds to bring up the same file.
> 
> I don't know if you would consider this a show stopper but it was enough for
> me to back out 1.1.9 and go back to 1.0.

 In addition to the NFS issues mentioned.

 I had an exchange about mutt 1.1.x slowness with tlr two weeks ago.
 I noticed the same slowdown after version 1.1.2. The slowdown occured
 even for small (a few dozen kB), local mailboxes. The explanation:
 I fixed charmap support, i.e. finally installed the charmaps-0.0 stuff
 into /usr/local/share/mutt/charmaps (/usr/local is mounted across the
 network).

 The slowdown rate is proportional to the number of different
 Content-Type/charset= headers in a mailbox file, apparently
 because the charmaps are loaded along with the messages.

 If you leave the same instance of mutt open and (c)hange mailboxes, the
 charsets should be cached.


 Convenient as they are, charsets are another feature that make it easier
 for ppl to shoot themselves (and others) in the foot. Now that my mutt
 is charset sensitive, I often find messages with big5, iso-2022-jp, or
 koi8-r, although none of the special characters are actually in the 
 message body (checked with vi in "C"). Free performance killer with
 every mail message.

Keeping text below signature on reply

[Jorge Godoy]

Hi!

Mutt uses some patterns to verify signatures and uses them to cut out
these and the text below it when replying a message.

On my system it's looking for the standard "--". On some messages
there are text below the signature of the people who wrote the message
that must be replied and when I try replying it, mutt cuts this text
off. Is there a way to avoid this?

Thanks,
--
Godoy.  <[EMAIL PROTECTED]> 

Setor de Publicações
Publishing Department   Conectiva S.A.

Re: listing number of messages in folder view

[Sergei Kolobov]

Benjamin Korvemaker wrote:
> Is there a way to list the number of messages that are in a folder when
> listing the folders? (Checking the format strings in the manual doesn't
> seem to indicate so, but I may have overlooked the right place.)  Even an
> indicator of which folders have old messages would be nice.  I'm using mutt
> 1.0 (do I just need to upgrade to a development version?) and maildirs.

Currently, there's no way to display number of new messages in folder
list. I also thought it might be useful so I have created a small patch
which adds few new options for folder_format variable:

  %n - number of new messages in the folder
  %o - number of old messages in the folder
  %m - total number of messages in the folder 

So my folder_format looks like this:

set folder_format="%2C %N %5n %5o %f"

This works only for Maildir folders (it might work for mh folders too
although I have not checked that).

My patch is against the development version (1.1.1i). I will test it
against the latest version, clean it up a little bit, add some
documentation and will probably post it to the list if there's any
interest.

Sergei

-- 
Sergei Kolobov

Can anyone help read this?

[Denis Chapligin]

Hi

How can i read this message? 'charset-hook windows-1251 cp1251' doesn't help.

From: "=?windows-1251?B?wOvr4CDD5eTo7OA=?=" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Subject: request
Date: Wed, 15 Mar 2000 11:43:24 +0200
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="=_NextPart_000_0071_01BF8E73.AB8EA9E0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Status: RO
Content-Length: 1319
Lines: 39

This is a multi-part message in MIME format.

--=_NextPart_000_0071_01BF8E73.AB8EA9E0
Content-Type: text/plain;
charset="windows-1251"
Content-Transfer-Encoding: quoted-printable

=C4=EE=E1=F0=FB=E9 =E4=E5=ED=FC! =CE=CE=CE  =C0=EB=E2=E8=F1, login: =
alvis, =EF=F0=EE=F1=E8=F2 =EF=F0=E5=E4=EE=F1=F2=E0=E2=E8=F2=FC =
=E4=EE=EC=E5=ED=ED=EE=E5 =E8=EC=FF www.alvis.kaliningrad.ru =
=CF=F0=EE=F8=F3 =EF=EE=E4=F2=E2=E5=F0=E4=E8=F2=FC. =C0=EB=EB=E0 =
=C3=E5=E4=E8=EC=E0.

--=_NextPart_000_0071_01BF8E73.AB8EA9E0
Content-Type: text/html;
charset="windows-1251"
Content-Transfer-Encoding: quoted-printable









=C4=EE=E1=F0=FB=E9 =E4=E5=ED=FC! =CE=CE=CE  =
=C0=EB=E2=E8=F1,=20
login: alvis, =EF=F0=EE=F1=E8=F2 =EF=F0=E5=E4=EE=F1=F2=E0=E2=E8=F2=FC =
=E4=EE=EC=E5=ED=ED=EE=E5 =E8=EC=FF http://www.alvis.kaliningrad.ru">www.alvis.kaliningrad.ru =
=CF=F0=EE=F8=F3=20
=EF=EE=E4=F2=E2=E5=F0=E4=E8=F2=FC. =C0=EB=EB=E0 =
=C3=E5=E4=E8=EC=E0.

--=_NextPart_000_0071_01BF8E73.AB8EA9E0--




--
Denis Chapligin

Re: Can anyone help read this?

[Edmund GRIMLEY EVANS]

Denis Chapligin <[EMAIL PROTECTED]>:

> How can i read this message? 'charset-hook windows-1251 cp1251' doesn't help.

The text/plain part contains this line:

äÏÂÒÙÊ ÄÅÎØ! ïïï  áÌ×ÉÓ, login: alvis, ÐÒÏÓÉÔ ÐÒÅÄÏÓÔÁ×ÉÔØ ÄÏÍÅÎÎÏÅ ÉÍÑ 
www.alvis.kaliningrad.ru ðÒÏÛÕ ÐÏÄÔ×ÅÒÄÉÔØ. áÌÌÁ çÅÄÉÍÁ.

I hope it wasn't confidential!

This message is in koi8-r. Presumably there's something wrong with
your charsets set-up if your mutt doesn't convert between cp1251 and
koi8-r for you.

Edmund

Re: Can anyone help read this?

[Denis Chapligin]

Hi

On Wed, Mar 15, 2000 at 02:05:05PM +, Edmund GRIMLEY EVANS wrote:
> > How can i read this message? 'charset-hook windows-1251 cp1251' doesn't help.
>
[skipped]
>
> I hope it wasn't confidential!
yes, i have read it before using some external tools.
> This message is in koi8-r. Presumably there's something wrong with
> your charsets set-up if your mutt doesn't convert between cp1251 and
> koi8-r for you.
>
How can i diagnose and resolve this problem?
--
Denis Chapligin

Re: Keeping text below signature on reply

[Jon Parise]

On Wed, Mar 15, 2000 at 08:22:47AM -0300, Jorge Godoy wrote:

> Mutt uses some patterns to verify signatures and uses them to cut
> out these and the text below it when replying a message.
> 
> On my system it's looking for the standard "--". On some messages
> there are text below the signature of the people who wrote the
> message that must be replied and when I try replying it, mutt
> cuts this text off. Is there a way to avoid this?

I don't believe it's mutt that's removing that text.  It's most
likely a function of your editor.

-- 
Jon Parise ([EMAIL PROTECTED])  .  Rochester Inst. of Technology
http://www.pobox.com/~parise/  :  Computer Science House Member

Re: Mutt 1.1.9 about 3-4x slower than mutt 1.0 (was Re: [Announce] mutt-1.1.9 is out - RELEASE CANDIDATE!)

[Eric Boehm]

> "Thomas" == Thomas Roessler <[EMAIL PROTECTED]> writes:
> "Lars" == Lars Hecking <[EMAIL PROTECTED]> writes:

Thomas> You are transferring almost 8 MBit/s with the new mutt versions.
Thomas> This looks like the bottleneck is really NFS and your Ethernet,
Thomas> not mutt.  With the old mutt, you get more than 34 MBit/s, which
Thomas> looks like your system's local NFS cache.

Thomas> -HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK

Thomas> This output confirms Brendan's suspicion.  More precisely, you
Thomas> have one of the few system configurations which get into locking
Thomas> hell with old mutt versions.

Thomas> What happens is this: Your system has a mail spool which doesn't
Thomas> require additional privileges to set up (-USE_SETGID).  This means
Thomas> that dotlocking (+USE_DOTLOCK) is done within mutt, and not in an
Thomas> external program.  However, this actually breaks fcntl locking by
Thomas> opening and closing the spool file _after_ doing the fcntl lock,
Thomas> thereby actually releasing it.

It sounds like you are saying that I should change the combination of 

+USE_DOTLOCK +USE_FCNTL -USE_FLOCK

to something else but it isn't clear to me what I should change it to.

Are there any changes I should make to the HP-UX configuration. That has

+USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK

Thomas> Note that maildir folders may actually lead to a performance
Thomas> improvement for you: This folder format doesn't require any
Thomas> locking, that is, mutt will fully benefit from the NFS client's
Thomas> cache.

I'm not sure that I want to do that as I sometimes use Netscape to read mail
folders. 

An additional point of information.

My mail is really downloaded with fetchmail from a POP server and then
processed with procmail. On occasion, mail may be delivered to my
workstation's sendmail. This should be no different than fetchmail's action
(since it delivers to port 25 and sendmail takes it from there).

Lars>  I had an exchange about mutt 1.1.x slowness with tlr two weeks ago.
Lars> I noticed the same slowdown after version 1.1.2. The slowdown
Lars> occured even for small (a few dozen kB), local mailboxes. The
Lars> explanation: I fixed charmap support, i.e. finally installed the
Lars> charmaps-0.0 stuff into /usr/local/share/mutt/charmaps (/usr/local
Lars> is mounted across the network).

Lars>  The slowdown rate is proportional to the number of different
Lars> Content-Type/charset= headers in a mailbox file, apparently because
Lars> the charmaps are loaded along with the messages.

Lars>  If you leave the same instance of mutt open and (c)hange mailboxes,
Lars> the charsets should be cached.

I usually do leave a single instance open.

Lars>  Convenient as they are, charsets are another feature that
Lars> make it easier for ppl to shoot themselves (and others) in the
Lars> foot. Now that my mutt is charset sensitive, I often find messages
Lars> with big5, iso-2022-jp, or koi8-r, although none of the special
Lars> characters are actually in the message body (checked with vi in
Lars> "C"). Free performance killer with every mail message.  

Is there a way to diable this "feature"?

-- 
Eric M. Boehm   [EMAIL PROTECTED]

Signature selection

[Terje Elde]

Hi all,

Being a employee of a Norwegian company I'm forced to have three different
signature files. One for my personal mail, one when I'm writing company
mail to a Norwegian email address, and one for all other business related
emails.

Hunting out business related email is easy at the start, but quickly
becomes a bit difficult. All incoming mail starts its life coming to a
mailing list, which procmail drops into a Maildir. Adding a folder-hook to
set my email to the business email, rather than my private email, is thus
easy, just as it'd be reasy to choose the right signature file if I only
had one, but is there any way I can manage to set mutt up to check the
domain I'm sending to, and set the correct sig?

Also, when I've replied to the customer, they sometimes reply to my reply
(those bastards :) and it ends up, as it should, in my inbox. When I reply
to it my email automagically gets set to the company email, because I'm
replying to a email sent to that address, but is there any way to catch this
to the signature can be set as well?

Lots of thanks if anybody can give me a hand here.

Terje

 PGP signature

Re: Random Signature

[Rob Reid]

At  3:57 AM EST on March 15 Daniel Gerber sent off:
> This might just be an old one...

It sure is!
 
>  I tried to set mutt (1.0.1/1.1.8/1.1.9) up for random signatures but it
>  didn't work. Following the manual I made a '.sigfixed' file in $HOME and a
>  directory '.Sig' with the alternating parts. I had to manually insert the
>  line '#define ENABLE_RANDOM_SIG' in config.h (compile time option
>  --enable-random-sig didn't do anything). Still not working. Do I miss a
>  patch or something like that..?

See http://astro.utoronto.ca/~reid/mutt/ for how to do what you want and more.

Can you tell the list exactly where in the manual you found the bit about
#define ENABLE_RANDOM_SIG?  That feature, if it was ever really there, was
removed years ago and the the manual should have been fixed years ago too.

Thanks.

-- 
"An eye for an eye leaves everybody blind." - Martin Luther King Jr.
Robert I. Reid <[EMAIL PROTECTED]> http://astro.utoronto.ca/~reid/
PGP Key: http://astro.utoronto.ca/~reid/pgp.html

testing procmail

[J McKitrick]

I'm trying to test procmail with mutt.  I'm new to mutt, and *very*
new to procmail  I used a friend's procmailrc as a template, but i
need to know if there s a way to test it without losing mail.

jm
-- 
-
Jonathon McKitrick  /  [EMAIL PROTECTED] \
"I prefer the term Artificial Person myself."/
-

Re: Signature selection

[Gary Johnson]

On Wed, Mar 15, 2000 at 04:11:09PM +0100, Terje Elde wrote:

>  ... but is there any way I can manage to set mutt up to check the
> domain I'm sending to, and set the correct sig?

I have one signature file for "internal" e-mail and another for
"external" e-mail.  Here's what I put in my muttrc file to select the
appropriate signature as a function of the addresses's domain:

send-hook . 'set signature=$HOME/.mutt/signature'
send-hook '^~t "@hp\.com$|\.hp\.com$|@agilent\.com$|\.agilent\.com$"' 'set 
signature=$HOME/.mutt/signature.internal'

In my case, "internal" is anything going to hp.com or agilent.com.

-- 
Gary Johnson | Agilent Technologies
[EMAIL PROTECTED] | RF Communications Product Generation Unit
 | Spokane, Washington, USA

Re: testing procmail

[Jag]

On Wed, 15 Mar 2000, J McKitrick wrote:

> I'm trying to test procmail with mutt.  I'm new to mutt, and *very*
> new to procmail  I used a friend's procmailrc as a template, but i
> need to know if there s a way to test it without losing mail.

Check out 'man procmailex'  It's nothing but example .procmailrc's.  If
you search for 'backup' in the man page it'll give you a recipe you can
put at the top of your .procmailrc to store all your mail in a backup
file before it tries to process the message.  Be careful with that
recipe though, I think it's setup for Maildir and not mbox format.

Jag

Re: Mutt 1.1.9 about 3-4x slower than mutt 1.0 (was Re: [Announce] mutt-1.1.9 is out - RELEASE CANDIDATE!)

[Thomas Roessler]

On 2000-03-15 09:36:26 -0500, Eric Boehm wrote:

> It sounds like you are saying that I should change the
> combination of 
> 
> +USE_DOTLOCK +USE_FCNTL -USE_FLOCK
> 
> to something else but it isn't clear to me what I
> should change it to.

You really want to compile your mutt 1.0 with an external
dotlock program.  However, I'd really suggest you stick
with 1.1.

> Are there any changes I should make to the HP-UX configuration. That has

> +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK

That's fine, reliability-wise.

> Lars>  Convenient as they are, charsets are another feature that
> Lars> make it easier for ppl to shoot themselves (and others) in the
> Lars> foot. Now that my mutt is charset sensitive, I often find messages
> Lars> with big5, iso-2022-jp, or koi8-r, although none of the special
> Lars> characters are actually in the message body (checked with vi in
> Lars> "C"). Free performance killer with every mail message.  

> Is there a way to diable this "feature"?

You can use the edit-type function to change mutt's idea
of what content type and/or character set a message is in.

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

Re: testing procmail

[Jason Helfman]

I got started with this...and it helped out very much
http://www.ii.com/internet/robots/procmail/qs/

/jgh

- Original Message -
From: Jag <[EMAIL PROTECTED]>
Date: Wednesday, March 15, 2000 11:12 am
Subject: Re: testing procmail

> On Wed, 15 Mar 2000, J McKitrick wrote:
> 
> > I'm trying to test procmail with mutt.  I'm new to mutt, and *very*
> > new to procmail  I used a friend's procmailrc as a template, but i
> > need to know if there s a way to test it without losing mail.
> 
> Check out 'man procmailex'  It's nothing but example 
> .procmailrc's.  If
> you search for 'backup' in the man page it'll give you a recipe 
> you can
> put at the top of your .procmailrc to store all your mail in a backup
> file before it tries to process the message.  Be careful with that
> recipe though, I think it's setup for Maildir and not mbox format.
> 
> Jag
> 

Re: Mutt 1.1.9 about 3-4x slower than mutt 1.0 (was Re: [Announce] mutt-1.1.9 is out - RELEASE CANDIDATE!)

[David DeSimone]

Eric Boehm <[EMAIL PROTECTED]> wrote:
>
> Yes, across NFS.  I copied the file to a local drive and ran both
> mutts.  The time was about the same (1.8 sec).  Both mutts were also
> run from a local drive.

Mutt wants to use fcntl-locking on the file.  This forces NFS to use a
non-caching mode, where all I/O is transfered directly to/from the
server, instead of being cached on the local system.  This slows things
down, but it is also very safe.

If you were to configure with --disable-fcntl, things would speed up,
but it would also be unsafe.  There could be conditions in which the
mail server tries to update your mail spool while Mutt is also trying to
update it, leading to mailbox corruption.  Using the correct locking
protocols would avoid this, although it would slow things down.

-- 
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 1.1.9 about 3-4x slower than mutt 1.0 (was Re: [Announce] mutt-1.1.9 is out - RELEASE CANDIDATE!)

[Lars Hecking]

 
> Lars>  Convenient as they are, charsets are another feature that
> Lars> make it easier for ppl to shoot themselves (and others) in the
> Lars> foot. Now that my mutt is charset sensitive, I often find messages
> Lars> with big5, iso-2022-jp, or koi8-r, although none of the special
> Lars> characters are actually in the message body (checked with vi in
> Lars> "C"). Free performance killer with every mail message.  
> 
> Is there a way to diable this "feature"?

 After configure, I usually go into config.h and change CHARMAPS_DIR
 to point to some nonexistant location.

Re: Keeping text below signature on reply

[Jeremy Blosser]

Jorge Godoy [[EMAIL PROTECTED]] wrote:
> Mutt uses some patterns to verify signatures and uses them to cut out
> these and the text below it when replying a message.
> 
> On my system it's looking for the standard "--". On some messages


It's "-- ".  Note the space.


And as noted, Mutt doesn't cut this.  Your editor must be.

-- 
Jeremy Blosser   |   [EMAIL PROTECTED]   |   http://jblosser.firinn.org/
-+-+--
"If Microsoft can change and compete on quality, I've won." -- L. Torvalds

 PGP signature

Re: testing procmail

[Jon Walthour]

On Wed, Mar 15, 2000 at 11:30:07AM -0500, J McKitrick wrote:
> I'm trying to test procmail with mutt.  I'm new to mutt, and *very*
> new to procmail  I used a friend's procmailrc as a template, but i
> need to know if there s a way to test it without losing mail.

Check out http://www.uwasa.fi/~ts/info/proctips.html. Specifically, look
at Tip #2: Building a test-bench. How can I test individual procmail
recipes?

-- 
Thanks,

Jon Walthour, BSCD
Cincinnati, Ohio
~~~
The 21st century begins on January 1, 2001

Re: testing procmail

[Robert Kim]

There is an excellent procmail FAQ.  It shows you step-by-step method to test the 
procmail.  If it worked for me, it must be easy.  I was able to set up procmail in my 
personal mail account w/o any problem.

However, I'm having trouble w/ my work mail account.  For some reason I can not "|" or 
write to file from my .forward file which renders my procmail useless.  It says I 
don't have the right shell.  Oh well, I'll probably have to look somewhere else for 
the answer.


* J McKitrick ([EMAIL PROTECTED]) [000315 08:49]:
> I'm trying to test procmail with mutt.  I'm new to mutt, and *very*
> new to procmail  I used a friend's procmailrc as a template, but i
> need to know if there s a way to test it without losing mail.
> 
> jm
> -- 
> -
> Jonathon McKitrick  /  [EMAIL PROTECTED] \
> "I prefer the term Artificial Person myself."/
> -

-- 
--

 Robert W. Kim
 e-mail: [EMAIL PROTECTED]

--

Re: testing procmail

[J McKitrick]

Well, i took your advice, and according to the test, this should work.
I tried the most basic possible procmail filter:
I'm trying to match subjects with 'test' in them.  But every time i
send myself such a message, it disappears into oblivion.

The procmail rule sends it to 'chat', which is a mailbox 
~/mail/chat

But it never shows up in chat.  No thing returns from the mailing, no
errors.  It just disappears.

jm
-- 
-
Jonathon McKitrick  /  [EMAIL PROTECTED] \
"I prefer the term Artificial Person myself."/
-

Re: testing procmail

[J McKitrick]

Nevermind.  Figured it out.

jm
-- 
-
Jonathon McKitrick  /  [EMAIL PROTECTED] \
"I prefer the term Artificial Person myself."/
-

Re: testing procmail

[J McKitrick]

I realize this is a mutt list, not a procmail list,
but this is just a quick question not worth subscribing to another
list for:

Here's my test .procmailrc

Problem is, nothing sent from me is ending up in chat.  it all goes to
the default directory.

In .muttrc, i have:

mailboxes
~/mail
~/mail/chat

jm
-- 
-
Jonathon McKitrick  /  [EMAIL PROTECTED] \
"I prefer the term Artificial Person myself."/
-



MAILDIR=/usr/home/jcm/mail
LOGFILE=/usr/home/jcm/procmail.log

:0
* ^From:.*jcm
$MAILDIR/chat

# Fall back to the default mailbox.

Re: testing procmail

[Eugene Lee]

On Wed, Mar 15, 2000 at 05:32:50PM +, J McKitrick wrote:

:I realize this is a mutt list, not a procmail list,
:but this is just a quick question not worth subscribing to another
:list for:
:
:Here's my test .procmailrc
:
:Problem is, nothing sent from me is ending up in chat.  it all goes to
:the default directory.

To your .procmailrc, add this line to enable extended diagnostics:

VERBOSE=on

Then send another test email, and check your LOGFILE to see what
Procmail is doing.  The recipe looks fine, so I'm guessing that Procmail
isn't even running.  In which case you need to fix your $HOME/.forward
file, if your local MTA (Sendmail, qmail, etc.) isn't configured to call
Procmail automatically.


-- 
Eugene Lee
[EMAIL PROTECTED]

Re: testing procmail

[Lars Hecking]

 Enable verbose logging in procmail. And remember that you need a
 local lockfile for file deliveries.

 This is really off-topic here.

 A searchable procmail mailing list archive is at
 http://www.xray.mpe.mpg.de/mailing-lists/procmail/
 
J McKitrick writes:
> Well, i took your advice, and according to the test, this should work.
> I tried the most basic possible procmail filter:
> I'm trying to match subjects with 'test' in them.  But every time i
> send myself such a message, it disappears into oblivion.
> 
> The procmail rule sends it to 'chat', which is a mailbox 
> ~/mail/chat
> 
> But it never shows up in chat.  No thing returns from the mailing, no
> errors.  It just disappears.
> 
> jm
> -- 
> -
> Jonathon McKitrick  /  [EMAIL PROTECTED] \
> "I prefer the term Artificial Person myself."/
> -

-- 
"We demand rigidly defined areas of doubt and uncertainty!"
-- Vroomfondel

File locking (was: Mutt 1.1.9 about 3-4x slower than mutt 1.0)

[Vincent Lefevre]

On Wed, Mar 15, 2000 at 11:19:45 -0600, David DeSimone wrote:
> Mutt wants to use fcntl-locking on the file.  This forces NFS to use a
> non-caching mode, where all I/O is transfered directly to/from the
> server, instead of being cached on the local system.  This slows things
> down, but it is also very safe.

This is safer for incoming mailboxes. But for archive boxes, that are
accessed from only one machine, it is useless. So, could the locking
mechanism be chosen from the .muttrc?

-- 
Vincent Lefèvre <[EMAIL PROTECTED]> - Web:  - 100%
validated HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des
Jeux Mathématiques et Logiques, TETRHEX, etc.
Computer science / computer arithmetic / Arénaire project at LIP, ENS-Lyon

pgp 6.5

[Attila Csosz]

Can mutt handle PGP keys from PGP 6.5?

Thanks
 Attila


-- 
--
- Mail: [EMAIL PROTECTED]; Debian 2.2 Linux  / 2.2.13 / exim-
- Get my PGP key: gpg --keyserver keys.pgp.com --recv-key 0x2cc33acb -

Re: testing procmail

[Jason Helfman]

After all of that, you didn't even post what the resolution was!@!!!

/jgh

- Original Message -
From: J McKitrick <[EMAIL PROTECTED]>
Date: Wednesday, March 15, 2000 1:00 pm
Subject: Re: testing procmail

> Nevermind.  Figured it out.
> 
> jm
> -- 
> -
> Jonathon McKitrick  /  [EMAIL PROTECTED] \
> "I prefer the term Artificial Person myself."/
> -
> 

Re: File locking (was: Mutt 1.1.9 about 3-4x slower than mutt 1.0)

[David DeSimone]

Vincent Lefevre <[EMAIL PROTECTED]> wrote:
>
> This is safer for incoming mailboxes.  But for archive boxes, that are
> accessed from only one machine, it is useless.  So, could the locking
> mechanism be chosen from the .muttrc?

If the mailbox is only accessed from one machine, why is it on an NFS
server?  Just put the mailbox on the one machine that is going to access
it.  No more NFS slow-down.

-- 
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

gnupg srpms

[Jason Helfman]

wanting to try the gnu pgp, what srpms would i need to download, being
in the us.


Current remote directory is /pub/replay/pub/redhat/SRPMS.
ncftp ...eplay/pub/redhat/SRPMS > ls g*
gnupg-0.4.0-3.src.rpm  gnupg-rsa-1.0-2.src.rpm
gnupg-1.0.0-1.src.rpm  gnupg-rsaref-1.0-2.src.rpm
gnupg-rsa-1.0-1.src.rpm
ncftp ...eplay/pub/redhat/SRPMS >


-- 
/helfman

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

Re: PGP behavior

[Alex Lane]

* On Wed, Mar 15, 2000 at 12:28:55AM -0600, Alex Lane wrote:
> Keeping in mind this is not a PGP mail list, I nonetheless would be
> appreciative if anyone could explain why I get a signal 11 error when
> running pgp 6.5.2. The mutt docs I've looked at distinguish pgp2 and
> pgp5; is 6.5.2 a completely different animal?
> 
> I may be taking a oversimplified view of things, but mutt 1.0i-2 (rpm
> distro for RHL 6.0) expects to see '/usr/bin/pgps' when I specify pgp5
> in the .muttrc file, apparently. So, I've tried renaming the pgp that
> came from Network Associates, and I've tried creating a symbolic link to
> the executable so that I can invoke 'pgps' and execute the file. 
> 
> What might I be doing wrong?
> 

Not to give the impression I am talking to myself much these days,
but...

PGP 5.x appears to live in several executables, each specializing in
some part of the process. 'pgpk' one supposes, takes care of key
functions; other members of the crew are 'pgpv' and 'pgps' (there may be
more). My 'try' at a solution didn't amount to much.

Doing a bunch of browsing on the mutt home page helped lots. ("Kids, can
you say RTFM? I knew you could!")

Specifying pgp6 for use with the rpm binary in 1.0i doesn't do a heck of
a lot except generate error messages, I found.

Downloading mutt-1.0.1i, and then doing a straightforward
untar--config--make-install seems to straighten everything out just
right. Some functionality that appeared to have 'disappeared' from pgp
is now back, all is right with the world, and I can go back to sleep.

Cheers...
-- 
Alex Lane * Seabrook, Texas, USA  -*-  [EMAIL PROTECTED] * www.galexi.com/alex/
Never forget they're paying you by the hour, not by the solution.
 (Sherby's Third Law of Consulting)

 PGP signature

Re: File locking (was: Mutt 1.1.9 about 3-4x slower than mutt 1.0)

[Vincent Lefevre]

On Wed, Mar 15, 2000 at 18:23:11 -0600, David DeSimone wrote:
> If the mailbox is only accessed from one machine, why is it on an NFS
> server?

Because my home is on an NFS server. This is the main reason. But in
fact, I want to be able to access these mailboxes from other machines
too, for instance because my machine is down. However it will always
be only one machine at the same time.

-- 
Vincent Lefèvre <[EMAIL PROTECTED]> - Web:  - 100%
validated HTML - Acorn Risc PC, Yellow Pig 17, Championnat International des
Jeux Mathématiques et Logiques, TETRHEX, etc.
Computer science / computer arithmetic / Arénaire project at LIP, ENS-Lyon