Re: attachments appear as NoName
Hi there, On Wed, Mar 08 2000 09:07:22 +0100 wrote Martin Keseg - Sun Slovakia - SE with subject "Re: attachments appear as NoName": > > If these attachments do not have a Content-Disposition filename= > > field, this would appear correct. [...] > > For instance, a recent message sent to mutt-dev with the structure > > > > I 1 [multipa/mixed, 7bit, 1.6K] > > I 2 |-> [text/plain, quoted, us-ascii, 0.6K] > > A 3 `->TODO.diff [text/plain, quoted, us-ascii, 0.7K] > > I 4 [applica/pgp-signat, 7bit, 0.2K] > > > > appears in dtmail with an empty message field and three NoName > > attachments. So, I'd say that dtmail has certain problems with > > multipart/mixed. Attachment 3 _is_ named > > > > Content-Disposition: attachment; filename="TODO.diff" > > > > and dtmail doesn't recognise this. > > This q. was discused here few month ago and ppl from mutt-dev say thats problem > of dtmail. I was looking at the difference between mutt's attachments and some from other mail clients and there was one I got sometime and looking at the header of the attachment says: [-- Type: application/msword, Encoding: base64, Size: 16K --] Content-Type: application/msword; name="Schedule.doc" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="Schedule.doc" and one of my recently mailed mutt mails shows this: [-- Type: text/plain, Encoding: 7bit, Size: 3.2K --] Content-Type: text/plain; charset=us-ascii Content-Description: send.c.diff Content-Disposition: attachment; filename="send.c.diff" As you can see there is no `name' field in mutt's attachment and the other one has it and it's content is the same as in the `filename' field. Maybe dtmail looks for a `name' field to find the attachment's name (maybe some other clients too) and does simply ignore the `filename' field. Is the `name' field necessary for attachments and it is a "bug" in mutt not to add it or should the `filename' field be enough and it is a "bug" in dtmail not to recognize it? (That seems to be the question here.) Regards, Stefan. -- Parkinson's Fourth Law: The number of people in any working group tends to increase regardless of the amount of work to be done.
Re: mutt-1.1.8 is out
Eugene Lee <[EMAIL PROTECTED]> wrote on Thu, 09 Mar 2000: > Besides, when releasing software that is still in beta testing, how do > you count versions according to the Linux kernel way? For example, the > previous Mutt beta was 1.1.7. Since the current release is still beta, > shouldn't it be numbered as 1.1.9 ? No, the *second* digit being even/odd indicates stable/beta releases. (Or "developement" releases instead of "beta", but it's the same thing.) So 1.1.x are all betas, with the last digit (x) indicating beta count. 1.0.x (and 1.2.x) will all be stable releases. This is how both the Linux kernel and Mutt do it. It's a bit weird at first but you get used to it, and it does avoid problems when you get things like 1.2beta124 when you have the 124th beta release of 1.2... Also, this way, the stable release will have a numerically higher number than the developement branch that led to it. 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 it weren't for the last minute, nothing would get done.
Re: [Announce] mutt-1.1.8 is out
On Mon, Mar 06, 2000 at 11:13:14AM +0100, Thomas Mueller wrote: : :> :Mutt-1.1.8 is out. This is another BETA version. Changes :> :against 1.1.7 include fixes for one recent and one :> :long-standing, but mostly unnoticed bug. :> :> Just a quick observation. Mutt is one of the few pieces of software :> that gets full version numbers for betas, versus most conventions that :> use a next-version-number + "b" + beta-version-number. I just found :> this practice to be a bit unusual. :) : :?? Linux Kernel, Gimp, ... they all use even numbers for stable releases :and odd numbers for development version. My history is based from BSD, Apache, BIND, Sendmail, etc. and never held any numerical favoritism. :-) I actually prefer a major.minor.fix versioning format. Besides, when releasing software that is still in beta testing, how do you count versions according to the Linux kernel way? For example, the previous Mutt beta was 1.1.7. Since the current release is still beta, shouldn't it be numbered as 1.1.9 ? Just curious, this is really new information to me. I feel so clueless... -- Eugene Lee [EMAIL PROTECTED]
Re: attachments appear as NoName
Stefan Bender <[EMAIL PROTECTED]>: > [-- Type: application/msword, Encoding: base64, Size: 16K --] > Content-Type: application/msword; name="Schedule.doc" > Content-Transfer-Encoding: base64 > Content-Disposition: attachment; filename="Schedule.doc" > > and one of my recently mailed mutt mails shows this: > > [-- Type: text/plain, Encoding: 7bit, Size: 3.2K --] > Content-Type: text/plain; charset=us-ascii > Content-Description: send.c.diff > Content-Disposition: attachment; filename="send.c.diff" Here you're comparing a text/plain attachment produced by mutt with an application/msword attachment produced by some by some other MUA. Could you show us the headers of a text/plain attachment produced by the other MUA? I've never seen a "name" parameter with Content-Type text/plain; the RFCs don't seem to mention such a thing. I assume MicroSoft are entitled to invent any parameters they want for Content-Type application/msword. "The set of meaningful parameters depends on the media type and subtype", says RFC 2045. Edmund
Re: [Announce] mutt-1.1.8 is out
On 2000-03-09 01:56:21 -0800, Eugene Lee wrote: > Besides, when releasing software that is still in beta > testing, how do you count versions according to the > Linux kernel way? For example, the previous Mutt beta > was 1.1.7. Since the current release is still beta, > shouldn't it be numbered as 1.1.9 ? The first digit of the version number is the major release. 0.* was not-yet-released (oh well ;-), 1.0 was the first stable release. 1.0.1 is a fix-up version of that. 1.1.* was an unstable branch (actually, it's the same branch which used to be known as 0.96 earlier). When 1.1.* is mature, it'll be called 1.2, and we'll start a new unstable branch which will be named 1.3. The next release will be 1.4, or 2.0, or whatever. -- http://www.guug.de/~roessler/
Re: [Announce] mutt-1.1.8 is out
On Thu, Mar 09, 2000 at 04:18:20PM +0530, Mrinal Kalakrishnan wrote: > No, the minor version is what shows whether it's beta or not. So in > 1.1.8, second `1' shows that it's a beta version. The stable release > will be 1.2.x. Not exactly. There are development-only (non-BETA) versions, as 1.1 through 1.1.5 are. As a general rule: Use x.y[.z] versions with odd y ONLY when announced on [EMAIL PROTECTED] or [EMAIL PROTECTED], and ONLY under conditions as announced. In the opposite, versions with even y always are considered stable. It may happen that there will be 1.2pre versions, so continue to read this list :-))) Gero
Re: [Announce] mutt-1.1.8 is out
Hi, Eugene Lee typed: > Besides, when releasing software that is still in beta testing, how do > you count versions according to the Linux kernel way? For example, the > previous Mutt beta was 1.1.7. Since the current release is still beta, > shouldn't it be numbered as 1.1.9 ? No, the minor version is what shows whether it's beta or not. So in 1.1.8, second `1' shows that it's a beta version. The stable release will be 1.2.x. Same with the linux kernel - current stable kernel is 2.2.x, and development is 2.3.x, which will become the stable 2.4.x. -- Mrinal Kalakrishnan <[EMAIL PROTECTED]> (PGP:B1E86F5B) http://listen.to/mrinal - - - - = ( Redhat Linux 6.1 ) = - - - - = ( Kernel 2.2.12-20 ) = - - - - BETA TESTERS do it looking for mistakes
Re: viewing URL's and changing reply-to
> When i used pine,i could jump to a URL int he message with down-arrow, > and view it with a return key and lynx. Is there something similar > for mutt? Is it just a simple mailcap entry? If so, how do i select > the URL to be viewed? See http://www.mutt.org/doc/manual/manual-4.html#ss4.12 > Also, in pine i could change the reply-to address, so i could route > all reply mail through fowarding. Is there a similar option in mutt? Use (send-)hooks to alter the Reply-To: Header -- Ralf Hildebrandt <[EMAIL PROTECTED]> www.stahl.bau.tu-bs.de/~hildeb Freedom to be an idiot is part of freedom in general. PGP signature
viewing URL's and changing reply-to
Hi all, i have 2 questions. When i used pine,i could jump to a URL int he message with down-arrow, and view it with a return key and lynx. Is there something similar for mutt? Is it just a simple mailcap entry? If so, how do i select the URL to be viewed? Also, in pine i could change the reply-to address, so i could route all reply mail through fowarding. Is there a similar option in mutt? I read the config files, and couldn't tell. Nothing jumped out at me. -- -=> jm <=- --- Student Loan Officer: "Mr. Wright? We'd like to know what you did with the $30,000 dollars we gave you for college." Steven Wright: "I gave it to my friend Bob, and he built a nuclear weapon with it. And i'd really appreciate it if you didn't call me anymore."
Re: [Announce] mutt-1.1.8 is out
Hi, Gero Treuner typed: > > No, the minor version is what shows whether it's beta or not. So in > > 1.1.8, second `1' shows that it's a beta version. The stable release > > will be 1.2.x. > Not exactly. There are development-only (non-BETA) versions, as > 1.1 through 1.1.5 are. OK, I didn't know that. I just labelled all versions that are not the stable release as `beta'. But what is the essential difference between the non-beta and the beta versions? I mean, both categories are available for people to try out aren't they? -- Mrinal Kalakrishnan <[EMAIL PROTECTED]> (PGP:B1E86F5B) http://listen.to/mrinal - - - - = ( Redhat Linux 6.1 ) = - - - - = ( Kernel 2.2.12-20 ) = - - - - Hackers discover the powers of two.
Re: attachments appear as NoName
Hi, On Thu, Mar 09 2000 10:10:13 + wrote Edmund GRIMLEY EVANS with subject "Re: attachments appear as NoName": > Here you're comparing a text/plain attachment produced by mutt with an > application/msword attachment produced by some by some other MUA. I didn't pay attention to the different content types and took the first attachment I found where I recognized the difference. But to be sure I tested it sending some mails to myself, e.g. with jpeg attachments: with mutt: [-- Type: image/jpeg, Encoding: base64, Size: 231K --] Content-Type: image/jpeg Content-Disposition: attachment; filename="ctrl-alt-del.jpeg" Content-Transfer-Encoding: base64 and with kmail: [-- Type: image/jpeg, Encoding: base64, Size: 230K --] Content-Type: image/jpeg; name="ctrl-alt-del.jpeg" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="ctrl-alt-del.jpeg" I got jpeg attachments from a MS Outlook client which also have the `name' parameter. > Could you show us the headers of a text/plain attachment produced by > the other MUA? Unfortunately not but I sent a message to me with same attachment I showed in my last messages using kmail and here it is with a `name' parameter for a text/plain attachment: [-- Type: text/plain, Encoding: 8bit, Size: 3.2K --] Content-Type: text/plain; name="send.c.diff" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="send.c.diff" Anyway it was more a guess than something... Kmail does not seem to have that problem with mutt's attachments anyway, so I start to believe that this is only a dtmail problem. > I've never seen a "name" parameter with Content-Type text/plain; the > RFCs don't seem to mention such a thing. I assume MicroSoft are > entitled to invent any parameters they want for Content-Type > application/msword. "The set of meaningful parameters depends on the > media type and subtype", says RFC 2045. I was trying to find something useful about these parameters but the rfc's don't mention a `name' parameter explicitely. Instead they say "MIME implementations must ignore any parameters whose names they do not recognize." I think this is the case when mutt sees these unrecognized(?) `name' parameters. And in rfc 2183 (about the content-disposition header) I found: "The `filename' parameter can be used to suggest a filename for storing the bodypart, if the user wishes to store it in an external file." I don't know how dtmail behaves but maybe you can check if it creates a `name' parameter or not on it's attachments and if it has a `content-disposition' header field with `filename' parameter or not. I think if it does not create these fields by itself, it is likely that it ignores them too. Regards, Stefan. -- Every solution breeds new problems.
question on saving of sent messages
A few more tweaks, and i'll be almost there. I've noticed that sometimes when i reply to a message in a saved folder,or sometimes even the inbox, mutt complains that it cannot write the sent message because /foldername/sent does not exist. I assume this means i need to set the saved messages folder to one that refers to the mail directory or home directory rather than the directory i am in when i send, correct? Also, is there a problem with folder name TAB completion? When i save, it asks for a folder name. I try 'f TAB' to select 'foldername' but it complains it doesn't exist. Yet the '?' brings up the list just fine. Is this because it is expecting the entire pathname? Is there a shortcut? Does mutt only display new mail messages when the keyboard is used? I find that new mail only appears after i hit a key, if it has been dormant for a while and new mail has been received. -- -=> jm <=- --- Student Loan Officer: "Mr. Wright? We'd like to know what you did with the $30,000 dollars we gave you for college." Steven Wright: "I gave it to my friend Bob, and he built a nuclear weapon with it. And i'd really appreciate it if you didn't call me anymore."
Re: question on saving of sent messages
J McKitrick <[EMAIL PROTECTED]> wrote: > > I've noticed that sometimes when i reply to a message in a saved > folder,or sometimes even the inbox, mutt complains that it cannot > write the sent message because /foldername/sent does not exist. I > assume this means i need to set the saved messages folder to one that > refers to the mail directory or home directory rather than the > directory i am in when i send, correct? You normally will want to refer to folders by putting the "=" or "+" prefix in front of the name. The "=" or "+" expands to the value of the variable $folder, which is an absolute path to the directory where you keep your folders. Then it doesn't matter what directory you're in. > Also, is there a problem with folder name TAB completion? When i > save, it asks for a folder name. I try 'f TAB' to select 'foldername' > but it complains it doesn't exist. Try "=f " > Yet the '?' brings up the list just fine. The default directory that "?" brings up is the $folder directory. There are times when I've found this annoying, but it seems to be traditional at this point. > Does mutt only display new mail messages when the keyboard is used? I > find that new mail only appears after i hit a key, if it has been > dormant for a while and new mail has been received. Yes, Mutt is not multi-threaded, so it does not poll for mail in the background while waiting for a keypress from you. However, there is a variable called $timeout which tells Mutt how long to wait for you to press a key. If you haven't pressed a key by then, it will stop waiting for the keypress, go and poll for mail, then come back and wait some more. So by setting this to a small value (30 seconds?) you can get near-instant notification of new mail. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: question on saving of sent messages
Thanks for the help! -- -=> jm <=- --- Student Loan Officer: "Mr. Wright? We'd like to know what you did with the $30,000 dollars we gave you for college." Steven Wright: "I gave it to my friend Bob, and he built a nuclear weapon with it. And i'd really appreciate it if you didn't call me anymore."
why is mutt better?
I just got in a debate over email clients, and my windows friend argues anything i can do in mutt, he can do in TheBat! just as easily. I checked the feature list, and it is extensive. Most of what mutt offers, thebat offers. Why is the advantage of mutt, or any text-based email client? -- -=> jm <=- --- Student Loan Officer: "Mr. Wright? We'd like to know what you did with the $30,000 dollars we gave you for college." Steven Wright: "I gave it to my friend Bob, and he built a nuclear weapon with it. And i'd really appreciate it if you didn't call me anymore."
Re: [Announce] mutt-1.1.8 is out
Mrinal -- ...and then Mrinal Kalakrishnan said... % Hi, Hi! % % Gero Treuner typed: % > Not exactly. There are development-only (non-BETA) versions, as % > 1.1 through 1.1.5 are. % % OK, I didn't know that. I just labelled all versions that are not the % stable release as `beta'. Not a bad assumption, except with such amazingly functional and stable "beta" code as mutt. It's been beta, as I recall, since the 0.9 days, and was very usable as alpha in the 0.8 days (when I joined up). % % But what is the essential difference between the non-beta and the beta % versions? I mean, both categories are available for people to try out % aren't they? They are, and that's been the philosophy of mutt (as I understand it, anyway) all along. Since "[a]ll mail clients suck", it's important to get The Right Tool out to folks as much and as quickly as possible -- so the code was available early on. Since things which outright break the program rarely (again, as I understand) make it into the CVS tree, you can check out a pretty working version even if part of it is someone's work in progress. Only when such tinkering is "finished" (a very qualified term!) might that release go on to be considered beta. I suppose the biggest difference would be that the developer would respond to trouble reports on non-beta versions as "Yeah, I know; I haven't finished that piece of code and it's supposed to break" instead of in the usual great and supportive manner. There; I guess I just said thanks to all of the developers for helping me with my little questions, anyway :-) % % -- % Mrinal Kalakrishnan <[EMAIL PROTECTED]> (PGP:B1E86F5B) http://listen.to/mrinal % - - - - = ( Redhat Linux 6.1 ) = - - - - = ( Kernel 2.2.12-20 ) = - - - - % Hackers discover the powers of two. :-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: why is mutt better?
Hi! ...and then J McKitrick said... % I just got in a debate over email clients, and my windows friend % argues anything i can do in mutt, he can do in TheBat! just as easily. % I checked the feature list, and it is extensive. Most of what mutt Any pointers to such a thing so that we can compare? % offers, thebat offers. Why is the advantage of mutt, or any % text-based email client? Well, you mentioned your "windows" friend, so that's one reason right there: mutt runs under unix-like variants. I like text-based email clients because I like text-based email. No GUIs for this guy. I also like all of the hook functionality and the ability to do various things based on various conditions. I haven't seen anything else that comes close. I'll leave it to someone who really takes advantage of mutt's featureset to plug it -- once we have any idea what we're up against, so to speak. Without a comparative list of features, just throw the mutt manual at any challengers (and hope to hit 'em square on ;-) % -- % -=> jm <=- :-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: attachments appear as NoName
Stefan -- I've lost track of whether [the argument is that] mutt should put a 'name="*"' parameter on the Content-Type: header or [the complaint is that] mutt expects such a parameter. It seems to me that either can be fixed with scripts. 1) If we want mutt to provide the parameter, change $sendmail to a script that automatically adds the name= data to the Content-Type: line and then feeds everything on to sendmail. 2) If mutt wants to see the parameter, make a procmail rule that checks for Content-Type: without a following name= and use formail to change it and add the data from the Content-Disposition: header (may require a separate script called by procmail to get the filename data and then feed everything to formail). In fact, it seems to me that a fairly generic perl filter could be written which checks for a Content-Type: header, checks to see if it needs a name= parameter, goes farther thru the message to get the info, changes the Content-Type: header appropriately, and then spits the modified message back out on stdout. You could then feed every outgoing message thru that script and then sendmail via $sendmail on the way out, and then feed every incoming message thru it with procmail on the way in. This doesn't mean, of course, that I know anything about MIME or even general email RFCs :-) If "everyone" out there expects a name= parameter, maybe we could just hack mutt to spit out Content-Type: headers that way with a leading X-Content-Type-Explanation: "for stupid mail clients like dtmail" so that everyone knows we know why we're doing it ;-) :-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: why is mutt better?
Well, here's a couple of links official site www.ritlabs.com/the_bat/index.html review www.zdnet.com/pcmag/features/e-mail/mail13.html If either of these don't work, i searched yahoo for 'the bat! email' and both were at the top of the list. One nice feature i saw was a separate scrolling windows allowing you to refer to a message while replying, but without quoting it. That could be handy. Of course, the bat doesn't support IMAP, while mutt does. Other than that, it looks like it's just a matter of GUI vs text. -- -=> jm <=- --- Student Loan Officer: "Mr. Wright? We'd like to know what you did with the $30,000 dollars we gave you for college." Steven Wright: "I gave it to my friend Bob, and he built a nuclear weapon with it. And i'd really appreciate it if you didn't call me anymore."
Re: why is mutt better?
J McKitrick writes: > I just got in a debate over email clients, and my windows friend > argues anything i can do in mutt, he can do in TheBat! just as easily. > I checked the feature list, and it is extensive. Most of what mutt > offers, thebat offers. Why is the advantage of mutt, or any > text-based email client? - mutt is a text-based client; this is a huge advantage for me, as I tend to type emails, not click them - does thebat support gpg (it seems, not) - mutt is Free Software
%N in $folder_format
In my .muttrc I have: set folder_format="%3C %N %-32.32f %-16.16d %s" However, the space with the %N is always blank when I do 'c' and '?' to browse mailboxes. Is there something special I have to do to get this to work? FWIW I'm delivering mail into these folders with procmail. -- Drew Bloechl [EMAIL PROTECTED]
Re: why is mutt better?
J McKitrick <[EMAIL PROTECTED]> wrote: > > I just got in a debate over email clients, and my windows friend > argues anything i can do in mutt, he can do in TheBat! just as > easily. Such arguments rarely lead to a useful exchange of information. They more usually end up as "My computer can beat up your computer" type of "discussion." Is your friend actually interested in learning from this exchange, or does he just want to tell you how great his program is? > I checked the feature list, and it is extensive. Most of what mutt > offers, thebat offers. Why is the advantage of mutt, or any > text-based email client? If TheBat! does everything that he wants it to, then he should use it. Mutt isn't trying to take over the world. :) -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Reply to full name from alias list
Hi, On Wed, Mar 08, 2000 at 02:02:23PM +0530, Mrinal Kalakrishnan wrote: > I was wondering if there is a feature by which, when I reply to, say > this mailing list ([EMAIL PROTECTED]), the `To:' line should become > the whole name and address from my alias file - i.e. `The Mutt Users > List <[EMAIL PROTECTED]>', instead of what the original sender put > in his `To:' line. > > Hope this was clear enough. I didn't find any option for this in the > docs (1.1.8i). Does this patch: http://sec.42.org/mutt/patch-0.95.4.sec.reverse_reply.1 | patch-0.95.4.sec.reverse_reply.1: | extends reverse_alias to also fix the Realnames in outgoing Mail. Do what you want? (It applies cleanly to 1.0, i didn't test the development-versions) CU, Sec -- One of the main causes of the fall of the Roman Empire was that, lacking zero, they had now way to indicate successful termination of their C Programs.
Re: why is mutt better?
On Thu, Mar 09, 2000 at 07:22:05PM +, J McKitrick wrote: [snip] > Of course, the bat doesn't support IMAP, while mutt does. > Other than that, it looks like it's just a matter of GUI vs text. Hmmm... not according to it's feature list. "support for imap4, pop, apop, smtp protocols" regards, alan -- Arcterex -=|=- [EMAIL PROTECTED] -=|=- http://arcterex.ufies.org '... I was worried they were going to say "you don't have enough LSD in your system to do UNIX programming."' -- Paul Tomblin in a.s.r
signature send-hook problem
I have a bunch of signature files I use with friends, which I wan't to be used only for messages to those friends. If I exit out and then start mutt again everything works as I expect. . And that part works fine. But I can't figure out how to get it to reset to my default .signature file for the next message. I copied (slightly modified) my .muttrc. The commented out line always gets matched and will force the default signature. Is is simply changing the order? Or is there some "send-hook this message only" or "reset for each new message" command that I missed. send-hook fred "set signature=~/.signature-fred" send-hook ethel "set signature=~/.signature-ethel" send-hook lucy "set signature=~/.signature-lucy" send-hook ricky "set signature=~/.signature-ricardo" #send-hook * "set signature=~/.signature" -- Josh Kuperman [EMAIL PROTECTED]
Re: why is mutt better?
I already deleted the original email with the feature list (now I wish I hadn't so I could look it up), but does it have similar list functionality? I've never heard of any other mailer that has "list reply" and the ability to intelligently reply to list emails. It would actually be good if these features were more common. 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 / Cheap, Fast, Good -- pick any two. You can't have all three.
Re: signature send-hook problem
Josh Kuperman <[EMAIL PROTECTED]> wrote on Thu, 09 Mar 2000: > The commented out line always gets matched and will force the > default signature. Is is simply changing the order? Yes, the order is significant. Put the default send-hook first. And, incidentally, the best (or recommended) way of writing a pattern that matches everything is with a single dot, "." send-hook . "set signature=~/.signature" 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 / "Time's fun when you're having flies." -- Kermit the Frog
Re: why is mutt better?
On Thu, Mar 09, 2000 at 01:57:08PM -0600, David DeSimone wrote: > > Such arguments rarely lead to a useful exchange of information. They > more usually end up as "My computer can beat up your computer" type of > "discussion." Is your friend actually interested in learning from this > exchange, or does he just want to tell you how great his program is? Actually, maybe it's my fault here. I always tell him my unix box can beat up his windows box with one hard drive tied behind its back. He just argues that windows is simpler, and that power tools should be made easier to use. Oh, well. Different strokes. -- -=> jm <=- --- Student Loan Officer: "Mr. Wright? We'd like to know what you did with the $30,000 dollars we gave you for college." Steven Wright: "I gave it to my friend Bob, and he built a nuclear weapon with it. And i'd really appreciate it if you didn't call me anymore."
Re: %N in $folder_format
Drew Bloechl wrote: : In my .muttrc I have: : : set folder_format="%3C %N %-32.32f %-16.16d %s" : : However, the space with the %N is always blank when I do 'c' and '?' : to browse mailboxes. Is there something special I have to do to get : this to work? FWIW I'm delivering mail into these folders with : procmail. Your incomming mailbox (mailboxes) is placed on NFS-mounted file system? Try --enable-buffy-size in configure-time. -- Andrew W. Nosenko([EMAIL PROTECTED])
Re: signature send-hook problem
On Thu, Mar 09, 2000 at 03:34:08PM -0500, Josh Kuperman wrote: > I have a bunch of signature files I use with friends, which I wan't to > be used only for messages to those friends. If I exit out and then > start mutt again everything works as I expect. . And that part works > fine. But I can't figure out how to get it to reset to my default > .signature file for the next message. > > send-hook fred "set signature=~/.signature-fred" > send-hook ethel "set signature=~/.signature-ethel" > send-hook lucy "set signature=~/.signature-lucy" > send-hook ricky "set signature=~/.signature-ricardo" > #send-hook * "set signature=~/.signature" Change `*' to `.': this means default hook (RTFM for details). As you said, the '*' will match anything: from what I can gather, `.' will be used if no other hook matches. So, in effect, it's the default action. This from my .muttrc: send-hook . set signature=~/.sig/normal send-hook (debian-.*@.*debian.org|[EMAIL PROTECTED])$ \ 'set signature=~/.sig/public' send-hook ^majordomo|request@ \ 'set signature=""' This works fine for me. HTH, HAND, -- Alisdair McDiarmid[EMAIL PROTECTED]
Re: signature send-hook problem
Josh Kuperman writes: > I have a bunch of signature files I use with friends, which I wan't to > be used only for messages to those friends. If I exit out and then > start mutt again everything works as I expect. . And that part works > fine. But I can't figure out how to get it to reset to my default > .signature file for the next message. I copied (slightly modified) my > .muttrc. The commented out line always gets matched and will force the > default signature. Is is simply changing the order? Or is there some > "send-hook this message only" or "reset for each new message" command > that I missed. Prepend these entries with send-hook . set signature=~/.signature > send-hook fred "set signature=~/.signature-fred" > send-hook ethel "set signature=~/.signature-ethel" > send-hook lucy "set signature=~/.signature-lucy" > send-hook ricky "set signature=~/.signature-ricardo" > #send-hook * "set signature=~/.signature"
Re: signature send-hook problem
On Thu, Mar 09, 2000 at 03:34:08PM -0500, Josh Kuperman ([EMAIL PROTECTED]) said: > I have a bunch of signature files I use with friends, which I wan't to > be used only for messages to those friends. If I exit out and then > start mutt again everything works as I expect. . And that part works > fine. But I can't figure out how to get it to reset to my default > .signature file for the next message. I copied (slightly modified) my > .muttrc. The commented out line always gets matched and will force the > default signature. Is is simply changing the order? Yep, that's it. From the manual (section 3, Configuration): When multiple matches occur, commands are executed in the order they are specified in the muttrc. > Or is there some "send-hook this message only" or "reset for each > new message" command that I missed. > > send-hook fred "set signature=~/.signature-fred" > send-hook ethel "set signature=~/.signature-ethel" > send-hook lucy "set signature=~/.signature-lucy" > send-hook ricky "set signature=~/.signature-ricardo" > #send-hook * "set signature=~/.signature" So put this last one first. -- Jim Toth [EMAIL PROTECTED]
Re: Reply to full name from alias list
Hi, On Thu, Mar 09 2000 21:16:32 +0100 wrote Stefan `Sec` Zehl with subject "Re: Reply to full name from alias list": > Does this patch: > http://sec.42.org/mutt/patch-0.95.4.sec.reverse_reply.1 > > | patch-0.95.4.sec.reverse_reply.1: > | extends reverse_alias to also fix the Realnames in outgoing Mail. I had to make the changes manually in send.c to make it work with 1.1.8; patchlist.c somehow disappeared. But it looks better than my version and a little bit smarter :-). Thanks, and what about adding this feature to one of the next versions? Regards, Stefan. -- First Law of Socio-Genetics: Celibacy is not hereditary.
Re: %N in $folder_format
On Fri, Mar 10, 2000 at 12:08:42AM +0200, Andrew W. Nosenko wrote: > Drew Bloechl wrote: > : In my .muttrc I have: > : > : set folder_format="%3C %N %-32.32f %-16.16d %s" > : > : However, the space with the %N is always blank when I do 'c' and '?' > : to browse mailboxes. Is there something special I have to do to get > : this to work? FWIW I'm delivering mail into these folders with > : procmail. > Your incomming mailbox (mailboxes) is placed on NFS-mounted file system? > Try --enable-buffy-size in configure-time. Nope. Local disk. ~/Mail. -- Drew Bloechl [EMAIL PROTECTED]
Re: why is mutt better?
> Actually, maybe it's my fault here. I always tell him my unix box can > beat up his windows box with one hard drive tied behind its back. He > just argues that windows is simpler, and that power tools should be > made easier to use. But then they wouldn't be power tools anymore ;-)
Re: why is mutt better?
On Thu, Mar 09, 2000 at 06:39:45PM +, J McKitrick wrote: : :I just got in a debate over email clients, and my windows friend :argues anything i can do in mutt, he can do in TheBat! just as easily. :I checked the feature list, and it is extensive. Most of what mutt :offers, thebat offers. Why is the advantage of mutt, or any :text-based email client? - uses any editor you want (like any Unix mail client) - has extensive hook mechanism (although choice of actions isn't) - spawn subshells to do whatever - tags messages without moving them to another folder/mailbox Having said this, I saw one feature in TheBat that I'd like to see Mutt have someday: the ability to create and use templates for new messages, replies, forwarded messages, etc. -- Eugene Lee [EMAIL PROTECTED]
Re: signature send-hook problem
On Thu, Mar 09, 2000 at 05:25:36PM -0500, Jim Toth wrote: :On Thu, Mar 09, 2000 at 03:34:08PM -0500, Josh Kuperman ([EMAIL PROTECTED]) :said: :> :> The commented out line always gets matched and will force the :> default signature. Is is simply changing the order? : :Yep, that's it. From the manual (section 3, Configuration): : : When multiple matches occur, commands are executed in the order : they are specified in the muttrc. I got bit by this too just a little while ago. I guess I'm used to the short circuit logic in C. -- Eugene Lee [EMAIL PROTECTED]
Re: why is mutt better?
on Thu, Mar 09, 2000 at 06:20:07PM -0800, Eugene Lee <[EMAIL PROTECTED]> wrote: > On Thu, Mar 09, 2000 at 06:39:45PM +, J McKitrick wrote: > : > :I just got in a debate over email clients, and my windows friend > :argues anything i can do in mutt, he can do in TheBat! just as easily. > :I checked the feature list, and it is extensive. Most of what mutt > :offers, thebat offers. Why is the advantage of mutt, or any > :text-based email client? > > - uses any editor you want (like any Unix mail client) > - has extensive hook mechanism (although choice of actions isn't) > - spawn subshells to do whatever > - tags messages without moving them to another folder/mailbox What is thebat like for speed? Mutt is very fast at reading and sorting large mail folders. BB -- Bevan Broun ph (08) 9380 1587 Computer Systems Officer fax (08) 9380 1065 Dept. Electrical and Electronic Engineering University of Western Australia rm. G70
Re: signature send-hook problem
Eugene & Josh, et al -- ...and then Eugene Lee said... % On Thu, Mar 09, 2000 at 05:25:36PM -0500, Jim Toth wrote: % : % : When multiple matches occur, commands are executed in the order % : they are specified in the muttrc. % % I got bit by this too just a little while ago. I guess I'm used to the % short circuit logic in C. Don't kick yourself yet. If more than one hook can apply, like a send-hook, then all are checked and all matches are applied in the order found. If, however, only one can apply (like a folder-hook or mebbe an fcc-hook), then the first one to generate a match drops you out of hook checking -- and so you should have your default case at the end. Sounds kinda funny at first, but you certainly couldn't have send-hooks stopping early, and why bother to build some sort of a parse tree for f*-hooks if you can just count on intelligent users to reverse their order for that type of hook :-) % % -- % Eugene Lee % [EMAIL PROTECTED] :-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: %N in $folder_format
Drew -- ...and then Drew Bloechl said... % On Fri, Mar 10, 2000 at 12:08:42AM +0200, Andrew W. Nosenko wrote: % > Drew Bloechl wrote: % > : % > : However, the space with the %N is always blank when I do 'c' and '?' % > : to browse mailboxes. Is there something special I have to do to get % > : this to work? FWIW I'm delivering mail into these folders with % > : procmail. % > Your incomming mailbox (mailboxes) is placed on NFS-mounted file system? % > Try --enable-buffy-size in configure-time. % % Nope. Local disk. ~/Mail. Is your shell, perhaps, checking for new mail as well? Anything that accesses the folder, as I recall, will reset the new function. Thus, --enable-buffy-size might just be the ticket after all. % % -- % Drew Bloechl % [EMAIL PROTECTED] :-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 to full name from alias list
Stefan (Bender) -- ...and then Stefan Bender said... % Hi, % % On Thu, Mar 09 2000 21:16:32 +0100 wrote Stefan `Sec` Zehl % % > | patch-0.95.4.sec.reverse_reply.1: % > | extends reverse_alias to also fix the Realnames in outgoing Mail. % % I had to make the changes manually in send.c to make it work with % 1.1.8; patchlist.c somehow disappeared. But it looks better than my Actually, patchlist.c is created by his patch-0.00.sec.patchlist.7 file (or a revision higher than that); you need to do a little more checking on his patch page. % version and a little bit smarter :-). It is pretty slick :-) % Thanks, and what about adding this feature to one of the next versions? This is one of the many not-directly-supported feature patches that are floating around out there; most of them are linked from the mutt home page, I believe. It probably won't make it into the main distribution because it would change a basic function of a mailer (believing what the other guy chooses to call himself) and because it's so well supported off of the development group's plate (so to speak). Personally, I like my mutt bred with 10 such feature patches, including the famous compressed folders patch, that I have to dig up from here and there and then check versions when I pull down a new mutt -- but I'm getting the hang of it :-) % % Regards, Stefan. % % -- % First Law of Socio-Genetics: % Celibacy is not hereditary. :-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
