Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Chris Green]

On Wed, Mar 29, 2000 at 10:53:53PM +0200, Thomas Roessler wrote:
> 
> Against 1.1.9, a couple of bugs is fixed.  I really hope
> we can release this code as-is as 1.2 - so please report
> eventual bugs and problems as soon as possible to this
> list.
> 
I have just built 1.1.10 and installed on this Linux system (as a user,
no root access) and also on Solaris 2.6 (report in separate mail).

There are still a few minor issues in the build, here goes

The Linux system reports as:-
Linux shell 2.2.13 #8 Thu Oct 21 20:32:42 GMT 1999 i586 unknown


I buildt mutt with:-
./configure --prefix=/home/d/cgreen --with-slang --with-domain=x-1.net 
--enable-pop --enable-imap


There a couple of compiler warnings:-
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../intl  -I../intl  -Wall -pedantic -g -O2 
-c imap.c
imap.c: In function `imap_check_mailbox':
imap.c:1157: warning: `t' might be used uninitialized in this function

gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../intl  -I../intl  -Wall -pedantic -g -O2 
-c socket.c
In file included from /usr/include/netinet/in.h:27,
 from socket.c:29:
/usr/include/bits/socket.h:226: warning: ANSI C forbids zero-size array 
`__cmsg_data'

gcc -DSHAREDIR=\"/home/d/cgreen/share/mutt\" -DSYSCONFDIR=\"/home/d/cgreen/etc\"   
 -DBINDIR=\"/home/d/cgreen/bin\" -DHAVE_CONFIG_H=1 -I. -I. -I. -I./imap -Iintl 
-I/home/d/cgreen/include  -I./intl  -Wall -pedantic -g -O2 -c pop.c
In file included from /usr/include/sys/socket.h:34,
 from pop.c:28:
/usr/include/bits/socket.h:226: warning: ANSI C forbids zero-size array 
`__cmsg_data'


The most significant errors were in the 'make install' phase:-

mkdir /home/d/cgreen/doc/mutt/samples
for f in Mush.rc Pine.rc gpg.rc pgp2.rc pgp5.rc pgp6.rc Tin.rc ; do \
/usr/bin/install -c -m 644 ./$f /home/d/cgreen/doc/mutt/samples ;  \
done
/usr/bin/install: ./pgp6.rc: No such file or directory


if test -f /home/d/cgreen/bin/mutt_dotlock && test xmail != x ; then \
chgrp mail /home/d/cgreen/bin/mutt_dotlock && \
chmod 2755 /home/d/cgreen/bin/mutt_dotlock || \
{ echo "Can't fix mutt_dotlock's permissions!" >&2 ; exit 1 ; } \
fi
chgrp: you are not a member of group `mail': Operation not permitted
Can't fix mutt_dotlock's permissions!
make[2]: *** [install-exec-local] Error 1
make[2]: Leaving directory `/home/d/cgreen/build/mutt-1.1.10'
make[1]: *** [install-am] Error 2
make[1]: Leaving directory `/home/d/cgreen/build/mutt-1.1.10'
make: *** [install-recursive] Error 1



The problems above of course didn't stop mutt installing as you can see.
I've not come across any errors while running mutt.  I think the most
significant errors are the missing pgp6.rc file and the fac that the
install tries to set mutt_dotlock's permissions even though I have done
a local directory install.

N.B. The Solaris install had more errors, see next mail.

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

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Chris Green]

On Wed, Mar 29, 2000 at 10:53:53PM +0200, Thomas Roessler wrote:
> Against 1.1.9, a couple of bugs is fixed.  I really hope
> we can release this code as-is as 1.2 - so please report
> eventual bugs and problems as soon as possible to this
> list.
> 
OK, here's a report on my build on a Solaris 2.6 system, not quite so
smooth as the Linux build I'm afraid.


System reports as:-
SunOS borg 5.6 Generic_105181-17 sun4u sparc SUNW,Ultra-1


Compiler used:-
gcc version 2.95.1 19990816 (release)


Configured with:-
./configure  --prefix=/usr/chris --with-slang --with-domain=kbss.bt.co.uk 
--enable-pop --enable-imap


There were quite a lot of compiler warnings:-
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../intl  -I../intl  -Wall -pedantic -g -O2 
-c command.c
command.c: In function `imap_handle_untagged':
command.c:165: warning: subscript has type `char'
command.c:216: warning: subscript has type `char'

gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../intl  -I../intl  -Wall -pedantic -g -O2 
-c imap.c
imap.c: In function `imap_reopen_mailbox':
imap.c:229: warning: subscript has type `char'
imap.c:233: warning: subscript has type `char'
imap.c: In function `imap_open_mailbox':
imap.c:609: warning: subscript has type `char'
imap.c:613: warning: subscript has type `char'
imap.c: In function `imap_check_mailbox':
imap.c:1157: warning: `t' might be used uninitialized in this function
imap.c: In function `imap_mailbox_check':
imap.c:1278: warning: subscript has type `char'

gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../intl  -I../intl  -Wall -pedantic -g -O2 
-c message.c
message.c: In function `msg_parse_fetch':
message.c:788: warning: subscript has type `char'

gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../intl  -I../intl  -Wall -pedantic -g -O2 
-c util.c
util.c: In function `imap_get_literal_count':
util.c:98: warning: subscript has type `char'

gcc -DSHAREDIR=\"/usr/chris/share/mutt\" -DSYSCONFDIR=\"/usr/chris/etc\"   
-DBINDIR=\"/usr/chris/bin\" -DHAVE_CONFIG_H=1 -I. -I. -I. -I./imap -Iintl 
-I/usr/chris/include -I./intl  -Wall -pedantic -g -O2 -c rfc2231.c
rfc2231.c: In function `rfc2231_decode_parameters':
rfc2231.c:136: warning: subscript has type `char'
rfc2231.c: In function `rfc2231_decode_one':
rfc2231.c:209: warning: subscript has type `char'
rfc2231.c:209: warning: subscript has type `char'

gcc -DSHAREDIR=\"/usr/chris/share/mutt\" -DSYSCONFDIR=\"/usr/chris/etc\"   
-DBINDIR=\"/usr/chris/bin\" -DHAVE_CONFIG_H=1 -I. -I. -I. -I./imap -Iintl 
-I/usr/chris/include -I./intl  -Wall -pedantic -g -O2 -c pgpkey.c
pgpkey.c: In function `pgp_entry_fmt':
pgpkey.c:139: warning: subscript has type `char'

gcc -DSHAREDIR=\"/usr/chris/share/mutt\" -DSYSCONFDIR=\"/usr/chris/etc\"   
-DBINDIR=\"/usr/chris/bin\" -DHAVE_CONFIG_H=1 -I. -I. -I. -I./imap -Iintl 
-I/usr/chris/include -I./intl  -Wall -pedantic -g -O2 -c gnupgparse.c
gnupgparse.c: In function `fix_uid':
gnupgparse.c:77: warning: subscript has type `char'
gnupgparse.c:77: warning: subscript has type `char'


Then 'make install' breaks completely on the missing pgp6.rc file:-
Making install in contrib
../mkinstalldirs /usr/chris/doc/mutt/samples
for f in Mush.rc Pine.rc gpg.rc pgp2.rc pgp5.rc pgp6.rc Tin.rc ; do \
.././install-sh -c -m 644 ./$f /usr/chris/doc/mutt/samples ; \
done
install:  ./pgp6.rc does not exist
*** Error code 1
make: Fatal error: Command failed for target `install'
Current working directory /usr/chris/mutt-1.1.10/contrib
*** Error code 1
make: Fatal error: Command failed for target `install-recursive'


Finally I get the same error as on the Linux install regarding the
mutt_dotlock file:-

if test -f /usr/chris/bin/mutt_dotlock && test x != x ; then \
chgrp  /usr/chris/bin/mutt_dotlock && \
chmod 755 /usr/chris/bin/mutt_dotlock || \
{ echo "Can't fix mutt_dotlock's permissions!" >&2 ; exit 1 ; } \
fi


