SRPM Bug! (was: [ANNOUNCE] mutt-1.0pre1i RPMs)

1999-08-25 Thread Thomas Ribbrock
Hi folks, Alec Habig (Thanks Alec!) just notified me of a bug my source rpms for mutt-0.95.7i and mutt-1.0pre1: When rebulding the SRPM, it might overwrite files in /usr/share/mutt on the life file system. I hope to get round to fix that today or tomorrow (watch this space! ;-) ), but I thought I

'make install' hangs (was Re: [Announce] Release candidate: 1.0pre1)

1999-08-25 Thread Thomas Wolmer VK/EHS/OM/DE
Problem: ehswolm@vksun25:~/mutt-1.0pre1>make install Making install in doc . . . Making install in charsets cd . && sh ./gen_charsets ./../mkinstalldirs /home/5/ehswolm/share/mutt/charsets ( cd . && for f in `cat charsets.list` ; do .././install-sh -c \ -m 644 $f /home/5/ehswolm/share/mut

Re: [ANNOUNCE] mutt-1.0pre1i RPMs

1999-08-25 Thread Telsa
On Wed, Aug 25, 1999 at 01:35:09AM +0100 or thereabouts, Thomas Ribbrock wrote: > Folks, this is happening too fast... ;-) :) > Anyway, the new RPMs are finished and available (as usual) at: > http://www.bigfoot.com/~kaytan/tuxior.html > Maybe this time I get round to upload them to incoming.re

Re: [ANNOUNCE] mutt-1.0pre1i RPMs

1999-08-25 Thread Peter van Dijk
On Wed, Aug 25, 1999 at 11:09:55AM +0100, Telsa wrote: > On Wed, Aug 25, 1999 at 01:35:09AM +0100 or thereabouts, Thomas Ribbrock wrote: > > Folks, this is happening too fast... ;-) > > :) > > > Anyway, the new RPMs are finished and available (as usual) at: > > http://www.bigfoot.com/~kaytan/tu

Re: [ANNOUNCE] mutt-1.0pre1i RPMs

1999-08-25 Thread Fairlight
On Wed, Aug 25, 1999 at 12:20:30PM +0200, Peter van Dijk thus spoke: > ftp.replay.com is hosted in The Netherlands, which means it can indeed have > all kinds of crypto stuff. It's where I go when I need ssh stuff :) There is no actual crypto shipped in mutt, so the only "problem" is RH being fin

Re: [ANNOUNCE] mutt-1.0pre1i RPMs

1999-08-25 Thread Ralf Hildebrandt
On Wed, Aug 25, 1999 at 08:40:42AM -0400, Fairlight wrote: > There is no actual crypto shipped in mutt, so the only "problem" is RH > being finicky about "i" versions on their site, from what I can see. :/ Nope. Even the hooks for PGP/strong crypto are illegal to export. -- Ralf Hildebrandt <

Re: [ANNOUNCE] mutt-1.0pre1i RPMs

1999-08-25 Thread Fairlight
On Wed, Aug 25, 1999 at 03:00:04PM +0200, Ralf Hildebrandt thus spoke: > On Wed, Aug 25, 1999 at 08:40:42AM -0400, Fairlight wrote: > > > There is no actual crypto shipped in mutt, so the only "problem" is RH > > being finicky about "i" versions on their site, from what I can see. :/ > > Nope.

Re: updates to www.mutt.org

1999-08-25 Thread Erik Jacobsen
Thanks, these are good things. Seems like the .txt and .txt.gz links point to the same (ungzipped) text file, though... One other thought: am I the only one out there who likes "text" and/or ".txt" files to mean "plain text" (i.e., with ASCII codes >= 0x20, except for whitespace encodings)? I'm

Re: updates to www.mutt.org

1999-08-25 Thread Kim DeVaughn
On Wed, Aug 25, 1999, Erik Jacobsen ([EMAIL PROTECTED]) said: | | One other thought: am I the only one out there who likes "text" and/or | ".txt" files to mean "plain text" (i.e., with ASCII codes >= 0x20, except | for whitespace encodings)? Yes indeed (or, to avoid confusion, "me too"). Also, N

Re: updates to www.mutt.org

