Re: Maildir is not Updated
Benjamin Michotte wrote: Oh my god... I just switched from mbox to maildir... and also reswitch to mbox... 2 minutes 38 to open my in.mutt maildir (± 6000 mails) instead of 18 secondes to the same in mbox format Mmh, sounds strange to me. I have one big maildir (it's a mailing listi archive) with 18,413 emails. Mutt needs 60 to 90 secuto read and thread the mails (on a AMD K6 400 MHz with SCSI-UW). -Tim -- Tim Schlotfeldt, Kiel/Frankfurt, FRG Encrypted email preferred.
Re: urlview
On Sun, Dec 02, 2001 at 07:24:45PM +0100, Elimar Riesebieter wrote: Hi all, I am using mutt since 4 weeks: It is fantastic! Now it is very easy to read usenets and other stuff! I have searched the docs ... how can i pull specific usenets into my mutt inbox? aloha, dave msg20957/pgp0.pgp Description: PGP signature
Re: Mail archiving
Moin, * Thomas Hurst [EMAIL PROTECTED] [01-12-03 00:24]: * Thorsten Haude ([EMAIL PROTECTED]) wrote: I have different views on Maildirs (see other thread), and I would move the mails thread-wise, but on all other points, I agree. Hm, thread-wise is conciderably more expensive - date-wise involves just scanning the maildir, grabbing all the time()'s, sorting them and cutting off the top 1 week. I know, but I really don't want to break threads. I also forgot to mention that I would mails a month old. I have no solution, but will work on one based on Mail::Audit. Mail::something, not Audit. Could do with libmutt and Mail::Mutt :) Huh? What's that? couldn't find anything on CPAN. Thorsten -- Question Authority!
Re: Maildir is not Updated
Hi, * Will Yardley [EMAIL PROTECTED] [01-12-03 01:08]: Thorsten Haude wrote: I don't use ext2, but Reiser. The difference is less severe, but noticeable. Maildir seems to have the problem that it only works with certain file system types. i also just noticed your version string... if that's correct, you might want to upgrade to one of the most recent dev mutts - the Maidlir threading code is supposedly better as of 1.3.18i and there have been more improvements since then as well. It's a pity you didn't notice it a few days back when I asked about the problems I had. Now I think some time will pass before I try it again. I have also since learned (should have checked earlier) that there is no Mail::Box::Maildir module. i haven't used mutt extensively with mbox so it's hard to do a good comparison. I have, but not exensively, for good reasons. Thorsten -- Don't let your sense of morals prevent you from doing what is right. - Isaac Asimov
Locking mboxes
I'm having an oddball problem with locking. Mutt 1.3.24i on RedHat 7.2 Linux 2.4.16. The mailboxes in question are mbox format on an NFS server running Slackware 8.0 Linux 2.4.16. When attempting to write to a box (say, save a message), I get: Couldn't lock /home/rnbwpnt/MAIL//spam? I get this error if spam is zero-length (touch spam), or if it contains one or more messages, or if it doesn't exist and I confirm create. I do not get locking problems on Maildir boxes (everything except this is Maildir, and I need mbox for this one application). There are no obvious conflicts in /var/lock/. Manually operating on the file in question (rm, mv, cp) produces no errors. Looking for pointers on where I might be going wrong. Searching for lock in the mutt manual at mutt.org produced only a note about how Maildir doesn't need it, and set dotlock_program (which is in the default location). Thank you. ag
color problems after upgrade
hi, i just installed mutt 1.3.23i on a woody box ... previously, i was using 1.2.5i on a potato box via xterm (i want to run a local mutt with fetchmail) the first thin i notice is that 1.2.5 allows my xterm background to show through (which i like) but the 1.2.23i seems to force the white on black scheme no matter what console / xterm colors i have configured. suggestions? also, any advice on copying my pgp key/user info over from the old box to the new one? tia aloha, dave msg20961/pgp0.pgp Description: PGP signature
Re: Locking mboxes
Aaron -- ...and then Aaron Goldblatt said... % I'm having an oddball problem with locking. Mutt 1.3.24i on RedHat 7.2 % Linux 2.4.16. The mailboxes in question are mbox format on an NFS % server running Slackware 8.0 Linux 2.4.16. ... % There are no obvious conflicts in /var/lock/. Manually operating on the % file in question (rm, mv, cp) produces no errors. IIRC, there are three types of locking: dotlock, flock, and fnctl. You know about dotlocking from your trip through the manual, but IIRC that's not recommended for NFS. You should run mutt -v and look at how your mutt is compiled to lock and ensure that that's supported on your system. You might find that there are NFS permission issues where, say, mutt_dotlock (which should be SGID mail) can't write to your home dir or some such. % ... % Thank you. HTH HAND % % ag :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg20962/pgp0.pgp Description: PGP signature
key transfer (was color problems after upgrade)
Dave -- ...and then Dave Price said... % hi, Hello! % % suggestions? I'm sorry to say that I don't have any suggestions for your color problems. Best of luck. % % also, any advice on copying my pgp key/user info over from the old box % to the new one? This should be as easy as tarring up your .pgp directory and shipping the tar file over for extraction. % % tia HTH HAND % % aloha, % dave % :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg20963/pgp0.pgp Description: PGP signature
Re: Some send-hook executions are cached?
Magnus -- Did you ever get an answer for this? I was going back through my mutt-users folder for anti-spam URLs and tripped on it. ...and then Magnus Bodin said... % % I did some experiments with send-hook, like this: % % send-hook . 'my_hdr Reply-By: `perl -e print scalar(localtime(time+7200))` % % and it did indeed generated a new (outlook-annoying) header for each mail. That's good. % % % But when I took this further to generate a dynamic realname like this: % % send-hook spamlist set realname = \`perl -e '$t=$^T+81867600; $a=int($t/(7*86400)); $b=$t%(7*86400); printf qq#magnus ver. %d.%06d\n#,$a,$b'`\ % % The result of the perl-script seems to get cached somehow, since it does % the generation only once per mutt-session. Even if I have other set % realname=.. (static ones) that gets executed in between. % % Why is this? Can this be circumvented if I want the external command to be % executed every time? My guess is that it's because you're using instead of '' around your hook. If you use single quotes (as in your time example) the inside isn't evaluated until calling time; if you use double quotes it's evaluated at muttrc evaluation time. Neat idea, BTW. Maybe that's why I have it in my mailbox -- but it didn't have a replied flag. % % Silly reason - serious question. Silly reasons are good :-) % % /magnus HTH HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg20964/pgp0.pgp Description: PGP signature
Re: a bunch of newbie questions
On Sat, Dec 01, 2001 at 08:59:24AM +0100, Sven Guckes wrote: * Paul Brannan [EMAIL PROTECTED] [011130 15:42]: 1) When I start mutt, I see this message: fcntl: No locks available (errno = 37) How can I make it go away? use the file locking that goes along with your system?! Could you please point me to the documentation for specifying a different form of file locking? The mutt FAQ and mutt docs at mutt.org do not appear to contain such information. 2) When I go to the index, I see this message: /home/pbrannan/.mh_profile not found, mh format names disabled How can I make it go away? well - are you using mh folders? I'm using IMAP to access my mail. I do not know what format the IMAP server uses to store its messages. 3) When changing between mailboxes, I am constantly asked whether I want to purge deleted messages. I can make this go away with set delete=no, but then when I press $ to expunge the messages, nothing happens. What must I do to get rid of deleted messages when delete is set to no? delete=no means never delete anything. check your logic! you want delete=yes which means yes, delete those message and DONT ASK ME. I don't want delete=yes, because I don't want my deleted messages to be purged, except when I specifcally tell my mail client to purge messages (that is, I do not want to change to a different mail folder, come back the original folder, and discover that my deleted messages are gone). Is it at all possible to purge messages when delete=no? I tried binding the keys such that pressing $ will temporarily set delete=yes, but this seems to be rather tricky. Thanks for your help! Paul
Re: a couple more questions - sync-mailbox
On Sat, Dec 01, 2001 at 09:08:02AM +0100, Sven Guckes wrote: * Paul Brannan [EMAIL PROTECTED] [011130 15:45]: 1) How can I refresh the current inbox? Use the command sync-mailbox - bound to '$' by default. And please use '?' to show the help screen and '/' to search within. Then go RTFM. Pressing '$' does not appear to have any effect. As a test, I: a) send a message to myself b) return to my INBOX (which resides on an IMAP server) c) wait a while, then press '$' -- nothing happens d) quit mutt e) start mutt and return to my INBOX -- the message is there As a test, I try the same thing in Pine: a) send a message to myself b) return to my INBOX c) press Ctrl-L -- the message is there Is there a configuration option I am missing in Mutt? Thanks again, Paul
Re: a couple more questions - sync-mailbox
On Mon, Dec 03, 2001 at 10:19:33AM -0500, Paul Brannan wrote: On Sat, Dec 01, 2001 at 09:08:02AM +0100, Sven Guckes wrote: * Paul Brannan [EMAIL PROTECTED] [011130 15:45]: 1) How can I refresh the current inbox? Use the command sync-mailbox - bound to '$' by default. And please use '?' to show the help screen and '/' to search within. Then go RTFM. Pressing '$' does not appear to have any effect. As a test, I: a) send a message to myself b) return to my INBOX (which resides on an IMAP server) c) wait a while, then press '$' -- nothing happens d) quit mutt e) start mutt and return to my INBOX -- the message is there syncing doesn't delete anything on it's own... you have to delete the message if you expect the sync to remove it from the mailbox. or am I misunderstanding you? -- Dan Boger Linux MVP brainbench.com msg20967/pgp0.pgp Description: PGP signature
Re: Mail archiving
* David T-G ([EMAIL PROTECTED]) wrote: ...and then Nicolas Rachinsky said... On Sun, Dec 02, 2001 at 11:24:53PM +, Thomas Hurst [EMAIL PROTECTED] wrote: * Thorsten Haude ([EMAIL PROTECTED]) wrote: I have no solution, but will work on one based on Mail::Audit. Could do with libmutt and Mail::Mutt :) What are these two, and where can I get more info about them? The colon colon signifies a perl module, or at least AFAIK. Not strictly a Perl module, since plenty of other languages use ::, but yes, I was implying a perl module :) Unfortunately neither libmutt nor Mail::Mutt (which would provide an interface to mutt through scripting) exist :) -- Thomas 'Freaky' Hurst - [EMAIL PROTECTED] - http://www.aagh.net/
Re: a couple more questions - sync-mailbox
On Mon, Dec 03, 2001 at 10:24:04AM -0500, Dan Boger wrote: On Mon, Dec 03, 2001 at 10:19:33AM -0500, Paul Brannan wrote: Pressing '$' does not appear to have any effect. As a test, I: a) send a message to myself b) return to my INBOX (which resides on an IMAP server) c) wait a while, then press '$' -- nothing happens d) quit mutt e) start mutt and return to my INBOX -- the message is there syncing doesn't delete anything on it's own... you have to delete the message if you expect the sync to remove it from the mailbox. or am I misunderstanding you? No, I'm not trying to delete the message. What I want to do is send a message to myself and refresh the mailbox, so that I can see the message in my mailbox before the next scheduled mail check. (In other words, I want to be able to check my mail at an arbitrary time, rather than at every mail_check interval). Paul
Re: a bunch of newbie questions
* Paul Brannan [EMAIL PROTECTED] [03-12-2001 16:16]: | use the file locking that goes along with your system?! | | Could you please point me to the documentation for specifying a | different form of file locking? The mutt FAQ and mutt docs at mutt.org | do not appear to contain such information. You should check out ./configure --help; it shows all compile time options for specifying which locking mechanism to use! | Is it at all possible to purge messages when delete=no? I tried | binding the keys such that pressing $ will temporarily set delete=yes, | but this seems to be rather tricky. Doesn't something like: macro index $ enter-commandset delete=yesentersync-mailboxenter-commandset delete=noenter work? Sorry for the long line and not testing this ;) -- René Clerc - ([EMAIL PROTECTED]) Q: What is the burning question on the mind of every dyslexic existentialist? A: Is there a dog? msg20970/pgp0.pgp Description: PGP signature
Re: a bunch of newbie questions
On Monday, 03 December 2001 at 10:14, Paul Brannan wrote: On Sat, Dec 01, 2001 at 08:59:24AM +0100, Sven Guckes wrote: * Paul Brannan [EMAIL PROTECTED] [011130 15:42]: 1) When I start mutt, I see this message: fcntl: No locks available (errno = 37) How can I make it go away? use the file locking that goes along with your system?! Could you please point me to the documentation for specifying a different form of file locking? The mutt FAQ and mutt docs at mutt.org do not appear to contain such information. 2) When I go to the index, I see this message: /home/pbrannan/.mh_profile not found, mh format names disabled How can I make it go away? well - are you using mh folders? I'm using IMAP to access my mail. I do not know what format the IMAP server uses to store its messages. you are talking to a chatty UW-IMAP server. That very server was the inspiration for the $imap_servernoise variable, which you may wish to unset. That will probably solve both 1 and 2. I don't want delete=yes, because I don't want my deleted messages to be purged, except when I specifcally tell my mail client to purge messages (that is, I do not want to change to a different mail folder, come back the original folder, and discover that my deleted messages are gone). Is it at all possible to purge messages when delete=no? I tried binding the keys such that pressing $ will temporarily set delete=yes, but this seems to be rather tricky. This is your best bet. what about something like: macro index $ ':set delete=yesentersync-mailbox:set delete=noenter' -b
Re: Mail archiving
* Thorsten Haude ([EMAIL PROTECTED]) wrote: * Thomas Hurst [EMAIL PROTECTED] [01-12-03 00:24]: Hm, thread-wise is conciderably more expensive - date-wise involves just scanning the maildir, grabbing all the time()'s, sorting them and cutting off the top 1 week. I know, but I really don't want to break threads. I also forgot to mention that I would mails a month old. Breaking old threads isn't really a problem for me. Not as if they're going to be looked at much. Could do with libmutt and Mail::Mutt :) Huh? What's that? couldn't find anything on CPAN. A fictional interface to a shared library version of Mutt providing mailbox functionality, threading etc. Although personally I'd want a Ruby module :) -- Thomas 'Freaky' Hurst - [EMAIL PROTECTED] - http://www.aagh.net/
Re: Mail archiving
Hi, * Thomas Hurst [EMAIL PROTECTED] [01-12-03 16:28]: Unfortunately neither libmutt nor Mail::Mutt (which would provide an interface to mutt through scripting) exist :) I found libmutt with Google. Thorsten -- They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety. - Benjamin Franklin
Re: a bunch of newbie questions
On Mon, Dec 03, 2001 at 10:31:53AM -0500, Brendan Cully wrote: * Paul Brannan [EMAIL PROTECTED] [011130 15:42]: 1) When I start mutt, I see this message: fcntl: No locks available (errno = 37) How can I make it go away? 2) When I go to the index, I see this message: /home/pbrannan/.mh_profile not found, mh format names disabled you are talking to a chatty UW-IMAP server. That very server was the inspiration for the $imap_servernoise variable, which you may wish to unset. That will probably solve both 1 and 2. This solves #2, but not #1 :( This is your best bet. what about something like: macro index $ ':set delete=yesentersync-mailbox:set delete=noenter' That works really well. However, this does not: macro index $ ':set delete=ask-yesentersync-mailbox:set delete=noenter' All I get is a beep, and delete remains set to ask-yes. Paul
Re: a couple more questions - sync-mailbox
Paul Brannan [EMAIL PROTECTED] writes: On Sat, Dec 01, 2001 at 09:08:02AM +0100, Sven Guckes wrote: * Paul Brannan [EMAIL PROTECTED] [011130 15:45]: 1) How can I refresh the current inbox? Use the command sync-mailbox - bound to '$' by default. And please use '?' to show the help screen and '/' to search within. Then go RTFM. Pressing '$' does not appear to have any effect. As a test, I: I also have the same problem. '$' does nothing and I cannot find the sync-mailbox command. This problem only occurs in X-windows, via a terminal or menu. Outside of X it works fine. -- Harold Sargeant
a hook entered upon sending a message?
Hi there, is there a means to let mutt perform an action on the message it sends out _when_ it sends it? All the documented hooks take place long before this happens... To be more specific, I'm looking for a way to delay the inserting of the signature until the moment the message goes off. I know my own signature, I don't need to see it every time I write an email. :) TIA -- Roamn FreeBSD 4.4-STABLE 5:39PM up 41 days, 4:22, 16 users, load averages: 0.06, 0.03, 0.04
Re: patches (colored questions, conditional tag-prefix)
On Sat, Nov 17, 2001 at 01:06:14PM +0100, Nicolas Rachinsky wrote: On Fri, Nov 16, 2001 at 05:07:59PM +0100, Nicolas Rachinsky [EMAIL PROTECTED] wrote: The second one adds a new command tag-prefix-cond. It should behave exactly the same as tag-prefix, with one difference. If there are no tagged messages, it will empty the ungetch-buffer, this seems to reliably stop/abort every macro. It's a hack, but it seems to work. I should add, this works also for push commands (and it seems to work for exec). I use the following in my .muttrc: folder-hook regex for all mailing list folders push \tag-pattern~d2w\nuntag-pattern~F|~D\ntag-prefix-condsave-message\n\n\ I've missed it the first time I read this mail but where comes from 'tag-prefix-cond' ? It looks like this command doesn't exist in my version and neither in cvs. Without it (using tag-prefix) when no mail are tagged (no old mail), the current one is saved. # mutt -v Mutt 1.3.24i (2001-11-29) ... patch-1.3.23.2.rr.compressed.1 patch-1.3.15.sw.pgp-outlook.1 patch-1.3.23.Md.gnutls.1 Md.use-editor Md.paths-mutt.man Md.use-etc-mailname Md.Muttrc Md.muttbug-warning patch-1.2.xtitles.1 patch-1.3.23.1.ametzler.pgp_good_sign Christophe It moves all messages older than 2 weeks except flagged ones to an archive folder (I have other folder-hooks to set appropriate save-hooks). Nicolas -- Christophe Barbé [EMAIL PROTECTED] GnuPG FingerPrint: E0F6 FADF 2A5C F072 6AF8 F67A 8F45 2F1E D72C B41E msg20978/pgp0.pgp Description: PGP signature
Re: patches (colored questions, conditional tag-prefix)
On Mon, Dec 03, 2001 at 05:52:41PM +0100, christophe barbé [EMAIL PROTECTED] wrote: I've missed it the first time I read this mail but where comes from 'tag-prefix-cond' ? It comes from a patch I've written, you find it under www.rachinsky.de. Nicolas
function mail unavailable in the browser menu
Hi there, what is the rationale behind making the mail function unavailable in the browser menu? The need to enter a mailbox just to send a mail has bothered me for some time, and when I finally went to bind it, I realized I was out of luck... :| -- FreeBSD 4.4-STABLE 7:47PM up 41 days, 6:30, 17 users, load averages: 0.15, 0.12, 0.05
Re: Locking mboxes
mutt -v Okay. bash-2.05$ mutt -v Mutt 1.3.24i (2001-11-29) Copyright (C) 1996-2001 Michael R. Elkins and others. Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'. Mutt is free software, and you are welcome to redistribute it under certain conditions; type `mutt -vv' for details. System: Linux 2.4.16 (i686) [using ncurses 5.2] Compile options: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL -USE_FLOCK -USE_POP -USE_IMAP -USE_GSS -USE_SSL -USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGIN FO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID -HAVE_GETADDRINFO ISPELL=/usr/bin/ispell SENDMAIL=/usr/sbin/sendmail MAILPATH=/var/mail PKGDATADIR=/usr/local/share/mutt SYSCONFDIR=/usr/local/etc EXECSHELL=/bin/sh -MIXMASTER To contact the developers, please mail to [EMAIL PROTECTED]. To report a bug, please use the flea(1) utility. So I recompiled: ./configure --with-flock --enable-nfs-fix Now it looks like this: -DOMAIN +DEBUG -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE +USE_FCNTL +USE_FLOCK -USE_POP -USE_IMAP -USE_GSS -USE_SSL -USE_SASL +HAVE_REGCOMP -USE_GNU_REGEX +HAVE_COLOR +HAVE_START_COLOR +HAVE_TYPEAHEAD +HAVE_BKGDSET +HAVE_CURS_SET +HAVE_META +HAVE_RESIZETERM +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS -SUN_ATTACHMENT +ENABLE_NLS -LOCALES_HACK +HAVE_WC_FUNCS +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_ICONV -ICONV_NONTRANS +HAVE_GETSID -HAVE_GETADDRINFO issues where, say, mutt_dotlock (which should be SGID mail) can't write to your home dir or some such. Strikes me as odd, but I'll look: bash-2.05$ ls -la /usr/local/bin/mutt_dotlock -rwxr-sr-x1 root mail43680 Dec 3 13:23 \ /usr/local/bin/mutt_dotlock I don't have trouble with the Maildir mailboxes, but razor (http://razor.sourceforge.net/) doesn't work with Maildir. Note that writing a message to /tmp (a non-NFS filesystem) is successful, so I guess the problem IS NFS, but beyond what I've done I don't know what to do about it. Recompiling as above did not resolve the issue. ag
Re: Locking mboxes
Aaron -- ...and then Aaron Goldblatt said... %mutt -v % % Okay. % % bash-2.05$ mutt -v % Mutt 1.3.24i (2001-11-29) ... % -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE % +USE_FCNTL -USE_FLOCK ... So that tells us how you can lock. Good. % % % So I recompiled: ./configure --with-flock --enable-nfs-fix % % Now it looks like this: % ... % -HOMESPOOL +USE_SETGID +USE_DOTLOCK +DL_STANDALONE % +USE_FCNTL +USE_FLOCK ... That looks better; I don't know if your system will support flocking, but now your mutt does. ... % issues where, say, mutt_dotlock (which should be SGID mail) can't write % to your home dir or some such. % % Strikes me as odd, but I'll look: % % bash-2.05$ ls -la /usr/local/bin/mutt_dotlock % -rwxr-sr-x1 root mail43680 Dec 3 13:23 \ %/usr/local/bin/mutt_dotlock % % I don't have trouble with the Maildir mailboxes, but razor % (http://razor.sourceforge.net/) doesn't work with Maildir. Well, Maildir boxes don't require locking, so your success is expected :-) % % Note that writing a message to /tmp (a non-NFS filesystem) is % successful, so I guess the problem IS NFS, but beyond what I've done I % don't know what to do about it. Recompiling as above did not resolve % the issue. No, that won't do it. You can test your permissions by trying to manually dotlock something like cd $HOME touch testfile mutt_dotlock testfile to see what you get. You might play with the -t and -f parameters to see what you get. At this point, you should check with your sysadmin to look at how you might have your home dir exported to allow your box to run a program with SGID perms set. Alternatively, you might pull the mail in as usual but then save it to a Maildir after razor has finished with the box. Ugly, but a workaround :-) % % ag HTH HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg20983/pgp0.pgp Description: PGP signature
Re: a bunch of newbie questions
Paul -- ...and then Paul Brannan said... % On Mon, Dec 03, 2001 at 10:31:53AM -0500, Brendan Cully wrote: %* Paul Brannan [EMAIL PROTECTED] [011130 15:42]: % 1) When I start mutt, I see this message: % fcntl: No locks available (errno = 37) %How can I make it go away? ... % inspiration for the $imap_servernoise variable, which you may wish to unset. % That will probably solve both 1 and 2. % % This solves #2, but not #1 :( Interesting. What does mutt -v show you? Do you have dotlocking available? It looks to me as though mutt can only use fcntl locks but they are not supported on your system; mutt is usually pretty good at figuring out how it should lock. % % This is your best bet. what about something like: % macro index $ ':set delete=yesentersync-mailbox:set delete=noenter' % % That works really well. However, this does not: % % macro index $ ':set delete=ask-yesentersync-mailbox:set delete=noenter' % % All I get is a beep, and delete remains set to ask-yes. That makes sense. Your macro sets it to ask-yes and then tries to sync the mailbox, which will generate a y/n prompt. Instead of passing mutt an expected value, however, you try to next give it a colon, which will of course cause an error. If you want the messages to be deleted when you sync, set it to yes in your macro; if not, leave it at no and forget about the macro. If you want to be asked then just set it to ask-no and forget about the macro, and when you usually don't want to delete (like when you change folders, IIRC) just hit return twice (once when you find and choose your mailbox and once to take the default no). % % Paul :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg20984/pgp0.pgp Description: PGP signature
Re: a hook entered upon sending a message?
Roman -- ...and then Roman Neuhauser said... % Hi there, % % is there a means to let mutt perform an action on the message it sends % out _when_ it sends it? All the documented hooks take place long before Not AFAIK. % this happens... To be more specific, I'm looking for a way to delay the % inserting of the signature until the moment the message goes off. % I know my own signature, I don't need to see it every time I write an % email. :) If it really bothers you that much, unset $signature and $sig_dashes and then modify your editor command to append your signature file onto the temp file after the real editor completes. Note that re-editing a file will cause duplicate signatures, so you might also tell your editor to find the sig_dashes and delete from there down before jumping back to the beginning of the message. The code is left as an exercise for the reader ;-) % % TIA HTH HAND % % -- % Roamn % % FreeBSD 4.4-STABLE % 5:39PM up 41 days, 4:22, 16 users, load averages: 0.06, 0.03, 0.04 :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg20985/pgp0.pgp Description: PGP signature
Limiting folder list
I've got quite a few folders, but a number of them haven't had any new mail for the last few days - is there a function similar to limit to limit the folder view to, for instance, folders with a last modified date 24 hours? -- Thomas 'Freaky' Hurst - [EMAIL PROTECTED] - http://www.aagh.net/
Re: a hook entered upon sending a message?
On Mon, Dec 03, 2001 at 03:04:22PM -0500, David T-G wrote: Roman -- ...and then Roman Neuhauser said... % Hi there, % % is there a means to let mutt perform an action on the message it sends % out _when_ it sends it? All the documented hooks take place long before Not AFAIK. % this happens... To be more specific, I'm looking for a way to delay the % inserting of the signature until the moment the message goes off. % I know my own signature, I don't need to see it every time I write an % email. :) If it really bothers you that much, unset $signature and $sig_dashes and then modify your editor command to append your signature file onto the temp file after the real editor completes. Note that re-editing a file will cause duplicate signatures, so you might also tell your editor to find the sig_dashes and delete from there down before jumping back to the beginning of the message. Would this work? send-hook . set signature='.signature' message-hook . set signature='' Although you might have a problem if replying to the same message twice in a row without changing messages. The code is left as an exercise for the reader ;-) % % TIA HTH HAND % % -- % Roamn % % FreeBSD 4.4-STABLE % 5:39PM up 41 days, 4:22, 16 users, load averages: 0.06, 0.03, 0.04 :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! Curt -- Any time things appear to be going better, you have overlooked something.
Re: a bunch of newbie questions
* Paul Brannan [EMAIL PROTECTED] [03-12-2001 21:36]: | If you want the messages to be deleted when you sync, set it to yes in | your macro; if not, leave it at no and forget about the macro. If you | want to be asked then just set it to ask-no and forget about the macro, | and when you usually don't want to delete (like when you change folders, | IIRC) just hit return twice (once when you find and choose your mailbox | and once to take the default no). | | That seems like such a hack, and is awfully inconvenient. How do most | other mutt users handle deleting and purging messages? Does anyone else | actually use delete=no? No I don't: I have it set to ask-yes, because I don't mind hittin another enter when it comes to deletion of mails. You mentioned you just started to use mutt: I'm using it for a few years now (haven't put a mark on the calendar ;), and can assure you: there will be a time you wish you would've been prompted for the deletion! But, of course, these are just my 2c. -- René Clerc - ([EMAIL PROTECTED]) If it's natural to kill why do men have to go into training to learn how? -Joan Baez msg20991/pgp0.pgp Description: PGP signature
Re: a hook entered upon sending a message?
* Roman Neuhauser [EMAIL PROTECTED] [03-12-2001 21:22]: | From: David T-G [EMAIL PROTECTED] [...] | If it really bothers you that much, unset $signature and $sig_dashes and | then modify your editor command to append your signature file onto the | temp file after the real editor completes. Note that re-editing a file | will cause duplicate signatures, so you might also tell your editor to | find the sig_dashes and delete from there down before jumping back to | the beginning of the message. | | Yeah, I figured out it'd be probably left for vim to do this. Then | again, (I'm no vim-hacker) there are at least three ways to quit | from vim, saving the buffer, which means I'd have to noremap all of | them... Unless I'm missing a way to avoid this. Ok, time to mail | [EMAIL PROTECTED] :) What about rebinding 'y' to filter the message through some script? That's probably easier. | The code is left as an exercise for the reader ;-) You lazy ... ;) | No problem. Thanks for the reply. HTH, -- René Clerc - ([EMAIL PROTECTED]) We are not retreating - we are advancing in another direction. -General Douglas MacArthur msg20992/pgp0.pgp Description: PGP signature
Re: Locking mboxes
File Locking + NFS = very bad news It is inherently unreliable. -- Regards Cliff
Re: a bunch of newbie questions
Hi, * Paul Brannan [EMAIL PROTECTED] [01-12-03 21:34]: If you want the messages to be deleted when you sync, set it to yes in your macro; if not, leave it at no and forget about the macro. If you want to be asked then just set it to ask-no and forget about the macro, and when you usually don't want to delete (like when you change folders, IIRC) just hit return twice (once when you find and choose your mailbox and once to take the default no). That seems like such a hack, and is awfully inconvenient. How do most other mutt users handle deleting and purging messages? Does anyone else actually use delete=no? I can't really see your problem, since most of the time I want to delete mails I mark as 'to delete'. Anyway, I use a trashbox: - - - Schnipp - - - # Trashcan folder-hook . 'macro index d save-message=admin/trash\n Move mail to trashcan' folder-hook . 'macro pager d save-message=admin/trash\n Move mail to trashcan' folder-hook . 'macro index \cd tag-threadsave-message=admin/trash\n Move thread to trashcan' folder-hook trash 'bind index d delete-message' folder-hook trash 'bind index \cd delete-thread' - - - Schnapp - - - Thorsten -- Denn ein Tyrann ist nicht, wenn die Masse nicht geduldig stillhält. - Kurt Tucholsky
Re: Locking mboxes
Cliff -- ...and then Cliff Sarginson said... % File Locking + NFS = very bad news Agreed. If he has to use an mbox, though, he may not have many choices (my drop-in-mbox+run-razor+move-to-maildir kludge being one of them). % % It is inherently unreliable. Always? % % -- % Regards % Cliff % :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg20995/pgp0.pgp Description: PGP signature
Re: a bunch of newbie questions
Paul -- ...and then Paul Brannan said... % On Mon, Dec 03, 2001 at 02:59:31PM -0500, David T-G wrote: % ...and then Paul Brannan said... % %mutt -v % % show you? Do you have dotlocking available? It looks to me as though ... % % The relevant portion of mutt -v indicates: % -HOMESPOOL +USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK Well, that makes dotlocking look good... % % I tried using mutt_dotlock on a test file in my home directory (as Right. % suggested in the other thread), and it successfully created % testfile.lock; mutt_dotlock -u testfile successfully removed the file as % well. And this was from your NFS client box? Interesting. I wonder why mutt doesn't pick it up, since ... % % I've never used fcntl before, but a simple test application yields: % fcntl: No locks available ... it looks like the problem is fcntl locking failing. % % The program looks like this: ... % This same program works in /tmp (which is non-nfs; the first run the % program produces no output, and the second run the call to open() % fails). Sounds right. % % Perhaps this is a problem of the client being able to lock over nfs but % the server not? I don't know *that* much about locking, so I don't know what works where and what doesn't. It sounds like the case, though. % % If you want the messages to be deleted when you sync, set it to yes in % your macro; if not, leave it at no and forget about the macro. If you % want to be asked then just set it to ask-no and forget about the macro, % and when you usually don't want to delete (like when you change folders, % IIRC) just hit return twice (once when you find and choose your mailbox % and once to take the default no). % % That seems like such a hack, and is awfully inconvenient. How do most That's funny... Your going back and forth with $delete sounds like a real hack to me :-) % other mutt users handle deleting and purging messages? Does anyone else % actually use delete=no? I can't answer for anyone else, but I have delete=yes but have rebound q to sync because I got tired of accidentally quitting (and marking old and all of that) when I just meant to sync. I rarely change folders but instead have umpteen copies of mutt running in screen windows -- many of which are started directly by screen's rc file, which means that when I exit mutt the window dies, too, and I have to restart and retitle it and so on. Rene, since starting to use mutt I've never wished delete was set to ask-yes, but I sure hated mark_old (though I want stuff marked old at times) :-) % % Paul :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg20996/pgp0.pgp Description: PGP signature
Re: a hook entered upon sending a message?
Roman -- ...and then Roman Neuhauser said... % % ...and then Roman Neuhauser said... % % % % is there a means to let mutt perform an action on the message it sends % % out _when_ it sends it? All the documented hooks take place long before % % Not AFAIK. % % Any plans to implement this feature? Not AFAIK. [I couldn't resist ;-] % % % inserting of the signature until the moment the message goes off. ... % temp file after the real editor completes. Note that re-editing a file % will cause duplicate signatures, so you might also tell your editor to % find the sig_dashes and delete from there down before jumping back to % the beginning of the message. % % Yeah, I figured out it'd be probably left for vim to do this. Then Sounds good to me. % again, (I'm no vim-hacker) there are at least three ways to quit % from vim, saving the buffer, which means I'd have to noremap all of Why? % them... Unless I'm missing a way to avoid this. Ok, time to mail % [EMAIL PROTECTED] :) I think you are. Set $editor in mutt to call vim and then append your signature, and in the vim call instead of just vim +/^$ do some magic which jumps to ^-- $, does a delete from there to the end, and then jumps back to the first /$^ in the file. % % The code is left as an exercise for the reader ;-) % % No problem. Thanks for the reply. Sure thing! % % -- % FreeBSD 4.4-STABLE % 9:16PM up 41 days, 7:59, 16 users, load averages: 0.13, 0.31, 0.26 HTH HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg20997/pgp0.pgp Description: PGP signature
Re: Locking mboxes
On Mon, Dec 03, 2001 at 07:17:14PM -0500, David T-G wrote: Cliff -- ...and then Cliff Sarginson said... % File Locking + NFS = very bad news Agreed. If he has to use an mbox, though, he may not have many choices (my drop-in-mbox+run-razor+move-to-maildir kludge being one of them). % % It is inherently unreliable. Always? I would not design a production quality mail setup that relied on it if that is what you are asking. But NFS is way past it's sell by date in my view. Some technologies get stretched beyond their design limitations. Time synchronisation (or lack thereof) is also a royal pain in the butt with any application relying on very accurate time keeping. There are alternatives. But that is OT, and not very helpful for this problem :( -- Regards Cliff
Re: a hook entered upon sending a message?
On Mon, Dec 03, 2001 at 07:28:15PM -0500, David T-G wrote: Roman -- ...and then Roman Neuhauser said... % % ...and then Roman Neuhauser said... % % % % is there a means to let mutt perform an action on the message it sends % % out _when_ it sends it? All the documented hooks take place long before % % Not AFAIK. % % Any plans to implement this feature? Not AFAIK. [I couldn't resist ;-] % % % inserting of the signature until the moment the message goes off. ... % temp file after the real editor completes. Note that re-editing a file % will cause duplicate signatures, so you might also tell your editor to % find the sig_dashes and delete from there down before jumping back to % the beginning of the message. % % Yeah, I figured out it'd be probably left for vim to do this. Then Sounds good to me. % again, (I'm no vim-hacker) there are at least three ways to quit % from vim, saving the buffer, which means I'd have to noremap all of Why? % them... Unless I'm missing a way to avoid this. Ok, time to mail % [EMAIL PROTECTED] :) I think you are. Set $editor in mutt to call vim and then append your signature, and in the vim call instead of just vim +/^$ do some magic which jumps to ^-- $, does a delete from there to the end, and then jumps back to the first /$^ in the file. % % The code is left as an exercise for the reader ;-) % % No problem. Thanks for the reply. Sure thing! Mmm, this whole signature thing is really unsolveable. For example, I am a strong believer in bottom-posting to threads, or replying in context. An automatic signature at the bottom is then fine. However these evil people who top-post mean that unless you want to complete addle the thread logic you also have to top post, in which case a sig at the end is a little weird. Since my sig is so simple and cookie-free I can always just type it in somewhere I suppose .. :) -- Regards Cliff
Re: a hook entered upon sending a message?
* Cliff Sarginson ([EMAIL PROTECTED]) wrote: However these evil people who top-post mean that unless you want to complete addle the thread logic you also have to top post, in which case a sig at the end is a little weird. If someone top posts I just nuke all their quotes and reply as normal to their comments. If people want to see the previous message in it's entirity they can look back up the thread. nmap F4 :,/^-- $/-2dCR Is handy for nuking things like that. -- Thomas 'Freaky' Hurst - [EMAIL PROTECTED] - http://www.aagh.net/
Re: Locking mboxes
Cliff -- ...and then Cliff Sarginson said... % On Mon, Dec 03, 2001 at 07:17:14PM -0500, David T-G wrote: % % ...and then Cliff Sarginson said... % % File Locking + NFS = very bad news ... % % It is inherently unreliable. % % Always? % % I would not design a production quality mail setup that relied on it % if that is what you are asking. Well, that's one way to answer it :-) I don't know enough to know whether there are right and wrong ways to implement NFS so that locking works or if it's just plain always bad. % But NFS is way past it's sell by date in my view. *grin* % Some technologies get stretched beyond their design limitations. Admitted. I haven't seen anything else targed at *NIX, though; am I just blind^Wsheltered or has the industry taken the it ain't broke enough to fix stance? % % Time synchronisation (or lack thereof) is also a royal pain in the % butt with any application relying on very accurate time keeping. Oh, yeah. Miserable, I know. % % There are alternatives. That's what I was wondering... % % But that is OT, and not very helpful for this problem :( But interesting, though :-) And perhaps he could take the entire thread, once it fills out nicely with all sorts of other input, ideas, and experiential data, and hand it to the sysadmin and initiate a site-wide transformation -- all because he uses The Mailer That Knows Better ;-) % % -- % Regards % Cliff % :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.justpickone.org/davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! msg21002/pgp0.pgp Description: PGP signature
Re: color problems after upgrade
William, On Mon, Dec 03, 2001 at 01:26:23PM -0800, Will Yardley wrote: what does your colors section look like? mine works fine, and i use the most recent release on both potato and woody with no problems. are you using 'default' for the background color? what TERM do you have set? mine starts out like this most of my muttrc is up at the site below if you go back a couple directories. ## set colors ## some colors are specific to my weird eterm settings - might need to * be changed #color object foreground background patterns /expressions ## ## first regular stuff color indicator default brightblue color status white green color treered default ## then header patterns color header brightblack default ^Subject: Thanks for the advice. i had only: color quoted white default (i had difficuly reading the green defaul guoted on a pale blue background that i use in my aterm) I tried you colors, and those object where default is specified as the background, the aterm background shows thru - everything else - the message body, and the main index background is still white on black. aloha, dave msg21005/pgp0.pgp Description: PGP signature
line editor command history behavior
I've just noticed that if you are cycling through the command history and abort with a ^G, the next time you invoke the line editor you are placed at the point in history list at which you aborted. example: :command 1 :command 2 :command 3 :command 4 :command 5 cycle up the history to 'command 3', abort and invoke the line editor again. Hit the Up key and you are at 'command 2' which is not the last command you entered. This seems a little strange to me and I was wondering if it was intentional. Regards, Doug
Re: patch-1.3.23.cd.edit_threads-6[.CYA] not working
* Prahlad Vaidyanathan [EMAIL PROTECTED] [11/30/01 17:39]: Or wait a little... I will rewrite the patch so that it can work along with the new threading code. Done. I'll take the latter option. Thanks ! You'll find the patch updated for the new threading implementation at http://cedricduval.free.fr/mutt/ Regards, -- Cedric
mail-followup-to standard....
the only quasi-official reference i've been able to find on the Mail-Followup-To header is: http://www.ietf.org/proceedings/98dec/I-D/draft-ietf-drums-mail-followup-to-00.txt while i think that this becoming standard would be a Good Thing, since the draft is from 1997, it would seem unlikely that it will be adopted as a standard, at least unless there's some sort of initiative. i wrote the pine developers this week, asking that they make pine at least honor this header, and was asked by mark crispin if there was a document describing this / listing it as a standard. the link above was the only document i could really send back, which - admittedly - lacks any sort of 'official' clout (having expired in may 1998). while i don't use pine, it is annoying when pine users don't honor my mail-followup-to headers. while it's easy to sit and say that mutt does things 'right', and all other MUAs do things wrong, it seems that perhaps doing things to try and get this type of thing standardized would increase the liklihood of other MUAs becoming less brain damaged. while mutt users (myself included) may see mutt's way of doing things as 'correct', without an rfc on the subject (and adoption by more MUAs), it's hard to tell other poeple that they're doing things wrong. while we all (presumably) love mutt, it's hard to say that it's the MUA for everyone so a push towards getting this type of thing adopted as standard would be very helpful. does anyone else have information on what it would take to set the proverbial wheel turning on getting this adopted as some sort of official standard? -- William Yardley System Administrator, Newdream Network [EMAIL PROTECTED] http://infinitejazz.net/will/pgp/gpg.asc
Re: Maildir is not Updated
Hi, * Benjamin Michotte [EMAIL PROTECTED] [01-12-03 00:38]: Could I change my: find $HOME/mail -type f -print | grep -Ev '(outbox|trash|spam)' | sort | xargs That part worked alright: mailboxes `find ~/Mail -type d -print | grep -Ev '(backup|sent|postponed|trash|/cur$|/tmp$|/new$|/Mail$|/ML$|/admin$|/Shopping$)' | xargs` Thorsten -- The only thing necessary for the triumph of evil is for the good men to do nothing. - Edmund Burke