All this is using the Solaris make in /usr/ccs/bin/make, using (a rather
old) GNU make is even worse:-
/tools/bin/make  all-recursive
Making all in m4
make[2]: Nothing to be done for `all'.
Making all in po
cd .. && /tools/bin/make keymap_alldefs.h
./gen_defs ./OPS ./OPS.PGP ./OPS.MIX > keymap_alldefs.h
PATH=../src:$PATH : --default-domain=mutt --directory=..  --add-comments 
--keyword=_ --keyword=N_ --files-from=./POTFILES.in && test ! -f mutt.po || ( rm -f 
./mutt.pot && mv mutt.po ./mutt.pot )
make[2]: :: Command not found
make[2]: *** [cat-id-tbl.c] Error 127
make[1]: *** [all-recursive] Error 1
make: *** [all-recursive-am] Error 1



I have worked around this by putting a dummy pgp6.rc file in the
contrib directory, mutt then installs OK.  I haven't noticed any
problems with the installed executable, I will report any that I find.

-- 
Chris Green ([EMAIL PR

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Chris Green]

On Thu, Mar 30, 2000 at 09:54:02AM +0100, Chris Green wrote:
> 
> Finally I get the same error as on the Linux install regarding the
> mutt_dotlock file:-
> 
> if test -f /usr/chris/bin/mutt_dotlock && test x != x ; then \
>   chgrp  /usr/chris/bin/mutt_dotlock && \
>   chmod 755 /usr/chris/bin/mutt_dotlock || \
>   { echo "Can't fix mutt_dotlock's permissions!" >&2 ; exit 1 ; } \
> fi
> 
Oops, not an error at all, sorry!  Just me reading the error message
and assuming it gave the same error as on the Linux system.

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

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Thomas Roessler]

On 2000-03-30 09:14:09 +0100, Chris Green wrote:

> There a couple of compiler warnings:-
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../intl  -I../intl  -Wall -pedantic -g 
>-O2 -c imap.c
> imap.c: In function `imap_check_mailbox':
> imap.c:1157: warning: `t' might be used uninitialized in this function

This is an over-eager gcc.  The variable is not used
uninitialized.

> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../intl  -I../intl  -Wall -pedantic -g 
>-O2 -c socket.c
> In file included from /usr/include/netinet/in.h:27,
>from socket.c:29:
> /usr/include/bits/socket.h:226: warning: ANSI C forbids zero-size array 
>`__cmsg_data'
> 
> gcc -DSHAREDIR=\"/home/d/cgreen/share/mutt\" -DSYSCONFDIR=\"/home/d/cgreen/etc\" 
>   -DBINDIR=\"/home/d/cgreen/bin\" -DHAVE_CONFIG_H=1 -I. -I. -I. -I./imap -Iintl 
>-I/home/d/cgreen/include  -I./intl  -Wall -pedantic -g -O2 -c pop.c
> In file included from /usr/include/sys/socket.h:34,
>from pop.c:28:
> /usr/include/bits/socket.h:226: warning: ANSI C forbids zero-size array 
>`__cmsg_data'

Problems with system headers, not our problem.

> The most significant errors were in the 'make install' phase:-

> mkdir /home/d/cgreen/doc/mutt/samples
> for f in Mush.rc Pine.rc gpg.rc pgp2.rc pgp5.rc pgp6.rc Tin.rc ; do \
>   /usr/bin/install -c -m 644 ./$f /home/d/cgreen/doc/mutt/samples ;  \
> done
> /usr/bin/install: ./pgp6.rc: No such file or directory

Ups.

> if test -f /home/d/cgreen/bin/mutt_dotlock && test xmail != x ; then \
>   chgrp mail /home/d/cgreen/bin/mutt_dotlock && \
>   chmod 2755 /home/d/cgreen/bin/mutt_dotlock || \
>   { echo "Can't fix mutt_dotlock's permissions!" >&2 ; exit 1 ; } \
> fi
> chgrp: you are not a member of group `mail': Operation not permitted
> Can't fix mutt_dotlock's permissions!
> make[2]: *** [install-exec-local] Error 1
> make[2]: Leaving directory `/home/d/cgreen/build/mutt-1.1.10'
> make[1]: *** [install-am] Error 2
> make[1]: Leaving directory `/home/d/cgreen/build/mutt-1.1.10'
> make: *** [install-recursive] Error 1

Ah, ok.  You are installing mutt with user permissions,
and it tries to adapt mutt_dotlock to your system's
situation.

> The problems above of course didn't stop mutt
> installing as you can see. I've not come across any
> errors while running mutt.  I think the most
> significant errors are the missing pgp6.rc file and the
> fac that the install tries to set mutt_dotlock's
> permissions even though I have done a local directory
> install.

umh...  I wouldn't really consider this a problem in the
installation mechanism...

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

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Aaron Schrab]

At 11:05 +0200 30 Mar 2000, Thomas Roessler <[EMAIL PROTECTED]> wrote:
> On 2000-03-30 09:14:09 +0100, Chris Green wrote:
> 
> > There a couple of compiler warnings:-
> > gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../intl  -I../intl  -Wall -pedantic -g 
>-O2 -c imap.c
> > imap.c: In function `imap_check_mailbox':
> > imap.c:1157: warning: `t' might be used uninitialized in this function
> 
> This is an over-eager gcc.  The variable is not used
> uninitialized.

Still, it would probably be a good idea to prevent the warning.
Spurious warnings can mask ones that are real problems.

> > fac that the install tries to set mutt_dotlock's
> > permissions even though I have done a local directory
> > install.
> 
> umh...  I wouldn't really consider this a problem in the
> installation mechanism...

Since in cases like this, the resulting install could easily be unsafe,
it could be argued that installing at all is an error.  There should
probably be more noticeable errors at the least, maybe even require the
person doing the install run something like "make unsafe_install".

-- 
Aaron Schrab [EMAIL PROTECTED]  http://www.execpc.com/~aarons/
 Everyone can be taught to sculpt: Michelangelo would have had to be
 taught how _not_ to.  So it is with the great programmers.

Re: pgp/gpg password, temp file?

[Terje Elde]

* Christopher Smith ([EMAIL PROTECTED]) [000330 02:09]:
> -you still need some authentication mechanism between gnupgd and
> applications, and this must somehow be fairly secure. I believe ssh2
> relies on process parent/child relationships to do
> authorization/authentication and I don't see this as reliable.

No!

Think like this:

Mutt wishes to store a password for later use, so it asks the user for the
passphrase, xor's it with a key, connects to gnupgd using a named pipe set
up by the admin of the box, hands the xored passphrase to gnupgd, and wipes it
from memory, then requests (over the same connection) a token it can use to
get the key back, which is passed down to mutt. This token will never be
passed over the cleartext link again, because a challenge response thing is
much more fun. Why you ask? Because this way you allow mutt to keep track of
how many times the passphrase has been read from gnupgd, and you can thus set
of all sorta of alarms and uglyness should there have been a read mutt didn't
want.

Just my $0.02.

Terje Elde
-- 
PGP @ http://www.elde.org0xBC26460D 0xE16020ED
55BE 4633 6DAD 1CE6 0C58  544A F072 E02E BC26 460D

 PGP signature

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Edmund GRIMLEY EVANS]

Aaron Schrab <[EMAIL PROTECTED]>:

> > > There a couple of compiler warnings:-
> > > gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I../intl  -I../intl  -Wall -pedantic 
>-g -O2 -c imap.c
> > > imap.c: In function `imap_check_mailbox':
> > > imap.c:1157: warning: `t' might be used uninitialized in this function
> > 
> > This is an over-eager gcc.  The variable is not used
> > uninitialized.
> 
> Still, it would probably be a good idea to prevent the warning.
> Spurious warnings can mask ones that are real problems.

I don't like warnings, either.

