Re: mutt, emacs, iterm2 on OS X
On Thursday, November 7 at 11:12 AM, quoth Peter Davis: I'm using mutt 1.5.21 on OS X 10.9 in iTerm2, with emacs 24.2.1 set as my editor (with the -nw option, so emacs runs in the same window as mutt). I find when I edit a message or reply, either emacs or mutt is not restoring the terminal state properly, so the screen does not display correctly. I see partial lines that are not erased or repainted, reverse video areas that should not be, etc. I basically have to quit and restart mutt to get things right again. That sounds like you have your TERM environment variable set incorrectly for iTerm2. I'm not sure what the right TERM setting is, but if you're currently using something like vt100, you might be able to fix it by setting your TERM to xterm. You should also be able to fix it by pressing ctrl-L - that forces a terminal clear and redraw. ~Kyle -- Nip the shoots of arbitrary power in the bud, is the only maxim which can ever preserve the liberties of the people. -- John Quincy Adams pgpwT6gbADXJ6.pgp Description: PGP signature
Re: Store Mailbox directory on Dropbox
On Tuesday, August 20 at 03:24 PM, quoth Leon Waldman: Do any one have any inputs or caveats in store the Maildir folders on dropbox to sync them between different computers? I think the caveat is going to be race conditions; and given that Dropbox can be used offline, the race conditions can be quite easy to trigger. There is no inherent tracking of unique messages in Maildir folders. Imagine the relatively simple situation where you receive a new message. In location A you read it, and in location B you delete it. As long as you haven't had a full A sync followed by a full B sync BEFORE you delete that message, you can run into trouble (imagine B's dropbox client does a scheduled sync before A does, so B will wait a full refresh timeout before it will see the changes to A). Reading the email causes the underlying mail file to be renamed, which means that the delete operation on the slower (temporarily un-sync'd) host will be reversed, and your message will magically re-appear. However, since it shows back up marked as read, not only will it be easy for you to not notice, it will be easy for mutt to not notice (don't worry, mutt will notice eventually). Since Dropbox can be used offline as well as online, imagine the same thing happening where A is offline when you read the message (it queues up the delete file X, store file X.newname operations), and comes back online sometime after you deleted the message in location B. Changes to the mail directory done on A will supersede operations done on location B in unexpected ways. As another example, imagine that on location B, instead of delete the message, you reply to it. Replying causes another rename operation, which means that after a full sync, you will have two copies of that message: one marked read, and the other marked replied. So okay, maybe Maildir isn't the right storage technique, how about Mbox? This is an even bigger problem, because in situations like I just described, the entire MAILBOX will be duplicated (by Dropbox itself), because Dropbox has no real way of handling change conflicts in the internals of files (all files, to them, are binary blobs, not text blocks whose changes can be merged). The fact of the matter is that Dropbox is not designed for frequently changing data, or for handling even slightly-overlapping synchronization issues ESPECIALLY of filesystem meta-data, such as file names and directories, which Maildir relies on for correct operation. In terms of how it technically functions, Dropbox can be better thought of as an on-line backup system: synchronization operations are not instantaneous, and has only rudimentary conflict resolution mechanisms. On the other hand, such synchronization issues (and worse) are EXACTLY what IMAP was designed to handle. ~Kyle -- As far as the laws of mathematics refer to reality, they are not certain, and as far as they are certain, they do not refer to reality. -- Albert Einstein
Re: Long urls - update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, April 1 at 07:30 PM, quoth Luis Mochan: I tried now your fix, and it didn't work for me; my browser doesn't find the resulting pages when the url has ampersands that are converted to %26 (probably because the % itself is further encoded as %25 before been sent to the server by the browser (?)) What?!? That's *really* strange. Is extract_url.pl double-encoding the percent, or is some script in between doing that? I don't know much about shell programming, but I found that /etc/urlhandler/url_handler.sh is a shell script that obtains its url doing '$url=$1'. Ahh, indeed, that could cause a problem. Variables are substituted simply, in an as if typed manner. Take this simple example: # foo=bar # echo $foo bar Fairly straightforward. BUT, if we use an ampersand: # foo=barbaz [1] 20113 baz: command not found [1]+ Donefoo=bar # echo $foo # You see, the ampersand did two things there: first, it created a sub-shell to execute 'foo=bar' in the background, and then attempted to execute 'baz' as if it were a command. What that shell script *should* have done is quote the argument, like this: url=$1 To return to my example: # foo=barbaz # echo $foo barbaz I don't understand why echo by itself yields the correct result (above) while echo through a bash script yields the truncated result. It's because of the incorrectly quoted variable assignment, which is cutting off the URL at the ampersand. ~Kyle - -- Always forgive your enemies; nothing annoys them so much. -- Oscar Wilde -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJRWvELAAoJECuveozR/AWeW+QP/0a/uhmbPio/web5Fu4zbcS8 VFj5/FJR1ql/0Wfrs9eL/JPb06cyvGm8M2xrLq/eVwuvMc4gPzIKwtqEwutanVh8 1JvUWCYFlQxqwYW5H4EKT9y6zCkqgJenisXdD0T9EbWO13fleDnlBXki5o63WPyb GzPA11TuHOXIq6cxcMWfx6tt8DgtkIj36Jk5bpcS0/mE1s+nthsTCGILhM3PVU5k ejLlFUFY1L7YUePqYpqhyCA/akMOvpcbMPdxw701WWMcr1UGi9Netu/otpZTPrz0 XiS2XvdzggCMwIRBJU5buhT9HpOOjmH2qPXIr0WDW3S6MKquAvm8agHvtkgXEqNI 0vGZ/KqKoNUBUJUgjOaFW9zZFvUHrYhzfsdFHjspglVbPMreqw3DggZErUa0Eifm q1j0dYsOZ/xmmp3iFO38iYfc5NBTJcXuBZIDS+scRJw4ZFhfedEBJcskEX7Jcxnu l9bwwa+nIxEidUou87EcKslzDB/lux0ihdsZzSRQNmpV82FW59kCqkcY0brLJoeh GgJgtHk4tFe2Vw4cN4uAw8EpvxnmAP/lDCmTwUVcdKbvy+p8f49vvElpUC+eWnq/ vQuynegYN/GQyj0CQJxU25m35UhKG7X+XzYOKojmnxG9E9O94YANZ5NBxRUuyR8K ntttDNCaEt6oARXNCp2H =MZB4 -END PGP SIGNATURE-
Re: Long urls - update
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sunday, March 31 at 11:16 PM, quoth Luis Mochan:
I'm a perl guy, yet that's non-trivial here. Thx. :-)
You're welcome. I don't know if there are other characters that appear
in an url and need to be escaped for the shell ([;]?); they could
easily be accomodated by modifying 'wlmsanitize'. The page for the
extract_url project (http://www.memoryhole.net/~kyle/extract_url/)
mentions that the program already transforms characters dangerous to
the shell, but then it only mentions explicitly single quotes and
dollar signs.
Hello,
I'm the author of extract_url.pl, so perhaps I can shed some light
here.
The *correct* place to fix the issue of escaping (or otherwise
sanitizing) ampersands is in the sanitizeuri function (line 208). The
current version of extract_url.pl uses this:
sub sanitizeuri {
my($uri) = @_;
$uri =~
s/([^a-zA-Z0-9_.!*()\@:=\?\/%~+-])/sprintf(%%%X,ord($1))/egs;
return $uri;
}
Essentially, what that does is explicitly whitelists the characters
a-z, A-Z, 0-9, _, ., !, *, (, ), @, , :, =, ?, /, %, ~, +, and - and
turns *anything* else into the percent-encoded equivalent (e.g. %26),
which should be correctly decoded by any standards-compliant
URL-decoder (see RFC 3986). If you want to eliminate ampersands from
the characters allowed in a URL, simply remove the ampersand from that
list. It's as simple as that. I think Luis's patch is a little overly
complicated, and I think the policy of using backslashes to escape
such characters (instead of percent-encoding) is dangerous, given that
it's more likely to be stripped off by intervening scripts. I don't
want future bug reports that say my setup strips backslashes, so can
you create an option that will triple-backslash the $ character?. :)
(Followed, the next week, by a request for quadruple-backslashing, of
course!)
I've personally never had a problem with ampersands, and I'm not sure
why some people do. Extract_url.pl constructs system commands like so:
/path/to/handler 'http://url.with/anampersand'
... which should be perfectly safe and work just fine (and does for
me). I suspect the problem stems from using other wrapper script (e.g.
/etc/urlhandler/urlhandler.sh). I bet the that wrapper script is not
properly quoting its first argument.
In any event, percent-encoding, by modifying that one line, is
probably the right way to go.
~Kyle
- --
The purpose of computing is insight, not numbers.
-- Richard W. Hamming
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!
iQIcBAEBCAAGBQJRWfZoAAoJECuveozR/AWeH4oQAKRu3Jg1n7KVXT0q0DogCoE+
Ms/gH8EKUwN8KtWhg3wNDgCIh0GXaNykywQPshbM59qP6U8uFofavngGfQv1YCEV
vM94vsNLY8AOfdv/6tRkQFKDi5RadKRfjcJYqHzr11LSJ2e+Ns+i4gx+0jkSCe9/
2FIWjZjsmH5WUHNktAzC0dCGxqBb6vO4Oc7JRuLpaof6jLWLMvJBgM9HVCf67RrX
aEALusVBqSZKBlr+UBk1lF0obEbijGX+hJuHg8udaOVgCsljpzDcOku5my2V13Pu
LZ1ltKv4/y+Z2tofyjDpXNnsomENYfWb6LGfQgystY8xvSv94TJLOlM7oaSsJmJq
hPdP0T5rJ3lryaadc3I5p7GUI5zqUk0T6e8FM8vM1ZUXS8NyN0ZN7NeSSX/5mAMS
OCCkxxXSaLnbr2HUetjYknnVB4W6WKR2eEjgP+VHMtemRb9W6UVgjO1nnoqm4WOM
zRPDIk6VvJgTPUuIso5oq2JoYC0wowmXJBz31UL6y98p1zcPcZVPFDxtf/9p6pUV
/VTDD4bPZCSaQiwhr2abUd4OxOd5bpYx994Z7L5oCQezGDXhEt6XgeEdGBdT21bt
z8FKnqGNOp0EO9C2kX9fPGbRITXK32urUEqeuuB0AHDp3D7VyZ3KRiXIeFFRWvMj
kQzyzKnbnm1uHloyk89l
=n1YG
-END PGP SIGNATURE-
Re: select wrapped lines / click long url / bug 3453
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tuesday, October 23 at 05:39 PM, quoth Alex Efros: I know about urlview, but it both doesn't show long urls well and more complicated to use than just copypaste (with disabled markers). Long URLs are harder to handle than a terminal can deal with, because of email encoding issues. Terminals can deal well with *some* long URLs, but not all. I use the urlview replacement that I wrote: extract_url.pl (http://www.memoryhole.net/~kyle/extract_url/). The motivation for my script in the first place was dealing with long URLs, so it does that pretty well. The specific problem I was addressing is that sometimes long URLs are encoded in email in a somewhat unusual way, with removeable spaces added in to wrap the URL to 80 characters, which means you need something that actually understands MIME-encoding to correctly glue it all back together. If you take a look at the screenshots, it shows what happens when you select a really long URL (it displays the whole thing for you). Whether it's more complicated than copypaste is a matter of opinion; I like it because it means my fingers don't have to leave the keyboard AND it works with both HTML-email and standard email AND it deals with these wrapped URLs in a way that doesn't force me to go back and forth between browser and terminal copying and pasting several times. ~Kyle - -- Coffee renders many foolish people temporarily capable of wise actions. -- Montesquieu -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJQmAQpAAoJECuveozR/AWeA1oP+wRRigC89x1WFPUfmZ7nhZ/o PJEzfGaLFHE6YX1gOl7qYXJ1inAmffRHiFHMgYkeFhvRCLZacBvZFBiApZcjlCWL m9O6EaKSSMGFbViGakbv+cISpToi5bgAB7S0A5ie5hmne3j/dWkYAs4b3y0Ic2W/ n1dkfwUdSxb254vGra/4ah7fxbcWbC7wvPJPRthjscAsFiN1qBSyHbhMoa25hhO0 fTfu2DYnPR2dkZKtr0c3hVOgn0UvaVSEb0deFaS+xNogXpIE7vSBuHBSp2fYmRFt vpEoeupNITSzF3xhb+k+j2959LO3ojO4l03fMGjBOZUlznJPH/NGUSaWF+1wqWND JX8Py/gLDPDh5teElauIIZwBCCaLpXks/k32xmN+UdWMocmSfJ2dFLfBUuBA+0sh ptWgTZrjqq2jz0dFxEY4rF8niLAAZEATQLHLoHMvkVz6pENd/vTFraOyITSg87Xq qpzEBSqeL0lUuvvtVbaSy8Vu7OxFOAvzVhGMXV/NK/A3+RnD+9A05tjKA5HDrt87 NoInQAffVX9TfWUR1ixbmBvfUcEYc6Bspkbj9+08Qql7+7VEbjdhHUYfTNDUS89W n1ImQMc0gSiejdDsKoVyuYC6wMf94nAEwO7Mjk+Exsy7wQQUSkQyBobAQYisj5BH tBNo2TnqjqrqOSKL9daP =M8Q9 -END PGP SIGNATURE-
Re: Multi-boot and Mutt
On Sunday, July 29 at 03:03 AM, quoth Jack M: One can also use backtics in a muttrc to surround a snippet of shell script, thereby avoiding the need for keeping another shell script file laying round (in three places, no less): source `some-conditional-here` You can do even better than that; the power of inline backticks is significant. For example: set from=`[ $HOST == 'unix' ] echo -n unix || echo /n win32`@here.com I use the same muttrc on a variety of OS's (MacOSX and Linux, mostly, but also various BSDs and Solaris), and use exactly this kind of trick to get them all working right. ~Kyle -- Arguing with a fool proves there are two. -- Doris M. Smith
Re: extract_url is not found in /home/user/bin
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thursday, July 21 at 08:39 PM, quoth Martin: Hi, I've just tried extract_url and it seems really good. After I select an URL to view, mutt (in the terminal window) still wants me to press a key to go back to mutt. I would like it to behave, that once i select an URL to view, I am immediatelly back in mutt, without pressing any key. Any idea how to do that? Sounds like you have $wait_key set in your muttrc (it's set by default). Try adding the following to your muttrc: set wait_key=no ~Kyle - -- Almost everything about a human creature is ridiculous, except its ability to suffer bravely and die gallantly for whatever it loves and believes in. The validity of that belief, the appropriateness of that love, is irrelevant; it is the bravery and the gallantry that count. -- Robert A. Heinlein, Job: A Comedy of Justice -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJONr//AAoJECuveozR/AWeMJ8QAJFtwWCW40JJLZXx2e3rwFbv XqAnenP5hoq9+rcSPrizC2mtinMiuGVn34oBilQtJ+Fr0AVQXn9ne8V2Khv4SKRz ztRhFJZ07HXHVA2H6dHB/xzbTlR//ZehSsd0o/5ItaqDgSHxpTix+1Om3feOxxnG acl4Nuamgox3uda7n84Q/MW68+NdGwcvwl4ztGcSf6io96RThGN/2gfdjAXkbgQB z6gem+GQ7L3UF7BfhufqSYWGuCgKbCHrrgEQN72eFnUwMI23AYSb0eevc+qoEm9i 4BMkZYxW05/FnuwWaGKWSNJnFyb2yFHrEPYwSAVxkSDudPQgeeBSTTv4sRuSHNjd RaUMwNkvTcp69Z7GtVYY++UoTMsNGHCuEDS5XzkUIx/X0IUDBDjxR2n7i5YEn6rU GGfzmUOtPAM+9BJKH6vFXjDga/j0AidUIuTZvyKdmMXo5ecGRbOqTWqusugsEWkC aQ/kXBOWIC7dyEPkk8exM6hfK7ZUWeq1hiUp1OvSPzboeSTm94QQgfuXRXjBgniy MK+fYrvD8eRPXix5mIB9c7uxx6Kw0KSHM+plWZNi+kmC3eFdRJrC8UIXcwBS/Cbx d4HUaTRf88VVNtsJf6I/PklZCoDX5oIJbimwqQoAtV6nIltnCqrOcan5jTh54CC9 8gcequlvWYIVCnBeGNHw =7UIx -END PGP SIGNATURE-
Re: how to visit link hide in email
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thursday, May 26 at 09:08 AM, quoth chris M. sprite: I find that some link hide in words , for example: click this link[1] , here, link[1] is a link. but I can not click it or do other things. so, how to display this link ? There's lots of ways. The one I prefer is to use extract_url (http://www.memoryhole.net/~kyle/extract_url/). ~Kyle - -- Not choice, but habit rules the unreflecting herd. -- William Wordsworth -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJN3egYAAoJECuveozR/AWeFfYP/3n8huoL66PIytO1oKcRB3FN wdchogptylJGgU8CcdWLu6uZrz4D1eRJ4SrZkKIBzywcMmKaB2cHsJDmMo7TFX9i O6rPhgPb2fcVNi+8HK13USUEtjq/W5PJ0Bgq6m6uPDNHWqqfV+fQgrYQzhedIuRu VxDAXbBly7S1ZcrTj9j+iYASpsYJ6EJOmSEihlN5BdseX4pQaSFDuDPHpHg9YBez RDZdl5fddoakziAg8luyKuSRLZP/BWAsu4/WayIH/a6eq+HxXIXeiZqClQg0vpUd B/9sluH/hU9a20r1wKwgje/y3Z3cbag4AZQ0MY8lCqObsM/fLIL8ZRYf2Wi8xRAH hbHvq+/klerGkBCqvp463gZPqPjqL5Nm1c8xz5ikLw/iOq3sBERdiK0hVgnx53XZ N22NHPdaRi0wae6V6VeXbLERIYYhD2tsU1en1PcAeoJEPFatjpvPw72cFWhOzzm3 LmOeaEnWB8rZ6zhqR51FzdJMuqzMjIQmlnmK0lcBGl6H+ls0LKNi2G3AFLDBMAMz s+hIXWxqBOgbmOO5HKasY6oz2VIyxrVnwXW4MAQQqYuT05KU4uoapE9TWZf5ObzM f52YRIIXse0+sv9aa0MH7/LMP+nzXIimsvxUZdkyrkVOzXb2kdSl1nJSI6EichRO uAsKAZAsCD/GP0+BCouR =Wp4K -END PGP SIGNATURE-
Re: How to match a whole word?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sunday, December 19 at 04:07 AM, quoth Yue Wu: I tried to match a whole word 'tex' in mail body like: color index brightgreen default '~b tex' but it will also match other words consisting with tex. I tried with \tex\ and \btex\b but failed, my question is: how to match a whole word in mutt world? Which regex library are you using? When you run `mutt -v`, do you see +HAVE_REGCOMP and +USE_GNU_REGEX or -HAVE_REGCOMP and/or - -USE_GNU_REGEX? ~Kyle - -- No one loves armed missionaries. -- Maximilien Robespierre -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJNDiBuAAoJECuveozR/AWeliMQAKTnbIe4b+s2OPN7EJ/EJ7kI z7z3GTvYt5zxGCzsl9jiLf9vhiL33XXgr1C+ixynkLW5eZhkBfQiwsvC93LXfQF0 F8jOR5pNZD1i/ZgoHYhMBrnqtOzBTS4rL5gikTlTzl1us6hDUFdsmia5cHujkS31 JSyYkUiYzt76POoh9CuZdFc2vakHyTSwzfLNGdYX7pQgIqgH0KDYC4RS+Li3K7Cf f8tUFTHnrvHjbg7OcbYEvcVNRSegN6w+DxeIudP0qHCaxHGnxpd+Cg1f0xYkG7Hp Y02UMIuK+2WJBufBDf+pd3FmCk83WzQ0sInwgOWw+OO37VTIiDy0qNcCbCl808J4 lc6AD3opfDVTX5drT0YtV/CLGSVVnsee1aiNZhzjd0tCx7/2IArJs6w66IJ+4W/h 2NTT92CIG0CHpO+kZhdp8FbQaB2TSkSa1nf71inPv8dgVs5DliUlCZBfT6BENTNB nuNskVnUfJqBhx+XLEl4wXQEHpijmy4GWciIWu0lScKrXRNh7UpZF/Xf/J4UNQLC XkQP5qgOlrXCQrDI6elIMQS/l+5K65HyIk3LUhcP8t9stnP5NN9thW3efUiNZy/l UAVrwuliJDudyJVPeabW9Rf6E4OgNhGsgTiUKMRYfPYDlUBKw18px+ro+CHT6wlL yYwF6OyI+r9swqM0Ll0x =nPLZ -END PGP SIGNATURE-
Re: How to match a whole word?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, December 20 at 12:39 AM, quoth Yue Wu: Which regex library are you using? When you run `mutt -v`, do you see +HAVE_REGCOMP and +USE_GNU_REGEX or -HAVE_REGCOMP and/or -USE_GNU_REGEX? +HAVE_REGCOMP -USE_GNU_REGEX According to the manual (http://www.mutt.org/doc/manual/manual-4.html) You can only use things like \ and \ if you're using the GNU regex package. It doesn't look like native mutt regex's can be relied on for such things. ~Kyle - -- A deep unwavering belief is a sure sign that you're missing something. -- Unknown -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJNDjiSAAoJECuveozR/AWe2yEQAJmQyeoPRdqsU0DZzf5+cxXp +t6QEl0bfBMon4M7ZZUCHV1AfkVMzx0zvGo9zOO6pUh1i4K30OFDssEWs6drMUOu /6mFA/HKp5z21NYxIP3/4b+sO3WEJWOBs5NSsNOcbMseW217Zma/LHbFK/ezqHPU 6nYb2lEnx1/T+S1e6Ah76PJM0+9GB9oeM4Gpo8WXORSX+rFTa3BgzsMne2jl3nhG nGxwfGmzBeDepZbQPXUwjhgT7Wqm9S0rslmA0aI7rwyfkmSTNgE18SNCfA6mUqKQ YcuL9u8NBUGkgLl/LUfef5LiYuvZN6JD1ect58Mre/JvFXJ/800FOG+u6ev+43+6 2GgXmmB8+kN9Kmvez+5Qy9noTC3Dru84mDRSniCd4KjMoU18mEKYt+ffs/X8riTp UD6gsWnxjglDghcwjLMf2KnmAdNjBJKJJ330MuwId4N3aiRe/iK9POt4ufGIrJhL yOjDbEafrSN1L4q47peWLCkwvXJu/m7CYGeyulY5adX/oEcmx6GkWzyLKeCYhj/z DJZRPscztUCBERWBl3+gJnazu8vcmsB0jomwYaGS9mnbGKqrwLuqRqZwAR/CYUBR cs+UfaOnF53hp47FLTwiv84ceXKCRVCLwc1pNvnlc8/PRw8Ix2KxG7j/98nskQef dm0NAR4p1XdcvjLwj0bI =UALM -END PGP SIGNATURE-
Re: can't config mutt to use gpg2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sunday, December 19 at 07:30 PM, quoth Will Fiveash: Recently I started using gpg2 and the gpg-agent to reduce the number of times I enter my gpg password. This is working in general but I can't seem to get mutt to call gpg2 even though I've replaced all instances of /usr/local/bin/gpg with /usr/local/bin/gpg2 in my ~/.muttrc_gpg-1.5 config file which is being sourced by ~/.muttrc. Any thoughts as to what is going on? What error messages have you been getting? ~Kyle - -- Coffee is the common man's gold, and like gold, it brings to every person the feeling of luxury and nobility. -- Sheik Abd-al-Kadir -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJNDsOaAAoJECuveozR/AWeZLEP/3oBgFPpA8EEA4IRqKtnK5Xy dbhbXRPOlo65CqWXowa0u8vRk6FgUb1at8QDnugEAcXTuSRW4O1QcILLob3Im/KL GVPFc+9oKDwLugFO5sAuXo1h+t7/SERklbLnbPl3TFga+tNBXr+4xwoxAUsoRhza uqgvoM9vl8rRB4scgf0VdHW0plNV9mC9q+PeJhOIMVJDRiWrl8XygKoIWhC6/sMY UUi6AkXDnkowvn9C8N8LEqxZMPSU1qLCTWmorhDC+Arw6+Lm0XdB9XWEEVOegXPx bY8Qh0ay74rqpTjKX0oGT0tU+LGLe8KnK4UDqoKlA9aWSrg1oVlG6K7S+0BoAO+p C2VciORP5U3cIm1mnCMX/jP10m3cNIFx2qdeLaNY+sourThg+ZvMkQ7G/5z8F87g Dvt29ffWOxOKiFYn5AWMLbT2TNYlaMblHtk70AXAvjEa21d2ETjmA2EEahwCXvTI lCZLDaA36QtMlw70++YyLkkr3pNrXNU7fjvZWRHzaFdM2tObC71RzLmgeNauxdwh 4cqGgmqdxlwfU/0Mzpz1pnj3slUvGhfSaxftwOTfASewvPL4amPs17s98RwD77bo UDslzwVsQzsfueZCo/TTdObPI7wD0YLzYWvXWmQjR7eifC6cf91kNVGLGmzT4Xbl Xh2STXatTSOKB+pURhXy =L269 -END PGP SIGNATURE-
Re: can't config mutt to use gpg2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sunday, December 19 at 09:21 PM, quoth Will Fiveash: On Sun, Dec 19, 2010 at 07:46:50PM -0700, Kyle Wheeler wrote: On Sunday, December 19 at 07:30 PM, quoth Will Fiveash: Recently I started using gpg2 and the gpg-agent to reduce the number of times I enter my gpg password. This is working in general but I can't seem to get mutt to call gpg2 even though I've replaced all instances of /usr/local/bin/gpg with /usr/local/bin/gpg2 in my ~/.muttrc_gpg-1.5 config file which is being sourced by ~/.muttrc. Any thoughts as to what is going on? What error messages have you been getting? Sorry, I should have been more clear; mutt continues to run gpg instead of gpg2 thus the gpg-agent isn't being used. Who said you had to use gpg2 in order to use gpg-agent? I've used gpg-agent with gpg 1.4.x for years; all you have to do is add 'use-agent' to your gpg.conf. I was going to ask how you know gpg2 isn't being used, but... Anyway, out of curiosity, why worry about it? As far as I know, there's no real benefit to using gpg2; the only difference is that it supports building against an external gnupglib library as opposed to being self-contained. All the encryption methods are the same, and gpg v1 has undergone more rigorous testing by the security community. Is there something you're trying to accomplish in particular? Maybe my information about gpg2 is outdated... ~Kyle - -- A fanatic is one who can't change his mind and won't change the subject. -- Winston Churchill, July 5, 1954 -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJNDtueAAoJECuveozR/AWe2VAP+QFvoiGfS7T3QlUkLENWUqvu 1Fvnz2S7nzVGzW7FOqStFCFOPEa8nfPbp+Fp+yC05v3JQfiNC1eyt2jgRtRCYpGt HW1KU1abRGu/HcCmyjWP/LJ6N2OoS/oJCOJ1CAQ3txHBDeiroNQiJ/PP2kDBuRQJ +P9Xo4c1s478hq/tC9l3muBkdsHDM2L/FJWL45oa9anUENODD50AKweUqjqHnMq0 frhXezBx8qsBpW2j7NV8iRWgRRyeTs6KwFcdAtuTy39h34NQa5Fbbvy2eeS/DVi0 NDwDF/i/sEWIjFRB9YronZ3dzO9GfCKevLDJ5ZGvmYbZhXDzCHJ5b5wpCBilU6nS 8TbRKfGSfvgzxs1ZLj8NH48fK0kH0Q+vVez6eWcsnikOrrMyJc5fDvQRpAsuJmzs uZ1obNGmA8M8nB06ZbGjIEH7C7aL78wlOB4jjUOC+s2ZHOIAoeKeBswyy+2wmBLW Igp8g2/yGr7bPOPEBMIpT6S/8TFhdNMPEyXiyQ70Dohq3cGtPOOmiEoVmnNc99Fk MgJOpI78gTOzw/MsEozgzvv0vK/EpNDjnRDKZSWqxYWDmS1jov+X7i2Ln8UPV6mx JSz2jJXXl5YNxrZeB7/W4UT8OxUNXnJHqTW13bHMWxmKaNyJNdc8kiNK7m7cl9sL 7dTxN9l3PgWbXhAQJAw7 =FZnn -END PGP SIGNATURE-
Re: Mail-Followup-To and friends
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Saturday, October 23 at 05:45 PM, quoth Mike Hollis: The only problem with this config is I have to use List-Reply for some mail and not for others. I had this problem (or something similar), and I used hooks to fix it for all intents and purposes. With the following hooks, I just use 'r' to reply to any and all messages, and mutt will almost always do the right thing: # make replying to the list something I don't have to think about folder-hook . 'bind index l list-reply; bind index r reply' folder-hook INBOX.Subscribed'bind index r list-reply; bind index l reply' folder-hook INBOX.Organizations 'bind index r list-reply; bind index l reply' message-hook .'bind pager l list-reply; bind pager r reply' message-hook ~l 'bind pager r list-reply; bind pager l reply' In essence, this swaps r and l back and forth in terms of what they do. The first three hooks handle index behavior, the last two hooks handle what happens when I'm viewing a message (and function independently of the first three hooks, so list messages can be in any folder). For messages that match the ~l pattern (i.e. lists I am subscribed to or have otherwise defined as mailing lists), r is a list-reply, otherwise, it's a normal reply. Maybe this will help you. ~Kyle - -- I do not feel obliged to believe that the same God who has endowed us with sense, reason, and intellect has intended us to forgo their use. -- Gallileo -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJMxcuxAAoJECuveozR/AWeB6kP/A5ULros+1pI0e1LzMAlwK2y 0MpMOhAHySU9AVS/GsioyfeyH71QISsL2d2Bl24sYw/41dgTa1YEtlIcsDcDXKuT bcyV//VNkVgY69yRqCN0f30IlpHPWpvkwptWhk+DbQ2PAurUFdu6NfU+C1xqSiMM 8c0nvKbq5r7FE4IyZnWKggXbADMTgC5FYZ83U1+eyVarqVm3Lr7mmlk95RweKXAM tkbf5kv5u2qOHsGmJTYjvmt+Yd2C4uKDPSbdmPZKkgmZOk9A3/aoBn7yJPboxGvY 1lroUbT1Uy6261+S9K1Re1DRItLCLX453TDgfYrhI2ZpkIYit/WtRZRdPga+sDKS Bjys+u7LC12Rfe2JwzOO3HZ7kbpDCYkMuSd4AJi7tYJZH1tevl8FK6gpesBZ5IcR 2/3Nu1v32rRRRkeRl8y/bZy5eMkAREgTpL2sK9VF7vx7bCoWJnRWqzhJA8l8pfna Ci2UXolPrGoh2xcK5G91AeP08hst6qlpI2ZoG2ThmJ6X3hRJtOQL2FUB7iHjRxqT RCL3dxsKTrSrDowwpE6jwqY3oPGtacmNwE6htkboD/Fvxdks+uZ7EN5UrUrVgTrU 00i61Ltb7T8evUtY3C0mqX92OL1SQpYpCFOUWNLHvsXRRFYB4iKU9pQ+gq4NA40l Sb5qAsbgkiLil6cUIhA9 =Ot/w -END PGP SIGNATURE-
Re: Tree view messed up
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thursday, October 7 at 01:58 PM, quoth the.real.ka...@gmail.com: Hello list, I have a short question regarding tree view in mutt. I use the following configuration in my muttrc: set sort=threads set strict_threads=yes set sort_browser=reverse-date set sort_aux=date-sent That's your entire muttrc? And this ends with a view that is somehow broken, I mean the arrows are not underneath each other. An little screenshot can be seen here in [0], I hope this makes clear what I mean. This is certainly due to the different length of the sender. Is there any way to fix this? It looks like your $index_format setting is either incorrectly limiting your sender lengths OR your sender's names have characters in them that mutt is having trouble getting a good length of (e.g. characters that occupy two columns). ~Kyle - -- Holding on to anger, resentment and hurt only gives you tense muscles, a headache and a sore jaw from clenching your teeth. Forgiveness gives you back the laughter and the lightness in your life. -- Joan Lunden -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJMrbjMAAoJECuveozR/AWejo0P/0oU9x7ieisaqyAh4gqa6VTK oB/yOe1WPv8EXwgbUHSjHjmhLZrJGB4iUMAvjt3csn3f77IsnmZ5mc7cSGEe7Aki OJ5MHVHBPX8vUaZ8alUAnud6PoMRAtGf0A0otjy7h76zMNGjGbXDgtUgkdrxcR8X 9gUGEZ9YfmWJqHMVnDX4ozW7j94h/0umqrtlFB0RdE+BcfSUfYihvfVG/c31fsXR HYdRHbBiwbhHQI1uOw+Xid3FFuX0wcwCJY2mA7urvDro97Dp2Skh4ZiFk+PtGEVD KY6lUEme/uv3ksEbY2e/kkN2dC7KSs0wehrs1Npw5SZM3er708mWHQcoZK+1XSLN FDsZh77XLUspjg+6SaJ8AJ0v7oivWu+Oux3eCVlD/fSNVB6ihGcIJf4iyn4yUjoc 6w3AZ5ax2JiDX9B9P34XKV1FfUYWmKaQvlMsPIDFSu0pZOizu1xLh8pT3mvNQlwf YfnLG9qfTwqGnmhikOsCd/sXUy71fqkHtlc+NHzKL1zvWqTxR86vh+nVKg/InS7W 8L9Yx2Kwi1w53DQBiH74oW8876NYsxl8WNt0qaSfQo3b+GM8R4jlO05hC6TWwHbo 1LUP52czHwhCQ1n1E+XxtSsk934V5U4uercBOYCUH3dO3kgKEptrUuFv9ZHXktDR OO8QulH07Ckrh4OJBaKG =SgOw -END PGP SIGNATURE-
Re: setting mutt to charset UTF-8 ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, October 6 at 03:48 PM, quoth Matthias Apitz: It seems I have opened now the Pandora's box :-) Indeed! But at some point, it'll Just Work (tm). What combination of terminal and editor should be used now? When I'm receiving an ISO-8859-1 message with, for example, the Spanish char á (0xe1 in ISO) and I do a reply then: with xterm (ISO-8859-1) and 'vim' the á is correctly presented as á with urxvt (UTF-8) and 'vim' the á is presented as á Why is this? It's because vim isn't *told* what character set the input file will be; it has to guess. Mutt is handing it a UTF-8 file (because mutt converts mail messages into whatever the local terminal character set is before handing it to any other program (such as vim), for obvious reasons). In UTF-8, the á character is represented as a two-byte character: 0xc3 0xa1. However, your vim is assuming that input files are in ISO-8859-1, and both of those bytes are valid ISO-8859-1 characters (this is the fundamentally impossible problem of determining character set from unidentified byte streams). As you might imagine, 0xc3 is Â, and 0xa1 is ¡. This is what I have in my vimrc to handle this: if has(multi_byte) set encoding=utf-8 if $LANG !~ '\(UTF\|utf\)-\?8' $LC_CTYPE !~ '\(UTF\|utf\)-\?8' Note that this only works if your shell GUARANTEES that either LANG or LC_CTYPE will be set correctly (as mine does). If not, it would be useful to do more thorough terminal detection here... but you really should make sure that LANG and/or LC_CTYPE is set correctly. set termencoding=latin1 endif endif ~Kyle - -- Morality, like art, means drawing a line someplace. -- Oscar Wilde -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJMrIUBAAoJECuveozR/AWeoZoQAIciEQffoLoECthEB2h7lVGg Lk9+siJSSZeTQO47hQglUw+wMGdgBRqisH1mEAiztJcObwaD5zXVgbvEHvRxsMPW og8x0+h2yL+Tz5PxAwBtfqCwB2sWdddkX/mfcfs45l4yfP2jW60oK1W0t5N1e4fO TXCCGAckPy1pTygPuUKVU8dhJR577J/Hki7RBneihY3T0PfKzkLhyOGsEEVZCKkR 9DV6Uvdlu45yLVhomUr/puhruUpi/vKfxr4BwzXsZ9aEPw98zkthDn8fATmdXH2A +otONaMQglnd+K61ic3DrulpBTOB0QDwSvvVJrv38NKgz7tGxngQppvR6TOcnoSD Qn7dahWTpP4s0IxrMbmEhMNr3MNf+Jg5dWMIfKOxAERRgRRYQ2ixQIbFIpcPaH4C fw0drbshOdXDMbZrkLkTO6Vf7sNkMxaVo+f1HAZ/TWsfcZz9pWhPmAqeVv6Azxk7 N/2/kJWU7+k8K6DbnMcfL8P3sBfTaarfkuWPzQoU69Mny+NSAtFU30DeNkAqieNp 4uqSwh/U54HtvMtQ0dtHgpRFGIEw1xLQBUGznTBfpcy5wYOUnXQBqlswQjkoOl9v pJ9OGL2+1qEJRTJQc1NS8rNlkM0AqV/qu3WnpOZOkjora8dNELkSQtaAbEWsDn3r lAnbR1IyjwSGvqlHJLfx =skjq -END PGP SIGNATURE-
Re: setting mutt to charset UTF-8 ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, October 6 at 04:31 PM, quoth Matthias Apitz: It's because vim isn't *told* what character set the input file will be; it has to guess. Mutt is handing it a UTF-8 file (because mutt converts mail messages into whatever the local terminal character set is before handing it to any other program (such as vim), for obvious reasons). In UTF-8, the á character is represented as a two-byte character: 0xc3 0xa1. However, your vim is assuming that input files are in ISO-8859-1, and both of those bytes are valid ISO-8859-1 characters (this is the fundamentally impossible problem of determining character set from unidentified byte streams). As you might imagine, 0xc3 is Â, and 0xa1 is ¡. ... It is converted *before* it is stored into the temp file for 'vim'; I've checked this with truss(1) what mutt hands over to vim (see the marked bytes): Well, of course it is. When mutt reads an email message, it reads it into it's own local memory, transforms it into a form that is convenient to think about (in this case, utf-8), and uses that to display to the terminal. Thus, it's pretty obvious why mutt would use that same source to write out files for vim. In other words, the file is written in utf-8 characters; it is not written in latin1 characters and then converted. But this is, I think, an irrelevant detail. The real point of the matter is that the file is in UTF-8 encoding by the time vim gets it. g...@current:~ env | egrep 'LANG|LC_' LANG=es_ES.UTF-8 Presumably, that's a valid LANG on your system. Just for giggles, make sure. Run locale -a | grep en_ES ~Kyle - -- A great many people think they are thinking when they are actually rearranging their prejudices. -- William James -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJMrI0mAAoJECuveozR/AWet3kP/2ryZiNE75zuEopd+7XgY3ut r+ywAhxvmuJtpPEQG2S4jotGvKThuR77y7tzZr9MLEGOui+YRhzqvWY7bVxp2EO8 Qo9iwRxs8dZ/pm82n7UryhbHFIM4Jpkw2KHXT8Ud1pqufqH+qgzdNJEauTAAz05s q8GCCxYlL2uNJkRgUOQzsN3hOFfGDXwSCgMcy9k8khx9Gw5736ah5gRxZADgGhf5 r+wHONkFafbtvGRb3wQfNVRx1I+LXP6T5Z79S2FnIaC7LDp/4fWyOGL27H77v3qO QrgELodiyzlthR6D43WRDZ1cEVJ2a/3qLW8YdizomM3nTk7IXPtEpjYMD5GNAT+u iOiqIRSThaj6Hz8FGLCYRsu7uq9HNLSVmRQYlqPo1yaPCgREyOFrArRYY90WBueR tGFlxsKoJVRXu+vPfa73IwoyGPq+5aYjdtCpwQd4BgZw+/akf5ZbUVcoEnShZy4+ I5d25yhNfUj1TrbLV/oUxxPmw9exJnE6Acgr0Ce5Fz/lIrIkUR32gX7j6yRwYeLL FJkjIIJJbNu7r1tJYf12Vr0LFXp/Cp8w/epFauDdolOPhipVxx17scNWWq0SqnW2 2UrTr758IRYRskpi5/otaszejanCZ2d+7jeJutDHrGBsgSZNwMiYDO3zlmSZrVR5 ixUeEwaGsD+utJvdZ4Td =52rG -END PGP SIGNATURE-
Re: setting mutt to charset UTF-8 ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, October 6 at 05:07 PM, quoth Matthias Apitz: You are right, but only half way :-) In parts it is written in ISO-8859-1 I found the reason. From .muttrc the $attribution was inserted as El día %d, %n escribió:\n Ahhh, I see. This is something that *might* be solved with $config_charset (which specifies what character set the config file is written in; allowing mutt to ensure that the attribution is written in the same character set as the email message). ~Kyle - -- Remember not only to say the right thing in the right place, but far more difficult still, to leave unsaid the wrong thing at the tempting moment. -- Benjamin Franklin -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJMrJJyAAoJECuveozR/AWeTc0P/1vaNlXDmEQSuHyN4DX4X5OS k5oUYkRh0JhQfnH6mjYeXbeIKKVVxUIGTp3Y0u91UjmD6hAtOneVPqGBImTLN6Ol qGNaZ90F8dOTn7mLx1mZt5fx8JkieISYl3gzki0dfCpOA0+4SuGs8gslZgZUsQg5 JAnwRh9Ju3OUmwWduRymx+vZbgUtc1kYAH9vR2gX2IH4HPXnGCHWWRrkd5Mixr/n xN0Pesfr5GEEHbE3vDbP46qgfVWKeeo+/nTGfJX9WQgjHoCBNdV5a1/mVlsJRjoF VGrc7xnrGs5PuRYFKV1LSO6COFWOhOl+PfxGmq9V1CZ/WO3ww+LaOxBrtnqEOq52 eGdHDurH8y2xXbn7slTPKXrfC7ehBKfmdz9Qurf42+WP08/VZhkCy8xBHLFhwrVw cHDc9+tlP78vFEJqFB2SYbhAs6idmj6in6Od1yaI1huhUM23BEV+SpNLZYNKpqHt adqzDzUXMNLIaMzAGs6SHmKvH6HPh9Oew1ETNFWuGSxSxvcBTWhGOfEEi2bTjevE UD3YKOUKdyhQn8CHDw+aroxFcpdbxazQFHWk3yQ8AcncISi9fRX+tPiGxnOkX41N 3GNaYEW2WRrsfj/eD2zYckRqxpjQsVc+bymDBNB7krk7MB2UnMWlKLk2cYgmj8AM 6QCLoS7j3CiuizbcoypU =sbwT -END PGP SIGNATURE-
Re: setting mutt to charset UTF-8 ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tuesday, October 5 at 11:58 AM, quoth Matthias Apitz: Error in /home/guru/.muttrc, line 70: Invalid value for option send_charset: us-ascii:iso-8859-1:utf-8 I double checked this against the man page and even cutpaste the value from there... What does this mean? Literally, it means that one of those charsets wasn't in the list of preferred MIME names (i.e. isn't supported by your version of iconv) AND your mutt was compiled without utf8 support. Check your mutt -v output; you may need to recompile mutt to enable it to do fancy character set stuff. ~Kyle - -- All men dream; but not equally. -- T. F. Lawrence (of Arabia) -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJMq0IBAAoJECuveozR/AWeXq4QAJtS8o12EiZWX9ooUsF4+MX4 ivl2pTMDuV6CCUxqkLX+ikOOu7yCHwfIuTEyIwAnNwLJfhGt1uAwDYbWwSKOFnZ5 /sHrcpD/49qk8JFtx/IpqqrAvW2UI8jUALqeSsn46WMMjwW0ytZDNrC9JYUiQ9br Tr4LCEC6SP+TcoD1rJbwKqtO0xyQpaMltYfS2ZOtvOlCwRMbzjI4qDaPAWSVFIiI zoxR6tZDjxZu8cNqZ5XLszwvUrE+gefcU+mexvd8xz6gIXoTcijjlQwja++gyW04 9NfHvwiNOOcmnbA59Td1V2szDdyjvSeIxdt+GDACIt9L5n2f/8U5rue6iW68Rc4L btgbM21WWJwAbpmghU04Wrq9mtz4t95BY4+FiT+nx9puXlaQlsqyQLkwy7MJ5IEg pyeIsLJl1z6fn2YTpD5YQDYaeWSTbnSo6LiXJsuYWvnfCx5UrlUQfprVTpK4e+Wi sqJ2zIikhvcoJU8iqWl8LkY7OhoXZ2Habz9hYbYCETQj/LvmDkmziv0W0JsaeLSX z0fgJwrCCGSUdHDePsyftF1NGZuXtQN4ehbJv0DVJecL2g8dbw6GN+e6hBfV2vsd NmHuQ9MxoLZcZA7N+HI5DzEuoBL4B42waNYdGyJKItc7LmM+uoNR6EJYFonqnX6A OWKaC9jLyBTx9zqIdWhs =MdWw -END PGP SIGNATURE-
Re: setting mutt to charset UTF-8 ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, October 4 at 11:25 AM, quoth Athanasius: I'm unsure if I should completely switch to UTF-8 already, maybe this would cause big disaster in the receiving sites, mailing lists etc. What is the opinion about of other mutt users and what is the tendenz we should follow? I've been using mutt as a UTF-8 enabled program for... gosh, probably four years now. So, it works, and it works well. Here are some things to consider, though: 1. As has been said, mutt uses the smallest necessary charset (of the options listed in $send_charset, in order). This makes it very compatible; for the most part, I generally use the UTF-8 capability only for displaying emails (with some rare exceptions). 2. Mutt's ability to display UTF-8 is limited by the libraries and environment it relies upon. So, if your terminal can't understand UTF-8 (or isn't configured to understand it), if you don't have fonts with the new characters, if you don't have ncursesw or a similar version of slang... lots of things can trip you up. And, some general charset comments: 3. As has been said before on this list, never EVER EVER EVER set $charset yourself unless you know what you're doing and why. Mutt should be able to figure out what the charset is by itself. In virtually all cases, if mutt guesses the charset wrong, then your environment is set up incorrectly. The only good reason to set $charset manually is to use some special features in your iconv library that mutt may not know about. 4. The $config_charset variable changes the way mutt interprets the config file from that point on. Use only if necessary. 5. The $assumed_charset variable, for most English speakers, should be windows-1252 (aka cp1252). YMMV, if you have special circumstances. 6. Charset-hooks are your friend! Most of the time, though, you'll just be using charset-hooks to map commonly mislabelled charsets to windows-1252. ~Kyle - -- If an elderly respected expert in a given field tells you that something can be done he is almost certainly right. If an elderly respected expert in a given field tells you that something is impossible, he is almost certainly wrong. -- Robert A. Heinlein -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJMqqQ+AAoJECuveozR/AWeTNYP/1SHq8eBADIftxhgkUD+KO8V 6lngA303oTD8/H2Nansyc04VqhlEF4ngo0NsMWBeRgPUfA4qZlzCAL40QCva+NYB av12QUt2uI+kTBWFK8Bd51Kiwq8i7xYQSIJQTyqiVTuB8G67Re3yhKI9mLuHtWv9 N6wfdRuC6gRHMp3GwndEA2bW+WPiLajXdBbJwrF1+CniqQEMP/f8gVAaAcfO0OKS qJ8lyhp1bvD83wq2EuNSesI/wWAznCwkzRF+fOEu3xDxjJarzE/ev2Zb96B5RW+W 32VMwIAm6V+4dW6txujpI12IhggRmTE2UADizHs83fNBP7a4PcAcp3UsbrymZ0TS 7A7dbpWVQTsyPwRnLdECD6MkreLpW8588eWIYJqvQH57t2HyQ/VUUr/040cSm/6Q nm83opXBtwBNBB3haUPJKZ6wVObzjL7drVjLw6gUJ7ccIH6C2xV9jDewSOpFsmAq eNVsh28I1nKXnkNVIbFrGvnAM1EFatzE5v0pWV+YklNPt+TlsSf0HCKcteFIMf/o gv+ie2dnqpDcIRqHQm1ChnER2LyolpLMqVgVykgyCaQzLHcwQK9h75eKfyWZQGr+ /F9dczHqcc4dJK9q4SNYtepVe8SkdOhTKqlQ3cNg8prqa9Gu1leYpYAinJ5DaOIP FsLgO4BkPYJdXVckxoPK =qEcE -END PGP SIGNATURE-
Re: converting from pine to mutt
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sunday, September 12 at 07:16 PM, quoth Tim Gray: On Sep 12, 2010 at 11:37 AM -0400, Thaddeus Morgan wrote: 1) What is the best method of converting a large number of mbox folder into Maildir folders? I've read that mutt's -f and -e options are suitable for doing this. Is there a best practice I should follow? Mutt can do it. Mutt *can* do it, but depending on the type of mbox folder, perhaps *shouldn't*. Mutt makes certain assumptions about your mbox folder's format that may not be correct, and can result in permanent (subtle) corruption of the messages (if mutt is wrong). The *best* way to convert from one format to another is to use a program designed for exactly the variant of mbox you have been using. See http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/mail-mbox-formats.html for details on the various formats of mbox. ~Kyle - -- Everybody has to die... but I always believed an exception would be made in my case. -- William Saroyan -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJMjj6fAAoJECuveozR/AWe7NIP/Ah/8s6FREDWpItI+pz3ZJtt /mT/PibVMhFd93R96W44Pj5XaDckUYCWCI8/wfFoBb3bRzb6duAvOz1fzr7k0Smp 0KQ4MNQt8CzVD+6g4kYqMLPsqpFYaFqgXeQZrQQ5fSZ8zGQiK4ud+bgjCcp3AZeb IiuTloRy6LaUFiP5eG2RXlsYk0lQ4mdTrbrOiLZ8maOHtl2lvA4iAHqFtw4HJd23 rK06zhs1H5AnPdeRWQx9yoGae1UFPq1VubIiOJbwvqlJaYU4A3PQ9+nj082xKm6t fjxTsSz6B/EtSFChwq6HR2gWAxKNEHqnKLs6V30/s3gtyaAya2nKD/mo6rcB3UhY BRMUCqdEwhyZQn5asCTBLPFvKPffGe4IQWKr5Qvct7ZgKnBO405vjHcNmWdyBu6a +jTBzLmterMPghPTP8UdVntxprVT01A9HE9WAOd+Az2YVynzbEc8HmLQJBCcqWiW ITsUgWRy82tFZ4Sp6rPqpGxH37K2scjxyxPgHbCdUahDCqArSWZ4Jxi/W5Y+KjAp UnTXu4fsQbaUT5CYi/tuQU/Rte23QSH3udAVSWLCO8v6OCQ+OmkZRLcdRIgUleyl 6vPXLpF5yMYSYQkf00qqN04ko3nKyBFeMYxRw53hvBGmnn8QlpQFf6sFQF1OXnyM yCGZkaTjqemEFjnfqWV6 =6LDt -END PGP SIGNATURE-
Re: charsets
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thursday, July 29 at 11:32 AM, quoth Paul E Condon: I'm still having problems. I'd like to read some documentation that expands on what these configuration lines do. Without a better idea of what you're after, I'd say the Mutt manual is the place to look up the definition of charset-hook. I can't find any mention of unknown-8bits or x-user-defined in the Mutt E-Mail Client manual. And you won't; that's just experience talking. I've seen emails that label their own charset as unknown-8bits or x-user-defined. For example, one of them was generated by pine when the user was trying to respond to a utf-8 message; the message had quoted the utf-8 characters, but pine could only identify them as not latin-1, and so fell back to unknown-8bits. I forget where I saw x-user-defined... the point is, they're bogus character-set labels instituted by software that's gotten confused or that doesn't have support for a modern charset or both. The charset-hook command defines an alias for a character set. This is useful to properly display messages which are tagged with a character set name not known to Mutt. The iconv-hook command defines a system-specific name for a character set. This is helpful when your systems character conversion library insists on using strange, system-specific names for character sets. ___ In this, iconv-hook is described as a method of handling a 'character set name' that is not known to Mutt. Is there a place where I can find a list of the character set names that are known to the copy of Mutt on my machine? Where? How? Or (gently, please) why is this a silly question? You're right, the distinction is quite fuzzy. The way I would think of it is this way: charset-hook is used for mapping a weird/unknown/wrong charset name onto the correct charset name. iconv-hook is used for mapping a correct charset name onto a system-specific one (i.e. if your system is broken). The example for iconv-hook given in the mutt man page is for transforming iso-8859-1 (i.e. the correct name) to a system-specific 8859-1. Thus, they can stack: the charset-hook can transform latin1 (and many others) into iso-8859-1, and iconv-hook munges iso-8859-1 into whatever your system prefers. In practice, however, I believe you can use them both to achieve the same effect. In other words, both can transform latin1 into 8859-1 (or whatever) by themselves; the only reason that both exist is to allow for a certain amount of stacking---in other words, the charset-hook hooks (for correcting or canonicalizing incoming charset names) can be distributed among many systems, while the iconv-hooks (for translating correct or canonicalized names into system-specific non-canonical names) should only be true for a single system (and probably one that has a broken iconv implementation). Does that make sense? ~Kyle - -- Always forgive your enemies; nothing annoys them so much. -- Oscar Wilde -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJMWcdbAAoJECuveozR/AWetSAP/iixHpElY79qJRnqxcBW+7nx jaul8sKkOcyDl/oA1+tHNtqeJ6NCQl5j/ExSYckKNC9b8nZYZ6wF8XGQUc1ZMbrj 76bs52IYjjAfkkT7njBfXlNJz2uYA42C7pHSxk3WYOiyB7PshcCqxbI6A0rzQvxs HSvlMCqSTI4m2ldX1iLWsKPR09ZecBzq4s9woD1Mp1zm/uFA39/YafFCmyIvkY+5 COOwj/Uv5XGjNdC1zSQYFKEUFkYMEKlTS5bapm6ac1tkhMGw01uL7GFA/lVsHymp 6a6VsmTdm0KayH5XVAp2Da8bSVPI1qxqObI7kwKHQJFz3E9I7j6Yy/Qzuc0hUqSU ViHrWhPKJp/iKIycvfWbajazXMm5RqPJ9bGm5kP77kVAAOy1KlUB3zpZTNtNKRS/ mzDI4XFlWx89FmwsznbhtCHqIlrtDaT9qajMryNr3l2Ab/LVzm30BLO1YHAUHOGo 8nDVlu07uav9k+jlvnlQSxG0wu3VeF/nuGZCSbDlqc9xdxLSRuqfZtJ5idPbrV7c BrO8RYbh0djZriIkmblazlQL84FzwYfw1htTrkux0E/frGmcLtoxy4TiPbJSFRBi NUYfO/W1ZUFbQtcq2crTQYlyB4GCjHwe1Ai44ObpOXbUbxdIIkTRecahNljAprEP 1u/iwLtEF2TLpmx6m2+x =30fE -END PGP SIGNATURE-
Re: charsets
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tuesday, July 27 at 12:35 PM, quoth Paul E Condon: 1) The short answer does not work. My copy of Mutt informs me that LC_TYPE is not a recognized variable name. LC_TYPE (or, more correctly, LC_CTYPE) is not a mutt variable. It should not be set in your ~/.muttrc. It is an environment variable. It should be set in your ~/.profile. Also, you should probably set LANG (also an environment variable) rather than LC_CTYPE. For example, if you use bash or sh, like so: export LANG=en_US.UTF-8 (Not sure this will appear correctly on your computer. Your computer may actually catch the backslash sequences and display the intended quotes. On my computer there are TWO backslashes, each followed by three digits.) Gary is right, the problem is rooted in Redmond. Has anyone here seen this? Could the problem be that 'en_US.iso88591' should be 'en_US.iso88591-1'? The email in the expample contains 'charset=iso-8859-1'. Suggestions for a fix/work around? This has been posted to the list many times, but yes, the recommended solution is to add the following to your muttrc: charset-hook ^unknown-8bit$ windows-1252 charset-hook ^x-user-defined$ windows-1252 charset-hook ^iso-8859-1$ windows-1252 charset-hook ^us-ascii$ windows-1252 ~Kyle - -- However many holy words you read, However many you speak, what good will they do you If you do not act on upon them? -- Buddha -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJMT0f4AAoJECuveozR/AWeemEP/iYk9b/WYOO4Xrokfmtihmxf i4ETE3ue/eQ3ziVnfaRK5JnpHcdbLIgfWDKe6PRO26exc1dceiy48TJfDJVsaZXG ascigQHDpuPi82XzWorHgNqoIeCbL2ih19rDdGMxK8TCxttaaSF3656VVCBGmgls fcEG16tvQnDVYqkVV4szDjOU3e/2tD+9imuKheZClq/5CuJE02ozMerRIbtcrs5k LtByl/ub1SZJLXhLZjYn8k+ljEAvvobaA77hD8dT9Bx4BfKPtAn5Kaj/3HZVtkZy DQb1VbzIXcQ9ahx7lY6tNQdz47Yaz/c8+NjzpY/C4S7HlQxcZUPNPpQhIDUxLti9 pnfl0XnpCB5lAb1S2TlQsIRSfRgrt19YXMTuAmRAJqEu6Y18+mmMR0qpK1iO7PFu f4Y8/GRglt+IaBvmHD800pv/2gj4LCf726beezDON8rYJVZUqSpIT4OXxGen5Zs+ EGKITrzvFph8ahYTDh356nrTLH/U+4Dn6rRlCAqczybvFmiP3qhhQWlTEVNlyYyL d8VmRyqH/maaiaOMxjRjMfVV1GIKYTbC4EbfW8/LjxPvEk9Ddhp5I2qm8h59l6bo Vdo9gH6ugLhPCwW+WHoL9okP/5P888oR044Efm3bDCv5306dnarVV7wT8PsaTXsc QjN5QDkW5Tw5R/qeOmft =6565 -END PGP SIGNATURE-
Re: Mailbox closed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sunday, July 4 at 01:36 PM, quoth chombee: My muttrc has `set imap_keepalive=450`. Maybe I should reduce the keepalive time even further? But 450 is already twice as often as the IMAP standard requires. For what it's worth, many IMAP servers ignore the IMAP standard for things like timeouts. Though the IMAP standard(s) say(s) that autologout timers MUST be at least 30 minutes, it's not uncommon to find IMAP servers that will disconnect if you're idle for more than 5 minutes. Unless you have the power or influence to get the server operators to behave according to the standard, you've gotta configure your IMAP client to deal with it. I will say that mutt is a bit unusual in that it makes it explicit when the connection dies. Most (if not all) GUI IMAP clients hide re-establishing connections so that most people never notice that their connections died. As a final piece of advice, I'd suggest that you read up on the interaction between all the various mutt timeouts (particularly $timeout and $mail_check), and consider that $imap_timeout is similar to $mail_check in how it interacts with $timeout. The way this works is somewhat counter-intuitive. http://wiki.mutt.org/?MuttFaq/Folder ~Kyle - -- The means of defense against foreign danger historically have become the instruments of tyranny at home. -- James Madison -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJMMPElAAoJECuveozR/AWe8ggQAIvqO7xseL9DDhqScdrcD2Bm wv2+k06VXQu2iDuNVzGiQTPNPtyUne4JDvG0ip/nIq//Q20u1EODMrNQy5CzMG+7 GlRGG9RV2JRjQvFLccJ85PeDrv44Y8OoGYUjgnoCKQepHi639P70tXYO32QyyzQ3 EoSEv9MW5SZS/slOeJX2rbu9323Z2Nbg4MoYTbYTc1gMR/wDv8cMSCM/Sj7Lqr4v lRRTF9z0KrdsFpF49mJ4ZnHDctvMLiJvOIkHGTNv7WmQAMEFYAZ1ykfbbNAGb3Ua lv7YgbnPRSr7yBBCOH3PxIqFadgmdsQaDbGWdwnlkBjC63FEmuOl9EPU2Q74UPAi 1FTUZr4YkgIsTD3QsLxULVeXpDZjfmZcu/EflVKzXG3NfYFhl7HvsyYMMqzTA0Ji bX7PtibDg6a1IITFnh9iqb/UNKmy/7CW5M39DaOR41WDBTRsm62A4bTE/fyDKnUy tbMGUmZ4o9uXfqDFoNBnVK6ZxWtkQN3DJmJf/pBKNFhCNFnlAkhfzYLJtXhZGO2H GH6hPXzTc/dVaR7t/87dHUVSn5fFhxw/TII4EZfZtY4dtl4SXaICJDD5Hf3EA8Jc Nywz66Hzi6lZF9dh9uIQuopJj/UxkmrjUdXbsdER96PrBdZ/2PkOW2XS9zf619Xg Qi0WP2zIKxc56unD+wQv =covi -END PGP SIGNATURE-
Re: sidebar - strange behaviour
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, June 2 at 03:14 PM, quoth Anton Vernigor: Sorry if it is not correct to ask about sidebar patch in this mailing list, but I haven't found anything like my problem description in the internet. You wouldn't be the first. The official way to ask the developers of the sidebar patch a question is to use their website: http://www.lunar-linux.org/index.php?option=com_contenttask=viewid=44 And one more question - I had to use mailboxes configuration parameter to see All mail folder in Gmail, but I found it in the internet, and can't find netither in configuration file comments nor in the documentation. Where can I read more about this parameter. Here's the documentation (you could have found it by googling mutt mailboxes): http://www.mutt.org/doc/manual/manual-3.html#ss3.11 ~Kyle - -- I would rather have a mind opened by wonder than one closed by belief. -- Gerry Spence -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJMBnctAAoJECuveozR/AWeQiQP/iq+Sd5anyKetx0SzKoc7WO/ 12G0SE3zzAan3cHKcCD3+PGkF12NtpQsTmEP9jul1BV9mnpjbEwWAz4Bi2q58Ml0 TXMARDCjnQofs9qDUavEaWaD/2F+F49cpKTYiN2w6goOEfGAFLCADxrB6ASZIhNp RhEuN/jdGhiedU2rPGoKC38GDIewOfEGxbb4iWkUh0X1DWrevXytfXZbg7dxQop0 wL/AwmYl/RJwpndTnXbdLARCyrLL1WAK5h/1iDwKmNav9lm3uqJac27KNJVfEP7i JUo+LgY0hf93i9MiBk2OBq+KD0KYipOFR8R5vULLYx+YRuhJBaKzj6K0WwahSEqG vrqe4M73ObpS12Spqvl+1RzB0mHGmXkUl12hjdZTj4Xz4qPnjwljgV0p4KszkdDm R1luOL6Tc9hXXL5VKjai6koVRJqQygycyqpcq7WM8GybGhxRvMmQpRYt4DIHedn8 n9hVqqhzOdA3EMr3uYTkZe7U4Y5t7t6+ZNbheV5Z3dcn4QHAE8RGlwLW9tdNSn+c Q77SyhWQzj37liEosZjobKIV0l2gTpHzVYMsv2YUKz+7HDF+NTkte0oKZllVotRn UBRjCKS+1Ik+FDB/U1/Bo2ys/NVL+F3YHHt1XtcxKnFlWxPkUFluTES2wovZgmkM RPGbEARi+G4LIBAjdmui =yQpw -END PGP SIGNATURE-
Re: Privacy considerations when using mutt
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, May 10 at 04:06 PM, quoth chombee: I'm wondering about the privacy implications of using mutt. Say I'm using it on my laptop (or any untrusted host, maybe a computer owned and administrated by someone else) and if my laptop gets stolen I don't want my email to be compromised in any way. I don't want a copy of my email to be stored on my laptop, or accessible from it without typing my password. So I use mutt, and I connect to my email account over IMAP with SSL. I don't put my IMAP password in my muttrc file, instead I type it every time I connect. I used to do that, until I discovered the power of gpg to decode things on the fly. Now I have an encrypted mutt config file that is sourced by the main mutt config file, like this: source gpg -d .muttrc.secure.gpg| It'll ask for my gpg password, decode it, etc. I can even then use gpg-agent to store my passphrase and allow me to quit and restart mutt multiple times without retyping the passphrase. The header and message cache options seem like an obvious information leak. Which is a shame, because they really speed things up! I suppose a possibility is to encrypt a directory containing the mutt config and cache files etc., and each time you check your email decrypt that directory then launch mutt. Depending on what you're after, you certainly don't *have* to encrypt it. You *could*, for example, simply use a wrapper script around mutt to automatically delete the header and message cache. It wouldn't make first-visits to messages and mailboxes fast, but would allow you to take *some* advantage of the caches. But a wrapper script---or even something called from within your muttrc---is a powerful way of making such an encrypted directory simple and convenient. If you're feeling *really* paranoid, however, you may wish to reconsider using a laptop at all. If it's stolen, a smart thief can recover your passwords by taking out your hard drive and scanning the swap partition and/or swap files for anything that had been stored in memory (like a password) but that had been swapped to disk for whatever reason. Worse than that, an even smarter thief can get those passwords even if you can prevent them from being swapped to disk, by quickly cooling and then removing your RAM from your laptop. It's a very scary, surprisingly easy technique: http://maltainfosec.org/archives/92-Recovering-passwords-from-RAM.html Because your RAM is vulnerable, ANYTHING on your laptop is vulnerable, even if it's encrypted in memory (because you'd have to have a way to decrypt it ALSO stored in memory). So... it all boils down to how paranoid you're feeling. At that level of paranoia, webmail might be the best option---even there, you have some potential issues with password saving or, at the very least, session-ID saving. Much more paranoia than that, though, and you probably shouldn't use a laptop at all. ~Kyle - -- Once again the conservative sandwich-heavy portfolio pays off for the hungry investor! -- Zoidberg -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJL6C2BAAoJECuveozR/AWeo48P/i/i6y9pQjBiThnAN+Hy/U4Q DYcJfTMjAkceN+YH3svqz5xRuI0ekDoWB8lo1TQ/U4xXywymDEIk02u14vnizTch qWGp93EnAE8ArPhgC2ZHHUh7eYHn9fIdb9FH3plaVv5cDSS65e0zG/mRIwigXj/b aS72ov/vDZlZUGJwYWp+MNWudFWcCXqFlxzp568QaThs9tZbE00nHOKaBbRCNmUX cMvts15ecnNvaVlzqTVuF5M0lSCZdwPeEWw+W7wBv6FP4ClItmKtmUo/31iQSFWc IeVLYOnZuuKSB63mhWhG79nz+9+wFkFZ4gLL38cRaGYI4rIJW8Z+myIRMiAqQlBk u4UZ1XOitTcHXZfggXwWTNEG4jkX+Rzl+lNNN07sm98oWIGgSVfGYNrg9vAus90u nl5pEWkNhaBl8+25dhgjoM23IWvRIa+k6aLG4w45Eev7Za19VsWfoDoahRM/1aco yHjFzOFjR5ENSw7U+vIQeH0RwuVJ/HGofaxf/FKvv8XkpxgYjeuervQ9JiDBLW/z JdVNyJO73gzi8hWR9BZoc2RjdSYFD7m1aPyCTFcurwXMyAGYwhRMVRI+1ynixjEa t6zmx6GvdvYywkYLUi/DfT6J/+oiAKPYf2xOdeLKgZMw6UXOT+GtuFeTcfjATvDb Xr6zOKF5H7GQrNrI7Qcq =SR6U -END PGP SIGNATURE-
Re: Privacy considerations when using mutt
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, May 10 at 01:06 PM, quoth rog...@sdf.org: source gpg -d .muttrc.secure.gpg| Do what?!? That's awesome. Thanks for the tip. Not sure if I'll use it, but it's a great thing to keep in the bag of tricks. wow, a bash script freak here and I never thought of this until now. makes me wonder how dumb i really am! :D As a fellow bash freak... that's *nothing*. Bwahahaha! Let's compare notes (granted, this is two years old): http://www.memoryhole.net/kyle/2008/03/my_bashrc.html I find, all the encryption/password stuff isn't necessary if you lead a normal life. A theif will find more value in your hardware versus your intelligence. And, all that extra energy used by putting in a password everyday will be useless. All in all, best to try to remember the wife's birthday or anniversery, versus trying to hide the affair -- unless she's better looking. ;-) HEH. It helps when officially complying with corporate rules about passwords. ~Kyle - -- It is a tragic mix-up when the United States spends $500,000 for every enemy soldier killed, and only $53 annually on the victims of poverty. -- Reverend Martin Luther King, Jr. -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJL6HgGAAoJECuveozR/AWeH6sP/ROo0s8p+oF9H2fZoXc4dOPI 4xzEHqrm0PNmmdA2NRd/51eb54Q6zkjdqFxyVh/zHWa+uUaJ18MMBKxAUHXdWacc 3vlrKI025y8Yw2pW2M3elx5PlJEum+2tj7vRQHEr5mywDF1WLogwD9rurqL4V7f0 EjSw06KJKytYHKxgoY4IAxwvy2/k/rHKqPWkV0KlONfbn5LMuhYsuHWVyJk9x2kV Vv7Z8qfE1uvto8rqmUs4j6NaRq4264RQoneOav4Igs1SIY8PjPxcqrVtgg6kphG5 3y43Cg9gfDHHhXLMnDna0EbfPi+uDnMw0H56tZitfwHHuaeLOVlYSKaKeevtKEi3 YB9pFbMZQAeCJElLfry0yyZcegjj9X+uEgHM8JGgxvfLS8IgMxP3xAcqVPhU+v9V jN9CI8fu+8htA22+ss2bdiR/XUepPuoessoH+irfxI1dyzkK51aV30byXxP0DTpV 1xOTQX4UuOaF6hiwqjbZIzpoa25G5TPyi4onfMcVNjqcv92fdoP2AWM7A2z3XW6Z 7Kcuqd/dNEFbmfsCh/j8i47mFfvkeZl/p9DdHhssiXy1Rt++i48xaGnK4Zk7BTKl UDc0LvCSI67BOJNYGNeCGzIkmxUfwzu7FN4FNLpJciZMY+DPefO8Nt9jK5cABiC9 OwUAKpZHHBLtItzbzuKE =f6G4 -END PGP SIGNATURE-
Re: Mac OS X Terminal.app, FreeBSD, ssh
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tuesday, May 4 at 03:59 PM, quoth Jamie Griffin: There are quite a few entries in /etc/termcap already for xterm-*, including xterm-color. Good! I tried setting TERM=xterm-color in ~.cshrc (obviously using the correct environment setting syntax for csh) but it made things worse by mangling up the display on the console of my FreeBSD machine, and didn't improve the display on the Mac either. Perhaps i did that wrong? Probably not. First of all, your console is obviously NOT an xterm, so pretending that it IS an xterm will produce bad results (for obvious reasons); for that reason (among others), it's almost always a bad idea to unconditionally set your TERM in your cshrc. This is one of those environment variables that is supposed to be set correctly by each terminal (whether it's your console or your GUI terminal or whatever), and then passed along by ssh whenever you connect to a remote system (the reason ssh passes the TERM setting along is that TERM is supposed to describe the terminal that is being used, so that console applications (such as mutt) know how to correctly manipulate your terminal). As far as why setting TERM to xterm-color messed up your ssh connections as well... what's most likely the issue is a disagreement among your various systems over what constitutes xterm-color. On some systems, xterm-color is a synonym for xterm-256color, while on others its a synonym for xterm-16color or something even more restricted. I believe it's an issue of philosophy: should the xterm-color termcap file reflect the local system's xterm and its maximum capabilities, or should the xterm-color termcap file represent the minimum color xterm's capabilities. Since many systems default to the max-capabilities of their own copy of xterm, I find that it's usually more useful to be specific about what kind of xterm I'm using. So, I almost always use xterm-16color as my TERM setting when using xterm, because that's enough colors for me and because most color xterms can handle 16 colors---many cannot handle 256 colors, and if you try to use 256 colors with an xterm that can only handle 16, you'll probably get weird-looking results. What terminal program are you using on your Mac? Apple's Terminal or an honest-to-god xterm or something else? ~Kyle - -- It is only possible to live happily ever after on a day-to-day basis. -- Margaret Bonnano -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJL4EjaAAoJECuveozR/AWeuyEP/RtSwFaNvbAsFlkBE6mlgpFc NHmGS890e3sqwFBkYu7OAeJkXoC7wltQ//8bBGW8L1P9Izwzr6lPQJGuMxqmP8LG xnrpL6bTHCFdfkVlq6l1vDpoX84b9an787hBpzbMHwh+eCPT9ebtKDNegGAPI9hc PpNNhDuaLXz/Cx/qozs+1H1H0I9C0NL9h1s1SfPqrvd7ftLSniGpzwkNoBx5BQ/O RuZNf/ndi6fVdgp0LWLz09IdJwL1m86W+C69Uiscm+XqDVCef0IfZ7uSZb3wFZrX 8iv9nytIvMm+s8GDRG4I9dtEqQpB5bF4RodzNE9y5woTUAJOLucb+CkUcgoyZQiU jYCrprOK9fGzluBJmy//TM2a/vaQ0eo2UnOUm6C3N1SWJNXF+ZloZKreXlH9xRRT Whz0vRLVkmna8BX9RiBkzPiVX0KaJkHFXhLAHOAMq6lGvA19HSh6RUOV06UniGnT 5/EzMz4ZTBME5u12L/3t0p2j/9HWEp5Ci0MbO30D5t4RbheckNVNx8KrfhLn/DKa QJXC6ZmXVZqUL+xCEVG6ZnHsl4xdjwTR8gny8EXYn/JejrWaVcQXISnvX76feS2o gqUNtDVZuDSklhoFZco07+UC5ALUZXp0bd0SL/2DXEWU7wwsrztx+pKHXJ781gn3 DuJS0k+dkiHLvH9UD7He =Do2D -END PGP SIGNATURE-
Re: Mutt, OS X 10.6.3, and ncurses issue
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, April 19 at 04:42 PM, quoth John Velman: jrv:~ jr$ otool -L $(which mutt) /usr/local/bin/mutt: /usr/lib/libncurses.5.4.dylib (compatibility version 5.4.0, current version 5.4.0) Okay... ncurses: ncurses 5.7.20081102 (compiled with 5.7) Heh. :) Why does mutt -v give different answers? This mutt was compiled from mutt-1.5.20.tar, this afternoon under OS X 10.6.3, XCode 3.2.1 is installed. Mutt's report depends on the version information in the header files, which don't *necessarily* have to match the library files. ~Kyle - -- I have great faith in fools; my friends call it self-confidence. -- Edgar Allen Poe -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLzQnEAAoJECuveozR/AWeEkEP/2cpq7aD912MQT7VCSm9k37q x8afEZQeFGYjUG/sCPzeiw0l8XeXFFt/sepylTaGoGVzTnsdfOonKnvi3FLxLtnP Oa5pEeHLVhMDMtKA78Xuga4U+5rq6HdV+dDRBoy9YRSB7PW/WrKkzkdmJI9FlwMV vyjQ1YP2VOpfIIpCsasIwLxyghwqRe6i6FqnMjIqP2FyrBrjFUWdwRpJPK7OHYXr ZnkJD93s9kfLU8mA5jYCL1vIRkM0HiuE2fZm8Ruijh8/WSOqswWaRyJLeQBjkVtp cqTdwXEshFcwzxx7FxahfruoEizZdbBfBtBgSCzjZ1X3q65ejH49QVW3qsoOcXtg 0Ewz3fgcv0IyNIbxCl9qZ+Xu94V1vQi7SgnXezIT6RrzWIphkUhNLWyz6zfuOUF2 LidgcJgBDI0sl23OAkGqK/bTf0WXwaGLp8J1mIBLStqxvZKlNy4bVmA+gCCBuCvV rETZwGPU9MIyTsqYs/FI+3zY5/S5D6pGpGSfvRM7eFKmQpV2wXiRqE1gd9xZb55k fwTXSSEgXYQdxhT22CJ6G27S70XCcPEzwCi3gBrABt/UcES/+r8a7c2zpuhCZsxI wnFbfp/u6ruxDu4wUCXIb7SLyl4ne1kLItMPTDV0OA9R85usv57+DP8CVPL5q/mB NursgWoEFj2ErnbZogmJ =1IBB -END PGP SIGNATURE-
Re: snow leopard and mailboxes (and arrow keys)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, April 12 at 04:03 PM, quoth John Velman: When I place the curser on a header line in Mutt and press Ctl-b, i get a long list of the url's contained in that message, followed by Press any key to continue When I do, it takes me back to the Mutt mailbox listing. Sounds like you no longer have the Curses::UI perl module installed. Install that, and extract_url should go back to giving you a menu. I haven't a clue yet as to why my .muttrc doesn't seem to be working -- well, not completely working, anyhow. When I press 'L', it generates a reply to this list, but when I tried 'L' with some random message in my inbox, it did give me the message: No mailing lists found. So, it's reading my list of mailing lists, but not my list of mailboxes or my macro for \cb. Any ideas? That one I can't really help you with. All I can say is: when you reinstalled, you removed any-and-all extra software that you'd installed (such as the Curses::UI module). If your muttrc relied on any of that extra software, that's probably why it's not working. ~Kyle - -- I have always found that mercy bears richer fruits than strict justice. -- Abraham Lincoln -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLxA7gAAoJECuveozR/AWePrMP/RWVtGQBbVnCBh/7Mi3Xths2 eebifR0vqVFnNQga6ja6g/vgCg7hPON+qO6Dqv2fqUCKwcubVvJMbgSOhsSn+w1D s0c4mhEm+UyRLmfkvTjP8nz50gY0Jyij+kVHfTy0kQ+t+ANnqMirqGVw3QVe4MTk csQXlb/mV6+TMzqd1k/bvf5TngJQziw/H7XlefHoCsDRYLtiBgKiNk2w2l8eJsCq FMujkwGlT+Z7+ufCSNKTYGy8/6akbcl61pGyQqZZEAu+lMbvCiq9VHcfRlYl96p/ HRVEkXyPUb5MfhMh32wYMbf+34WbV5p8qUUU2ICmlgXwWd3567cpQhNnl2I6+t4a JRzLs0/pdEGLJN7KNT2Mc0SzJV4Fm4ylZx/zpUSiFcxPGGDBi3dLTslvFQpVVeTf mjyLi9Qs6BWyzCiTjXSZMsO2huouInr7s25IybTnISlXsyugwKgh0l/jMToH87xR iECBfowV+owts4f0XpV+TQAqj4/pPSrgdSqpeRQKQxotG3TdvRj6VyN4yHAX1Xbv gk5loLVjYYi3WWNO6JhZ4nOX9OKLEkFjAvccIzRAheI6eAwFzJIr6SbQDJebPXiG wlauFYQQya4hG0bmxKSWUxlg2OFYRjil/uTWW52/+Izk0FbgkyJwxCPM1MFJga0T PXhuOQD79Zx20F3ANyTp =g3zT -END PGP SIGNATURE-
Re: snow leopard and mailboxes (and arrow keys)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, April 12 at 09:41 AM, quoth John Velman: And by the way, my extract_url no longer works: It is in my .muttrc as: What do you mean by no longer works? No longer allows you to use the arrow keys to move up and down? (If so, it is probably a result of the same problem that broke the arrow keys for mutt.) ~Kyle - -- To laugh often, to win the affection of children, to earn the appreciation of honest critics and endure the betrayal of false friends, to appreciate beauty, to find the best in others, to leave the world a bit better, whether by a healthy child, a garden patch, or a redeemed social condition; to know even one life has breathed easier because you have lived. This is to have succeeded! -- Emerson -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLw5HPAAoJECuveozR/AWePC8P/jsPIX/jqnFvYZSown3Si+uM 3MuPjMHeFcuibgUJMw6eFn96YP2lCJO8/k3sZ4Ilf74/hTjc9+F5lJeuI320tatD SrkNxiZnD46UHg8hh9gn1lIoMTtuT1UxdpMFQkHrJEffoK3vt6UZ4Ta4gIploK71 wOePN2nOQyk0vmidrmQ12k11MdCbvR51v1vPEGkRthx6/Mrhdke+2rH1OGJBt3UR pBKDV9A0Scl4pOfNaVr9i0+56L9CURwvRT6YTRzSye7Md8V///yfGdiNYDoVhRdU aBSevpaPbYMs/81Ql5fTKLTuvsQr4HzMbR58dTnJyC90lSYMk8+gmHcozy7hnLBM yLVR+dVDwjihjo8KmPwfmi9tqc2DrM0ZETUfSTQyAp51K5vTUWMpiJYUi/f9NtDh 5u/B/wwHZZ4wMCzAlD9exKM25M+xcbPNhynPAKGFeUmbdnCyHkziuSgkYQfpQLH2 eQ+3cEsOmOiV3cSMX9qo5mObL8NOzIgNoS7xUpq5CrdNDcnxlqop9t17wBMuApcS z2EXEn9UzsCGyiRz2q9o70MXpqkjBvKXf1+DLOmn7amBrtS5c3OvxQGByV5v5cft dh57U3N5W5egx4f62XKkRMnHfPxDIJdUuFzLop8aEKEXWV+CN5Y7+z1RPznH3VRb FudVoBjaYnWZMY8a5czu =R4Px -END PGP SIGNATURE-
Re: Simple Mutt with Eee PC 701.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 set sent = +/Sent set trash = +/Trash Error in ~/foo/.muttrc, line 9: sent: unknown variable That's because the variable you want is called record, not sent. (I know, that's not necessarily obvious...) The second I encounter an error with when I attempt to quit Mutt: Purge 12 deleted messages? ([yes]/no): y Create .Trash? ([yes]/no): y Can't open trash folder Hrm. Did you define the $folder variable BEFORE defining those variables, or after? You need to define it FIRST. The + symbol there is actually a reference to the $folder variable. For example, with the following settings: set folder=/tmp set record=+/Sent set trash=+/Trash ... your trash will be stored in /tmp/Trash. Buy the same logic, with these settings: set folder=$HOME set record=+/Sent set trash=+/Trash ... your trash will be stored in $HOME/Trash. However, with these settings: set record=+/Sent set trash=+/Trash set folder=/tmp ... your trash will be stored in /Trash. This is because at the time that mutt read the set trash line, the $folder variable didn't contain anything. Make sense? ~Kyle - -- That it is better 100 guilty Persons should escape than that one innocent Person should suffer, is a Maxim that has been long and generally approved. -- Benjamin Franklin -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLXgywAAoJECuveozR/AWe0tcQAJXus5/0rnwd3EXR9Bpb0hbD tUG87/gnmbJYakoj4OfKBy5BKb3qj+lF5K2uT5B5mrOaJF9Fdocssba8Lq0PiPyu GcavtZ2Ke/WW3ExV1MqTnl6aXtAsjafQ2YdBTXR0gY3JOSk8w4DKaVqYycfOjwYq LZv5ri7bfq35j4DggDW86qBf07Jv/JTnxC96A4cIPblEiiDprgpEs4zzTduaa1xt vBomyGn5z7Y4cGtbDcXqjiz/dLzIfnTX9xKTAiuY544gYyrggKx0kujGzaNK7b/9 V6jkWubhkGxjMYbOOAiksdaD5d6ELxNRTCZ5InvCHqJ7TGQYBvpS72TRYvq7v2d5 u4AbyNWnRnM6l/U6PrQRccMUJAgzZdzchEMv8FNN7w92CrGc+soNoGYUspPvDnLF kJrsrz6cXc2OZEjNhtZ5uB+I0y0vlVsfPs0F/otm6jWZP8F3+GhC88tazCrKx+gY ypfkr6LY62Jw9uWvuZQZwOGl5zO5z0qwiyiyQvoPL+Z3A1WgKszxDRIKWMNiRkdN AwJkLb8E0+bk1muulv26cjQn/rRY6r+BXjf4Vhg8ssd8eHeZgzbU5HF2KEE1GlQ3 fIcItlop3FTqRrpffMf6det4gVkv8jWIK1vqDSsB7HAQ+whQu47BKO6MDPh+j/QZ UOjVftEtkzGedrbnzRw8 =640B -END PGP SIGNATURE-
Re: Queued outgoing mail
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, January 25 at 11:53 AM, quoth Tim Gray: Is there a method for queuing outgoing mail? Eudora used to have a feature where you could queue sent mail for deliver at either a specified time, or after a specified delay (ex. 10 mins from now). Is there anyway to do this with mutt? I'm currently using postfix as my smtp delivery agent if that makes a difference. Mutt does not have its own queue of mail; it uses other programs to handle mail sending. For example, on your system, it uses postfix. Thus, whenever you send mail with mutt, mutt hands that message to postfix. Postfix places that message in its queue, and then a different component of postfix pulls the message from the queue and delivers it. If you only want email delivered at some point in the future, you're going to have to investigate postfix's delay features. Mutt does not queue email by itself. On a related note, if I send an email while I'm offline, it goes into the postfix queue fine. Actually, it goes into the postfix queue even when you're online; it just doesn't stay there for very long. How/when does postfix flush that email out? It depends on your setup. It's possible that postfix simply retries along some sort of retry schedule (the default, IIRC, is an exponential backoff schedule). If postfix has been set up in a particularly intelligent fashion, it will hold queued messages indefinitely until some other system (such as hald, on linux, or launchd on OSX) notifies it that it now has a network connection and that the queue may be flushed. ~Kyle - -- Religion, morality, and knowledge, being necessary to good government and the happiness of mankind, school and the means of education shall forever be encouraged. -- The Ohio Ordinance of 1787, Article III -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLXg4lAAoJECuveozR/AWeiIMQAKBKoo6+nwBukRUd6Zm1UtJO TtiqGugSk+pKOcQGn8fwRtyw8pwRZWG7lpYEhzNjp4G5Mg1/tN9lf+ELNDWyQxW6 ENnXw16lYjOGHe+U6Rss7nqGem5chz3Mn7LFCws/BkJXzASS4osMNdM1w+O3QTZH cdEtVECPyN531s32Fq84lZlmEKwm+y5iKZYNgyPnSLD2/j4G6KYeOco87Q48LUAU PZ/UDsWvbpvLrVCgpjGDCI8ztMTPJ400+ytLrLzb3IUhwcDBd9oJ4QgI9jHhfvfi gspaptxZP6WLzeB1kWY5QBPCEyIvQ+lAjm7FpTaDeBVWeqwhFrRX5LLL2VFRVrf4 iTw/64ohuSs0Hqwn1uCu6NGfjoFBy9CD3shSQKFHhXXdLnhb2tGiqFGRvqS2KA2d cIv4OwL0A19kpvLiUHdtBWaaY3dgCveAzNDhs+JnGpK/7rR6AvdFXHQt8CjXKS4h lSDlPwQc/pnpmWzXJDtipP4uJqm9R8jUSKqcJHb4a2Yj8cOCgbTUJMdfpOakgfvs 70Qvvzymxv5Jesu/uMnfi0KJ7PfjjcfmivS2KeCJJE71dcvbR7I5fW2eT9GL2D5K j81RyjjIehulWZciepdTzbV9HZ+xv5dAOjv3MCwz/d/4vfh4M9bCWGpi2C2hyzZ7 xgcrPtkUc2UVW9vnk03Z =y0Tt -END PGP SIGNATURE-
Re: mailbox designations
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sunday, January 10 at 08:56 PM, quoth RobertHoltzman: I run ubuntu 8.04 on my desktop box and on my laptop. Both run mutt 1.5.17. On the laptop the mailboxes called up with ? each has an * after the name, i.e. list-mutt-users*. The * doesn't appear on the list on the desktop box. I could be wrong but I don't recall seeing this before. Not a deal breaker but irritating. An explanation would be appreciated. The * is appended to the name of mailboxes that, for whatever reason, have the user executable bit set. The reason (I think) is that you probably never want your mailbox files to be executable, and it's an indication that your permission settings may not be what you think they are. To fix it, simply run `chmod u-x` on every mailbox file. ~Kyle - -- This is my simple religion. There is no need for temples; no need for complicated philosophy. Our own brain, our own heart is our temple; the philosophy is kindness. -- Dalai Lama -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLS1ACAAoJECuveozR/AWeWaUQAJXNWJFUE0UChSRwjUnYivRJ PBdQRmBqN3DT6cXFPB3I20HErF2bbjZhCBg9Faqgff2IQ4r3zkgfdeuE6zP9eKGb wsSABfmnz9IEg9VTT5kiD1jM/YuCuelt5L7QS0ROwjCXkFP9AOvG2BI68oGCRHKJ 83BP0CW6jYWPnBDtBCNZg4jOVF7Lp6vSrspKERMG4pvoMKoWe0QFjw5IBLLFtK64 IXx6jp5Bf6312ZjpFx6gHpF+rlo4P4ir9/xS0EhWT3Bg18T5LUCxLJBMaLqsonKv xebm2/tlMmfDwH+gpn/Y7Edc4cVbJ+umjBpLnTGmQ35zLRewMFrPR7Lse9B0Ju0G HiQkGy2pfsJvvBPwD9iG2hi5KsLSCQWFuT5uTfjVHlMB53Jla4OLGcdgkiqBVo5h B4hdnU650HVZJqCN/WagqTmJltXDNfgcclfwGN8jy11J6BvZWM0M25up0HUrNshS CLh/gxaOxiY1tUC3wg193ximY33b1SlmSua3/UKV1ktrTitN39aaFR4u2WYTHCkv CmtEcYc0SEfx2qNrQRVmjPOMLw1J9h86h3FrRwGjLSSiHfXx6ck9MvGLgYnEWCoy Ulkd4vVcE4LzYWMuSd0Wtnhi6ipugQHr6M1iOofOeSo18yzAs7uc8LtK6C7wlf4s 8FCjxkTwNO7EVvibSsH2 =DFrk -END PGP SIGNATURE-
Re: IMAP connection closes instantly
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, January 11 at 05:58 PM, quoth Jostein Berntsen: He replied with this link: http://piiis.blogspot.com/2007/08/stop-annoying-imap-error-message-in.html Can this help in any way? Whoever wrote that blog posting doesn't *quite* understand how IMAP works, but what they're essentially advocating is putting Outlook into a nearly offline mode. What happens with the configuration they're creating is that Outlook doesn't check with the mail server for so long that it assumes the connection has expired and simply opens a new connection every time it has to do something. That's not helpful. I have tried to regulate the timeout value to higher, with no result. The Imap_keepalive is set to standard value. A higher $timeout won't help, in part because the $timeout setting doesn't do what you think it does. And even if it did, the point is that your server's administrator has apparently decided not to support persistent IMAP connections. In other words, connections to your IMAP server are apparently not allowed to last longer than a minute or two. If anything, you want a *lower* timeout value so that the server thinks you're busy using it. But if (as it appears) he's set an absolute limit on the length of your connections, then it doesn't really matter how often you remind the server that you're still there: it will simply disconnect you after a certain time period, NO MATTER WHAT. The link your admin sent you is essentially a way of configuring Outlook to more effectively hide the fact that the server violated the IMAP spec and disconnected it. This only works because clients like Outlook (or Thunderbird or Apple Mail) often simply open a new connection to the server without bothering you. Mutt, however, does not (generally) do things without telling you, and so when its connection to the mail server dies (for ANY REASON), it will let you know about it. I could give a dissertation about the apparent basic misunderstanding of the IMAP protocol in this blog post your admin sent, but I don't think it would help anything. I'll repeat: the IMAP protocol is DESIGNED to be used for LONG TERM CONNECTIONS. A well-administered IMAP server (and a well-configured IMAP client) should allow you to remain connected for as long as you want (even years at a time). If you cannot remain connected for as long as you want (assuming your client has a reasonably low (e.g. five or ten minute) timeout), then something on the server is broken---either the server configuration or the server software. Heck, IMAP even has the IDLE command, which allows clients to tell the server let me know when new mail arrives, thereby avoiding periodic checks and saving tons of bandwidth. ~Kyle - -- Men at some time are masters of their fates: The fault, dear Brutus, is not in our stars, But in ourselves, that we are underlings. -- Shakespeare, in Julius Caesar -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLS2sDAAoJECuveozR/AWeJ2IP/2I1s+uNUPzHokxudxZHY5qC Hr0lKyXD/6ZKfSdd0NBjTZvbXv5A08iuXiLlx49xOYvWEAfXTehFS2CU/h0Wsy08 RxqbIsJaJwzZtMpkAp/hXPB9QDDRikyITujSfeRMgO6pTyknD/cWP/o78N8ZwQ4R 8WEHAn0aHS/BLEQ84up7wcvTitsx/lx/mMLyiBgN63SKyjxU2wq7AojcjNzZnZP1 3yGcQwcLbtIr9MhP/hklaIOEAbkqqaciOTK1YMZSAjIlyx9CewrD/rCkDWpSsLLi e7rYlevND6qIaibGAo1Sl/zwa7a811YN4vRxpczZSgv2vPSJH0+H/7+cQPHABzIR opoj24aOGaeJxMsOqJOr5OSj7HAqVz+9ZyCa6/aHjimsMeF1ERJL0Sf2aZEPgTKN EHFLZc2q/EeeDqQO+kfyxrdmEKhDtSBrI+ykalh5fjLL5q82CNvWgKodTM99yiC9 kQKPpJeHm8v5pYZ0f/2bmVFreoXFpHYOPg2mh1HiG5XYLpjS1keWmgiJy7/muHCL FI030oZgdmD5gYTtOfZdON3CfSCbO9Gk6817MNMz36De7bsNuBMfyfrAeHteX+TG vK8UuTNljguuV2gvdv5F8q6lq6CCbST9v3jjAGOtjBxsNhDXnMdMg/gYJJXXvjsC wAStX1ygr7HkxvAJrhsz =lvBd -END PGP SIGNATURE-
Re: IMAP connection closes instantly
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Friday, January 8 at 04:36 AM, quoth Jostein Berntsen: I have set up a imap connection to an Exchange server at work, and it logs in fine. But then the connection disconnects within a minute even if I browse the mails. Is there any setting I should configure here? Not really... Mutt is designed to work with IMAP servers that allow persistent connections (as IMAP itself is designed for persistent connections). But if your company server limits connection lengths arbitrarily... there's not much you can do about it. ~Kyle - -- My definition of a free society is a society where it is safe to be unpopular. -- Adlai E. Stevenson Jr. -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLRriqAAoJECuveozR/AWe99wP/RA8TFC3M6MpPzew//BRK6IU IvUIjQDpfcppVL6F4WcGhohK5FOntXH7SaTIJfrAxn5S7EFiBXHN0+w14lkorE8g xGVX4F/jd8atxtVnWTmlkhDbog55c73mCN3CwDtXMSyi9r9+p2CBtgXKkFJu/3gV EdAvIfb8asfSeLDw76q+Jz5wcX9d0DvjuH7CMKqnZjK7PvqF/ruWK8Y21AK0ZIVR nkKFkQBkIHom5qajgnDImNYOnWKrHaolfylxBIMFLEN2X44B/HXG6n0BF/bfHDRR CrsBXSN/gwK51VMxHUAOSkP/puSEfBJDDmyJ0gubNI4BG1BPlUusUP5er0l5jet4 /8KPCDaYo3WhSrksBbVx3/eXJ5uTt3ZJ3JR5Smh/km4Ta1K3wK0qoM7q24GMIj3R bKbmz1ZQvbSHKftjApGgfOoQu0EilvJ7o7W6YdgJOlrzY918/tZ3escvbEObp8D4 Nxvcgn4wOmbdAKeEhoKAJSbk2IxsvvJwgGyOkIC5gTUdFn3TiHgYQ1mK8lG0/T9Z BmG7b+8u3l44/+XPStXKKFMyymmW++9NRUJKT9Z9PQX+Da6vakFAUPmKD9cpjzGW q601v2iNJs/MAX/joeey1rEy4hNkhak+GHhMiG480AarSp2RGPD4ba/Oje9bFjbB Tvcwa0wKbGU5UHiAppVK =XKZQ -END PGP SIGNATURE-
Re: Certain (mailing list) emails NOT being threaded ... trying to
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Friday, January 8 at 12:38 PM, quoth Wilkinson, Alex: However, threading never ever has seemed to work. I am finally wanting to investigate why and if possible how to fix it. Do you have strict threading enabled? If so, try turning it off (unset strict_threads). It's possible that that mailing list is stripping out the usual email headers that establish threads (such as In-Reply-To and References). ~Kyle - -- In all affairs it's a healthy thing now and then to hang a question mark on the things you have long taken for granted. -- Bertrand Russell -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLRrklAAoJECuveozR/AWe9iUP/RMlLM5mfDLSUXF2WOJwjyGV UC2QIG2bp5eN9cnMfkGN1NBdVk6Ea9NTMG+5CJoJ3ya+V+MKRgLN1hdzz5ZCGiuZ friJcVx9BDlRvgFto6Xfo9YwK01O5sdBIGAUbPmZNY98wfnP27Vp+upubsuW/5Bx hqBKrnP5q8bGfbmOgKI8VxTZrTjvkOd7lLPkqDiUsUwrNFe34BGGr9CHR5VGmvO4 8tPiqC6CQp01iSPMmwyu1eXZVN/3zOlbZTZFTO/C0sNE31o2PCdFDZKJawYaWFh+ WuLt4wXf79uT8mXSNAdMCccNlHxgcBAjmd9RyrEdMb4prc7kkMGLrwU6XUbuaU7V JucQi34MvOCNi0rJ+GUV0j5zxcImeHmfQ447KXNR//7iEtkIEHnWLyW2s2Gma5LF hd5SiGUFlfcoMQj49qsp4ldyU70r4t4ncs1cyajFQeLzRp/IFXR3Mqp7fY40vOr5 3l4UcY6llQC+5LQ5WZNRlEwQgkSyF2flSLjL5nirfVf8vMx7NwctANGs4Ueb0o7H ysA9kiACNTo5mB6KVev+3/a1m0+HR7JFIvirX11hmUMT387WrvgmbvroqxSnKBRs 3wNKDx2SsnIO+9LVPqhkgpT/tUm4POX0JDOmY9DbTmxj2L6N4MBsGC8CJ70mVaHK g0lHComUtqiKVsmysvKO =ZTWB -END PGP SIGNATURE-
Re: time
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, January 6 at 11:42 AM, quoth Ravi Uday: Kyle, This didn't work. The mail header shows : Date: Tue, 5 Jan 2010 21:59:44 -0800 but my laptop's time is : Jan-6th-2010 11:38 AM. As Derek Martin pointed out, I got the TZ value wrong. It should be: export TZ=Asia/Kolkata ~Kyle - -- He who joyfully marches in rank and file has already earned my contempt. He has been given a large brain by mistake, since for him the spinal cord would suffice. -- Albert Einstein -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLRLUnAAoJECuveozR/AWeWsEP/iCWPJgPqihMBh8nV3Xut00a WarmmVnbyYzuyeeXZMB9VoUUNRLjcDy/lO6uc6eyr0GilGNdSz0Qdzuoq62Lq8zb +FrZjGN00o6OnogAfaO86vLEOe2jSaFJ40vTdxwgfQGAyDVhXh+v/CBBlRkSoO4e CiZO022yrRG3gTc/B55qFySLhsfmM7SQB/ke1rq5fkVDkrw8QmHbNRSNH24CFUzD sV+aePUgzdF1CbNbcwD3tuaUcBtraOY+K6Rufse23fhiBCnnY32JwffEPGbo7I6W 8JyfOmZg+VbOJDxCQUy9TSspSolWf0bnBJiZc4dr9Bf8oFIv6sw3Hnh2rEfMjYnS vjnZNwE4Uz0sprDWoY6YFGpdzEamGulVVEsV3UA1Mwd81Tg/olNutYCubdibOyCt Wn0qNRzLjyOFc46QSasPQSrQEWUdoc0u9LuhEhZP2GFbOjE3V0fdc0iuggWW6yCr YiTbogLuZF1HUPy+u9Ltfd0Mg/MaM1WaHtXjZRRxKBsWSjF+wlNIJJ2s6bi3wfU2 pQtIcpmhDinxXHkViJ6B5J/XYkN/ywtC7HnWgYewMT2oA7rd0FO5MYblh3vEX1yP /IDE8V/pV39b3ojnhpBSlLCq1U67w6Ce3eoQ/NbOCFyXKa+ocdOoSyHiqB7+aF/U aF/yO+dWwIV9IvkSmHIW =wcqb -END PGP SIGNATURE-
Re: time
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, January 6 at 10:57 PM, quoth Ravi Uday: It is still the same. on linux : bash-3.00$ date Wed Jan 6 17:24:25 Asia/Kolkata 2010 bash-3.00$ On a new email, inside mutt the header shows it as : Date: Wed, 6 Jan 2010 09:24:20 -0800 Hrm. I would have thought it would do: Date: Wed, 6 Jan 2010 09:24:20 +0530 Because what mutt SHOULD be doing is printing the Date header in the local time (according to your timezone) and then specify the timezone via the standard offset (which, for IST, is +0530). What mutt does to generate the Date header is to call the system function localtime() for the time and date---that SHOULD produce the same output as the `date` command at the commandline. I do note that mutt's source says it's optimized for negative timezone offsets, but I don't know enough to be able to tell if its calculating positive timezone offsets correctly---it may not be. ~Kyle - -- The important work of moving the world forward does not wait to be done by perfect men. -- George Eliot -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLRNjvAAoJECuveozR/AWe86YQAK13Y9HHD8TAta3T5o8I7Uvr PkuApIsMHGFBS9fzZXFwMuhGn1GFhHLN07bWHOERyzYIlyslIEAgnLeYOekce15f dWrAG8kZXw3ix+tZWDm5z5fNYKSBcNdHKJxOI5kaL+rqOv6dgxc6w6wMfF0xFOvP cm/f+kZ6q1ZY+fjmiOyr4nbWqOfjtzTCjW5ixIQLAJphdzd9fPZgK5fJUWV5ph9A fizldLWTM5ORnNd4tlNLxH1PFew6CxJM2WTGBjzErCqeYqKCcYVzXt7hPdk4xz61 DZNC0rNXQaU18BGJhizIbu9QWHAQrCTVl9zRdlVbmZ64FDAkY5ycu5mjqMPSWUko s3Yehst84MdiH9X8iD1Pw4+31+R6wGzBSGOqI8hiJ0rUmiMkagKk5r6/4w5BDWMv P0C/WcosLrL1cxx/ILRtPvkKAuOQHVtRWm2J6TaMygtaKKU5GRWQlX2BklVfHyne YaVuuqr1x7M0BP/h9wWedPNZsm7qg3Tcf171y9v9cIUGo4AWNY2Mu2/PeKlAnC4O SgUBZJ3ooEv8GWho/C+IEJ+01g6iOWkyL575oBnUAjYpysySkLWIIemInurUDQzm LDwzGo4Tmh6+c0T5nmFPhhnePfqzknAC5OSvAt8gwO5MMTgCb4ooKG5emoISV9l3 w7a1NEzRBfBExvj/jCzF =Vto5 -END PGP SIGNATURE-
Re: time
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tuesday, January 5 at 11:42 PM, quoth Ravi Uday: Hi, how to change the date and time format from PST to IndianStandardTime (IST) in .muttrc Add this to your ~/.bashrc: export TZ=IST ~Kyle - -- However many holy words you read, However many you speak, what good will they do you If you do not act on upon them? -- Buddha -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLQ4MBAAoJECuveozR/AWeg+4P/iuYmERmpA5Bz5Be6abU1/6l 3I/CzVLamlSKfWvPeXvalTBYZKv9nHb4Hqw3U8tmoVC926aLjl5bfb38dbrHmQ/j DtJE9xkOS7wNU+T13l4p3IrZaCPua3Ld0YP6nzvWrRpnlJXgxbJsDn/3tTlR8VZ4 /bGGwOq9Co31wskN0q5HYHs5wUrrmb8j4FMFur+7iOScRkvU0t+9ltDYxdSN84YT YAhmZ8NIpm0r9RWQniREwqP2/oZiVqhoqEVbBbte2BGEajy/0oOJLVZ471j8fSYy E42xYVSU7sEMKQfIUG4P84Wkw7COszL+LR0iLw0XphIzYeGx5X6Z6EnArqINIBa8 T3EUiovCW5PRCraW+LOCOWKkD2GrDCwyfmXs3x25sw2YgnE/keskEt3kYNmwSjCu HdNG2iRsGh6kOYvgWmfgBXFl7hd37aSRq18B5pijMw69aIBjKdORy3jy1TpNamst AtZ+TuSgL8OecRXPYPCMZJPxmRo7mk5BQUFRMm+U8xaeF2uXYfbs2/y48LpSnaD5 zILkjzIw8r04cRo1JEehMjETozo0BOj7JCESmw6KDpMXKrcLUJ1taZbkDkYc/R9b lkO0Ri/LNud132CuTL+VL3l9YNNHDocSAKWCdBlCznT5l0mH4iXGqCtakCx2BKM1 c4KCEjULj82nyvEfHfFc =WlUG -END PGP SIGNATURE-
Re: How to count new emails in mbox format mailbox?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sunday, January 3 at 04:39 PM, quoth Ionel Mugurel Ciobica:
You were told already...
privmailnew=$(grep -c '^From ' ${private})
inmailnew=$(grep -c '^From ' ${inbox})
That's only true if and only if the mbox file is NOT in mboxcl2
format. Many mbox formats (mboxo, mboxrd, and mutt's favorite: mboxcl)
transform internal lines that begin with From into From, but mboxcl2
does not (it uses Content-Length: headers to reliably determine where
the next message is).
There's a good description of several of the common mbox formats here:
http://homepages.tesco.net/J.deBoynePollard/FGA/mail-mbox-formats.html
~Kyle
- --
Important families are like potatoes. The best parts are underground.
-- Francis Bacon
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!
iQIcBAEBCAAGBQJLQhbGAAoJECuveozR/AWerQAP/R+gajViBpTaPTREIPQCrwjP
szvTOmzKaKBkBmqJVk7etzdMRyAtre+Kzupwc8gHO370Saf0beee8e3MWA4hKXPB
EFhSDlrUTFquf0EvZe2kUfXgr2V2VeBpujX2lcXMY7rNDS8Z7jw67tgCKg+PYLp4
GkvgqDiSwH/WQrW81IPhRC86z3kBPsQqUuO2ghe+zQNl0i9tOpVF/3ygrEjYTkio
7IuXfTOF+mBpoEBH019TNMjVZxE5OBfT01X0curwEVimRgWUlU0DlXfW7YqrIUVY
AhfxH2SptkMZ+ttSmpzIcp2TI5FgpVFOOUu/sgov7iDjite+lgGYlIJWaDVBA20v
30DewWZXZ3WdDuiMWlRBIGgKnpqWNnx2weTAvkxtBp0SKb/8x9hm8uBPCHTSNvqZ
5XjJAUAsGvK4EzEWUKy2ni0KyVNkPgNOjcMTT8KYr8I5vPTfVKdLjTZ3zwDOrDlo
2g3NRoGkv7JgtNv+je45tXygO7nXAQ4ykAkID4/+Tj64Vk61WOx9Sn4fv5Wk0Kuk
JJXEvFwdxnYsVe5keugBVJDZlcz2oszMyi3p/Iqxrg22M4M7VojW1i8WMZ0ze0sv
s6PFEQfI2DGKF3/I5aoJYF97WLA//uJVT2OXEYrlPFRX1Blep1M6ar/xLYQVYqIf
CxlRmlDmsPQ7DRqyKIyU
=oLzI
-END PGP SIGNATURE-
Re: Is it safe to use mbox?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, December 23 at 01:41 PM, quoth Derek Martin: On Wed, Dec 23, 2009 at 10:17:57AM -0600, Kyle Wheeler wrote: Now, I'm assuming that you're storing your mbox locally on a standard unix filesystem rather than on an NFS-mount or on an MS-DOS partition or something similarly weird. Does mbox have issues on MS-DOS partitions? I wasn't aware of any (though you need to be careful about using mixed case). I was aware that maildir does, because on MS filesystems, you can't use ':' in a path. Honestly, I'm not sure. I know that MS-DOS requires explicit sharing, so it's easy for a mail client to prevent delivery of new mail by accident, but that's easy to work around. And as long as you avoid those, you can be assured that using mbox is *safe*. It's not *efficient* (because everyone who touches the mbox must lock the file first), but it is safe. I really hate when people say stuff like this. Efficient and fast are two different things. From a parallel perspective, one giant lock (even one giant write lock) is NOT efficient, no matter how you look at it. It may well be *fast* for the common case (especially when the common case is one-writer), but that's a different issue. But if you're here to rehash the fast argument, I think we can't get anywhere without pointing to the CourierMTA's webpage of mbox/maildir benchmarks: http://www.courier-mta.org/mbox-vs-maildir/ Plus, while maildir doesn't need to lock, it does need to open(2) every individual message, whether you're reading or writing, which more than makes up for not having to lock in terms of efficiency lossage. You only need to open(2) every individual message if you're reading the whole thing for the first time. You certainly don't need to do that if you're delivering mail, or deleting mail, or marking a message as read, or what have you. Both folder formats are efficient at some things, and less efficient at others. Which one will perorm better for you depends a lot on your usage patterns and the underlying filesystem. Agreed. Fans of maildir like to sell it as being inherently better than mbox in every way, and that's simply false. I use both, about 50% each, because for my usage patterns, maildir is better about half the time, and mbox is better the other half. [This is why the fact that Mutt behaves (or mostly behaved) differently for the two formats has always been a pet peeve of mine.] Also agreed. That's why I like Dovecot, actually, because I can use mbox for my Archive tree and maildir for everything else and get the exact same semantics. ~Kyle - -- If after I depart this vale you ever remember me and have thought to please my ghost, forgive some sinner, and wink your eye at some homely girl. -- H.L. Mencken's Epitaph -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLNM78AAoJECuveozR/AWeYZIQAKbACnuGtZCmIxC4IxJSUpfy 1hd+fHLz6xB+wlkX1ET6n+JX/OefRlTa1dOyPhEswLNiOccNyfVBm53LE1awAyXe Ose9yBqDSc/Fw6iC2SFsALqXF9txFYmKBtH1aIfV4XyDPJvw1wqDI76Cm487iVVR ot6udy+AMBuR2er/iYQ44hUCyIt29j4+ghcxg9aSnXSKHzO8J5Xg6UpBQr7jzBT3 yZW8+dTCC1cmATq5Qhp/z314DU3Yu3Fbrh6vQ8QM5Ywj2dSc4aWYxxKysWOF++ET wfa6+LQI+kCr51CGDYSZ38by71j+JU30htNa4Hqb0u6DiYtAlC2ak6YrAgZsObYe 61ZWKSrlSdRy9w/ldyQhbB0ILKxdFhCtQ1V+7BA9gFo+7AiN1GfIc9nLPMgVtIV/ AD505XxS/sPYH0o5l9sl2KF0wlN/cevGVcipzGw33XEVJsFr0qxOgh2NT0mtYEkD NWIrn8J1EzEYKGzYptpD8/u1SSuchIUMPSJqyMS8NyL2sBmNTNjYNCt52c8VIGtB 4em+EkLeH/xOogyP8URg/AAJhyYA9937o+RS87tpLAj80Wp7/bb/JZ6nVfOMdFyn V7rP7T0hayljeKgtvnCVZ/cAVuj5V6H1tRpz6mCSacujWFyklmGfmnoNqtBEDX1e 6zjlrky5dIRtC5NEdum9 =BfJy -END PGP SIGNATURE-
Re: Is it safe to use mbox?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, December 23 at 09:17 PM, quoth 吴悦: I want to use mbox mail format, I want to use the combination of mpop + procmail + mutt, but I have a question about the safe of using mbox: my mpop keeps running intervally in crontab, when I'm in mutt, when I do some mail management operators like deleting, viewing, is it safe? I know maildir format has no such issue. Yes, using mbox that way is safe. Now, I'm assuming that you're storing your mbox locally on a standard unix filesystem rather than on an NFS-mount or on an MS-DOS partition or something similarly weird. And as long as you avoid those, you can be assured that using mbox is *safe*. It's not *efficient* (because everyone who touches the mbox must lock the file first), but it is safe. ~Kyle - -- Strong coffee, much strong coffee, is what awakens me. Coffee gives me warmth, waking, an unusual force and a pain that is not without very great pleasure. -- Napoleon Bonaparte -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLMkK1AAoJECuveozR/AWeR4kP/ipzJIcS3dIslLdi/AfeHW25 tiZtqp6MUccm09KwP2cAy64XS6vLGKVUz1cSn4BqYB+9sfpiNxjxTX9HR5avEPa2 5cfQwqsua6GO9d7TIoJYBpE3ftSFCdcGkgUnHhr6NnwUh1quC0whSF/l3gEaTIQ9 XInOaK0nomvJDnp1ScPlz0APKe+jtQLr6QL9IsfCCLzcNRvQFakH3cy6pFWzHi8R gbfNuAf2ZGKpus/Wn6VL/dtFsUdFah+Xkd2vtAZbcGbgXTs+O11NfyE1V5LcAd0X iNMWB3z9Rlc8MNU3KvnChZVfTGguZ3LpQxeh2bsBKP4yvJqJs1fywAU5Q7SQJsZb cQfxVDLRBEWPGTp4hWkj3Qrf/tl7QFE4fAghPQ87h7wmPMu4H8LbZnDeU7zM11wz XEOFVtcEzJDtxXtjwSq+h2EIn7HrqY1eFwHmBMMWwlIUAND1WUf0IeXDfMN9xy6S gSOHBy/cvXGF0dirC1gk3rK4Igqou842nhbdvrmIExTUi3DY+f9meoZ/kfIrdwUf 3mH5grjiP7IypNPeUiAh/kYpQV83QfkenjZ59Ho7hw7oG1+0kQR2UohAzypIIDLy b1iUsSA1C0bA5yBbbiYT75FWJqQ4zijKm+Cvk8Y7JP0mdcAQnH1aHuAT6o0E/2ss dmMHPuCRc8jSQ9lx9XOp =3v5r -END PGP SIGNATURE-
Re: reviving GPG with mutt
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, December 23 at 09:27 AM, quoth Scott Jones: A few months ago I moved my mutt installation and mail boxes over to a newer machine. I believe that my list of keys and all those other files and folders made the transfer safely but I unable to sign, with the passphrase i had set up on my old mail server. Where would gpg/pgp save all those keys I had gathered from signed email? What folder name? ~/.gnupg/pubring.gpg and ~/.gnupg/secring.gpg ~Kyle - -- Where all men think alike, no one thinks very much. -- Walter Lippmann -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLMkYdAAoJECuveozR/AWenkQQAIQ3aK3UI/t1D9GdxYdCCDjK d6hbCS1Flku0chlKMP4gQJRgkPM+FyeWxZgetpObEmKsDWu4f3ftk8Evds7mcPTX UMuVul+bVZPZdoyq8hOlOKSIfTq/IHcLkbSM7O99KIxJgNDo5Y5XBaSAvhrJXvdf 7mIE9ldG8dJ9nV+/Kpm9aXGqkpsEwnIrgbrOtyGrWvxIEBNKuoQ0yaDSiam8IR6z vZ2pNUOEH7qZMRhj5RuCbMHlsG+ibuRTVV1JbGoPKR92DA6Anr45LHbNCjLUp38Y g/XVOAPCgadMS9sbq6HlC9vSVvwA5PQxxAbD5NraAR+a9wwLeVs/Jrg00GUTjURT zpLgwp3ZAFFttuvu82tyNBdh9qY506x/5R6wdBWeRHJy1a66vl6uFxUNu9511LEe oT21L/eODF3vQj+FXtRGHq1Ax8mdyXotbswdoVURsw0UbCkymrgL3ie1s2wXXFa3 kB85wAOFlKRtL/NOI8YXqELF0ctwjY1YfDpmc+UGz4xBTXFi6vHdcCmT6TkXiBW2 3/v3g469fUG2g3Mll+IZQWTHfuB2EjCjimkK61SUDsaIRAFMoVoywngOGGM7U6KC NjISnuo9zjfNciU3Bu0In7COW/DkAiZURBW6Odvf1cFp8wmoE0t8gk1pnBpO0VMH 0ve5c4jGNzb4HFBEcFsa =F3SK -END PGP SIGNATURE-
Re: PGP/MIME for Outlook (was: mutt feeds more to gnupg than it
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, December 2 at 12:07 PM, quoth Kyle Wheeler: On Monday, November 30 at 08:04 PM, quoth martin f krafft: This is going off-topic, but I'd appreciate a response. GpgOL might be able to decipher PGP/MIME, which would be a grand step, Apparently it can. but last I checked, it couldn't create PGP/MIME, only inline. I haven't checked recently either; when I get some time, I'll fire up the ole XP virtual machine to check it out. Unfortunately, all I have is MS Office 2000, which is too old to work with GPG4Win. Can anyone else try it? ~Kyle - -- Scientists have shown that the moon is moving away at a tiny, although measurable distance from earth every year. If you do the math, you can calculate that 65 million years ago, the moon was orbiting at a distance of about 35 feet from the earth's surface. This would explain the death of the dinosaurs ... the tallest ones, anyway. -- Unknown -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLGa1uAAoJECuveozR/AWemQoP/2BK8TtLVNaQ91tPkXHgFJ/+ Ox477aaCP3BjXe0DcJT++tF6l4TWP4vdpN9J82vMqEHmYW73Ebl46RDABryKVcpF mlR4wv6v6dfChV9WAbW4VljZArSnSNrv8u5nuSoInDUmB8p83sQh5Xyc+Ghe3CPk kzqfanAN7sBEwd0fTkDa+ekkTcwEfVmWTmJgytgXq7YsM2ahKJXpPoJIklyksmOS 6mM+gyaSeEuiuu1cJmCB/NNz9mUQRbf5Y54cvZwpc0jgfhjmvOUOXEU26u3ot1xU COSw1VKjxpDj4ZLVQEF6cUBPDKxNONfBLaPnAu8zt8M2j7Q/oh28NUy9+wvad0Sl Kqgahikj6CiRTRtyTvxWM/SaFiBQicjpr17ACAw6nZ1uLGUKaqhwa8ibkQEDsUdB 8rBr3+2i4L2PR8X7TWDFBqVVKJNw0B4TsqBP1kMT8MTASpTfrKGWWqyFnOUcXi0g lb3hGX4lZOEuR2BEJ3HLe1gcJwGtu7RmuBA7bdsjtc5/0V0/V1xGzxH3e8jjSDxI 2jNuQm6CSdTvTBJaC61cf6lXs6j8sGSoqH9zhOakDOhvFRfc3+D2c3dhOBr37frF EmgFFPotAkm1CsORrzuWypXvLt4SYz1ewQ1JJVK1r/erfR0zqOxuGZ5OYM3cLLzk zFBnHB7EfYhTILlb85ru =bRtY -END PGP SIGNATURE-
Re: PGP/MIME for Outlook (was: mutt feeds more to gnupg than it
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, November 30 at 08:04 PM, quoth martin f krafft: This is going off-topic, but I'd appreciate a response. GpgOL might be able to decipher PGP/MIME, which would be a grand step, Apparently it can. but last I checked, it couldn't create PGP/MIME, only inline. I haven't checked recently either; when I get some time, I'll fire up the ole XP virtual machine to check it out. ~Kyle - -- It is dangerous to be right when the government is wrong. -- Voltaire -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLFqzqAAoJECuveozR/AWeXooP/2+ozQhEx3aFpaGoxWA6WN+D njMmoQZV6FqWRd3iHs4oZJa5ZeFy4KrjS5oUqgZhV5jPrYhRxJyqcQKCp3Yap2Tj DoO/q6AMuEZiWoe6lTiLXFU299AvIN1P9lf56euzdlZ2a0JVFKdV1vK0La3M+FUh TZV6B1EdGaFI/qSsygrsO0He4LNUqlWllKAofT7lQkN/gYNA3ahAk7ODK0qfMSuW elNrRU9JlH2X3mz1W0RkOeVO1JAKQifKmMOgjulAqNL+mURY29xnBmdcFPCcdNeC BhqtG6yX0xA5e4+Tx3BgoF4MCRhzgBKSe03Sn4zlwBn2cOKe2/PnMM+sxESaVXPn f1zIjvYWUyAOPu/SDSstUhOg/98O9ePm+4h6e7SBCk3DMsN8sG8GINPj1cEn3ukJ cN9ij0/5Y4L1jzF0owYKY9gu3lOUEv+q5DFzXUKmrw29RQrUfULCvu/z8BrQ5zJR CvxMqe4ywNjzQdItH65dlNnVgG4rgpUWTI+Eo7Ywik7/vZ+xLxLsJ/PYQ/RTWywg /rqPq3I6/tWHmdkdRTs1Pv/+VBo5ilXdN3xS9IBixZrWCDcj7f5dqfR+ALwHb1Rl CQopq5uXLHkTajgdzwEuDu01njhcmAxuL00YqvbuD7AOEBUTbFNSCn2ojrL9nOKb Dl6af2WvrkP1C8SBWUQ7 =Rw/8 -END PGP SIGNATURE-
Re: mutt feeds more to gnupg than it needs, causes invisible/lost
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, November 30 at 09:58 AM, quoth martin f krafft: The problem comes when they aren't your peers (but e.g. your boss), or when you deal with Outlook+PGP people, because as far as I know, there is no way to do PGP-MIME with Outlook. ...Or if you deal with (Al)Pine+PGP people, because (Al)Pine cannot deal with PGP-MIME or any MIME format where one MIME component must be interpreted differently based on the contents of another MIME component. As for Outlook... I guess you haven't seen GPG4Win? http://www.gpg4win.org/index.html It supports PGP/MIME, S/MIME, and a few others. ~Kyle - -- Those who agree with us may not be right, but we admire their astuteness. -- Cullen Hightower -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLE+cJAAoJECuveozR/AWeOBgP/3P3Zu5vJ1WgPrylpoZZ7Dll jyFSoPTAl9WRYwWFh5K8ZvjjuUlaQxEyxveqjHNsiiwmm795DqAQjcjLMwUtZt5c p/5ZGuH+wrvyLLkPTWZ7VV4T0Zf/mKC4yikgx2qPRLP6NG7cUq4hBkDdyhEzXNGp NBQ6faFmxBT5miO0VoBAgq7Ytkv8r2RgOXJW8CSxKPaca/JFq6OZJgtDIbhlNda9 jikQg79/kc4ySJu7xOenL6lzLSYXccwFmfREi4yRZVBn5T1LD4O+pd+ZnMnvwLFW Cp5+cHOInpff/GSxQ1GO9q7+01QLL5zVDyP4KArIgLcSr1eb+eTcXLkZWg+nlefJ /UCAEMAWON/tm/R5T4ioKwn5Z9urd9oO9p5cp+p+nJEGWVmaAjRGCF8ViVp/uIsu XZ5sYqENQis93rauTpoiGAHHS7y+16KtD9aFKUCgX7gUL5LsqpMmx9HDg1bXyoqS AEat950MsJQ0sd9g1QQEnMEtbG2gpThYm0hzEg6XrexRH2LcfDLD4ObnNUbQw7RF RCDUCBcIQGIazyGkhIE/uKRioQmMU6dqUEjvIKlqQAxOiEN0P3kM0NeZhpi+g2iT +EKIOTlaavdJJOUXSLA77L5uU/SLIoJATrRbYyTCsR0zcoYCcqS6SGwwkNVhZ9mY 6hPCJhxB0sOxqQxvP6wN =W5VY -END PGP SIGNATURE-
Re: All mail meta-folder. Possible?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thursday, November 19 at 12:50 PM, quoth Salvatore Iovene: I run postfix, procmail and mutt on my own server with a fqdn. Meaning that mutt reads the Maildir's directly? I was wondering if anybody managed to achieve something like GMail's All mail meta folder. Sure I could have a procmail rule to copy every mail to a all-mail maildir, but that wouldn't synchronize the read status of a message when I read it from some particular maildir. So, with maildir, in order to synchronize the read status, you need the filenames to be not only identical, but you need changes in one place to be reflected in the other place. To do that with raw Maildirs, I think you'd probably need to be able to use something like the FUSE MergeFS to construct the All Mail folder. I think the standard MergeFS (http://sites.google.com/site/tkorody/mergefsfuse) is read-only, so you couldn't mark messages as read from the All Mail folder, but it would accurately reflect the read/unread status from the other folders the instant they get set. That, of course, would only work with a static list of folders. Dynamically adding new folders to the merged folder would be... hard. ~Kyle - -- Coffee is the common man's gold, and like gold, it brings to every person the feeling of luxury and nobility. -- Sheik Abd-al-Kadir -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLBWjUAAoJECuveozR/AWelV8P/3bR8v6EVSVO4f0lMqZyDHd8 eVP30dCeYJbP7wH9v0Up6MJN/hJXIYSisCQEkLbB8rHr3WnpPjdHQjIOO11GFU+E GR3z967qMyphRT+TDJ2tPYNXslodlAQBGnQn6Zz0sEYVC2jmg+QdG+5kvg5Sp8fL rXMWTcwM2jeu8EMFk11sH/iWuCur3ZGM2o1QClet3LmmMFbihtQRU+uZG5GCks6E v2jg887omHezueLgZoSueh/wZvEjiRVLmfuo2eHcYPwm53Z3V8wkdbkb9/C6jyp4 Yl1p3lq3bRrq18llutUI25ooTHhIPgGrjHDGZ4w1XWK4lQkThdmVPmE+7c+fgGLa lhawGWHWLN+7LhEUUbw4bXkUNuTBmcNdXGhs878QJQM0Sqe4i6YhG4ZkWLNS3Iy0 GdkZnsRfaEMR69B9yrbKyT/oLP+Xno+YN0aUqeDzdNC+msHm/2zLwipbaH3gX+vy zG23U+5bzHbEelijugh/w/y3cbuXpCdHT26nxvC9TB7f+kQsBbYNBIVi74V9YvkF VaRH+AsxQpq1zKWoqEud2POeurYk6ZWUhUif9S4+pulA8J29QvjyIqfpizgp2c6G b+amXNEjyj2nyNVO6hr0+jPREa5rw7hyZNfRdgAs94D3ezWTd9vKqZOkreJirHs1 40h5YsocHYi106KlCtf9 =Y5VI -END PGP SIGNATURE-
Re: All mail meta-folder. Possible?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thursday, November 19 at 10:57 AM, quoth Noah Sheppard: On Thu, Nov 19, 2009 at 12:50:37PM +, Salvatore Iovene wrote: I was wondering if anybody managed to achieve something like GMail's All mail meta folder. Sure I could have a procmail rule to copy every mail to a all-mail maildir, but that wouldn't synchronize the read status of a message when I read it from some particular maildir. You might be able to do something using soft or hard links, procmail, and some special deletion macro. Might get kind of messy though. The problem with links and Maildir is that it wouldn't synchronize the read status of the messages. The read status is stored in the filename, thus, the link could be renamed (thereby marking it as read) without affecting the original message's read status. Even worse, if the original is marked as read, it is renamed, thereby breaking any soft links to it. And you're right, deletion gets even messier. :) ~Kyle - -- Die for the person who will catch a cold for you. -- Persian saying -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIbBAEBCAAGBQJLBXI9AAoJECuveozR/AWeeg8P9AxB+/EVd4wb1hIVN1RFvbOj DboLp2BB1/v1vvCB9Qgyb+b4AAiz4YuLNEiI3fYFCR1z3ypumeJpLs6H+S4+8KIk y+UM9QpT+N6ff7KvenkZHRnh192dB58HOlf+AI+04nF2xdtzKecF+Q5Uc3u/sN0m OI3FvvYOMj2db54JV1hp1+tvu2BxKWwp+lW/ktM6Gr6J9gXaklXQ2HEyUY77UQP5 FnS6MuDuhBocAQ9gLiLcfdQt6Vrqhrxra2+JqpCDDVM3Mi2ERkbVFnyjAp+X84NY FeKk2q5qEL8A2yo2JdI4LbI4WTU2E5RZL1Mo3vq3/K5aavGoOnBoRDof2vFWw5o3 JeJ4HsFbddxWdKsKcyVDFzJ18km1h162zHL3uUJJCLFChLMii6ZooU5TDbbpphB6 b7Fn1T+qFHaC7Mi2BXlpY0sZbhHzzZCOWwy5J0WNOtUHY3plzG2C3uSS+axX6HJk ae6oHVpKh1W6Kyg3yHL/I9ZeoKdar9dYoS25SqtalcP2VmACA5+xszUn9JKr2bYa fbfrbnO7868TiMj5EWVfWOUx6ZIFuaj/58ai91b1d0xMla+1bOr/c5TtQYSLbsli HoaY2ddvD/YO/8QjHHafuEWQ6mEt4dHAmkeO6RADKJQRm+IFTljEHgbc8TAcoUv8 Vfb0g2n6+us3iYxwTvU= =2Adz -END PGP SIGNATURE-
Re: intermittant hesitation after key strokes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Saturday, November 14 at 11:08 AM, quoth Robert Holtzman: When installed in debian lenny on my desktop box and on ubuntu hardy on my laptop it's fine. Hiting c shows the default mailbox to open as the next one with new mail. Better than alpine. Installed on ubuntu hardy, also on my desktop box, hitting c causes it to ask what mailbox to open and I have to bring up the list and scroll down to the one I want. Why the difference between ubuntu on the two different computers is driving me nuts. Okay, let's look at this more specifically, on two machines, change-folder suggests the next mailbox with new mail. On one, it doesn't. If you're always viewing locally stored messages (e.g. stored in your home directories), and if your messages are stored in mbox format, then it's possible that the difference is that your ubuntu desktop mounts its drives with the noatime option, which messes up mutt's detection of new mail. Thus, it doesn't suggest a mailbox for the simple reason that it doesn't think any of them contain new mail. If you're always viewing *remote* email (e.g. accessing your mail via IMAP), then it's harder to guess why mailboxes with new mail aren't being suggested. In either case, you don't *have* to use the big list to find your mailboxes. Mutt's change-folder prompt can work like the shell: you can use tab completion to make it faster. For example, I keep my mutt mailing list mail organized into INBOX/Subscribed/Mutt. I have $folder set to INBOX. Thus, whenever I want to read the mutt mailing list email, I simply press c=STABMTABENTER (where the things in brackets are key-presses). ~Kyle - -- Imagine what it would be like if TV actually were good. It would be the end of everything we know. -- Marvin Minsky -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJLAC5oAAoJECuveozR/AWe6n4P/j9a0+NgrxNzeA9nmNn2xzbE /yA+FpqskUa587S4vKSGu3pTL9voijhepzV7eNJlUfWfqfz52OGsLbUZS2XMoOTH NJ8CaLvxFupOjOUal4Ztn+7KidgVkq4M89wJDmkvdzvnwQbbKdM7Tu+/mgo9LDo3 qcSwrrlId3JiViR4LoMy0ersiPOHx7mYzBqiBUJn3kyVzN5aNE+Yo4GP4oLHB9aN mZ9SbsRwbwWqdqdqALr8DDYpuUgHlpM8u23hB6lyWPhcrQms+jJVhstcZpgE+prd OuRJ/IsM5ePVyb1SwpphLrbgGiOOlWvMwkxiWvxGw5aAM7idXoB1gMupXCw/GTSV r9DDdOMA8qXay18S9G7WiNYq2lLFpRwy5cCEwtsHT3CzMMkvEEf9vXmXoJ/Bk4eL 8gBjolNCoHEP4J2lxdoQF+spww8RQeXCSdgHJmpl26Y9teRc/kX23nnMtxkIx5p9 OfsZIlqgQcmXTECSE3j7U4K6k/jMNyc9piq9mFFjRb/NsXfV3QgNaSwVBWgw+6/7 q0pQ1B7fdy9Zi2p4rw06U0HRpzZeWsDBpyWFz9qrvA3ECF3MBiAr6UhgyrbzAvzp 5GGrKpTMuo7Ucxe/sA9qLLir62ToMwODXxOByRX6oI+9idVtbmqvZUzI8sYnt2ki wSkIPxlPUiFst62JcCXF =rOhH -END PGP SIGNATURE-
Re: intermittant hesitation after key strokes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Saturday, November 14 at 11:41 AM, quoth Robert Holtzman: Doesn't that just scream this programmer knows what they're doing? Probably, if I were a programmer. I got part way into C some time ago but according to the actuarial tables I wasn't going to live long enough to get proficient. You're talking to a 73 yr old retired mech engineer. :) What's the phrase... learn like you're going to live forever, love like you'll die tomorrow, and dance like nobody's watching? Anyway, I understand your point, but as an engineer I know you can understand the basic idea: testing shows that the so-called shortcut is actually not as good as the more typical method, and that suggests that the guy who designed the shortcut didn't actually test his shortcut to see if it was actually faster. ~Kyle - -- I have great faith in fools; my friends call it self-confidence. -- Edgar Allen Poe -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJK/4QvAAoJECuveozR/AWeauMQAKb7aSD1e2sU3DOpgc76wFfs HrJ5Ycy8sx8xjWB3hHrTYLZIMCFQb0s8C6ov2Zwe5XUhPoT2LI18iw38+9ouMeE0 kIhn7H3emUw/e4HejSiaxV5Z/z5DZrJ6QWdC0qEAdi0Di+pc2Hh/idENH3adqpRt WfFZocAr6KMRasJvj1cZX6PPq1r2GNY8tdJHQ477SfVhRwGb3/NoALMW/zlkHBoK JOoJQ9ZrxV01tkYlKAgRK/ICIP8ysN14U5wy8q+75gPCRwvoRaEMdV2bfgvDiRBQ qvpN7cCbkLrg+jc4WHX/hHP1vuoTDBfz69zVMK9z09Df4+A0jaQspWaIsNgk9Cxd O0w9lcu67fqcitfTwQbgOyEt2B26eNtSRzwKUgGYgk9jN4qMU0LUVr36IQPyr/hj F/u7VuwbtNgomOKHa4Yn4zlT6sW+mWKodxb7oujemGyt6Y8lYdBvMSc8uKLoNb8q 2bdoDnpfLnuAVaXoXmKdhtqiSbZLry5vhD/hdAlsXYm0OPoee13RY3R29JIx1Bq3 0svGqqUnaXeG75m6QCMzlzjv0gBqd2L4WhupCkbenRivMV+wIMIAdeqQuSuEePcC /vGcSdepTgC30spc8W3LiPR01qiXTTlmYLLi427KHOf5K1s+rhu0VcXo0RWXYHfj V/scLQDnVKWQG1QkUEwW =SvR4 -END PGP SIGNATURE-
Re: intermittant hesitation after key strokes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Saturday, November 14 at 11:08 AM, quoth Robert Holtzman: Why the difference between ubuntu on the two different computers is driving me nuts. The ~/,muttrc file is the same on all three, having been copied via a flash drive. Any ideas? Well, my first thought would be the system-wide Muttrc might be different between the two. Check /etc/Muttrc on both machines (I assume that's where they keep 'em... you may have to go looking for files called either Muttrc or muttrc). They might have some slightly different settings that are throwing you off. ~Kyle - -- Do not seek to follow in the footsteps of the men of old. Seek what they sought. -- Matsuo Basho -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJK/4TNAAoJECuveozR/AWeRG4QAJ5/cHNytrVTh9merG1ozrvP huqAuO/4c+uUMAD0rbPQ6HXgVZKRAyNF972w1DeHanHKz/N3TY2lNl94YxoIXiol z26GJJsX228ptZq2YCKzsygOY5AEouZ2LWflKNTzt6QXDTCiSgyJwxC0RBWnFl+K b4AfC3XOcLXM1bRMjBEgoQyLXe0Iz5ti/Vfvj199tRN8rmMpMw9vG3XUzLdGOt5G mF7ndH0ZpF6oYkuSTfX/QERI2wCglMROOHJHrx4K68K+UeXMA0tY+dDYhEZlA3ji VoWXoLb8v99+oU57bUd58uerrvFVc8S1HWEf6GqOKhUShhp2UdKQU78u5zkhRUbg zQtGr4KSFfSNv/MmDS3S44RZNUrFk1KgwO7KwjXpjwO3SsbaKVtzIJdtaxkuv2r5 WeAkw5ZJWYeBAQpN5YOFc/nVVllolj16pFhPJ9FBSzzOaNMjVO0+HdpnVMXyQOVT P4VdQginAD1eURXwq4DlEzNVp30O4UT684vbX/5BRQU/Lcm/evecP6e1fm0M8eE7 NhJSpb1+DLmdvelLKbs/EEmK2js91A/R8md6eQU3xVpIgPx49UFZUajvPD4k9nhS MTt/6gPzCHrGj1uUrlLdZUY4VPySeJWjV028rxKYHC7yo9aw0/3YujzfJUbabL/u ku7R7GnFqyCazTa8p+U8 =RGtU -END PGP SIGNATURE-
Re: intermittant hesitation after key strokes
On Thursday, November 12 at 11:40 PM, quoth Robert Holtzman:
The only reason I'm running the sidebar is that I'm used to
pine/alpine where the mailbox list is a click away.
Understood. Personally, I find the mailbox list rather annoying. I
have lots of rarely-used mailboxes (for grouping messages about
subjects that I rarely talk about, or mailing lists that I monitor and
only check up on once or twice a week) that usually end up cluttering
up such interfaces. I like that in mutt I can simply use
tab-completion to navigate to my folders. (You *can* get a list of
folders... but you aren't forced to use it if you don't want to.)
Educate me (as if you haven't been doing that so far). Why ick?
Well, this comes up every so often, so I'll copy what I've said before
about it. Mainly, I quoted one of the guiding lights of mutt
development (and the man to whom mutt 1.6 will probably be dedicated),
Rocco Rutte, who wrote
(http://marc.info/?l=mutt-devm=112133798519807w=2):
For example, the sidebar patch available for mutt looks to work at
first sight but there're many things just heavily broken or things
you really don't want to stay in the code (like using snprintf()
and strlen() to calculate the amount of digits of a number.)
The sidebar patch is much larger than it needs to be, and affects
large portions of the mutt codebase that have nothing to do with
showing a sidebar (for example, if memory serves, the sidebar patch
changes mbox handling in some weird way). Generally speaking, despite
its popularity and its apparent continued development, the developers
of the sidebar patch do not maintain a presence on this mailing list,
do not have their own mailing list, and (to my knowledge) do not
provide any kind of support for either users of their patch or for
people interested in cleaning it up such that it might become
palatable to the mainline mutt developers.
And just so you know, Rocco's complaints are still valid. Check out
this example function from the current sidebar patch (published July
19th, 2009):
static int quick_log10(int n)
{
char string[32];
sprintf(string, %d, n);
return strlen(string);
}
Just because I was curious, I actually compared this quick version
of log10 to the real log10 (with the attached small program). Turns
out calculating log10 the quick way is an order of magnitude slower
than doing it the usual way. Doesn't that just scream this programmer
knows what they're doing?
So... now you know why I say ick.
~Kyle
--
Computers are useless. They can only give you answers.
-- Pablo Picasso
#include string.h
#include stdlib.h
#include stdio.h
#include sys/time.h
#include math.h
int quick_log10(int n)
{
char string[32];
sprintf(string, %d, n);
return strlen(string);
}
int main()
{
int count, i;
const int max = 10;
struct timeval start, stop;
int logsum = 0;
int *numbers;
numbers = malloc(max * sizeof(int));
for (count=0; countmax; count++) {
numbers[count] = random();
}
gettimeofday(start,NULL);
for (i=0; i10; i++) {
for (count=0; countmax; count++) {
logsum += log10(numbers[count]);
}
}
gettimeofday(stop, NULL);
printf(math.h(%i): %f seconds\n, logsum, (stop.tv_sec +
stop.tv_usec*1e-6) - (start.tv_sec + start.tv_usec*1e-6));
logsum = 0;
gettimeofday(start,NULL);
for (i=0; i10; i++) {
for (count=0; countmax; count++) {
logsum += quick_log10(numbers[count]);
}
}
gettimeofday(stop, NULL);
printf(sidebar(%i): %f seconds\n, logsum, (stop.tv_sec +
stop.tv_usec*1e-6) - (start.tv_sec + start.tv_usec*1e-6));
return 0;
}
pgpbAw6xhSUv3.pgp
Description: PGP signature
Re: intermittant hesitation after key strokes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, November 11 at 11:25 PM, quoth Robert Holtzman: My mailboxes are on my hd. Huh. Okay. How many is mutt checking on? Still can't figure out why mutt would insist on polling mailboxes for keystrokes unrelated to any mailbox (s, t, *, ?, etc) That's easy to explain: because you told it to. Here's the way it works: you told mutt (well, it's set this way by default, but...) via $mail_check that you want ALL of your mailboxes to be checked every 5 seconds. Now, mutt isn't multithreaded, so it doesn't have a separate thread waiting five seconds and then checking for mail. Instead, it has a single thread that spends most of its time waiting for you to press a key. Every time you press a key, mutt checks the time against the various timeouts. If it's been 5 seconds or more since the last time it polled all of your mailboxes, it will check all of your mailboxes when you press a key NO MATTER WHAT KEY YOU PRESSED. The key press merely allowed mutt to break out of its waiting-for-a-key loop, enabling it to trigger any actions that should have happened (i.e. check for mail). The other preference setting that affects this is the $timeout setting, which sets how long until mutt gives up waiting for you to press a key. By default, $timeout is set to 5 minutes (300 seconds). Thus, if you do nothing at all (i.e. press no keys), mutt will only check all of your mailboxes every 5 minutes, despite the fact that $mail_check is set to 5 seconds. and why the problem is intermittent. Well, given mutt's event-driven structure, checking for mail is inherently intermittent. But I think the intermittent delays probably also have something to do with the number of mailboxes you have mutt checking, and the characteristics of your hard drive (i.e. does checking all of them involve spinning up the disk? Searching through large unhashed directories? etc.). ~Kyle - -- The community which does not protect its humblest and most hated member in the free utterance of his opinions, no matter how false or hateful, is only a gang of slaves. If there is anything in the universe that can't stand discussion, let it crack. -- Wendell Phillips, 1863 -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJK/DWpAAoJECuveozR/AWeTygP/3qGHb4F2gVLZ9kDOlf8v/YH DRR1ZdWyZxemF+X36TK5fcze7lxBv58pQRSbQOY9jeHgB7t7AV/mtpc+LU2LpUgk ddPwr8mAjAPmsG8ozHnBvlSFS15Q1Ul8G7XVgaLsA0UPkhb5CxVM2PGPnHU9KeA2 Qzv5x3V+KXYGOtG00Ive0aCR5dcJ/5hLDkUADDXqEt0cEfE8cW2gObwDxl4OyJvB aPk9obAyj8AP8UKUCcAcs5YvHTCgcO0+/EGIbrWMwcnt3yteSOGR30MV8KMfxfDX o7bN7MZdOTwIpsjihcvomu++hGKTMKuJLIRQ+Ion1yQcZqVd+v634V05daq26+/G Ov/a+XEbpu+xm7EnRChI83sSLzsvWPl4HLgIDU5junK9FgiEWGo//M3XfVl5aelj +wPoU3ct7k8wSxPrwqWoqqOLowdVFejRndL3v+13aH2l3TB2Z7B02oJ0AkZiulFf rKmyEUWttYKjFxWXMF1jW8sYfcv27/gYkToOLp/6JzV3+cub46K553xVDbxDywRH Sm5xfW53+cdXCnA/EJjSiMKWl6mFuZir1RqKPv/OH7u6xMFuLWAyfOPuLktXsngg FQyrURtyMyhuohOdPU67uBRda+BhikB8ht+EiPh3LRWr9j/B5ejof0RcdEJ8mbh+ PIv0Redm1EFT2AJmlzfo =c+MZ -END PGP SIGNATURE-
Re: intermittant hesitation after key strokes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thursday, November 12 at 10:57 AM, quoth Robert Holtzman: Hard to say as they go by pretty fast but there are a total of 37 in ~./mail. That includes 14 saved-*, backup, spam, outbox, etc. Don't know if mutt checks these. Can't see why it should. How many have you told it to check via the `mailboxes` command in your muttrc? What I still don't understand is why mutt displays this behavior and when I close it for a few hours/days then use it the next time, the problem doesn't appear at all. Depends on the status/condition of your hard drive. For example, if your OS can cache all of the necessary meta data and inodes, it doesn't have to check the disk every time... but if it cannot cache them (for whatever reason, such as doing lots of other disk operations at the time, for example, if its rebuilding/maintaining a search index or something), then it has to touch the disk to check up on those files. One more thing. When mutt polls after a keystroke, it does it at *every* keystroke 1-2 seconds apart. Well within the polling interval. Something seems inconsistent. Hmmm... what version of mutt did you say you were using? I know there was a bug a while back that made polls happen more frequently than they were supposed to, but I'm pretty sure that got fixed. ~Kyle - -- Do not seek to follow in the footsteps of the men of old. Seek what they sought. -- Matsuo Basho -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJK/G3WAAoJECuveozR/AWeLkEQAK0mF0mRc9LnHo/vfsOxiMgY 4otJAHfHZmwGd1ae8MWymJGtzUTdMKSwaWFATlCDDEgHh8qc5r4LNAJjZsjwfSSw 04qqh9zWpKVfsHfv32weYXrxgW3aA+Y88O/wV8jlJMw+Es5/MhsNrj+LkqR8+8XX pawxE8ybmAsUhbjUbEFhYokrqpEVyweRZyN2t4LuQJCTplqyrVjJ4KWYurWOo9kn B4FHYhUVDuU2/k9WxN6l27Lcg4its9Uf2J0crPfh00eABJ9QfOGDsRD+uZdxy6Ty HUa+S5de5W7t/JUHulJ9BWV8zmBc6oS37102hAj1eQ7V0qfsp0VsL2OH6UzLfGBM o9DBwiOpbqbvd2P4Q0mTkPNeMtAh0lpLhOnMqtzpBMkFIFkcsVWDAbm1YSgztK0x xyr0NkOMppYKduGPnYLFQu+oYUkgu7XSv4j/eWi6jOVCEdkDgXZrRKSDdQ5F1ERM RSxnlhuBRAk3WdZxqsMlIF06AXKuZIWbvFmvCntyTm49eVqdTWK3Ok7ChO2mj7RM OqghbnM3axi+8AKXSJzTO3M4K0fSJvl49/TyoEwLnqBGkL2bkaD6fFt3Zn736rxf Q+jKf7/ipKcjIjOYHKf+w2pUB7hIvhV3o161ERQK1hSjfsCIuOoD57UwElHeWF9T yLIIVB/JjSWRqftn5RHQ =308C -END PGP SIGNATURE-
Re: intermittant hesitation after key strokes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thursday, November 12 at 02:44 PM, quoth Robert Holtzman: Since, to my knowledge, for a mailbox to be shown in the sidebar it must be included in the list of mailboxes and inclusion means it will be checked, the answer is...all. If I'm wrong please correct me. Ohh, you're using the sidebar patch? Ick. Well, it's quite likely that the sidebar patch changes the behavior I described. To get details on it, though, you'll have to ask the patch's authors (who, last I checked, refuse to support their patch). Depends on the status/condition of your hard drive. For example, if your OS can cache all of the necessary meta data and inodes, it doesn't have to check the disk every time... but if it cannot cache them (for whatever reason, such as doing lots of other disk operations at the time, for example, if its rebuilding/maintaining a search index or something), then it has to touch the disk to check up on those files. Not sure if this applies. The processes you mention all seem to be ram and/or swap dependent. 2Gb should be sufficient. Again, if I'm wrong a correction would be appreciated. Rebuilding a search index (for example, the `locate` function on linux/BSD or something even more comprehensive, like MacOS's Spotlight feature) is DEFINITELY disk-dependent, and has little to do with your RAM. Secondly, you may be unaware, but some disks actually have their own hardware cache (which behaves like RAM, but is hidden from the OS). 1.5.17 which is the one in the ubuntu repo. Umm... well, according to Ubuntu's web page, 1.5.20 is the one in their repo (http://packages.ubuntu.com/karmic/mutt). 1.5.17 is about three years old, and may very well still have the bug I mentioned (I don't see mention of it in mutt's UPDATING file, though). ~Kyle - -- If after I depart this vale you ever remember me and have thought to please my ghost, forgive some sinner, and wink your eye at some homely girl. -- H.L. Mencken's Epitaph -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJK/JRNAAoJECuveozR/AWeMUkP/195soutmBBTLQWbz5Jnc+KC lrHGzaP7dVAaue9ygjnUl/p8pVQqu77Vlt6wLf1fDUnburNLA6gAYRokhdmCL0zi 93yBqBA9Q7fo0fDDbV7CY1euhkXd7pSan01cGDlAvHLp0nuCanRmGts98CwsxfZJ vzusj203JoAybOX9mbJvgz5U9zVRjtr+6FuaVoIXrpG42CkUSFuaZHZd1MhQqb6p bd2Z8QSBXFUZeQ/d219qf3tB3OecEmZT5n1pNo4Gzla8+IBxDCE/iWw1gxC2sjkE JzAL5Y3iN3aycQP44LnJDKXdEaGM848k9avUl9B4mc321qM4BwUif3WpgRJ8k+hj 077H1Z8C78xcMnL8oV67+dsbCzjQLqoS1kld6vqt7qWrIzR0bKT1sf9X6EW4Hfbh n/kz5wOE0pNKD5RKGhLirh/XwT88JBwD/HUTI0FtH11Q4IebjyVhTEyKBMRXSZ9c oXjwPQCWgsUJE+nsJSLeJ4kok0ZNYCNSF9HSwNsQRc3LHZaJvgc7s0DgIbghZEqf u43BBwX++eT0xkCRwiKIlVv1a6wwG24STN4Irck8tPZ9D5wkonnUPdvPO3jyYA2s dJ6j6JOqzsrG78fv0phyt/vZkEr0HdlUi9Pqqfv2HcnVJ8B+Bee21KTNr5HPI94s 12ek9oO7y9R/EoaoQwZu =anZO -END PGP SIGNATURE-
Re: intermittant hesitation after key strokes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tuesday, November 10 at 11:02 PM, quoth Robert Holtzman: On Tue, Nov 10, 2009 at 04:36:25PM -0800, Morris, Patrick wrote: Mutt checks for mailbox changes frequently, It doesn't have to. If you're using a remote mailbox and the network connection's being flaky, or it's local and your hard drive is having fits, things can get pretty choppy. Would mutt exhibit this behavior if I don't have a constant connection to my isp's pop3 server? Correct. So, mutt has a lot of settings, most of which are set under the assumption that you're using mutt to read a local mbox. For example, the $mail_check variable is, by default, 5. What that means is that mutt will expect to check for new mail every five seconds---which is a good default if your mailbox(es) is/are just a disk-access away, but if accessing your mail requires network operations, five seconds is absurdly small. Boost that value up some (even to as little as 60 (1 minute)), and I think you'll find that mutt suddenly gets more responsive while accessing your pop3 server. ~Kyle - -- A man cannot be held responsible for what his mind does while he's asleep. -- Jean Luc Picard -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJK+sh+AAoJECuveozR/AWeI40QAITFBjx/Dd84PNmNw5YwLoVC AqLsLPhRNsv4dI4Y1XbqJ8aRpsW14gzJdVkIr9uaGCaEmDHLk5xFPGCzrvu8iqB7 X2JGWgu1cHXNspkbiX/wQEWcwhQV+DITLm9ZjJbLx24zCGiH0Cz6+lUkJOEaZZwE kbCvGBRAkbDyrTu75U2hUUDmfkBtBUaNfBIHyyAyneFLz45648WDVjDAgyzlNYPi HCI2IL3+e/tCW7cWbHYiauGKLBwgsHNgneSmU8DZbOCcyZdPJVdR4OLRXQtJ1Dze /0mtK5zcjoFDRwfO9y7kUvSlL1KuZgwt/ND1tt2gCL4oxjolNCyDzpqmW8ufeB2L ttzsYmu0bfxAuZQrC36TCW3aK3S8YpAgS+sh/YB1E/jSaPNmEjAf/QnmXEBAcHu9 GMGP9yAwFqT6ImZhbADhLnwTYJrpR/b8FrEaDaASBcoKuOvZXAtvvJHodvd6xfW1 ChFvr7I2NKelz0czoXtfOlh1yzWmIECqsXlPRl54MH8cFF+kqTBIjefkXEni9U+0 F5WAvf8AEzZxxqQVzvV3DSras7LvKVXMOVu+ImnUiGkthXlSbrkXhsXtQp6frFdZ PFqE62+opZOySJ1nvGUUXLJBAqD1wT7OiY6uK9jeS6e5BYyUqMxoen1/RpPADmop LGUjl7OUG1NaOPZhlr51 =C3XN -END PGP SIGNATURE-
Re: tagging from 1st to actual message
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, November 11 at 03:51 PM, quoth Matthias Apitz: I can tag with T~m1-100 the messages 1...100; how can I tag from 1 to the actual message? I've checked the manual and FAQ and don't see it :-( Define the actual message. ~Kyle - -- Reliability means never having to say you're sorry. -- Dr. Daniel J. Bernstein -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJK+x1/AAoJECuveozR/AWeTzMP/3rch7sLaeykBnL3FpRBldWf VVlKWlo1I9IQUavoHKvygRnFlpuK9ExZ4s3ulW7lrJLn+lx+Lq/cmNVIsNSVZL22 tnkCOW8ZBT+nbcx2roIrbLwu+TggyjKJWcr85Br6m/EdFVp+acZ4nGkT1nIOQIYM PeZpilkOYarIpr+8optv4wshe90Hdf87uk5M9JUt90XIHudie+IaUJXDUN30aHal 0Yfv7knbJrl0p+fP8KhgHZhJNrlbL3TGLYl/FOt9FrcLsqDq6RbZ5FT52xNGKbRs 2fJbM6sgLr/KkSEpSxetC+TGSGDMvMcdM8f01nA+kboa7VA6iIGycd6sCXUM6oZY Fvyb7yEjadCoZf13/ZJ6BBkXzSuznhlOcD/Mpx6rp48RGZJRfLGmECAn2nIO2T+1 laSBEDDhDKsOXBXmS9qvoktHiLYLBpZTvF0N8kqQdwsOEaZYCTIFqRdRcjcCncxc r3ydRVMmX3GGcEQqMgWf0s3p8xCZLuRNKq6/23ALOGlPkU7Wf+fYxVJDAztIvPxA cTWFRQMKQs4/sMMJMqLW4LsggWJmR7w/uSw5pv8B4AzGD561uuyZ8tiHkgwDhwGu UNmNQZibHq9gOAmQgzxTxH3lrO0GFR7RJ9FkaqaWMKO75bHZ4LApuFZFbBuQS7+i 7ccI8fxh0tllMo1F8jhx =Q2kO -END PGP SIGNATURE-
Re: tagging from 1st to actual message
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, November 11 at 09:43 PM, quoth Matthias Apitz: I can tag with T~m1-100 the messages 1...100; how can I tag from 1 to the actual message? I've checked the manual and FAQ and don't see it :-( Define the actual message. The message where I am when I jump with NNN to some message. Well, there's no simple pattern that matches the current message. The closest is ~mNNN. It's possible that you could modify all your message jump keys to set a $my_* variable, that could then be used (I think)... But I guess the short answer is: no such luck. :( ~Kyle - -- I have learned to be less confident in the conclusions of human reason, and give more credit to the honesty of contrary opinions. -- Thomas Jefferson to Edward Livingston, 1824 -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJK+yXaAAoJECuveozR/AWeVboQALLOpODRexWCpXDbTxKsNIe7 4NzB381sgfokK8Jimu5bZDiWFkDe9jhyIG1bC5o9UuBBjTZFw7xYDJjQnCIBiasC CgeF+ThPOseNNO9bJNUUhbZmGKA0NPmAcv9tulT8Sp31WOlnNn/TvIOusn4sEdCA 3mJKSw4LtcEsNt94iz5bdf3O4vrlhGJV+wQqzv4jWCA/rW5sXDIU7KwkZ8410f8K 4kyXk0pb4SYtcfytTgR1tTobgWNp/Sp1e7TOAus/qAk99QTVvREw8tBUX0YWTJm2 Qjt7L1HQikopmOsgUVccL2MyCznMTtthWK2JGS4aTueW8XTsbfZ3RsNlwWrqbmne r46rJMJ674sshzb49vzGJvyCkXKc1AXH1SCBHjCsdyy6gUlXTJU6CjPOoIx06LB5 ZRBwEpiWZhgzAyIRsRsjpL4QVOMQsiLGWLJcogxx7oDryl9ZThzQHd5byTdCcC8K 86V8a0jEFawVlV5V/T5yykK/pGKPbxIWX59gnQgKC/Yy6rOJhV3Nyphz616zfJe5 zZTTbfBNqz7VKooLdxG7nzAZYHhOqAkJNAB08/7qXS+v6SbZJHfZlJ2WJcbjo5wg G7HR8O+zDqBeQjo5hTFlpj9vSW4lOO8yo07UXMSoVPmCrL6iXJXOz2ZvXWH/aDoH m1ZFxKB4r+imCwrKxWRz =61MV -END PGP SIGNATURE-
Re: mutt no longer renders HTML or spawns browser on text/html attachments
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Thursday, November 5 at 05:24 PM, quoth martin f krafft:
for a few weeks now, my mutt (version info below) renders HTML
messages as HTML, i.e. it does not run them through w3m, which is
configured in mailcap as the first copiousoutput text/html viewer. I
also have implicit_autoview on.
No idea on this one.
What's worse is that hitting enter on such attachments just places
the raw HTML into the internal pager. If I use view-mailcap ('m'),
then a browser is spawned.
That's easy: mutt's default behavior changed. To return your original
behavior, just specify it in your muttrc:
bind attachments enter view-mailcap
~Kyle
- --
Compassion is the basis of morality.
-- Arnold Schopenhauer
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!
iQIVAwUBSvOjryuveozR/AWeAQg5nw//SGq4w57Rmq2ZwJ5kZWr1SqaiE+CT16sH
geFD7i/YnBomK3IWtc20x63+iV4c4uApemv6qT5NLUEG085LPE0dbmVTj+W5lky7
ne7RCHkBSWtFKtgIX3SDQfGwjoQ0WmmzvYu/z9IDzUyQKGXc0uaaRYDgFvv+bXju
+rO8zYJ9OXaW1VIEZgBLVo7wW4yA4RuQeMVJ5KRl81Fd3t+zbeijrFVdJbI9opZd
kpVdQaWDNf356+Ki9VYw9CODBUEVHeVGlaszgdJ8zz2mDeXN3G1vW31GkmQD4uIk
QcFlY5oAjEi6/CngUNvk6WOK2hBqWXZaJLCErjU2a7nnLYRXUc6ALeGJmQpbi6aT
sgw50KgHVxoTbCqrh3cHhpp1JCcXHJOnEuylRu7tYn82pMQVVkFipmHBs/gJ6nrD
xNbXHP6gZNLmORHa2zeWICP13Mw9NMT2Q+mHSCconk/dAoUgUSW/0QaRkVw0uhkk
lz80OLI9tLXBAS3qhuqGboq9NuoBX5oyKvq5nj/hszYJyTInbH5b36mZ40oSF3k4
4vN3WKbvl18fOtr06ikOs0BUu8F8n0VMnge6MXMePUfRZp4o67vxtewsuOrvHEj/
6XA6lBd5XAiKyjX8peyNfNQ4E5PYLnRZFG/LuC/38EjZkEUV0LQCAAC34QTIKo3w
tVFVorUVW8A=
=DMaV
-END PGP SIGNATURE-
Re: Change default Re: your mail subject when replying to blank
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, November 2 at 05:13 PM, quoth Noah Sheppard: I think the point of having a configurable default is so that we don't have to change it when prompted. I'd rather not have to type Re: my custom non-subject reply subject or whatever every time I reply to a message which had no subject. Actually... couldn't you do that with a reply-hook? reply-hook '~s ^$' 'edit-subjectkill-lineMy Custom Headerenter' (I haven't tested that, of course) ~Kyle - -- You cannot reason a person out of a position he did not reason himself into in the first place. -- Jonathan Swift -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIVAwUBSu9cbCuveozR/AWeAQjBbBAAiZg/f2aHeVu+DEqD5kJziNNTexFAfxL2 mDxZBKNiNnFJYnxzPTXYuNxn2YM0iKCUKTY5/MtkmsAh7GdY42Tp1JU8q3QRC8do ELKxxwkSqJVO3wyQZVmM69QSwGpm7tcSLmHW5WxborG8Tu+UguFIb0XJUb93qQIr Zo80MKpEo7W40DnM8ci4j29SN4uShin/DT7MKTzf0JY8+Qhb4hJRGNigTiKCdSPM oGfIWdLhG7MxfkGs1wDVF1C9j/PmJeT+tlqOlGH+PbuTP0zdrDFgpFy2ueQSnpVj VAGQObGLe9FI4hiDvulN4fwMlvwplvTqUVsD8ulPQmOhmxNJRfvcsKAlcYn01nDz 6un0pS+bc5S2rp83nQ4QiAJKJMfScqjSTMq9M5+ODcIGIhgYoxSJmqu4XOi7bvsR 6X+d26deXlET9jiht00ZXirbYmQOwMpLNyohIeeP12T67fj0urdO199qBowuavN9 hjG7DsLFWWVscV/WEc/K8QfP101Ga6IFj5GxdDq0LI4yWqjSYEwF+NGSmxVCDPQ6 nhPFnaTV4U4F2woh0mRmXm9MJsSEuA99RDH0ML/rDw4j+OUbAEJDrEAMufgornWR wqPil/P3JcE2SxzaNN8Ud8lneHfvKjMP27Eqzy/dwfXVtWIDBmaYM+qKeIIqoggg HhXVzQ1abPw= =2JJH -END PGP SIGNATURE-
Re: regex and UTF-8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Friday, October 30 at 07:36 PM, quoth Kevin Kammer: On Fri, Oct 30, 2009 at 08:43:21AM -0500, Kyle Wheeler wrote: Are you using your system's regex library, or the one that comes with mutt? It's possible that your system's regex library has a bug in it (and it would be nice to eliminate that before blaming mutt for the problem). Mutt was compiled with the +USE_GNU_REGEX flag set; it should be using that, yes? Yup, I think that's mutt's internal regex engine. Hmm. At best, you might be able to work around it with LC_COLLATE (which defines the type of sorting programs ought to use). Sounds like a bug; bring it up with mutt-dev! :( ~Kyle - -- When ideas fail, words come in very handy. -- Johann Wolfgang von Goethe -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJK69MIAAoJECuveozR/AWeqiYQAIjjDs/w8zmU/jiT35QPzmJy v4hPWjs1l2Jx7gkIL8Dkt7MD8zAdaUNT3SjxB9WNZ99H+2Xl1S7lwMnJ/RETlaE0 bA6c5JbVF01bDBJKJk3cS+x8eYpyawgILv09l7PzJi8a5gI51CHPMuNk5MiUFndZ 2XAqUFGBmJNDjqaYbBxip1UUI6dwY+FgIwY1XIBoqA9+fLbM54zZDazpSS/Cc7Bt NPD7gv+0wt3QXPwg87SHU3rdMCWxUYHheh9sRTfwqKH7PPvF0BsQowLmxj5TZwp/ CL4NkuRjGKoN/PwU4bzPqBhMAdSJl2lg2/HRIe8a721qECEUK3HPDY/GTMXxtW9g 4Kck2SOn3tFQn1hmbKzqUXnf8GfVKmRhW7lgHMjIzowWoq8vhPF9DmQFNBauPUMB C0DOcQw9LznN3UA06DP+evGB9KOJ3yIsgLJeKT56a/f7KSgaVMVBiaSiOzoLxJ3c CtFd9KKTgZ3gDyBPymniY2/amSc7iDUNt+kLg3ukcXuSzuE+Xo32xsIsPFFi6Ul9 rrQeRJCtkwkyTtqBGkd5CoNJBTK4fJzOhvLDOeTmDLRoHmNqGQQyNPyvaK3QwW20 0kzM6a0J8V2E94EDk7MYysxXmPyOgfAMO8noyZT55V4uq4sncGap1tCwwAFy7kaC 4Mj9Z4+ukwfxIayTASmQ =loYn -END PGP SIGNATURE-
Re: Content-Transfer-Encoding: quoted-printable urlview(1)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Saturday, October 31 at 04:20 PM, quoth Matthias Apitz: I'm receiving mails from a bulletin board forum in form of the encoding 'Content-Transfer-Encoding: quoted-printable' and having URLs in the body as Been there, done that. I feel your pain. Ofc, urlview(1) is unhappy and unable to offer the correct URL to send it to the browser. Any idea how to solve this, maybe with putting something in from of urlview(1) to pipe through before it goes to this? Urlview is broken in a variety of ways. This is one of them. Another is when long URLs get broken over multiple lines in format=flowed messages. Or just long urls period (urlview won't show you the end of urls that happen to be longer than your terminal, making it hard to choose between multiple nearly-identical-looking URLs). And that's not even to mention the fact that it gives you no actual *context* for the URLs, so unless you can guess what the URL meant from reading the URL or can count how many URLs down into the email you want, it's hard to figure out which link you really wanted. Anyway, the solution to your problem is a perl script that I wrote, called extract_url.pl. You can use it as a filter in front of urlview OR you can use it as a full replacement for urlview (though you'd need a few extra perl modules to support the curses terminal interface). I think you'll find it beats the pants off of urlview in every way. http://www.memoryhole.net/~kyle/extract_url/ ~Kyle - -- Victory goes to the player who makes the next-to-last mistake. -- Chessmaster Savielly Gricorievitch Tartakower -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJK7IFDAAoJECuveozR/AWeEZsP/RbCXljU+zWoeTD7mvHzgFIp md6GwqbtMh0v68pRT2mnKyI2SSKg88292CJypmDV2Ddy2h0CDzP840O2aQJlJW5j bZXKN6SlFZURSswRovlsImFzuggS8OgY/wxS7BgKkF3auNhStV1PaP2MPxI9p9sH ObToA3A4AyBvTEQZaihDZUjWljm5XIF1ulQbLW/QyRGpdrRr8ZLLkoafU20a1gCu na5of96CN64ZEBIw/4GIozQpSlnlE1DfhIkSn7aoW+urf+Z7WmkfTe7pKoH6atsL 4ZG3Ulu9T6KhDiXIcSqgp8Ipw6b/mSHnPTulW95dWdURL3E7Ed5gbSY/tZGUIBSQ TaYPPqNYYZhQlBJFJJtIEI1Di/YprlVId6o7lWGioUQMPnugXMHkNy/zsHd5Tdtu ufAXr+ILHFqnGz388Y01rj7FY0qS9Fhro7VVwey17pRWpCn3cb+zu40nkg2hjVSW h/V2GWlNxa52fQ7/iNnds4J/3sBtDvVvXhLUptQWZl/r4Tmhctupu0AgxC2s9Bls PFy76+TCJxN2cvbqmTBgag+tbsm/bQx1/hvWIsmwHi/yuLzVJojIIy9VKfl86F7X UWsQmZi20v2PgMs4ky2dI2jkVXqiwDlSQGNXsiF/ehbY5GVHTb3DAhk7dT5vVzHU YgNAsokkHX9QfwqXNUlK =SvDy -END PGP SIGNATURE-
Re: regex and UTF-8
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Friday, October 30 at 02:12 AM, quoth Kevin Kammer: I was not using any capitalized letters it the regexs. I know that if one or more letters is/are capitalized, the expression will be evaluated case-sensitive. Nevertheless, '~f tony' matched for messages from tony but not from Tony Are you using your system's regex library, or the one that comes with mutt? It's possible that your system's regex library has a bug in it (and it would be nice to eliminate that before blaming mutt for the problem). ~Kyle - -- In the game of life and evolution there are three players at the table: Human Beings, Nature, and Machines. I am firmly on the side of Nature. But Nature, I suspect, is on the side of the Machines. -- George Dyson -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJK6u14AAoJECuveozR/AWeJ8QQALGWSupr32fztC38NwkhCn20 oYCnnMUbq3UM+GkAfjXLo9urD5sx07vw2AA4ztDuErtCyrtq+dF6XiT8BNh8yvV8 01+IPl5/KeCPCXdxkBGqxpXBRVfxrwTH1g5rYgAb+3x/HrvS2qOxfO9RPPKFIeVT n2PX8rqkPhgvD9DMMSjWKJEkDRVgqFg4Irni3tVDbNmjE0a/nEKUlIlqDYyt0eGN ZJxJaMWtKsXA8td4sPWZ+/SZxXNpFNOY1moh9KXc6Cs0xK00RZPpPFByk5KWYSab aCn1A1ZJp9A/BjAzjnWWT3O55ew1qwtn03mou14VQXzPYSJtMccVT4w9E49kKPXD sBgk8aI3QtoSP4RtBcJI2by1UFctZ2s2DkkopQ77mFH9biORhOg+clc68/dqa3Tv +UrP/XlzWIokFlRD7hNddv9kKSlcy1Xtew5OSjey1gWOD89xH/NefwELvfR5kPlS 9lLQiA4XoQPGMnUVUhnBcOQUUj2oVLHoU8Lz7zsuhIBBga5hotbafGh2tvRuaJ2m /8tRBLcykwaYLU4YD/9Chnf+k4i2w7ukYRZki8qFZ+YVKTO6ozf32a4DQ8QwJfty kqyOGHTePU1H/ocYKxaqN8wXu0pIJUjG5jLIG5YYLTKV4mJK5TGQ07b7MyW95OzT Sh3C+75povRBtGwkdksg =5QMP -END PGP SIGNATURE-
Re: How to display patch/diff files with color inside Mutt?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, October 26 at 01:56 PM, quoth Horacio Sanson: I tried using pygmentize that in console colors the diff files correctly but when used from within mutt the text is displayed correctly but not colored. Add this to your muttrc: set allow_ansi Normally, mutt doesn't let inline viewer programs generate colors. I believe the rationale is that to do so would give them too much power to fool the user (e.g. to fake a PGP-successfully-decoded header or something). But, if you set the $allow_ansi variable, mutt will preserve the colors. ~Kyle - -- We all grow up with the weight of history on us. Our ancestors dwell in the attics of our brains as they do in the spiraling chains of knowledge hidden in every cell of our bodies. -- Shirley Abbott -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIVAwUBSushOiuveozR/AWeAQg7LA//Scr8dHMYPrH7l4ydgC6sraN94qn3Elpj PeXMsVZCr9EpthKEhQfU/8fNYYxV9v4GzjAi68dp3A3eNgFLDILXhXWgCf7liBNh HEXl4EFN1qLT0uz2syClzdzqQhGsF3+BJLDHLx2JeqNzB88gRVr2Yb5wa1CeOXXs o9XVSUSo23ogY1xl7LM6B+LWuFUZhxRw/q78fKqv7/pf49Pr3rGNny+klWH+IyvJ VjEKNZNA/RmzeEGP1kkQ0J/w9gw9VBHawwf1QNAPSGGXVYxwKPeu9Lu3ls8MzBI5 Nzi4Xtr0z3pbWiXxLBWBlTMzn2bvRo+txMPHo2k0bqIMYQVqtGSjVxUzt+8+3X+S mPVEyDvl88CDX7xDH0DgFyfFtGfQf/cbuMN6ortK/Kfb04YG8Z51bx6hs0tGIY3k Ma29lEdjXR2FvM4gCz+mJwHQgnGgpFlUWOVbH1Y3vYigUvQflFgjCKJoNYO/O9Ok ks24WXrQ5y97hjt8CgYTubRCO4GJ+c1wJH1OGWAre2r4EBMhOP/VEQ/1rJs43FB4 L1aHz4+0MRkkeOJA9GPAJrHt+Ut5rFbNNmU1An7I/hRcZfLcvYBor0+YPf/ezWWF un7bg1p53TAEz9a1PUP3dU699NCcx7i9DWoPS1uOSudSdTIKT89ZWODit/WINhl3 790oekJ0Yn0= =NxE8 -END PGP SIGNATURE-
Re: wrapping long lines
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Friday, October 30 at 03:11 PM, quoth Brandon Metcalf: Has anyone implemented some vim goodness to format these lines so they show up like so when replying: Have you investigated the vim command gq? (without the quotes) ~Kyle - -- The liberty of a democracy is not safe if the people tolerate the growth of a private power to a point where it becomes stronger than the democratic state itself. -- Franklin D. Roosevelt -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIVAwUBSutKWCuveozR/AWeAQgUwA//exIYiFLofYTxnpWdOOLHa2g9cthfXy20 jBSVuWsIU8BaJ0cfQyU9s3tTA5Bebb3lsQ2Bei5tJ65TYaYtvq5+tslOPXFPfXMl waP9K4xZrFifu/iD0LbSirsS31b5VeADox2AyBiSdAuGxRbePWXx7VTiWDbNUKGz nPgTubv2h9OlCi3i3PSPmafwUYq8tiYf/QXujr9p4BrIAXO00qkuuDyxH5xf/HNF zI684eN4PnsXs/1gR1rCQ7GR7jrbNm0yfEEMc6DDaR72g+zO/qzWNXQPBjAAchPA Z0sWNCXFeJ1IoZV0zHC2bG2LRro672ZnzgEz6QoImftgWAivOcrh9ejG7AhV1Rxt ekRokj0NF55iAhov/BnXDCX56cVrf0Oda48++H7GXVXIjbNzY9KGkAgebloBeWZk bYP4bmEul/3JC+EcBb6w0j6TeIKaOVr8ArcZAI1RSV3HcqzTZjIoE34s2Saf0KGJ UnX87jV1XEJjHOx8W+8aNu6Wick9/BdMYSYzMiSJaC7hZXEti36zfJVChC6BPDUA m/LQP903+dgo+dM2ljP1RPV9gwGYY9nl0oyRLhw6TVuVrSulUhmoH6Gi979YSKZB ARWS2HNrJ1TAMEpwVTwqv+ccEEAc9AuCGCYB+arqwx3PTruF5PUCpXyxczgHyrGU BL0Mo1RDLD8= =dlRd -END PGP SIGNATURE-
Re: Move message
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Friday, October 23 at 10:26 AM, quoth J. Prendick: If I move a message into another folder, mutt first downloads the message and reuploads it to the selcted folder. That's a bit annoying, especially with large attachments. I don't think, mutt has done that before. Mutt shouldn't do that. The only reason I can think it might *download* the full message is if you've got some hook somewhere that matches ~b or ~h (thus requiring the full message). It should never need to fully re-upload... unless maybe it thinks that the source and destination folder are on different servers or use different accounts. In any event, it sounds like a configuration problem. ~Kyle - -- It is better to dwell in the wilderness than with a contentious and an angry woman. -- Proverbs 21:19 -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIVAwUBSumqXyuveozR/AWeAQg4bQ//ZMX7ClPiW80nIBubtV8PoyXdLuy5HUi0 e9M0zCr29sv1hYPlOhIl/kKg7NIlZUmVw012UBNICq5tKiVHf3xLd0MGOmbOLyKu ZwZ3ptZftdk/vUpPKKtU9XUqT9UMugykKsE33P8J7j/AAzL06EM7X3RCZTrOlGvX n4YeOuKmGd4HZgLUlC2UCuDd/AG4UlHKbVSFY57S7SdGo4x3mV1fJxjlYkFuimve AC438ZWwZlf8KveVeGNx8AqsuPb2cIwE6kTer6dRs96FiNSkJEQNike22/elu5hV 17dDx6VuVc3KvCE6EUyKuGDu0vs8vaFipOAIp2G744VXqPbYriB+iSHSi5dATQcX M8rUu3wqk7oC/cm42pXkKMBFAHtOl6o/UzWYaLUV4cYP91Zr6+5T92hZz5/8gS+i VZBmPgSsDIot39ofXNZIPAqp3dBQYQ+Pi+Zwo9cD1IXOq8PCzBGtEK0QGxgZIuPk 75jOsJDt2D45IIee8ZGOaKqnu/MkPy6o8WpYRZ/DYack8OX+KkrCxpbYZ9R0bPCS nw+XaSJoipxNGYBe1JOG6U5h8b8KnkkJ5VqTcIsPrw2Z4tg0BCFHEw31X+uySV4f e5/4vX0mON97O2Omz1pISSTDwiQAR392PD9ja0LhvNRWIjglPLFPo14I+i7vhAL+ /GPZsn5uZMo= =Mvl8 -END PGP SIGNATURE-
Re: archive key binding for gmail
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thursday, October 29 at 06:08 PM, quoth Randomcoder: So far I got this macro index A 's=[Gmail]/All Mail' somehow when I do A on a message I get =[Gmail]/All MailMail Yeah, that's right, double Mail. How do I correct this ? It's because the space key is bound to tab-complete (or something similar) in mutt's editor environment. The easiest way to work around it is to insert a control-V before the space (when you edit your config file, you'll have to press control-v twice to insert it). ~Kyle - -- Look, I can surely say by now that I've got the antibodies to communism inside me. But when I think of consumer society, with all its tragedies, I wonder which of the two systems is better. -- Pope John Paul II, 1979 -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIVAwUBSum/iyuveozR/AWeAQjTohAAhACSdVfkrA6cgzQyNXs2bYnderqM3Ka9 JvRJLyHQirlscM6XUxVLTRBTphwuKLICSOGveB/L24R6ax/AlgVOe2SEtaAH/hCY 4xK6EQOL3a1fq65avcnHq4C7dqh3vlv5Ta5x+grJL7QIYnkx7aOLqv0Becotjl9r JbFyeCEE570GdGpzedzh1DVxUzoA5lJW1Lonq6KPoBZApNopjG01a52pE98F0qXX c+CZPigimkTiIpSdwCmhtLotkVgA+1ucUUF0xvySzRV6HB0IlgZqCVoeepjvNY5E /js0lvTl7O1oR6fZIW2KDvQ4WXzyX7FQuOHZBQCAranCi4q6DgpWRVZbRh7qcrSJ oaUEeM2QFYRG+lgC3qmstOtL5ovvKGbxh37sczbRoDRYGZTUhTSqlBML3FSobE6N mkdOgTGdVmqoWUlbi0DUoJ8lD1sSQko5pIoqd9APFSAdj4CSnrURKjK2x79QsrOl uX53DEhACCJCXinOjMZ793r7x5avAiEyogqyFy4CtcTt3PayI3v1MxSj8/5n8nm0 YIjSuHIw1gjfaKXrzBLk9LUSHl/CCcbhpdHqi1w/xyXz61jTd8Tw1zxu9YUygkSt jVrz4Ts9oEEM09gF6IK5mgL6fw5HMui11wZz1UWaeE3i1ZW7jvaKDxDlx3/3bNMd vxMTyAZs0V0= =RQYR -END PGP SIGNATURE-
Re: display name
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thursday, October 22 at 04:57 PM, quoth ed: Is there a way to change the display of the From header in a message in the pager view? There's no *easy* way. In the pager view, mutt is showing you the real (decoded) headers. In the index view, you can have mutt show you the name of the alias whose address matches the sender's address rather than the name included in the email itself, but in the pager view, mutt doesn't give you the option to create fake headers (e.g. with the name of the associated alias). It just shows you the ones that are actually there. However, if you're clever with perl, you can create a display_filter script that will locate the From header, look it up in your alias file, and translate it into anything you like. It wouldn't be very difficult. ~Kyle - -- I know that there are people who do not love their fellow man, and I hate people like that! -- Tom Lehrer -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIVAwUBSuCZkyuveozR/AWeAQiAEw/+OQRKWoAFLPOWLIlIguCmY2y5835YVz9+ Rg4fa4pugnrID2WGABwCoCHmW3zKhpzRmXnfXSoQIyJcnTYMkfYfNE6uo8C9WQqH AHVyIIOHDmVvxUgiNyfN7ji//biWk66zFxmLT5CGe9bXymCAi3S9QwTNUlDR4Z/i jdAbN3ZFE5SfJyM2RPs499YQC5AQwIFD5FVlxLXQ59NV7zqPbm7xCLV6mSnRqz1N EN52kbWO0Bq233gYrU5qGnkcZqEyG3+XhTN7QfSOce2n3pG7wr5sEtymvVQRkiSY tXJ19Kbsb3nr8Vw3uvRdnN2Ivqq/Tdw8lE4/LW28pkiUmeGMWK9GDSMq2NZK4in4 2YhD+6WqJ1SMUTwXFIkGlhMoafXeXuxJa5UmnYtT5BOA4drEj3/q9qUdT2b1Iagw M6sqMe8KW4mS8gQMTmsX3eb02FcQIxknZe8PObveLX3sjjwvKvsQnfKewltKgSsN zxVsROH5etRpmWU+SCQLnvBOqx7a2xHZE5CL6NwimQz2vsxUCIx0BwhkG7l8/irq TXq4ajM7ZqDkzJqu8UD1hqq8Qp2o5WiqWmcmVEOh+kpcS9eeJf3tnP3xw8OP4Sot DEGopY+IO/HslYQsWpI5reKNT/APF8KWcNucRYZND5XFF3EcLyWSJ8bhIlDd6Thn zYLpQ4U/i9I= =s3p4 -END PGP SIGNATURE-
Re: Terminal for mutt (Poll)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, October 7 at 09:01 PM, quoth Cooper T53: Which terminal do you prefer for mutt? I *prefer* xterm-unicode, but I typically use Apple's Terminal.app. And why? Xterm is blazing fast, full-featured, and very compatible with just about everything. Apple's Terminal.app, on the other hand, (when sufficiently customized to resemble Xterm) is less of a pain on OSX, has a nicer scroll bar, and works better with the copy/paste stuff. It used to be painfully slow, but it's gotten much better. And while I am at it, dark background or light background? Dark. ~Kyle - -- Anger is never without Reason, but seldom with a good One. -- Benjamin Franklin -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKzVWMAAoJECuveozR/AWeVB4QAI4om2o6zqwas6V4f+oC4E1A TkypD2ll99BD3i2JO+Xc6zJyMGWxIky5yySpX6WsoqYytYw1CITtZhqHRCtVJRRa KfkOg+h62fgRM/vtYPM8Zg4r8QXy6vLy289gVvaNQNtHgI0n6FIK8H0/uYamvF81 nZnBwmYPKdA7QlUnrRZyZhzKNBaoMUcds0RpfM7n3KGf36w55QoEBs8dhodjVJ1p Fa7INBzt0+gP9YJqkmwmxoe9mdE6aYlY3xgF9KtPtfuggcA+/zGy35ga+mjxVRQ4 X7eeE/FcJQ47cppbDBjfG911zi/nykhfEp7DKEE2eOUB4cyf8C5+ptYfLXtUz8AI p1cDr8AxthIt9U0VCahZg2VAt7EsqOcpLJndXzO9G9JAALJ8YTA+cObR3JYYKbaQ x/fA1H7Brfd+fJnxRXI2rEl0iqFlqHkldIe0KG8JuIIBq3+z1aSyNPpk7huxZddN R5emCHNiW9E2kNFesZg5XncG4/7qbsHKKc5S9cP8SblT4txuCfJ4dpWcJV6g5t2B 6nTpuqpmTYCISqGbIJ6DhTKO/KdIhH1pLPCZDNkDYDwmi556ildNdlP9j0iRRttS 8JIiEoETDc2hSq4V9G7N141tU+lc8K09sMQ5f7qACP1j9UVTSTgwE/LnexM5NOta Vy9iB6y0GL+GAky+ayJ9 =d1AU -END PGP SIGNATURE-
Re: How to remove empty maildir?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, September 23 at 08:16 PM, quoth Wu, Yue: Hi, list, question is how to use some commands(i.g. shell commands) to remove the empty maildirs, i.e. no any file in maildirs' new/ cur/ and tmp/? If you know it won't be re-created or delivered to while you're fussing with it, you can just use `rm -r maildirname` or even `rmdir maildirname/new maildirname/cur maildirname/tmp maildirname` ~Kyle - -- Science has proof without any certainty. Creationists have certainty without any proof. -- Ashley Montague -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKuiDeAAoJECuveozR/AWe3vUP/Rse15oRQ/ijWxXPoAGvFLZT HiBXQVbETRtzAMGnH7+HUSCdIZTTXeZU8P1iso1N1aThDMtahisgQXNVHejkVGGc GRb8nVGIbGXpLacQfsuWCDY/nzqXIBIkR4pYPkiKLm+898UNz/1bx0UTv7pC6Gn0 F62J2nDGvb02F42Xe6Of3uD4PbuaKwvwbWOqayqiicm3yAcWep+7yq0Z6+cUIQ1H 7JB++dP9TocVyVjFys9bvvEidsn24bPEzW0aZcp/o8JS8lKzHR0n6NxDkTRQ03sP 2b2bJqSz1dHZ3FsMo6uXT36Liv/tYArYi7senPCuHSO/snpfPstigJ3q+uWRv8vZ o2Ow1TEe6p/SKk+pWwRTWB9O/eKgkxHn2oWc9SZ2jCvBWgL6y6ZD91w2jh5HT4Yg aDvDrL/TGbZGC5PddC1MeBSmacqPOTuxQUSwXhX+F4yHRhh1X+F2nO539dy6RAet zXkVXYD/mPWs6ZEdTHB08ek0zzkKApzBEmivld6KlGGauJikLdN+ZxOoacX3GbAS IBMUmVz163bKZPu0CU3QZFbrhtUvIjhev+gwGWk2mMWxPZxTrFaH246Snq92hUkd Kw4jCJscxixuD1UB1PCzfpMJPUttP108/EqxMwAW/HZmfk5V8f9J+Ohn/wl6Sq/a zfCy7DDi7qpdDOhOn0Q+ =Z5eY -END PGP SIGNATURE-
Re: no way to view html part in browser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, September 23 at 03:08 PM, quoth Louis-David Mitterrand: Using debian's mutt 1.5.20-4 I can no longer view the html part of a message in a graphical browser (firefox). This has been discussed a couple times on this mailing list already. Sure you can; it's just that the default behavior of the return key (in the attachment menu) changed. For good or ill, the mutt authors decided that it should use the same behavior as inline (in other words, it requires the copiousoutput flag). HOWEVER, you can get the old behavior using the 'm' key, which is bound to the view-mailcap function. You can even restore the original behavior by adding the following to your muttrc: bind attach Return view-mailcap ~Kyle - -- Unthinking respect for authority is the greatest enemy of truth. -- Albert Einstein -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKuiJgAAoJECuveozR/AWeGpIQALOVReBs/iqL+BxT6ZZlCANj hoZmEtKBufIv8gbv+Z9RCO5zsxyfz9D2Ho6npDqIw+u3SZ1G6Dv+K8bDvWOGvoJ3 ZwbQb1T9C6XovX9PnW/OVWxmp9B0B+BtGHPdLXE4h6jLnteNw0u/Lk/peyRWoBxT 9O9MoIzEbvtvquzUvbTjKm9EZJjEARyP+TzoVHiMDhgD8hrw+AeaXOAEExSu9cXW ZaniJqcQEtK37Qd49XgML8IPD2ZoXeKIHAXSGWeANtKJ/7vBOxmXBCZ7BC4TKM8s 5CBK6mzRKKvzKDU3+PIE9VL/EM7yxM6/iFGEfIFtoLyt33WMhk0BVc0SybGgddU+ zJQcRROAA3NW50k69hcpowo5z2OmdQo6pmzLENJEMcSRPk3jLmWfr1kFzMNaGoVQ QPh+o7bhQ2HJzZxHu3Ddn3Fbb1edOgRz5XtAi7fr/2WxsaUy7OLm9qW/6LHXVoGl 1EO2+S+zhujvziD2jpU3PP3jt4EHnp4A7sUPvojFYLdqeRKaSFmbvqPWAAadpmsE jPDttNvpIF5XKPw4/LpktwhkxtUuiWA4bYMgO9nudu4/IcUY4hn0U/wrNxqaPmp5 aLgxSqx41fN5lr8wHpVpbYGX9I4FOuXg0y+vXJpN9PHAdJJuEE8QP/0WbrpZkgrp akth4BmSvVH4ypZXo5W0 =phHa -END PGP SIGNATURE-
Re: Blank html when trying to view html attachment by opera
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tuesday, September 22 at 10:33 PM, quoth Wu, Yue: Hi, list, I have a weird issue, my mailcap has this entry: text/html; opera '%s'; test=test -n $DISPLAY But I still can't view the html attachment, opera always shows me a blank html file. What's wrong? The way that mutt works is that for mailcap handling, it creates temporary files containing the portion of the email that needs to be viewed, and then launches the program specified in your mailcap. When that program exits, mutt deletes the temporary file (if it didn't, those temporary files would accumulate and pose not only a problem filling up your disk but also a privacy problem). This is logical and makes sense; the usual order of events goes like this: 1. mutt creates temporary file 2. mutt launches specified program 3. program views file contents, per user's request 4. program exits 5. mutt deletes temporary file HOWEVER, this can cause problems with programs like opera and firefox that don't stay bound to the original execution. They create a master execution of the program, and simply send the filename to it. Then, the original invocation exits. If that sounds confusing, try this description of the order of events: 1. mutt creates temporary file containing html 2. mutt launches opera with the filename as an argument 3. opera launches the opera-master process 4. opera sends a message to the opera-master process to open the temporary file 5. opera exits 6. mutt deletes temporary file 7. opera-master attempts to open the temporary file See the problem? How can mutt know when Opera is done using the file? The usual solution is to create a wrapper script that will copy the temporary file somewhere safe. This essentially just avoids mutt's cleanup; so you need to have your own way of managing all the temporary files that will get created. ~Kyle - -- In any conversation where only one side may be argued, we instinctively assume that those who publicly defend the official position are motivated by ideology and not by an interest in truth. The outlawed position is then assumed to be true, and wins by default. -- Fr. Andrew Hamilton SJ -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKuON+AAoJECuveozR/AWeQ5kQAIE7EJ6SqAImbq6x7C+frPPy VVhB5OtjrjXYIhACU987qVMmE35kJWChHHvnmC+N7X7fzql9RjMIXn9chhelpeA/ QyY9E4zy0ITxLi94V8gBdHtS+47PTV8qsM8lOPv19hPINwWZ9B/imIIr1WQ2XIvq YrL5u3skC5t0tqpsu1lvf0P3b3iPlLuq9RUqod4sJ7w2eDoLbsh4klGDwjQ3VFGT 8mvkzPhPs2nnsk1zFfGKO6I5BIwZqvzxuj2mVHqMkFeoSQE5iG8IX+oGLMGrv6cY RUQJzfvk6m+Piz3QwGI5iwaFv9oUcv4dE2ykgqrCRLMfyiPSQwc91ejDUwl1XdYG HUk0/8o32T2nI7z/BosRCe+bbPM0qfbtq+1XoEuwllcxLajxYoSo/1Z3S0AAfzZC kZ/milOB9LJNmYSbsuhGTgLLeiOgSU8guqSVEB00mkD/v/3I0QiAalnKntNzXMxi fY416IayDSCmiFu+GoDbfSW0XLxoluTKGTTf6dZqwtUUwKYGcmoTpSX6AnmY8d+0 siv4OoRPk5fBlL8aNAjUErVrMzENxUOJIY1C0OjLH24Zx10moeifHqMPfMf4ajDC OK7iixbAmQDNyawwoqlP7+yyts16tgllXcNdeMK37ELAe9Y7NLFpI7pMegOb4uUm Ui6AHStW4sW/njhqhrhj =iw+5 -END PGP SIGNATURE-
Re: mutt not reading header_cache during startup.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Saturday, September 19 at 10:33 PM, quoth Manish Katiyar: I can see a big cached file created, but after it finishes downloading my 80K mails, it says Error opening mailbox. If I start mutt again it again starts downloading headers rather than reading from the cache. For whatever reason, Gmail doesn't like it when people attempt to pull down lots of headers (which is precisely what mutt does). So, after a certain number (I don't know how many), it simply refuses to continue and sends a response saying, essentially, your command has failed. Now, mutt can handle this several different ways. The way mutt currently handles it is by assuming that failed commands cannot be trusted even a little bit, so any headers transferred by the failed command are considered unlikely to be accurate, and are thus ignored. I think you can make a valid argument that this isn't good behavior on mutt's part (as such, take it up with mutt-dev), but it seems to me that this is simply an attempt to work around yet more gmail IMAP idiocy (see the list archives for all the various issues people have with gmail's truly awful IMAP implementation). :( ~Kyle - -- It only takes 20 years for a liberal to become a conservative without changing a single idea. -- Robert Anton Wilson -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIVAwUBSrYf2yuveozR/AWeAQiY+w/8CrQztIXq/Yxe2v4WuUF6qNmIpGCgxepz zGh0ckly8meHs6S4yjyz062w2JpjWyoEAF2vbUxHmJ5TzHPHKoMK18Hwq4GdYX6D tMsq4aEQXFr8ZhAT/N5m5rQ6P3nQDKwnqaTRhGDwqsSCY9UDm3Xyzz0LHyOzNVKZ BiT2KgXjmbenmpnJmISCD9p3zVfQ5CqFFu37eewlJ9JIy/rWYdyOwYagw/3TVfxX q2PwGDDQtfg11WzvviEBu62UCAcXGrgOHgqcS5WBRwyWG/tA6NFkd9Obo/QZxsvt lBzQ9avxtq0Q5Hqe0oQ89tyMh57LtzEcEsVVYVjbnngTogux6gE5vD2COrIzW87q y3BZa8Z/o7UssMVzK/Chx2GBoMDhGxTi5tZB8rJT5G6szm7cQnjOs/MqGiS1JRnr qDcm402d4jsPWiexFYejvmSSMCYuSi1tA4XhNuqQZBfxBFZbFSPRUxpu0weLbCxP ccTFQqQ9TLuAAdLXypxzvyxR/LY0Y9zbLugf6IHYd571y7UUAnI9+jdQzu4f6NJp S9lDXTJ13w5Jfych0SIaxglLJO+aksOIl48OhjMbi2TaJ6+28wKS6Vm+D/g98etr 9xGIUb2R7AsGUc+CZ4doB+VZWwjOzU1YwbtCcPEg1V/awutAji3GlqFaVq6lME5e TwnY9M2Cw9I= =6LQN -END PGP SIGNATURE-
Re: best way to automatically 'fix' mime-type
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Monday, September 14 at 10:11 AM, quoth David E Mussulman:
To get back my favored digest view, I've been Control-E editing the
message in mutt to change the Content-Type back to multipart/digest.
This works but it's manual and I'm getting tired of doing that for
each MIME digest I read daily. Can that be automated somehow?
Either in mutt (like a folder-hook) or with another tool that would
work with maildir to adjust the proper messages?
Thoughts? Ideas? Recipes?
Well, the thing that occurs to me is you could set up a macro that
sets $editor to a script that modifies the Content-Type, calls
edit-message on your messages, and then resets $editor back to
whatever you normally use. The trick then is generating a script that
does it. Without testing it, I would think this awk script would work:
awk '/^$/{exit}/^Content-Type: multipart\/mixed/{print $1,
multipart/digest}/./{print}'
~Kyle
- --
Next in importance to freedom and justice is popular education,
without which neither freedom nor justice can be permanently
maintained.
-- James A. Garfield
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!
iQIcBAEBCAAGBQJKrnJHAAoJECuveozR/AWe36QP/RMU1rKcwOPpShY/EblrmcZ0
057DFlRrTbuTVbzmo5BAO9e/baixNSv0PyRgzTyQek/1Kmbshtj7KunX3gFxQWzc
BLmiZvgVRvU10+CpL/iCakll3E+exWgODHs/EYHPYHHCBpFHLrc9zIAN58ivbqDO
XIBJqpOfoyAobF9zobuBac98VdeOBpzuCeFZ1f6UGTWfNpLmYg1hW6vBlCsdkLCO
y4/zlKv0+oSMSeSx34P+gl3RUEfEWj92dLxT33gEiGA+cbdQNIu8I9kEVd9tHfkp
7i7bvlGvADHn/qFRJ3b3qninR3/rVDlmZuo0EZPHJV5mPnfi/mEtjES7PRI+HKw6
amd7FcdQObu4HUgNY9ARy76CjfkEvCTOB99cNTdKRcq0ZcAS17pUzYElBuc9nJrF
MT/q2CWDEVFCygp/y61LhRUYH+dabHKYOxCjIvekji7/FElRji93J8IRP4htTGba
zvIQ2Xek3w8dAG+g4z+Py4iQlMeITundsK2kWMjTfXvIbGRrn3lhE0tzxBmmjAEE
93x7rTuGXN5+fXVD97xk33WgAFYYkGnS7UNu3j/mzyPwasqMWNHJbTffq+7hsB/u
M34f5AQWVugFWHuoZs5DFSBjbvBe2HMWaP4ZEl32jXnssmjChE5b+LP7JFf4J7HR
AL7MfgVKi/IK9RQmpfRd
=QjCy
-END PGP SIGNATURE-
Re: imap cannot resume from error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Friday, September 11 at 04:24 PM, quoth bill lam: [2009-09-11 15:55:26] 4 a0006 NO Some messages could not be FETCHed (Failure) Hmmm. Try posting this info on the mutt-dev list. ~Kyle - -- If after I depart this vale you ever remember me and have thought to please my ghost, forgive some sinner, and wink your eye at some homely girl. -- H.L. Mencken's Epitaph -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKqmOeAAoJECuveozR/AWea/0P+wWtBEBzPXyzfBmGwzturGWn 7s+5s4NqyHDWOn/qYb037QR0Lb0tOlpRKBqAjdnIkAD+NWNHxBrbPRwwweUw4w9B N/ibjj/Bxyv3KN4s2Xare+MdyhdDdVdr60+gNwsdIBJSbsfSmkl0bPrP/MudwRDD Pl5x5YreC21SJ7ucwPro/rHPgMcFgQBZggk/kqotBSrAB+ZFy2+VpTmc/HdxwUQ9 GBwf4VhTP6j3r4q8qBFjuTPwHROBmaAux4a+8McfAsgc8CS+qzkaB9Li4Raiy/qp oJK6hhun+4qJV9jYQxfPITZpDxOZu20JyyvlGH2/fBfP4S2ClWnkL92j9F+dG5dR WhKMhwdv9DgRZMPPPDo4OlteYhkAq0K6lDXwN4pizafGWTxMjseF1/qdSmu1oV/h HSO32d1lBtjyzcUGbw+O7zHQBNwtMQO8gFz8hGphYg57wLT2EDG+XF87l8KcjwYK vi7uchijP/fujkRKRLQc2nRCpGTozBSDgZtP9dX/Y12uwp3JpvHN5svaYaOsQsHh /NMJpgklA8kDOTs1kQvYnxHV2soovIVKyVMTSjP7m/p9lfEOuCZodIs/HE2T56gH Nx0NFSjmq4h/zFBXqJST5HeTVRovzN4IWBCTQfM7JeX6ojJBZRnmcVPceSrLTUM0 3pNqPoIlZi6nhb2YCFJz =LXpk -END PGP SIGNATURE-
Re: default color transparency broken in Snow Leopard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thursday, September 10 at 02:19 PM, quoth Vance Shipley: On Wed, Sep 09, 2009 at 02:32:53PM -0500, Kyle Wheeler wrote: } What's your TERM setting? I usually use dtterm, which as I understood it was the most compatible with Terminal.app. Meh. dtterm is, I believe, for Sun terminals. nsterm is more accurate, because it's for NeXTStep Terminals (from which Terminal.app is derived). } I use nsterm-16color for Apple's Terminal.app I don't know how you do that as there is a short list available in the preferences window and that's not on it. I do it by adding the following to my ~/.bashrc file: export TERM=nsterm-16color Actually, since I use the same bashrc on multiple different machines, it actually looks like this: if [ $TERM_PROGRAM == Apple_Terminal ] ; then export TERM=nsterm-16color fi Can you try opening up a stock Terminal.app window and see if you get similiar issues? With dtterm, mutt complains that most of my color settings are invalid, because dtterm doesn't have enough colors (officially, dtterm only supports 8 colors, while Apple's Terminal supports 16, and I use all 16). I don't notice that any of my backgrounds are non-transparent, though. ~Kyle - -- To believe in God is impossible---to not believe in him is absurd. -- Voltaire -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKqV5xAAoJECuveozR/AWeApkP/3CkIE7O5e2oTp9zes1Qe5n8 MnHQwLX6W3CrL4K0KJ7l7s8eO91Ttoj03/cQTyWwIErmYUG9kzH0RVJAacLvcBkY U15jWwLBEF2PRW4LDRKfYjponeZuzElrAblHJysVMJxdOBn1wpeJbOf++oZQIPYz tkd9zdXtcf5Ngd21odqDPu+CX51EdcGYs0ZPwDdDaykdGOEhQ/XJOVP+bWie7cem 6uBTN0z1HXSyQtPflUVGJ3jszja8WJWT9tVbiHgUbpvO/Ie15mpQ553F6Ko1bQZP BsCIpX6GQU/u/Vj2qYvFqE/T7No6S65zPqvHhXIeUYvyXYMPRRYXkeYOTFQGd1Zi jdu7gXb8OBIAV8dDta6DjDRwyRPruh4H5XPqPKdhxo0p7hhdzkw9gGkiTzHnBpRr APvnoTq7w50yCe/ETizCxmmUN3lJS7q0WiQi0lgsYTbPdX4k240fp9A5NhMSx+Ka +N/+fiFBVG0Dk1NbyiTF3Dg+/E4Yc3GGTAWliTKxLYZ3M4r6o7x2hX9KVJjdXbGM T8CBtGBtXiKA7JfEHKMYNm7Eb35zrPQhsv58yyGkefRcsF6H3xbk4ngRg4DagpMT fQO7VmeIzTWuJha3GPep0DHyaUVDGlWvGdojx+wUIH89motjIpBhP+AtfTEhlED4 5J2GKZFpavVvsUqNTu1M =1/zV -END PGP SIGNATURE-
Re: default color transparency broken in Snow Leopard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thursday, September 10 at 04:04 PM, quoth Derek Martin: On Thu, Sep 10, 2009 at 03:15:52PM -0500, Kyle Wheeler wrote: Meh. dtterm is, I believe, for Sun terminals. Close enough; dtterm is the standard terminal application from CDE, the Common Desktop Environment, based on Motif. It was supposed to be platform neutral, available on all major Unix (or more accurately, X Window System) platforms. Fair enough. In any event, it's notably *not* the Apple Terminal, or even related to the Apple Terminal (as far as I know). ~Kyle - -- My definition of marriage: ... it resembles a pair of shears, so joined that they cannot be separated; often moving in opposite directions, yet always punishing anyone who comes between them. -- Sydney Smith -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKqWyVAAoJECuveozR/AWe5I8P/1agKfApBYeShGwK6fIRII34 P67ptyaSVcELz9FrMHw19B7IqbRnNGk02D9Ur+rp5v/2XzR/43j2NnmkSUT9ifVI Ieu7qreMD5ljy0A2cmu/xaQ0t3mwgUiy/JxgP7sN9J2isnV5A84LHB9nJoXUKx/M CuOqQOq+Ry3h22Sph5RU53YNb7TkHDoa7ygERAKM/hYd+Kj+YajIBzwoejw9kREp i1jmLGampdeeIZ1zFaw+wlOQZn7/XzUr3Zyw0sfx7jZigRtYv3qdqG3hLa8s/1kO Jt4ejdS/O8HAxOipAMdlMuQdNxRuIaizh+2cjBCBuHNeN8BKaaVn/YcXXiH6lW9L 9EV4O7ELgjGewI8RU1H2AulATlUiyWEXjZce+EofR5my89Ux7NYf686SWzyvDIPv 1s7QxIbk99GZP56v57BUoHBOnRujzNEsa6wkDwFXyMRqk+k6P5Lo0+F8ifvpB3R+ ABcUSrsGcZK+jajPL9fKnqB6X+rUKma0Y5j9d4esPfYM95laZKZ2HHMVIcUJvs8j HkwBF007eGuhWC5e/HMOUck8S79qyE6FhfuQAq/5/AHC5t+7zoh/HU6XfsdM/VfJ m7LNX+NULVKOJc5EmnW1g4wAZ+Ia+wxHaweQ1MQ3lC94ambKG7mU3/dAvyUajITm DG25vsM6sk5WTr+2Y45L =09Iu -END PGP SIGNATURE-
Re: imap cannot resume from error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thursday, September 10 at 10:19 PM, quoth bill lam: I suspect it is network soft errors or gmail impose restriction to prevent abuse by limiting the number of email download during a session. It reported an error code of 800ccc0f to thunderbird, but thunderbird can resume download as described in the above. On the contrary mutt imap cache apparently cannot resume from error, so that I can never download cache successfully (I've tried for nearly 10 times already). Can this be improved? It probably depends on the error. I mean, Thunderbird may be erroneously assuming that all thus-far-downloaded messages are valid even though the error message is intended to indicate that they are not. My guess, though, is that mutt simply doesn't trust data received via IMAP commands that ended in errors, and so attempts to verify it. If you could produce a mutt debug file with the tail end of the IMAP conversation, so we can investigate what kind of error gmail is sending, perhaps the problem could be fixed. ~Kyle - -- Man cannot live by bread alone. He must have peanut butter. -- Bill Cosby -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKqW49AAoJECuveozR/AWe9Z8QAIEHhI8LRVZGVE4PKMp5Ja01 qqWGkW64FENtZWWklfQ0bVgrw/kXwVKC9iZz8ED+kY+0ft++O73zAOz0rEFo0DwB UgLv9N7NRB1Epa3hsnQC/7ZkrvJQDlWavOPzVIY8xMbJ3pXDa5puqL4rEQDJ/U8E fuaRcJYu7QDK6fnP+urLu0qD0NbPoLDojKoPyogVAjUslRg+wpUEJhLYr8edW27n sP4/d4l11Os/5o10YaHG4GgPXkqb+rLWBajOdTyfds2XYqD5OGerBD98N11Uxll+ tTlmJkkiwgHpggQDTZwg1UFtu52LCkrne7hXREtWtsy5Ch0U1qYGrGzMROJ5D2v/ aFNMaf5+knAVFaUeyxMO3dui/vnOrbRP7CqGqqFdkCjh41FGM/Mc6R3mYXoChEAt Hn0VR8GEk+FJVMFIlqyae7m1UipHKXKWWhpLu/U8R7Pv6HXf6L4N9A8yzSTcM3jo luom02J+SU+AHFIp3n9fh0XuupCqqv7AEwOE/9+ZruzU9+VciPowJZG3EacQKnhN XuTS1K/bKn7UFkFoiQseXDp4jOSCqnoX6OtP2voG/CD7kwIlb9Rgg5yFIiPPq4o7 lNn7KavRrBXwxEeKX64ooBM4bnqXAb4bN9Wd76fMIKFzNT3QCDu2l4nJbT4J5mIO nlRFBMDFTCXbHpQgOevD =+ZNm -END PGP SIGNATURE-
Re: imap cannot resume from error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Friday, September 11 at 06:44 AM, quoth bill lam: On Thu, 10 Sep 2009, Kyle Wheeler wrote: If you could produce a mutt debug file with the tail end of the IMAP conversation, so we can investigate what kind of error gmail is sending, perhaps the problem could be fixed. How to do it? First, your mutt must be compiled with debugging enabled (when you run `mutt -v`, look for +DEBUG). Then, run mutt with the flag '-d4'. That will create a file called ~/.muttdebug0 that contains a transcript of everything mutt does, including the full IMAP conversation. Re-create the problem, then put the tail-end of that file somewhere where we can see it. ~Kyle - -- This 'telephone' has too many shortcomings to be seriously considered as a means of communication. The device is inherently of no value to us. -- Western Union internal memo, 1876 -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKqeNCAAoJECuveozR/AWekagP/1u8xXR9/H59nq9XGRt2nfit kRpsQwDJz0rEUMMTdXsUA/w0Z3rOwhqM3D+r5eDHiKuz/b6LzszKq4PYWENCoTlb AKCXhaqeDaIRkUlEbZws5N79Q0Kw3qfGl09o3O2kdg2D4fdho5f+7VgCC2v9Pttx 0fS84RYXmXNiXHRxXCebBCpPquX1Efe3VM/N5xObR3XpWOQsynaRt8GIJCX+Za4d nEeP8C93ba0V+z30YvXJK9bKa5+bUFxZbUovwYSs0oOiKRT6JjzDRNuXU8b4VaIY Lq2ejMuvKiRjAC7xj8nAb3u+M2I7nAn0P2QAk4pA2AELyFe/csu94kNUzsIwi4L9 59TgRb18mSpRF9SDSIhIAcAAiPstmAA7VhMWGgpokh00LkhPLp+yj6BS2U1MujUP bqwzFQhnerj46nytIwAZaxSSGZPONz+3W/HwdvSYA3d+tidsnDYsOoRS+ImMlaJs UKnWoA12GDzT4FKHPb6C4NUrxqwmQ39BIuAsY+p56n94NRDMpiLh391BiXYUm59o cWz5o3duglSfBSV675lplGcNVR+UhT3K3vfb10O3R9YZlDIKHtpgLwSNaBNSstEz 0bptIn2MtN4HTZnT3h8MSqJK/NBtOmTrksUtirekxAcRgTGBqbTAq23le0Srcc91 +TLm/4LE7KPGirOPcYfr =jL1c -END PGP SIGNATURE-
Re: default color transparency broken in Snow Leopard
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, September 9 at 07:33 AM, quoth Vance Shipley: Since upgrading to Snow Leopard my colour definitions are messed up. Anywhere where I set the colour I use 'default' for the background colour so that it remains whatever the current background colour is. With the upgrade this no longer works, the background gets set to ANSI white (grey). Interesting. I just upgraded to Snow Leopard, and I didn't notice anything like that. On the other hand, I use my own termcap definitions, so my guess is that that's what's changed for you: the Snow Leopard termcap definitions have changed. What's your TERM setting? I use nsterm-16color for Apple's Terminal.app (I modified it slightly to enable the alt-screen feature, but that shouldn't be necessary to get the right colors). ~Kyle - -- I am ready to meet my Maker. Whether my Maker is ready for the great ordeal of meeting me is another matter. -- Winston Churchill -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKqALkAAoJECuveozR/AWesykP/AhPKXGn0eqEpxgOnEMItqlK rjztrjlt7NqpyqnRIwFkemTCbDuZ6R97GHxaTz7baKxmngLqCrBx3r8Aoj3TLLsg L+Kdjq+J28ANN6XR0jGY7oCaZERbndBuDuRjz8EQyTGxncNOd/0j/EL3cTKA5G3E YRLTlk++rgn4Wpe83vPL6hPFlFtguXSFVTQ4jum+0I6ge53fA/nwtpeJSCXkTXqF 50/N1v5FDtNzxmSnGjm3TTW1mx+mzTye4pE98QAahUiC1wuCrp6zAxd/dvddsKoR 6OYsGWe5luxTJoeH9RTrciFc6YYP/yp/cLCluvlbPQdtWEXVPZvtN1gcf+mHRw+z JRt0uYkiH47ExaxWw0kRky2GJ2I45Auf4HJwFBSta9QtImU8d4uAGF8I2hZq8ZUk 32sh04AElhEolT51KnbmXfuYlYwNF+2rjStItkG9JmJHyZEZSZ4XLp8IBDY0ZiyP TTQmv2mwp0h4nLOTrqJiHVrp6RWNK0EY4gDBprwo7D3nCeoDTalWKZ8NB3Rtq+ur CC1kKflKwBTb0gwtQPpIGai4AmzTkTp8egaZW7NempEenex6m3hRyAvViRglHCRO z9xqQTF9fDnYbsRoNcl0lEkfDhkuVl88m0Hid5VS23Tan77VxJnV37E6a4ECtO6X pCbJq7JCZMqlrHfbf0d0 =XtI/ -END PGP SIGNATURE-
Re: The MBOX file paradigm
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Friday, September 4 at 09:49 PM, quoth Chris G: Depending on what/who created the maildir hierarchy you may find it virtually impossible to move directories (which aren't real directories) and mailboxes around. [snip] Mail.holidays.2009.sarthe [snip] I fail to see how this makes renaming or moving the sarthe mailbox virtually impossible. It makes it extremely awkward if you have some mailboxes at levels part of the way down the hierarchy, it also make the names painfully long. Okay, we clearly have different understandings of the term virtually impossible. I read it as cannot be even theoretically accomplished, except maybe in some unusual circumstances, whereas you seem to define it as merely extremely awkward. By that metric, all of the walks in the Monty Python Ministry of Funny Walks sketch are virtually impossible. In any event, I disagree about how awkward it is. It requires more steps to move multiple mailboxes at the same time, yes. But that makes it more involved, not more awkward. Compiling mutt from source requires more steps than installing a pre-fab package, but that doesn't make it awkward. I note you haven't questioned my comment that maildirs are difficult to delete safely! :-) They're only difficult to delete safely if you're expecting them to get recreated at any moment. And that's only true if you need an algorithm that doesn't impose arbitrary naming restrictions. If you're allowed to do this: mv maildir ..maildir_deleteme rm -rf ..maildir_deletemeXXX But those caveats apply in *exactly* the same way as your criteria for maildir being 'safe' for access by multiple applications! *My* criteria? Perhaps I missed an email here; at what point did I establish these criteria? In any event, I was wrong about the renaming business. There's an inherent race condition between knowing the contents of a maildir and choosing to delete it. An atomic rename doesn't help, because there's still a race between knowing the contents and renaming it. This can only be done safely if there is some external locking mechanism to tie those two actions together. I don't think this is a big problem, but... shrug ~Kyle - -- Our lives begin to end the day we become silent about things that matter. -- Martin Luther King Jr. -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKo8/BAAoJECuveozR/AWeWgkP/0FyFWB2AK6cFf7sTgGdB95v JQwTaOarbR6HzwRlC5JA6WgCCNAIiuZMpq9auGkgPW9u/00IhYi0cC+Ks/WgLwDJ ZIK4pLNmvYuB5aW5L4vimboVBo+b8oHjvmRXE1EMADp80iLqhS4Px91a+v8pDBDl IcpPOnPn2kRtVKO+mo+KXWoUh7Uq3G8u3gQSnGmOp39XqzXm6k8Jo9vnrFuID2uw AG/sko8qh3isC79+wQSJqSvUuUxsOipHa6EX7p+0KCjLQQso2BxXhYbg1aEmazIe W6kIgsu9779DSusmNd40Xwyy0QJ0O3/SI0cJTkJzBcyQb8AiDLvu/vvO6CBXXA3w 4kggdgYYTSk2bvBu8N4TON0iOgQ+CKjuG62DLPV9i4jm4D0Rd0PAzr4P2Mpf/Asr GkXVd7ZiSEga06J07M6GAbDZremwUcP+VMvreI61UJIe3o6aVgmu2GjI8uQ7Lrls Kkuv2nP8wPyvPKYOIm/Q02SKqcd9KZBuOaiA/3NfvuAcHjkN9aVNjEDtNoLd6Ps9 thzuSS0FUX68Ez/DB07Izc2pwlONGzAlm35mJtCGUf+BmKWLAqMQ7fkvSCcFPROr bPB49MDQr4HNsVdczBvnoYx0s2UX0UvtA8M6eiAbhcb2h8B4fWGrmxjMS+H8oy7r dKadDTXl6Ha39CGviC1k =r4XN -END PGP SIGNATURE-
Re: The MBOX file paradigm
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Friday, September 4 at 05:32 PM, quoth Chris G: The advantages are: - reading/writing/moving/deleting messages is faster than opening an mbox, looking for the right message, editing it, then rewriting the whole mbox. Possibly faster for a *program* to do but not so easy for a person to do directly. sarcasm This is exactly the same reason that we still use punchcards for data storage. Sure these fancy magnetic storage media are faster for *computers* to read and write, but they're a pain in the butt to edit by hand. If I see an error in a punchcard, I can just use scotch tape or a hole-puncher to fix it. But with magnetic storage? Forget it! /sarcasm What's your point? Perhaps you edit mbox files without using these newfangled things called programs. You prefer to simply load kernel modules to edit them? Or perhaps you break out the oscilloscope? Otherwise there's a *program* involved. And if you're complaining that your program doesn't make it easy to find/edit/save email messages stored in a Maildir, perhaps the real truth is that you're using the wrong KIND of program. For example, we abandoned the idea of using text editors to edit the content of SQL databases; that doesn't mean SQL databases are a bad idea. - grep returns individual messages, not an mbox to search through But on the other hand you have to do a recursive grep through a hierarchy of directories. With mbox there is a simple text file whose name is the name of the mailbox so you can easily 'grep name of mailbox' to search for something. I don't understand your complaint. Is 'grep -r nameofmailbox' difficult to type? Is this an argument about the number of keystrokes? Plus, your simple alternative doesn't provide the same features. Yes you can 'grep nameofmailbox' with mbox, but that only tells you whether the text you want is in that mbox, not which message within the mbox it's in. It doesn't even tell you which LINE it's on. Sure, you could use the -n flag to print the line number, but that's just as difficult as using the -r flag, right? Depending on what/who created the maildir hierarchy you may find it virtually impossible to move directories (which aren't real directories) and mailboxes around. Why not? ~Kyle - -- If Jack Valenti had been around at the time of Gutenberg he would have organized the monks to come and burn down the printing press. -- ITAA president Harris Miller -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKoUmdAAoJECuveozR/AWe1m0P/jPudA1jsuXZAXunT5Qt2tsw +2WEaFnUaetIQKpp7e9oJPXNC+58UqkvV1JUugLKiIrgLDuvyKkZqTK0wnkfZoSa HuPnO6BG+1lVnciqsHiHywqnuiF0ahfbyhjKLqKtvNQS28i5msNR5X0lWvlg5Bh8 C9naW9UsOhbmpVDq9uXs0S7s0prDjW7wtO7QfSzODoy+P/kEE4u/stjv9iouFUx+ 8iWooq+lEzteBcHkOafPCMqzX2LXLDe4ub9BcR2Y4M54Iqc2wKVDkExOGURsMDN/ USZi5OOtlEvcY3/1oqm/A2EsWN072PILnxY7n7zJYOo4Q20Z3tJzVh9Ql+eEZco/ Fy2KnN1wtYKoazTjkMcPhnAFDx7CTHux1xfn1gw8ZOZTPzFsNJw+bGLX5ObMhBQD u8Nnl70ITV5EQqlL28HwG1QJ77dbtyv5unEtJQL/iqdNq7hS18d7meBadrtu/fuO TpmRg7n6iMIyuIqTcDW/Wqp5I9dOdiLIuadBvpg7GqY44JsYVBXRALj6cAQjHkLJ N6QavyuMZVJ5cyfl9qFAoXjwLRE+RjDTOO3nlGumqE5ZBj4ThCkpSth3r2gmHD/j gDVWGBEK/U5VPF7zCikfiKtH4ZePHvNVgDrCR5QIMAQ1KYDc6UHhuufDBJxvqzgk fbfJWVqxAs0QQ5fvTj8J =RUjc -END PGP SIGNATURE-
Re: The MBOX file paradigm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Friday, September 4 at 06:27 PM, quoth Chris G:
- reading/writing/moving/deleting messages is faster than opening
an mbox, looking for the right message, editing it, then
rewriting the whole mbox.
Possibly faster for a *program* to do but not so easy for a
person to do directly.
I was referring to re-arrangement of mailboxes in particular, not
editing of message,
... perhaps I'm not understanding you, then. Why is 'mv' slower for
Maildir than it is for mbox? On most Unix systems, it's the exact same
operation (modify a dirent).
anyway when does one want to edit messages, it's not something I've
ever wanted to do.
Sometimes comes in handy if you're using email messages as notes to
yourself or if you have a corrupt one you want to correct or if you
want to test an email parsing tool you're writing... that sort of
thing.
Depending on what/who created the maildir hierarchy you may
find it virtually impossible to move directories (which aren't
real directories) and mailboxes around.
Why not?
Because *lots* of them create maildirs which aren't real directories
but use '.' as a delimiter. For example I have:-
[snip]
Mail/holidays/2009/sarthe
Where bikeRide and sarthe are the actual mailboxes (with others on the
other branches of course).
Many maildir creators (most of the maildir+ ones I believe) in reality
create the above as:-
[snip]
Mail.holidays.2009.sarthe
I fail to see how this makes renaming or moving the sarthe mailbox
virtually impossible.
So all the mailboxes are at the same level with names with embedded
dots, if you want to move mailboxes up and down the hierachy it is
rather difficult.
Meh. First of all, if I'm using mutt, I can use whatever mail folder
layout I want. Second, if I'm using the Maildir++ layout as described,
it's usually because I'm using IMAP, which works the exact same way.
Third, it's not that hard to rename multiple things with a little
shell knowledge. For example:
for F in Mail.holidays.2009.* ; do
mv $F ${F/.2009/}
done
But I suppose that all depends on your definition of rather
difficult.
I note you haven't questioned my comment that maildirs are difficult
to delete safely! :-)
They're only difficult to delete safely if you're expecting them to
get recreated at any moment. And that's only true if you need an
algorithm that doesn't impose arbitrary naming restrictions. If you're
allowed to do this:
mv maildir ..maildir_deleteme
rm -rf ..maildir_deletemeXXX
...then it's not difficult (as long as mv is atomic, which it usually
is).
~Kyle
- --
Conscience frequently errs from invincible ignorance without losing
its dignity.
-- Gaudium et spes
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!
iQIcBAEBCAAGBQJKoVldAAoJECuveozR/AWejl0P/0koeX8g0hfpDgpLcZBA2hbr
+beTZwJh8oxIlcX4Loclig2J2UkY7yJ1ZqcoGhxr4hksS4NC7JUDjWvJZ1YhPTva
kNMbZHf0iSxGKfcEXO4WYSUbroTNdAagq2YGWlRHaH5f39xtZWpQ0Ss8kQgXKBmb
fzZE9ovN+M/czyS6zFr+pJElcQUvZCJyc70jKowr/jSYWV5MuRuF2pnfEMrwwfXz
bggREaFpB3jP/gDG3nT55FLfWWc4t1g78PER4hvZVPDTy3BnjANDRDNsrvKysQDZ
4sowjVvGL/ZIjqypqsEflToQpobfSO+u7da9ayTvzDHYuJcKniFAtA6KjVUqKLUY
feWKlJFRqkiH3TpcO69dO6/QNriASNhbD/W+Z7FTYp6ZLwyQ5AZC+UcDz85mcwyE
oomQDV428MpXUXoTldke9FPaHOya1fBpPHmlMu8HU0tid09lpnsKQC7UQFCZzTdA
pYXmAzd9Gi+PB3AbJh8G4GLUKc17Pz09XyzPBDwQEKUXg9A26uJte/b+XuAnNBlR
0wEGs3NvfJR2BetnDVK4CMkFUMzH0vtRzARwRB1Nx8LakXdbaAFUtOeZgC0/aWw/
h1ZQkYUyDboZFkpQcOwK3ui+ZM07C1p8iYcqb7tshpM5xmRhogCxgBTdw7u1MPkN
UBRfSAYr8nDJlgetqdtO
=HNN4
-END PGP SIGNATURE-
Re: The MBOX file paradigm
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Friday, September 4 at 04:09 PM, quoth Dave Dodge: - to remove uneeded attachments when archiving a discussion thread. For example a co-worker produces some software my own project depends on, and has lately been mailing me prerelease versions for testing. I want to keep the discussion itself, but I don't need all of the attachments since most of them have been superceded by later versions. In most cases, mutt actually makes this easier than using a text editor; you can just delete attachments from the attachment menu. :D ~Kyle - -- Do what you can, with what you have, where you are. -- Theodore Roosevelt -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKoXnRAAoJECuveozR/AWeh9oP/RwsH3ECWtJn72A2G8F0VfHm Xlel4At1nGJj1zCwmOjOfE7ULC81AJMYd/yqG/T4X5puiGS2GEecS3+tKcWnn3TF H5OuD/LbkK66udD60mvYfI7ZbrVx7dqJofON9B2COgXLh90apVX1vPrRHa/NJ+be pQA67F0tZZQZg+LsGiWWkpx2LRd2Yh84Q5R3inHHGEpJUQfA52XrGSbIv28JtsBR gX9Efw2w+1kDtU4L2oeNtjWM2ott5qyjyl1h29SpnOU2hWFQp6IVo6TE/rgVTCfe 84yPBnwMAR1gOazmxt86iM0q4JWhG+d3hWHM9FGFv6Xh/zl/TRkV+ew1in7SXsab wkpSmy2B3kZdrT0SFU/+DLTxBm+CEaDNjAq7l7HQ1fM8YUOUkkJMbEH+m3GXR50P g2bThPQg/ZeJQVFfFWGn+j08FNyE3CpHG719u77Vx9XWNlzhxmdUPA3TUfj9zU5h ZbQr3TBhL/7Qcfd9L7g/WyVLSfCHwzWF3tm6Dpx8kocCAlkt0204EdugUo2aX6UQ j/NaRdWUO8El8YMZ3O2FmzZdB639JksK2sxh7y5JbZXnsNOrBpDR3Fxq4J1Ovz2p kYvXhKfqamc7H7lziWKDch4acd5eE08+seIHjcTGO3Wbu4d2NlsKetlJ2UFf+FRD WEvE0RXe3STeunWGeGUJ =ZNgl -END PGP SIGNATURE-
Re: The MBOX file paradigm
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Friday, September 4 at 04:43 PM, quoth Thomas Baker: I frequently edit entire threads in order to circulate their contents -- with redundant quotes and attachments removed and headers pruned -- as digests. I wouldn't know how to do that efficiently if I couldn't just edit the mbox file with vim. There's always edit-message in mutt. ~Kyle - -- Make no little plans. They have no magic to stir men's blood. -- Daniel Burnham -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKoZ+LAAoJECuveozR/AWeveUQAKlGEJ+gisPlvZsGtORg4KV+ YdXd/TFTipP1qiMxGbbpVo7E59HxW+KEtfbwvLD8xwtlNay3Cv08/6/yz0Yqn9kt QquF0+Ve9O5d3qBFKEvz9RhS9faQiOfP2KqTg2QXaW2BK65z7zdkkYUSlld27BaQ 5qpjJSiwCmPPsxAWQXrLK8WqNjSvvr/V7pSdZNT9XBG5aObZRKIoEkZgnozXAiUr LOjmBNQD4Sd6H3OKTiuIBq8oS3iyP0mazF7F6kgDQRxpeWsd1kK+MsvIoT2EouQV MgH2HPJvdlUcxlBaQLKf5tU5P1aLStzp6twZTCWw8A79dD9HhvvV0OyLb2GH+eUg txAVijpYIUOD3lbI/0gmW8vwYRS8Y0Qf8OcbZOsYCqqwJ0lUtyKN0uNNKSVSci0N BQd5tSrfZ1WeU+YWJ2oUoHo8nuKb1uk+Wfvwt5mQCwG6lq6WmGTdAt3i8HcSJYkZ z4KzxyExO1PrrEx1xlC1VBOFQ1IdI2cNVee0N874GA3C7oAglOoLJdzcPbXmgpRa RcBRSVT4VTa64fV9SmufqUXa8oENxu2CEAMSWAnaGHz42sfv/DnjPU+/Jhw1lE5i 57l1JJL5cUoV+AYmGwvYbF9webQs05Q/S5UTueQ9D7xNLrEiZoLbbSBw5L0z3FU1 Ji8NeBUe2CiKN9vXxIK2 =zXj2 -END PGP SIGNATURE-
Re: [solved] Re: Selecting INBOX...gdbm fatal: lseek error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thursday, September 3 at 02:04 PM, quoth Tim Tebbit: set header_cache=~/.mutt/cache/headers set message_cachedir=~/.mutt/cache/bodies set certificate_file=~/.mutt/certificates After reviewing my post I saw this. And decided to try rm -r .mutt which worked like a charm. I still have no idea the why behind this. Could someone fill me in? It sounds like you got a corrupted file there somehow. Of course, since it's just a cache, it's safe to delete it and let mutt start over. ~Kyle - -- Imagine what it would be like if TV actually were good. It would be the end of everything we know. -- Marvin Minsky -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKoC7mAAoJECuveozR/AWepWYP+gM4SZT7AR5gSDQNMaOGekN0 EHIKlCy7sgjfI0X/TS+bokSiSTZgMjvlB+gae7InaGOORB8gS/IczV+VGF3vU3xz kHKwq7ibsy3rtTiE1W++LeuOGOSv3zSh6jQROeNPfGwwzbnxyYvsuFvtg8ymR2U9 Gx2rXWHhe6jagr9LB7hNMGUcTaxoyKYaPlt6R9OhAQ+ZP45D6+Fgj5mXEq+Hk2RH jacAPAzA7MhJa32z6qd0fRaBPQJ19l6S+XSZqS2O0XmPA6cW+HB0yUum4HSGW0sg sgdt+rgl5KxbokH8vVrlWYSUNymHVPfK8dhxyIBfBABGmPcmioHduGul8HoP4HzF X2n9gn/LEririMxkngoRnOoxLeF+nMAKJ9OI5JViD2w2NgNFyjbpZyCQjXTW+ycX AFtf5OysuDMvsOJwPZlewUhv00KzN5jFD57i832wZU4AHsXCFzbsAwtdGtuy0K0q FuB/r29lfQe0DXwrY+tHBMQZM5S91YxEG8usM0XW/WVtL6wCzonqp9YMsy7toR7a ZfdAL0bxgzFRybT5UzHIWT5v+fpHPQNFo3ujujTKolxI+0Yl9D9mpbuKdXjGIcgV P19I9q6HJbQ1uClqThWFSOmWcmU/YDheUW4RGuujm78PtrCjmLB2XaxQEEdW45fO QV7kRoKPbZXVT6P3w12X =njk7 -END PGP SIGNATURE-
Re: Multiple SMTP Accounts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Friday, August 28 at 05:49 PM, quoth Cristopher Thomas: I have two separate email accounts, and I need to be able to send mail from each of them. Is there a way to set up the two accounts and then specify which I will be sending from at some point in the composition/sending process? The short answer is: yes. Here's the long answer: Email is, of course, far more complicated than even that. You can, for example, usually send email *through* an account that claims to be *from* the other account. This is sometimes useful, and sometimes not. For example, I have many email addresses on several domains, and I can send email from any of them through my primary email server. Many people do this with their ISP's email server. What I'm saying is that an email address and an account on a server that will allow you to send (relay) email are separate. As such, mutt treats them separately. So, you can change the from address of your mail (e.g. the $from setting) and you can change the server through which you will send your mail (e.g. the $smtp_url setting). If you like, you can change them both at the same time. There are two ways that people usually handle this with mutt. They typically either use $reverse_name to ensure that the return address they use is appropriate to the messages they're replying to and then use a send-hook to match the $smtp_url setting to that address OR they create a macro that can be triggered in the compose menu (i.e. immediately after composing a message and before it is sent) that changes both the return address and the sending server. Here's an example of two of those macros (imagine each one is all on one line): macro compose F1 enter-commandset smtp_url=smtp://domain1.com from...@domain1.comenteredit-fromkill-linem...@domain1.comenter macro compose F2 enter-commandset smtp_url=smtp://domain2.org from...@domain2.orgenteredit-fromkill-linem...@domain2.orgenter Make sense? ~Kyle - -- The world is full of willing people, some willing to work, the rest willing to let them. -- Robert Frost -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKmFgnAAoJECuveozR/AWexK8P+QH2V+g0lQs38CfhKOhAsI2P x0fb4x7cQrSun7WlSHgYDyoqw1wA0gq0cyiQlTb38UzV7WKBeyg1LbgPIrK1k7i0 sz9CmQHsmD6QQrOAXELiM07eFsvhmnuOsfpusrhBp13P1gjX6ivlwQaOsWpna9hs H/LOudcqfdLYwFKcx5FC37afixBnX7a4wDVw/1lZ0YmaT0gU2OQlWYsPf0UsdIVg N3bC1VJdB5fP1/usN3M2wKokj5yRMIZvHRnRJDyjOReiS41yBpsKMp1mNpzEr3cP mQ/llAXJEywPLGWGaefU8DbFlksSzYYOJBsj6TBpXCdxy1iKI6e2pK5nfmmpxAos +SvcjjlP1q4qfytghpWQCffV4Z+znrG/EFihQghd+wZ/xb8UFv85fivVrUFufc1p 0TShcRF8OX8G7+5ZZmJqU/9CPr0ZKSuh51Wx4W3HmKjd6Vq8t9xv1k2OvDEOuNWh gUBNG1VVImMCp8DGQU2bDSuBYVOR9tPuPAl7RdHuiweM9LJc6MyLgU88lwGeZj15 8LDN531EUZze54eFHxOF9nTh9Q//77NHapJyeC9pOAJQtiMXbWP1Nm15Wzu//DF1 wS1Pl2oFZrpjNntER+5wLYiCpPmvgEzZ5dIi8TgXyAkhGKZY3oINg9zF1nnhPHQD FLddQ0wST192qHcj2+3t =1ylx -END PGP SIGNATURE-
Re: sidebar - square bracket with number display
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Friday, August 28 at 07:42 PM, quoth Joseph: On 08/28/09 18:11, Joseph wrote: After upgrading to mutt-1.5.20 with sidebar I have notice the display looks a bit different: Is there a way to revert to old behavior? The sidebar patch is not supported by the mutt developers. Your best bet is to ask the guys who maintain the sidebar patch (good luck, though). Sorry. :( ~Kyle - -- To announce that there must be no criticism of the President, or that we are to stand by the President, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. -- Theodore Roosevelt, 1912 -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKmLZTAAoJECuveozR/AWeVK8QAJ7HCtW63Ni1grMWauSm4dfA /nIjS0uN1CpWB7oqLHephAqsxPomBH8ehlAXqL44kMl8HmiOGUeiEUr+/MirHj3e rFLiaw0nXA0XJwB5ijYlNd2L/kEb4dcjBQVoROgwsiDZf15Xd57rPMRugfm6IU1H Opsn+cofC1Z7hlIVGpsYjMeYPBSZyhi7iZUi/bLXRu6h86D7AwgTfoWMLHFG9Ygy wlG1ilTdVVKBsFDKeb0RSeWKE0oE0WM9sIJxGMxpHPWCxBtkAoo+xlVtsBCNvhBz +acC1yoIjV/BUz9+Tc19I1uG7JjCkPx0M6n2vbvGh3lldjD2DUL808xf5Kahih7O kl1rz1zfgAqqDERqucV+NSjFVR0TrJIi8b/+placuKmDDoHpXsPXAvViLsLjrDEF U1353Bna9EIH8ZXuJPPhSPyrl6ORJ1nWeXhj8tuRJ9n8hJOf3C0R88JO2JFK34Ps PqIFfjdyrwCUj0t3ECLMbFG55BTw/54oFj/NMQMyBqegJ+e59T/Z0O7KMgdcdgYd OPwEg2zbutj2PgAJY9mWV0RoEl3HAoFTCsKEsUc4Pkgm9Gq9ZW1NKu8xXipX/AwV siuBFIBzI/C2dekpWNoaBksyZKkoUlVR3PpYUJHuR6j3xzu8Ce01W433H0Lxvqdx iHBOQRRykAzrV3eH03lG =466T -END PGP SIGNATURE-
Re: What is Spam
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, August 26 at 05:48 PM, quoth Terry Johnson: Since this is my first post I just wanted to ask what is considered spam on this mailing list. I did a google search but found nothing. Just wanted to know? I had used mutt a long time ago and just recently wanted to give it a try again. Well, I think generally unwanted and/or irrelevant and/or sales messages count, but I don't think there's ever been a formal list definition. Put it this way: there are no stupid questions (well, okay, there are, but within reason, there aren't). ~Kyle - -- Faith is what someone knows to be true, whether they believe it or not. -- Flannery O'Connor -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKldPXAAoJECuveozR/AWe/3MP/1SDnRbBb4oZ6Lr5yGqHdU/3 M3P6UpGhwOtdk42/fDsT3I6lZa+3fC4etK+TrpFuz1L2qzEdIDDiJFCBweWpj2/6 OLFYjvQIEIvuAz4vNQb3E7yo08JUSiSapFv2TB4e8SPioUwinvs8LfONj/L7dQZa AoJaMst9N7slzfPot5yruvteBcDEDwb4goL6a/+Sl8P0lvI9ULGr4hECrO4rfYPE 7NTEoXfUQMNl9zbsqUf65YPA0A5yLanrJARxDKUGMkb57yYXhfnPnGVMpEUrLJHv s9D1DOfwx5g1jMJ26KK98KGTTNFCwbeEimhfZN9fN5Rg1gJmT7HN3Zz5lDmWUFyi 6Tupu3P5ELoVGgm3/B+96C6Wa1XHvU0yjYFFD5fg/ApxwKkxGeZqQFXX6uyNUyOD Iubju4VQb48jieRfhqUvgHETLZTmk0KYUJmfKquvp38GDztGjJTnk/TpYLexyyVO 1AbZ2j2neqZ5SPdIeGWjx9IXpMEEXkIHM20kHbEeoVBydaD6JxKPG0PRqFkYg0eX SjfhzI5VHGUtCrZa6bNvd8R7cDbDC1Aj4yFRFPD6kKsp8KkpLPXnaIh3WOQmLsoT xvv0ouvwK8MRmzdML1fHI4j5uBwzXYhXJjomhvLW29bQFjdTrZyGgudzd/Mp4EvL BW619F6cBMSqaDHd6IM3 =nQWc -END PGP SIGNATURE-
Re: more strange behavior
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, August 24 at 10:53 PM, quoth Robert Holtzman: There are 20 files some with as many as 30-40k messages. This ~/mail directory was copied over from my desktop box where mutt works flawlessly. mail_check=10. I'll try increasing it later when I get some more time. In other words, if checking all your mailboxes takes longer than 10 seconds, mutt will be caught in an infinite loop of checking for new mail. It may have worked better on your desktop box because the hard drive there is faster and has more cache. What type of mailboxes do you use? Different formats (mbox vs mh vs maildir) take different amounts of effort to identify new messages in extremely large mailboxes. Mbox is usually the fastest because mutt relies on the timestamps on the mailbox file. ~Kyle - -- And thou shalt smite the house of Ahab thy master, that I may avenge the blood of my servants the prophets, and the blood of all the servants of the LORD, at the hand of Jezebel. For the whole house of Ahab shall perish. -- Bible, II Kings (9:7-8) -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKk/EVAAoJECuveozR/AWe4BAQAIGwQ68GLut25H+5CliRAIsn pXh2RiJia5fYZZeB9Pi8c9I/J7S9+8QEbVrNmbijgtHe8E3WsEY+ZmqWiRf783+Z RZPTRDuzOw0MCiKQW7xQB8hcmfykYh6x/CMccb6eY50XW08Q9LQ/1rC0VEN++zRu sYYAw46zl5tU1xykCC41QN+6IXhRBhUGr60uL1+CpP5m2k+bpL8zTdBhbZvA0+m5 B3WN07sj9d9hq+ro7fiZ/GKEc9pcjJ4YQO+6K1+APh4YdZl2Uwqlvypu2hivPWS+ XFsr8k6ASqDr18lBLHrO6oVu5wNa9SDwjSrPv7TqCZIv3J5nbfPKADV+vqEAfeDW 2O9y4vex9qFbKRNQx4v2h00BGaWlOD/d1ldnTxrQ0BAkgf7HoOwuWAcRN9ocfBV6 pqtYsPmOov1dMcyGLQMuT5RfNEaDsAJU2N5g5iafYtrXHQN0HDZU/n38Jc33b6DW mjxqbv7GrjnSueD6Mm7M7btgbMtthhbp99SMl/we5xxaVCrPsDBf9OxvGrGQ9yQ9 cVKGzB/cJ+DGZq0DDuOy4FBIsbChGHBLBYDq0E0P/+FPewtgAG3bXF1ZtVDrOqhG vWJuuSZTaRzObywUUM+aU5zuSJvuyJsghfhWPnf48clqNf/h0WtWUgxyNGoW9Ryc hZFopq7wYSZLkL/2yP3t =Cayu -END PGP SIGNATURE-
Re: Header filtering when reading mail
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tuesday, August 25 at 02:31 PM, quoth Baldur Gislason: How can I change the header filter (toggled by h key) to display only the headers I want to see (From, To, Cc, Subject) and not anything else? By default, toggling the filter seems to filter out some standard headers but that still leaves my screen full of custom headers that I'm not interested in reading. You're looking for the ignore/unignore commands. To limit yourself to just the headers you want, first ignore everything and then unignore the ones you want. For example: ignore * unignore From: To: Cc: Subject: ~Kyle - -- I know God will not give me anything I can't handle. I just wish that He didn't trust me so much. -- Mother Theresa -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKk/ZJAAoJECuveozR/AWe2MUP/RGPYrj3ZW8W7LyEBw0Rk4VT 1kimE6A9qMOZ+k4xnrWkRcp+aU2/qKtuPMx4Ie8iZE7J9UJY4KEisx0NOSRuCklt bXluThIxeKEyMP/DdfJWoPn8XlFMT6Xi+/5O2xo/oRo35zpdHFZSJvRcAEU4qjcm zJ4Gg5Andzj3wqycaDD23H9iqvrBqdQDaFuj3ZwHOPL/NysHqzZf8vXn5NgiC/HL IbUwYpS+ZMQ7EjhKyruy4zYlmGG+4bzzAGR0GhAi28RWrZsRdXq5VYxvqk8JHlLf KwyBjPOWvwh3KjmEkHyJewyrnO94i1sbNy6xhjL4Ahn4aWlxnjD/LfK0WaoHRe3A J2PRoHpbpjFycRdmgpMosWWKvUDhNSxJrDxocEaVRzK9Ska09HRcti2AFVeNSDAE Pb2ZrnepVz9ibU19dRgKSYHrR2GBT8/hVVEfsURUVd4hQHgfG8xU8E9gGCqNrElH I7TzE5pDAhVJdw0acoOFMpqfGM9VUWpRk4Zwr9dvCQ5PB/qmzeQA4DMunEjV6sM8 TaI5WELJWrKv9ms12tdfTWnimHJRyypTt8dB2AAcfdPfZGddIb6NSqPK/137M7ZO 7eEcmaceVmIU69z7bZovbO1gACxwn4L8XTwkVsE94ub3bj4S4ulNVCGOanLxbc/P sSq3jfLh801UoLGycYr6 =M7uN -END PGP SIGNATURE-
Re: long attachment names
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sunday, August 23 at 02:14 AM, quoth Martin Alaçam: That's easy - you're looking for the detach-file command, which I believe is bound to 'd' by default. Thanks for the answers. Is there not a way to make it show only the file name, not the whole path? That would help a lot already. Strictly speaking, the path IS the file's name. There's no way of just showing the basename, though. ~Kyle - -- Hanging on to resentment is letting someone you despise live rent-free in your head. -- Ann Landers -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKkViKAAoJECuveozR/AWe2LwQALMT81gDQQp3t4+uLNLBy0Hd nWjyCCp70o4Nhld2PYa3rvQ3PgmeN/4Wn7VuHulC+Mj/fEB4NTmU84d0dw9ubOSm K4wzXDbPbssGE3vGYblrOzaGXEv3LYT95HK4LZ2csai3Aa9T/OjheFMDUpXuqMjp mEoEkSI0zC1jLQZB3xXNAs8ATWiL6QaNU/wHQ+sRkJP4AEMhpx0hKgBTYaD8r8j+ 6eLC/vx0EztkkM033SZ5gifJWBe2Eew8HkAzbGvqxXdNuVfLfsf2kxxBshvDxnfA VZsB76GMNpuEMQV826KA/Vrp88xvGYMLW8rNq41P8Sviwwx/TZ+WR/JfX1MaxT9U a4OXLu4txr2KacWGcstSb/qQtxnqTSeLCRn8VfbaF6ZpJ7I+5gCmw4IdLG74guxz 5ZhH4enk1CsuUMJhVIXBB62X2KA9X7vcuuLCdeyUM0Hji/rceui+d85U4Pg9+xwH d/4Cq5CSSyi6BhFBQLEf3bLJ3UsejhOWEOWdBVPaM22XbcAbDMrXgrczglYVM2lw NvbCL7BXfTw6R9PHK+hIdV8rF2SEJeVHyLRHvl1TofTcvcruGvgC1OVOM1TiRFBG B1WViu+4LCDX6t6O7auAp7zr7ivgnxj0Ed8C3wRP3ah89FKhAFx1uZQwHMDYQRcZ mn83te3J0Ayz3C1uTRTH =mjQD -END PGP SIGNATURE-
Re: long attachment names
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Friday, August 21 at 12:44 PM, quoth belge...@seznam.cz: I often have to attach a file with a long name. I can see only the beginning of the path. The problem is when I have several files with the same long name and a different ending (like 0908-0403_blablabla.doc and the same as odt). Is there a way to view the whole filenames? The only one I can think of is to make your terminal wider. :( Also, how do I remove an attachement after attaching it and finding out that it is wrong? That's easy - you're looking for the detach-file command, which I believe is bound to 'd' by default. ~Kyle - -- Reality is that which, when you stop believing in it, doesn't go away. -- Philip K. Dick -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKjvElAAoJECuveozR/AWe4P8QAJERlU3JLQEjRe8l7X5orqhJ VUrFJLekLVBc4q/vsLEGFKXbEcmSdxEZnWEVSKr/zWH49idl37969KV/x0+81Lvb 7UcXxnR5sLxZR62ptmIduZJ6LXHT9oj4NFjVVflOi8KF4ZGHzbUEfrsfp578yIuz RXv4YyZBqlAL/OTv8OAqoEsgy6+OhJp1a39ndj06+GhS/nRvJqRpKHcNPQRQXDq5 OF7bFBxbeDv/6g8JsAWbWjAVZirlvhEj99KRAVPYHmwGHZyYGzGRIgq8eovx60Of zQL6xU1kot4t3bl3Da958ovQaXuawHT7hm5jV9uqMHKBCzOzPEkGJG8lYedH2+Nf fjgIkiE1mb11vXajbCpIkjw0nYMgfajgHPkdRrOADw3Bi0X/A62wTEV1MSTMVtL5 YyLpAc6y9XdNvParq4V63co0qHUljNNb4lR/aGCuQPpZd2oOk3TvKimi4kGWzw9K UmpML5fln25qKI1QSKH14+3yXC3m7CiTuZvHGyuiasrWGqatpjHeolH82t0sNYp6 2pBQ+Evuggc9H+MnkeU5ULTb5AgIdcOzcVh0O4YenZBG9lBCoFKviTewxIljRQvS dSl+yQ4AjeynvsbGRyH1+xfAOGIEQybqZpoQB/GeRA+vPYoq/mF4jICXPy+FWrjZ Y0IATD7SkP7gTkuT/qeX =9lpZ -END PGP SIGNATURE-
Re: long attachment names
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Friday, August 21 at 08:29 PM, quoth Christian Ebert: * Kyle Wheeler on Friday, August 21, 2009 at 14:10:36 -0500 On Friday, August 21 at 12:44 PM, quoth belge...@seznam.cz: Also, how do I remove an attachement after attaching it and finding out that it is wrong? That's easy - you're looking for the detach-file command, which I believe is bound to 'd' by default. Almost, it's bound to 'D' by Default ;-) d is edit-description ... come to think of it I might swap these bindings, because I always hit d first ... Heh - especially given how (imho) pointless edit-description is for most situations. It appears that I swapped them too. ~Kyle - -- Reliability means never having to say you're sorry. -- Dr. Daniel J. Bernstein -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKjwslAAoJECuveozR/AWe5NcP/RRh3j+EHcPwvJtwECfzL3Z3 z8LVHCftJvXQcrasGdFS+rvXNtAPe5zm/r5LDMFNGFkue/e/0WBYEIe0d332ODvs KflhbLBt8xP3q3wicZa6uMIymDY1pLHIuLylgZ8n4V5PHu68EoZ6ZakbzWU9g12Q QGNKImvULYknzAliG5nFb3V3Ml0U+hzB+KzI1mt0YEO4ax50ObkNVo1AVwES2Coy US/csf/opnu/qwT38VFTeRsSf61/a6+rgHUWE9T4ylVhg/Y/W+QclaI+MYeLNfU4 SbDbRZHhs+EfT9TEUSgCsqQYq2x2m39zy/pVfwCk7xkX8qj8j4zuCK/qEvCW26Um XwSpWrp9URvsE2gQWlfYcXfKq8GcCvq/HMOihDIxsvbIAQfPCpQ8Lx+UUy89cG+l oP8CLRu04Kp1x0T2EPpSmX2YV7YQtv904V3j3SEsovUcpkbEkwEmU5NBDUphc2lz 824WcjXFVxtGI14SJn4JaxNF/8NgyJRMSYsOBaeh/v3ovrDYaYUHrXUT9x/ZGBSD dVewCn/gint37MC/ngW9oeIv1wSdWdjGxqmJiRBLfcGuUymCF4NfxTkg7Yh6QM6T AdDFVwCGqI+gr78AzBSy1yFa+UQhx1no0EDZT9mbSjPngQ0wYZSW6wuG2Ovp4wkm Sh8vxjKTaSKkCXHgzbZ2 =s7Ok -END PGP SIGNATURE-
Re: conflicting date format with attribution
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wednesday, August 19 at 01:06 PM, quoth steve:
set date_format=%a %d %b %y
set index_format%4C %c %D %s
which is ok for the index. Now when I reply to a message, I would like
to have the attribution specially set, something like (in French) this:
Le mardi 18 août 2009, John Dow (j...@example.com) a écrit :
So full day name and full month name.
So I tried:
set attribution=Le %d, %n (%a) a écrit :\n
But I then get short names for day and month.
So set it explicitly, like this:
set attribution=Le %{%A %d %B %Y}, %n (%a) a écrit :\n
Note the %{} construction.
~Kyle
- --
Only the fool hopes to repeat an experience; the wise man knows that
every experience is to be viewed as a blessing.
-- Henry Miller
-BEGIN PGP SIGNATURE-
Comment: Thank you for using encryption!
iQIcBAEBCAAGBQJKi/VBAAoJECuveozR/AWeNZ0P/RWkWbfx4g7N7VaI1SwwE9iO
6iDoRjeKKV+McRuFNMUKIqUcrEQTfl4/9jeCYqzQcnvqB2WO22S++6vELOd5pEAx
2VXBmQPudPw8O5RTCRbMQjAJN8IQme8rWAA6fW+kIyHFpScH8oTVoKiT3Lhg8px8
Ib2OL/fIfDkNEW9fBRMYfHxHULb2ynqLn1clBprVlpj76rDmgsyMRnBQquw+kWiE
PgLzVvuG9j1toVk8xSV8BDyp46Kvk7yrX2/QOIdVi4/BpVZ6AsttLhL2ItKzH/8j
NB+vRam/wneCmI9lw1XUX1lHdbatmEN5ze7KHWtvQJJMi3iwLHymx2Ln6FFKhtUx
dZRoiEo+FWgR9PUvMOehEBwdKAgy3AYxfb8KfTTaVZK7ySi0wKCaXtyxTuepsvRw
rzKc06T9jAAFxktv/eYU+J3GFLlLOxEP1b/Voc/bL0OExmw/1oMg7ivt9060ZuJB
/sGY2ovcQRyiEPbsHZYdzpAOftYreojkzZVkZmWM+RuKdd4PncIIlBo0YqCzOcYg
gb2ZVBtYzHkR8KuO8TUrkBdwgsxGwSp6eU9UgRp+z3o0kFngruc4kREZ5dqNzToD
ASe2sKybICf2BWJkH7WGsw2dP7PAsQnc3+Sf+/UAQ9H3aE4RAV53ycGF8+YNDP61
99Q+orp0jgmPnX3ZG7J5
=LiMW
-END PGP SIGNATURE-
Re: Colors in quoted *replies*
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, August 19 at 03:49 PM, quoth steve: I have colors when I read a message, but not when I'm replying to it. How can I get this? Get a better text editor (or learn how to use the one you've got). (I prefer vim, some folks prefer emacs, and there are several other good ones out there.) ~Kyle - -- Nothing makes a woman more beautiful than the belief she is beautiful. -- Sophia Loren -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKjAP0AAoJECuveozR/AWeX6cP+gJxaiMQ24OiFMfFK/PB+k/B +MjxMfbpj5QGG/VbQmp+0HT+eP4k0ebqtXnuchtEUqMR1WmirwGTG8QIq96bcFKN iwlaEtTn6ZhYbRvL50i+X4f5IduqgSGeh5vzeJZhqpSlwDZxAsTGvlHS65Vo0WwN DmEnKewmXK/+tFIylfsWsm9JExvUO2SxAVc5417HxbFfbFSQcQhi7bxH7maTDiOH lCSMXBhhqVZ8oRhUo9P2ZmXfkyIpumSZY5aUfcWhJ5JyWQ5MI7+oPiPbytLN/9eX rWwqRT1mhyhd/MFtIUuSwRz/GCEFEtBA/67HcgXWkmHy5AxAlC1VBJm0TOAZVZft b2/1XSym//jXKwqofYrEJRRCH6DFE/5KcYzazkKPglTPGzQR3657rPtrM3qHkHp2 rhPeUP5c9kDEmxzUHKERP/kJB2nPGwuucJWXKgSYnlzrOnM+pDAiWF7Ux3VaKCFP jPXSX6Rzxzo1lBbh+fNz1AqqBT/j2PZJw6KXMA2Cv6oXZy2QKT2isU4Pho6pJvfU dDiEx85QQyLTl8E4Ymz94mn+Fc/5QwRDZ4jOkbvHZ+Oxt5b7qppdkLdSmprtvaX0 MAaqKOCCTjyNghl6UtQv3agFyCkUOJ0OVTfFOJ6NeCdBZGA3errmj8PkxTCyvg+4 V1fur+neyXpJx31oNl7j =a+Ok -END PGP SIGNATURE-
Re: Colors in quoted *replies*
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wednesday, August 19 at 03:59 PM, quoth steve: (I prefer vim, some folks prefer emacs, and there are several other good ones out there.) vim too. Well then, it's simply a matter of adding the following line to your ~/.vimrc: syntax on ~Kyle - -- Men think epilepsy divine, merely because they do not understand it. But if they called everything divine which they do not understand, why, there would be no end of divine things. -- Hippocrates -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKjAhwAAoJECuveozR/AWeae4P/3c06iVNKp8lNNK3NraraaOK A5OQcMxcyQN476Bb30zvMH1gsL4XgTKztvOSRj6q6VG/ImJfAa21QF14Q71rO4Yz OLSNoV1XxkL+hrH0q21+aBUW1Fu98NBDnW3OjIFMW4RG8sqxkM1H1iwJhl6JLD66 sS7YM+4M5VdZ42K9hGFxm+CsslCzqZXSyH8V8C6kUyV2k3WdSEKh7tPXfuOVOI8T O5OT4OJCvbj8KhEIVXRxLD0uAzsm7iMzi2DNBg6CKi+ZSUQg0OsGwsexE7kRk3Nq 9EOFjBfUrFDH61+I4gFS+SHDSVKi4ooxYlZEu0jYJUgh4sAiDfnDB/BCqH+mowy+ 7xqvC0Qj9wAU0UYaOrEu2At8in5hZsopYvffQxQc3BRR0xRuAc9qY/G+RKOmvSxW zmCSKSKLSAow1xKmeAPj/YmY5f8M0iWIx1vSAl88S+dild08eVMQ2fRslM77pR5m lHidykVJU3paFUdfy5REz90piTb2msPbZQav3h4VhSP6PdGol7Y6aM0duUOJmopy /RrdXDkOItoZ/zUTAWEIkep4l572TsVgv/aKk7oa7E3VookmR6O6m/fwCDCaZDyk thTmtMNXYkNdTE1hZ2QhmiRO5ZHaVkiTQtP1zSuyMkSszNze0U9PvW2JNxKmm0EV pOk/V+eFAa3XE+fYILR1 =HNjT -END PGP SIGNATURE-
Re: group reply exclude self?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tuesday, August 18 at 08:55 AM, quoth James: All, I'm wondering if there's some way to tell mutt to automatically remove self from group replies. I find this to be a pain sometimes when on long email threads. To quote the muttrc man page: metoo Type: boolean Default: no If unset, Mutt will remove your address (see the alternates command) from the list of recipients when replying to a message. So, from the sounds of it, you just need to set up your alternates correctly. ~Kyle - -- Conscience is the most secret core and sanctuary of a man. There he is alone with God, Whose voice echoes in his depths. -- Gaudium et spes -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIbBAEBCAAGBQJKiqo3AAoJECuveozR/AWe8aUP+Npl3UHP53jmBUa67YKSLhkg cZTwwW7ewPsl/Ir7j1APhdA/YliDNU8gb+BQmq41+E4DCJzM7B4is7RQWFIBwABC zLrmdq+faRoaVB7/6wVkhssIa75Z+uwVXlasnZOTJ55KTKOhYyop7lbc438u5Yql TiHmcftfOpAjIY50YTEHoss8Imy7S1WVV+8rj1aPM+TPyta+UnghJrLwARA2X0gh 39/VC4x2HlX2SIdkzhrS4wGRzPFzECcM7XhWCmjRvrOyOR3u3lmAlUaxj+eYIQWr E705knOZx+ifSWGZ/CsSuhjCUDYcLFK3VWr/JQkgOqhmapoejMDUS++KA86X1VHS x7Yh4UHTnXbY113E1ZWqMYbxQ9EGjNho6th4EvLnrWYlOI8Qp0iTuoiM5r1/0ON/ YUm+HYY+0387hwYjz4v/5Z4GHyoTzTk5Qk8BOkSo4xXrgIfYAJ+5Aie2SVLDBPSE mxr1d5NyPcBSfmU5oAOjCT+d/Fwctp055s9U0mVTKRQW/GpTJJ6o8Ia44KxC39z5 unAbiByr23Sx2ezOAnOg5eGxXl9FaNApRu0td9tesrKI5T1VhgCyDT8oKZAwWNcy qZGjvc6C64GpvLo8ol8xbLGVkOuFOMJH8zL0O6dxZaC9m9MV7C4zfKZ3y8o9jQN3 3aiEuUvg4opF7dXu3WQ= =ByPJ -END PGP SIGNATURE-
Re: pressing 'g' truncates
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Sunday, August 16 at 09:18 PM, quoth Ravi Uday: I think its only some msgs, as I don't see it happening now. But it definitely happens. Is there a way to find out which msgs it truncates Observe when it happens, and see if you notice a pattern. ~Kyle - -- We must not confuse dissent with disloyalty. When the loyal opposition dies, I think the soul of America dies with it. -- Edward R. Murrow -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKif3sAAoJECuveozR/AWeQEgP/imTkL3HFW/nkjFzYerEOzEz BHCeyKC8658RV2cF3RvVz8+CvqA1E/xRaGihBBmPGnuvpN8yL9RT7sQWU03RRJSV 8/sKoViw2tEcTWUO2nMikS+HIm0S2jITydvjodWaJKIETTO+QoM8kkQAF8XfpNIB +HKZ5mXvusMUnD7WcgqpM8zFFjnY15EE7X1P8oXOQqVT1mN4XZy9lE3fSuF2czyn a3QOiDU0VoQZC4y9Tus1YySK9MTx5DUU/ZJQbYfjhRkt2LV3HMGgKDaeP6oJgFOg tZuzLmpO2S9f4kirriLLnBBAMXajGK7A2YCCvn7smRdKs+47DCT8yj3BP+5SCQap fNUaOQ+ZomDWRqak6SjP/17iUNNPTJ1cr8homcjRBclbw8XfEd+3nL6bnBdPBgMY 9qFqxOuRe5QyL/O3srR4Flw3F9ygc/DaWOBV8G2WEcI2cvHbdZpaQHX/zRvfkrMt 9mqzXUrAg9EBPWbBvit9aiY+7vDT6tchcvsxfCuYTxBKABXkfggDFBNTYJm+8ApN cbGVCWHPoV5xSuPgObM6zamKHnCgkLRNejC3KXbFbXLbyW6HGOr5gtXTgtDFme5Z oWAMHirfdJtQ7u/PgCLt/dXRWO4e2pdw1mF/VyXmh5u9Mj8Vr/xihyklRVnBfLG7 xW/rc/RcM7ogTzXTyccE =RHPu -END PGP SIGNATURE-
Re: What is the best way to approach Deleted mail removal from
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Monday, August 17 at 12:32 PM, quoth Rocco Rutte: [ btw, any idea why your subject is truncated? ] Huh... I hadn't noticed that. I haven't a clue. Is this one also truncated? If you have no choice but to use POP3, I highly recommend you use mutt to access your POP3 server directly. With the message and header caching, it can be just as fast as a fetchmail-based option, and it handles things like deleted messages much better. That's only half true, please don't recommend the internal fetchmail function for POP because it is partially broken (http://dev.mutt.org/trac/ticket/1751). Due to mutt's architecture, this isn't as easy to fix as it sounds. I wasn't thinking of the mutt fetch_mail thing, I was thinking of setting $folder to pop3://u...@host/. I was under the impression that that worked reasonably well. Am I wrong? The problem, of course, is that POP3 has no means of searching messages other than by doing it the old fashioned way (download each one). Where IMAP gives each message a unique, long-term UID number, POP3 does not (it has UIDs, but they only last as long as the POP3 connection). RFC1939 has this on the UIDL command: I stand corrected! ~Kyle - -- I am certain there is too much certainty in the world. -- Michael Crichton, State of Fear -BEGIN PGP SIGNATURE- Comment: Thank you for using encryption! iQIcBAEBCAAGBQJKif9EAAoJECuveozR/AWe+10QALCrxbyFg0ehx+4N6q4GMUsc /2m0Sqop6ibuGQquPNfgZntaKoIUkQYQCJRIUTAxRVtxjjizHL4JJ9p50MZ7MImF pug7e62poH95XDJxssqfitSleHpj2nL0jZpO23SRj0OjUEDJmWjxW8ZyUFsxUY2s Bi47rx1YiTvejJ0st/s316ymUMZVQnXIc50HwOXckdXuSps4nFGSWPjoPhjXOoX3 TwrspFb40E/tDyjUN3Ow89/rq5k/Ppd+uOdG5Tmz6xsRijYrork6YcRw3ujP+/TX mHJkm8OtTn/ocEaeVrDSKQ7gyPJn9juFgaT2KFAJTgQEHyFEjfEbiRUsXkIckRHB piIXG3IDFqumlFU7bIc1m+RX9GFkIlRA0wxjsN/uEB0Z/bLdlVlDyVatdU1QpgTE Bb1Q1IWmIejirKQPXI+sn8QB8lODSngmDweQjp5KCbV8UOXqeOnfn3mgZ3pMRliL fAcrMizO75R1vIofh4XPYQEd9t+PxrjP8RFZfkfa5xXYWnK34VSrdjcUsi5p0wuE 7vSYuUEYPUFlOLlkRkmt3UfSfTeZzGLjk6wcFk5/evLUynlpW5CcY27kbopGLcAS bd5tgKNX6h9ZFDTgt3dI553JMRK5Zh6hFIWcVuQJq6mvuUmQsJ6Pcyd7nwgA6qGW oNTtQkmFfw7wEYV6Pocz =hP3B -END PGP SIGNATURE-
