escape commands sometimes ignored...
I have a very strange problem... This weekend I finally got around to upgrading my very old mutt, 0.95.6i, to 1.2.5. I read README.UPGRADE, changed my lists command to subscribe, and fixed an odd little regex problem in my alternates command. It seems to be working pretty well, with one glaring exception. I have a series of macros of this form: macro generic \eE :source ~/.mutt/headers.efo\r macro generic \eW :source ~/.mutt/headers.wbrs\r ... and so on and on. The files loaded by these macros all look like: | unmy_hdr * | my_hdr Organization: WBRS 100.1 FM, Waltham MA | my_hdr X-URL: http://www.wbrs.org/ | my_hdr From: Ofer Inbar [EMAIL PROTECTED] | set status_format=-%r- %f: [EMAIL PROTECTED] ---[Msgs:%?M?%M/?%m%?n? New:%n?%?d? |Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b? |%l]---(%s%?S?/%S?)-%-(%P)--- | set signature=~/Sig/wbrs.sig Each file clears all previous my_hdr definitions, loads a header set and defines the signature file for a new role, and alters my status line so I can see which role header set is currently loaded. This worked perfectly in 0.95.6i. Now that I've upgraded to 1.2.5, though, it only works part of the time. All of these escape macros are listed when I hit ?, but if I actually try to use them, sometimes they work, and sometimes they appear to just do nothing at all. Often, if I try one and it does nothing, if I just try it again one or two times, it works. The odds of success seem to be different for each macro. For example, my esc-E macro works roughly 50% of the time, while my esc-P macro seems to work fewer than 1 out of 10 tries. I tried watching mutt's activity with truss, and I see that it does read my keystrokes. Sometimes, it opens and reads the headers file. Other times, it just doesn't. Here's the truss output when it does nothing: poll(0xEFFFC460, 1, 60) = 1 poll(0xEFFFC378, 1, 1) = 1 read(3, 1B, 1)= 1 poll(0xEFFFC460, 1, 100)= 1 poll(0xEFFFC378, 1, 1) = 1 read(3, P, 1)= 1 poll(0xEFFFC3F8, 1, 0) = 0 stat(/home/cos/Mail/mbox, 0xEFFFE620) = 0 time() = 997659834 time() = 997659834 stat(/home/cos/Mail/mbox, 0xEFFFE508) = 0 stat(/var/mail//cos, 0xEFFFE690) = 0 time() = 997659834 time() = 997659834 poll(0xEFFFC460, 1, 60) (sleeping...) Here's another attempt at loading the same header set (esc-P), that did succeed. This was with the exact same mutt process as the previous example, and the same truss process watching it: poll(0xEFFFC460, 1, 60) (sleeping...) poll(0xEFFFC460, 1, 60) = 1 poll(0xEFFFC378, 1, 1) = 1 read(3, 1B, 1)= 1 poll(0xEFFFC460, 1, 100)= 0 poll(0xEFFFC460, 1, 60) = 1 poll(0xEFFFC378, 1, 1) = 1 read(3, P, 1)= 1 open(/home/cos/.mutt/headers.poly, O_RDONLY) = 5 fstat64(5, 0xEFFFDE28) = 0 ioctl(5, TCGETA, 0xEFFFDDB4)Err#25 ENOTTY read(5, u n m y _ h d r *\n m.., 8192) = 284 read(5, 0x00236794, 8192) = 0 llseek(5, 0, SEEK_CUR) = 284 close(5)= 0 stat(/home/cos/Mail/mbox, 0xEFFFE620) = 0 time() = 997659950 time() = 997659950 time() = 997659950 ... time() = 997659950 time() = 997659950 stat(/home/cos/Mail/postponed, 0xEFFFDEB0)= 0 stat(/home/cos/Mail/postponed, 0xEFFFD6D0)= 0 time() = 997659950 time() = 997659950 write(1, 1B [ 3 4 h1B [ ? 2 5 h1B.., 99) = 99 poll(0xEFFFC460, 1, 60) = 1 poll(0xEFFFC378, 1, 1) = 1 read(3, 1B, 1)= 1 poll(0xEFFFC460, 1, 100)= 1 poll(0xEFFFC378, 1, 1) = 1 read(3, R, 1)= 1 poll(0xEFFFC3F8, 1, 0) = 0 stat(/home/cos/Mail/mbox, 0xEFFFE620) = 0 time() = 997659952 time() = 997659952 time() = 997659952 time() = 997659952 poll(0xEFFFC460, 1, 60) (sleeping...) This is on a Solaris 2.6 box, mutt built using 2.95.2 19991024. My
Re: Mutt and gpg encryption-problem
| Hi all.. | | ich have a small problem (I think) with mutt and gpg. | I'v got mutt-1.3.19 with gnupg-1.0.6 and all went fine, but when I want to | encrypt a mail, I got this: | | usage: gpg [options] --encrypt [filename] | | I seems something wrong, but i do not find this error. | | In my .muttrc I have this vor gpg- encryptions: | | set pgp_encrypt_only_command=gpg -v --batch --output - --encrypt --textmode | --armor --always-trust -- -r %r -- %f | | set pgp_encrypt_sign_command=gpg --passphrase-fd 0 -v --batch --textmode | --output - --encrypt --sign %?a?-u %a? --armor --always-trust -- | -r %r -- %f. try this: set pgp_encrypt_only_command=pgpewrap gpg -v --batch --output - --encrypt --textmode --armor --always-trust -- -r %r -- %f set pgp_encrypt_sign_command=pgpewrap gpg --passphrase-fd 0 -v --batch --output - --encrypt --sign %?a?-u %a? --armor --always-trust -- -r %r -- %f It works fine for me ... R. -- vb $factor | ps auxw | grep bobot gally gally 1846 0.0 7.3 4140 2300 ? SAug03 2:16 bobot++ vb $factor | kill -9 1846 -*- SignOff gally (EOF From client) - #linuxfr PGP signature
[SOT] scoring strategies
Not directly a technical question so Slightly OT; A wise man once said real man score their email Well poking around with scoring in mutt I would like to ask any real man what strategy do you use in scoring mail? give every incomming mail 50 points and then subtract or add points based on exclamation marks in the subject, pgp signed/encrypted or not, comming from a known address or not or give any message 100 points and then substract/add don't give any points and then add points for characteristics just curious. -- /guido Quid quid latine dictum sit, altum viditur. PGP signature
Re: Delete to Trash instead?
On Sat, Aug 11, 2001 at 12:46:25AM -0700, Justin R. Miller wrote: Thus spake Justin R. Miller ([EMAIL PROTECTED]): Been meaning to get around to an automatic trash-emptying macro though... [ nifty Python script deleted ] Perhaps I'm missing the goal, but if you just want to occasionally clean out your trash, why not let Mutt do it? Here's my (admittedly quick and dirty) trash maintenance stuff, with lots reused [i.e. stolen :-] from earlier postings to the list: ## Delete messages to the trash can rather than bit-bucket, unless ## we're in the trash folder. folder-hook . macro index d save-message~/tmp/.mail_trashentery folder-hook . macro pager d save-message~/tmp/.mail_trashentery folder-hook mail_trash macro index d delete-message folder-hook mail_trash macro pager d delete-message # When we go into to the trash folder, tag stuff greater than 30 # days old. Don't mark anything that's already flagged, though. folder-hook mail_trash push 'T~r30d!~F\n' So all one needs to do is occasionally (I probably do it weekly just to drag something back out) visit your trash folder, then before leaving, mark the tagged messages as deleted. It scares me a bit to have something other than a mail program dinking with my mailboxes... Eric -- It has long been known that one horse can run faster than another -- but which one? Differences are crucial. -- Lazarus Long Eric Peterson WB6PYK (805)370-3046 mailto:[EMAIL PROTECTED] http://www.troikanetworks.com
Re: Whatever happened to MIME?
On 2001-08-14 13:03:03 +0200, Peter Schuller wrote: What would cause mutt not to use quoted-printable MIME encoding? Check the allow_8bit setting. -- Thomas Roesslerhttp://log.does-not-exist.org/
Re: Delete to Trash instead?
Thus spake Eric Peterson ([EMAIL PROTECTED]): Perhaps I'm missing the goal, but if you just want to occasionally clean out your trash, why not let Mutt do it? My goal was two-fold: get the job done and learn Python :-) Here's my (admittedly quick and dirty) trash maintenance stuff, with lots reused [i.e. stolen :-] from earlier postings to the list: Cool, I'll have a look! So all one needs to do is occasionally (I probably do it weekly just to drag something back out) visit your trash folder, then before leaving, mark the tagged messages as deleted. Yeah, but see... there's some manual work involved. I'd rather not have to open the unnecessarily large folder over IMAP in the first place. It scares me a bit to have something other than a mail program dinking with my mailboxes... Heh, that's why the first release only touches the trash folder... :-) -Justin -- [ ] -- Justin R. Miller - [EMAIL PROTECTED] -- [ ] [ ] -- see full headers for PGP key information -- [ ] [ ] -- http://solidlinux.com/~justin/pubkey.asc -- [ ] PGP signature
mutt + abook + pgp
I've patched abook 0.4.13 a bit to make the usage of mutt's PGP features more comfortable. Perhaps this may be of some use for others as well. You can get it from http://www.uni-paderborn.de/~rsommer/abook-pgp.tgz The patch introduces three new address book properties for a person: - A flag indicating whether mails send to this recipient are to be encrypted and/or signed by default. - If encryption is activated, which key is be used for it - What the recipient does like more: PGP/MIME or old style application/pgp To make use of this, two additional Python scripts are enclosed with the patch: (1) abook2mutt.py is an extended export filter. It outputs send-hooks that activate encryption/signatures for recipients. Additionally, it can output aliases (works as abook's export filter) and color index patterns which highlight all mails send from users in your address book (effect comparable to abook's contrib/whitelist, but takes another approach) Example: - cut 1 - Name: Joe User 2 - PGP : Encrypt and sign 3 - Key ID : 0x12345678 4 - PGP/Mime: Yes E-mail addresses: 5 - [EMAIL PROTECTED] 6 - - cut ./abook2mutt.py -c cyan -a -p ~/.abook.addressbook send-hook . set pgp_autoencrypt=no send-hook . set pgp_autosign=no send-hook . set pgp_create_traditional=no alias joe Joe User [EMAIL PROTECTED] color index cyan default '~f joe@no\.where | ~e joe@no\.where' send-hook joe@no\.where set pgp_autoencrypt=yes send-hook joe@no\.where set pgp_autosign=yes pgp-hook joe@no\.where 0x12345678 (2) alias.py is a substitute for mutt's create-alias function (and for abook's contrib/mail2alias.py). In addition to extracting name and email address from the mail given on stdin, it tries to detect whether PGP is used and inserts corresponding items into abook's address book. Note that this is all quite new and hardly tested. Any comments and suggestions are welcome! Robin -- Robin Sommer* phone05251/65041 * [EMAIL PROTECTED] PGP fingerprint * 3D19 DFA8 4D49 79DA 2DFE * EAE5 D6BA 121D 7833 816E -- Fliegen lernt nur, wer aus allen Wolken faellt [HRK]
colors/mono: bold vs. bright
What is the difference between the colors' 'bright' attribute and mono's 'bold'? The Mutt manual says that 'bright' makes the color boldfaced, but it is definitely different than mono's bold, where bold makes the characters a but thicker, where 'bright' simply seems to make them brighter. Thanks. -Ken
Re: colors/mono: bold vs. bright
On Tue, Aug 14, 2001 at 01:46:00PM -0400, Ken Weingold ([EMAIL PROTECTED]) wrote: What is the difference between the colors' 'bright' attribute and mono's 'bold'? The Mutt manual says that 'bright' makes the color boldfaced, but it is definitely different than mono's bold, where bold makes the characters a but thicker, where 'bright' simply seems to make them brighter. It depends on your terminal. Some will show white as about a 50% gray and bright white as white, and similarly blue as almost navy and bright blue as royal blue. Others will show white as white, and bright white as bold white, and blue as royal blue and bright blue as bold royal blue. I go out of my way to use the latter, myself. :-) -Rich -- Rich Lafferty --+--- Montreal, Quebec, Canada | Save the Pacific Northwest Tree Octopus! http://www.lafferty.ca/|http://zapatopi.net/treeoctopus.html [EMAIL PROTECTED] ---+---
Re: colors/mono: bold vs. bright
On Tue, Aug 14, 2001 at 01:46:00PM -0400, Ken Weingold wrote: What is the difference between the colors' 'bright' attribute and mono's 'bold'? The Mutt manual says that 'bright' makes the color boldfaced, but it is definitely different than mono's bold, where bold makes the characters a but thicker, where 'bright' simply seems to make them brighter. 'bold' may be characters drawn with thicker lines and/or brighter lines (or neither). it depends on the terminal type and its configuration. mutt's only asking the terminal for 'bold' (there's no termcap/terminfo attribute for 'bright') -- Thomas E. Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
always problem with accents
hello, I wrote some weeks ago about a problem with the accents in mutt 1.3.x . Yesterday, I tried all the afternoons to understand where it comes from... without any success. In fact, when I use my mutt 1.2.5i, I haven't any problem with them. - éèçà - I tried with a lot of LC_ALL, LC_MESSAGE and so on but nothing change. I've \351 instead of é, \352 instead of è... I also tried to compile with some options like --enable-locales-fix... no change. How can is it possible ? It's only with the 1.3.x ... with the 1.2.x (i recompiled yesterday 1.2.1 for testing) and without --enable-locales-fix, I don't have the accents but with it, I've got my accents) is it a problem with my system ? if yes, what's the problem ? thanks, cu, binny -- cat: signature: No such file or directory Benjamin Michotte[EMAIL PROTECTED] °v° web : http://www.baby-linux.net _o_ homepage : http://www.baby-linux.net/binny slaktool : http://slaktool.sourceforge.net icq uin : 99745024 PGP signature
Re: escape commands sometimes ignored...
I wrote: This worked perfectly in 0.95.6i. Now that I've upgraded to 1.2.5, though, it only works part of the time. All of these escape macros are listed when I hit ?, but if I actually try to use them, sometimes they work, and sometimes they appear to just do nothing at all. Often, if I try one and it does nothing, if I just try it again one or two times, it works. The odds of success seem to be different for each macro. For example, my esc-E macro works roughly 50% of the time, while my esc-P macro seems to work fewer than 1 out of 10 tries. Someone suggested to me that it might be a timing problem, which set of a bell, so I experimented, and it definitely is. Looking at the truss output in this light, it became obvious: when it didn't work: poll(0xEFFFC460, 1, 60) = 1 poll(0xEFFFC378, 1, 1) = 1 read(3, 1B, 1)= 1 poll(0xEFFFC460, 1, 100)= 1 poll(0xEFFFC378, 1, 1) = 1 read(3, P, 1)= 1 poll(0xEFFFC3F8, 1, 0) = 0 when it did: poll(0xEFFFC460, 1, 60) = 1 poll(0xEFFFC378, 1, 1) = 1 read(3, 1B, 1)= 1 poll(0xEFFFC460, 1, 100)= 0 poll(0xEFFFC460, 1, 60) = 1 poll(0xEFFFC378, 1, 1) = 1 read(3, P, 1)= 1 open(/home/cos/.mutt/headers.poly, O_RDONLY) = 5 That first poll after ESC is read, with a timeout of 100 milliseconds, succeeds in the first example and doesn't in the second. So, this must be something that tries to guess whether I'm tying a function key that sends an escape code, or actually typing escape by hand, by looking at how quickly the next character comes. I've got mutt running on two boxes exhibiting this behavior. One of them forces a delay of about 1 second, the other requires me to wait more than a second and a half, for my escape combos to work. How did 100 milliseconds turn into 1 second? Why was the required delay so small before that I never noticed it, and so large now that it gets in the way of my typing? I guess this has become more of an slang question than a mutt question. -- Cos (Ofer Inbar) -- [EMAIL PROTECTED] [EMAIL PROTECTED] I am convinced that He [God] does not play dice. -- Albert Einstein But he [Einstein] was wrong. And in fact, anyone who has played role-playing games knows that God probably had to roll quite a few dice to come up with a character like Einstein. :-) -- Larry Wall
Re: SMTP AUTH-capable MTA
Vineet Kumar wrote: ... decision I disagree with. And seeing as that screening server has already had three significant downtimes in the past month I'd like to bypass it altogether. Before you spend a lot of time and energy downloading and compiling something of your own, make sure you check whether it will work by attempting an outgoing connection to port 25 (of any reliable smtp server). If the policy is to redirect all mail to a screening host, I'd be surprised if there wasn't a firewall rule to enforce that policy by disallowing outgoing connections to port 25. So tunnel a local port thru an SSH server listening to port 443 (https), and connect to your favourite SMTP server from there. Usually does the trick. Unless you have a really paranoid admin. btw, can't the dev team reconsider and *allow mutt to have SMTP capabilities* please pretty please /magnus Cheers, -- Vineet http://www.anti-dmca.org Unauthorized use of this .sig may constitute violation of US law. Qba\'g gernq ba zr\! |tr 'a-zA-Z' 'n-za-mN-ZA-M' Part 1.2Type: application/pgp-signature