--- imap.c.orig Wed Mar  8 10:01:44 2000
+++ imap.c  Thu Mar 30 11:50:06 2000
@@ -1154,13 +1154,8 @@
 {
   char buf[LONG_STRING];
   static time_t checktime=0;
-  time_t t;
+  time_t t = 0; /* to avoid compiler warning */
 
-  /* 
-   * gcc thinks it has to warn about uninitialized use
-   * of t.  This is wrong.
-   */
-  
   if (ImapCheckTimeout)
   { 
 t = time(NULL);

Re: pgp/gpg password, temp file?

[Edmund GRIMLEY EVANS]

I was thinking of something simpler: mutt spawns a suid program called
muttpgphelper, say, and gives the passphrase to this program. When
mutt wants to invoke gnupg it sends a request down a pipe to
muttpgphelper which then invokes gnupg and gives the passphrase to
gnupg down another pipe.

pgp_timeout could be implemented by muttpgphelper calling alarm() ...

Edmund

Re: pgp/gpg password, temp file?

[Terje Elde]

* Edmund GRIMLEY EVANS ([EMAIL PROTECTED]) [000330 13:06]:
> I was thinking of something simpler: mutt spawns a suid program called
> muttpgphelper, say, and gives the passphrase to this program. When
> mutt wants to invoke gnupg it sends a request down a pipe to
> muttpgphelper which then invokes gnupg and gives the passphrase to
> gnupg down another pipe.
> 
> pgp_timeout could be implemented by muttpgphelper calling alarm() ...

Might be simpler, but is it better? With a daemon you first of all have multi
user support, and there's no need for setuid bits. Just to name a few
benefits.

Terje
-- 
Tuj uh yaau fudj å buiu qdthu fuhieduhi ahofjuhju cubtydwuh.
Uh yaau tujju qbj tuj rulyiuj tk jhudwuh veh å yddiu qj cqd cå rhkau
ijuhauhu shofje?

 PGP signature

Re: pgp/gpg password, temp file?

[Thomas Roessler]

On 2000-03-30 12:06:42 +0100, Edmund GRIMLEY EVANS wrote:

> I was thinking of something simpler: mutt spawns a suid
> program called muttpgphelper, say, and gives the
> passphrase to this program. When mutt wants to invoke
> gnupg it sends a request down a pipe to muttpgphelper
> which then invokes gnupg and gives the passphrase to
> gnupg down another pipe.

I think a more interesting variant may be some kind of
passphrase-agent which is directly contacted by gnupg, pgp
& friends through some Unix domain socket.  I have even
some code from a year or two ago  However, this has
two downsides:

(1) mutt still has to temporarily store the pass phrase or
parts thereof in insecure memory

(2) same with most versions of PGP - remember, most don't
run setuid root.

(3) this approach requires modifications to all PGP
back-ends used.

Frankly, I really don't believe one should expect highest
security from low-security devices.  If you really care,
don't use a pass phrase, and software crypto, but use a
smart card with biometric user authentication for all the
public-key crypto.

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

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Chris Green]

On Thu, Mar 30, 2000 at 04:21:40AM -0600, Aaron Schrab wrote:
> > umh...  I wouldn't really consider this a problem in the
> > installation mechanism...
> 
> Since in cases like this, the resulting install could easily be unsafe,
> it could be argued that installing at all is an error.  There should
> probably be more noticeable errors at the least, maybe even require the
> person doing the install run something like "make unsafe_install".
> 
Yes, I think this is right, if you allow the --prefix=
option then it suggests that the installation can be done by a
non-root user.

Is the issue just one of locking the mail spool correctly by the way?
Should it be possible for a user of mail on a system to set the
permissions correctly or does mutt require root to install?  I think
not actually as I didn't get this error on my other (Solaris) install
and I did that as a user too.

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

Re: pgp/gpg password, temp file?

[Terje Elde]

* Thomas Roessler ([EMAIL PROTECTED]) [000330 13:27]:
> > I was thinking of something simpler: mutt spawns a suid
> > program called muttpgphelper, say, and gives the
> > passphrase to this program. When mutt wants to invoke
> > gnupg it sends a request down a pipe to muttpgphelper
> > which then invokes gnupg and gives the passphrase to
> > gnupg down another pipe.
> 
> I think a more interesting variant may be some kind of
> passphrase-agent which is directly contacted by gnupg, pgp
> & friends through some Unix domain socket.  I have even
> some code from a year or two ago  However, this has
> two downsides:
> 
> (1) mutt still has to temporarily store the pass phrase or
> parts thereof in insecure memory

No. You can always allow the gnupgd thing to grab the keyboard and get the
data itself.

But this is really a non-issue, as what we're trying to avoid here is the
thing getting swapped out, which it won't be when you keep sending chars to
the application.

> (2) same with most versions of PGP - remember, most don't
> run setuid root.

Keep in mind that most PGP apps don't keep the passphrase in memory for ages.

> (3) this approach requires modifications to all PGP
> back-ends used.

It does? Why?

> Frankly, I really don't believe one should expect highest
> security from low-security devices.  If you really care,
> don't use a pass phrase, and software crypto, but use a
> smart card with biometric user authentication for all the
> public-key crypto.

Smard cards get broken.

Anyways, I do get your point, but mine is simply that while we cannot get
perfect security, why not improve on at least the things that are easy to
attack?

Terje Elde
-- 
Tuj uh yaau fudj å buiu qdthu fuhieduhi ahofjuhju cubtydwuh.
Uh yaau tujju qbj tuj rulyiuj tk jhudwuh veh å yddiu qj cqd cå rhkau
ijuhauhu shofje?

 PGP signature

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Vincent Lefevre]

On Thu, Mar 30, 2000 at 11:52:02 +0100, Edmund GRIMLEY EVANS wrote:
[snip]
> -  time_t t;
> +  time_t t = 0; /* to avoid compiler warning */
>  
> -  /* 
> -   * gcc thinks it has to warn about uninitialized use
> -   * of t.  This is wrong.
> -   */
> -  

I disagree. You shouldn't prevent warnings like this. If gcc thinks
that the variable is uninitialized, it should be fixed, and you
shouldn't add unnecessary code, that makes it bigger...

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

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Ralf Hildebrandt]

On Thu, Mar 30, 2000 at 02:48:53PM +0200, Vincent Lefevre wrote:
> On Thu, Mar 30, 2000 at 11:52:02 +0100, Edmund GRIMLEY EVANS wrote:
> [snip]
> > -  time_t t;
> > +  time_t t = 0; /* to avoid compiler warning */
> >  
> > -  /* 
> > -   * gcc thinks it has to warn about uninitialized use
> > -   * of t.  This is wrong.
> > -   */
> > -  
> 
> I disagree. You shouldn't prevent warnings like this. If gcc thinks
> that the variable is uninitialized, it should be fixed, and you
> shouldn't add unnecessary code, that makes it bigger...

? That's what he did !
He added: time_t t = 0; /* to avoid compiler warning */
And removed: The comment in /* */

-- 
Ralf Hildebrandt <[EMAIL PROTECTED]> www.stahl.bau.tu-bs.de/~hildeb
NT vs UNIX, why UNIX:   It doesn't matter how big or hot your 
thing is at the moment if it doesn't stay up or perform.


 PGP signature

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Ralf Hildebrandt]

Hmm, what about the --with-charmaps option?

I downloaded ftp://ftp.guug.de/pub/mutt/charmaps-0.0.tar.gz and untarred it
in the sourcedire of mutt-1.1.10 -- but this file is really old. Has it been
overridden yet?

-- 
Ralf Hildebrandt <[EMAIL PROTECTED]> www.stahl.bau.tu-bs.de/~hildeb
Windows has detected that a gnat has farted near your computer. Press
any key to reboot. 


 PGP signature

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Gero Treuner]

On Thu, Mar 30, 2000 at 02:55:38PM +0200, Ralf Hildebrandt wrote:
> ? That's what he did !
> He added: time_t t = 0; /* to avoid compiler warning */
> And removed: The comment in /* */