1999-08-25 Thread Peter van Dijk
On Wed, Aug 25, 1999 at 07:42:41AM -0600, Kim DeVaughn wrote: > On Wed, Aug 25, 1999, Erik Jacobsen ([EMAIL PROTECTED]) said: > | > | One other thought: am I the only one out there who likes "text" and/or > | ".txt" files to mean "plain text" (i.e., with ASCII codes >= 0x20, except > | for whitesp

Re: updates to www.mutt.org

1999-08-25 Thread Kim DeVaughn
On Wed, Aug 25, 1999, Peter van Dijk ([EMAIL PROTECTED]) said: | | On Wed, Aug 25, 1999 at 07:42:41AM -0600, Kim DeVaughn stupidly said: | > | > Also, NO chars >= 0x3F, please ...! | | I think you mean 0x7F. Duh. Of course that's what I meant ...! Thanks for catching that. /kim (who shouldn't

mutt-1.0pre1 build using SGI cc fixed - patch attatched

1999-08-25 Thread Alec Habig
Hi, SGI's cc tends to be pretty picky, and it doesn't like you to declare strings with "char blah[]" and initialize it at the same time. I have no idea why, but it bombs when it sees this. Luckily, "char * blah" works just fine and means the same thing. So, the attached patch allows people to

configurable?

1999-08-25 Thread Fairlight
Gee, and you call mutt configurable? :) :) *chuckle* Just kidding, but one question... Seriously...there's one thing that I -can't- seem to find to reconfigure, ant that's the "-- Forwarded message by" ...or however it reads, when you forward a message. You can change the Subject header's

Re: updates to www.mutt.org

1999-08-25 Thread David DeSimone
Erik Jacobsen <[EMAIL PROTECTED]> wrote: > > I'm always having to get rid of the ^Hs by piping the distribution's > manual.txt through "col -b" (or s/(\S\010)//g for perl people :) I use "less" to read text files, and it does a fine job of translating those backspaces into nice bold and underline

Re: configurable?

1999-08-25 Thread Gero Treuner
Hi! On Wed, Aug 25, 1999 at 11:48:34AM -0400, Fairlight wrote: > Seriously...there's one thing that I -can't- seem to find to reconfigure, > ant that's the "-- Forwarded message by" ...or however it reads, when you > forward a message. You can configure it within your editor by substituting

Re: Is this a pine bug or my mutt is misconfiged

1999-08-25 Thread Michael Elkins
On Wed, Aug 25, 1999 at 11:02:45AM +1000, Shao Zhang wrote: > When I send attachments to someone else. If they use mutt to > save the attachments, then it is fine. But if they use pine to > save it, then pine does not give a default file name. Many > people have complained

Re: configurable?

1999-08-25 Thread Fairlight
On Wed, Aug 25, 1999 at 07:07:11PM +0200, Gero Treuner thus spoke: > Hi! > > On Wed, Aug 25, 1999 at 11:48:34AM -0400, Fairlight wrote: > > Seriously...there's one thing that I -can't- seem to find to reconfigure, > > ant that's the "-- Forwarded message by" ...or however it reads, when you >

Re: updates to www.mutt.org

1999-08-25 Thread Erik Jacobsen
On Wed, Aug 25, 1999 at 11:45 AM, David DeSimone ([EMAIL PROTECTED]) typed: > Of course, it's hard to put those nice highlights back again, if you > take them out. Why not simply filter the file through "col -b" once, > and save it that way on your system, so that you don't have to do it > every

Re: updates to www.mutt.org

1999-08-25 Thread Manoj Kasichainula
On Wed, Aug 25, 1999 at 03:03:11PM -0400, Erik Jacobsen wrote: > I use "less" too, but I still get stuff like: > > [EMAIL PROTECTED] -- low traffic list for announcements set the environment variable LESSCHARSET=latin1 -- Manoj Kasichainula - manojk at io dot com - http://www.io.com/~manoj

Re: [ANNOUNCE] mutt-1.0pre1i RPMs

1999-08-25 Thread Thomas Ribbrock
On Wed, Aug 25, 1999 at 03:00:04PM +0200, Ralf Hildebrandt wrote: > Nope. Even the hooks for PGP/strong crypto are illegal to export. Could you please elaborate on that? I was wondering about that for a long time now and I'd be grateful to get to know what exactly led to the split between "mutt

Re: updates to www.mutt.org

1999-08-25 Thread Jeremy Blosser
Erik Jacobsen [[EMAIL PROTECTED]] wrote: > Thanks, these are good things. Seems like the .txt and .txt.gz links point > to the same (ungzipped) text file, though... This is a feature of your browser. It's gunzipping the file as it downloads it. To just download it, use your browser's mechanism

Re: crypto laws (was: [ANNOUNCE] mutt-1.0pre1i RPMs)

1999-08-25 Thread Jeremy Blosser
Fairlight [[EMAIL PROTECTED]] wrote: > On Wed, Aug 25, 1999 at 03:00:04PM +0200, Ralf Hildebrandt thus spoke: > > On Wed, Aug 25, 1999 at 08:40:42AM -0400, Fairlight wrote: > > > > > There is no actual crypto shipped in mutt, so the only "problem" is RH > > > being finicky about "i" versions on t

Re: [ANNOUNCE] mutt-1.0pre1i RPMs

1999-08-25 Thread Jeremy Blosser
Thomas Ribbrock [[EMAIL PROTECTED]] wrote: > On Wed, Aug 25, 1999 at 03:00:04PM +0200, Ralf Hildebrandt wrote: > > > Nope. Even the hooks for PGP/strong crypto are illegal to export. > > Could you please elaborate on that? I was wondering about that for a long > time now and I'd be grateful to

[OT] U.S. Crypto-Export Laws (was: [ANNOUNCE] mutt-1.0pre1i RPMs)

1999-08-25 Thread Thomas Ribbrock
On Wed, Aug 25, 1999 at 03:33:24PM -0500, Jeremy Blosser wrote: > See http://www.mozilla.org/crypto-faq.html, which includes links to the > applicable legislation. Thanks. Looks bleak, indeed. However, just out of interest: Does anybody have links to the legislations? All such links on the pa

Re: [OT] U.S. Crypto-Export Laws (was: [ANNOUNCE] mutt-1.0pre1i RPMs)

1999-08-25 Thread Jeremy Blosser
Thomas Ribbrock [[EMAIL PROTECTED]] wrote: > On Wed, Aug 25, 1999 at 03:33:24PM -0500, Jeremy Blosser wrote: > > > See http://www.mozilla.org/crypto-faq.html, which includes links to the > > applicable legislation. > > Thanks. Looks bleak, indeed. > > However, just out of interest: Does anybo

Re: [OT] U.S. Crypto-Export Laws (was: [ANNOUNCE] mutt-1.0pre1i RPMs)

1999-08-25 Thread Pete Toscano
well, at the risk of getting a little too political, all you americans on this list who feel that these encryption laws are inane should check out this site: http://www.computerprivacy.com/. i question the effectiveness of contacting legislators at all, but it's worth a shot. pete On Wed, 25 A

Re: [OT] U.S. Crypto-Export Laws (was: [ANNOUNCE] mutt-1.0pre1i RPMs)

1999-08-25 Thread Fairlight
On Wed, Aug 25, 1999 at 05:49:59PM -0400, Pete Toscano thus spoke: > well, at the risk of getting a little too political, all you americans > on this list who feel that these encryption laws are inane should check > out this site: http://www.computerprivacy.com/. i question the > effectiveness o

Re: [OT] U.S. Crypto-Export Laws (was: [ANNOUNCE] mutt-1.0pre1i RPMs)

1999-08-25 Thread Kim DeVaughn
On Wed, Aug 25, 1999, Fairlight ([EMAIL PROTECTED]) said: | | But yeah...this is getting political. Sorry for raising the question...I | should have just let Telsa's post alone (although I'm slightly less | ignorant now, for having questioned it). Sorry to have troubled the rest | of you with th

