Re: Suggestion when saving mails
* On 21 Jul 2010, Roger wrote: Since I'm always saving/moving email to $HOME/.maildir/.Spam... you would think Mutt would catch-on after the 10th email. ;-) I attach the following macros to the z key in my .muttrc macro index z s=mutt/spam\n move message to spam macro pager z s=mutt/spam\n move message to spam And then i can just z(ap) any nasty spam. Ah. Thanks Steve. Wasn't going to get around to configuring save-hook for awhile, but since you mention this, I'll likely deploy it here. ;-) I assume your goal in saving stuff you know is spam is to finely train your spam analysis engine. Consider using the spam directive with this. For example: # SpamAssassin markup catcher. spam X-Spam-Status: Yes, score=([^ ]+) SA:%1 # Add more patterns as needed for other spam engines you use. # Save known spam to spam folder for bayesian analysis. fcc-save-hook ~H . =spam # Augment this with macros to save uncaught spam and false positives. # (I use ^S as a prefix for a variety of spam-related functions.) macro index \Css save-message=spamenter message is spam macro pager \Css save-message=spamenterexit message is spam macro index \Csn save-message=notspamenter message is not spam macro pager \Csn save-message=notspamenterexit message is not spam If that's not your goal, I'm not sure why you're saving spam. :) -- -D.d...@uchicago.eduIT ServicesUniversity of Chicago
Re: color limit?
On Wed, Jul 21, 2010 at 02:02:56PM -0700, Chip Camden wrote: Quoth Chip Camden on Wednesday, 21 July 2010: I have 256 colors enabled for my urxvt, and all works well with mutt until I try to define more than 21 color specifications in .muttrc, the colors seem to get confused. Must be a table overflow or something. Should I engender a flea? Or is this already known? I tried searching the flea database without success. UPDATE: looks like the breaking point is over 16 colors -- I just didn't notice that the ones beyond the 16th were borked. FYI: You can always check your terminal and applications for 16 color support by using the 256colors2.pl color test script. (Google search for 256colors2.pl) For terminal, if you see more then 2 or 3 gradients of pink on the far right box column, it's likely 256 color support is supported. As for apps, you just need to enable the specific color within the app to see if it works. The big problem I've seen so far, when a user toggles between a 16 color and 256 color application and/or terminal. Terminals *and* applications tend to totally screw-up colors when switching between 16 and 256 color. And, there's usually no fallback color theme for applications -- ie. A user switches to a 16 color terminal and tries to run an application configured for 256 color. I'm thinking, the last issue of having no fallback method is the big issue here. And, the lack of of a fallback method theme for Applications, is likely present within terminals too? I know for one, Linux virtual consoles (framebuffer) lack 16 color support -- supposedly a kernel terminal issue. Since I do a lot of work in virtual terminals, I don't use anything 16 colors. I know VI/VIM lacks a fallback method. -- Roger http://rogerx.freeshell.org/
Notify-send doesn't work with procmail?
Hi, Every one! I try to use notify-send to send a message to my desktop when a new mail arrives, but i find notify-send dosen't work with procmail: In my procmailrc, I have: # notification :0 ic: | play /usr/share/sounds/gnome/default/alerts/drip.ogg; notify-send -i 'evolution' New Mail Arrives Only the sound could be heard, but no notifcation popped out. I can't figure out what's wrong with it. Could anyone help me? Thank you ^^ -- He Wen School of Electrical Engineering Computer Science Peking University Beijing 100871 China
Re: Notify-send doesn't work with procmail?
On Fri, Jul 23, 2010 at 12:03:26PM +0800, He Wen wrote: Hi, Every one! I try to use notify-send to send a message to my desktop when a new mail arrives, but i find notify-send dosen't work with procmail: In my procmailrc, I have: # notification :0 ic: | play /usr/share/sounds/gnome/default/alerts/drip.ogg; notify-send -i 'evolution' New Mail Arrives Only the sound could be heard, but no notifcation popped out. I can't figure out what's wrong with it. Could anyone help me? Thank you ^^ Try substituting a for the ;, or ? ie. | play /usr/share/sounds/gnome/default/alerts/drip.ogg notify-send -i Also, make sure notify-send is within your $PATH. ie: $ whereis notify-send /usr/local/bin/notify-send $ echo $PATH /bin:/usr/bin: export PATH=$PATH:/usr/local/bin But I'm sure some procmail junky will find you're error better then I!