It is not the size of the source file discussed here, but the size of
the resulting binary. This tends to be bigger and slower because of the
additional assignment.

Personally I don't care. I know what -Wall means, and how picky
compilers are then. System administrators should know this, too,
consider this as an extra service of the developer and assume that
the developer saw and checked the warning.

POSIX/ANSI conformance warnings aren't that important, and I guess
several installers verify the source that variables are indeed
initialized.


Gero

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Edmund GRIMLEY EVANS]

Vincent Lefevre <[EMAIL PROTECTED]>:

> > -  time_t t;
> > +  time_t t = 0; /* to avoid compiler warning */
> >  
> > -  /* 
> > -   * gcc thinks it has to warn about uninitialized use
> > -   * of t.  This is wrong.
> > -   */
> > -  
> 
> I disagree. You shouldn't prevent warnings like this. If gcc thinks
> that the variable is uninitialized, it should be fixed, and you
> shouldn't add unnecessary code, that makes it bigger...

You're right. My patch made the code bigger. By exactly one xor
instruction on i386! But here's an alternative patch that makes the
code smaller (but it is less obvious that this patch is safe):

--- imap.c.orig Wed Mar  8 10:01:44 2000
+++ imap.c  Thu Mar 30 14:15:02 2000
@@ -1154,13 +1154,8 @@
 {
   char buf[LONG_STRING];
   static time_t checktime=0;
-  time_t t;
+  time_t t = 0;
 
-  /* 
-   * gcc thinks it has to warn about uninitialized use
-   * of t.  This is wrong.
-   */
-  
   if (ImapCheckTimeout)
   { 
 t = time(NULL);
@@ -1170,7 +1165,7 @@
   if ((ImapCheckTimeout && t >= ImapCheckTimeout)
   || ((CTX_DATA->reopen & IMAP_REOPEN_ALLOW) && (CTX_DATA->reopen & 
~IMAP_REOPEN_ALLOW)))
   {
-if (ImapCheckTimeout) checktime += t;
+checktime += t;
 
 CTX_DATA->check_status = 0;
 if (imap_exec (buf, sizeof (buf), CTX_DATA, "NOOP", 0) != 0)

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Ralf Hildebrandt]

On Thu, Mar 30, 2000 at 03:21:19PM +0200, Gero Treuner wrote:

> It is not the size of the source file discussed here, but the size of
> the resulting binary. This tends to be bigger and slower because of the
> additional assignment.

=:|

I really prefer code that compiles without warning. Sometimes (!) this can't
be prevented, but in this case...

> Personally I don't care. I know what -Wall means, and how picky
> compilers are then. System administrators should know this, too,
> consider this as an extra service of the developer and assume that
> the developer saw and checked the warning.

Hey, HP's CC is even more anal about the code.

-- 
Ralf Hildebrandt <[EMAIL PROTECTED]> www.stahl.bau.tu-bs.de/~hildeb
Ah, young webmaster... java leads to shockwave. Shockwave leads to
realaudio. And realaudio leads to suffering. 

Re: pgp/gpg password, temp file?

[Jason Helfman]

I didn't expect to start a religious war, but being Jewish, I can
appreciate this

I just wanted to know why. It was cached temporarily was enough for me,
but the responses were intriguing.

:>

On Thu, Mar 30, 2000 at 01:20:09PM +0200, Thomas Roessler muttered:
> On 2000-03-30 12:06:42 +0100, Edmund GRIMLEY EVANS wrote:
> 
> > I was thinking of something simpler: mutt spawns a suid
> > program called muttpgphelper, say, and gives the
> > passphrase to this program. When mutt wants to invoke
> > gnupg it sends a request down a pipe to muttpgphelper
> > which then invokes gnupg and gives the passphrase to
> > gnupg down another pipe.
> 
> I think a more interesting variant may be some kind of
> passphrase-agent which is directly contacted by gnupg, pgp
> & friends through some Unix domain socket.  I have even
> some code from a year or two ago  However, this has
> two downsides:
> 
> (1) mutt still has to temporarily store the pass phrase or
> parts thereof in insecure memory
> 
> (2) same with most versions of PGP - remember, most don't
> run setuid root.
> 
> (3) this approach requires modifications to all PGP
> back-ends used.
> 
> Frankly, I really don't believe one should expect highest
> security from low-security devices.  If you really care,
> don't use a pass phrase, and software crypto, but use a
> smart card with biometric user authentication for all the
> public-key crypto.
> 
> -- 
> http://www.guug.de/~roessler/
> 

-- 
/helfman

"At any given moment, you may find the ticket to the circus that has always beenin 
your possession."
Fingerprint: 2F76 2856 776A 3E07 9F3E  452A 17D9 9B28 D75E 0A36
GnuPG http://www.gnupg.org  Get Private!  1024D/D75E0A36

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[David T-G]

Chris --

...and then Chris Green said...
% On Thu, Mar 30, 2000 at 04:21:40AM -0600, Aaron Schrab wrote:
% > 
% > Since in cases like this, the resulting install could easily be unsafe,
% > it could be argued that installing at all is an error.  There should

Actually, it seems to me that the install won't be unsafe -- it just
won't be able to lock $MAIL.  If you use procmail or some such to drop
your mail in a spool file that you control, then your inboxisno different
from any ofyour other folders -- and you can do anything you want.  No
safety issue involved...


% > probably be more noticeable errors at the least, maybe even require the
% > person doing the install run something like "make unsafe_install".
% > 
% Yes, I think this is right, if you allow the --prefix=
% option then it suggests that the installation can be done by a
% non-root user.

It does, admittedly, but it also allows root to install mutt somewhere
other than /usr/local (like mebbe /).  Because of the nature of most mail
locking system, you're going to have to have root authority to set the
gid bit on mutt_dotlock at least once.

Now, the good news is that any mutt_dotlock with the proper perms will
do.  If you can get your sysadmin to install mutt_dotlock somewhere (like
/usr/local/bin or even your personal bin) you can safely ignore any
difficulties with a mutt_dotlock in a later build and not use the new
one.  As an added bonus, you can call mutt_dotlock yourself in a script
if you want to manually copy your $MAIL file to somewhere else where you
can play with it and then *safely* zero out the real one.


% 
% Is the issue just one of locking the mail spool correctly by the way?
% Should it be possible for a user of mail on a system to set the
% permissions correctly or does mutt require root to install?  I think
% not actually as I didn't get this error on my other (Solaris) install
% and I did that as a user too.

I guess I already answered this part :-)  Yes, the only difficulty
installing mutt as a user is that you can't set the g+s bit on
mutt_dotlock, the only bit of code that needs special permissions.  
[In fact, that's why mutt_dotlock was created; lots of very reasonable
people did not want a big program like mutt running with special
permissions.]


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


:-D
-- 
David T-G   * It's easier to fight for one's principles
(play) [EMAIL PROTECTED]  * than to live up to them. -- fortune cookie
(work) [EMAIL PROTECTED]
http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
The "new millennium" starts at the beginning of 2001.  There was no year 0.
Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh*


 PGP signature

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[David T-G]

Chris --

I don't have a lot of input on your Solaris build, but I do know that the
Sun-supplied make and cc just plain stink.  You mentioned that your gcc is
old; can you get/build a new one and then try with that?


:-D
-- 
David T-G   * It's easier to fight for one's principles
(play) [EMAIL PROTECTED]  * than to live up to them. -- fortune cookie
(work) [EMAIL PROTECTED]
http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
The "new millennium" starts at the beginning of 2001.  There was no year 0.
Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh*


 PGP signature

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Stephan Seitz]

Hi!

