Re: Mutt/Netscape eludes me
On 2001.03.15, in [EMAIL PROTECTED],
"Zach Thompson" [EMAIL PROTECTED] wrote:
It tells netsacpe to launch the url in a pre-existing window - the id that we
just found in netscape.sh.
Alternatively:
netscape -remote 'openURL(http://www.foo.net/, mutt-ns)'
will open http://www.foo.net/ in a netscape window with the name
"mutt-ns". (Each NS windows may have an internally-associated name.)
If mutt-ns does not exist, it will be launched as a new window.
If the comma and window name are not present, the default NS window
will be used. You just have to have NS running already. (This is a
behavioral change from the original implementation of the -remote
interface -- NS 3.0, maybe 2.0? -- where a -remote command would start
Netscape if it was not running already.)
So, you could test for Netscape's being mapped with
xlswins | grep Netscape
then start netscape if that fails, and wait for it to map before simply
using the -remote command. Something like:
#!/bin/sh
## uncomment to use a separate window for urlview/mutt
#WINDOW=", mutt-ns"
not () {
if "$@"; then
false
else
true
fi
}
ns_mapped () {
xlswins | grep Netscape: /dev/null
}
if not ns_mapped; then
netscape
fi
while not ns_mapped; do
## Should have a check here in case netscape never maps for some reason
sleep 2
done
netscape -remote "openURL($1$WINDOW)"
That should approximately work. I use lynx or w3m, so I'm not
completely sure.
Zach, your config is weird. You're sending to mutt-users, but it's not
in the header, so responses to your mail don't go the list by default.
--
-D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: can't pgp sign
On 2001.03.13, in [EMAIL PROTECTED], "Horace G. Friend III" [EMAIL PROTECTED] wrote: Hi, I've got pgp (ver. 6.5.8i) working outside of mutt. I can also verify signed msgs after I get their public keys outside of mutt. But I can't sign outgoing msgs. After selecting the (s)ign command from the pgp menu enter my passphrase, I get a received signal 11 press any key to continue... message and the message doesn't get sent. What's signal 11? Which manual should I look into -- pgp or mutt? Run "kill -l". On most (but not all) systems, it's a segmentation fault (SIGSEGV). -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: mutt as newsreader
On 2001.03.07, in [EMAIL PROTECTED], "Suresh Ramasubramanian" [EMAIL PROTECTED] wrote: mike polniak proclaimed on mutt-users that: Is anyone using mutt as a newsreader? Supposedly there is a nntp patch for mutt. Any comments on how well this works? Vselvolod (sp?) Volkov has a newsreader patch for mutt - and you'd post through a mail2news gateway. There isn't a good newsreader. The mutt patch works OK in some respects, but I keep finding constraints which I haven't had time to investigate and bring up with VVV. For *basic* newsreading, though it's my preference. Do mutt users have a preferred newsreader? slrn - http://space.mit.edu/~davis/ The interface is just like an old mutt (with the dual window view) I disagree. I don't think slrn is like mutt at all. I love mutt. I find slrn very difficult to use - I'd rather use trn. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: mutt as newsreader
On 2001.03.07, in [EMAIL PROTECTED], "ndrw mchl grnbrg" [EMAIL PROTECTED] wrote: Well, slrn requires some config, just like mutt does, but all in all, I think it's a very good newsreader. It's not the configuration, mainly; it's the way it works. It doesn't accomodate the way I read news. But the configuration is also less than ideal. I don't enjoy S-Lang. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Word-wrap when printing and quoting
On 2001.02.28, in [EMAIL PROTECTED],
"Dirk Laurie" [EMAIL PROTECTED] wrote:
The problem is this: by the time vim gets control, the quote sign ""
has already been prepended to the line. I want the line-break algorithm
to do its thing before the "" sign gets prepended.
The problem is also that this is another weird vim-ism.
Try using "par q" to reformat your lines. You can set up a macro for
this. I've used
map v mz{j0!}par 72gh^M'z
(^M is really control-m.)
Par is available from
http://www.cs.berkeley.edu/~amc/Par/
if you don't already have it. It's like "fmt", but holy cow.
--
-D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Unbind All?
On 2001.02.22, in [EMAIL PROTECTED], "Jay Rossiter / Signe" [EMAIL PROTECTED] wrote: Is there a way to unbind all keys with one, or a small series, of commands? I'm trying to set mutt up so that the only commands bound are ones that I explicitly set. I'm tired of tpyoing a key and ending up in some menu or option that I didn't want. Hopefully, I can find something short of "Unbind each key seperately", but if anyone has a script to do this, that'd work, too. :p There's not now, but I have a patch to define that permits "unbind" and "unmacro" to do this. See http://home.uchicago.edu/~dgc/mutt/#unbind That patch was for mutt 1.3.2, but might apply on 1.2.5. If you have trouble, let me know and I'll backport it. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: one aliase for multiple email addresses
On 2001.02.18, in [EMAIL PROTECTED], "[EMAIL PROTECTED]" [EMAIL PROTECTED] wrote: I'm wondering if it's possible to setup an alias that delivers to multiple addresses? Something like... alias foo [EMAIL PROTECTED] [EMAIL PROTECTED] (foo group) Something like that. The manual says: 3.2. Defining/Using aliases Usage: alias key address [ , address, ... ] It's usually very cumbersome to remember or type out the address of someone you are communicating with. Mutt allows you to create ``aliases'' which map a short string to a full address. Note: if you want to create an alias for a group (by specifying more than one address), you must separate the addresses with a comma (``,''). -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: index_format to show attachments?
On 2001.01.30, in [EMAIL PROTECTED], "Duncan Watson" [EMAIL PROTECTED] wrote: Hello, I am trying to show messages that attachments in the index. I took a look at index_format but no luck at first reading. Does anyone have an idea on how to accomplish this? Can't be done, but I wrote a patch that permits this. http://home.uchicago.edu/~dgc/mutt -- Duncan Watson Application Engineer [For best reading adjust your window width to the length of this line -djw] 123456789012345678901234567890123456789012345678901234567890123456789012345 75 columns? What kind of terminal size is that? :) -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Extra line added on edit message
On 2000.12.28, in [EMAIL PROTECTED],
"Suresh Ramasubramanian" [EMAIL PROTECTED] wrote:
I am using some scripts for cleaning up some mails by setting editor
variable to script name. And, every time I try it, new lines get
added at end.
Could you share this script? Or you could just archive mails by using
date-wise folders in your .procmailrc (say mails from mutt-users in
march get appended to mutt-users-march)
I'm using this to macro-reply to messages with some stock response
text.
macro attach \;m "enter-commandset
wait_key=noenterpipe-entrymm-replyenterenter-commandset wait_key=yesenter"
"Send Mailman completion message"
"mm-reply" is attached. It's an "attach" macro because I use it only
to reply to MIME message/rfc822 components. It probably could be a
"normal" macro if you wanted to do that kind of thing.
--
-D.[EMAIL PROTECTED]NSITUniversity of Chicago
#!/bin/sh
TMP=/tmp/mutt-formail-$$
mailquote () {
awk '
ok==1 { printf " "; }
/^$/{ ok=1; }
{ print; }'
}
formail -brkt \
| mailquote \
| sed -e 's/^$/\
done\
/' ${TMP}
/dev/tty /opt/bin/mutt -H ${TMP} \
-e 'set abort_unmodified=no' \
-e 'set editor=/bin/true' \
-e 'macro compose e "\enter-command\set
editor=\"vi\"\enter\\edit-message\"'
/bin/rm -f ${TMP}
Re: Why doesn't xterm refresh?
On 2000.12.20, in [EMAIL PROTECTED], "Lance Simmons" [EMAIL PROTECTED] wrote: I don't understand this suggestion. I don't see the word "script" used in the Mutt manual in a way that seems relevant, or in the xterm documentation. Could you elaborate? The "script" program initiates a new shell which logs all character terminal events (i.e., characters) to a file. If you enter shell prompt% script You should get a new shell prompt with a different history number. Run mutt in there. tcsh% mutt Then exit mutt after damage is done, and exit the secondary shell. "Script" will tell you the session was logged to a file called "typescript". You can replay this session using cat, more, less, etc. Thomas is saying that application errors of the variety you describe should reveal themselves in the typescript, as well as while initially running the application. Environmental (X, terminal emulator program, etc.) errors will not, because the typescript file is a log only of the shell and the mutt session. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Question regarding clearsigning emails automatically
On 2000.12.14, in [EMAIL PROTECTED], "Lars Hecking" [EMAIL PROTECTED] wrote: IMHO signing list email is a useless and wasteful exercise, especially if the sender hasn't submitted his/her keys to the public keyservers. In this situation, those who have configured their encrytion software to automatically import keys from these servers are penalised. This has come up before in my conversation with others. I think that signing all mail as a policy is a waste of resources and a potential source of annoyance, whether it's list mail or not. I think that sensitive material (code patches, or authoritative announcements of new software releases, or analyses of the latest Communications Prohibition Act, and the like) ought to be signed if possible; anyone who is concerned about the validity of the message can check the signature if they like. But, by and large, it doesn't matter. I don't really care whether it was really the person I know as Lars Hecking who wrote the message I'm replying to right now. It only matters what's said in this case, and not much who said it. If I want to confirm all this, I can write to Lars and he can sign it. If I sign my mail to Lars, he'll quite possibly even sign his reply. But chances are exceedingly small that any given item of information really needs to be corroborated. Since PGP became available, I've been asked only a handful of times to resend something with a signature. I'm reluctant to believe that's only because people don't know that I have a signing key. Having the signatures come up, and my mailer and OpenPGP client freeze while I wait to download a signature that might and might not be on the server that I use, only to discover that the signed material doesn't even need validation, is somewhat irritating at times - semi-political privacy agenda or no. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Error messages
On 2000.12.13, in [EMAIL PROTECTED], "Charles Curley" [EMAIL PROTECTED] wrote: When working on my .muttrc, it would be very nice if there were some way to see error messages generated by bugs in the .muttrc. Is there any such mechanism? You mean just to test the muttrc file and report parse errors? How about: mutt -F test.muttrc -f /dev/null -e "push x" /dev/null -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: limiting to message size
On 2000.11.07, in [EMAIL PROTECTED], "Mikko Hänninen" [EMAIL PROTECTED] wrote: Jonathan Scott Duff [EMAIL PROTECTED] wrote on Mon, 06 Nov 2000: Hi, I'm using mutt 1.2.5i and was wondering if there were some convient way to match messages based on the number of paragraphs, lines, words, characters, etc.? No way currently. Well, characters is the same as the message size, so ~z works for that. But nothing else is available. A patch might be added if someone made one available. :-) Word/paragraph information is not present in the message object in mutt's code, and I don't think it should be, and I don't think it will be. :) However, I can imagine a pattern expression that pipes each message through a command, and matches based on that command's exit status: if 0, match; else, no match. This could work like: ~Z 'set -- `wc %s`; [ $2 -gt 1000 ] true || false' to match messages with more than 1000 words. This would be slow, but simple, and possibly useful. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: mailing a stream as a file
On 2000.11.04, in [EMAIL PROTECTED], "Eric Smith" [EMAIL PROTECTED] wrote: Hi This "works" zip - *txt|mutt -s'send a zip file of all txt docs' eric -a - Odd; it doesn't work for me. The syntax you give fails to send to the users "-a" or "-". Putting "eric" after all options (as I would expect to be necessary) fails to attach "-". on 'V' in mutt received mail gives: - I 1 no description [text/plain, quoted, iso-8859-1, 96K] A 2 - [text/plain, 7bit, us-ascii, 0K] With the top one being a legal zip file - only problem is that you have to name the file when saving it, cause it is nameless. Also the encoding says test/plain but when you save the attachemnt, you get a legal zip file. Is there a way to force a file name? this will also help mutt to state the encoding correctly. I expect that you can use "-e push 'keystrokes'" to push the keystrokes or symbols for changing the attachment's name and file type, but I can't test that hypothesis -- see above. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Two suggestions
On 2000.10.24, in [EMAIL PROTECTED], "Dan Boger" [EMAIL PROTECTED] wrote: yikes! why would you want to ever overwrite a whole folder with one message? I'd be scared of hitting o by mistake... Mutt treats all save files as folders. Sometimes you just want the one message, but you might have reason to save twice. I've wanted this. It might be sensible to offer this choice only if the "folder" is not truly a folder -- that is, it's not under the $folders path. I wouldn't want to answer it all the time, though. I'm not sure it's worth the confusion, on the whole. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Addressbook For Mutt
On 2000.10.05, in [EMAIL PROTECTED],
"Pyuesh Daya" [EMAIL PROTECTED] wrote:
Is it possible to run two external programs to run with mutt. I am already running
the "Shift Q" to query an external perl script which queries an Ldap ServerIs
this possible...
How do I bind another stroke key to query another external Program !!
Assuming you want to query both sources each time, I'd just use a
wrapper:
#!/bin/sh
for query_source in local ldap qi; do
mutt_query_${query_source} "$*"
done | sort | uniq
set query_command="query_wrapper '%s'"
or something like that. All untested, of course; I only use one
directory source.
--
-D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: request
On 2000.09.27, in [EMAIL PROTECTED], "David T-G" [EMAIL PROTECTED] wrote: With the dev versions of mutt, or with 1.2.5 and patches, you can create and edit an X-Label: header which can contain anything you wish; you can even act against it with an expando. I use this to note tips, scripts, URLs, and the like all of the time. These patches are at http://home.uchicago.edu/~dgc/mutt/ There's a patch to add the basic X-Label (that's already in 1.3.x) support to 1.2.5, and also a couple of patches to extend that with an edit-label function. I find that really handy. (And David T-G, the updated patch fixes that 1.1.12 patch bug. :) You can also edit the email in place (well, in an automated fashion and with it saved back to the current mailbox, but it will be at the end of the file) with the 'e'dit command. edit-label makes the edit-message step unnecessary -- just press "y", then enter the new label and enter, and it's done. Works on bundles of tagged messages, too. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago PGP signature
Re: Attachements
On 2000.09.28, in [EMAIL PROTECTED], "Emmanuel Anne" [EMAIL PROTECTED] wrote: I had a look at the docs, but could not find a way to handle bad attachements ie : jpeg images attached as "application/octet-stream" insted of "image/jpeg". Does someone know a way to view them directly instead of first saving them on the disk ??? Obviously you're going to have to tell Mutt what kind of attachment you're dealing with, or else a command to process it with. You can use 'v' to go into theattachments list, and pipe individual attachments to a program. If you have a script that will feed stdin to xv (or whatever), you can pipeto that script. Or, if you want to automate more, you can pipe to a program that takes the content-type on the command line, and uses metamail to invoke the correct viewer no matter what. Then you can set up macros, one for each kind of data you receive as octet-stream, that will try viewing the attachment as a single type. OR, you can write a script that saves the stdin to a tmp file, use "file" to determine what kind of data is in it, and invokes metamail on the corresponding content-type. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Q: Why no replies to my post??
On 2000.09.27, in [EMAIL PROTECTED], "Byrial Jensen" [EMAIL PROTECTED] wrote: On Tue, Sep 26, 2000 at 09:08:23 -0500, David Champion wrote: Me, too. I take a different approach: I have a short wrapper script that I use for invoking mutt. It sets LANG, then returns LC_COLLATE to C so that sorting works correctly. :) Mutt disregards the setting of LC_COLLATE and always sorts according to the C locale. But of course it is good to be prepared Yes, but Mutt's subprocesses don't. :) if this bug someday should be fixed. :-) (It can easily be fixed by replacing a few mutt_strcasecmp() calls with strcoll() calls in sort.c, I think). That sounds like it would be good, although I'd never take advantage, personally. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Content-Disposition
On 2000.09.26, in [EMAIL PROTECTED], "Andy Spiegl" [EMAIL PROTECTED] wrote: Bruce DeVisser wrote: ^D on the compose menu toggles this, under Mutt 1.2.5i. (If I hit ? in the compose menu, it's the very first keybinding described. :) Great! I just upgraded and really like this feature. Now I am wondering how I can set the default of disposition to I(nline). I can't find anything about that in the manual. Is there a way? Well, you can set a compose macro to inline after adding. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: asked many times
On 2000.09.26, in [EMAIL PROTECTED], "Andy Spiegl" [EMAIL PROTECTED] wrote: So I tried: send-hook '~C mutt-' 'set from="Andy Spiegl [EMAIL PROTECTED]"' but then from is set for the next mail, not for the current one. *argh* This is good and correct. How did you guys solve this dilemma? You need to define a send-hook matching anything, with precedence over this send-hook, which resets $from to a default value. For example, I have this in my muttrc: send-hook '.' 'unmy_hdr Reply-To:' send-hook '~C postmaster@uchicago' 'my_hdr Reply-To: [EMAIL PROTECTED]' The first one unsets Reply-To: for any send, then passes on to the second. The second one sets Reply-To: for any mail to our postmaster address (which forwards to me). Not quite the same as setting $from, but close enough to illustrate. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: message's important flag
On 2000.09.26, in [EMAIL PROTECTED],
"Lukas Schroeder" [EMAIL PROTECTED] wrote:
Anyways, besides this beautiful '!' next to the message, does a set
important flag of a set of messages trigger any additional useful
functionality like easy switching via repeated TAB-punching or
something?
Sure, if you say:
macro index tab "search~Fenter" "Find next flagged message"
:)
TAB finds the next (N)ew message by default.
I also have a "color" line to highlight my flagged messages in red, and
this procmail rule to process messages the sender tagged as urgent:
:0 f
* ^(Importance: High|Priority: Urgent)
| ${FORMAIL} -I "X-Status: F"
Now when PC users make a message important, it comes into my mailbox in
red with the "!" on.
--
-D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Content-Disposition
On 2000.09.26, in [EMAIL PROTECTED], "Andy Spiegl" [EMAIL PROTECTED] wrote: Well, you can set a compose macro to inline after adding. Ehmm, sounds like a good idea, but how do I do that? Sorry for the stupid question, Andy. Actually, I think it was a bad idea. I guess you can't macro an interactive text entry *and* keystrokes that come afterward. You have to pre-assign the entered text, or stop with the symbol that invokes the text entry. It wouldn't be a bad feature to add, though -- some special token meaning "wait for enter, then proceed with macro processing". -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: asked many times
On 2000.09.26, in [EMAIL PROTECTED], "Mikko Hänninen" [EMAIL PROTECTED] wrote: David Champion [EMAIL PROTECTED] wrote on Tue, 26 Sep 2000: send-hook '~C mutt-' 'set from="Andy Spiegl [EMAIL PROTECTED]"' but then from is set for the next mail, not for the current one. *argh* This is good and correct. Uhh, no. You can't use $from with send-hooks, because as the person posting noticed, the $from only comes into effect for the next email. You have to use "my_hdr From:" if you want to change the From line from send-hooks. Not sure if that's what you were talking about, or not. :-) OK, I've never actually tried using $from in a send-hook, and was unaware of that issue. I was thinking of the general approach, not the specific hook command. (Oops.) -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Aborted unmodified message.
On 2000.09.26, in [EMAIL PROTECTED], "Marc van Dongen" [EMAIL PROTECTED] wrote: Hi there, I just re-installed vim on my system. When I now try to compose a message after I enter the name of the recipient mutt does not allow me to write a message. Istead it displays a Aborted unmodified message. message. set abort_unmodified=ask-no Wow, two questions in a row I'm dealing with as they roll in. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: catchup command?
On 2000.09.23, in [EMAIL PROTECTED], "Byrial Jensen" [EMAIL PROTECTED] wrote: Tag all messages, mark the tagged messages read, and finally untag them. Can be bound to macro if you like, for example: macro index R "T~Aenter;WN;t" "Mark all messages read" This is correct, of course, and what I gave is not. I should learn not to reply with unproven answers at 4:00 in the morning. :) -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: A better mutt? (Was Re: catchup command?)
On 2000.09.23, in [EMAIL PROTECTED], "Jens Askengren" [EMAIL PROTECTED] wrote: A GUI-mutt could be implemented by separating mutt into a backend and several frontends (curses, X11, etc). The frontend could be selected at compiletime, or loaded as a plugin/dll/.so-lib at runtime. Given the same .muttrc, the different frontends should feel and act the same. A few years ago, I was tired of my frustrations with MH, elm, and Columbia mm, and I hated Pine. Although I didn't really want to use a GUI, I had occasional uses for one, and knew others like having them, too. I had an idea then of producing a mailer founded on a small core, with modules to provide the front-ends, the mailbox interfaces, and script-language bindings. One DSO for an X frontend, one DSO for a curses frontend, one for an MH-like stateless system. One for CGI or mod_perl, maybe. A DSO for IMAP, one for MH, one for mbox, one for NNTP. A DSO for perl, a DSO for python. I wanted to provide interfaces suitable to implement all these, in such a ways that they could be used concurrently (although some UI combinations would be hard to make sense of). I was in the planning stages, and had written a tiny amount of core code, when I found mutt. I've been happily procrastinating ever since. (I don't really have that kind of time, anyway.) Mutt is an excellent mailer, good enough to resolve almost all my issues with the mailers I've used over the years. But I still like my original plan, and I still want to see it done, just because I feel that it's the right approach to a mailer's design. In some ways, it's easiest now if it's done on Mutt, but that's a LOT of code-mashing and munging. I don't know whether it's worth it anymore. But I think that kind of design is a REALLY good idea. And, in that light, there's absolutely no reason to bar a GUI front-end, even though I personally don't have much use for one. Additionally, a GUI-mutt could have a frame based addressbook, a .muttrc-wizzard, etc. Yes, but another interface could too. That ought not to be dependent on a GUI, although it might be most comfortable in a GUI. That ought to be an available interface to any willing UI. What do you think? If such an idea has a chance to go into the mutt-sources, I would like to contribute to a GTK-frontend. I guess you know what I think now. :) Yes, yes, yes, but I don't really know whether it's feasible, and I certainly don't know whether the mutt group is interested in this kind of fundamental change. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago PGP signature
Re: About PGP encryption
The address [EMAIL PROTECTED] is preferred over [EMAIL PROTECTED] On 2000.09.20, in [EMAIL PROTECTED], "Eugene Paskevich" [EMAIL PROTECTED] wrote: P.S. How can I include cookies from fortune for example into my signature? Answer directly please. You probably missed the other replies if you're not on the list. (That's a problem with using using lists/subscribe -- lots of lists are open.) Anyway, from the other replies I gather that the usual command for fortune is "/usr/games/fortune -s". In that case, put this in your .muttrc: set signature="/usr/games/fortune -s |" to have just a fortune. If you want to use a standard sig plus a fortune, try: set signature="cat .sig.std; /usr/games/fortune -s |" Or get fancier: set signature="/usr/games/fortune -s | fmt -w 45 | paste .sig.std - |" ...you get the idea. This last is essentially what I used below, except that I had to fake /usr/games/fortune since I didn't install it on my system. You can just replace all the stuff with "~/bin/foo |", where "~/bin/foo" is some script that creates the signature text however you please. -- -D."Spoke with Camus today about my cookbook. [EMAIL PROTECTED] Though he has never actually eaten, he gave NSIT me much encouragement. I rushed home University of Chicago immediately to begin work."
Re: News support in mutt
On 2000.09.20, in [EMAIL PROTECTED], "Wilhelm Wienemann" [EMAIL PROTECTED] wrote: Could you please give an URL were the nntp-support can be downloaded? http://www.fiction.net/blong/programs/mutt/#nntp There is also a NNTP-patch for mutt from "Andrej N. Gritsenko" [EMAIL PROTECTED] but I don't know about a Server to download this patch. Vsevolod Volkov has it now: http://mutt.org.ua/download/ I think nntp is definitily worth including into mutt. Mainly mutt is a Mail-User-Agent! Here it works very well together with 'slrn' to forward or reply a Newsposting. Maybe such combination will also work for you. If you ask me, this is a completely artificial distinction. I personally don't think slrn works well at all, but mutt works wonderfully. The NNTP support has problems, but mutt is still a better newsreader for me than slrn, tin, trn, or that other one that used to be popular. I don't mean to start a fight, just to say that this answer does not work for everyone. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Completely rewriting the From header programatically
On 2000.09.15, in [EMAIL PROTECTED], "Dave Morse" [EMAIL PROTECTED] wrote: I pop my mail from [EMAIL PROTECTED], and write email from home as user dm on a system that calls itself bomberlan.net. What is the voodoo I put in the .muttrc that makes mutt always send mail appearing to be from "[EMAIL PROTECTED]". set from="[EMAIL PROTECTED]" set use_from Really, I have 2 mail boxes, another one is svref at yahoo.com. In replying to a message, is there a way I can set the From field to be the address that the person originally wrote me at? set reverse_name -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: signature detection for color and mono
On 2000.09.14, in [EMAIL PROTECTED], "Lukasz Stelmach" [EMAIL PROTECTED] wrote: By³a godzina 23:09:20 w ¶roda 13 wrzesieñ, gdy do autobusu wsiad³ kanar i wrzasn±³:"David Champion!!! Bilecik do kontroli!!!" A on(a) na to: Is there any way to disable this? I want the pager to treat signatures the same as the body Correct me if i am wrong you do not wan colorful signature? If so do in Correct, but I also want my body regexes to color parts of the signature -- I don't want it treated as a single big block. The thing is: I have directions in .muttrc for coloring URLs and email addresses differently from the surrounding text. These often appear in signatures, and I'd like them similarly highlighted there. I think this requires a code patch, but not a major one. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
signature detection for color and mono
Is there any way to disable this? I want the pager to treat signatures the same as the body -- at least as far as colorizing body regexes goes. "Color signature" won't take a regex argument; it colors the whole signature. Would a patch to treat this be accepted? :) -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: not a FAQ
On 2000.09.12, in [EMAIL PROTECTED], "Bruce DeVisser" [EMAIL PROTECTED] wrote: On Tue, Sep 12, 2000 at 02:22:19PM -0700, Chris Chisolm wrote: I have read all the FAQs I can find and searched the man page but I still have a couple questions. 1. How do you forward a message, including all the attachments that came with the message? Ideally I would include the forwarded main message as text and the all the attachments would be auto loaded as attachments to the new mail. Manual, section 2.5: Forwarding can be done by including the original message in the new message's body (surrounded by indicating lines) or including it as a MIME attachment, depending on the value of the $mime_forward variable. Decoding of attachments, like in the pager, can be controlled by the $forward_decode and $mime_forward_decode variables, respectively. The desired forwarding format may depend on the content, therefore $mime_forward is a quadoption which, for example, can be set to ``ask-no''. The inclusion of headers is controlled by the current setting of the $weed variable, unless mime_forward is set. I use: set forw_decode set mime_forward=ask-yes On a related note, I am wondering if there is a way to add an attachment consisting of an *attachment* from another email (as opposed to an *entire* other email). View attachments, select the interesting one, press the "forward" key. Or select multiple interesting ones, and tag-forward. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: not a FAQ
On 2000.09.12, in [EMAIL PROTECTED], "Chris Chisolm" [EMAIL PROTECTED] wrote: 1. How do you forward a message, including all the attachments that came with the message? Ideally I would include the forwarded main message as text and the all the attachments would be auto loaded as attachments to the new mail. See other reply; sorry, did not include your address. 2. This is probably an RFE but...Is there any way to save a set of complicated limit strings(perhaps to a file) and so have a preset list of choices on how to limit and display your mail? Macros. Something:TO something or CC something or subject something or subject 1844 or subject 524158 or subject 6437265; I'm not sure what "Something:" means, but if this is a common limit, put this in your .muttrc. (Pick your own binding; I chose "%1" pseudo-randomly.) macro index "%1" "limit~C something | ~s \"(something|1844|524158|6437265)\"enter" When you want that limit, type "%1". -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: delete-and-jump-to-next-unread
On 2000.09.09, in [EMAIL PROTECTED], "Jens Askengren" [EMAIL PROTECTED] wrote: macro index Delete"delete-messagenext-unread" but since delete-message automatically skips to the next it doesn't work as expected. What about macro index Delete "delete-messageprevious-entrynext-unread" -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: config question
On 2000.09.08, in [EMAIL PROTECTED], "Gary Johnson" [EMAIL PROTECTED] wrote: On Thu, Sep 07, 2000 at 11:15:18PM -0700, Jason Helfman wrote: Would their be a way to configure mutt to test if I am running X, and based off the exit of this, 1 or 0, use a particular mutt variable setting? Something like this? set editor=`RunningX echo gvim || echo vim` Or: source `RunningX echo .muttrc.x || echo /dev/null if you have a lot of things to vary. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: config question
On 2000.09.08, in [EMAIL PROTECTED], "Jason Helfman" [EMAIL PROTECTED] wrote: On Fri, Sep 08, 2000 at 01:05:38PM -0500, David Champion muttered: | On 2000.09.08, in [EMAIL PROTECTED], | Or: | source `RunningX echo .muttrc.x || echo /dev/null | | if you have a lot of things to vary. What is this all about, RunningX ? is this a process? I just copied what Gary said, but RunningX is a program that checks whether you're running X. It amounts to the attached code. Run it through shell and it produces "ifx" in the cwd which does the same thing. Whee, that was fun. :) -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago ifx.sh
Re: mbox to maildir
On 2000.09.06, in [EMAIL PROTECTED],
"Jason Helfman" [EMAIL PROTECTED] wrote:
Does anyone have a script that does this?
If you have mh or nmh installed, I'd think that you can "inc" the mbox
to a new folder and rename that folder's directory as .../folder/cur,
then mkdir ../folder/{tmp,new} as well.
You can also do something like this:
formail -s sh -c 'cat .../foldername/cur/`expr $FILENO + 1`' mbox
--
-D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: urlview and netscape not fast enough to read tmp file ?
On 2000.08.24, in [EMAIL PROTECTED],
"Ron da Silva" [EMAIL PROTECTED] wrote:
Seems like mutt writes attachments to /tmp and forwards the filename
to netscape (based on my mailcap file) and then deletes the /tmp file;
however, seems like sometimes the file gets deleted before netscape
finishes reading the file from /tmp. Thus, I get a partial page or
none at all.
Anyone seen the above? Any ideas on fixing it?
Use this script (or something like it) as your viewer, like this:
image/jpeg; ns-wrapper %s
#!/bin/sh
## Wrap ns so that it doesn't lose the file
set -- `echo $1 | sed -e 's/\(.*\)\.\([^\.][^\.]*\)$/\1 \2/'`
file=$1-tmp.$2
echo ln -s $1.$2 ${file}
netscape -remote "openURL(${file}, new-window)"
exec sh -c "sleep 60; rm -f ${file}"
Untested, watch out, beware, etc.
--
-D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: urlview and netscape not fast enough to read tmp file ?
On 2000.08.24, in [EMAIL PROTECTED],
"Brendan Cully" [EMAIL PROTECTED] wrote:
As I recall, doing something like adding copiousoutput to the
particular mailcap entry may work (by getting mutt to wait for you to
press a key)... or maybe it was needsterminal...
I think the problem is that netscape -remote returns immediately once
the command is delivered, and not necesarily after the remote operation
has completed the page load.
On Thursday, 24 August 2000 at 16:41, David Champion wrote:
#!/bin/sh
## Wrap ns so that it doesn't lose the file
set -- `echo $1 | sed -e 's/\(.*\)\.\([^\.][^\.]*\)$/\1 \2/'`
file=$1-tmp.$2
echo ln -s $1.$2 ${file}
netscape -remote "openURL(${file}, new-window)"
exec sh -c "sleep 60; rm -f ${file}"
Oops -- this last line obviously won't work. Maybe just cut out the
"exec".
--
-D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: 1.3.x series need for iconv/libiconv
On 2000.08.17, in [EMAIL PROTECTED], "Martin [Keso] Keseg" [EMAIL PROTECTED] wrote: The two places that needed libiconv were Solaris 2.6 and Red Hat Linux release 6.1. no, it;s not a problem about development computers, that's a problem of solaris. I was talking about iconv problem with Brendan Cully and we were making some tests and we decided, that ppl on solaris have to use libiconv. I've yet to see why more recent versions of Solaris than 2.6 would require libiconv. But 2.6 is three years old. I'd sooner recommend upgrading your OS, if you have that authority and aren't bound by poor applications or paranoid application developers. :) Solaris 7 and 8 seem fine with their native iconv interfaces. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: script, macro
On 2000.08.17, in [EMAIL PROTECTED], "Jason Helfman" [EMAIL PROTECTED] wrote: no not while vi is open...I mean I am in mutt. I run a macro, asks me some questions, and passes it right to vi Is this for new mail? You can write a macro that sets $editor to a script which runs the questionnaire, then runs your real editor, then sends and changes $editor back to something normal. well i guess even further is, what are ppl doing when they say they have soemthing that is being passed through a scriptcould it be the other way, the script asking them Don't know what you mean. even further on this issue..., i guess I could just make a script and have it echo to /var/qmail/bin/qmail-inject ??? I don't know how qmail-inject works, but ( echo From: me@mine echo To: you@yours echo Subject: this echo Date: now echo echo bye. ) | /usr/lib/sendmail -oem -fme@mine you@yours is quite a common way of scripting mail deliveries. Still not clear what you're looking for, but maybe that helps. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: MIME Parts Not Forwarded?
On 2000.08.16, in [EMAIL PROTECTED], "Todd Goodman" [EMAIL PROTECTED] wrote: What I'm ultimately looking for is to edit the first text part (as when I answer no to mime_forward) but to still have all other parts of the orginal message attached just as they were in the original. Use resend-message. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: The Endless Quest for Simplification
On 2000.08.16, in [EMAIL PROTECTED], "Evan Vetere" [EMAIL PROTECTED] wrote: I've got a bunch of mail files in ~/mail; procmail drops stuff there. Each file in that dir is, uh, sourced, in my .muttrc: mailboxes ~/mail/blah ~/mail/bork ~/mail/foo ~/mail/zort Can I generate that list automagically? I'm imagining something like: mailboxes ~/mail/* You could try: source 'echo mailboxes `ls ~/mail/.` |' Not sure it'll work, but something like it should. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: push and the limit command
On 2000.08.15, in [EMAIL PROTECTED], "[EMAIL PROTECTED]" [EMAIL PROTECTED] wrote: push "l!~s '^DON'\\''T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA$'^M" This (I hope) anchors the string at both ends so that only messages with this exact subject will be matched so messages with 'Re:' on the front etc. will not be ignored. Turns out you also can use: push "limit! ~h X-IMAP:return" or, I guess, push "l! ~h X-IMAP:\n" I can't guess how much slower that might be, if any, but it's surely simpler. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Build problem with 1.3.7 on Solaris
On 2000.08.11, in [EMAIL PROTECTED], "[EMAIL PROTECTED]" [EMAIL PROTECTED] wrote: I have checked this out thoroughly now and I'm convinced there is some sort of problem building 1.3.7 (and 1.3.6) on Solaris. ... make: Fatal error: Don't know how to make target `../types.h' Current working directory /usr/chris/mutt-1.3.7/imap *** Error code 1 This is exactly the same problem as the older keymap_defs.h problem, just a different file. The mechanics for dealing with these depends seem to depend on weird properties of GNU make. You can either make types.h first (I suppose; I haven't tried it) or use GNU make. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
[OT] Re: Automatic mail archiving
On 2000.07.26, in [EMAIL PROTECTED], "Gregor Zattler" [EMAIL PROTECTED] wrote: * David Champion [EMAIL PROTECTED] [Mit 26 Jul 2000 03:37:59 GMT]: I have procmail deliver to ~/Mail/lists/listname. Each "listname" in that directory is a symlink to ~/Mail/lists/monthly/listname-MM or to ~/Mail/lists/annual/listname-. A cron job rewrites the symlinks once a month using a Makefile designed for handling the links. I'm interested too. I know it's OT on this list but perhaps it's easier to post it on the list. There were a number of people interested, so I guess I will. I cleaned commented it up a bit, too, and added an ability to do quarterlies since Mikko mentioned that. It's not hard to define whatever period you want. I hope everything still works. :) I feel a little foolish -- there's really no reason this should be a makefile instead of a shell script. But my old archive handler (using another scheme) used make with good reason, so it came naturally in this case. Oh well. I'll add to what Mikko mentioned before: using symlinks is nice, too, because it takes a lot of weight from procmail. Using symlinks is essentially caching the "date" command output on the filesystem, and executing it once per month rather than with each incoming message. It's altogether more efficient. Enough of that. Here's the file. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago ## ## Makefile for managing periodic mail-archive symlinks ## ## $Id: Makefile,v 1.2 2000/07/27 10:16:23 dgc Exp $ ## ## DIRECTIONS: ## 1. Drop this Makefile into a directory where you want to keep links to ##your archives. ## 2. Create subdirectories there named "annual", "monthly", and/or ##"quarterly", or whatever you'd rather call them. ## 3. For each archive: ##a. Decide whether you want to cycle the archive on an annual, ## quarterly, or monthly basis. ##b. Run "make add ARCHIVE=name-of-archive PERIOD=xxx", where "xxx" is ## the period you decide on. This will create the initial symlink. ## 4. Set up procmail to deliver mail into the "name-of-archive" folder. ## 5. Create a cron(1) task to run "cd .../path/to/dir; make rotate" once ##per month. This will update all symlinks. (Actually, you can run ##this more or less often; it doesn't matter. If you made a weekly ##period, you could run it monthly *and* weekly.) ## ## NOTES: ## The file for the "family" archive (cycled monthly) for April, 1998 ## will be .../monthly/family-199804. You can gzip these if you wish -- ## no trouble. ## ## To add support for a new period, create a subdirectory for it, and ## add a macro definition for SFXfoo as below. SFXfoo should expand ## to the correct suffix for today's date, and be unique among all ## iterations of that period. For example, a period of one week, labelled ## according to the ISO definition, could use ## SFXweekly = `date %Y-%V` ## ## You can change SFX* macros as you wish if you don't like these formats, ## but be sure to change $(STRIP) accordingly. $(STRIP) must be capable ## of removing any of your SFX* macros from the end of a filename. ## ## Uncomment to debug, or use "make DO=echo". #DO = echo ## Default period for rotation of new archives with "make add-archive". ## Supercede this with (for example) "make add-archive PERIOD=quarterly". ## A valid PERIOD = monthly # You probably don't need to touch anything else. # ## Generates a suffix for PERIOD=annual SFXannual = `date +%Y` ## Generates a suffix for PERIOD=monthly SFXmonthly = `date +%Y%m` ## Generates a suffix for PERIOD=quarterly, like "1997q2". (Hi Mikko! :) SFXquarterly= `date '+[%Yq] P %m 1 - 3 / 1 + p' | dc` ## A command to strip suffices from archive files. STRIP = sed -e 's/-[0-9][0-9][0-9][0-9q-]*$$//' -e 's/-[0-9][0-9][0-9][0-9q-]*\.gz$$//' ## How to create and remove locks. LOCK= /opt/bin/lockfile UNLOCK = /usr/bin/rm -f ## A default target that tells you available targets. all: @echo @echo "make rotate- rotate all archives" @echo "make add ARCHIVE=name [PERIOD=xxx] - link new archive (default period=$(PERIOD))" @echo @echo "or, if you prefer:" @echo "make add-annual ARCHIVE=name - link new archive (annual period)" @echo "make add-monthly ARCHIVE=name - link new archive (monthly period)" @echo "make add-quarterly ARCHIVE=name- link new archive (quarterly period)" @echo ## Safety valves check-archive: @ if [ -z "$(ARCHIVE)" ]; then \ echo; \ echo '!!! You need to give ARCHIVE=name on the command line.'; \ echo; \
Re: Hiding Subjects in PGP-encrypted messages
On 2000.07.29, in [EMAIL PROTECTED], "Randall Hopper" [EMAIL PROTECTED] wrote: One wish I have is for there to be an alternative way to specify the subject such that it is stored and retrieved from the body and not the header, so it can be PGPed. I'd like this, too, and so would other people I do encrypted mail with. The real problem is that there doesn't seem to be a standard for it, so even if we came up with a solution here, there's no promise that other mailers would decide on the same thing. A mailer-specific solution to this is almost sure to create segmentation and incompatibility. This discussion should occur in an open group. Using a mime component is a good starting point. It makes it easier for a mailer to search subjects, should it choose to do so. A standard could also decide on X-PGP-Subject, or somesuch, and make that an armored encryption. But that decision must be standardized to have any real value. (end soapbox) Meanwhile, we (I and my correspondents) typically just copy the Subject: line to the body of the message and put silly words in the real Subject: (to distinguish one thread from another). You can easily do this if $edit_hdrs is set. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Piping mail through a script from a macro
On 2000.07.27, in [EMAIL PROTECTED], "Ben Beuchler" [EMAIL PROTECTED] wrote: Good point. Fixed that but it still didn't work. It turns out that it was the \Cs. For some reason mutt didn't like using ^s as a macro. No matter what I specified there, it locked up. I checked and it is not being used anywhere else in the config. My Eterm doesn't have anything bound to that... Very weird. I changed the keystroke to 'Z' and it worked fine. $20 says it "unlocks" when you type ^Q. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: gnupg and pgp incompatibility
On 2000.07.24, in [EMAIL PROTECTED], "David T-G" [EMAIL PROTECTED] wrote: David, et al -- % So, short answer: Eudora can send to Mutt, but Mutt can't send to % Eudora, and it's Eudora's fault. FWIW, I have been able to send with mutt-0.95.4i and pgp5; my recipient may whine a bit, but he's been reading the messages well for quite a while now (since his upgrade a few months ago). Yes... to be more precise: Eudora can read signed messages, but (in my experience) it can neither verify signed PGP/MIME messages, nor decrypt encrypted PGP/MIME messages. In addition, I never have a problem reading his mail, but that could be because I'm using the procmail recipe from PGP-Notes and don't have to worry about it any more :-) Yeah. I just took that out of my own config so I can test this a little more -- I've just been studying Eudora the last couple of days. ME gave some sample macros for circumventing this issue when he posted his edit-type patch, I think; these should work in absence of procmail. I tried sending old-style messages with pgp_create_traditional; he tells me that Eudora detaches the message and he has to go and find it and open it (he chooses to use Word, of all things!), and the text is there. I'm not familiar with pgp_create_traditional -- I haven't been paying attention to this area of development, since it all works OK for me so far. :) I searched both mutt archives and a teeny bit of the web in general, but didn't find anything. Is "the old way" what you meant, or do you hint at something else? Yes: I was referring to macros for filtering components through PGP/GPG. You posted one of them. (Ah, no substitute for personal archives. Web archives can all * * *!) Here are examples with citations, altered a bit to be more readable. A lot of you have these already, but maybe this makes a useful summary for the FAQ or something. I think these will work, but I haven't tested them all since rewriting them. Check primary sources if in doubt. I'm not sure which of these would work best with Eudora, and my "Eudora-empowered" PC is not at hand. The usual disclaimers: I don't mean to suggest that there aren't better sources for this stuff; this is just what I found. No resposibility if this stuff crashes your mailer, erases your mail, drowns your fish, etc. Everything I say is a lie. + Basic composition filter to traditionally encode the current message component (typically the only component in a us-ascii, text/plain message), using PGP 2 or NAI's PGP 6. [1] macro compose S "filter-entrypgp +verbose=0 -fast \ +clearsig=on\nyedit-typekill-lineapplication/pgp; \ format=text; x-action=sign\n" + Use of the edit-type function to coerce a message into application/pgp format without use of procmail. [2] macro index \eS "edit-typekill-lineapplication/pgp; format=text; \ x-action=sign\n" macro index \eE "edit-typekill-lineapplication/pgp; format=text; \ x-action=encrypt\n" macro pager \eS "edit-typekill-lineapplication/pgp; format=text; \ x-action=sign\n" macro pager \eE "edit-typekill-lineapplication/pgp; format=text; \ x-action=encrypt\n" macro attach \eS "edit-typekill-lineapplication/pgp; format=text; \ x-action=sign\n" macro attach \eE "edit-typekill-lineapplication/pgp; format=text; \ x-action=encrypt\n" + Composition filters for signing and encryption with PGP 5. [3] # old-style signing macro compose S "filter-entrypgps +verbose=0 -fat \ +clearsig=on\nyedit-typekill-lineapplication/pgp;format=text; \ x-action=sign\n" # old-style encrypting ### have to hard-code recipient for now... macro compose E "filter-entrypgpe -s -r RECIPIENT -r 0xYOURKEY \ -fat\nyapplication/pgp; format=text; x-action=encrypt\n" D. T-G: "There is a patch out there, I believe, which will let you insert %r at RECIPIENT, but I forget what it is :-)" dgc: I'm not sure how this applies, myself, since there's no context in which to select a recipient. Seems you'd need pgpe to ask you, but I've never used it, so I'll leave it alone. + Composition filter for application/pgp signing using GnuPG. [4] macro compose S "filter-entrygpg --sign --armor --textmode \ --clearsign\nyedit-typekill-lineapplication/pgp; format=text; \ x-action=sign\n" 'clearsign the message' + Composition filter for very traditional (not even MIME at all) signing and encrypting, using PGP 2 or PGP 6. [5] macro compose S "filter-entrypgp +verbose=0 -fast +clearsig=on\nyedit-typekill-linetext/plain\n" macro compose E "filter-entrypgp +verbose=0 -feast +clearsig=on\nyedit-typekill-linetext/plain\n" [1] Included documentation, from mutt-*.*.*/doc/PGP-Notes.txt [2] M. Elkins, in [EMAIL PROTECTED] [3] D. T-G, in [EMAIL PROTECTED] [4] [EMAIL PROTECTED], in m12rJjB-000jXxC@localhost [5] C. Cera, in [EMAIL PROTECTED] -- -D.
Re: gnupg and pgp incompatibility
On 2000.07.22, in [EMAIL PROTECTED], "Dennis Robertson" [EMAIL PROTECTED] wrote: Hello List, I am trying to correspond with a friend who uses Windows and Eudora 4.3.2 (gasp!) with PGP 6.5.3. I use mutt and gnupg 1.0.1 ;). When he invokes decrypt on my messages all he sees is: "Content-type: text/plain: charset=us-ascii". That is the end of the process; no text Are you certain that you have mutt properly configured? What do you for a content-type if you bcc yourself one of these messages? What about Fcc:? is visible. He has no difficulty corresponding with me and others using pgp and windows. I have read of mutt's alleged shortcomings with mime on the qmail list. Is there a way to make mutt/gnupg and windows/eudora/pgp 6.5.3 talk to each other? I don't know about these allegations. As far as I know, mutt does PGP/MIME perfectly, but does not do SMIME or application/pgp. Eudora 4.3.2 will issue valid PGP/MIME, which mutt can read, but it can not read PGP/MIME issued by either mutt or itself. (Yes: Eudora cannot read its own output.) There are procmail rules for bending Eudora's usual PGP output into a format Mutt can work with. Check the web site or list archives. So, short answer: Eudora can send to Mutt, but Mutt can't send to Eudora, and it's Eudora's fault. (Actually there are ways to make Mutt send messages that Eudora can handle, but these are kludgy and don't involve proper MIME. I think they involve macros. Again, check the web or archives.) -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: SMTP
On 2000.07.13, in [EMAIL PROTECTED], "Marius Gedminas" [EMAIL PROTECTED] wrote: It's not that I advocate adding SMTP support to Mutt [2], but I just --- [2] Well, that would be a nice thing to have if I try to compile it on WinNT again ;) I don't mean to say anything about whether I agree with either side on this issue, but there are SMTP clients for Windows. I haven't used any of them, so I can't recommend one, but I believe that Blat! was recommended to me once. You can find a deep assortment of options and references at any search engine. http://gepasi.dbs.aber.ac.uk/softw/Blat.html http://www.google.com/search?q=smtp+client+windowsmeta=lr%3D%26hl%3D -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: tagging unread
On 2000.07.09, in [EMAIL PROTECTED], "Jason Helfman" [EMAIL PROTECTED] wrote: I searched threw the manual and it looks us though you may not be able to tag something as unread. If this is the case, why? If I am wrong, can you please point me to the right place in the manual... Keystrokes: w set-flag n (for new) -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: browsing imap folders, and other questions
On 2000.07.07, in 00a001bfe869$78def130$0200a8c0@mdaxke,
"Mark D. Anderson" [EMAIL PROTECTED] wrote:
Which implies to me that it is possible to browse folders of an IMAP server.
So how is that done?
In order:
c change-folder
? to list folders/enter browser
c change-dir
^u kill-line
then enter an IMAP path: e.g., {imap.demo.int/ssl}inbox
You can also just
set folder = {imap.demo.int/ssl}inbox
in your .muttrc; then all folders are IMAP folders, and the browser
goes to IMAP by default.
Also, is there a way to absolutely prevent mutt from mucking about with my /var/mail
or /home/mda/inbox and so on -- i want it to do nothing *except* imap.
See above; that's one way.
--
-D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: those users (was Re: Reply to all???)
On 2000.06.30, in [EMAIL PROTECTED], "Mrinal Kalakrishnan" [EMAIL PROTECTED] wrote: The advantage with LinuxDoc/DocBook DTDs is that you can convert it to any format you like later. So you can have an online HTML version, plain text, PS, PDF, etc.. (like the mutt docs) The disadvantage, last time I checked, is that it's still tedious to get them processed on Unix. Maybe that's not necessary, but I always argue with any decision that (in practice) drives data or a process out of the realm of portability. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: those users (was Re: Reply to all???)
On 2000.06.30, in [EMAIL PROTECTED], "Suresh Ramasubramanian" [EMAIL PROTECTED] wrote: get them processed on Unix. Maybe that's not necessary, but I always argue with any decision that (in practice) drives data or a process out of the realm of portability. ... so what format do you suggest? HTML is the best - still (imho) I'm a major fan of runoff. :) -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: tag-thread works sporadically
On 2000.06.30, in [EMAIL PROTECTED], "brd" [EMAIL PROTECTED] wrote: I've noticed that when tryting to tag a whole thread with the esc-t combo, sometimes it will work and sometimes not. I may have to do it a few times before it works, but it's not the same number each time. I think I've noticed the same thing with body search esc-b, so maybe it's a bigger problem with my setup. I haven't investigated this at all, but if I type ESC-anything too quickly, it doesn't go in. If I pause half a second between ESC and the next stroke, it's fine. This has been so with mutts from 1.0 (I think) through 1.3.3, on Solarises 7 and 8, with slangs 1.3.9 and 1.4.1 (and maybe also 1.2.2). I haven't tried with ncurses. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Default SUBJECT in forward..
On 2000.06.30, in [EMAIL PROTECTED], "Sergio Bruder" [EMAIL PROTECTED] wrote: There is a way to alter the default Subject of a forwarded message? set forward_format. The %-expansions are teh same as for $index_format. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Can't compile mutt 1.3.4
On 2000.06.29, in [EMAIL PROTECTED], "Mark Berry" [EMAIL PROTECTED] wrote: On Thu, Jun 29, 2000 at 12:39:26AM +0200, Thomas Roessler wrote: checking for iconv... yes checking whether this iconv is good enough... no configure: error: Try using libiconv instead Get libiconv from http://clisp.cons.org/~haible/. I downloaded libiconv-1.3.tar.gz and followed the generic install. However I still get the same warning as above. Can anyone tell me what I am doing wrong? Using Solaris? At line 4312 of configure, insert this line: mutt_cv_iconv_good=yes -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Removing a prefix from the subject of messages
On 2000.06.29, in [EMAIL PROTECTED],
"Lars Hecking" [EMAIL PROTECTED] wrote:
D'oh. That's a job for procmail's MATCH and formail. No need for an
external program.
No, but it's easier with an external program, because procmail's
$MATCHing is so weak. Here's my old procmail matcher (more or less):
:0
* LIST ?? .+
{
RE=""
:0
* SUBJECT ?? ^ *\/[rR][eE]:
{ RE="${MATCH} " }
:0 E
* LIST ?? yes
* SUBJECT ?? ^ *\[[^]]+\] *\/[^ ].*
{ NEW_SUBJECT="${RE}${MATCH}" }
:0
* LIST ?? yes
* SUBJECT ?? ^ *[rR][eE]: *\[[^]]+\] *\/[^ ].*
{ NEW_SUBJECT="${RE}${MATCH}" }
:0 E
* $ SUBJECT ?? ^ *\[${LIST}\] *[rR][eE]: *\[${LIST}\] *\/[^ ].*
{ NEW_SUBJECT="${RE}${MATCH}" }
:0 E
* $ SUBJECT ?? ^ *\[${LIST}\] *\/[^ ].*
{ NEW_SUBJECT="${RE}${MATCH}" }
:0 E
* $ SUBJECT ?? ^ *[rR][eE]: *\[${LIST}\] *\/[^ ].*
{ NEW_SUBJECT="${RE}${MATCH}" }
}
Here's the new one:
:0
* LIST ?? .+
{
NEW_SUBJECT=`echo ${SUBJECT} | sed -e "s/\[${LIST}\] *//g"`
}
(The formail runs later.) Am I missing something? Is there a way to
achieve the same match with \/ and $MATCH that uses fewer steps?
--
-D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: undelete messages
On 2000.06.25, in [EMAIL PROTECTED], "Vincent Danen" [EMAIL PROTECTED] wrote: How do I undelete messages? When I try to go back to a deleted message, mutt won't let me... I can't move the arrow onto it. I see Type in the message number to jump to any message, or use the next-entry and previous-entry bindings to scroll. Next-entry defaults to uppercase "J", and previous-entry is uppercase "K". -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Message attributes, MH folders
On 2000.06.20, in [EMAIL PROTECTED], "clemensF" [EMAIL PROTECTED] wrote: so, why in the world would one want to leave mh for mutt? Are you asking why in the world would one want to leave: next spacespacespacenext comp ... send spacespacenext spacespacenext spacespacespacespacenext next repl send for: spacespacespacespacespacem ... yspacespacespacespace spacespacespacespacespacespacespacer ... y ? Multiply by 50 times a day: that's why. I can use mutt with one hand behind my back, and I find that doing so is good for me. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: special flags (was Re: Message attributes, MH folders)
On 2000.06.19, in [EMAIL PROTECTED], "David T-G" [EMAIL PROTECTED] wrote: Any way to put the X-Label: contents into $index_format? My index_format has: "%?y?[%y] ?". From the docs: The ``X-Label:'' header field can be used to further identify mailing lists or list subject matter (or just to annotate messages individually). The ``$index_format'' variable's ``%y'' and ``%Y'' escapes can be used to expand ``X-Label:'' fields in the index, and Mutt's pattern-matcher can match regular expressions to ``X-Label:'' fields with the `` y'' selector. ``X-Label:'' is not a standard message header field, but it can easily be inserted by procmail and other mail filtering agents. And: %y `x-label:' field, if present %Y `x-label' field, if present, and (1) not at part of a thread tree, (2) at the top of a thread, or (3) `x-label' is different from preceding message's `x-label'. (Yuck! How did I do such a lousy formatting job?) I also have a patch that allows the label command (bound to 'y' by default) to edit labels in the status line, like similar commands for editing other fields. I find this immensely useful, but Thomas is happy with using edit-headers. :) Add-on for 1.3: http://home.uchicago.edu/~dgc/mutt/mutt-1.3.dgc.xlabel.3 All X-Label patches for 1.2: http://home.uchicago.edu/~dgc/mutt/mutt-1.1.12.dgc.xlabel.3 -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: special flags (was Re: Message attributes, MH folders)
On 2000.06.19, in [EMAIL PROTECTED], "David Champion" [EMAIL PROTECTED] wrote: On 2000.06.19, in [EMAIL PROTECTED], "David T-G" [EMAIL PROTECTED] wrote: Any way to put the X-Label: contents into $index_format? My index_format has: "%?y?[%y] ?". From the docs: ... fields with the `` y'' selector. ``X-Label:'' is not a standard message header field, but it can easily be inserted by procmail and other mail filtering agents. I'll add to this: %y and %Y both respond to the %?y?if-else? structure, and both take standard string-formatting stuff (%-4.4y). My procmail inserts an X-Label for each known mailing list, thus offloading most pattern-matching from Mutt to my MDA. Inside Mutt, I only every use ~y for matching lists. I also have a patch that allows the label command (bound to 'y' by default) to edit labels in the status line, like similar commands for editing other fields. I find this immensely useful, but Thomas is happy with using edit-headers. :) This works as well for multi-tagging. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: test=RunningX
On 2000.06.19, in [EMAIL PROTECTED],
"clemensF" [EMAIL PROTECTED] wrote:
Mrinal Kalakrishnan:
No it's different. If you're in a console while X is running, the
RunningX test will fail, because it actually tries to open the
display. Whereas the $DISPLAY variable still exists, so "test -n
isn't there some other way (a unix way) for trying to open the x- display?
is one of the standard /dev/* devices associated with an x- display?
Generally, it's a unix-domain socket (AF_UNIX), usually
/tmp/.X11-unix/X{displaynumber}. XOpenDisplay() is the standard way to
open it. This RunningX program is no more than a wrapper for
XOpenDisplay, so it's about as canonical as you get.
--
-D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Re:
I warn you now - this is more than you asked for.
On 2000.06.17, in [EMAIL PROTECTED],
"Andrew Eichmann" [EMAIL PROTECTED] wrote:
the subject line. For example, if the original message's Subject:
line is ``[BOB] What's the frequency, Kenneth?''where ``[BOB]'' is
the mailing list name that gets prepended to the subject, the replies
...
Is there a built-in solution to this? Does anybody else have this
problem? I imagine something stripping out all variations of ``Re:''
I have this problem, too -- it's one of the reasons I can't stand lists
that alter your postings' subject: lines.
My .procmailrc loads a file named "classaction". This file sets some
operational defaults, then loads a bunch of matching rules from another
file called "classes". It then alters messages as documented in
"classaction".
"classaction" and a stripped-down copy of "classes" are attached. In
reality, I process about 120 different lists and other categories of
like mail from this setup. It's fast, but that doesn't actually matter
since it's asynch with my mail-reading.
"$ ${XFROM}" is a procmail macro I use for matching sender addresses.
You can substitute the built-in "^FROM" (or whatever).
You'll note that this setup only marks messages by removing [LISTNAME]
stuff from the subject (if STRIPLAB is set in the list's config), and
adds the X-Label: header. I have mutt set up to do all its list
matching on "~y listname" instead of duplicating all the patterns, so
procmail and mutt are VERY intertwined here.
(X-Label: and "~y" are a 1.3.x thing. This makes it easy to move a
message from one category to another in Mutt's eyes. Once a message is
archived and delivered, it's all about Mutt, and I don't worry about
saving anything that has an X-Label: because I know it's already
archived.)
Anyway, maybe you don't want all that, but it shows how I'm using
procmail to match the expressions. :)
--
-D.[EMAIL PROTECTED]NSITUniversity of Chicago
###
###
### Handle all mail classes properly, phase 1.
###
### These DEFAULTS hinge archival, labelling, and inbox display on whether
### ${CLASS} is defined. For these options, you need only define ${CLASS}
### to a shorthand for the mail class a message should belong to.
###
### Nullify the class name. If CLASS is undefined, mail will pass through
### the class-action package untouched and unarchived. (Auto-forwarding
### will still occur, though.) ${CLASS} implies a few things:
### 1. Name of the archival folder
### 2. Name for class labelling (X-Label header field or Subject: rewrite)
### If ${CLASS} is literally "null", mail in a given class will be killed off
### after matching.
CLASS=
### If ${CLASS} is set to someting besides "null", and ${ARCHIVE} is set,
### messages will be archived. If ${ARCHIVE} is "yes", the archival folder's
### name will be copied from ${CLASS}. If ${ARCHIVE} is anything else, mail
### will be archived to that folder name.
###
### The archived copy will be unadulterated.
ARCHIVE=yes
### If ${CLASS} is set to someting besides "null", and ${LABEL} is set,
### messages will have an "X-Label:" header field inserted. If ${LABEL}
### is "yes", the X-Label will be set to ${CLASS}. If ${LABEL} is set
### to any other value, the X-Label will be set to that value.
LABEL=yes
### If ${HARDLABEL} is "yes", rewrite
### Subject: Re: foo
### as
### Subject: [$LABEL] Re: foo
### instead of inserting an X-Label: header.
HARDLABEL=no
### If ${STRIPLAB} is set to "yes", remove anything enclosed in square
### brackets from the beginning, or following a leading "Re: ", of the
### Subject: header. If ${STRIPLAB} is set to anything else, remove
### only such tags if they match ${STRIPLAB}. This is for removing
### the tags generated by some mailing-list managers so that we can
### prefer X-Label:s.
STRIPLAB=
### If ${HIDE} is set to "yes", the class-action package will not
### store messages in a class to the default folder (inbox). If ${HIDE}
### is unset, or set to anything besides "yes" , messages will be stored
### to the default folder IN ADDITION to any archival. The copy in the
### default folder will be marked with "Status: O".
HIDE=no
###
### Try to match mail to a list or class. Multiple matches are multiply
### acted upon.
INCLUDERC=$PMDIR/classes
### If CLASS was set to "null", just ditch it and end
:0
* CLASS ?? null
/dev/null
### If CLASS was set and ARCHIVE is set, prepare to archive
:0
* CLASS ?? .+
{
## Check the cache for this dropbox; drop if a repeat.
## Rewriting the value of IDCACHE here allows each list to
## maintain internal uniqueness, but doesn't prevent duplicate
## refiles of messages aimed at two or more separate lists.
IDCACHE=lists/`dirname $CLASS`/.`basename $CLASS`.idcache
Re: mailboxes
On 2000.06.18, in [EMAIL PROTECTED], "Dennis Robertson" [EMAIL PROTECTED] wrote: Hello List, This is embarrassing. I have made letterboxes in $HOME/Mail using touch. These new files don't open automatically but bring up the "open with" dialogue when clicked. Procmail evidently can't see or open them You don't mention what file-manager you're using, but many of them figure out the relevant application using the "file" command or /etc/magic. For the files to be recognized as mbox files, you need to have mail in them. As for getting mail in with procmail, see how you do with what Suresh and David said. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: [sureshr@staff.juno.com: Re: How do I make pop support do polling?]
On 2000.06.11, in [EMAIL PROTECTED], "Nils Vogels" [EMAIL PROTECTED] wrote: On Sun, Jun 11, 2000 at 03:22:27PM -0400, David T-G wrote: Nothing -- except in the minds of folks who make decisions at his company. *sigh* ... managers ... ;-) My group runs a system with nearly 500 concurrent users at peak times, and at least 100 at most times. We kill all user daemons and frequent cron tasks on sight. If people want to probe the IMAP server every 15 minutes from their own systems, that's not our business, but if they probe every 90 seconds, that also becomes our business, and we ask them to stop. There's nothing wrong with that, either. When you provide a resource to the public, you have the right to specify terms of service. P.S. I am not a manager. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Sci-fi question about voice email and auto_view
On 2000.06.11, in 005801bfd3a3$5bbb1320$f8a0a6d4@alderaan, "Daniel González Gasull" [EMAIL PROTECTED] wrote: Hello all. Perhaps this is a silly question, but, is there any program (say catwav) which let me do something like catwav message.wav and display the message in my console with speech recognition? I'd say "almost certainly not". As far as I know, speech recognition is not yet to the point that software can reliably do it without being "trained" to the voice that's producing the speech. The best way to handle this would be to put the voice recognition software on the mobile phone, and have it submit the email as multipart/alternative. That's a suggestion for anyone out there in the mobile phone business. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: new option?
On 2000.06.08, in [EMAIL PROTECTED], "Lars Hecking" [EMAIL PROTECTED] wrote: In principle, yes, but it may even work without. Nevertheless, echo -n is not portable. Unquoted backquotes turn all whitespace into plain spaces: `ls a b c` = a b c Quoted backquotes do not: "`ls a b c`"= a b c -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Open Netscape, remote new window
On 2000.06.01, in [EMAIL PROTECTED], "[EMAIL PROTECTED]" [EMAIL PROTECTED] wrote: I have my urlview working lovely with netscape opening inside the same window, but what if I want to open in a new window? % netscape -remote 'openURL(http://www.mutt.org/, new-window)' -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: headers in incoming mail
On 2000.05.26, in [EMAIL PROTECTED], "Manuel Arriaga" [EMAIL PROTECTED] wrote: Hi all, Two short config questions: - I have put "ignore (blabla)" into my .muttrc in order to keep the visible part of the headers in incoming mail readable, but now I would like to sort the different lines, too. Is this possible? Read the manual regarding the hdr_order directive. - Is it possible to set up your Fcc: mailbox (in my case Mail/Sent) so that it displays the messages recipiend in the index, instead of the sender (always me... :-)? folder-hook . set index_format="whatever is normal or default" folder-hook =Sent set index_format="change %f or %n or whatever to %F" I think. Actually, though I just use %F instead of the default all the time. It tells me who I sent to if I wrote it, and who it came from otherwise. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Binding bug + minor annoyance.
On 2000.05.26, in [EMAIL PROTECTED], "David DeSimone" [EMAIL PROTECTED] wrote: David Champion [EMAIL PROTECTED] wrote: Maybe the original poster (I forgot who...) would be OK with "unbind * *" and "unmacro * *". But there is no "unbind" nor "unmacro" command... I know. Implementing them just seems like a better solution to this problem. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Two ideas
On 2000.05.26, in [EMAIL PROTECTED], "Rob Reid" [EMAIL PROTECTED] wrote: You mean strip sigs from quoted text in a reply? That's the editor's job I strenuously disagree. I think we should rather say: it is the established judgement of the Mutt development team that stripping signatures from quoted text should be done by one's editor, not by Mutt. I don't think that signature removal is obviously a designated task of any program, but that it is a matter of personal preference and of contextual convenience. (This is why I think Mutt should be able to do it.) I hate to be redundant, but the matter-of-factness above was disturbing. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Exclusive matching
On 2000.05.25, in [EMAIL PROTECTED], "Mikko Hänninen" [EMAIL PROTECTED] wrote: ~L alice ~L bob ~L carol ^~L (alice\|bob\|carol) I'm curious, do you really need the first part, the three matches? The last part should do their job too. Since you tried these things, I suppose you tested it without them too... Yes, I do. The second part does't guarantee that a message is to/from all three. The first three patterns (ANDed) make sure that all three people get the message, and the last pattern makes sure that ONLY those three get it. Without it, a message from Alice to Bob (excluding Carol) is still matched. Well, it does, but it parses from "top down" -- it takes the whole string first, and then splits it up to expressions. | can be "or", so it splits it at that. It doesn't look at the context. You can avoid it by quoting it, like you did, or by giving the pattern in quotes: "^~L (alice|bob|carol)" (or something like that). Ah, I see. It's ^~L "(alice|bob|carol)". Precedence would be a good topic for the manual to go over quickly. do that. Is there some way to get $alternates into the expression? I don't think there's any way to expands a random Mutt variable in these situations, only the %-expandos... That's what I think, too, for the present. Should there be? I'm happy with a "yes" to either question. :) That's a "no" and a "maybe"... Sorry, no "yes". :-) "Wait and see" -- you are wise. Well, here's an example of wanting to evaluate your own address, where ~P and ~p are not enough. I'm not sure what an appropriate solution would be, except for permitting expansion of any "set" variable in the editor, but I can understand reluctance to do that. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Binding bug + minor annoyance.
On 2000.05.25, in [EMAIL PROTECTED], "David DeSimone" [EMAIL PROTECTED] wrote: Mikko Hänninen [EMAIL PROTECTED] wrote: That's good as an option, but then the problem would be that you can't have an independent stand-alone binary that works even with no resource files... Is this really one of the design goals of Mutt? I don't see a problem I don't know, but it's a useful (though not strictly necessary) fallback. with getting people used to the idea that there must be a system-Muttrc, and it should be copied wherever Mutt gets copied. That way, if a site has policies like domain-names and hidden-hosts, they won't get lost just because someone copies the Mutt binary somewhere else. Perhaps Mutt should simply fail to start without some sort of configuration input. :) Seems to me that the correct solution -- if you want to make this patch, anyway -- is not to change the default settings at all, but to make them active only when there's no system Muttrc. I'm uncertain how useful this is, though. To me, the best advantage of eliminating defaults is not having to unbind lots of stuff in your own files. But if the system Muttrc is going to make the same bindings, anyway, where's the gain? Maybe the original poster (I forgot who...) would be OK with "unbind * *" and "unmacro * *". -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Exclusive matching
Alice, Bob, and Carol want to find all email that was sent from any one
of them to BOTH of the others, but that was not sent to ANY fourth
person.
I can make mutt match all messages that include Alice, Bob, and Carol:
~L alice ~L bob ~L carol
My mailbox has a message from Carol to Alice, excluding Bob, which this
pattern does not match. Fine.
But I need still to exclude messages which are cc:ed to any fourth
party. The Mutt manual says:
4.2.1. Pattern Modifier
Note that patterns matching 'lists' of addresses (notably c,C,p,P and
t) match if there is at least one match in the whole list. If you want
to make sure that all elements of that list match, you need to prefix
your pattern with ^. This example matches all mails which only has
recipients from Germany.
If I read that correctly, then this pattern:
^ ~L alice | ~L bob | ~L carol
should exclude messages to Dave. It doesn't -- it matches everything.
A look at the source code suggests that this is a misread, though, and
that "^" goes before any pattern component. Well, this pattern:
^~L alice | ^~L bob | ^~L carol
doesn't match anything at all.
I expect by combining these two, I get what I want:
~L alice ~L bob ~L carol (^~L alice | ^~L bob | ^~L carol)
But that doesn't work.
I briefly tried using parens in a regexp way -- e.g.,
~L (alice|bob|carol)
but that doesn't seem to work at all. And when I try escaping the
parens just to see what happens, I get "Unmatched ( or \(".
I'm not sure whether I have a bug, an intractable problem, or a clue
deficiency. Any tips? What's the right way to approach this? Mailing
lists/aliases are not really a solution for this particular problem.
Thanks. Here's my mutt -v. I attached a mailbox that contains 8
messages: 6 that I want matched, 1 that is from Carol to Alice, Bob,
and Dave, and 1 that does not include Bob. (The last two should not be
matched.) Ignore the "patches applied" part. :)
Mutt 1.3i (2000-05-09)
Copyright (C) 1996-2000 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: SunOS 5.8 [using slang 10309]
Compile options:
-DOMAIN
+DEBUG
-HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK
+USE_IMAP +USE_GSS +USE_SSL +USE_POP -HAVE_REGCOMP +USE_GNU_REGEX
+HAVE_COLOR +HAVE_PGP -BUFFY_SIZE -EXACT_ADDRESS +ENABLE_NLS
SENDMAIL="/usr/lib/sendmail"
MAILPATH="/var/mail"
SHAREDIR="/opt/pkgs/mutt-1.3/lib/mutt"
SYSCONFDIR="/opt/pkgs/mutt-1.3/etc"
ISPELL="/opt/bin/ispell"
Patches applied:
Patch Name: mutt-1.1.12.dgc.krb5.2
+ URI: http://home.uchicago.edu/~dgc/mutt
+ Desc: Fix Kerberos 5 checking for pre-1.1 MIT in configure.in
Patch Name: mutt-1.1.12.skimo.exmhthread.1
+ Desc: Modify threading for exmh's (and others'?) oddball In-Reply-To:
Patch Name: mutt-1.3.dgc.xlabel.3
+ URI: http://home.uchicago.edu/~dgc/mutt
+ Desc: Add in-line status-bar editor for X-Label: header
Patch Name: patch-1.1.14.waf.compose_status.1
+ Desc: Add summary format for Compose menu
To contact the developers, please mail to [EMAIL PROTECTED].
To report a bug, please use the muttbug utility.
Re: Exclusive matching
On 2000.05.24, in [EMAIL PROTECTED], "David Champion" [EMAIL PROTECTED] wrote: I attached a mailbox that contains 8 messages: 6 that I want matched, 1 that is from Carol to Alice, Bob, and Dave, and 1 that does not include Bob. (The last two should not be matched.) Oops. *Now* I attached a mailbox. example.mbox.gz
Re: Exclusive matching
On 2000.05.24, in [EMAIL PROTECTED],
"David Champion" [EMAIL PROTECTED] wrote:
A look at the source code suggests that this is a misread, though, and
that "^" goes before any pattern component. Well, this pattern:
^~L alice | ^~L bob | ^~L carol
doesn't match anything at all.
I'm still curious about this, but read on.
On 2000.05.24, in [EMAIL PROTECTED],
"Mikko Hänninen" [EMAIL PROTECTED] wrote:
David Champion [EMAIL PROTECTED] wrote on Wed, 24 May 2000:
I briefly tried using parens in a regexp way -- e.g.,
~L (alice|bob|carol)
but that doesn't seem to work at all.
I didn't look into this deeply, but just to throw an idea out --
did you try something like:
^~L (alice|bob|carol)
That was one of the first things I tried, but as you noted below, that
makes Mutt treat the '|' as a pattern separator.
parens just to see what happens, I get "Unmatched ( or \(".
That sounds like a parson problem... Hmm, yes, if you escape the ()'s,
then you need to escape the |'s too, or else they will be seen as as
separating patterns, as opposed to separating expressions within a
single pattern.
OK. I didn't need to escape the parens at all, just the pipes. This
expression is exactly what I'm looking for:
~L alice ~L bob ~L carol ^~L (alice\|bob\|carol)
(I was hoping that the parser would change the meaning of '|' inside
parens -- I didn't think of "\|" because I wasn't looking for a literal
pipe.)
Now, suppose I'm Alice. I'd like to be able to remove the "alice"
parts of that and let $alternates cover it, but I don't see any way to
do that. Is there some way to get $alternates into the expression?
Should there be? I'm happy with a "yes" to either question. :)
Thanks, Mikko!
--
-D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: converting Date: header field to local timezone in pager?
On 2000.05.17, in [EMAIL PROTECTED], "David Roche" [EMAIL PROTECTED] wrote: I've searched all over the docs, and can't figure out how to get the pager to display all Date: header fields in time converted to the local timezone. Is this possible? This is not exactly what you describe below, but it achieves a similar effect: set pager_format="%S%T %C: %-16.16n [%[%y/%m/%d %H:%M:%S %Z]] %s" The "%[%y/%m/%d %H:%M:%S %Z]" is a date format string. In other words, some mails from the UK dispay dates like this: Date: Wed, 17 May 2000 11:09:03 +0100 While mails from the US West Coast (my local timezone) display like this: Date: Wed, 17 May 2000 07:51:46 -0700 (PDT) When displaying these two mails, I'd like to see: Date: Wed, 17 May 2000 03:09:03 Date: Wed, 17 May 2000 07:51:46 Or, better yet: Date: Wed, 17 May 2000 03:09:03 (11:09:03 +0100) Date: Wed, 17 May 2000 07:51:46 (07:51:46 -0700 (PDT)) How can I accomplish this? Thanks, David Roche -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: Doing netnews with mutt
On 2000.05.16, in [EMAIL PROTECTED], "Bennett Todd" [EMAIL PROTECTED] wrote: Ok, I've gotten so hooked on mutt that I'm wanting to use it for netnews. I know this has been discussed a lot, but as best I've been able to tell the focus has been on NNTP support for some reason --- even though mutt does email fine without talking SMTP. It does email fine without talking IMAP, too, but sometimes access to a remote message store is good. I'd much rather use mutt's IMAP mode than use mutt in conjunction with fetchmail. This is just a defense against your last statement, though, not a proclamation of opposition to what you're doing. That's actually a very interesting idea. So, on a related note: are there any other NNTP patches for mutt, besides Brandon Long's 0.95 version? I'd imagine that they'll never make it into the core, but I'm still interested. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: 2 IMAP questions again
On 2000.05.16, in [EMAIL PROTECTED], "Brendan Cully" [EMAIL PROTECTED] wrote: don't know which clients can make use of that yet). The best option is just to use IMAP always or never, probably. I don't think that's realistic, as long as non-IMAP access is possible, for some people. But I guess what I'm asking about can be done with a bit of limit code and a push. It's surprising how many calls our tech support line gets where callers are worrying about "DO NOT DELETE THIS MESSAGE" messages, asking whether they're viruses, etc. -- -D.[EMAIL PROTECTED] NSIT University of Chicago
Re: mutt 1.1.1 : make error
On 1999.12.01, in [EMAIL PROTECTED], "Thomas Roessler" [EMAIL PROTECTED] wrote: On 1999-11-30 21:23:01 +0100, J Horacio MG wrote: Then I `make clean', copy mutt-1.0/keymap_defs.h into mutt-1.1.1/, and `make' again, but: Don't do this. keymap_defs.h is auto-generated from the various OPS files; using a version from a different mutt version may lead to all kinds of problems. You may wish to try typing "make keymap_defs.h"; generally, this should work. I had this problem with mutt-1.1 on solaris 7. I used "make keymap_defs.h" and all was fine, but there does seem to be some error (in the configure process, I guess). -- -D. [EMAIL PROTECTED]"While a void is expressed in this recipe, I am struck NS/ENSA by its inapplicability to the bourgeois lifestyle. Networking Services How can the eater recognize that the food denied him Uchicago.Com is a tuna casserole and not some other dish?"
query_command for uiuc's ph/qi
I hadn't seen a query_command program for qi on www.mutt.org, so I
wrote one. (I know they're around, but I was blinded or something and
I missed them.) I particularly didn't know about the one on Brandon
Long's archive that handles multiple servers, but mine handles them
better anyway. :)
We don't have many mutt users here, but I haven't heard anything from
any of them, so I'll let all of you try it out anyway.
It's a perl script, I'm afraid. There's a nested hash at the top that
defines your server(s) and parameters that apply to them individually.
At uchicago.edu we have two standard servers, so this was kinda
necessary. You can turn it to your advantage, too: I put nwu.edu in my
copy, as well, since we're in the same general neighborhood.
The reason I think this is better, btw, are that 1) the awful nested
hash lets you set parameters for each server independently; 2) this one
is a little smarter about using the info available via `siteinfo' to
fill in blanks; and 3) it tries hard to give useful commentary on the
matches.
It doesn't require a client or the perl Net::Ph (or whatever) module.
--
-D. [EMAIL PROTECTED]"Tuna Casserole. Ingredients: 1 large casserole dish.
NS/ENSA Place [the dish] in a cold oven. Place a chair facing
Networking Services the oven and sit in it forever. Think about how hungry
Uchicago.Com you are. When night falls, do not turn on the light."
#!/opt/bin/perl
##
## [EMAIL PROTECTED], evil qi guy
##
###
## Configurable parameters:
## List all Qi servers to check.
## server = hostname of server ($)
## port= service/port, if not the default (csnet-ns/105) ($)
## fullname= field containing full name on this server ($)
## dfields = fields with descriptive text about person ([])
## capnames= do names need to be coerced into proper capitalization? ($)
## shownull= Show records with empty mailbox fields? ($)
@QISVRS = ( {
server = "ns.uchicago.edu",
port= undef,
fullname= "name",
dfields = \@INFOFIELDS,
capnames= 1,
shownulls = 1,
},
{
server = "alumni.uchicago.edu",
port= undef,
fullname= "name",
dfields = \@INFOFIELDS,
capnames= 1,
shownulls = 1,
},
# {
# server = "ns.nwu.edu",
# port= undef,
# fullname= "name",
# dfields = [qw(title department curriculum text)],
# capnames= 1,
# shownulls = 0,
# },
## UIUC is s l o w
# {
# server = "ns.uiuc.edu",
# port= undef,
# fullname= "name",
# dfields = [qw(title department curriculum text)],
# capnames= 1,
# shownulls = 0,
# },
);
## Fields to take commentary text from, in precedence order.
@INFOFIELDS = qw(
title
appointment
department
curriculum
text
);
## No more config after this.
###
use Symbol;
use Socket;
use Sys::Hostname;
($A0 = $0) =~ s:.*/::;
sub max {
my (@all) = @_;
my ($x);
$x = 0;
for (@all) {
$x = $_ if ($_ $x);
}
return $x;
}
sub QiConnect {
my ($host, $port) = @_;
my @pw;
my $sock = gensym;
my $port = getservbyname($port, 'tcp')
|| getservbyport($port, 'tcp')
|| getservbyname('csnet-ns', 'tcp')
|| getservbyname('ns', 'tcp')
|| getservbyport(105, 'tcp');
my $sin = sockaddr_in($port, inet_aton($host));
socket($sock, PF_INET, SOCK_STREAM, getprotobyname('tcp'));
connect($sock, $sin);
select $sock; $| = 1; select STDOUT;
@pw = getpwuid($);
print $sock "hello ", $pw[0], "\@", hostname, " [$0]\n";
while ($sock) {
last if (/^[2-9]/);
}
return $sock;
}
if ($#ARGV != 0) {
print "$A0: usage: $A0 query_exp\n";
exit 1;
}
($SEARCH = $ARGV[0]) =~ s/\s+/\*/g;
$nresults = 0;
for $svr (@QISVRS) {
@matches = ();
$Qi = QiConnect($svr-{server}, $svr-{port});
print $Qi "siteinfo\n";
IO: while ($Qi) {
last IO if (/^[2-9]/);
chomp;
($r, $n, $f, $v) = split(/\s*:\s*/, $_);
if ($f =~ /^maildomain$/) {
$svr-{maildomain} = "\@$v";
} elsif ($f =~ /^mailfield$/) {
Re: [wish] alternates_work
On 1999.11.11, in [EMAIL PROTECTED], "Sven Guckes" [EMAIL PROTECTED] wrote: I want an extra flag for work related mails so they wont show up as non-personal mails. And I want an extra pattern modifier for these so I wont have to use long regexp with limit commands. I have four jobs and a major identity crisis. I'd like to extend Sven's request to six flags, please. I don't see that's it's the mail agent's task to mark mail according to whatever roles the user splits them among in his mind. While I like marking my mail, too, it's not my mailer's job to facilitate this. If it chooses to do so, it must not make assumptions about these categories; it must provide a means of allowing me to define categories arbitrarily within the limits of its matching ability. This would mean implementing unlimited categories, with matching rules which are not limited exclusively to the destination address (using, say, mutt's general message-matching syntax), and with the ability to mark messages with more than just a particular letter in the status field. I use procmail to do it instead. -- -D. [EMAIL PROTECTED]"Tuna Casserole. Ingredients: 1 large casserole dish. NS/ENSA Place [the dish] in a cold oven. Place a chair facing Networking Services the oven and sit in it forever. Think about how hungry Uchicago.Com you are. When night falls, do not turn on the light."
Re: no such color
On 1999.11.06, in [EMAIL PROTECTED], "Wilhelm Wienemann" [EMAIL PROTECTED] wrote: i tell mutt to use color "default", but mutt tell me "default: no such color", why? for example "color error brightred default" Therefore you need 'ncurses' version 4.2 (the recent version is 5.0) or you have to compile mutt against 'slang'. Since version 4.2 'ncurses' is working with a 'default' color option. It's more complicated than this. I've tried all six of the following combinations. The 1.0pre4/slang configurations accept "default" as a color, and the 1.0 releases do not. COLORFGBG is set under all. 1.0pre4 ncurses-5.0 error 1.0pre4 slang-1.2.2 ok 1.0pre4 slang-1.3.9 ok 1.0 ncurses-5.0 error 1.0 slang-1.2.2 error 1.0 slang-1.3.9 error -- -D. [EMAIL PROTECTED]"[T]he traditional omelet form...is bourgeois. Today NS/ENSA I tried making one out of cigarette, some coffee, and Networking Services four tiny stones. I fed it to Malraux, who puked. Uchicago.Com I am encouraged, but my journey is still long."
Re: no such color
On 1999.11.06, in [EMAIL PROTECTED], "Rejo Zenger" [EMAIL PROTECTED] wrote: ++ 06/11/99 05:12 -0600 - David Champion: It's more complicated than this. I've tried all six of the following combinations. The 1.0pre4/slang configurations accept "default" as a color, and the 1.0 releases do not. COLORFGBG is set under all. I have mutt 1.0i and ncurses 4.2-50 running and default is working. Now it's working with 1.0 and slang-1.2.2. No idea what's changed, but I take it all back. -- -D. [EMAIL PROTECTED]"[T]he traditional omelet form...is bourgeois. Today NS/ENSA I tried making one out of cigarette, some coffee, and Networking Services four tiny stones. I fed it to Malraux, who puked. Uchicago.Com I am encouraged, but my journey is still long."
