Re: mail_check and mark_old
On Thu, Mar 23, 2000 at 11:16:45PM +0200, Mikko Hänninen wrote: Erik Thiele [EMAIL PROTECTED] wrote on Thu, 23 Mar 2000: mark_old: i use standard unix mail folders. unset mark_old does what i want. but in mutt -y overview mode, the folders with new messages inside won't be shown (they are shown only the first time). but this is probably a feature ? i ain'T sure ;) That's because (I assume) after Mutt exits, the modification and access times are the same. This is really a tricky issue: should the "N" flag in the folder index indicate that the folder has *newly arrived* mail in it, or should it indicate that the folder contains mail marked as new? These two are separate methods, and you can't have both. Currently, the behaviour seems to vary depending on the folder type. mbox folders behave in the former way, and Maildir folders in the latter. I believe this is so regardless of the value of $mark_old. I suppose when exiting a mbox folder with messages still marked as new, Mutt could set the folder access time 1 second earlier than the modification time, in order to get the N flag in the folder listing. However it's not clear whether it should do this or not; some people may want it one way while others the other. This suggests the need for YAO (yet-another-option)... i think the best item for a YAO, that would also solve the "Compressed Folders and the "N" flag" thread would be: real_check_not_only_atime it means that mutt doesn't examine the atime of the folder but instead looks inside and determines all of it's information from inside the folder. this option would fix ALL of those stupid atime related problems. YES, it is slow. but it works (tm) ;) cu erik -- Name: Erik Thiele Email: [EMAIL PROTECTED]o `QQ'_ IRC: erikyyy/ __8 WWW: http://www.erikyyy.de/ ' `
Re: Flag N with compressed folders
~/.procmailrc: :0 * ^TO_:.*mutt-users. |gzip -c $s ~/Mail/mutt-users.gz Until now I never had problems with loosing mail. So I didnt need any "lock". BTW: Should I lock? What? Why? (As long as I'm the only person on my computer..) Just add the second colon at the beginning of the recipe. If I understand the procmail man page correctly, it will then use ~/Mail/mutt-users.gz.$LOCKEXT. You being the only user on the computer doesn't matter: you could have several mail messages coming in at the same time, and a number of concurrent procmail processes trying to appand to the mailbox file at the same time. Anyway..Is this right now a problem I can fix somehow? Well I dont really need the patch for saving space on my HD. - I just only like the idea. :)
Re: dupe checking
i thought it would come down to some script with procmail/formail, but was hoping that there's a "one key solution" from within mutt. but the examples from the procmailex manpage seem to be very interesting though. i will try the solution from .procmailrc that checks every mail automatically for dupes Just make sure to read the whole section about dupe checking. Use the second recipe, not the first.
Re: Flag N with compressed folders
On Fri, 24 Mar 2000, Gero Reichard wrote: :0 * ^TO_:.*mutt-users. |gzip -c $s ~/Mail/mutt-users.gz Until now I never had problems with loosing mail. So I didnt need any "lock". BTW: Should I lock? What? Why? (As long as I'm the only person on my computer..) Above you have a command to append to mutt-users.gz. IMHO you should lock this folder before writing to it, because otherwise a second process (either mutt or a second procmail instance) could write to this file at the same time, which may cause trouble. Anyway..Is this right now a problem I can fix somehow? I would try this procmail rule: :0: * ^Sender: owner-mutt-users@mutt\.org |gzip -c $s ~/Mail/mutt-users.gz If I understand procmailrc(5), the extra ':' should use the name after '', append $LOCKEXT and use this as the lockfile. Tscho Roland -- * [EMAIL PROTECTED] * http://www.spinnaker.de/ *
Re: [CLUG] Mutt
! Erik Jarvi [EMAIL PROTECTED] [240300 06:54]: On Thu, Mar 23, 2000 at 09:30:29AM -0600, Jason Helfman wrote: Well you can use the system defaults, by using the "?" key. But I believe it is "C" to copy the message to another folder. Thanks for the info. I figured it out. "s" for save to a folder, and "C" is to copy to a folder. My only complaint with Mutt is you can't (I think) hilite the index by subject. I'd like to have the different mailing lists that I'm on have a different color. I've only been able to hilite by status. new, deleted, tagged, or flagged. I am goign to copy this message to [EMAIL PROTECTED] and see if this can be done. I am almost positive that you can do what you are speaking of. You can do anything with mutt, I have found. I've been looking into the (proc|send|fetch)mail combo. My only concern is leaving port 25 open. I have ident logging, and I've noticed that sending mail the host where I'm sending mail to is connecting to ident. Are there any gotcha's by not using my ISP's mailserver to send mail, since I'm on a dialup? Thanks, Erik -=- ChicagoLand Linux Users Group: general discussion mailing list. To unsubscribe mail to [EMAIL PROTECTED] with body, "unsubscribe clug". -=- To recieve announcements only: subscribe to clug-announce by mailing to [EMAIL PROTECTED] with body, "subscribe clug-announce". -=- Online archives at http://clug.chicago.il.us/list/ -- /helfman "At any given moment, you may find the ticket to the circus that has always beenin your possession." Fingerprint: 2F76 2856 776A 3E07 9F3E 452A 17D9 9B28 D75E 0A36 GnuPG http://www.gnupg.org Get Private! PGP signature
Question about $from and send-hooks
Hi, My turn to have a question. :-) Since I seem to answer questions about send-hooks, $reverse_name, my_hdr From: etc., I thought I should try to finally adapt my own .muttrc files to using "set from=" instead of "my_hdr From:". I ran into a problem though. I simply replaced each "my_hdr From:" command with the appropriate "set from=" and "set realname=" commands. But doing this doesn't seem to be equal to using "my_hdr From:" -- the from address does get changed, but the change does not take effect for the *current* new email. So in fact, the address gets changed for the next email, since the send-hook for that message isn't acting on that email either. I noticed this because I have a default send-hook that should set my address to [EMAIL PROTECTED], however one of my emails sent out had the address as [EMAIL PROTECTED] -- this is a valid address but one that I never want to use. So, should setting $from (and $realname) inside a send-hook actually change the from address or not for the current email? If it doesn't, then it can't be used as a full replacement for "my_hdr From:" (and then we again get the $reverse_name problem). I'm using Mutt 1.1.9. 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 / *** WANRING -- this signature quote is spellt wrong. ***
colors for teraterm
I've noticed that the colors that look great in an xterm on my home machine don't look so good in a teraterm window running in windows here at work. Has anyone found a good color scheme that is effective, easy on the eyes, and preferably uses a black background? jm -- Jonathon McKitrick -- [EMAIL PROTECTED] The spice must flow
Re: [CLUG] Mutt
On Fri, Mar 24, 2000 at 06:57:54AM -0600, Jason Helfman wrote: ! Erik Jarvi [EMAIL PROTECTED] [240300 06:54]: On Thu, Mar 23, 2000 at 09:30:29AM -0600, Jason Helfman wrote: Well you can use the system defaults, by using the "?" key. But I believe it is "C" to copy the message to another folder. Thanks for the info. I figured it out. "s" for save to a folder, and "C" is to copy to a folder. My only complaint with Mutt is you can't (I think) hilite the index by subject. I'd like to have the different mailing lists that I'm on have a different color. I've only been able to hilite by status. new, deleted, tagged, or flagged. I am goign to copy this message to [EMAIL PROTECTED] and see if this can be done. I am almost positive that you can do what you are speaking of. You can do anything with mutt, I have found. If what you mean is highlight messages in the index with some kind of contrasting color based on the Subject (or whatever), yes you can do it. Just add something like the following to your muttrc: color index foreground color background color Expression to match on For instance, the following will highlight in red any messages with "mutt" in the subject: color index red default "~s mutt" The following will make all new messages bold blue (kind of like some other email clients you may know :-): color index brightblue default "~N" The possibilities are virtually endless (given the possible color permutations of course.) Also, don't forget the "limit" function (normally bound to lower case L: 'l'), which can be used to only show message matching criteria similar to the expressions you can use in "color index." In fact, that is the main point: learn about the expressions that you can use for message matching, so that you can get the full highlighting capabilities. I guess that was your main problem. Be sure to read section 4.2. Patterns, of the Mutt manual to learn about this. Press F1 in Mutt, then / to search, then "4.2." This will take you right to the section I'm talking about. -- Ryan Leavengood [EMAIL PROTECTED]
A mutt-worthy macro
Now that I appear to be learning my way around mutt, I thought I should contribute the following pair of macros, suitable for folks on this list :-) send-hook . 'set attribution="On %d, %n wrote:"' send-hook mutt- 'set attribution="On %d, %n muttered:"' -- -- C^2 No windows were crashed in the making of this email. Looking for fine software and/or web pages? http://w3.trib.com/~ccurley
Re: [CLUG] Mutt
On Fri, Mar 24, 2000 at 06:57:54AM -0600, Jason Helfman wrote: My only complaint with Mutt is you can't (I think) hilite the index by subject. I'd like to have the different mailing lists that I'm on have a different color. I've only been able to hilite by status. new, deleted, tagged, or flagged. Sure you can :) color index foregorund-color backgrund-color "~s Subject" To have different mailinglists in different colors try i.e. color index fg bg "~C mutt-users" Michael
Re: mail_check and mark_old
Erik Thiele [EMAIL PROTECTED] wrote on Fri, 24 Mar 2000: i think the best item for a YAO, that would also solve the "Compressed Folders and the "N" flag" thread would be: real_check_not_only_atime it means that mutt doesn't examine the atime of the folder but instead looks inside and determines all of it's information from inside the folder. this option would fix ALL of those stupid atime related problems. This would be another option. I was talking about something else... About that *assuming* Mutt can detect properly whether there is any mail marked as "New" inside the folder, should it show the N flag in folder index or not, such as what you get when $mark_old is unset. Or only if the "New" mail is really new and not from a previous folder sync? 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 / "I'm looking for a life, to come rescue me..." -- The Corrs
Re: Mutt 1.1.9 about 3-4x slower than mutt 1.0 (was Re: [Announce] mutt-1.1.9 is out - RELEASE CANDIDATE!)
Did you disable fcntl-style locking when building Mutt? -Clint On Mar 14, Eric Boehm wrote: I have found that mutt 1.1.9 is about 4x slower reading a 7.4 MB mail file with 1451 messages in it than mutt 1.0. I tried this several times to eliminate the effects of caching. It took mutt 1.0 about 7.8 seconds to bring up the file, it took mutt 1.1.9 about 28.8 seconds to bring up the same file. I don't know if you would consider this a show stopper but it was enough for me to back out 1.1.9 and go back to 1.0.
text/english?
I just got email with an attachment type [text/english, base64, us-ascii, 3.5K] What would be an appropriate mailcap entry?