On Don, Mär 30, 2000 at 09:19:42 -0500, David T-G wrote
> Now, the good news is that any mutt_dotlock with the proper perms will
> do.  If you can get your sysadmin to install mutt_dotlock somewhere (like

I would like an install-option that installs mutt without
mutt_dotlock.

I can install software on an Irix-system, but I can't set a s-bit.
My root installed a mutt_dotlock after testing the binary, so I don't
need a new one.

Shade and sweet water!

Stephan

-- 
| Stephan SeitzE-Mail: [EMAIL PROTECTED] |
|  WWW: http://fsing.fs.uni-sb.de/~stse/|
| PGP Public Keys: http://fsing.fs.uni-sb.de/~stse/pgp.html |

 PGP signature

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[John Franklin]

On Thu, Mar 30, 2000 at 02:25:45PM +0100, Edmund GRIMLEY EVANS wrote:
> Vincent Lefevre <[EMAIL PROTECTED]>:
> You're right. My patch made the code bigger. By exactly one xor
> instruction on i386! But here's an alternative patch that makes the
> code smaller (but it is less obvious that this patch is safe):

I was looking at submitting a similar patch, but you beat me to it.
one difference, tho:

> --- imap.c.orig   Wed Mar  8 10:01:44 2000
> +++ imap.cThu Mar 30 14:15:02 2000
> @@ -1154,13 +1154,8 @@
>  {
>char buf[LONG_STRING];
>static time_t checktime=0;
> -  time_t t;
> +  time_t t = 0;
>  
> -  /* 
> -   * gcc thinks it has to warn about uninitialized use
> -   * of t.  This is wrong.
> -   */
> -  
>if (ImapCheckTimeout)
>{ 
>  t = time(NULL);
> @@ -1170,7 +1165,7 @@
>if ((ImapCheckTimeout && t >= ImapCheckTimeout)

We don't need to test for ImapCheckTimeout again.

>|| ((CTX_DATA->reopen & IMAP_REOPEN_ALLOW) && (CTX_DATA->reopen & 
>~IMAP_REOPEN_ALLOW)))
>{
> -if (ImapCheckTimeout) checktime += t;
> +checktime += t;

I noticed you removed it here already.

>  
>  CTX_DATA->check_status = 0;
>  if (imap_exec (buf, sizeof (buf), CTX_DATA, "NOOP", 0) != 0)

-- 
John Franklin
[EMAIL PROTECTED]
ICBM: 35°48'19"N 78°46'39"W

Re: default save folder

[Michael . Tatge]

Hi!

On Wed, Mar 29, 2000 at 10:32:16PM +0200, Jean-Charles Bagneris wrote:
> Of course, each time I press 's', I have to give the name of the folder I want to 
>save to.
> So my question is : is there a way to give (in a folder-hook may be) a default name 
>for the
> archive folder ?

Put something like 
save-hook   in your .muttrc
If you want to have the whole thread i.e. even your own mails in that
folder use that fcc-save-hook command.

Michael

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Lars Hecking]

David T-G writes:
> Chris --
> 
> I don't have a lot of input on your Solaris build, but I do know that the
> Sun-supplied make and cc just plain stink.  You mentioned that your gcc is
> old; can you get/build a new one and then try with that?

 Old by date, but still, it's the previous release :) His problems are
 certainly not related to this, as the real failures are at install time:

 o contrib/pgp6.rc is missing from the distribution,
 and some other failures I cannot reproduce. Possibly a shell problem.
 The $(srcdir)/$(PACKAGE).pot: target in po/Makefile behaves in my case.

 In there is a bug in make install for doc/muttrc.man if mutt is built
  outside the source directory.
 
 While Sun ships a few crappy tools, make is quite decent. And the C compiler
 (commercial, not the defunct stub in /usr/ucb) is quite good as well.

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Chris Green]

On Thu, Mar 30, 2000 at 09:21:14AM -0500, David T-G wrote:
> Chris --
> 
> I don't have a lot of input on your Solaris build, but I do know that the
> Sun-supplied make and cc just plain stink.  You mentioned that your gcc is
> old; can you get/build a new one and then try with that?
> 
The compiler is already gcc. It's just the make that's an old gnu one,
I'll see if I can get a newer one installed.

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

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Thomas Roessler]

Maybe a contest about generating the shortest
self-replicating program which runs on a given
architecture is more productive like this. ;-)

I'm offering 11 bytes, plus portability.

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

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Edmund GRIMLEY EVANS]

Thomas Roessler <[EMAIL PROTECTED]>:

> Maybe a contest about generating the shortest
> self-replicating program which runs on a given
> architecture is more productive like this. ;-)
> 
> I'm offering 11 bytes, plus portability.

Does it work anything like the attached program?

Edmund


#include 

void escape(char *x)
{
  for (; *x; x++)
if (*x == '"' || *x == '\\')
  printf("\\%c", *x);
else if (*x == '\n')
  printf("\\n\"\n\"");
else
  putchar(*x);
}

int main(int argc, char *argv[])
{
  char *x = "#include \n"
"\n"
"void escape(char *x)\n"
"{\n"
"  for (; *x; x++)\n"
"if (*x == '\"' || *x == '')\n"
"  printf(\"%c\", *x);\n"
"else if (*x == '\\n')\n"
"  printf(\"n\\\"\\n\\\"\");\n"
"else\n"
"  putchar(*x);\n"
"}\n"
"\n"
"int main(int argc, char *argv[])\n"
"{\n"
"  char *x = \"";
  char *y = "\";\n"
"\n"
"  printf(\"%s\", x);\n"
"  escape(x);\n"
"  printf(\"\\\";\\n  char *y = \\\"\");\n"
"  escape(y);\n"
"  printf(\"%s\", y);\n"
"  return 0;\n"
"}\n"
"";

  printf("%s", x);
  escape(x);
  printf("\";\n  char *y = \"");
  escape(y);
  printf("%s", y);
  return 0;
}

Problem: I recieved a strange email with several strange headers.

[Robert Suetterlin]

Hello,

I recieved a strange email from some company. The mail headers do not list me 
as recipient so I do not know why I did recieve the mail at all. Also the top 'FROM ' 
header line (and the derieved return path) is a bit strange and I do not really know 
what to make of it. I attached the email to this letter, so if any of You mail gurus 
are listening perhaps You know why I get this mail and what to make of the header line.

Bye,

Robert S. {:).

-- 
Robert S"utterlin

eMail: [EMAIL PROTECTED]
office phone: +(49)89 / 3299 - 3545
office address: Giessenbachstrasse, POBox 1603, 85740 Garching, Germany

priv phone: (+49)89 / 54 76 31 83
address: Siglstr. 15, 80686 Muenchen, Germany.




This is an automated message from C & C's satellite E-Mail system.

Your E-Mail message has been delivered.

Your message contains attachments. Please send attachments only if
required for operations.

Thank you for your cooperation,
C & C's E-Mail Computer


