Re: Hello. I need help configuring mutt.
Jonathan Rosebaugh proclaimed on mutt-users that: primary_hostname = example.com qualify_domain = example.com I do not know why this seems so hard to understand: I DO NOT HAVE A CANONICAL DOMAIN NAME!!! You dont need one. Now try this: primary_hostname=frodo.localdomain qualify_domain=email.com Then configure mail to accept mail for frodo.localdomain Outgoing mail will go out properly, masquerading as email.com now. Even if you dont set the sender envelope. -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
Re: Collapse threads
* Michael Tatge [EMAIL PROTECTED], 2001-05-06 01:58 +0200: Michael Tatge muttered: Hi, Efata muttered: How I can make default for mutt to collapse message after I read. Thanks you want a thread to be collapsed, when there are no more new messages in it, while the other threads stay uncollapsed, right? Don't think that's possible without patching the source. I'm too fast once again. unset collapse_unread folder-hook . push \eV I love this one, Michael A. B. [[EMAIL PROTECTED]]
Re: Hello. I need help configuring mutt.
On Sun, May 06, 2001 at 06:31:11AM -0500, Jonathan Rosebaugh typed: That would be very nice if I wanted to masquerade as email.com. Unfortunatly, I don't. Look, I've got this solved the way I like it, so let's just drop this thread. Sure, man :) -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
strange config problem (1.2.5i)
Hello, I want to have something like that: mailboxes ! \ +amazon \ #+announces \ +arrivees in order to add/and delete viewing folders, with them classified by alpha order. problem is, parsing mailboxes stops after amazon, so arrivees isn't shown. seems like a problem with \ and # parsing... any workaround (other than putting every # folders at the end of the list, of course) or bug correction ? Arnaud. -- BOFH excuse: The monitor needs another box of pixels.
Re: F1 key macro to launch Mutt Manual
On Sun, May 06, 2001 at 07:11:27AM +0530, Suresh Ramasubramanian wrote: On Sat, May 05, 2001 at 07:01:51PM -0600, Duke Normandin typed: I'm looking for the F1 macro that'll launch the Mutt Manual. I've tried to create myself, but no joy! Anybody have it in their muttrc or know where I can find it? TIA... macro generic f1 !less /usr/doc/mutt/manual.txt\n Show Mutt documentation macro index f1 !less /usr/doc/mutt/manual.txt\n Show Mutt documentation macro pager f1 !less /usr/doc/mutt/manual.txt\n Show Mutt documentation Thanks bud! I had it just about fingered out -- forgot the bloody 'bang'. Later... -- -duke Calgary, Alberta, Canada
Re: HTML mail - mailcap problem
On Sat, May 05, 2001 at 09:21:01PM -0400, Michael P. Soulier wrote: On Sat, May 05, 2001 at 03:47:24PM -0600, Duke Normandin wrote: However, when I select a message from the index that's HTML I get the following: mailcap entry for type text/html not found What the hell? Hey Duke. Check the exact mime-type, there are about four that come up. Here's a cut from my .mailcap text/html ; lynx -dump -force_html %s ; copiousoutput text/htm; lynx -dump -force_html %s ; copiousoutput message/html; lynx -dump -force_html %s ; copiousoutput message/htm ; lynx -dump -force_html %s ; copiousoutput I use lynx instead of links. Works great. The copiousoutput is also required. Mike I'll try the 4 mailcap entries above and report back. Thanks! -- -duke Calgary, Alberta, Canada
Re: How to specify the current folder in a folder-hook?
On Sat, May 05, 2001 at 03:48:29PM -0500, Tim Legant wrote:
On Sat, May 05, 2001 at 01:43:30AM +0100, Mark Sheppard wrote:
I missed that post - I've only been using mutt (and subscribed to the
list) for a few days, but that sounds like the kind of thing I want.
Unfortunately when I add this line to .muttrc then run mutt and hit
`s' on an email with `L' by it it doesn't work, I just get prompted
for a mailbox name:
Save to mailbox ('?' for list): =
Hmmm. Well, I obviously didn't try it - I figured Lars was
authoritative! :)
I subscribe to multiple mailing lists but I use procmail to separate the
mail into the different folders before reading. Less work in the long
run, I find. Have you considered that? You might find it a lot more
satisfying than parking a brick on the 's' key
That wasn't really what I was after. I want all my incoming mail to
arrive in a single mailbox. Most list traffic I read and then delete,
but there's the occasional message or thread that I want to save using
this method.
For the time being I've hardcoded a hook for each mailing list (eg.
save-hook ~Cmutt-users =mutt-users), but it would be better if there
was something like the %0 thing you mentioned so I would only have to
have one rule to achieve this for all mailing lists.
I think mutt's kind of recognising the %0 otherwise it would prompt:
Save to mailbox ('?' for list): =%0
However it's just removing the %0 rather than replacing it by
something useful.
Mark.
Deleting messages when entering a folder
I would like mutt to delete messages older than a certain date when entering my mailing list folders, in other words executing the function: delete-pattern ~d 2w Is there a way to use folder hooks to execute a function? It seems as though hooks only run commands, and only macros use functions. Is this true, or am I just confused? Thanks. -- Brian Nelson [EMAIL PROTECTED]
Re: strange config problem (1.2.5i)
* On [010506 15:22] Arnaud S . Launay [EMAIL PROTECTED] wrote: Hello, I want to have something like that: mailboxes ! \ +amazon \ #+announces \ +arrivees seems like a problem with \ and # parsing... The problem being that '#' is the symbol for a comment in your muttrc, and so the rest of the line ins't parsed at all. Unless you mean you don't want to specify the +announces box on purpose, if so, i'm confused Lawrence
Re: strange config problem (1.2.5i)
On Sun, May 06, 2001 at 03:19:16PM +0200, Arnaud S . Launay wrote: I want to have something like that: mailboxes ! \ +amazon \ #+announces \ +arrivees in order to add/and delete viewing folders, with them classified by alpha order. problem is, parsing mailboxes stops after amazon, so arrivees isn't shown. Well, '#' is a comment through the end of the line. You've commented off your line-continuation character ( \ ) and therefore, as far as the parser is concerned, +amazon is the last entry on the line. seems like a problem with \ and # parsing... Nope, it's working the way it should. Comments are stripped first. This is true of just about every programming / configuration language in the world. I say just about because someone will probably point to one that doesn't work this way, but it would be the odd exception. any workaround (other than putting every # folders at the end of the list, of course) or bug correction ? Try mailboxes +amazon #mailboxes +announces mailboxes +arrivees Tim
Re: strange config problem (1.2.5i)
Le Sun, May 06, 2001 at 03:08:11PM -0500, Tim Legant a écrit: [snip] seems like a problem with \ and # parsing... Nope, it's working the way it should. Comments are stripped first. This is true of just about every programming / configuration language in the world. I say just about because someone will probably point to one that doesn't work this way, but it would be the odd exception. Yes, I see what you mean. As I was saying by mail to someone else, it's the difference between the logical computer language and human thought :) Anyway, and just for debate, what do you think of the following: # this line is a comment \ but what is this one ? is 2nd line a comment as there is the \ indicating the parsing continue on next line, or is it not, as everything beyond the # will be treated as comment and so not analysed ? in the case of mutt, the comment continue til the next blank line, but I'm not sure every soft acts in the same way... any workaround (other than putting every # folders at the end of the list, of course) or bug correction ? Try mailboxes +amazon #mailboxes +announces mailboxes +arrivees Did it right. Many, many thanks. Arnaud. -- BOFH excuse: Police are examining all internet packets in the search for a narco-net-traficer
Re: Deleting messages when entering a folder
Brian Nelson wrote: I would like mutt to delete messages older than a certain date when entering my mailing list folders, in other words executing the function: delete-pattern ~d 2w Is there a way to use folder hooks to execute a function? It seems as though hooks only run commands, and only macros use functions. Is this true, or am I just confused? Try using this as the command portion of the folder-hook: push delete-pattern~d 2wenter Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: Deleting messages when entering a folder
On Sun, May 06, 2001 at 05:33:51PM -0400, Mr. Wade wrote: Brian Nelson wrote: I would like mutt to delete messages older than a certain date when entering my mailing list folders, in other words executing the function: delete-pattern ~d 2w Is there a way to use folder hooks to execute a function? It seems as though hooks only run commands, and only macros use functions. Is this true, or am I just confused? Try using this as the command portion of the folder-hook: push delete-pattern~d 2wenter Good luck! Yup, that does it. Thanks. -- Brian Nelson [EMAIL PROTECTED]
Re: strange config problem (1.2.5i)
On 2001.05.06, in [EMAIL PROTECTED], Tim Legant [EMAIL PROTECTED] wrote: Nope, it's working the way it should. Comments are stripped first. This is true of just about every programming / configuration language in the world. I say just about because someone will probably point to one that doesn't work this way, but it would be the odd exception. Well, I'm all set up to look silly for mentioning it, but Sh doesn't work this way, for example, and I figure that this general syntax of using line termination, '#' comment markers, and '\' line continuations is *nominally* based upon -- or at least popular because of -- sh's model. In such a syntax, there are three ways of dealing with the relationship of comments to line continuations, and I don't really think there's a strong balance toward a single one of them among all syntaxes in the world. You can parse comment delimiters before line continuation (like sh), or line continuation before comments (like mutt), or you can offer a hybrid where comments end with an EOL *or* a line continutation marker, which is what Arnaud Launay expected. The hybrid is also what I, as a programmer, usually choose, since it seems to be the most flexible. I don't think it would be silly to ask about changing the order in which mutt parses these. I'd certainly vote for a change. But it would perhaps mess with too many people's configuration files, so I'm not sure it's worth it. I just want to disagree that this behavior is somehow naturally correct. :) -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Using multiple mail server for uploading mail
On Fri, May 04, 2001 at 05:28:53PM -0400, Sam Roberts wrote: Maybe I've made this more complicated than I should. What I am trying to do is be able to send mail with different return addresses ie. [EMAIL PROTECTED] and [EMAIL PROTECTED] Whatever I do, my email always has a return address of [EMAIL PROTECTED] I think you're confusing the envelope address and the from field. If you'r at work, and you want to send mail to people so the from field says [EMAIL PROTECTED], just write the address you want to be from in the from field while you're editing the message. Write whatever you want in there. When people get your mail it will look as if it's from that address, and their replies will go there. One problem solved? I do this all the time when I send somebody mail, but I want their replies to go to my home address. Another possibility is that your ISP is changing the domain part of the address to be @my.isp. I don't know if this would or should happen with an ISP, but it is done within large commercial organizations that have sub-domains. For example, From: [EMAIL PROTECTED] becomes From: [EMAIL PROTECTED] You're ISP may be changing [EMAIL PROTECTED] to [EMAIL PROTECTED] since it knows your real account with them. just another thought (that's two today! ;) ) jc
How to give color to parent message
How I give sign or color to message (message have child only) in collapse thread? Thanks
Re: How to give color to parent message
Efata wrote: How I give sign or color to message (message have child only) in collapse thread? Thanks I think you are asking how to specify index colors for a message that is part of a collapsed thread. Assuming your terminal supports color, this can be done using something like the following in ~/.muttrc or a another sourced file: color index red black ~v Of course, you could substitute whatever colors you like. This has effect only when the thread is collasped. When the thread is not collapsed, the color is not evidenced. Good luck! -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: How to give color to parent message
On 2001.05.06, in 1lgg_B.A.r8G.Qoe96@mostproper, Mr. Wade [EMAIL PROTECTED] wrote: Efata wrote: How I give sign or color to message (message have child only) in collapse thread? I think you are asking how to specify index colors for a message that is part of a collapsed thread. Assuming your terminal supports color, this can be done using something like the following in ~/.muttrc or a another sourced file: color index red black ~v You can also use the approach of setting index_format to contain %?M?%2M%4c? This will display the number of hidden children in a collapsed thread instead of the message size whenever a displayed message is a thread leader. I prefer this, since it gives more information and uses less color. (I save my colors for other things.) (Actually, my index_format the shows the number of children if there are collapsed children, or else the number of attachments if there are attachments, or else the message size. Quite a space-time-saver. :) ) -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: How to give color to parent message
Efata wrote: How I give sign or color to message (message have child only) in collapse thread? Mr. Wade replied: I think you are asking how to specify index colors for a message that is part of a collapsed thread. Assuming your terminal supports color, this can be done using something like the following in ~/.muttrc or a another sourced file: color index red black ~v David Champion commented: You can also use the approach of setting index_format to contain %?M?%2M%4c? This will display the number of hidden children in a collapsed thread instead of the message size whenever a displayed message is a thread leader. I prefer this, since it gives more information and uses less color. (I save my colors for other things.) (Actually, my index_format the shows the number of children if there are collapsed children, or else the number of attachments if there are attachments, or else the message size. Quite a space-time-saver. :) ) I use a strategey similar to David Champion's index_format method. My $index_format contains %?M?(#%03M)(%4c)? which is nearly identical to what he suggested. I'd be interested, though, in how he managed to get the index_format to display the number of attachments if there are attachments as he said. -- Mr. Wade -- Linux: The Choice of the GNU Generation
Re: How to give color to parent message
On 2001.05.06, in 6_VECC.A.XuH.KQf96@mostproper, Mr. Wade [EMAIL PROTECTED] wrote: I'd be interested, though, in how he managed to get the index_format to display the number of attachments if there are attachments as he said. A patch: http://home.uchicago.edu/~dgc/mutt/#attach It lets you configure pretty flexibly what attachment means, but suits most people's interests out of the box. I use this with the patch following it on that page, which simulates if/else-if/else constructions. The combination lets me show any of three different things in the same location, depending on circumstances. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Can't send zipfiles (revisited)
Is it me - or is it Mutt? I can't send a freaking zipfile w/o having the sucker grunged at the other end. I experimented with changing the encoding even -- to 7bit instead of base64. I'd like to have *no* encoding but can't see how that's done. Anybody else having trouble sending zip attachments? -- -duke Calgary, Alberta, Canada
Re: Can't send zipfiles (revisited)
Duke Normandin proclaimed on mutt-users that: Is it me - or is it Mutt? I can't send a freaking zipfile w/o having the sucker grunged at the other end. I experimented with changing the encoding even -- to 7bit instead of base64. I'd like to have *no* encoding but can't see how that's done. Anybody else having trouble sending zip attachments? No. -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI EMail Sturmbannfuhrer, Lower Middle Class Unix Sysadmin