Re: [OT] U.S. Crypto-Export Laws (was: [ANNOUNCE] mutt-1.0pre1i RPMs)

1999-08-25 Thread Jeremy Blosser
Kim DeVaughn [[EMAIL PROTECTED]] wrote: > On Wed, Aug 25, 1999, Fairlight ([EMAIL PROTECTED]) said: > | > | But yeah...this is getting political. Sorry for raising the question...I > | should have just let Telsa's post alone (although I'm slightly less > | ignorant now, for having questioned it).

[OT] us-crypto (was [ANNOUNCE] mutt-1.0pre1i RPMs)

1999-08-25 Thread Brendan Cully
On Wednesday, 25 August 1999 at 15:00, Ralf Hildebrandt wrote: > On Wed, Aug 25, 1999 at 08:40:42AM -0400, Fairlight wrote: > > > There is no actual crypto shipped in mutt, so the only "problem" is RH > > being finicky about "i" versions on their site, from what I can see. :/ > > Nope. Even the

Writing to IMAP server from command line?

1999-08-25 Thread Steve Talley
Hello, I like that mutt has the ability to write to different folders on an IMAP server, ie. {server}path/to/folder. Is it possible to pipe a message to mutt from the command line, so that it writes to a specified IMAP folder and then exits? If not, is there generic program out there that will

Re: Writing to IMAP server from command line?

1999-08-25 Thread Mikko Hänninen
Steve Talley <[EMAIL PROTECTED]> wrote on Wed, 25 Aug 1999: > I like that mutt has the ability to write to different folders on > an IMAP server, ie. {server}path/to/folder. Is it possible to > pipe a message to mutt from the command line, so that it writes > to a specified IMAP folder and then e

[Announce] mutt-1.0pre1i-2 RPMs

1999-08-25 Thread Thomas Ribbrock
And another one... ok, the bugs in the SRPM should be fixed by now. For the time being, I decided to upload the RPMs to a NEW URL: ^^^ http://indigo.ie/~pumuckel/ ^^^ List of RPMs (all for Red Hat Linux 5.2): - m

Re: [OT] U.S. Crypto-Export Laws (was: [ANNOUNCE] mutt-1.0pre1i RPMs)

1999-08-25 Thread Aaron Schrab
At 18:16 -0500 25 Aug 1999, Jeremy Blosser <[EMAIL PROTECTED]> wrote: > On another angle -- export to Canada is allowed, and Canada has very open > crypto. Has anyone ever tried combining these two facts into something > useful? As I understand it Canadian law specifically disallows exporting of