The e-mail message follows:
-
> Received: from buffy.tpgi.com.au([203.12.160.34]) (2198 bytes) by 
>kraken.cctechnol.com
>   via sendmail with P:esmtp/R:batch_it/T:batch_smtp
>   (sender: <[EMAIL PROTECTED]>) 
>   id <[EMAIL PROTECTED]>
>   for <[EMAIL PROTECTED]>; Wed, 29 Mar 2000 20:17:11 -0600 (CST)
>   (Smail-3.2.0.111 2000-Feb-17 #2 built 2000-Mar-20)
> Received: (from smtpd@localhost)
>   by buffy.tpgi.com.au (8.9.3/8.9.3) id MAA18448
>   for <[EMAIL PROTECTED]>; Thu, 30 Mar 2000 12:17:00 +1000
> Received: from bri2-56k-098.tpgi.com.au(203.29.144.98), claiming to be "serra"
>  via SMTP by buffy.tpgi.com.au, id smtpdKbkZme; Thu Mar 30 12:16:49 2000
> Received: by serra (sSMTP sendmail emulation); Thu, 30 Mar 2000 12:23:05 +1000
> Date: Thu, 30 Mar 2000 12:23:04 +1000
> From: Darrin Mison <[EMAIL PROTECTED]>
> To: Sam Alleman <[EMAIL PROTECTED]>
> Subject: Re: update encoding?
> Message-ID: <[EMAIL PROTECTED]>
> References: <[EMAIL PROTECTED]>
> Mime-Version: 1.0
> Content-Type: multipart/signed; micalg=pgp-md5;
>   protocol="application/pgp-signature"; boundary="opJtzjQTFsWo+cga"
> X-Mailer: Mutt 1.0i
> In-Reply-To: <[EMAIL PROTECTED]>; from 
>[EMAIL PROTECTED] on Wed, Mar 29, 2000 at 10:45:23PM +0900
> X-Operating-System: Linux serra 2.2.12-20
> 
> 
> --opJtzjQTFsWo+cga
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: quoted-printable
> 
> guessing here, but you use pgp to sign a message which=20
> you have postponed and then you get this when you send=20
> it again.  Don't know how to avoid it or if to.
> 
> 
> As Sam Alleman<[EMAIL PROTECTED]> once said:
> >=20
> > Hello again,
> >=20
> > Can anyone tell me what this message is all about:
> >=20
> > ~~/tmp/mutt-xena-22566-0 [#1] modified. Update encoding? ([y]/n):
> >=20
> > What does this mean, and is there any way to bypass this question?
> > Thanks.
> >=20
> > Sam
> 
> --
> Darrin Mison
> --=20
> "Necessity is the mother of invention" is a silly proverb.  "Necessity
> is the mother of futile dodges" is much nearer the truth.
> -- Alfred North Whitehead
> 
> --opJtzjQTFsWo+cga
> Content-Type: application/pgp-signature
> 
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.0.1 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
> 
> iEYEAREBAAYFAjjiuogACgkQbJuZmIkY3S6B5ACeMgFDnAoSqSP099T75Tq0D+xm
> 7JAAn0LT5oLioplDYNnuZyM15xGI2UV2
> =//v7
> -END PGP SIGNATURE-
> 
> --opJtzjQTFsWo+cga--
> .

Re: pgp/gpg password, temp file?

[Chris Tilbury]

On Thu, Mar 30, 2000 at 01:20:09PM +0200, Thomas Roessler muttered:
> On 2000-03-30 12:06:42 +0100, Edmund GRIMLEY EVANS wrote:
> 
> > I was thinking of something simpler: mutt spawns a suid
> > program called muttpgphelper, say, and gives the
> > passphrase to this program. When mutt wants to invoke
> > gnupg it sends a request down a pipe to muttpgphelper
> > which then invokes gnupg and gives the passphrase to
> > gnupg down another pipe.
> 
> > I think a more interesting variant may be some kind of
> > passphrase-agent which is directly contacted by gnupg, pgp
> > & friends through some Unix domain socket.  I have even
> > some code from a year or two ago  However, this has
> > two downsides:

SSH does something like this - there's a "ssh-agent" program which you add
keys to from your keyring by running a program. You give the passphrase
to the ssh-addkey program, it loads the (unencrypted) key into the agent
and then apps can communicate with this agent through a unix domain socket.

Nice, makes it easier to use ssh, but not terribly secure, I fear.




Chris

-- 
Chris Tilbury, UNIX Systems Administrator: UNIX & Networking Group
 Information Technology Services, University of Warwick, Coventry, UK
PHONE: 024 7652 3365 / FAX: 0870 088 4307 / MAIL: [EMAIL PROTECTED]

Re: Problem: I recieved a strange email with several strange headers.

[Hall Stevenson]

Hmmm, oddly, I rec'd the exact same message today !! It appears someone
may have skimmed the mutt list for e-mail addresses.

But, why your name didn't show in the header was that you (and I and
probably others on this list) were "Blind Carbon Copy"'d. This is how
spammers do it. With a "BCC", what good would it do if I sent you an
e-mail and BCC'd your boss (because I didn't want you to know he/she was
copied) and all you had to do was check the message headers and find out I
did that ??

Regards,
Hall

-Original Message-
From: Robert Suetterlin <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, March 30, 2000 12:20 PM
Subject: Problem: I recieved a strange email with several strange headers.


>Hello,
>
> I recieved a strange email from some company. The mail headers do not
list me as recipient so I do not know why I did recieve the mail at all.
Also the top 'FROM ' header line (and the derieved return path) is a bit
strange and I do not really know what to make of it. I attached the email
to this letter, so if any of You mail gurus are listening perhaps You know
why I get this mail and what to make of the header line.
>
>Bye,
>
> Robert S. {:).
>
>--
>Robert S"utterlin
>
>eMail: [EMAIL PROTECTED]
>office phone: +(49)89 / 3299 - 3545
>office address: Giessenbachstrasse, POBox 1603, 85740 Garching, Germany
>
>priv phone: (+49)89 / 54 76 31 83
>address: Siglstr. 15, 80686 Muenchen, Germany.
>

QmailAnalog

[S.P. Hoeke]

Hello,

I'm wondering if there's a FAQ or HOW-TO with regards to qmailanalog...
The man pages are, for me, not sufficient to get it running :-(

THNX,
 Steffan

Re: pgp/gpg password, temp file?

[Thomas Roessler]

On 2000-03-30 15:14:38 +0100, Chris Tilbury wrote:

> SSH does something like this - there's a "ssh-agent"
> program which you add keys to from your keyring by
> running a program.

Guess where the wording "passphrase-agent" came from. ;-)

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

Re: QmailAnalog

[Walt Mankowski]

On Thu, Mar 30, 2000 at 07:47:15PM +0200, S.P. Hoeke wrote:
> Hello,
> 
> I'm wondering if there's a FAQ or HOW-TO with regards to qmailanalog...
> The man pages are, for me, not sufficient to get it running :-(
> 
> THNX,
>  Steffan
> 

Maybe you'd have more luck asking your question on the qmail mailing
list.  :-)

Re: QmailAnalog

[S.P. Hoeke]

I should have been paying attention when i enterd the (incorrect) alias instead of 
trying to watch TV with one eye
Please don't shoot me :-0

Greetz,
 Steffan

On Thu, Mar 30, 2000 at 01:27:32PM -0500, Walt Mankowski muttered:
> On Thu, Mar 30, 2000 at 07:47:15PM +0200, S.P. Hoeke wrote:
> > Hello,
> > 
> > I'm wondering if there's a FAQ or HOW-TO with regards to qmailanalog...
> > The man pages are, for me, not sufficient to get it running :-(
> > 
> > THNX,
> >  Steffan
> > 
> 
> Maybe you'd have more luck asking your question on the qmail mailing
> list.  :-)
> 

Re: default save folder

[Jean-Charles Bagneris]

[EMAIL PROTECTED] wrote on 30 Mar 2000 :
> save-hook   in your .muttrc

I must be stupid...
I did read that when I first browsed the manual a few weeks ago.
But yesterday, I searched through config variables, not config commands.
Sorry for this, and thanks

-- 
JcB, Jean-Charles Bagneris, Montpellier, France

quoting reply

[Jason Helfman]

I was hunting around for this last night, but where do can you specify 
your character set for a "quoting reply"

of instance

blah blah said:
& lakdjfslakdjf
& kjad;slfjaklsdjf
& kajds;lfkjasldkfj

^---> this being the "quoting reply character"

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

Fingerprint: 2F76 2856 776A 3E07 9F3E  452A 17D9 9B28 D75E 0A36
 GnuPG http://www.gnupg.org  Get Private!

Re: quoting reply

[Eugene Lee]

On Thu, Mar 30, 2000 at 12:54:55PM -0600, Jason Helfman wrote:

:I was hunting around for this last night, but where do can you specify 
:your character set for a "quoting reply"

set indent_string="& "

-- 
Eugene Lee
[EMAIL PROTECTED]

Re: Problem: I recieved a strange email with several strange headers.

[supio]

