Re: mutt crashes -- 1.2.5 -> 1.4
* MindFuq <[EMAIL PROTECTED]> [2002-09-20 15:43]: > How do I upgrade mutt? http://www.math.fu-berlin.de/~guckes/mutt/install.php3 > I tried using rpm with the upgrade option, and > it had a dependancy on libc.so.6(GLIBC_2.2). > Then when I tried to upgrade GLIBC, > I got several screenfulls of other programs > that require the old version that I'm using. > I got the feeling I would have scrap > everything and install the latest OS. .. or install a stable version. > If I go get the latest tarball, will that have the > dependancy issue I ran into with the rpm file? [40+ lines of fullquote] if you have to tofu then please do not use mutt - thankyou. > X-Mailer: iPlanet Messenger Express 5.1 HotFix 1.4 (built the nerve.. > From: MindFuq <[EMAIL PROTECTED]> .. and buy yourself a name! Sven [who should not answer people without a name]
Re: Display certain threads
* On 2002.09.20, in <[EMAIL PROTECTED]>, * "Heiko Heil" <[EMAIL PROTECTED]> wrote: > Hello Mutt Users, > > what can I do in order to display all (and complete) threads which are > initiated by myself && which are containing messages from me. I'm not sure how to add in the second part of this, offhand. But you could try a macro that does this: # collapse all threads, showing only the initial msg ~P # limit to msgs from you # uncollapse, showing all msgs # tag all threads which are tagged ~T # limit to tagged msgs ~T # untag all tagged msgs You could probably build on that to locate messages that don't contain further messages from you, tag them, limit further, etc. But my brain hurts now, so I'm not sure exactly how. -- -D.We establised a fine coffee. What everybody can say Sun Project, APC/UCCO TASTY! It's fresh, so-mild, with some special coffee's University of Chicago bitter and sourtaste. "LET'S HAVE SUCH A COFFEE! NOW!" [EMAIL PROTECTED] Please love CAFE MIAMI. Many thanks.
charset input trouble
Hi, I have some trouble here getting Mutt to recognize non ASCII characters. Displaying them works wonderfully, other console programs work fine, too (bash, vi, mc, irssi, ...). The facts: Environment: * FreeBSD 4-stable * LANG=de_DE.ISO8859-1 LC_* unset Mutt: * Mutt 1.4i from the FBSD port tree * using SLANG (NCURSES doesn't work, too) set allow_8bit set use_8bitmime set charset=iso-8859-15 set send_charset="us-ascii:iso-8859-15:utf-8" set locale=de Setting the LC_ALL, LC_CTYPE or LANG environment variables to different settings does not help. I could not find any hints in the archive or with Google. Now I'm stuck. Any ideas? Thanks, Rob. -- r o b e r t | l i l l a c k www.lillaxsitedesign.de/rob secure mail key: 0xE7FFDF77
Display certain threads
Hello Mutt Users, what can I do in order to display all (and complete) threads which are initiated by myself && which are containing messages from me. I thought about the limit(l)-feature (e.g. l ~L my@email), but I didn't succeed... :-( -- Best regards Heiko
Re: [OT] Correct way to quote?
On Fri, Sep 20, 2002 at 11:59:32AM -0400, Ken Weingold wrote: > Actually, send a mail from Netscape Mail to mutt and you might find > that those '|'s are actually '> 's. I saw this on some mailer, maybe > Apple Mail. Really confusing, but that was the case. Now I found out what confused me. I often send mail with an inline gpg signature because I'm having friends whose muas are having problems with MIME. My problem was that I had the option "Allow flowed text" turned on in the Enigmail preferences. When sending an inline signed mail with these preferences to mutt (or any other mua) the '|'s don't disappear. After turning off this option everything works pertect. Regards Markus -- - Markus Garschall - <[EMAIL PROTECTED]> - - GnuPG: 4B8D B75E D8F2 A13A BAD9 25E4 319F 90FB 93B7 70B8 ID:93B770B8 - - My Pages: http://stud3.tuwien.ac.at/~e0125356/(gpg/93B770B8.gpg) --- -
Re: New mail to list.
On Tue, Sep 17, 2002 at 12:11:27PM -0400, darren chamberlain wrote: > * Alex Polite <[EMAIL PROTECTED]> [2002-09-17 08:22]: > > How do I start composing a new message to a mailing list? What I > > usually do now is push "L" for list-reply the remove the body and > > appropriate headers. > > I have this in my config: > > subscribe mutt-users@ > mailboxes =lists/mutt-users > folder-hook =lists/mutt-users "macro index m \"[EMAIL PROTECTED]\"" > > subscribe mutt-dev@ > subscribe @bugs.guug.de > mailboxes =lists/mutt-dev > folder-hook =lists/mutt-dev "macro index m \"[EMAIL PROTECTED]\"" > > When I hit m in my mutt folders, it executes the macro, with the > appropriate stuff filled in. > what would be nice would be to have a general config for all ML boxes I'm thinking of something like that : my conf is : boxes tree : ~/Mail/ML/mutt-users, ~/Mail/ML/mutt-users-fr, ~/Mail/foo ... ~/.muttrc: folder-hook =ML "source ~/.mutt/muttrc-ML" ~/.mutt/muttrc-ML: subscribe [EMAIL PROTECTED] subscribe [EMAIL PROTECTED] bind index r list-reply bind pager r list-reply alias mutt-users International mutt ML <[EMAIL PROTECTED]> alias mutt-users-fr French mutt ML <[EMAIL PROTECTED]> I need a macro like this : macro index m current_box_name it would put "mutt-users" for example, then it would work thanks to the alias My question is : how can I get current_box_name ? -- Bernard Massot msg31091/pgp0.pgp Description: PGP signature
Re: mutt crashes -- 1.2.5 -> 1.4
- On Fri, 20.Sep.2002, 11:42EDT, MindFuq uttered: > How do I upgrade mutt? I tried using rpm with the upgrade option, and > it had a dependancy on libc.so.6(GLIBC_2.2). Then when I tried to > upgrade GLIBC, I got several screenfulls of other programs that require > the old version that I'm using. I got the feeling I would have scrap > everything and install the latest OS. No need to scrap everything. Just go grab the source tarball and build it yourself. Or better yet you could use a spec file and build your own mutt RPM which you could then install. Doesn't look like the 1.4i source tarball comes with a spec so you'd have to find on on the net somewhere or write it yourself. > If I go get the latest tarball, will that have the dependancy issue I > ran into with the rpm file? > Not if you build mutt from source. Ciao, Keith. -- "Isn't it time we care and lose the hate Understand our fears" -- Dream Theater, "Blind Faith"
Re: [OT] Forcing correct quotes
* Sven Guckes <[EMAIL PROTECTED]> [2002-09-20 16:40 +0200]: > * Johan Almqvist <[EMAIL PROTECTED]> [2002-09-20 09:18]: > > > Sven [using sed as the display_filter > > >to correct incorrect quoting] > > > > Care to share? > > guckes.net/setup - as usual. I don't see anything in there that looks appropriate. Your muttrc files reference both df.default and sed-default, but neither of those exists. Your procmailrc does a lot of rewriting of emails, too, but it doesn't seem to have anything about redoing quoting. Which config file has the appropriate settings? -- [EMAIL PROTECTED] / phil! / DNRC / http://www.geeksimplex.org/phil/ PGP: ID: D8C75CF5 print: 0A7D B3AD 2D10 1099 7649 AB64 04C2 05A6 --- -- If you capture the hero's starship, keep it in the landing bay with the ramp down, only a few token guards on duty and a ton of explosives set to go off as soon as it clears the blast-range. -- Evil Overlord's Handbook, entry 116 --- --
Re: $mail_check and $timeout
On Fri, Sep 20, 2002 at 01:23:15PM +0200, Johan Svedberg wrote: > Could some friendly soul describe the differens between these two > settings ($mail_check and $timeout)? I've read the manual but I still > don't quite understand. Does one overwrite the other one? Is there a > reason why I wouldn't want these to be set equalent? The following explanation is based on general knowledge and observation of mutt's behavior, not on any actual knowledge of mutt's internals. When mutt finishes executing a function or command in response to user input from the keyboard, it checks for new mail if it has been longer than 'mail_check' seconds since the last time it checked. So if you are actively using mutt, it will check periodically for new mail, the period being about 'mail_check' seconds. However, if you are not giving mutt any commands, mutt is just sitting there waiting for input and has no opportunity to check for new mail. Mutt gets around this problem by having a keyboard inactivity timer that is restarted every time mutt receives input from the keyboard and otherwise times out 'timeout' seconds later. When this timer times out, mutt either: a) effectively executes a noop function and again checks for new mail if it has been longer than 'mail_check' seconds since the last time it checked, or b) always checks for new mail. I don't know which of a) or b) is true since I've always had 'timeout' >= 'mail_check'. If mutt is just sitting there and b) is true, mutt will check for new mail every 'timeout' seconds. If instead a) is true, mutt will check for new mail at an interval that's between 'mail_check' and 'mail_check'+'timeout' seconds. I have 'timeout' set to 10 and that's been close enough for me. HTH & HTA (Hope That's Accurate), Gary -- Gary Johnson | Agilent Technologies [EMAIL PROTECTED] | Spokane, Washington, USA http://www.spocom.com/users/gjohnson/mutt/ |
Re: [OT] Correct way to quote?
On Fri, Sep 20, 2002, Markus Garschall wrote: > Since I'm using Netscape beside Mutt as Mailer, I wanted to know whether > the old way to quote things in an E-Mail is the only correct one. > > e.g.: > > foo > > foo > > In the default-install Netscape does following: > > | bar > | bar Actually, send a mail from Netscape Mail to mutt and you might find that those '|'s are actually '> 's. I saw this on some mailer, maybe Apple Mail. Really confusing, but that was the case. -Ken
set pop_checkinterval
I can't seem to get set pop_checkinterval=60 to work. Is mutt suppose to get the new messages or just check for them. In any case I am not notified by mutt of any new messages available ever. I prefer to use mutt to check mail as I only have one pop account and its much simpler to use mutt instead of procmail, fetchmail and mutt. -- "I mean they are gonna kill ya so like if ya give em a quick, short, sharp, shock they won't do it again. Dig it! I mean he got off lightly cuz I would have given him a thrashing. I only hit him once. It was only a difference of opinion but really... I mean good manners don't cost nothin do they. Eh?"
Re: mutt crashes -- 1.2.5 -> 1.4
How do I upgrade mutt? I tried using rpm with the upgrade option, and it had a dependancy on libc.so.6(GLIBC_2.2). Then when I tried to upgrade GLIBC, I got several screenfulls of other programs that require the old version that I'm using. I got the feeling I would have scrap everything and install the latest OS. If I go get the latest tarball, will that have the dependancy issue I ran into with the rpm file? - Original Message - From: Sven Guckes <[EMAIL PROTECTED]> Date: Friday, September 20, 2002 8:52 am Subject: Re: mutt crashes -- 1.2.5 -> 1.4 > * MindFuq <[EMAIL PROTECTED]> [2002-09-20 07:27]: > > I've started using Sven Guckes configuration files, and mutt seems > > to crash much more frequently (enough to make it unusable). [..] > > It looks like I'll have to dump his config files.. > > well, i have been using mutt 1.4 for quite a while - > but none of my setup has made mutt crash in years. > > if you expect my full setup to work with your > personal stuff, well, you better think again. > after all my setup sources about a dozen files > which might not exist in your environment and > uses lots of things you might not need at all. > > > Could these crashes be the result of using config > > files not made for my version (1.2.5i)? [..] > > It crashed occasionally when I had no config files at all, but I > > could usually at least accomplish something before the crash. > > well, if it's not the setup then it probably > is the version itself, right? so - upgrade! > > otherwise you are just missing some 22 months > of development and tread on old bugs. besides, > you are not wasting your own time but ours, too. > > Sven > > -- > Sven Guckes[EMAIL PROTECTED] > http://guckes/net/mutt/mutt-1.2.5 [2000-07-29] > http://www.mutt.org Admins - please upgrade > mutt-1.4[2002-05-29] ftp://ftp.mutt.org/mutt/ the user > version to 1.4! > mutt-1.5.1 [2002-05-02] ftp://ftp.mutt.org/mutt/devel > news:comp.mail.mutt
Re: $mail_check and $timeout
* Johan Svedberg <[EMAIL PROTECTED]> [2002-09-20 11:33]: > Could some friendly soul describe the differens > between these two settings ($mail_check and $timeout)? the timeout counts down after your last key press. mail_check works continuously. > I've read the manual but I still don't quite understand. > Does one overwrite the other one? Is there a reason > why I wouldn't want these to be set equalent? yes. think. homework. rtfm 4.11 "IMAP Support". Sven
Re: mutt crashes -- 1.2.5 -> 1.4
* MindFuq <[EMAIL PROTECTED]> [2002-09-20 07:27]: > I've started using Sven Guckes configuration files, and mutt seems > to crash much more frequently (enough to make it unusable). [..] > It looks like I'll have to dump his config files.. well, i have been using mutt 1.4 for quite a while - but none of my setup has made mutt crash in years. if you expect my full setup to work with your personal stuff, well, you better think again. after all my setup sources about a dozen files which might not exist in your environment and uses lots of things you might not need at all. > Could these crashes be the result of using config > files not made for my version (1.2.5i)? [..] > It crashed occasionally when I had no config files at all, but I > could usually at least accomplish something before the crash. well, if it's not the setup then it probably is the version itself, right? so - upgrade! otherwise you are just missing some 22 months of development and tread on old bugs. besides, you are not wasting your own time but ours, too. Sven -- Sven Guckes[EMAIL PROTECTED] http://guckes/net/mutt/ mutt-1.2.5 [2000-07-29] http://www.mutt.org Admins - please upgrade mutt-1.4[2002-05-29] ftp://ftp.mutt.org/mutt/ the user version to 1.4! mutt-1.5.1 [2002-05-02] ftp://ftp.mutt.org/mutt/devel news:comp.mail.mutt
Re: [OT] Forcing correct quotes
* Sven Guckes <[EMAIL PROTECTED]> [020920 02:07]: > ">_" is the de-facto standard. period. > making this an option was a bad idea. * Johan Almqvist <[EMAIL PROTECTED]> [2002-09-20 09:18]: > Note the space after the > (i.e. >_) which makes things a lot > easier to read than just > (which I also consider broken) amen! > > Sven [using sed as the display_filter > >to correct incorrect quoting] > Care to share? guckes.net/setup - as usual. Sven
Re: S/MIME interoperability
You are right. If you look at smime.c you will see that Mutt desperatly needs either smime-type or (to satisfy Netscape 4.x mailers) a Content-Description. As s/mime is in development, we all have to wait or find some workarounds for it. See my mail from 18-09-02 for my current solution. I'm sure we have to discuss this further in private or join the mutt-dev list. BTW: the right way of figuring out if we have an "enveloped-data" or "signed-data" would be to look into the data itself (I was told). You can do this by: openssl smime -pk7out -in mail.msg | openssl asn1parse -dump Timo T. Rajala [2002-09-20 14:18]: > * Timo T. Rajala <[EMAIL PROTECTED]> writes: > > One difference is that the "smime-type=enveloped-data;" row is missing > > from the MS mail. I inserted this row in the MS mail and opened the > > mail in mutt: now both signature check and decrypt works. > > > > My question is: Is the MS MUA not following the S/MIME standard by > > omitting this row or is mutt wrong by not being able to handle it > > without this row? > > So this MS MUA SHOULD include "smime-type", but is not and mutt should > be able to determine the MIME type from the file extension but is not. -- Alex Pleiner zeitform Internet Dienste Fraunhoferstrasse 5 64283 Darmstadt, Germany http://www.zeitform.deTel.: +49 (0)6151 155-635 mailto:[EMAIL PROTECTED]Fax: +49 (0)6151 155-634 GnuPG/PGP Key-ID: 0x613C21EA
Re: Weird bug/feature ?
Cedric Duval [[EMAIL PROTECTED]] wrote:
> 'a' attaches a file, not a message (of course, the message can be in one
> file like with the mbox format - but not with maildir).
>
> There is a more appropriate function for what you want to do:
> ('A').
Right, I didn't know about the attach-message command. Just thought that
as the message was in a file, I could go and select it as any other
file, but I guess when I select the maildir, mutt recognizes it as such
instead of seeing it as just a directory.
Many thanks!!
--
Bruno Lustosa, aka Lofofora | Email: [EMAIL PROTECTED]
Network Administrator/Web Programmer | ICQ UIN: 1406477
Rio de Janeiro - Brazil |
msg31080/pgp0.pgp
Description: PGP signature
$mail_check and $timeout
Hi, all. Could some friendly soul describe the differens between these two settings ($mail_check and $timeout)? I've read the manual but I still don't quite understand. Does one overwrite the other one? Is there a reason why I wouldn't want these to be set equalent? Regards, Johan Svedberg
$mail_check and $timeout
Hi, all. Could some friendly soul describe the differens between these two settings ($mail_check and $timeout)? I've read the manual but I still don't quite understand. Does one overwrite the other one? Is there a reason why I wouldn't want these to be set equalent? Regards, Johan Svedberg
Re: S/MIME interoperability
* Timo T. Rajala <[EMAIL PROTECTED]> writes: > One difference is that the "smime-type=enveloped-data;" row is missing > from the MS mail. I inserted this row in the MS mail and opened the > mail in mutt: now both signature check and decrypt works. > > My question is: Is the MS MUA not following the S/MIME standard by > omitting this row or is mutt wrong by not being able to handle it > without this row? I'm quoting from RFC2633: 3.2: ... Because there are several types of application/pkcs7-mime objects, a sending agent SHOULD do as much as possible to help a receiving agent know about the contents of the object without forcing the receiving agent to decode the ASN.1 for the object. The MIME headers of all application/pkcs7-mime objects SHOULD include the optional "smime- type" parameter, as described in the following sections. 3.2.1: For the application/pkcs7-mime, sending agents SHOULD emit the optional "name" parameter to the Content-Type field for compatibility with older systems. Sending agents SHOULD also emit the optional Content-Disposition field [CONTDISP] with the "filename" parameter. If a sending agent emits the above parameters, the value of the parameters SHOULD be a file name with the appropriate extension: MIME TypeFile Extension Application/pkcs7-mime (signedData, .p7m envelopedData) Application/pkcs7-mime (degenerate .p7c signedData "certs-only" message) Application/pkcs7-signature .p7s So this MS MUA SHOULD include "smime-type", but is not and mutt should be able to determine the MIME type from the file extension but is not. -- Timo T. Rajala
Re: at last message
On Fri, Sep 20, 2002 at 10:20:18AM +0200, Nicolas Rachinsky wrote: > * Ricardo SIGNES <[EMAIL PROTECTED]> [2002-09-19 20:46 -0400]: > [...] > > I can't find a way to force not to move, nor can I find a way > > to get "back to where I was," taking into account the move that may result > > from . > > > > Is there a solution other than hacking the source? > > Yes. > From the fine manual: > | 6.3.208 resolve Man! I searched, with no joy. I'll put some $resolve toggling in there. Thanks. -- rjbs msg31076/pgp0.pgp Description: PGP signature
S/MIME interoperability
I am currently using mutt 1.5.1 and the S/MIME functions have proved to work without problems. But today I received an encrypted and signed S/MIME message which could not be neither verified nor decrypted by mutt (openssl). Here are the significant headers from two different mails, the first mail is created by Lotus Notes R5 and the second is created by some Microsoft MUA (don't know which, no MUA header). Both are signed and encrypted. The Notes mail works, the MS mail doesn't: Lotus Notes: Content-Transfer-Encoding: base64 Content-Type: application/x-pkcs7-mime; smime-type=enveloped-data; name=smime.p7m Content-Disposition: attachment; filename="smime.p7m" Content-Description: S/MIME Enveloped Data Microsoft unknown MUA: Content-Type: application/x-pkcs7-mime; name="smime.p7m" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7m" One difference is that the "smime-type=enveloped-data;" row is missing from the MS mail. I inserted this row in the MS mail and opened the mail in mutt: now both signature check and decrypt works. My question is: Is the MS MUA not following the S/MIME standard by omitting this row or is mutt wrong by not being able to handle it without this row? Any comments? -- Timo T. Rajala
[OT] Forcing correct quotes (was: Correct way to quote?)
* Sven Guckes <[EMAIL PROTECTED]> [020920 02:07]: > ">_" is the de-facto standard. period. > making this an option was a bad idea. Note the space after the > (i e >_) which makes things a lot easyier to read than just > (which I also consider broken) > Sven [using sed as the display_filter >to correct incorrect quoting] Care to share? -Johan -- Johan Almqvist http://www.almqvist.net/johan/qmail/
Re: at last message
* Ricardo SIGNES <[EMAIL PROTECTED]> [2002-09-19 20:46 -0400]: [...] > I can't find a way to force not to move, nor can I find a way to > get "back to where I was," taking into account the move that may result from > . > > Is there a solution other than hacking the source? Yes. >From the fine manual: | 6.3.208 resolve | | Type: boolean | | Default: yes | | When set, the cursor will be automatically advanced to the next | (possibly undeleted) message whenever a command that modifies the | current message is executed. Nicolas
mutt crashes
I've started using Sven Gluckes configuration files, and mutt seems to crash much more frequently (enough to make it unusable). I get: --- Detected an attempt to write across stack boundry Terminating /usr/bin/mutt "libsafe violation for /usr/bin/mutt, pid=1981; overflow caused by memcopy()" Null message body; hope that's ok --- It looks like I'll have to dump his config files.. which will be a bummer because I already customized them. I noticed some people run different config files for different versions. Could these crashes be the result of using config files not made for my version (1.2.5i)? Does anyone recommend a config file for this version? It crashed occasionally when I had no config files at all, but I could usually at least accomplish something before the crash. With Sven's scripts, I can't even page down in the first message I open w/out a crash.
