Re: support for compressed folders in 1.2?
It works for compressed mutt mail folders. Then what about the supporting for compressed mail folders in procmail when using mutt? I use procmail to deliver mails to different mail folders. After I've changed the mutt folders to gz format, procmail still delivers mails as uncompressed format, they can not work well together. thanks. zd === From: Lars Hecking Subject: Re: support for compressed folders in 1.2? Date: Thu, 18 May 2000 08:59:24 -0700 > I'm making the move from 0.95.5i to 1.2 to get all of the useful > changes therein. However, I'd been using Alain Penders' support for > compressed folders in 0.95.5i, and now can't live without it. :) > > I tried just patching the existing diffs into 1.2, but of course > that failed. Before I go through and port this stuff over to 1.2, > does anybody know if this has already been done? Thanks much! http://www.spinnaker.de/mutt/#compressed
Re: Sender profiles, personalities, setting from address etc.
I think this is a good idea. I will use it. Thanks Martti, Kelly Quoting Martti Rahkila <[EMAIL PROTECTED]>: > On Thu May 18, 2000 at 09:44:31AM +0100, Telsa Gwynne muttered: > > > On Thu, May 18, 2000 at 12:38:31PM +0530 or thereabouts, Suresh Ramasubramanian >wrote: > > > Martti Rahkila proclaimed on mutt-users that: > > > > > > >http://www.iki.fi/martti.rahkila/mutt/profiles.html > > > > > > You could send your .muttrc to dotfiles.org if you think it is special, so > > > that other users can adapt it to their needs. > > > > That would be cool. > > Hmm, I'm not sure if there's anything special in my muttrc apart > from the profile macros. In fact, my muttrc is pretty much the > same as Roland Rosenfeld's ultimate mutt settings execpt that > I have all the sender related parameters in separate profile files. > > > > >Maybe it's even worth adding to the Mutt link page or FAQ > > > >once its ready? > > > > > > I dunno, The mutt faq and manual documents this pretty ok, afaik :) > > > Pretty good one though. > > > > I think it's worth linking. The problem with the manual is that it's > > so very massive and organised in a particular fashion. It's a fantastic > > reference once you have an idea of what's going on. It's not great if > > you are new and simply want to know "How do I (set up profiles|get > > PGP/GnuPG working|organise folders)?": ie, one particular little task > > which involves some stuff from section 4 about patterns, and a whole > > bunch of variables which are scattered through section 6 in alphabetical > > rather than "things which are often tweaked together" order. > > > > I'm not complaining about the manual, btw: I think it's great, and I > > don't think you can combine both a reference and a list of such tasks > > easily into one document. I do think, however, that as well as all > > the muttrcs linked off www.mutt.org where we all try to explain > > every variable we use, some things like this which explain one particular > > task would be great. > > I agree, the idea of a profile is simple but in order to make good use > of it, you have to dig up several things from the manual. > Like how to define macros, what variables affect sending, > replying, pgp and so on. > > For example, I would have never thought of procmail filtering incoming > mail for getting pgp to work properly :-) > > Anyway, thanks, Telsa and Suresh, for your quick response! > > Martti Rahkila > - yet another (happy) Mutt-user > > [EMAIL PROTECTED] >
Re: Two "problems" with mutt-1.2
Mikko -- ...and then Mikko Hänninen said... % David T-G <[EMAIL PROTECTED]> wrote on Fri, 19 May 2000: % > % You're not supposed to be patching manual.sgml, manual.txt or % > % manual-6.html -- those file are auto-generated. Instead, a change in % > % the manual.sgml.head or manual.sgml.tail. Or like in this case, since % > % > Whoops :-) Guess I need the CVS source for that, and I don't got it. % % Actually, it's provided with the standard Mutt source, in the doc subdir. % I haven't ever used the CVS myself, yet I've done quite a bit of document % patching... Now, that's curious... I did a recursive grep for sendmail_wait even with ".*" between each letter for the man page style, and then modified those files that had the >0 reference... I wonder why I never saw init.h! % % But in this case all the relevant changes are done to the init.h file. % % Here's an example patch, using my suggestion, not yours. :-) Thanks :-) % % % Mikko :-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: Interesting From: header problem
Matthew Dharm <[EMAIL PROTECTED]> wrote on Fri, 19 May 2000: > > Nope, sorry. There's been talk of ways to solve this, and I think even > > the best way has been figured out (creating a pseudo-operator which tells > > that the next pattern operator should match against the headers of the > > replied-to message, not the current message, which could then be used in > > send-hooks). It's just that nobody's done it yet. > > Interesting. I guess people view 'reply' as just a special case of > 'send'... I actually view them as very different things, but oh well. Well, if you don't, then you run into all sorts of issues like which do you process first, reply-hooks or send-hooks? Or you could set things so that when doing a reply, only reply-hooks get executed, and send-hooks only become active when doing a new mail -- but that would be duplicating a lot of stuff a lot of the time, then. The last time it was discussed (and I was the one proposing reply-hooks then) I at least became convinced that what I described was the best way to implement it. Whatever the solution is, you at least make sure the user can ensure a send-hook can undo actions from a "reply-hook" (or comparable), and vice versa. > Well, if nobody is working on this, can someone give me a couple of > pointers of good places to start? After the linux kernel, this can't be > too hard (famous last words). Actually, I'm not that familiar with Mutt code. :-) Even if I've created one patch for Mutt -- which was soon regarded as superfluous and I came to use a different solution myself, too. :-) You may want to ask this on the mutt-dev list... > The problem is that reverse_name doesn't change my address because the mail > I'm replying to was addressed to a mailing list, not to any of my > alternates. So my from is my default from. Right. Unless you determine that this address means it's a reply to a list email, but then it could also be a completely new email just as well. 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 / If you don't care where you're going, you're never lost.
Re: Two "problems" with mutt-1.2
Mikko -- ...and then Mikko Hänninen said... % David T-G <[EMAIL PROTECTED]> wrote on Fri, 19 May 2000: % % > Hall, you've already seen the answer to this, but it's "the value must be % > numeric, not descriptive". % > % > Mutt folks, is this any tougher to fix than the attached patch? We keep % > hearing this question (no, Hall, you're not alone!), so it seems that the % > manual needs a little clarification... % % Well, it *does* state that the type is "number"? Also it talks about Yeah, but :-) % "number of seconds"... It seems a bit dumb to cater to those who can't % read. :-) But there could be a space added, like "> 0" and "< 0" in % which case it wouldn't look so much like a string. That sounds like a start. Just because we know it should be obvious doesn't mean that we can't make it more clear, and I don't think that this dumbs down the manual too terribly much... % % % > Let's see how I did making my first patch :-) % % Not too bad. :-) Hully gee! % % You're not supposed to be patching manual.sgml, manual.txt or % manual-6.html -- those file are auto-generated. Instead, a change in % the manual.sgml.head or manual.sgml.tail. Or like in this case, since Whoops :-) Guess I need the CVS source for that, and I don't got it. % it's a Mutt variable, the description is pulled out from the comments % in init.h. If you change it there, it will propagate into every place. I'll leave it for someone else with the proper files to do the right way (hint). % % (Except for the sample Muttrc, I think... Not too sure about muttrc.man % either but I do think that's auto-generated?) Thanks, Marius! % % % 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 / % Life is much too important to be taken seriously. :-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: Interesting From: header problem
On Fri, May 19, 2000 at 11:20:09PM +0300, Mikko Hänninen wrote: > Matthew Dharm <[EMAIL PROTECTED]> wrote on Thu, 18 May 2000: > > > (2) I'm _replying_ to mail that was sent to a mailing list. This is the > > tough case -- the To: field is some other random address, and the list > > isn't mentioned in the headers (note that I'm not list-replying or > > group-replying). So far I haven't figured out how to do this. > > Do you want to set your From header when you're sending *to* a mailing > list? That can be done with send-hook and the ~l pattern operator. > > If not, and you really mean what you say, then this isn't currently > do-able in Mutt. I really mean what I say. > > I guess what I'm basically looking for is a reply-hook. Something that I > > can use to change things based on the message I'm replying to. Does > > anything like that exist? > > Nope, sorry. There's been talk of ways to solve this, and I think even > the best way has been figured out (creating a pseudo-operator which tells > that the next pattern operator should match against the headers of the > replied-to message, not the current message, which could then be used in > send-hooks). It's just that nobody's done it yet. Interesting. I guess people view 'reply' as just a special case of 'send'... I actually view them as very different things, but oh well. > > Would it be possible to get it added as a > > feature? > > Sure, if you write it, or get someone to write it for you. :-) Well, if nobody is working on this, can someone give me a couple of pointers of good places to start? After the linux kernel, this can't be too hard (famous last words). > Actually, you can also match against the *From* address in a send-hook > as well. I'm not sure if this helps you at all, but you can use that > to find out when your from address has changed based on $reverse_name. > And I've not tried this, but I think you can also override the From > address from $reverse_name with the use of my_hdr From. The problem is that reverse_name doesn't change my address because the mail I'm replying to was addressed to a mailing list, not to any of my alternates. So my from is my default from. Matt Dharm -- Matthew Dharm Home: [EMAIL PROTECTED] Senior Engineer, QCP Inc.Work: [EMAIL PROTECTED] M: No, Windows doesn't have any nag screens. C: Then what are those blue and white screens I get every day? -- Mike and Cobb User Friendly, 1/4/1999
Re: Putting warnings into mutt
Antoine Martin <[EMAIL PROTECTED]> wrote on Fri, 19 May 2000: > Is it possible to put warning messages in the status bar > with a macro like "There are no messages." or "You are on the last page." Not as such. You can change the Status bar's format to include any message you like, at any point where you can run Mutt commands. However those commands likely can't get this kind of out of Mutt, ie. you can't really tell at which index position you are, how many pages there are, and so on, so those commands can't really do such messages. Regards, 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 / < The information went data way >
Re: Interesting From: header problem
Matthew Dharm <[EMAIL PROTECTED]> wrote on Thu, 18 May 2000: > Okay.. I've searched the mailing list archives for this, but it seems that > I'm the only person trying to do exactly this, and I can't seem to make > mutt do it. Perhaps some of you out there can help. Maybe. :-) > Basically, I want to change my From: header under certain conditions. Ok, there's three ways to change your From header -- setting $realname and $from, $reverse_name, and thirdly to use my_hdr From. In a send-hook, you can only use my_hdr From. > (1) Replying to a message sent to one of my mail aliases. That is, if > someone mails me at [EMAIL PROTECTED] and I hit 'reply', I > want that to be my from address. I can accomplish this with > reverse_name, but keep reading because this all ties together. Right. > (2) I'm _replying_ to mail that was sent to a mailing list. This is the > tough case -- the To: field is some other random address, and the list > isn't mentioned in the headers (note that I'm not list-replying or > group-replying). So far I haven't figured out how to do this. Do you want to set your From header when you're sending *to* a mailing list? That can be done with send-hook and the ~l pattern operator. If not, and you really mean what you say, then this isn't currently do-able in Mutt. > I guess what I'm basically looking for is a reply-hook. Something that I > can use to change things based on the message I'm replying to. Does > anything like that exist? Nope, sorry. There's been talk of ways to solve this, and I think even the best way has been figured out (creating a pseudo-operator which tells that the next pattern operator should match against the headers of the replied-to message, not the current message, which could then be used in send-hooks). It's just that nobody's done it yet. > Would it be possible to get it added as a > feature? Sure, if you write it, or get someone to write it for you. :-) > With that feature, both problems are pretty trivial, and more > flexibility is introduced -- reverse_name forces you to use the To: address > on the message you're replying to (as determined by your alternates > variable), and it would be nice to be able to hook on that and then > determine what address to use (possibly another one). Actually, you can also match against the *From* address in a send-hook as well. I'm not sure if this helps you at all, but you can use that to find out when your from address has changed based on $reverse_name. And I've not tried this, but I think you can also override the From address from $reverse_name with the use of my_hdr From. > Also imagine the situation where you're changing e-mail addresses. I'd > like to have a small blurb attached to the bottom of any reply I send to > a message that was sent to my old address -- the blurb would give my new > one. As far as I can tell, this can't be done right now. Well, if you can figure out the right send-hook for it, it's pretty easy to do -- just change the contents of $signature for that messages. > Tho I'd like to be wrong... anyone have any ideas? I don't think so, but maybe what I wrote helped you. 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 / Don't take life too seriously, it's only temporary.
Re: Two "problems" with mutt-1.2
* Suresh Ramasubramanian ([EMAIL PROTECTED]) [000519 03:03]: > Hall Stevenson proclaimed on mutt-users that: > > >set sendmail_wait=<0 > > Try sendmail_wait=-1 :) Cool, that fixed it !! ;-) Thanks ! Hall
Re: fix for redhat 1.2i mutt char encodings
On 2000-05-18 22:46:15 -0500, Carlos Puchol wrote: > redhat released an update, mutt-1.2i-2, but it needs to > have --enable-locales-fix added to the ./prepare line > for accented chars to print (the --with-charmaps option > does not seem to affect at all). There are two things which affect display and recoding of messages in non us-ascii character sets: - the charset variable - your locale settings Currently, these settings are unrelated; future versions of mutt (not in the 1.2 series) will derive the charset default from the locale if appropriate library functions are present. Now, what happens? The charset variable tells mutt what character set you are using locally. The message parsing code will recode any messages to that character set if possible; so people who have a local character set of koi8-r (sp?) can read and reply to messages in, say, windows-1251. The system's locale settings tell mutt what characters can be displayed, and what characters can't be displayed. So, if you have charset=iso-8859-1, but are using some locale which doesn't know about anything but us-ascii characters, äöüßé and friends will be displayed as question marks - after all, the locale tells mutt that these characters aren't printable on the current terminal. The solution? Either make mutt's checks independent of the locale (--enable-locales-fix), which is generally a bad idea, or make sure your locale settings are appropriate and tell the truth about printable and non-printable characters. LC_CTYPE=de_DE should work for iso-8859-1, BTW. -- http://www.guug.de/~roessler/
Re: Two "problems" with mutt-1.2
I sort of caught this discussion in the middle so this has probably already been asked, but does the xterm you are using support color? I argued with mutt for a day and a half until i realized that my xterm was the problem not mutt. Dave On Fri, 19 May 2000, Hall Stevenson wrote: > > On Fri, May 19, 2000 at 07:44:15AM -0400, Hall Stevenson > <[EMAIL PROTECTED]> wrote: > > > Yes, the first time I configured mutt, I didn't specify slang or > > > ncurses, but according to "./configure --help", it will use slang by > > > default. I'm 99% positive it found it -- would it compile if it > didn't > > > ?? > > > > Really? I have both ncurses and slang installed, and the > > configure script picked up ncurses to use. If you had (n)curses, > > configure could have found and used that. > > Sorry, I'm not positive right now... I'm at work, my linux box is at > home. I guess my main point is, it appears that neither option is > getting me color. I've got a few other things to try though. I'll report > back. > > > Should mutt -v spit out which library what used? > > I think it does. I'll double-check that again. > > Regards, > Hall > David S. Glaser AKA Grizz | M&M Systems Administrator | Forget virus scanning. Its all about "re- U201 M&ME Building | education". Preferably in a parking lot with Houghton, MI 49931 | a tire iron. - BOFH [EMAIL PROTECTED] |
Re: maildirs with both mail and other maildirs in them
David T-G proclaimed on mutt-users that: >% It's not unusual to find a number of files and some loose papers in a >% section in a filing cabinet, this is analogous. > >Oh, gawd -- next you'll want a GUI with little drawer icons ;-) MacMutt? -- Suresh Ramasubramanian | sureshr at staff.juno.com Are you a turtle?
Re: Two "problems" with mutt-1.2
> On Fri, May 19, 2000 at 07:44:15AM -0400, Hall Stevenson <[EMAIL PROTECTED]> wrote: > > Yes, the first time I configured mutt, I didn't specify slang or > > ncurses, but according to "./configure --help", it will use slang by > > default. I'm 99% positive it found it -- would it compile if it didn't > > ?? > > Really? I have both ncurses and slang installed, and the > configure script picked up ncurses to use. If you had (n)curses, > configure could have found and used that. Sorry, I'm not positive right now... I'm at work, my linux box is at home. I guess my main point is, it appears that neither option is getting me color. I've got a few other things to try though. I'll report back. > Should mutt -v spit out which library what used? I think it does. I'll double-check that again. Regards, Hall
Re: maildirs with both mail and other maildirs in them
Chris -- ...and then Chris Green said... % % It's not unusual to find a number of files and some loose papers in a % section in a filing cabinet, this is analogous. Oh, gawd -- next you'll want a GUI with little drawer icons ;-) % % -- % 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: Two "problems" with mutt-1.2
On Fri, May 19, 2000 at 10:39:53AM -0400, Bob Bell wrote: > On Fri, May 19, 2000 at 07:44:15AM -0400, Hall Stevenson <[EMAIL PROTECTED]> wrote: > > Yes, the first time I configured mutt, I didn't specify slang or > > ncurses, but according to "./configure --help", it will use slang by > > default. I'm 99% positive it found it -- would it compile if it didn't > > ?? > > Really? I have both ncurses and slang installed, and the > configure script picked up ncurses to use. If you had (n)curses, > configure could have found and used that. > > Should mutt -v spit out which library what used? > It does:- Mutt 1.1.13i (2000-05-03) Copyright (C) 1996-2000 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: SunOS 5.6 [using slang 10310] ^^^ It's not in the "Compile options:" bit though. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: Two "problems" with mutt-1.2
On Fri, May 19, 2000 at 07:44:15AM -0400, Hall Stevenson <[EMAIL PROTECTED]> wrote: > Yes, the first time I configured mutt, I didn't specify slang or > ncurses, but according to "./configure --help", it will use slang by > default. I'm 99% positive it found it -- would it compile if it didn't > ?? Really? I have both ncurses and slang installed, and the configure script picked up ncurses to use. If you had (n)curses, configure could have found and used that. Should mutt -v spit out which library what used? -- Bob BellCompaq Computer Corporation Software Engineer 110 Spit Brook Rd - ZKO3-3U/14 TruCluster GroupNashua, NH 03062-2698 [EMAIL PROTECTED] 603-884-0595
Re: maildirs with both mail and other maildirs in them
On Fri, May 19, 2000 at 03:54:26PM +0200, Frank Derichsweiler wrote: > On Fri, May 19, 2000 at 10:58:16AM +0100, Chris Green wrote: > > and jim. All the other agents' mail still goes to ~/agents/ but > > fred's and jim's mail goes to ~/agents/fred/ and ~/agents/jim/. From > > the user's point of view this makes a great deal of sense I think. > IMHO agents/fred, agents/jim agents/other make more sense. > Using this style the problem with the dir. name is gone. > Maybe, maybe not, it's surely up to the user and how s/he sees the world. It's not unusual to find a number of files and some loose papers in a section in a filing cabinet, this is analogous. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: maildirs with both mail and other maildirs in them
On Fri, May 19, 2000 at 10:58:16AM +0100, Chris Green wrote: > and jim. All the other agents' mail still goes to ~/agents/ but > fred's and jim's mail goes to ~/agents/fred/ and ~/agents/jim/. From > the user's point of view this makes a great deal of sense I think. IMHO agents/fred, agents/jim agents/other make more sense. Using this style the problem with the dir. name is gone. SCNR Frank
Re: Two "problems" with mutt-1.2
...and then Hall Stevenson said... % % Error in /home/hall/.muttrc, line 18: <0: invalid value % source: errors in /home/hall/.muttrc % Press any key to continue % % This is the "guilty" line: % % set sendmail_wait=<0 % % Perfectly valid, I thought. Worked fine with 1.0.x. And even the sample % Muttrc file shows it as an option. >> Hall, you've already seen the answer to this, but it's "the value must be >> numeric, not descriptive". >> Mutt folks, is this any tougher to fix than the attached patch? We keep >> hearing this question (no, Hall, you're not alone!), so it seems that the >> manual needs a little clarification... Thanks, David. I'm always relieved when I find I'm not the only one with a certain problem !! At least I know it's not something that *I* did wrong. Regards, Hall
Re: Two "problems" with mutt-1.2
> Hall Stevenson proclaimed on mutt-users that: > > >> Try sendmail_wait=-1 :) > > > >Thank you ;-) I'll give it a try this afternoon. Can I assume you use > >this setting and it *does* work ?? > > I don't, but Roessler does. > > $ cat /usr/local/doc/mutt/samples/sample.muttrc-tlr|grep 'sendmail_wait' > > set sendmail_wait=-1 # Put sendmail (i.e., postfix) to the background. > > That do? :) He's one of the developers, right ?? Yeah, I suppose I'll trust that... ;-) Can't hurt regardless. Thanks again! Hall
Re: Two "problems" with mutt-1.2
Hi, folks -- ...and then Hall Stevenson said... % % Error in /home/hall/.muttrc, line 18: <0: invalid value % source: errors in /home/hall/.muttrc % Press any key to continue % % This is the "guilty" line: % % set sendmail_wait=<0 % % Perfectly valid, I thought. Worked fine with 1.0.x. And even the sample % Muttrc file shows it as an option. Hall, you've already seen the answer to this, but it's "the value must be numeric, not descriptive". Mutt folks, is this any tougher to fix than the attached patch? We keep hearing this question (no, Hall, you're not alone!), so it seems that the manual needs a little clarification... Let's see how I did making my first patch :-) :-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* diff -urN mutt-1.2/Muttrc mutt-1.2-patched/Muttrc --- mutt-1.2/Muttrc Tue May 9 11:15:25 2000 +++ mutt-1.2-patched/Muttrc Fri May 19 08:05:48 2000 @@ -2480,11 +2480,11 @@ # to finish before giving up and putting delivery in the background. # # Mutt interprets the value of this variable as follows: -# >0 number of seconds to wait for sendmail to -# finish before continuing -# 0 wait forever for sendmail to finish -# <0 always put sendmail in the background -# without waiting +# greater than 0 number of seconds to wait for sendmail to +# finish before continuing +# 0 wait forever for sendmail to finish +#less than 0 always put sendmail in the background +# without waiting # # # diff -urN mutt-1.2/doc/manual-6.html mutt-1.2-patched/doc/manual-6.html --- mutt-1.2/doc/manual-6.html Tue May 9 11:15:36 2000 +++ mutt-1.2-patched/doc/manual-6.html Fri May 19 08:06:47 2000 @@ -2210,11 +2210,11 @@ ->0 number of seconds to wait for sendmail to -finish before continuing -0 wait forever for sendmail to finish -<0 always put sendmail in the background -without waiting +greater than 0 number of seconds to wait for sendmail to +finish before continuing + 0 wait forever for sendmail to finish + less than 0 always put sendmail in the background +without waiting Note that if you specify a value other than 0, the output of the child diff -urN mutt-1.2/doc/manual.sgml mutt-1.2-patched/doc/manual.sgml --- mutt-1.2/doc/manual.sgmlTue May 9 11:15:26 2000 +++ mutt-1.2-patched/doc/manual.sgmlFri May 19 08:07:26 2000 @@ -4989,11 +4989,11 @@ Mutt interprets the value of this variable as follows: ->0 number of seconds to wait for sendmail to -finish before continuing -0 wait forever for sendmail to finish -<0 always put sendmail in the background -without waiting +greater than 0 number of seconds to wait for sendmail to +finish before continuing + 0 wait forever for sendmail to finish + less than 0 always put sendmail in the background +without waiting Note that if you specify a value other than 0, the output of the child diff -urN mutt-1.2/doc/manual.txt mutt-1.2-patched/doc/manual.txt --- mutt-1.2/doc/manual.txt Tue May 9 11:15:29 2000 +++ mutt-1.2-patched/doc/manual.txt Fri May 19 08:08:54 2000 @@ -4813,11 +4813,11 @@ Mutt interprets the value of this variable as follows: - >0 number of seconds to wait for sendmail to - finish before continuing - 0 wait forever for sendmail to finish - <0 always put sendmail in the background - without waiting + greater than 0 number of seconds to wait for sendmail to + finish before continuing +0 wait forever for sendmail to finish + less than 0 always put sendmail in the background + without waiting Note that if you specify a value other than 0, the output of the child process will be put in a temporary file. If there is some error, you diff -urN mutt-1.2/doc/muttrc.man mutt-1.2-patched/doc/muttrc.man --- mutt-1.2/doc/muttrc.man Tue May 9 11:15:26 2000 +++ mutt-1.2-patched/doc/muttrc.man Fri May 19 08:09:25 2000 @@ -2949,11 +2949,11 @@ .sp .ft CR .nf ->0 number of seconds to wait for sendmail to -finish before continuing -0 wait forever for sendmail to finish -<0 always put sendmail in the background -without waiting +greater than 0 number of seconds to wait for sendmail to +finish before continui
Re: Two "problems" with mutt-1.2
Hall Stevenson proclaimed on mutt-users that: >> Try sendmail_wait=-1 :) > >Thank you ;-) I'll give it a try this afternoon. Can I assume you use >this setting and it *does* work ?? I don't, but Roessler does. $ cat /usr/local/doc/mutt/samples/sample.muttrc-tlr|grep 'sendmail_wait' set sendmail_wait=-1 # Put sendmail (i.e., postfix) to the background. That do? :) -- Suresh Ramasubramanian | sureshr at staff.juno.com Pick another fortune cookie.
Re: Binding bug + minor annoyance.
Chris, et al -- ...and then Chris Green said... % On Thu, May 18, 2000 at 05:13:10PM -0500, Larry P. Schrof wrote: % > % > generic binding seems to be broke. Am I doing something wrong? % > % > bind generic j previous-entry % > bind generic k next-entry % > bind index j noop % > bind index k noop % > ... % If you add 'generic' bindings they very rarely (if ever) seem to work, % it's something that has always been like this. I think maybe there % should be a note in the manual about it to say that 'generic' is really % only used to indicate that some built-in bindings apply everywhere and % is not a binding type to be used in the muttrc file. I don't think it's quite like that, although perhaps the manual could be a bit clearer on the subject (always room for improvement, right?). You can only generically bind a key if it's not otherwise bound; if it is, then those bindings take precedence and must be changed with a mode-specific (pager, index, etcetc) binding. If j/k were not bound anywhere, then the generic binding would work just fine. As we know, though, they are. The trick is to find an unused key (not a small feat!). % % Or maybe it's possible to fix it? One way might be to have mutt ship with no bindings and let you roll all of your own ;-) % % -- % 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: reply macro
David T-G proclaimed on mutt-users that: >Of course, if you already have one, then it probably *is* the easier way >to go ;-) It is, believe me :) And you wouldn't believe the amount of spam it attracts :) >I'd probably be of about the same viewpoint, since I do, too (I counted >them the other day for ssome need and was surprised at how many!). So >I'd write the script to allow a -f parameter and to be smart enough to >look for the To: address ;-) Am a bit lazy, shall we say :) Yep, a _lot_ of thing can be done by piping mail to a script, but still - I have this setup, and it works :) >Hmmm... This is starting to sound like a fun little hack, except I >don't like the idea of DSN in the first place so I'm not likely to bother. DSN _does_ have its uses - like certified mail has in the real world :) -- Suresh Ramasubramanian | sureshr at staff.juno.com Computers are not intelligent. They only think they are.
Re: Two "problems" with mutt-1.2
> On Thu, May 18, 2000 at 09:39:32AM -0400, Hall Stevenson wrote: > > My other problem is *no* colors at all. I'm using the same .muttrc file > > as before and I had colors. Did I miss a configure option ?? Typing > > "mutt -v" shows the "+HAVE_COLOR" flag. FWIW, here's all of what "mutt > > -v" shows: > > > > mutt -v > My 1.2 looks very similar to the above and my colours carried over OK. > The only major difference is that I'm using S-Lang, did you say you > had tried both S-Lang and ncurses? If you can use S-Lang I think > getting colour to work is easier. Yes, the first time I configured mutt, I didn't specify slang or ncurses, but according to "./configure --help", it will use slang by default. I'm 99% positive it found it -- would it compile if it didn't ?? My next step is to not use my "old" .muttrc file and let it use all default settings. Then, in the global Muttrc file, I'll make *one* color change and see what happens. Regards, Hall
Re: Two "problems" with mutt-1.2
> Hall Stevenson proclaimed on mutt-users that: > > >set sendmail_wait=<0 > > Try sendmail_wait=-1 :) Thank you ;-) I'll give it a try this afternoon. Can I assume you use this setting and it *does* work ?? Regards, Hall
Re: reply macro
Suresh -- ...and then Suresh Ramasubramanian said... % David T-G proclaimed on mutt-users that: % % >What, you can make a dummy login that can handle mail addressed to % >anyone, but not a script? Just put the script in /usr/local/bin and % >let the calling user (you know, that guy who pipes it a message) provide % >the From: info without even trying! % % Yep - you _do_ have a point, but I use the dummy login as an autoresponder Of course, if you already have one, then it probably *is* the easier way to go ;-) % anyway ... and this way, my _real_ mail id is not exposed to all and % sundry :) Ahhh... A good point, to be sure. % % I have several accounts aliasing to my real address, which is extensively % filtered, btw ... and I prefer it this way for these reasons. YMMV :) I'd probably be of about the same viewpoint, since I do, too (I counted them the other day for ssome need and was surprised at how many!). So I'd write the script to allow a -f parameter and to be smart enough to look for the To: address ;-) Hmmm... This is starting to sound like a fun little hack, except I don't like the idea of DSN in the first place so I'm not likely to bother. % % -- % Suresh Ramasubramanian | sureshr at staff.juno.com % There are two types of people in this world, good and bad. The good % sleep better, but the bad seem to enjoy the waking hours much more. % -- Woody Allen :-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: reply macro
David T-G proclaimed on mutt-users that: >What, you can make a dummy login that can handle mail addressed to >anyone, but not a script? Just put the script in /usr/local/bin and >let the calling user (you know, that guy who pipes it a message) provide >the From: info without even trying! Yep - you _do_ have a point, but I use the dummy login as an autoresponder anyway ... and this way, my _real_ mail id is not exposed to all and sundry :) I have several accounts aliasing to my real address, which is extensively filtered, btw ... and I prefer it this way for these reasons. YMMV :) -- Suresh Ramasubramanian | sureshr at staff.juno.com There are two types of people in this world, good and bad. The good sleep better, but the bad seem to enjoy the waking hours much more. -- Woody Allen
Re: reply macro
Suresh -- ...and then Suresh Ramasubramanian said... % David T-G proclaimed on mutt-users that: % % >The "script" method, I hope :-) Yeah, once the script exists, it's easy % >enough for anyone to use it. % % Making local copies of the script for every user would be tedious, to say % the least :) So, the dummy login :) What, you can make a dummy login that can handle mail addressed to anyone, but not a script? Just put the script in /usr/local/bin and let the calling user (you know, that guy who pipes it a message) provide the From: info without even trying! % % -- % Suresh Ramasubramanian | sureshr at staff.juno.com % Never commit yourself! Let someone else commit you. :-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
Putting warnings into mutt
Is it possible to put warning messages in the status bar with a macro like "There are no messages." or "You are on the last page." thanks, Antoine
Interesting From: header problem
Okay.. I've searched the mailing list archives for this, but it seems that I'm the only person trying to do exactly this, and I can't seem to make mutt do it. Perhaps some of you out there can help. Basically, I want to change my From: header under certain conditions. These conditions are: (1) Replying to a message sent to one of my mail aliases. That is, if someone mails me at [EMAIL PROTECTED] and I hit 'reply', I want that to be my from address. I can accomplish this with reverse_name, but keep reading because this all ties together. (2) I'm _replying_ to mail that was sent to a mailing list. This is the tough case -- the To: field is some other random address, and the list isn't mentioned in the headers (note that I'm not list-replying or group-replying). So far I haven't figured out how to do this. I guess what I'm basically looking for is a reply-hook. Something that I can use to change things based on the message I'm replying to. Does anything like that exist? Would it be possible to get it added as a feature? With that feature, both problems are pretty trivial, and more flexibility is introduced -- reverse_name forces you to use the To: address on the message you're replying to (as determined by your alternates variable), and it would be nice to be able to hook on that and then determine what address to use (possibly another one). Also imagine the situation where you're changing e-mail addresses. I'd like to have a small blurb attached to the bottom of any reply I send to a message that was sent to my old address -- the blurb would give my new one. As far as I can tell, this can't be done right now. Tho I'd like to be wrong... anyone have any ideas? Matt Dharm -- Matthew Dharm Home: [EMAIL PROTECTED] Senior Engineer, QCP Inc.Work: [EMAIL PROTECTED]
fix for redhat 1.2i mutt char encodings
i asked last week about a more recent rpm that did not have broken SHAREDIR, etc. like the original redhat 6.2 had. redhat released an update, mutt-1.2i-2, but it needs to have --enable-locales-fix added to the ./prepare line for accented chars to print (the --with-charmaps option does not seem to affect at all). so, instead of 3737 X 000518 D?nis Riedijk ( 32) Re: ... i like to see: 3737 X 000518 Dènis Riedijk ( 32) Re: ... as well as inside messages, this: for me it works with german special characters like ? ? ? without any problems. Thinks like ? ? are also possible. vs this: for me it works with german special characters like ö ä ü without any problems. Thinks like á é are also possible. thanks, ++ carlos
Re: maildirs with both mail and other maildirs in them
On Fri, May 19, 2000 at 02:28:17AM -0700, Brian D. Winters wrote: > On Fri, May 19, 2000 at 09:52:19AM +0100, Chris Green wrote: > > I have a maildir which has mail delivered to it directly (i.e. it has > > cur, new and tmp directories in it) but it also has other maildir > > folders in it. Mutt doesn't seem to be able to cope with this at all, > > am I missing something or is it just not possible to handle this with > > mutt? > > AFAIK you are not missing anything, although I'm not sure unable "to > cope with this at all" is totally accurate. I expect that if you give > mutt an explicit path to open it do so just fine. My guess is that > your problem is when trying to browse to the subdirectories? > Yes, that's right of course, I expect you can go directly to a 'folder in a maildir', but then you nee to know its name of course. > Perhaps you (or anyone else reading this) can answer a related > question I have been wondering about for quite a while. Why on earth > would you want to put directories other than cur/new/tmp in a maildir? > This seems really broken to me. My understanding is that maildirs are > directories which contain cur/new/tmp, not directories containing > cur/new/tmp plus N other unrelated directories to confuse things. > Because it can make a lot of sense to organise one's mail like this, for example I get a lot of E-mail from contract agents, so I create a folder called 'agents'. After a while I get so much mail in this folder that I want to split out the mail from one or two of the agents, say fred and jim so I create folders *in* the agents folder for fred and jim. All the other agents' mail still goes to ~/agents/ but fred's and jim's mail goes to ~/agents/fred/ and ~/agents/jim/. From the user's point of view this makes a great deal of sense I think. > My guess from past posts is that you are doing this because Courier > IMAP forces you to do so. Personally I think Courier is defective in > this regard, but the rest of my rant on that subject doesn't belong on > this list. IIRC courier also insists on beginning those directories > with a ".", which probably doesn't hurt mutt, but can't help. > I'd really like Courier to not use that preceding '.' too. However it doesn't *actually* create folders in the same directory as a maildir except in the top level inbox. The 'hierarchy' of folders is created by its naming convention, the above example would create the following maildirs in the inbox:- .agents .agents.fred .agents.jim > Back to trying to provide constructive suggestions, how well does > Courier handle symlinks? I've never tried this, but could you move > your subfolders elsewhere and symlink to them? Or could you symlink > to those folders from elsewhere for mutt's benefit? IMAP servers may > chose not to follow symlinks for security reasons, but mutt shouldn't > have any trouble following symlinks. This isn't the most elegant > solution, but I don't have any better suggestions. > Yes, this is the way I first looked into and it can be made to work, I started on a script to automatically create the symlinks. However I decided it's probably easier just to access the mail using the IMAP server 'locally', especially since I've gone through all the recent process of working out how to switch easily from browsing IMAP folders to browsing local folders. The other thing that I've done to simplify my life is to separate my Courier inbox (which I've renamed to imap) from the default inbox which procmail uses for delivering mail other then mail which it has filtered. In fact I may well switch procmail back to delivering in mbox format because (as another thread here has noted) mbox format folders show more useful information in the browser. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: maildirs with both mail and other maildirs in them
On Fri, May 19, 2000 at 09:52:19AM +0100, Chris Green wrote: > I have a maildir which has mail delivered to it directly (i.e. it has > cur, new and tmp directories in it) but it also has other maildir > folders in it. Mutt doesn't seem to be able to cope with this at all, > am I missing something or is it just not possible to handle this with > mutt? AFAIK you are not missing anything, although I'm not sure unable "to cope with this at all" is totally accurate. I expect that if you give mutt an explicit path to open it do so just fine. My guess is that your problem is when trying to browse to the subdirectories? Perhaps you (or anyone else reading this) can answer a related question I have been wondering about for quite a while. Why on earth would you want to put directories other than cur/new/tmp in a maildir? This seems really broken to me. My understanding is that maildirs are directories which contain cur/new/tmp, not directories containing cur/new/tmp plus N other unrelated directories to confuse things. My guess from past posts is that you are doing this because Courier IMAP forces you to do so. Personally I think Courier is defective in this regard, but the rest of my rant on that subject doesn't belong on this list. IIRC courier also insists on beginning those directories with a ".", which probably doesn't hurt mutt, but can't help. Back to trying to provide constructive suggestions, how well does Courier handle symlinks? I've never tried this, but could you move your subfolders elsewhere and symlink to them? Or could you symlink to those folders from elsewhere for mutt's benefit? IMAP servers may chose not to follow symlinks for security reasons, but mutt shouldn't have any trouble following symlinks. This isn't the most elegant solution, but I don't have any better suggestions. Brian
Re: Can't read cyrillic messages
Hello Sergei! On Wed, 17 May 2000, Sergei Gerasenko wrote: > I can't seem to be able to read messages in cyrillic with mutt. > Setting charset to ISO-8859-5 or KOI8-r does not help at all. This is > the compile options: ...they are looking OK. It sounds that it wont be a problem with mutt but a problem with your locale. Maybe you will change the locale settings on you box. Whats 'locale' shown on your machine? bye - Wilhelm -- > Wilhelm Wienemann, Amselweg 10, D-47546 Kalkar/Germany < ==> E-Mail: [EMAIL PROTECTED] <=== "And since you are the future keepers of everything, including music, we hope you will keep it well, with love, and in joy." (Frederick Fennell)
maildirs with both mail and other maildirs in them
I have a maildir which has mail delivered to it directly (i.e. it has cur, new and tmp directories in it) but it also has other maildir folders in it. Mutt doesn't seem to be able to cope with this at all, am I missing something or is it just not possible to handle this with mutt? -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: Binding bug + minor annoyance.
On Thu, May 18, 2000 at 05:13:10PM -0500, Larry P. Schrof wrote: > Mutt version: > > Mutt 1.0.1i (2000-01-18) > > Is this a bug? > == > > generic binding seems to be broke. Am I doing something wrong? > > bind generic j previous-entry > bind generic k next-entry > bind index j noop > bind index k noop > > When I hit 'k' or 'j' in the index, it gives me a "Key is not bound." > error. Yet, when I go to the binding listing screen (by hitting '?'), > 'j' and 'k' show up in the generic bindings section as bound to the > functions I assigned. > If you add 'generic' bindings they very rarely (if ever) seem to work, it's something that has always been like this. I think maybe there should be a note in the manual about it to say that 'generic' is really only used to indicate that some built-in bindings apply everywhere and is not a binding type to be used in the muttrc file. Or maybe it's possible to fix it? -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: Two "problems" with mutt-1.2
On Thu, May 18, 2000 at 09:39:32AM -0400, Hall Stevenson wrote: > My other problem is *no* colors at all. I'm using the same .muttrc file > as before and I had colors. Did I miss a configure option ?? Typing > "mutt -v" shows the "+HAVE_COLOR" flag. FWIW, here's all of what "mutt > -v" shows: > > mutt -v > Mutt 1.2i (2000-05-09) > Copyright (C) 1996-2000 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.2.15 [using ncurses 5.0] > Compile options: > -DOMAIN > +DEBUG > -HOMESPOOL +USE_SETGID +USE_DOTLOCK -USE_FCNTL +USE_FLOCK > -USE_IMAP -USE_GSS -USE_SSL +USE_POP +HAVE_REGCOMP -USE_GNU_REGEX > +HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS > SENDMAIL="/usr/sbin/sendmail" > MAILPATH="/var/spool/mail" > SHAREDIR="/usr/local/share/mutt" > SYSCONFDIR="/etc" > ISPELL="/usr/bin/ispell" > To contact the developers, please mail to <[EMAIL PROTECTED]>. > To report a bug, please use the muttbug utility. > My 1.2 looks very similar to the above and my colours carried over OK. The only major difference is that I'm using S-Lang, did you say you had tried both S-Lang and ncurses? If you can use S-Lang I think getting colour to work is easier. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: reply macro
On Fri, May 19, 2000 at 11:32:35AM +0530, Suresh Ramasubramanian wrote: > David T-G proclaimed on mutt-users that: > > >The "script" method, I hope :-) Yeah, once the script exists, it's easy > >enough for anyone to use it. > > Making local copies of the script for every user would be tedious, to say > the least :) So, the dummy login :) Where I'm, I can't create a dummy login, but we have a commun directory. I just have to put the script in, and everyone could use it... there is the script : TO=`tee /tmp/mutt_notify.$USER | formail -R Return-Receipt-To: Disposition-Notification-To: | formail -R X-Confirm-Reading-To: Disposition-Notification-To: | formail -x Disposition-Notification-To:` SUBJECT=`formail -x Subject: < /tmp/mutt_notify.$USER` FROM=`formail -x To: < /tmp/mutt_notify.$USER` DATE=`date` if [ -n "$TO" ] ; then echo "Sending notification to$TO" echo "Your message has been displayed on the screen of$FROM on $DATE" | mutt -s "NOTIFICATION OF:$SUBJECT" "$TO" else echo "No notification needed fi sleep 1 rm -f /tmp/mutt_notify.$USER and there the macro for this script : macro pager \cv "|mail_notify.sh\n" "Notification de lecture" macro index \cv "|mail_notify.sh\n" "Notification de lecture" If you have any idea to make this script better, tell it to me Thanks Antoine
