Re: Mutt hanging on color
Oh man, it works!! But I have brightyellow almost everywhere in the
.mutt.color.body..
color header brightyellow default .*
color body brightyellow default "\\\([-A-Z']{2,}[ ,]*\)+"
color body brightyellow red "1-[0-9]{3}[- ][-0-9]+ +ext.? [0-9]+"
color body brightyellow default "\\(c\\)"
Why is this one a one off? Wierd as hell... And I know brightyellow
works coz I see it in my headers, and it is different from yellow ;)
* Suresh Ramasubramanian [EMAIL PROTECTED] [000629 14:03]:
Wari Wahab proclaimed on mutt-users that:
# SCREAMING TEXT (often used in spam)
color body brightyellow default" \([-A-Z']{2,}[ ,]*\)+"
Maybe your terminal doesn't understand a color called brightyellow? Try
giving a hex equivalent - #aa will do very fine I think.
-suresh
--
Suresh Ramasubramanian + [EMAIL PROTECTED]
Who made the world I cannot tell;
'Tis made, and here am I in hell.
My hand, though now my knuckles bleed,
I never soiled with such a deed.
-- A. E. Housman
--
Regards: Wari Wahab
"There are two ways of disliking poetry; one way is to dislike it, the
other is to read Pope."
-- Oscar Wilde
Re: Mutt hanging on color
Wari Wahab proclaimed on mutt-users that:
Oh man, it works!! But I have brightyellow almost everywhere in the
.mutt.color.body..
!?!?! It's the same terminal anyway, fscked if I know what's up :)
-suresh
color header brightyellow default .*
color body brightyellow default "\\\([-A-Z']{2,}[ ,]*\)+"
color body brightyellow red "1-[0-9]{3}[- ][-0-9]+ +ext.? [0-9]+"
color body brightyellow default "\\(c\\)"
"There are two ways of disliking poetry; one way is to dislike it, the
other is to read Pope."
-- Oscar Wilde
I'd reply in pope's own words -
A little knowledge is a dangerous thing,
drink deep, or taste not of the pierian spring.
Oscar Wilde evidently hadn't read enough of Pope to appreciate him :)
--
Suresh Ramasubramanian + [EMAIL PROTECTED]
Who made the world I cannot tell;
'Tis made, and here am I in hell.
My hand, though now my knuckles bleed,
I never soiled with such a deed.
-- A. E. Housman
Re: Mutt hanging on color
This is curious enough to investigate...
* Suresh Ramasubramanian [EMAIL PROTECTED]:
Wari Wahab proclaimed on mutt-users that:
# SCREAMING TEXT (often used in spam)
color body brightyellow default" \([-A-Z']{2,}[ ,]*\)+"
Maybe your terminal doesn't understand a color called brightyellow? Try
giving a hex equivalent - #aa will do very fine I think.
To the contrary, it has nothing to do with the colors (I changed
'brightyellow' to 'green' to test this). Not all messages freeze mutt,
though I found a segment that does:
Breaks at the hyphens
While this doesn't freeze it at all:
Removing the hyphen from [-A-Z'] stops it from freezing, but I don't know why.
# SCREAMING TEXT (often used in spam)
color body brightyellow default" \([A-Z']{2,}[ ,]*\)+"
DAVID
--
But perhaps inhaling light silenced. -- e.e.cummings in a blender
Re: feature request: delayed delete
On Wed, Jun 28, 2000 at 02:06:02PM +0200, Marius Gedminas wrote: :On Wed, Jun 28, 2000 at 02:14:28AM -0700, Eugene Lee wrote: : : Besides tagging messages by absolute datetimes, this could be extended : to your specific problem by allowing relative datetime patterns. So you : could do things like tag messages that are 14 days old or older. : :So what's wrong with ~d and ~r? Nothing at all. I just need to RTFM more often. My bad. :) -- Eugene Lee [EMAIL PROTECTED]
Re: Mutt hanging on color
On 2000-06-29 14:46:31 +0800, Wari Wahab wrote:
color body brightyellow default" \([A-Z']{2,}[ ,]*\)+"
As a general rule, try to avoid regular expressions which
nest multiple instances of "+" and "*". They tend to take
very long to apply.
Note, BTW, that the grouping and the trailing + are not
needed in this case (mutt does something which has the
effect you intend to achieve with hthis), so you may wish
to try this one instead:
color body brightyellow default "[-A-Z'][-A-Z'][-A-Z']*[ ,]*"
It should work considerably faster.
Re: Mutt hanging on color
On Thu, Jun 29, 2000 at 11:17:45AM +0530, Suresh Ramasubramanian wrote:
Wari Wahab proclaimed on mutt-users that:
# SCREAMING TEXT (often used in spam)
color body brightyellow default" \([-A-Z']{2,}[ ,]*\)+"
Maybe your terminal doesn't understand a color called brightyellow? Try
giving a hex equivalent - #aa will do very fine I think.
'brightyellow' is built into mutt.
mutt could interpret an rgb value but has no way to tell (most)
terminal emulators to render that.
--
Thomas E. Dickey [EMAIL PROTECTED]
http://dickey.his.com
ftp://dickey.his.com
how to colorize the entire line of selected messages ?
Hi, Does anybody know how I could color the entire line of selected messages in front of the indicator ? I've set : indicator brightcyan black But as you know it just colors the arrow and I didn't find any other options :( And I'm not sure at all that it must be defined in the indicator's colors.. Any idea?
Re: how to colorize the entire line of selected messages ?
Virginie [ ML ] proclaimed on mutt-users that: Hi, Does anybody know how I could color the entire line of selected messages in front of the indicator ? I've set : indicator brightcyan black But as you know it just colors the arrow and I didn't find any other options :( And I'm not sure at all that it must be defined in the indicator's colors.. Heh ... just put this line into your .muttrc unset arrow_cursor That way, the entire message will be highlighted by a bar - like in pine. hth -suresh -- Suresh Ramasubramanian + [EMAIL PROTECTED] For perfect happiness, remember two things: (1) Be content with what you've got. (2) Be sure you've got plenty.
Re: how to colorize the entire line of selected messages ?
On Thu, Jun 29, 2000 at 01:16:56PM +0200, Virginie [ ML ] wrote: Hi, Does anybody know how I could color the entire line of selected messages in front of the indicator ? I've set : indicator brightcyan black But as you know it just colors the arrow and I didn't find any other options :( And I'm not sure at all that it must be defined in the indicator's colors.. You must have 'set arrow_cursor' in your muttrc file, just remove this and the whole line of the selected message in the index will be shown in inverse video. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: how to colorize the entire line of selected messages ?
On Thu, Jun 29, 2000 at 03:58:15PM +0530, Suresh Ramasubramanian wrote: Heh ... just put this line into your .muttrc unset arrow_cursor That way, the entire message will be highlighted by a bar - like in pine. hth -suresh It works fine ! I'm so happy, Thank you :) -- Virginie Vacca Parinux Member (LUG - Paris) E-mail: [EMAIL PROTECTED]
Re: Mutt hanging on color
Alright, this works as well ;) I have no idea what the regexp refer to
though and yours is considerably easier to understand..
The question still remains though, why does mutt freeze..
* Thomas Roessler [EMAIL PROTECTED] [000629 15:44]:
On 2000-06-29 14:46:31 +0800, Wari Wahab wrote:
color body brightyellow default" \([A-Z']{2,}[ ,]*\)+"
As a general rule, try to avoid regular expressions which
nest multiple instances of "+" and "*". They tend to take
very long to apply.
Note, BTW, that the grouping and the trailing + are not
needed in this case (mutt does something which has the
effect you intend to achieve with hthis), so you may wish
to try this one instead:
color body brightyellow default "[-A-Z'][-A-Z'][-A-Z']*[ ,]*"
It should work considerably faster.
--
Regards: Wari Wahab
Never offend people with style when you can offend them with
substance.
-- Sam Brown, "The Washington Post", January 26, 1977
Re: those users
On Wed, Jun 28, 2000 at 07:30:23AM -0400, David T-G wrote: % Come to think of it: the first section in the "How do I..." stuff should be % How do I ask questions correctly, How do I read the manual and What the hell Actually, that sounds like a very very good idea. Perhaps the first part of the web page should have that, too! % does RTFM mean?? :) *grin* Nah, we won't tell 'em that one :-) Fine, I'll leave this one out. I'm writing this How do I ask questions correctly and How do I read the manual. Is there anybody out there who has aready some "How do I ..." stuff so I can stick to his/her layout? If not, you'll have to take mine :) Kai PS: The latter may be considered as a threat! :) -- x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x Kai Blin(mailto:[EMAIL PROTECTED]) Webmaster Inst. of Human Genetics Dept. of Molecular Genetics Wilhelmstr 27 phone (49)7071-2974890 D 72074 Tuebingen, Germany fax (49)7071-295233 http://www.uni-tuebingen.de/uni/thm/molgen/molgen.html Do molecular biologists wear designer genes? x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x
Re: Mutt hanging on color
On 2000-06-29 19:42:26 +0800, Wari Wahab wrote: The question still remains though, why does mutt freeze.. Simple: The regexp library hangs when trying the regular expression. I don't believe it's an endless loop - most likely, mutt will continue to work in an hour or two. ;-)
Removing a prefix from the subject of messages
Hello. I want to remove a prefix from the messages coming from a mailing list I am subscribed before saving the messages in its folder. Currently my procmail recipes for saving the message is DUMMY=`test -d linux-br || mkdir linux-br` :0: * ^[EMAIL PROTECTED] linux-br/`date +%Y-%m` The subject header line comes with one of the prefixes "(linux-br) ", "Re: (linux-br) ", "Re: Re: (linux-br) ", and so on (without the quotes). Can someone help me with this? Thanks. Romildo -- Prof. José Romildo Malaquias [EMAIL PROTECTED] Departamento de Computação Universidade Federal de Ouro Preto Brasil
Re: Removing a prefix from the subject of messages
* Jose Romildo Malaquias wrote on Thu, 29 Jun 2000: [procmail question] Please use the procmail list [EMAIL PROTECTED] -Dirk
Re: Qmail isn't delivering to MAILDIR/new....?
I don't understand it but when I send a message through echo to: deklown | /var/qmail/bin/qmail-insert . it is delivered to my box in Maildir format perfectly. I do it through telnet to my actual email address, it is delivered in mbox format to /var/spool/mail/$USER If I take out my .procmailrc, no deliver at all I am going to join the qmail list today, because I really dont' want to bother everyone with this... Any help would be appreciated, though. On Thu, Jun 29, 2000 at 07:30:37AM +0200, Frank Derichsweiler muttered: | On Wed, Jun 28, 2000 at 09:31:17PM -0700, Jason Helfman wrote: | I have this as my .qmail file: | /home/deklown/Maildir/new/ | | That is the bug. | You have to say | | /home/deklown/Maildir/ | | qmail detects that it is a considered to be a maildir format mailbox | because the "/" at the end. Therefore it will deliver into the new | sub-directory. (As stated by the Maildir specs) | | HTH | Frank | | -- | Frank Derichsweiler -- Jason G Helfman Network Administrator BizRate.com Fingerprint: 0B79 2B17 98CF 2347 CF90 7B50 E11C 587C 5560 21CC GnuPG http://www.gnupg.org Get Private! 1024D/556021CC
Re: Removing a prefix from the subject of messages
If you can comfortably accept that all Subject: lines look like Subject: .*(linux-br) ... then just turn your recipe into a clone/copy recipe and pipe the message through sed -s "s/^Subject: .*(linux-br) /Subject: /" and then proceed as normal. D'oh. That's a job for procmail's MATCH and formail. No need for an external program.
Re: Removing a prefix from the subject of messages
On Thu, Jun 29, 2000 at 11:39:27AM -0400, David T-G wrote: ...and then Jose Romildo Malaquias said... % % I want to remove a prefix from the messages coming ... % % The subject header line comes with one of the prefixes % "(linux-br) ", "Re: (linux-br) ", "Re: Re: (linux-br) ", % and so on (without the quotes). This is really more of a procmail question, but we've been known to take stabs at such here on the mutt-users mailing list. If you can comfortably accept that all Subject: lines look like Subject: .*(linux-br) ... then just turn your recipe into a clone/copy recipe and pipe the message through sed -s "s/^Subject: .*(linux-br) /Subject: /" ^^ and then proceed as normal. As am not an experienced procmail user, would you please just look at my new recipes and see if their are correct? :0 fwh * ^[EMAIL PROTECTED] * ^Subject: (Re: )*\(linux-br\) | sed -e "s/^Subject: \(Re: \)*(linux-br) /Subject: /" DUMMY=`test -d linux-br || mkdir linux-br` :0: * ^[EMAIL PROTECTED] linux-br/`date +%Y-%m` Thanks. Romildo -- Prof. José Romildo Malaquias [EMAIL PROTECTED] Departamento de Computação Universidade Federal de Ouro Preto Brasil
Re: Removing a prefix from the subject of messages
Lars -- ...and then Lars Hecking said... % % If you can comfortably accept that all Subject: lines look like % %Subject: .*(linux-br) ... % % then just turn your recipe into a clone/copy recipe and pipe the message % through % %sed -s "s/^Subject: .*(linux-br) /Subject: /" % % and then proceed as normal. % % D'oh. That's a job for procmail's MATCH and formail. No need for an % external program. Well, I thought about that, and formail is a called program at the same level as sed, but I didn't know how to strip part of the Subject: line with formail :-) :-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: Removing a prefix from the subject of messages
Romildo -- ...and then Jose Romildo Malaquias said... % On Thu, Jun 29, 2000 at 11:39:27AM -0400, David T-G wrote: % %sed -s "s/^Subject: .*(linux-br) /Subject: /" % ^^ You're right, of course; thanks for catching my typo. % % As am not an experienced procmail user, would you please just % look at my new recipes and see if their are correct? The best way to test, of course, is to cat a few messages through procmail and see how they come out :-) % % :0 fwh % * ^[EMAIL PROTECTED] % * ^Subject: (Re: )*\(linux-br\) % | sed -e "s/^Subject: \(Re: \)*(linux-br) /Subject: /" This doesn't look bad, but it seems to me that a simple command like my original suggestion would do the same thing -- unless there might be posts that look like Subject: something (linux-br) ... whose subjects you would want to preserve. My sed command will strip out RE:, re:, Re:, FWD:, forward: (FWD), and more -- be that good or bad... % % DUMMY=`test -d linux-br || mkdir linux-br` % :0: % * ^[EMAIL PROTECTED] % linux-br/`date +%Y-%m` That part looks fine. I'm sure, too, that these could be combined into one, but I'm too lazy to look that up just now :-) % % Thanks. HTH HAND % % Romildo % -- % Prof. José Romildo Malaquias [EMAIL PROTECTED] % Departamento de Computação % Universidade Federal de Ouro Preto % Brasil :-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: Removing a prefix from the subject of messages
% D'oh. That's a job for procmail's MATCH and formail. No need for an % external program. Well, I thought about that, and formail is a called program at the same level as sed, but I didn't know how to strip part of the Subject: line with formail :-) As always, I realised that "external program" thing only after sending :) Formail doesn't strip the subject line. You tell procmail to extract the relevant parts, and then feed the result to formail which rewrites the headers. It's more of a "use the right tool for this job" issue ...
UTF-8?
Can Mutt 1.2 handle UTF-8? When I have $charset="iso-8859-13", and $send_charset="utf-8", bad things happen. BTW, I have glibc 2.1.3. Marius Gedminas -- Hoping the problem magically goes away by ignoring it is the "microsoft approach to programming" and should never be allowed. -- Linus Torvalds
Help on save-hook please
Hi. I've been running mutt for several days now and also managed to setup my own procmail recipes. My problem is with the the save-hook as I want to be able to save read messages to, let's say, a "Mail\read.mutt" file. This is my present ~/.muttrc contents for the save-hook: folder-hook . set sort=threads folder-hook /var/mail/rino set sort=date-received folder-hook =sent set sort=date-sent folder-hook . save-hook * =received folder-hook IN.misc save-hook * =obsd folder-hook IN.ipfilter save-hook * =ipf folder-hook IN.mutt-users save-hook * =mutters I have "~/Mail/IN.misc", "~/Mail/IN.ipfilter", "~/Mail/IN.mutt-users" for my other mailboxes which I can read using "mutt -f". I have gone and checked the FAQs, Nancy's, and the mini-FAQ (bronto-FAQ now) and couldn't find a clue why read messages still reside in my ~/Mail/IN.mutt file or any other mailboxes. For normal mail that arrives in /var/mail/rino they get saved in "~/Mail/received" without problems but not any other messages from my other mailboxes.
Re: Mail-Followup-To and Reply-To
[ Sorry, there is no In-Reply-To field because I forgot to set the correct headers in my original message, and I couldn't extract the message-id from the archive... ] On 2000-06-27, fman wrote: try my_hdr From: [EMAIL PROTECTED] My suggestion wasn't clear enough. Here's what I was proposing: Suppose that I want to send an email to [EMAIL PROTECTED], and that I am not subscribed to this list. I would like replies to go to the list and myself. It is currently possible to have Mutt put the following header automatically: Mail-Followup-To: [EMAIL PROTECTED], Hugo Haas [EMAIL PROTECTED] However, this is not standard and doesn't work very well in practice. So I was suggesting to add an option to do the same using Reply-To instead of Mail-Followup-To such as: Reply-To: [EMAIL PROTECTED], Hugo Haas [EMAIL PROTECTED] since it seems legitimate to me to use Reply-To in such a case (which I did this time). I don't think that it's possible to do this with send-hooks (or if it is, I'd be very interested to see how to make send-hook interact with the From, To, Cc and the value of lists and subscribe), so it would require some new code. I hope this is clearer now. -- Hugo Haas [EMAIL PROTECTED] - http://larve.net/people/hugo/ Marge, it takes two to lie. One to lie and one to listen. -- Homer J. Simpson
Re: Help on save-hook please
Rino Mardo [EMAIL PROTECTED] wrote on Wed, 28 Jun 2000: My problem is with the the save-hook as I want to be able to save read messages to, let's say, a "Mail\read.mutt" file. Do you want to save read messages automatically when you exit a folder, or do you want to specify the default folder you're given in the prompt when you choose to save a message? The first is done by setting $record appropriately (and $move should be something else than "no", of course). The second is done with save-hooks (or fcc-save-hooks, but you seem to want just save-hooks). save-hooks are checked when you do save-message which is bound to "s" by default, they are not checked on folder exit. folder-hook . save-hook * =received The * should be a . instead, like this: folder-hook . save-hook . =received But if you want automatic saving of read messages, what you're looking for is in fact: folder-hook . set record='+read.mutt' The + character is a shortcut to your $folder dir, which by default is ~/Mail. Alternatively you could also use = instead of +, but in the above it would be confusing. :-) Hope this helps, 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 / Funny off-topic messages are always on-topic.
Re: Can't compile mutt 1.3.4
On Thu, Jun 29, 2000 at 12:39:26AM +0200, Thomas Roessler wrote: checking for iconv... yes checking whether this iconv is good enough... no configure: error: Try using libiconv instead Get libiconv from http://clisp.cons.org/~haible/. I downloaded libiconv-1.3.tar.gz and followed the generic install. However I still get the same warning as above. Can anyone tell me what I am doing wrong? Regards Mark
Re: Mail-Followup-To and Reply-To
Hugo Haas [EMAIL PROTECTED] wrote on Tue, 27 Jun 2000: Hi. Hello! I read a lot about Mail-Followup-To and Reply-To recently (including in the mutt-users archive) and my conclusion is that: - Mail-Followup-To is not a standard and is supported by very few MUA's. Well, it's not a standard in the way that it would have been defined in a RFC. It's also not a standed in the way that there are a lot of popular MUAs which support it (ie. "industry standard" sort of). It *is* a standard in a way that there exists specific documentation on the use of it with definitions. (http://cr.yp.to/proto/replyto.html) The only MUA I know of which supports MFT is Mutt. Unfortunately. This means that users of other MUAs should campaign for adding such a feature to their clients, because it is unlikely to get added otherwise. :-( Except maybe if it was included in some RFC...? qmail (a MTA) does support MFT passively -- it can add the header to outgoing emails, but this only works for messages added locally with qmail-inject, and it doesn't mean that whatever MUA is used on such system will then respond to MFTs. - Reply-To should be able to do the right thing, even if some implementations are forcing people to use this field. This is not quite true. Reply-To doesn't specify whether a message reply is "discussion group followup" or a "private reply" -- there is a distintion between the two, and this distinction is what causes the problems with Reply-To. I'm also not aware of whether there is any specified way to have Reply-To set to more than one address. You can either have multiple Reply-To headers, one address per header, or you can have multiple addresses in one header. I think that in either case, the behaviour of MUAs is unspecified, so you may and will get random results. Does anyone know more about this? Of course, mailing-lists adding a Reply-To header would break that, but anyway there is no perfect solution. There is a perfect solution, which is MFT, it's just that the other MUAs don't support it. :-) Get them to support it, and the problem goes away. If they don't start to support it, the problems inherent in playing with Reply-To will remain. It's that simple. Most of the (discussion) mailing lists I'm on go through the "should Reply-To be set to the list or sender?" talk at least once, some go through it every now and then. This is proof enough that Reply-To isn't the right solution to mailing list issues, there's always some problems if you try to make it be the list-discussion indication method. Modern MUAs, except for Mutt (that I know of) simple do not deal with mailing lists intelligently, they are only intended for private email use. Just like the original mail specifics. I find it rather curious that nobody (well, the MUA authors and the users of those MUAs) actually perceives this as a serious problem... Yes, at the moment it doesn't look like MFT is widely supported. However, IMHO it's *clearly* the best solution to the problem. Just because it might be difficult to get the right solution adopted because of legacy behaviour, that doesn't mean we shouldn't *try* -- if we don't try, then some things will *never* get fixed, will they? Oh well, ranting about this on mutt-users is pretty much preaching to the choir, since Mutt already does support MFT. It's the *other* MUAs we should be concerned about, and the developers/users of those don't read mutt-users. To conclude, yes you shouldn't expect MFT to work yet except on lists where the majority of people use Mutt as the MUA. That doesn't mean that you should abandon it though! Hugo Haas [EMAIL PROTECTED] wrote on Thu, 29 Jun 2000: I don't think that it's possible to do this with send-hooks (or if it is, I'd be very interested to see how to make send-hook interact with the From, To, Cc and the value of lists and subscribe), so it would require some new code. You can't have it done automagically, like MFT is done now. You can match against the current From header with ~f, you can match against sending it to a subscribed (?) mailing list with ~l, but you can't construct similar sets of addresses as MFT generation does with .muttrc commands alone. So yes, it would require some new code. 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 / Warning: The electrons relaying this email travel at extremely high speed.
Re: Browser sorting by date and maildirs
Morten Bo Johansen [EMAIL PROTECTED] wrote on Sun, 25 Jun 2000: sort_browser=reverse-date It doesn't work, however, since I'm using maildirs and without assigning a lock file during procmail delivery then no time stamp is set on the mailbox folder and therefore Mutt cannot sort the folders as intended. (Rather the time stamp is set on the "cur/new/tmp" subfolders) You're right, I've found the same thing. Question: Is there any way that I can have a time stamp applied to mailbox folders without having to assign a (superfluos) lock file during delivery so that I can have folders with new mail always placed on top? There exists a patch for Mutt which makes Mutt consider the "new" sub-directory timestamp to be the "folder timestamp" for Maildir folders. I really think it should be integrated into the mainstream Mutt, but so far it hasn't been... Actually, looking at that patch, it also does something else with Maildirs, so maybe that's why. It's also a bit old (March), so may not apply cleanly to current Mutt versions. 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 / It has been discovered that research causes cancer in rats.
Re: Can't compile mutt 1.3.4
On 2000.06.29, in [EMAIL PROTECTED], "Mark Berry" [EMAIL PROTECTED] wrote: On Thu, Jun 29, 2000 at 12:39:26AM +0200, Thomas Roessler wrote: checking for iconv... yes checking whether this iconv is good enough... no configure: error: Try using libiconv instead Get libiconv from http://clisp.cons.org/~haible/. I downloaded libiconv-1.3.tar.gz and followed the generic install. However I still get the same warning as above. Can anyone tell me what I am doing wrong? Using Solaris? At line 4312 of configure, insert this line: mutt_cv_iconv_good=yes -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Can't compile mutt 1.3.4
David Champion writes: On 2000.06.29, in [EMAIL PROTECTED], "Mark Berry" [EMAIL PROTECTED] wrote: On Thu, Jun 29, 2000 at 12:39:26AM +0200, Thomas Roessler wrote: checking for iconv... yes checking whether this iconv is good enough... no configure: error: Try using libiconv instead Get libiconv from http://clisp.cons.org/~haible/. I downloaded libiconv-1.3.tar.gz and followed the generic install. However I still get the same warning as above. Can anyone tell me what I am doing wrong? Using Solaris? At line 4312 of configure, insert this line: mutt_cv_iconv_good=yes Maybe he didn't delete config.cache. Or he needs to supply LDFLAGS=-R/where/ever on the configure line. A look into config.log will clear this up.
Re: those users (was Re: Reply to all???)
On Tue, Jun 27, 2000 at 12:08:28PM -0400, David T-G wrote: [...] for starters? Heck, maybe the Muttrc included in RPMs could pop up a message saying "Don't ask; read first" until the user figures out how to get rid of it, [...] Hm, maybe for a start I could put a few big, red "Read the manual!" on the RPM Team webpages... ;-) Other than that, I'm not certain a "nag screen" is such a good idea - as tempting as the idea is. Simply too annoying, if you ask me. Thomas -- - Thomas Ribbrock http://mutt.linuxatwork.at (mutt RPMs) http://www.bigfoot.com/~kaytanICQ#: 15839919 "You have to live on the edge of reality - to make your dreams come true!"
Re: those users (was Re: Reply to all???)
On Fri, Jun 30, 2000 at 01:32:41AM +0100, Thomas Ribbrock wrote: On Tue, Jun 27, 2000 at 12:08:28PM -0400, David T-G wrote: [...] for starters? Heck, maybe the Muttrc included in RPMs could pop up a message saying "Don't ask; read first" until the user figures out how to get rid of it, [...] Hm, maybe for a start I could put a few big, red "Read the manual!" on the RPM Team webpages... ;-) Other than that, I'm not certain a "nag screen" is such a good idea - as tempting as the idea is. Simply too annoying, if you ask me. I'm pretty sure, that if such a message were added to Mutt, the mailing list would be flooded with questions "how do I turn this message off?" ;-) Marius Gedminas -- We don't care. We don't have to. We're the Phone Company.
Re: Mail-Followup-To and Reply-To
At 11:55 PM 6/29/00 +0300, Mikko Hänninen wrote: [...] I'm also not aware of whether there is any specified way to have Reply-To set to more than one address. You can either have multiple Reply-To headers, one address per header, or you can have multiple addresses in one header. I think that in either case, the behaviour of MUAs is unspecified, so you may and will get random results. Does anyone know more about this? It's perfectly fine, and has been since at least RFC-822 (1982). Of course, that doesn't mean that there aren't broken MUAs out there... Cheers, Stan ps - your post said Reply-To you, but MFT the list and Hugo. What should that combination mean, I wonder?
Re: Removing a prefix from the subject of messages
On 2000.06.29, in [EMAIL PROTECTED],
"Lars Hecking" [EMAIL PROTECTED] wrote:
D'oh. That's a job for procmail's MATCH and formail. No need for an
external program.
No, but it's easier with an external program, because procmail's
$MATCHing is so weak. Here's my old procmail matcher (more or less):
:0
* LIST ?? .+
{
RE=""
:0
* SUBJECT ?? ^ *\/[rR][eE]:
{ RE="${MATCH} " }
:0 E
* LIST ?? yes
* SUBJECT ?? ^ *\[[^]]+\] *\/[^ ].*
{ NEW_SUBJECT="${RE}${MATCH}" }
:0
* LIST ?? yes
* SUBJECT ?? ^ *[rR][eE]: *\[[^]]+\] *\/[^ ].*
{ NEW_SUBJECT="${RE}${MATCH}" }
:0 E
* $ SUBJECT ?? ^ *\[${LIST}\] *[rR][eE]: *\[${LIST}\] *\/[^ ].*
{ NEW_SUBJECT="${RE}${MATCH}" }
:0 E
* $ SUBJECT ?? ^ *\[${LIST}\] *\/[^ ].*
{ NEW_SUBJECT="${RE}${MATCH}" }
:0 E
* $ SUBJECT ?? ^ *[rR][eE]: *\[${LIST}\] *\/[^ ].*
{ NEW_SUBJECT="${RE}${MATCH}" }
}
Here's the new one:
:0
* LIST ?? .+
{
NEW_SUBJECT=`echo ${SUBJECT} | sed -e "s/\[${LIST}\] *//g"`
}
(The formail runs later.) Am I missing something? Is there a way to
achieve the same match with \/ and $MATCH that uses fewer steps?
--
-D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Mail-Followup-To and Reply-To
Stan Ryckman [EMAIL PROTECTED] wrote on Thu, 29 Jun 2000: It's perfectly fine, and has been since at least RFC-822 (1982). Of course, that doesn't mean that there aren't broken MUAs out there... And what's the proper way of doing multiple addresses? One, single Reply-To or multiple headers? In any case it looks like your mailer picked the entire header contents and added "@ma.ultranet.com" after it, for some reason. Proof enough that mailers do weird things with Reply-To headers. ps - your post said Reply-To you, but MFT the list and Hugo. What should that combination mean, I wonder? It means that private replies should go to [EMAIL PROTECTED], mail followups (list replies) should go to the list and Hugo. This is *one* example where trying to set up Reply-To properly would fail, as: 1) I'm required to have [EMAIL PROTECTED] as the From address, or I can't post to the list without approval 2) I still want to use [EMAIL PROTECTED] as my public address for replies that are sent privately to me 3) I want to indicate that I'm subscribed to mutt-users, so don't need private copies on list discussion 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 / Life would be much easier if I had the source code.
Re: Removing a prefix from the subject of messages
Romildo -- ...and then Jose Romildo Malaquias said... % Hello. Hi! % % I want to remove a prefix from the messages coming ... % % The subject header line comes with one of the prefixes % "(linux-br) ", "Re: (linux-br) ", "Re: Re: (linux-br) ", % and so on (without the quotes). This is really more of a procmail question, but we've been known to take stabs at such here on the mutt-users mailing list. If you can comfortably accept that all Subject: lines look like Subject: .*(linux-br) ... then just turn your recipe into a clone/copy recipe and pipe the message through sed -s "s/^Subject: .*(linux-br) /Subject: /" and then proceed as normal. % % Can someone help me with this? HTH HAND % % Thanks. % % Romildo % -- % Prof. José Romildo Malaquias [EMAIL PROTECTED] % Departamento de Computação % Universidade Federal de Ouro Preto % Brasil :-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: Help on save-hook please
On Thu, Jun 29, 2000 at 11:33:33PM +0300 or thereabouts, Mikko Hänninen wrote: snipped... folder-hook . save-hook * =received The * should be a . instead, like this: folder-hook . save-hook . =received Hmm, that could be the reason why I'm getting a repetition operand invalid. But if you want automatic saving of read messages, what you're looking for is in fact: folder-hook . set record='+read.mutt' But this is assuming I am only subscribed mutt-users right? So all mails go to "read.mutt" because of that "." in folder-hook. The + character is a shortcut to your $folder dir, which by default is ~/Mail. Alternatively you could also use = instead of +, but in the above it would be confusing. :-) Hope this helps, Mikko Yes the "+" part as I've already fixed my problem using mbox-hook for each of my mailing lists. Either I need new reading glasses or more sleep as I wasn't able to find what that "+" means up to now. Thank you for responding.