On Thu, Mar 30, 2000 at 12:43:00PM -0500, Hall Stevenson wrote:
> Hmmm, oddly, I rec'd the exact same message today !! It appears someone
> may have skimmed the mutt list for e-mail addresses.

I received this mail too. I think this is only a confirmation for a
delivered mail sent to this list (because of a set reply-to: ?) and has nothing to do 
with spam.
But it is not nice to confirm to a ml... - I hate mails my procmail
doesn't move ;)


-- 
greetings supio ( Marc Noller ) | [EMAIL PROTECTED] | http://oipus.net |
-|
- Filstal.Online e.V.  http://www.fto.de |
--- LinuxUserGroup Filstal http://lug.fto.de |

Re: quoting reply

[Lars Hecking]

> :I was hunting around for this last night, but where do can you specify 
> :your character set for a "quoting reply"
 
 The manual says:

... You are strongly encouraged not to
  change this value, as it tends to agitate the more fanatical netizens.
...

 :-)

> set indent_string="& "

 Why not set it to "From: " for maximum confusion and MUA breaking :-)

Re: Problem: I recieved a strange email with several strange headers.

[Sebastian Helms]

Hi,

* Robert Suetterlin wrote on 30 Mär 2000:

>   I recieved a strange email from some company. 

Sam Alleman is having his email forwarded via a satellite
data connection, as he is currently on a boat somewhere on the ocean
;-). I have written some mails to him and for every
mail I got such a delivery notification.

So if you sent a message to the list, ...

Regards,

Sebastian

-- 
"No worries." - Rincewind

Sebastian Helms   -  mailto:[EMAIL PROTECTED] (PGP available)

Re: update encoding?

[Chris Hoffmann]

On Wed, Mar 29, 2000 at 10:45:23PM +0900, Sam Alleman wrote:
 
> Can anyone tell me what this message is all about:
> 
> ~~/tmp/mutt-xena-22566-0 [#1] modified. Update encoding? ([y]/n):
> 
> What does this mean, and is there any way to bypass this question?

My guess is that mutt is telling you that there is a mismatch in 
time/date stamps - e.g the timestamp on the tmp file is in the future.

For me this happens when the clocks aren't in synch between
the host I am running mutt on, and the host where my ~/tmp is
NFS mounted from 

YMMV of course ...

Cheers,

Chris

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Christopher Smith]

On Thu, Mar 30, 2000 at 02:25:45PM +0100, Edmund GRIMLEY EVANS wrote:
> Vincent Lefevre <[EMAIL PROTECTED]>:
> 
> > > -  time_t t;
> > > +  time_t t = 0; /* to avoid compiler warning */
> > >  
> > > -  /* 
> > > -   * gcc thinks it has to warn about uninitialized use
> > > -   * of t.  This is wrong.
> > > -   */
> > > -  
> > 
> > I disagree. You shouldn't prevent warnings like this. If gcc thinks
> > that the variable is uninitialized, it should be fixed, and you
> > shouldn't add unnecessary code, that makes it bigger...
> You're right. My patch made the code bigger. By exactly one xor
> instruction on i386! But here's an alternative patch that makes the
> code smaller (but it is less obvious that this patch is safe):

Hmm... I thought the whole problem was just because the flow was
overly complex and it confused gcc (and those who might be reading the
source). I did this patch to clean it up, although I suspect the whole
thing could use a touch of refactoring based on how many branches are
in this function. This patch avoids putting the t variable on the
stack unless it's needed, and pulls it out of scope ASAP. It does
introduce one extra variable, but I suspect this incremental
improvement in code hygiene is more of a good thing than a bad one.

--Chris

