Re: X-Mailer header
begin quoting what David T-G said on Sat, Mar 30, 2002 at 10:34:59PM -0500: ObTopic: I personally feel that X-Mailer should be available just like every X-anything-else, but I don't care much more than that. Any header that's defined in a standard should be controlled, but X-Mailer is not defined in a standard. It shouldn't be controlled. msg26437/pgp0.pgp Description: PGP signature
Compressed patch problems
I applied the compressed folders patch, and it seemed to work. mutt -v shows: Mutt 1.3.28i (2002-03-13) Copyright (C) 1996-2001 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 2.4.9-31 (i586) [using ncurses 5.2] Compile options: -DOMAIN -DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_POP +USE_IMAP -USE_GSS +USE_SSL -USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK -COMPRESSED +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET ++HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID +HAVE_GETADDRINFO ISPELL=/usr/bin/ispell SENDMAIL=/usr/sbin/sendmail MAILPATH=/var/mail PKGDATADIR=/usr/share/mutt SYSCONFDIR=/usr/etc EXECSHELL=/bin/sh -MIXMASTER To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the flea(1) utility. patch-1.3.28.rr.compressed.1 patch-1.3.28.dw.pgp-traditional.2 At the end of my config, I have: # gzip open-hook \\.gz$ gzip -cd %f %t close-hook \\.gz$ gzip -c %t %f append-hook \\.gz$ gzip -c %t %f # # bzip2 open-hook \\.bz2$ bzip2 -cd %f %t close-hook \\.bz2$ bzip2 -c %t %f append-hook \\.bz2$ bzip2 -c %t %f However, when I run mutt, I get: Error in /home/smcmahon/.muttrc, line 282: open-hook: unknown command Error in /home/smcmahon/.muttrc, line 283: close-hook: unknown command Error in /home/smcmahon/.muttrc, line 284: append-hook: unknown command Error in /home/smcmahon/.muttrc, line 287: open-hook: unknown command Error in /home/smcmahon/.muttrc, line 288: close-hook: unknown command Error in /home/smcmahon/.muttrc, line 289: append-hook: unknown command source: errors in /home/smcmahon/.muttrc WTF? msg26438/pgp0.pgp Description: PGP signature
Re: X-Mailer header
begin quoting what David Collantes said on Sun, Mar 31, 2002 at 08:54:39AM -0500: Any header that's defined in a standard should be controlled, but X-Mailer is not defined in a standard. It shouldn't be controlled. What standards are you talking about? http://www.faqs.org/rfcs/ There are *not* standards. There are plenty of standards; however, X-Mailer is not defined in one, as I clearly stated above. And even if they were, why to offer the possibility to have custom headers (my_hdr) is they are not to be controlled? Controlled = you can't change it, because an RFC defines it Uncontrolled = you can change it with my_hdr because no RFC defines it Hope this clears up the confusion. msg26442/pgp0.pgp Description: PGP signature
Re: Mutt ignoring 'From ' lines in mailbox - Content-Length?
On Sun, Mar 31, 2002 at 05:21:36AM +0200, Sven Guckes wrote: * James Greenwood [EMAIL PROTECTED] [2002-03-30 17:05]: I have recently switched from Pine to Mutt and I have several mailboxes that open fine in Pine but not in Mutt. Mutt seems to concatenate some of the messages together so that there are fewer messages in the index... Are there any Content-Length lines? If so - delete them. It's easy with vi: :g/^Content-Length:$/d ... Does it work now? Hi Sven! I couldn't get that g command to work, had to change it to :g/^Content-Length:.*/d which seemed to do the trick. There were Content-Length lines in the file, which are now gone. However the problem is still there - on the mailbox I tried, pine still sees 102 messages and mutt sees only 3. Any other ideas? .. how can I re-order an existing mailbox file by date so that the file itself changes... Tag all messages and the save them to a new file (folder)... Thanks for that tip, although obviously I won't be able to try it on my corrupt(?) mailboxes until mutt can read them OK. have fun! :-) OK cheers :-) James -- James Greenwood | [EMAIL PROTECTED]
Re: Mutt ignoring 'From ' lines in mailbox - Content-Length?
On 020331, at 16:23:09, James Greenwood wrote However the problem is still there - on the mailbox I tried, pine still sees 102 messages and mutt sees only 3. Any other ideas? Perhaps formail could reformat the mailbox: formail -d oldmbox newmbox -- David Ellement
Re: X-Mailer header
On 03-31-2002 at 09:11 EST, Shawn McMahon [EMAIL PROTECTED] wrote: What standards are you talking about? http://www.faqs.org/rfcs/ :- RFC's are *not* standards. Who ever told you so? Hope this clears up the confusion. It was never a confusion, just a wrong statement: yours. ;-) Cheers, -- David Collantes - http://www.bus.ucf.edu/david/ College of Business Administration, University of Central Florida Few are those who see with their own eyes... feel with their own hearts. smime.p7s Description: application/pkcs7-signature
Re: Mutt ignoring 'From ' lines in mailbox
On Sun, Mar 31, 2002 at 07:29:06AM -0800, David Ellement wrote: On 020331, at 16:23:09, James Greenwood wrote However the problem is still there - on the mailbox I tried, pine still sees 102 messages and mutt sees only 3. Any other ideas? Perhaps formail could reformat the mailbox: formail -d oldmbox newmbox Thanks David - I tried that, it increased the number of visible messages from 3 to 14, but all the extra ones were actually attachments to other messages, not real messages themselves. However I think I've managed to fix the problem !!! I don't know if there's a bug in mutt though. I looked more carefully at the From lines of the messages it was picking up compared to those it wasn't, and in the ones mutt can see, the sender is an e-mail address, e.g. : From [EMAIL PROTECTED] Tue Oct 16 12:48:57 2001 whereas in the messages mutt is ignoring, it is a name, e.g.: From Bruce Smith Wed Oct 17 17:08:13 2001 and just removing the space like this solves the problem: From BruceSmith Wed Oct 17 17:08:13 2001 The names with spaces are obviously related to the fact that the e-mails came from Microsoft Outlook folders originally. I don't know enough about the mailbox format to know whether this is a bug in mutt, or a bug in the LibDBX program I used to translate the Outlook files into mailbox format. If no-one can answer that off the top of their head I'll read some docs/ RFCs I guess, and perhaps make a bug report to the approrpiate person. Anyway my problem should be easy enough to fix now - I can feel a regular expression coming on... Thanks a lot for your help everyone. James -- James Greenwood | [EMAIL PROTECTED]
Re: X-Mailer header
begin quoting what David Collantes said on Sun, Mar 31, 2002 at 10:05:22AM -0500: :- RFC's are *not* standards. Who ever told you so? sigh RFCs are not Standards, but they are standards. If you don't think so, stop using MIME, because it hasn't been adopted as a Standard yet, despite being a standard. College of Business Administration, University of Central Florida Don't make me drive over there and smack you; it's only about 20 minutes from Maitland. :-) msg26447/pgp0.pgp Description: PGP signature
Re: disable UIDL - fetchmail?
Date: Sun, 31 Mar 2002 05:24:20 +0200 From: Sven Guckes [EMAIL PROTECTED] Subject: Re: disable UIDL - fetchmail? * Guilherme Menegon [EMAIL PROTECTED] [2002-03-30 19:02]: My POP3 server does not support UIDL (unique ID listing) and because of that mutt can not fetch my mail. How can i disable UIDL in mutt? I don't need this feature since i leave no messages on server. well, if you are sure that mutt cannot do something then why do you want a solution with mutt? ;-) I'd say set pop_delete=yes - but will that help? Have you considered downloading your mails with fetchmail yet? Actually i am not sure mutt can not do it, otherwise why would i post it here? I already have set pop_delete=yes (that is why i do not leave messages on server). And yes, fetchmail can disable UIDL easily (set no uidl), but i like mutt and wanted a one-prog solution... Guilherme __ Guilherme Menegon ArantesSao Paulo, Brasil __
OT: Re: X-Mailer header
On 03-31-2002 at 12:24 EST, Shawn McMahon [EMAIL PROTECTED] wrote: RFCs are not Standards, but they are standards. sight Plonk! College of Business Administration, University of Central Florida Don't make me drive over there and smack you; it's only about 20 minutes from Maitland. :-) Ops! Hmmm, no, I take the plonk back. Let's see (browse his USENET and ML thread list), you made it to number 42 this month, 143 for the year. Ahhh, the message is signed, excellent! Totally valid in the court of law ;-) Bah, will not be necessary: be sure to bring with you your curriculum, specially your best Perl script. :- Over and out. Cheers, -- David Collantes - http://www.bus.ucf.edu/david/ College of Business Administration, University of Central Florida The only thing that interferes with my learning is my education. smime.p7s Description: application/pkcs7-signature
Re: X-Mailer header
* Michael Tatge [EMAIL PROTECTED] [2002-03-30 13:35:04 +0100]: NO. It's Period. Please don't make a new OT thread out of this, especially you David. ;-) Well, I just did some googling and found a bunch of sites about quote characters; none of my attempts at searching the RFCs turned up anything useful, but I don't think I was using very good search terms. There doesn't seem to be an authoritative answer on this, despite what one of the eminent presences on this list implied a while back (in private; hence why I changed from to in the first place...). So, while I'm definitely interested in following the standards, there doesn't seem to be one. Eliminating the space saves data, but more importantly it allows one more character to fit actual text into. Couple this with the fact that I've never heard of a mailer that triggered on for a quote, but not , and I don't see a compelling reason to switch back. Feel free to point out the authoritative source if there is one; I've changed my mutt settings plenty of times in response to things people say here (most recently my attribution string). By the way, Sven, you might want to check out this URL, I'm getting a 403 error: http://www.math.fu-berlin.de/~guckes/message/editing.html -- Hi David! :) msg26453/pgp0.pgp Description: PGP signature
Re: X-Mailer header
* John Buttery ([EMAIL PROTECTED]) wrote: * Michael Tatge [EMAIL PROTECTED] [2002-03-30 13:35:04 +0100]: NO. It's Period. Please don't make a new OT thread out of this, especially you David. ;-) ^ The problem with using just '' is that the quote string merges with the text and becomes difficult to disinguish, not only for users, but for reflowing algorithms which often have to put up with crap like: | %JF Bla bla That space goes a long way to ease working out what's a INITAL quote and what's not. If you want to turn: Foo bar wibble Into: Foo bar wibble Then that's fine (although I prefer the spaces; quotes rarely need to nest deeply, and the space makes working out the depth easier), but please don't say: Foo bar wibble is better because it saves a single character. I personally find quoting without a space after the quote more irritating than any of the exotic quote strings I've come across, with the possible exception of: C=This is quoted text C=Bla bla bla C= C=Cookie to whoever works out what this brain dead quote string is C=supposed to represent. With a space even that fits in with the (possible initial)([|%=#:;!$*-+])(possible initial) interpretation; without it, it's difficult to work out whether Bla is part of a name or initial or not. -- Thomas 'Freaky' Hurst - [EMAIL PROTECTED] - http://www.aagh.net/ - The mosquito is the state bird of New Jersey. -- Andy Warhol
update encoding?
Hello Everyone, I have been using mutt for abour 4 years now. Very happy with it I must say. Anyways, my system adminstrator had just updated mutt to 1.3.24i (2001-11-29) and since then, everytime I send a message either a forward, reply or even a new message, I get the following message when I hit send: ~/Mail/tmp/mutt-csce-4803-30 [#1] modified. Update encoding? ([yes]/no): How can I get rid of it? Its annoying to hit 'y' everytime I want to send an email, and besides, I do not see any difference in emails even when I hit n! Thanx for your help. --Sadiq
Re: X-Mailer header
* Thomas Hurst [EMAIL PROTECTED] [2002-04- 1 02:52:00 +0100]: * John Buttery ([EMAIL PROTECTED]) wrote: ^ The problem with using just '' is that the quote string merges with the text and becomes difficult to disinguish, not only for users, but for reflowing algorithms which often have to put up with crap like: | %JF Bla bla That space goes a long way to ease working out what's a INITAL quote and what's not. Hmm. That's a good point. Not so much the human parseability angle, but I suppose it would make things easier for the machine parsers. please don't say: Foo bar wibble is better because it saves a single character. I personally find Well, of course it's better for that reason. Sure it's a small improvement, but some is better than none. However, it's quite possible that the reasons for doing it the other way outweigh the space savings. quoting without a space after the quote more irritating than any of the exotic quote strings I've come across, with the possible exception of: C=This is quoted text C=Bla bla bla C= C=Cookie to whoever works out what this brain dead quote string is C=supposed to represent. Yeah; the thing about that quoting is that it can be useful to trace heavily-nested attributions when people mangle/remove some/all of the attribution lines. Of course, the real fix for this is for the previous repliers to have quoted properly, not to introduce a multi-character quote...um...character. :) I like your idea of squashing all leading characters, but leaving a space after the group as a whole. That would save some space, and not make things any harder on the parsers, since you're still looking at ( zero or more ( characters followed by zero or one spaces ) ) followed by a space. I'll have to percolate on this some, maybe I need to change my quote string back. No biscuit for the person who said was nonstandard, you know who you are. :) -- ...floor pie... msg26456/pgp0.pgp Description: PGP signature
Re: X-Mailer header
Alas! John Buttery spake thus: So, while I'm definitely interested in following the standards, there doesn't seem to be one. It's not a formal standard in any sense of the word standard; it's more like a deeply rooted tradition that goes all the way back to the early days of USENET (maybe even earlier). -- Rob 'Feztaa' Park [EMAIL PROTECTED] -- Then you admit confirming not denying you ever said that? NO! ... I mean Yes! WHAT? I'll put `maybe.' -- Bloom County msg26458/pgp0.pgp Description: PGP signature