--- imap.c.orig Thu Mar 30 14:42:54 2000
+++ imap.c  Thu Mar 30 14:55:30 2000
@@ -1153,9 +1153,8 @@
 int imap_check_mailbox (CONTEXT *ctx, int *index_hint)
 {
   char buf[LONG_STRING];
-  static time_t checktime=0;
-  time_t t;
-
+  short timedout = FALSE;
+   
   /* 
* gcc thinks it has to warn about uninitialized use
* of t.  This is wrong.
@@ -1163,15 +1162,20 @@
   
   if (ImapCheckTimeout)
   { 
-t = time(NULL);
+   static time_t checktime=0;
+   time_t t = time(NULL);
+
 t -= checktime;
+   if (t >= ImapCheckTimeout) 
+   {
+ checktime += t;
+ timedout = TRUE;
+   }
   }
 
-  if ((ImapCheckTimeout && t >= ImapCheckTimeout)
+  if ((timedout)
   || ((CTX_DATA->reopen & IMAP_REOPEN_ALLOW) && (CTX_DATA->reopen & 
~IMAP_REOPEN_ALLOW)))
   {
-if (ImapCheckTimeout) checktime += t;
-
 CTX_DATA->check_status = 0;
 if (imap_exec (buf, sizeof (buf), CTX_DATA, "NOOP", 0) != 0)

Re: quoting reply

[Edmund GRIMLEY EVANS]

Lars Hecking <[EMAIL PROTECTED]>:

> > set indent_string="& "
> 
>  Why not set it to "From: " for maximum confusion and MUA breaking :-)

That is a cool idea, but don't you mean "From "?

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Stefan `Sec` Zehl]

On Thu, Mar 30, 2000 at 06:49:15PM +0200, Thomas Roessler wrote:
> On 2000-03-30 17:11:26 +0100, Edmund GRIMLEY EVANS wrote:
> >> I'm offering 11 bytes, plus portability.
> > Does it work anything like the attached program?
> 
> No. Just try
> 
>   #!/bin/cat

Hm. I had almost the same idea :)

| matrix:~>echo 'cat $0'>a
| matrix:~>chmod a+x a
| matrix:~>./a
| cat $0
| matrix:~>wc -c a
|7 a

SCNR,
Sec
-- 
The UNIX Guru's View of Sex:
# unzip ; strip ; touch ; finger ; mount ; fsck ; more ; yes ; umount ; sleep

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[David T-G]

Lars --

...and then Lars Hecking said...
% David T-G writes:
% > Chris --
% > 
% > I don't have a lot of input on your Solaris build, but I do know that the
% > Sun-supplied make and cc just plain stink.  You mentioned that your gcc is
% > old; can you get/build a new one and then try with that?
% 
%  Old by date, but still, it's the previous release :) His problems are
%  certainly not related to this, as the real failures are at install time:

Well, I just started with his statement that an old version of gcc only
gets about 4 lines into the process :-)


% 
%  o contrib/pgp6.rc is missing from the distribution,
%  and some other failures I cannot reproduce. Possibly a shell problem.
%  The $(srcdir)/$(PACKAGE).pot: target in po/Makefile behaves in my case.

Yep.  Acknowledged.


% 
%  In there is a bug in make install for doc/muttrc.man if mutt is built
%   outside the source directory.
%  
%  While Sun ships a few crappy tools, make is quite decent. And the C compiler
%  (commercial, not the defunct stub in /usr/ucb) is quite good as well.

I know that the sparcworks compiler package is good, but I didn't know
that one in /usr/ccs was any good.  I'm a happy Sun bigot, myself,
and do a lot on them :-)  Maybe I'll have to check into compiliing...


:-D
-- 
David T-G   * It's easier to fight for one's principles
(play) [EMAIL PROTECTED]  * than to live up to them. -- fortune cookie
(work) [EMAIL PROTECTED]
http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
The "new millennium" starts at the beginning of 2001.  There was no year 0.
Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh*


 PGP signature

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[David T-G]

Chris --

...and then Chris Green said...
% On Thu, Mar 30, 2000 at 09:21:14AM -0500, David T-G wrote:
% > 
% > Sun-supplied make and cc just plain stink.  You mentioned that your gcc is
% > old; can you get/build a new one and then try with that?
% > 
% The compiler is already gcc. It's just the make that's an old gnu one,
% I'll see if I can get a newer one installed.

See, here is where I show my ignorance regarding compiling.  To me,
all that make and gcc and gas stuff goes together ;-)


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


:-D
-- 
David T-G   * It's easier to fight for one's principles
(play) [EMAIL PROTECTED]  * than to live up to them. -- fortune cookie
(work) [EMAIL PROTECTED]
http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
The "new millennium" starts at the beginning of 2001.  There was no year 0.
Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh*


 PGP signature

Re: default save folder

[David DeSimone]

Jean-Charles Bagneris <[EMAIL PROTECTED]> wrote:
>
> Of course, each time I press 's', I have to give the name of the
> folder I want to save to.  So my question is :  is there a way to give
> (in a folder-hook may be) a default name for the archive folder ?

You can also simply tag all the messages that you want to save, then
save them using a grouped command, and they will all be saved to the
single folder that you specify.  Use the tag-prefix (default ";") before
the save command, to specify saving all tagged messages.

-- 
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
Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D  AB A6 15 F1 BB BE 8C 44

Re: Problem: I recieved a strange email with several strange headers.

[Darrin Mison]

sorry guys that's my fault hit r(eply) instead of R(eply to list).

As Sebastian Helms<[EMAIL PROTECTED]> once said:
> So if you sent a message to the list, ...
> 

--
Darrin Mison
-- 
There's nothing like a girl with a plunging neckline to keep a man on his toes.

 PGP signature

Re: How to resend a mail?

[David DeSimone]

Mikko Hänninen <[EMAIL PROTECTED]> wrote:
>
> First save the email to a separate file.
> Then just call sendmail on the file:
> sendmail -t [EMAIL PROTECTED] < /path/to/folder/file

What you describe is exactly what the (b)ounce command does in Mutt.

-- 
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
Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D  AB A6 15 F1 BB BE 8C 44

Re: Any suggestion on mailling list?

[David DeSimone]

[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> I want to create "mailling lists" using mutt, that's to say, sending
> news to some users, but the users need not reply my mails.  As i want
> to implement the list using scripts, I can not invoke mutt
> interactively, all i can do is to use commandline options. 

Is there some reason you need to use Mutt?

Compose your message in a file, with full headers and all.  You need not
insert the recipients into the To: header, though you should have one in
the headers.  You can have a fake To: header, such as "To: my-list",
even if there is no such list as "my-list".

Once you have composed the file, send it directly via sendmail:

sendmail [EMAIL PROTECTED] [EMAIL PROTECTED] \
[EMAIL PROTECTED]  <  mail.file

As you can see, sendmail will take the contents of mail.file and
distribute it to all of the senders you name on the command line.

You can even put the list of names into a file, and insert them thusly:

sendmail `cat users.list`  <  mail.file

Voila!  A mutt-less solution (on the mutt mailing list, no less)!  :)

-- 
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
Richardson IT|PGP: 5B 47 34 9F 3B 9A B0 0D  AB A6 15 F1 BB BE 8C 44

Re: Re: Any suggestion on mailling list?

[sjp]

> [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >
> > I want to create "mailling lists" using mutt, that's to say, sending
> > news to some users, but the users need not reply my mails.  As i want
> > to implement the list using scripts, I can not invoke mutt
> > interactively, all i can do is to use commandline options. 
> 
> Is there some reason you need to use Mutt?
  
  My idea is to use Mutt to encode the attachments and produce the headers.

> 
> Compose your message in a file, with full headers and all.  You need not
> insert the recipients into the To: header, though you should have one in
> the headers.  You can have a fake To: header, such as "To: my-list",
> even if there is no such list as "my-list".
> 
> Once you have composed the file, send it directly via sendmail:
> 
> sendmail [EMAIL PROTECTED] [EMAIL PROTECTED] \
>   [EMAIL PROTECTED]  <  mail.file
> 
> As you can see, sendmail will take the contents of mail.file and
> distribute it to all of the senders you name on the command line.
> 
> You can even put the list of names into a file, and insert them thusly:
> 
> sendmail `cat users.list`  <  mail.file
> 
> Voila!  A mutt-less solution (on the mutt mailing list, no less)!  :)
> 

Yes, this is a good idea. But i can not send attachments by this method,
and the subscriber will find To: header is not for them, a bit confusing.

Thanks.
--
»¶Ó­Ê¹Óà 21CN µç×ÓÓʼþϵͳhttp://www.21cn.com
Thank you for using 21CN Email system

Re: append .signature on message send?

[lewst]

Mikko_Hänninen <[EMAIL PROTECTED]> wrote:

> Well, it can't be done with Mutt *alone*.  It can be done _to_ emails
> sent with Mutt, though.  There's been at least 2 or 3 different
> solutions mentioned to you, which all involve the use of external
> helper scripts.

Yes.  I read the digest so it took a while for those solutions
to reach me.  I like Bryial's suggestion of making the $sendmail 
variable point to script which appends the signature before invoking
the real sendmail program.  I will give this a shot.

Thanks to all.


__
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

Re: How to resend a mail?

[Mikko Hänninen]

David DeSimone <[EMAIL PROTECTED]> wrote on Thu, 30 Mar 2000:
> Mikko Hänninen <[EMAIL PROTECTED]> wrote:
> >
> > First save the email to a separate file.
> > Then just call sendmail on the file:
> > sendmail -t [EMAIL PROTECTED] < /path/to/folder/file
> 
> What you describe is exactly what the (b)ounce command does in Mutt.

Yes, err, right -- but the user wanted to do this from a script,
"non-interactively".  Sure Mutt could be made to do a bounce with
"push" but would you really recommend that? :-)


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: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Chris Green]

On Thu, Mar 30, 2000 at 07:39:42PM -0500, David T-G wrote:
> Lars --
> 
> ...and then Lars Hecking said...
> % David T-G writes:
> % > Chris --
> % > 
> % > I don't have a lot of input on your Solaris build, but I do know that the
> % > Sun-supplied make and cc just plain stink.  You mentioned that your gcc is
> % > old; can you get/build a new one and then try with that?
> % 
> %  Old by date, but still, it's the previous release :) His problems are
> %  certainly not related to this, as the real failures are at install time:
> 
> Well, I just started with his statement that an old version of gcc only
> gets about 4 lines into the process :-)
> 
No, it's an old version of GNU make, I have a very up to date version 
of gcc.
> 
> % 
> %  In there is a bug in make install for doc/muttrc.man if mutt is built
> %   outside the source directory.
> %  
> %  While Sun ships a few crappy tools, make is quite decent. And the C compiler
> %  (commercial, not the defunct stub in /usr/ucb) is quite good as well.
> 
> I know that the sparcworks compiler package is good, but I didn't know
> that one in /usr/ccs was any good.  I'm a happy Sun bigot, myself,
> and do a lot on them :-)  Maybe I'll have to check into compiliing...
> 
It's the make we're talking about here.  Sun still provides a proper
make and it's in /usr/ccs/bin/make.  That of course is also where the
'dummy' cc is that tell's you it's not a real cc if you don't have
the development tools.

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

Re: [Announce] Mutt-1.1.10 is out (RELEASE CANDIDATE)

[Chris Green]

On Thu, Mar 30, 2000 at 07:40:45PM -0500, David T-G wrote:
> Chris --
> 
> ...and then Chris Green said...
> % On Thu, Mar 30, 2000 at 09:21:14AM -0500, David T-G wrote:
> % > 
> % > Sun-supplied make and cc just plain stink.  You mentioned that your gcc is
> % > old; can you get/build a new one and then try with that?
> % > 
> % The compiler is already gcc. It's just the make that's an old gnu one,
> % I'll see if I can get a newer one installed.
> 
> See, here is where I show my ignorance regarding compiling.  To me,
> all that make and gcc and gas stuff goes together ;-)
> 
No, the GNU compiler (gcc) and the GNU make are quite separate
packages and you can install them separately, thus it's quite possible
to have a new gcc and an old GNU make.

The same applies to Sun, a basic SOlaris installation does include a
proper make but doesn't include cc.

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