Re: Setting From when replying
Dav Coleman <[EMAIL PROTECTED]> wrote: > > What I want is for mutt to set the From: field when I reply to a message > to the same address as the To: field in the original message. There is a 'reverse_name' option you can enable to do this. You will need to make sure that your 'alternates' setting matches all the different addresses you can receive mail as, so that Mutt can tell which To: lines refer to you, and which do not. Something like this should work: set alternates='^((dav|two)@abc\.com|[EMAIL PROTECTED]|[EMAIL PROTECTED])$' -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Save-hook question
Stewart V. Wright <[EMAIL PROTECTED]> wrote: > >fcc-save-hook ~A +People/%O.gz > > However, recently one of my correspondents has had their email name > changed to all capitals, so now rather than being saved in >People/personx.gz > mutt wants to create >People/PERSONX.gz Someone created a patch that will cause the following expanded text to be lower-cased if you use the "_" prefix. Like so: fcc-save-hook ~A +People/%_O.gz However, I cannot recall if this is standard behavior now, or if it still requires a patch. The behavior *is* in the version that I'm using (or at least, it's in the manual), but I am using the development version of Mutt, 1.1. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: e-mail address
Nguyen-Dai Quy <[EMAIL PROTECTED]> wrote: > > I would like to add automatically all email addresses into my "address > book". How ? Since there is no address book, there's no way to do what you want. The closest thing Mutt had is a list of aliases, which are basically short names that can be expanded to longer addresses. If that fits your purpose, then you can use the "a" command to add each message's address to your list of aliases. The following lines in your ~/.muttrc might help you keep them in a separate file for editing: Aliases set alias_file=~/.aliases # Set file to add aliases to source ~/.aliases # And read it in -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: regexp help?
Jim B <[EMAIL PROTECTED]> wrote:
>
> I believe this can be corrected by a well-written regular expression, but
> I'm not so good at that so I'm wondering if anyone can help.
This won't work with Mutt as it's currently coded, because Mutt assumes
that the reply_regexp matches something at the *beginning* of the
string, and takes anything following that match as the "real subject."
Mutt uses code like this:
if (e->subject)
{
regmatch_t pmatch[1];
rfc2047_decode (e->subject, e->subject, mutt_strlen (e->subject) + 1);
if (regexec (ReplyRegexp.rx, e->subject, 1, pmatch, 0) == 0)
e->real_subj = e->subject + pmatch[0].rm_eo;
else
e->real_subj = e->subject;
}
The pmatch[] array contains a list of matches to subexpressions within
the regular expression. pmatch[0], used here, matches the entire
regular expression. As written, the "real subject" is taken to be
whatever comes after the reply_regexp. So...
> Subject: RE: [GeneralService] Word1 Word2 [IMS21250368242002]
>
> set reply_regexp = "^(re|aw):[ \t]*[ \t]\[[a-z0-9]*\]"
>
> but that apparently doesn't work.
Nope, that won't work, because the reply_regexp matches the entire
string, leaving no "leftover" text for the "real subject".
By the way, something to watch out for in .mutrrc's:
set reply_regexp = "^(re|aw):[ \t]*"
This doesn't do what you think it does; Mutt sees the "\t" as simply
"t", because backslashes are parsed within double-quotes. So the regexp
comes out as "^(re|aw):[ t]*", and so a subject like "Re: Tuesday" comes
out with a real subject of "uesday". :)
Maybe there's a way to get middle-matching of subjects; I'll have to
play with it.
--
David DeSimone | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED] | that there is no man really clever who has not
Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson
UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: regexp help?
David T-G <[EMAIL PROTECTED]> wrote: > > Mutt regexp gurus: Is specifying the A-Z necessary if we don't care > about the case? If we do and have to use A-Z, will the re|aw exp > match upper case versions? Specifying any capital letter in your regexp will cause Mutt to match the regexp case-sensitively. If there are no capital letters in the regexp, it will be performed case-insensitively. So a regexp like "^(re|aw): [A-Z]*" will fail to match "Re: ", because the "A-Z" part causes a case-sensitive match. If the regexp was "^(re|aw): [a-z]*", it would match. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: checking multiple boxes.....
Jason Helfman <[EMAIL PROTECTED]> wrote: > > When I quit any program, I may get a msg that says "You have mail in > /var/spool/mail/$USER So what does this have to do with Mutt? > Is their a way for get sendmail to check the other boxes. I'm only in > a console window, so this would be helpful. This is a function of your shell. Most of them will check multiple mailboxes, if you tell them to. For instance, in tcsh: mailThe names of the files or directories to check for incoming mail, separated by whitespace, and optionally preceeded by a numeric word. Before each prompt, if 10 minutes have passed since the last check, the shell checks each file and says `You have new mail.' (or, if mail contains multiple files, `You have new mail in name.') if the filesize is greater than zero in size and has a modification time greater than its access time. If you are in a login shell, then no mail file is reported unless it has been modified after the time the shell has started up, in order to prevent redundant notifications. Most login programs will tell you whether or not you have mail when you log in. If a file specified in mail is a directory, the shell will count each file within that directory as a separate message, and will report `You have n mails.' or `You have n mails in name.' as appropriate. This functionality is provided primarily for those systems which store mail in this manner, such as the Andrew Mail System. If the first word of mail is numeric it is taken as a different mail checking interval, in seconds. Under very rare circumstances, the shell may report `You have mail.' instead of `You have new mail.' In ksh (and probably bash): MAIL If this parameter is set to the name of a mail file and the MAILPATH parameter is not set, the shell informs the user of arrival of mail in the specified file. MAILCHECK This variable specifies how often (in seconds) the shell checks for changes in the modification time of any of the files specified by the MAILPATH or MAIL parameters. The default value is 600 seconds. When the time has elapsed the shell checks before issuing the next prompt. MAILPATH A list of file names separated by colons (:). If this parameter is set, the shell informs the user of any modifications to the specified files that have occurred within the last MAILCHECK seconds. Each file name can be followed by a ? and a message to be printed, in which case the message undergoes parameter and command substitution with the parameter $_ defined as the name of the changed file. The default message is you have mail in $_. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Printing Problem in Mutt 0.91.1
Anup N. Patel <[EMAIL PROTECTED]> wrote: > > I'm using Mutt Version 0.91.1 and am having trouble printing. I tried > setting the "set print_command = "lpr -Plp1", but mutt gives me the > following error: "print_command: unknown variable" What is the > correct configuration variable. I think the old name for this variable was "print_cmd". Try using that instead. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: save as sorttes
Lars Thon <[EMAIL PROTECTED]> wrote: > > On Wed, Jan 19, 2000 at 07:36:52PM -0800, Lars Thon wrote: > > Is there a way to make Mutt save a mailbox in whatever is the > > current sort order, or do you happen to know some other program that > > will permenantly sort a mailbox? > > Mutt always saves messages in the order they were received. I am not > aware of any tool which would let you do that. I thought that Mutt could be used for this purpose, by tagging all the messages in the mailbox, and then saving them to a brand-new mailbox. Mutt will save the messages in the order they appear in the index. Then you can simply rename the new mailbox to the same name the old one had. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: save without delete
Brett Neely <[EMAIL PROTECTED]> wrote: > > How can I save an email without automatically causing its deletion? Use (C)opy instead of (s)ave. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: attaching PDF file
Boryeu Mao <[EMAIL PROTECTED]> wrote: > > Sorry about my opaque query - the problem is that the PDF file that > gets attached (with 'a' or -a) becomes unreadable when received. Most likely the problem is that your Mutt doesn't know what content-type to apply to the PDF data file, so it gets attached as type "application/ octet-stream", which the remote MUA doesn't know what to do with. There should be a "mime.types" file that came with Mutt. You should install it in a place where Mutt can find it, or in ~/.mime.types if you are not the system administrator. It has mappings for various file types to content-types. For instance: application/pdf pdf -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: problem with bounce
Lars Hecking <[EMAIL PROTECTED]> wrote: > > I agree with and understand everything you wrote above, but according > my copy of the bat book (1st ed only), the F flag in the F equate > means "Need From: in header", i.e. concerns From: and Resent-From: > headers, not the "From " mbox separator. I couldn't find my Bat Book, and my memory is faulty; my apologies. I looked it up on the web: http://www.sendmail.org/~ca/email/doc8.8/op-sh-5.html#sh-5.4 and discovered that for procmail delivery, you probably want the "f" option (The mailer wants a "-f from" flag), and you probably even more want the "n" option (Do not insert a UNIX-style "From" line on the front of the message). -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: problem with bounce
Lars Hecking <[EMAIL PROTECTED]> wrote:
>
> > Whatever MDA you are using, is at fault here. It has put the message
> > into your mailbox, with invalid headers. If you fix the MDA, the bounce
> > problem will go away.
>
> Possibly procmail or formail. But although escaping of bogus \nFrom
> lines is explained in the man pages, I cannot see how this possibly
> applies to this case.
Then think on this:
The message is placed in your mailbox looking like this:
From whoever Jan 21 09:10:11
>From some-sender Jan 21 09:10:04
Received by some-mailer at Jan 21 09:09:49
Recevedd
From: some-sender@somewhere
To: whoever
Subject: Test Message
This is a test message.
The first "From " line is the message separator for mbox messges. The
next line is the "original" message separator. A message should NOT
have a message separator until it is being placed for final delivery.
Procmail knows this, so when it tries to put the message into your
mailbox, it escapes the bogus separator and inserts its own. However,
this does not really make an RFC-compliant message. We'll see what
effect this has, later.
So, when Mutt goes to read the message, it wants to separate the message
into headers and body. It does this by scanning down the header section
until a non-compliant line is reached, which is usually the blank line
at the end of the header section. Mutt, you see, is a "smart" mailer
and has seen such bogusly-written messages before. There is a comment
to that effect in the source:
/* some bogus MTAs will quote the original "From " line */
if (mutt_strncmp (">From ", line, 6) == 0)
{
loc = ftell (f);
continue; /* just ignore */
}
So, Mutt ignores that. But that is simply Mutt's behavior. Other
programs touch mail messages, so their behavior may be different.
So anyway, Mutt shows the message correctly. The problem comes when you
bounce the message. During a bounce, the message text, exactly as-is,
will be piped to $sendmail, and sendmail will take that message and send
it to the intended bounced recipient. However, sendmail also knows what
constitutes an RFC-compliant message, but it apparently does NOT have
the above bit of code, like Mutt does... It sees the ">From " line in
the message, and says, "Hmm, that's not RFC-compliant, it must be part
of the message BODY!" And so everything below that is considered text
of the message, and the message essentially has NO headers. Then, since
there are no headers, sendmail automatically comes up with some basic
headers, including yourself as the From: header, and so on.
So, it is the original mis-formatting of the message that is at fault.
I suppose Mutt *could* try to get a little smarter, and not pass such a
bogus message to $sendmail, but really, isn't it best to fix the ROOT
cause of things? Your MDA is misconfigured, and that causes this whole
problem.
I imagine the problem is in the sendmail config, something like this:
Mlocal, P=/usr/bin/rmail, F=lsDFMAw5:/|@m, S=10/30, R=20/40,
T=DNS/RFC822/X-Unix,
A=rmail -d $u
This is my particular setting for the "local" MDA, in my sendmail.cf.
If I remember my sendmail configuration rightly, it is the "F" option in
the "F=" section which determines that a "From " header will be added to
the message before it is piped into the MDA. Now, for your case, you
probably have P=/usr/bin/procmail, and since procmail creates its own
message separator, having sendmail add it is superfluous; in that case,
removing the "F" might be the way to handle this.
At any rate, since this can be fixed at your site, perhaps it is best to
do that, rather than coerce Mutt to adapt to your broken mail system.
--
David DeSimone | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED] | that there is no man really clever who has not
Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson
UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: problem with bounce
Raju K V <[EMAIL PROTECTED]> wrote: > > But when I bounce a message, the recepient gets the mail with broken > headers. Example: > > I am bouncing a mail with headers: > - SENT HEADERS - > From smtp Wed Jan 12 12:38 IST 2000 remote from tagore > >From [EMAIL PROTECTED] Tue Jan 11 22:55:10 PST 2000 > Received: from kmglmail.wipsys.soft.net (kmglmail.wipsys.soft.net [164.164.26.11]) The headers in the message, as stored in your mailbox, are wrong. The original envelope separator "From " has been changed to ">From ", which is not a valid header. Apparently, when you bounce this message through sendmail, it notices that this header is wrong, and breaks the headers at that point, then generates totally new headers based on the sender (you). Whatever MDA you are using, is at fault here. It has put the message into your mailbox, with invalid headers. If you fix the MDA, the bounce problem will go away. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: plus signs
Jason Helfman <[EMAIL PROTECTED]> wrote: > > In the body of my msgs I have some + signs that have a white box > around them. What is this an issue of? Allow me to read some more from the manual to you, so that you need not send further huge posts to the list: 6.3.75. markers Type: boolean Default: yes Controls the display of wrapped lines in the internal pager. If set, a ``+'' marker is displayed at the beginning of wrapped lines. Also see the ``smart_wrap'' variable. For extra credit, find the "color markers" section in the manual. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: can't filter sent emails to sent box
Jason Helfman <[EMAIL PROTECTED]> wrote: > > I am very new to mutt, and by emailing back and forth with fellow mutt > users, documentation and the like, I am unable to figure out -- based > on my .muttrc file --- why email I send out want to go to the record > of the name it is sent to...for instance, if i send an email to > [EMAIL PROTECTED] If you are new to Mutt, perhaps you would consider reading its manual. It has a lot of good information about the program. 6.3.156. save_name Type: boolean Default: no This variable controls how copies of outgoing messages are saved. When set, a check is made to see if a mailbox specified by the recipient address exists (this is done by searching for a mailbox in the ``folder'' directory with the username part of the recipient address). If the mailbox exists, the outgoing message will be saved to that mailbox, otherwise the message is saved to the ``record'' mailbox. Also see the ``force_name'' variable. 6.3.43. force_name Type: boolean Default: no This variable is similar to ``save_name'', except that Mutt will store a copy of your outgoing message by the username of the address you are sending to even if that mailbox does not exist. Also see the ``record'' variable. 6.3.146. record Type: path Default: "" This specifies the file into which your outgoing messages should be appended. (This is meant as the primary method for saving a copy of your messages, but another way to do this is using the ``my_hdr'' command to create a Bcc: field with your email address in it.) The value of record is overridden by the ``force_name'' and ``save_name'' variables, and the ``fcc-hook'' command. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: ansi colors without X
Ronny Haryanto <[EMAIL PROTECTED]> wrote: > > Please correct me if I'm wrong You're wrong. ;) > I think you need to compile aginst the S-Lang library to use default, > you can't use [n]curses. The latest versions of ncurses do allow the use of the color "default", and Mutt will work with this. So upgrading to Slang or upgrading ncurses will do the trick. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: mbox v inbox
Bram Shirani <[EMAIL PROTECTED]> wrote: > > Ok...I've noticed that mbox and inbox are two separate entities, at > least the way I've got mutt configured. What I would like to do is > get rid of the "inbox" (where new messages are automaticlly sent) and > consolidate them into mbox I suggest you do the opposite, and consolidate all your messages into your "inbox". Add a "set move=no" command to your ~/.muttrc file, so that Mutt will stop moving the messages into "mbox". Then, you'll always find your new mail in your "inbox" and don't have to go looking for it. Mutt defaults to looking at your "inbox" whenever you start it. To get your message out of "mbox", open that folder in Mutt, tag all the message (T, all), then tag-save them to the folder called "!" (which is a synonym for your "inbox"). Press ";" to begin a tagged operation, then "s" to save, and enter "!" as the folder to save the messages to. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Colour via telnet/ssh
Chris Green <[EMAIL PROTECTED]> wrote: > > However, I may not have made myself clear, but running slrn across the > ssh connection I *do* get colours, whereas running mutt across the > same link I *don't* get colours. You made yourself clear. What perhaps was not made clear to you is that, unlike slrn, Mutt is a rather pedantic application, and does not attempt to work around broken terminfo databases. Slrn has the -C option to force color, even if the terminfo database fails to mention color. Mutt has no such option, because Mutt believes that you should fix your terminfo database instead of trying to teach every application about colors. It is, indeed, the better solution, and Mutt simply takes a stand that forces you to fix the root problem, rather than treat the symptoms. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Colour via telnet/ssh
Holger Eitzenberger <[EMAIL PROTECTED]> wrote: > > Please correct me if i am wrong but i think its mostly your ssh-client > (-- it has to understand ANSI colors --) which is responsible for the > colors. This is true for Win/Mac type platforms, where the ssh client generates the text window and VT100 emulation as well. But on Unix, which I believe the original poster is using, the xterm generates the windows, colors, etc, and ssh is merely a communication conduit, with no need to understand any sort of ANSI. I believe the other posters in this thread are correct; the termcap/ terminfo database on the remote computer does not contain color information. There is a FAQ on this topic at http://www.fefe.de/muttfaq/faq.html#no-color -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: multiple mailboxes (how to check for mail in them?)
Jan Fedak <[EMAIL PROTECTED]> wrote: > > Now, in mutt manual I've found that if I hit TAB, I'll be transferred > to next mailbox with any new mail. Perhaps you mis-read the manual; Mutt does not do this, as far as I know. TAB takes you to the next new message in the current folder; that's all. > However, if I push 'c' (change mailbox) and there's a new mail in some > of them, I'm offered its name on the command line. That's how it should work. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: just a 'lil problem with Mail-FollowUp-To: I need help with...
Mark Mielke <[EMAIL PROTECTED]> wrote: > > I KNOW what the documented behaviour for mutt is. What I was > explaining was why I always use 'g'roup reply instead of 'L'ist reply. I have also more-or-less abandoned the List-Reply function within Mutt. I participate in a few mailing lists which mostly consist of pleas for help from all over. Most of the users posting are not subscribed to the list; they merely want help from the list members. In the old days, I used to believe that one should always subscribe to a list before posting to it, but I no longer believe that; the number of lists is simply too staggering, to expect such behavior from most people. At any rate, I used to use List-Reply for everything. But what I found was that my well-intentioned posts were reaching the subscribed list members just fine... but those people didn't really need to see the post; it was mostly intended for the original poster, who received nothing from me. So now I use Group-Reply for everything. On lists like this one, where nearly everyone uses Mutt, and Mail-Followup-To headers can be trusted, it works quite well. On most other lists, I either send a reply to everyone who needs it, or send an occasional duplicate to a list subscriber. And no one complains. > 'L'ist reply doesn't do what I want when I want to reply to a list. It actually took me quite a while to realize why people weren't seeing my replies. Now that I think on it, List-Reply doesn't seem as useful as I had once thought. > I want a SMART 'L'ist reply which generates it the most perfectly it > can in the significant majority of the cases. > > Is that too much to ask? :-) There's no way for Mutt to know who subscribes or doesn't subscribe to a list. The best solution is the MFT header, but it only works well on a list like this one, where everyone uses it. I can't think of an intelligent solution; can you? -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: New Mail Sent to different mailboxes -> bypassing MTA
Scott V. McGuire <[EMAIL PROTECTED]> wrote: > > Any ideas on not using a full blown MTA for outgoing mail? It seems > like overkill to run sendmail (or even qmail) on a single user system > when all I need is a program to look like sendmail but immediately > send mail to my isp's smtp server. What if your ISP's mail servers are down? Then you can't send mail anymore, until they come back. If you run a local MTA, it can bypass the ISP's servers, and go directly to the remote mail server. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Output when nothing changes
Larry Lipstone <[EMAIL PROTECTED]> wrote: > > I find with my mutt-1.0i running on UnixWare 2.1.3, with TERM=dtterm, > every time the timeout (or whatever) period expires and it checks for > new mail, the program emits a "make cursor visible", then stat()'s the > mail drop, then sends "make cursor invisible". > > This causes my poor (yet expensive) ISDN connection to demand-dial on > the timeout (or whatever) interval, even when I'm receiving no new mail. I can't see how this behavior would cause your modem to dial out and initiate a connection. I can see how it would keep a connection open when it would otherwise time out. Why do you think it's desirable that the connection time out? Then you won't be notified of new mail anymore. And if you don't care that new mail is coming in, then why are you wasting ISDN money by keeping the connection active? I'm sorry that I don't understand your situation. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Exiting without applying deletions (was: Applying deletions without exiting)
Brendan Cully <[EMAIL PROTECTED]> wrote: > > BTW, IMAP handles both sides of this. Just don't purge - messages will > keep their D flags... The last time I checked, Mutt doesn't send flag-changes to the IMAP server until you quit... so the messages can't keep their D flags, because Mutt never sent them. Has that changed recently? -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: problem with deleting / syncing
Sebastian Helms <[EMAIL PROTECTED]> wrote: > > When I mark a message for deletion and quit the mailbox, and later > enter it again, the deleted message still is in there. The status has > changed back to not-delete. Perhaps you have 'set delete=no'? There are four settings for the variable, but only 'yes', 'ask-yes', and 'ask-no' make sense. If you set it to 'no', you will never be able to delete a message from a folder. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Exiting without applying deletions (was: Applying deletions without exiting)
Rich Lafferty <[EMAIL PROTECTED]> wrote: > > It seems that Pine can keep track of messages flagged as deleted, > between sessions (it adds a header, 'X-Status: D'), so you can mark a > bunch of messages as deleted and they stay marked until you finally > expunge/sync the mailbox. Mutt supports one side of this... if the mailbox contains messages with the 'X-Status: D' header, they will indeed be pre-marked for deletion upon entering the folder. I have a procmail script which marks spam messages in this fashion. However, Mutt has no support for writing a mailbox in this fashion. > Have I missed an option to do this in mutt, or is it not possible? > Was there a reason, or has it even been noticed/considered? (I sure > hadn't noticed it ;-) Why do people always insist that someone give a specific reason why something hasn't been done yet? As if everyone had already considered every possibility, and each was selected and rejected for various criteria... :) In this case, the idea has come up on this list, and several people thought it was a good idea, but nobody actually wrote any code, so nothing actually happened. That's how open software usually is. :) -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Mail User Agent (mutt)
Suporte SCO <[EMAIL PROTECTED]> wrote: > > # mutt > dynamic linker : mutt : error opening /usr/local/lib/libncurses.so.4 > Killed Did you look for the dynamic library at /usr/local/lib/libncurses.so.4 ?? It's obviously not there, so... go find it. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: procmail mailing list URL?
Paulius Danielius <[EMAIL PROTECTED]> wrote: > > To: [EMAIL PROTECTED] > From: Paulius Danielius <[EMAIL PROTECTED]> > Subject: procmail mailing list URL? > Date: Sat, 2 Dec 2000 01:40:39 +0200 Interesting date header... you have jumped very far in the future! -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: pgp sign
Attila Csosz <[EMAIL PROTECTED]> wrote: > > I'm wondering about how can be the length of the pgp sign of a small > and a very large mail is equal. Which part of the message will be > encrypted? As I understand it, a PGP signature is not an encryption of the message, but an encryption of an MD5 (or SHA) *digest* of the message. This is like a checksum, though much more sophisticated, but it is always the same size. Therefore, the encryption of the message digest will also be the same size, always. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: priority header
Thomas Roessler <[EMAIL PROTECTED]> wrote: > > I was actually thinking about flagging messages as important (the > "!" in the index). That can also be done using procmail to modify the Status: header according to the headers that it notices when the message is received. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: error during configure
Caldwell Warley <[EMAIL PROTECTED]> wrote:
>
> Recently I downloaded mutt 1.0 and tried the configure command. This was the result:
>
> loading cache ./config.cache
> checking for a BSD compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking whether make sets ${MAKE}... no
> checking for working aclocal... missing
> checking for working autoconf... missing
> checking for working automake... missing
> checking for working autoheader... missing
> checking for working makeinfo... missing
> checking host system type...
That was the entire result? It just stopped after checking system type?
I don't think I've ever seen such a thing.
> Now my .muttrc-local file (from version 0.9x) is a total of 0 kb. I
> don't know if the two are related, but for some reason I can use mutt
> fine.
If you are able to use Mutt without any trouble, then what exactly is
the problem that you are reporting? Your subject says "error during
configure" but there are no errors above. Most people don't have the
autoconf tools installed, so "missing" is the proper thing to print out.
> Also, is it correct that 'us' versions DO NOT support PGP?
Indeed.
--
David DeSimone | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED] | that there is no man really clever who has not
Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson
UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Avoid a portion of the reply
Michael Elkins <[EMAIL PROTECTED]> wrote:
>
> #!/usr/bin/perl
> while (<>) {
> last if /^---/;
> print;
> }
This is a wonderful idea, but the above script could be dangerous...
it'll cut off any message to the list, with a row of dashes in it:
---
Better to search for an exact match, such as:
last if /^---$/;
Anyway, you get the idea. Gotta watch those regexp's.. :)
--
David DeSimone | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED] | that there is no man really clever who has not
Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson
UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: save-hook list ignored after upgrade to 1.1.1i
Mark J. Bynum <[EMAIL PROTECTED]> wrote: > > Ever since I upgraded to development version 1.1.1i I can't seem to get my > save-hook to work right. List processing has changed on Mutt 1.1. > fcc-save-hook ~l ~/Mail/lists/%B > fcc-save-hook '~l' ~/Mail/lists/%B > fcc-save-hook '~l' =/lists/%B The ~l pattern matches "subscribed" lists only. You probably want to change all your "lists" commands to "subscribe" commands, anyway, to maintain previous behavior. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: deleted messages and arrows and key sequences
David T-G <[EMAIL PROTECTED]> wrote: > > I was trying to figure out a way to get the arrow keys to behave like > that, but I couldn't find the symbol for a shifted arrow :-) I'm sure > the key code/sequence exists, so ... There is no keycode for a shifted arrow. A standard VT100 terminal won't generate a different code for shifted arrows, so xterm's and other vt100 emulators won't generate them, either. You might have fun with resources and such to get such a key to be generated, but I don't know if it's worth it. :) -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: How to save to a new mailbox in a folder?
Chris Green <[EMAIL PROTECTED]> wrote: > > I have navigated down a couple of levels and see the mailbox I want to > save to doesn't yet exist, how can I say "save the message in this > directory with a new mailbox name ''"? Use the command, bound to "N" by default. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: window resize bug?
shawn a. <[EMAIL PROTECTED]> wrote: > > startup mutt, type a !vim (it also works when I hit a m), when > vim starts up resize the XTerm's window for a bit, this Is where the > bug happens for me -- mutt's interface overtakes vim but vim is still > running. its like vim and mutt are both trying to be the head app, it > is pretty weird. This is a signal-handling bug in your shell. When Mutt launches the editor, it is very careful to set up the signal handlers for all signals that could come in. However, the process tree goes something like this: mutt sh -c 'vim' vim So, the direct child of Mutt is sh, and the editor runs as a child of sh. What happens is that the intermediate 'sh' messes up the signal handlers. It shouldn't do that, and most shells don't, but there are apparently some buggy versions that do. When you resize your xterm, a SIGWINCH signal is sent to all the processes running in that window. That means Mutt, sh, and Vim all get the signal. Mutt and Vim handle it properly. Sh should ignore it, but it fails, and instead, sh exits completely, leaving vim still running as an orphaned process, where Mutt can't see it anymore. Mutt thinks that the editor has finished, so it resumes processing, but the editor is still running, and they fight over the terminal. So... What to do? Well, use a different shell. Upgrade your /bin/sh to a more recent version. Or, if you have another shell to use, that is /bin/sh compatible, use that, by re-configuring Mutt with the --with-exec-shell option. Try /bin/ksh or /bin/bash instead. As a last resort, you might try set editor="exec vim" This will cause the sh process to replace itself with the editor. That gets the buggy shell out of the way, but since the shell is going to be used to launch other commands from Mutt, too, you would be better off with a non-buggy shell instead. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: pgp/gpg
Alexander Dvorak t2069 <[EMAIL PROTECTED]> wrote: > > I have read the notes on pgp in the doc directory, but I still wonder > in which way the pgp (particularly the gpg) support was improoved ? As near as I can tell, PGP support was changed to be more flexible, so that any command that might be sent to PGP, or another encryption program, can be formatted and scripted using the command variables, instead of being hard-coded into Mutt. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Multiple POP accounts and personalities...
Chris Green <[EMAIL PROTECTED]> wrote: > > > Anyone else wanting additional features should use IMAP. > > But there lies the rub - 99% of users of MUAs DON'T HAVE THAT > CHOICE!!! We can't just "use IMAP", the choice isn't there! Then MAKE it happen! You are here, trying to push Mutt into conforming to an ill-fitting standard, simply because that's all your ISP offers you. Why aren't you, instead, putting this same pressure on your ISP, telling them that IMAP is what you need? Why does Mutt have to bend over backward for you? You presumably pay money to your ISP; you should get some decent service from them. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: problem with save-hook
Robert Chien <[EMAIL PROTECTED]> wrote: > > Try this instead: > > save-hook '~C linuxsa*' +linux Is the '*' there so that you can match 'linuxs', 'linuxsa', 'linuxsaa'? That's what it will do for you. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: problem with save-hook
Andrew O'Callaghan <[EMAIL PROTECTED]> wrote: > > save-hook linuxsa +linux > > I assumed this was going to save any mail that contained "linux" in > the To: field, into my ~/mail/linux mailbox. Since you know you want to match "linuxsa" in the To: field, go ahead and use that as your pattern: save-hook '~t linuxsa' +linux Since you might have some posts that are CC'd to that address instead of TO that address, you might find the ~C expression a better match: save-hook '~C linuxsa' +linux If this doesn't work, you might want to check and see if you have some other save-hook that might be matching sooner; save-hooks are examined in the order they are defined, and the first one that matches, is the one used. If you have a 'save-hook ~A' hook defined early on, none of the later hooks will matter! -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Happy with mutt, but...
Zsombor Gergely <[EMAIL PROTECTED]> wrote: > > This is a call for help! The problem is still unresolved What is the problem? > I inserted set allow_8bit and set charset="iso-8859-2" into .muttrc, > but nothing happened. What was supposed to happen? What happened instead? > I see everything correctly as I write it. Then what is wrong? > To be able to read my own messages, I have to encrypt them to myself. > I do it by adding a my_hdr bcc line to .muttrc, but feel that this is > not the best (and most elegant) way, since I send it over the network > to myself. I think you handle this by adding the command "encrypt-to 0x" in your .gnupg/options file. > Come on men, I do not belive that nobody uses pgp/gpg with mutt! How > do you do this? I use GPG with Mutt, but I am not doing it correctly. :) I still have some things that don't seem to work right (such as encryption and signing). It does appear to be verifying signatures, although there is one recipient whose signatures send GPG into an infinite loop, as near as I can tell. But that's not Mutt's problem. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Multiple POP accounts and personalities...
Edmund GRIMLEY EVANS <[EMAIL PROTECTED]> wrote: > > I haven't yet encountered an ISP POP3 server that doesn't do TOP. > I've only found one that didn't do UIDL. So would you have mutt use, or not use, the TOP command, and the UIDL command? > Note that fetchmail quite happily uses "TOP n 99" instead of "RETR > n" to retrieve e-mail. According to the comments in fetchmail's > pop3.c, this method very rarely fails. (I saw a case recently where > it did fail, but this was because the server had a buggy > implementation of TOP, not because it didn't implement TOP.) See, now we get to the case of why users are pointed to fetchmail: Because fetchmail has been bloated, er, I mean, specifically written to understand these buggy servers and try its best to deal with them. Trying to add this POP3 support to Mutt, you're going to run into the same problems, and probably get buried under user complaints about how things don't work just the way they want them to. I think the Mutt developers are shying away from POP3 support on two grounds: First, on a somewhat technical ground, since POP3 is not a very good protocol, and the only reason everyone wants to use it is that it's so ubiquitous. If users could only put pressure on their ISP's to get IMAP servers installed (which is not a very difficult job for an administrator to do!), then they wouldn't need to be demanding POP3 support from Mutt! Second, on a political ground, once Mutt claims that it will support POP3 mailboxes in this form, users will start to whine and complain because of all the buggy implementations of POP3 out there. The Mutt developers don't really enjoy listening to complaints. I wonder just how many the tkrat, balsa, and other MUA's get... -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Multiple POP accounts and personalities...
Ronny Haryanto <[EMAIL PROTECTED]> wrote: > > Some people doesn't have permanent internet connection, and it even > costs them by the minute. Therefore selective downloading could make > sense. Certainly. I have to dial up to the Internet myself. Fetchmail is configured to only poll POP servers when I am actively connected, and while I don't have it configured that way, it can be told to skip messages that are beyond a certain size. Thus, the desired behavior can be easily automated with fetchmail. That's really the main reason that Mutt's POP3 support is so lame: Because fetchmail does it better, so there's no point in doing all the work to improve Mutt's support. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Multiple POP accounts and personalities...
Chris Green <[EMAIL PROTECTED]> wrote: > > I personally think it's a pity that mutt doesn't accomodate POP3 users > a bit more. The fetchmail/procmail approach has one _major_ missing > feature, it's not interactive and so can't allow the user to decide > which mails to download from the POP3 server and, independently, which > mails to delete from the server. As long as I've been using mail on the Internet, I've grown accustomed to mail just "showing up" in my account, without needing to worry about how it got there. Fetchmail's background fetching of POP mail fits very well into this model, whereby mail simply appears magically in my mailbox. I'm not sure what it is that teaches people to think otherwise. > This can only be provided by an MUA interactively and are very useful > to anyone who reads mail on a POP3 server from different machines. What you really want is IMAP, not POP3. In fact, Mutt supports IMAP quite well in the development versions (1.1+), and it gives exactly the sort of interactivity that you seek. That is, in fact, what the IMAP protocol was designed for. The POP3 protocol was never designed to be an interactive protocol at all. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: index colors
Eugene Lee <[EMAIL PROTECTED]> wrote: > > > Is there anyway to get different colors in the index for "From" and > > "Subject" ? > > color header magenta default ^(Subject|To|Date|From): That colorizes the headers in the pager, but I think he was asking about the index display. Such as, can the "From" address and the "Subject" portions of the display, be put in different colors? The answer is NO. This has been lovingly termed "the rainbow effect," as far as features that users think that they want. I believe that, long ago, someone did implement this in an old version of Mutt, and he reported that it looked awful. So it was never folded into Mutt. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: color problem
Eugene Lee <[EMAIL PROTECTED]> wrote: > > : set quote_regexp="^([ \t]?[ \t]?[>:|])+" > > I'm curious, I don't quite understand the logic behind setting your > quote matching to this kind of pattern instead of using the default: > > set quote_regexp="^([ \t]*[>|#:}])+" Hmm, I didn't know that my regexp was so close to the default. You're right, the default will do the right thing, but in this case, the original poster was using Sven's muttrc, which has this very simple setting: set quote_regexp="^> " This regexp will always match the same length of text, so it will only recognize one quote level, or none. The chief difference between my regexp and the default, is that mine gives fewer false-positives. If someone sends me a nice ASCII-drawing chart of some kind, Mutt doesn't go crazy colorizing it. :) -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: color problem
George Georgalis <[EMAIL PROTECTED]> wrote: > > >color1 > >>color2 > >>>color1 > >>color2 > > They display in different colors in vim, but they are all the same in > the viewer? For me, they show up in different colors. You need two things to make this work: 1. Some colors defined for multiple quote levels 2. A proper quote_regexp that will match repeated quote levels properly Here's my settings for (1): color quoted green black color quoted1white black color quoted2brightred black color quoted3magenta black color quoted4red black And here's my setting for (2): set quote_regexp="^([ \t]?[ \t]?[>:|])+" Mutt will notice and colore more than five levels of quoting; it will simply re-use the colors again, if I remember rightly. The quote_regexp format is very important. It must match *only* the text at the front of the line, that forms the "quote" section. If it ends up matching the entire line, then all quotes will appear at the same "level." The reason for this is that Mutt looks at the *length* of the string that matches the regular expression. Each time a new length is seen, it is treated as a new level of quoting. Note, longer lengths are not treated as deeper levels, just *different* levels. Have fun. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: PGP/GPG
Sean Rima <[EMAIL PROTECTED]> wrote: > > The problem is the fact that there are a few people on the Mutt list > who use PGP2 and PGP5. These keys are not able to be used in GPG > AFAIK. >From what I have read, GPG can be configured or built with external module support, so that it can read and use these RSA and IDEA based message formats. However, I haven't really found any good instructions for building such a version of GPG. There are some nice files in the "contrib" directory, but I don't know how to put them together to make it work. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: flag 'A' for multiple attachments
Sven Guckes <[EMAIL PROTECTED]> wrote: > > I think this was done as you'd see the flag on almost all mails - even > thought they'd only have just a single one which might just be > text/plain. What I remember is that, as more mailbox formats were being added (IMAP), it became clear that Mutt couldn't always get all the information needed in order to display the flag. That is, you'd have to pretty much scan the folder itself to determine which mails have attachments and which do not. And that is expensive, over a network. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: fcntl: No locks available (errno = 37)
Marius Gedminas <[EMAIL PROTECTED]> wrote: > > As a minor side issue: is there a way to save message to a *file* > (i.e. without the locking)? Dotlocking does not work on FAT > partitions... Well, you can press "v" (view-attachments), and then save the body of the message as a regular file. You will lose the headers, though. Or, pipe the message through 'cat > file'. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: mangling a from header
Dominik Vogt <[EMAIL PROTECTED]> wrote: > > send-hook . "my_hdr From: [EMAIL PROTECTED]" > send-hook "^ *[fF]vwm" "my_hdr From: [EMAIL PROTECTED]" > send-hook "^ *[mM]utt" "my_hdr From: [EMAIL PROTECTED]" You seem to have a few minor nits that I'd like to pick at, here... The first is that you seem to assume that Mutt can only use a simple regular expression here. Actually, Mutt expects a "pattern", of which there is a section in the manual. You could do better to specify which part of the address you're matching on, such as the From:, To:, or Cc:. The default, if you give a simple expression, is to match all three. send-hook '~C ^fvwm' "my_hdr From: ..." might be closer to the effect you're looking for. The second is that you are assuming that the pattern matches the entire header line, so that you need to match some whitespace coming before the address. This is not true; Mutt only matches on the actual address, when you use an address pattern. So, if your pattern is '~t ^fvwm', and the header says "To: Those Guys that Do FVWM <[EMAIL PROTECTED]>", the pattern will match, because the only string that Mutt will attempt a match on is "[EMAIL PROTECTED]"; it will ignore the full-name portion. The third is that you need to force Mutt to look for upper and lower case characters with your pattern. This is not true; Mutt will match the pattern case-insensitively, if your pattern contains no upper-case characters. So you should be able to use these instead: send-hook ."my_hdr From: [EMAIL PROTECTED]" send-hook '~C ^fvwm' "my_hdr From: [EMAIL PROTECTED]" send-hook '~C ^mutt' "my_hdr From: [EMAIL PROTECTED]" These ought to work, whether you are replying, or list-replying, as long as one of the recipients (To or Cc) matches "fvwm" or "mutt". Of course, if they match both, you will get the latter as your From: header. That's how hooks work. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: fcntl: No locks available (errno = 37)
Lalo Martins <[EMAIL PROTECTED]> wrote: > > Oh, one more tidbit: I _can_ save attachments. Go figure. That's because attachments are saved to *files*, while messages are saved to *folders*. So attachments don't require any locking (unless you're saving a message/rfc822 type, which is a message, but now it's getting confusing). Basically, Mutt wants to fcntl-lock the folder, to be safe against someone else writing to it. Your NFS client is not running the necessary daemon to coordinate that lock with the server, so it fails, and Mutt gives up rather than possibly trash your mailbox. If you are *certain* that every mail-handling program at your site uses the same dot-locking mechanism, you can reconfigure Mutt with --disable-fcntl, and then you won't have this problem. But if you're wrong, and there is some program that does try to perform fcntl-locks as the only method to prevent synchronization problems, then the two programs can collide and trash the folder if they access it at the same time. Best is to fix the locking problem, as you may have other programs that want to lock files, too. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Sending messages w/ attachments from the command prompt
Mikko Hänninen <[EMAIL PROTECTED]> wrote: > > wizard@chamber:~> mutt wizard -a /dev/null -s foo < /dev/null > stty: standard input: Not a typewriter > stty: standard input: Not a typewriter > stty: standard input: Not a typewriter When Mutt spawns an external command (such as "sendmail"), it uses your exec-shell (/bin/sh? /bin/bash?) to launch that command. Some shells run startup sequences, based on environment variables such as $ENV. Bash runs .bashrc. You may be running an stty command from in one of these. Or several, perhaps, since you see it multiple times. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Sending messages w/ attachments from the command prompt
Rayne Wolery <[EMAIL PROTECTED]> wrote: > > What I was hoping to be able to do was to send an e-mail from the > command prompt with an attachment without any interaction Sounds like you want "mpack". That's what it does. Aris Mulyono <[EMAIL PROTECTED]> wrote: > > Can we specify a specific MIME type too for each attachment? Mutt finds the MIME type by searching your .mime.types file for the file extension. Mpack lets you specify it on the command line. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Clueless about NLS (was: Umlauts again)
Howard Arons <[EMAIL PROTECTED]> wrote: > > I simply cannot get Mutt to show German characters in the pager. The > characters either show up as ?'s or (worse yet) as Cyrillic-looking > letters. Even if I set LANG=de, the German menu items have the same > Cyrillic letters in them. Are you running Mutt on the console? In an xterm? What font do you have loaded? What font string is the xterm using? My xterm is using this font: -misc-fixed-medium-r-normal--10-100-75-75-c-60-iso8859-1 As you can see, it is an iso8859-1 font, which is why I can see the western-european characters. I would need to run in an xterm with a different font, to see Cyrillic characters. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: just another send-hook question
Richard P. Groenewegen <[EMAIL PROTECTED]> wrote: > > send-hook '~t [EMAIL PROTECTED]' '' > > but I'll only want this send-hook to work if [EMAIL PROTECTED] is the only > recipient. Isn't there a pattern modifier "^" that means "only"? send-hook '^~t [EMAIL PROTECTED]' '' That matches only if <[EMAIL PROTECTED]> is the only recipient on the To: header. Note that the Cc: header is not checked. If you really meant "only recipient of the message," you'd want ^~C instead. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Alternates
Nathan Cullen <[EMAIL PROTECTED]> wrote: > > Why (rhetorical question) can't I do it with alternates? > > alternates dre@chronic\.net > alternates snoop@lbc\.ca.us Actually, it used to be that way, but that was before Mutt really supported regular expressions. Once the regexp ability was added to Mutt, a short survey of the then-current Mutt users showed that everyone thought it would be just fine to make a single regexp that matched all addresses. So there you have it, the democratic process at work. :) > Does that just look much cleaner? Yes, it does. Sven Guckes <[EMAIL PROTECTED]> wrote: > > Wishlist? No disrespect intended, Sven, but do people read your wish list? -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: alternates_work
Jeremy Blosser <[EMAIL PROTECTED]> wrote: > > > So if everyone has a mail filter then why use "alternates" at all? > > Because $alternates has a lot less to do with filtering incoming mail > than it has to do with getting the correct From: address when you > reply to mail, etc. In my eyes, the main point of $alternates is to keep my own address from showing up in any group-replies that I do. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Alternates, Groups, Lists, and Work
Sean Rima <[EMAIL PROTECTED]> wrote: > > > My mail filter detects spam, but instead of deleting it, it inserts > > the header 'X-Status: D'. > > Any chance of seeing your filter, sounds good. Alas, my current mail filter is a home-brewed perl script, which is easy for me to tweak and modify, since I wrote it, but I fear it might be a bit of trouble for others to make sense of it. It works nicely, though, supporting direct delivery to mbox and maildir folders.. Perl can do anything. Perhaps I could share it with some folks to see how it perhaps could be improved for better release. Naturally, someone can certainly show how procmail could do this same thing. I simply got tired of procmail's "language," and decided to use a language I know better. :) Erf... topic drift... Sorry. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Alternates, Groups, Lists, and Work
Sven Guckes <[EMAIL PROTECTED]> wrote: > > Most people do not use a mail filter. For them it is nice to > handle both personal *and* work related mails from the mailbox. Mutt is not, nor is it intended to be, the "Emacs" of the MUA world. This is the Unix world, where discrete, simple tools work together to create something greater than their sum. If you want your mail separated, for whatever reason, then use a mail filter. It's that simple. > I'd like to maintain a mail filter only for filtering out spam. So you admit that you have a mail filter, but do not want to put it to its fullest use. > No, mutt does not give enough support for watching folders to be > really handy. What? Mutt notifies me whenever any of my incoming folders has new mail. Is that not "watching" enough? Once again, there are external tools available, such as the wonderful xbuffy. > In the end I want that the 'X' flag actually shows possible spams; and > work related mails are usually not spam. ;-) My mail filter detects spam, but instead of deleting it, it inserts the header 'X-Status: D'. Thus, when I enter my mailbox, all the spam is pre-marked for deletion, and I can either choose to examine it, and undelete the occasional non-spam message (and update my mail filter to let it pass), or simply ignore them and let them get deleted when I close the folder. > And then I'd like to be able to have mutt show > "/var/mail/guckes" as eg "MAILBOX" - much shorter. If you put mails for different purposes in different folders, your inbox WILL be shorter. Mine certainly is. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Sent mail
Michael Sanders <[EMAIL PROTECTED]> wrote: > > I think that should be "<" for $record. ">" refers to $mbox, no? D'oh... so much for trying to be helpful. My mistake. :) -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Sent mail
Subba Rao <[EMAIL PROTECTED]> wrote: > > Where is the outgoing mail saved? By default, nowhere. > How do I see what email I have sent through mutt? Tell Mutt that you want to save outgoing mail, and where to put it: set copy=yes set record=+sent Whatever folder you put as your $record setting, you can use ">" as a shorthand to reference it. So to change to that folder, type "c", and enter ">" as the folder to change to. When you want to come back to your inbox, change to the folder shortcut "!". -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Umlauts (again)
Alexander N. Benner <[EMAIL PROTECTED]> wrote: > > > Mutt will only display iso-latin1 chars if you set locale appropriate. > > try $LANG = en_US.iso88591 > > Also when started on a noniso based font terminal? Of course not. You would have to set your LANG variable to correspond to the environment you're running Mutt in. > or more generally: is there a way to change font within mutt? Of course not. Mutt runs inside a terminal. You tell Mutt what type of terminal that is, and what font it supports, and Mutt will do its best to support the font in use. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Killing an xterm with mutt
Jan Houtsma <[EMAIL PROTECTED]> wrote: > > For now i will add ":set quit=yes" to my muttrc cause i always know > that if i press q i want to quit :-) "set quit=yes" is the default. So if it wasn't already set that way, it's because someone (distro producer? sysadmin?) set it to something else for you. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Alternates
Fairlight <[EMAIL PROTECTED]> wrote: > > > You bunch them all in one big regex. It looks slightly ugly but > > fortunately it doesn't need to be human-parseable most of the time. > > I imagine it does look really confusing with lots of short things like > iki.fi in it. :) Well, if you do like many hackers, and try to make a "clever" regexp, it's probably going to be hard to read. But there's no reason you can't just make a "simple" regexp that does the same thing. For instance, instead of this: set alternates='^(fox|david|cretin)@(convex|hp).com)$" I could just do this: set alternates='^([EMAIL PROTECTED]|[EMAIL PROTECTED]|[EMAIL PROTECTED]|[EMAIL PROTECTED]|[EMAIL PROTECTED]|[EMAIL PROTECTED])$" Which one is easier to read, depends on the width of your terminal, and how much you enjoy parsing regular exprssions. :) -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Killing an xterm with mutt
Sven Guckes <[EMAIL PROTECTED]> wrote: > > > I am lazy and pressing that X is easier then typing "q", "y" :-) > > :set quit=yes > > Now you just have to type 'q' - from anywhere within the xterm. The "y" that he's referring to might be the "delete" prompt, so perhaps :set delete=yes would also help, and perhaps :set move=no (or yes) would help further. > Isn't that much easier than reaching for the mouse and place it on the > "X" first? ;-) I am inclined to agree that, in a mailer program, the hands are more likely to be located closer to the keyboard, than the mouse. :) > But you have a point there - mutt does not exit gracefully. This could be argued quite a bit, I imagine. Suppose your X server blew up, and took all your windows with it? Mutt cannot tell the difference between that condition, and closing the xterm with the [X] button. In both cases, the xterm disappears from around Mutt, and it has no idea why. In this case, Mutt errs on the side of caution, because it doesn't want to lose information, unless it's sure that you are really quitting. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: cannot change mailbox name
sam rosenfeld <[EMAIL PROTECTED]> wrote: > > I have a single-user (me) box with two potential mail users -- root > and user. When I'm logged in as "user" and open mutt, I get an error > message which reads: "/var/spool/mail/root: Permission denied > (errno=13)". The setting that controls this is called $spoolfile. You should check to see if it is getting set somewhere. It probably isn't, because if it's not set, Mutt will create a convenient default that probably points to the right place. The environment will come into play, though. If there is a $MAIL variable in your environment, it will be used as the default for $spoolfile. Otherwise, a default is constructed from the $USER variable. So I would presume that, either you have $MAIL set to /var/spool/mail/root, or you have $USER set to root. Both of these mean there is some misconfiguration in your login-session scripts, and probably not in any Mutt config scripts. > And, I want to make my screen a bit more attractive and readable. How > do I set the COLORFGBG? (The manual.txt is a bit obscure on this > issue.) This is a SLANG config variable, not exactly a Mutt config (though Mutt might have been compiled with Slang on your system). The COLORFGBG variable defines the foreground and background colors that your terminal has. Slang has no way to know, for instance, that your terminal's foreground color might be cyan, and the background might be black. So you can set this variable so that Slang can tell: export COLORFGBG="cyan;black" This does *NOT* mean that when you run a Slang program, it will make your foregroudn be cyan, and your background black! Instead it means that, when Slang runs with this setting, it will assume that, if the foreground is supposed to be cyan, and the background is supposed to be black, that it can just print normal, uncolored spaces, or use screen- clear and line-clear commands, because the proper colors will get used by the terminal. Now, that's probably clear as mud. :( -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: viewing html
Lars Hecking <[EMAIL PROTECTED]> wrote: > > > text/html; /usr/bin/lynx -dump -force_html %s; copiousoutput; nametemplate=%s.html > > Leave out the nametemplate part. While I agree that the nametemplate section is not necessary since -force_html is used, I can't see why it would cause this problem. Can you explain? -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Auto-archiving of outgoing mail
Daniel Roesen <[EMAIL PROTECTED]> wrote: > > > is it possible to have mutt automatically archive sent mail in a folder? > > set record=+sent-mail And make sure that you also "set copy=" in order to activate the functionality. I don't think setting $record actually turns on the function, because it has a default value of "+sent". -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: [1.0i] pager or quoted-printable encoding issue (funky characters)
Clint Olsen <[EMAIL PROTECTED]> wrote: > > > This sounds like your locale configuration is screwed up. > > Ok, so how about giving me a hint where to look on how to fix this? Try "man locale" on your system. In my case (HP-UX; your OS might work quite differently), I ran the command "locale -a", and received a list of supported locales. After examining them for a while, I chose this one that I liked: "en_US.iso88591". After deciding on this, I selected the locale by setting the $LANG variable in my environment. For csh, that means adding "setenv LANG en_US.iso88591" to my ~/.login, and for bash/ksh it means adding "export LANG=en_US.iso88591" to ~/.profile. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Hostname/Domainname
Bernd Renzing <[EMAIL PROTECTED]> wrote: > > From: Bernd Renzing <[EMAIL PROTECTED]> > > As you see, Mutt appends as domain @voyager.localnet. BUT and here's > now my Problem: my Hostname in /ETC/HOSTNAME and via SET | more and > via hostname -f is voyager.prima.de !!! Your message is probably routing through sendmail. Your sendmail.cf probably has that string listed as your domain name. Change it. You might also check /etc/resolv.conf and see if that file has your correct domain in it, too. > I've searched the completed Harddisk for this String, but i don't find > it ... :-(. It may not be written as literally "voyager.localnet". The domain name "localnet" is probably written somewhere, and the machine's hostname is added to it by well-meaning software, such as Mutt. Putting the correct domain name in the right place should fix this. But try searching for just the string "localnet" in your /etc directory, for a start. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Reply-To, save sent
Reed Lai <[EMAIL PROTECTED]> wrote: > > 1. i cannot make mutt to use Reply-To field in received message as >the reply address when i want to reply it. >i tried set reply_to=ask-yes, but it didn't work. Is the Reply-To address a list address? Did you set ignore_list_reply_to? Perhaps an example message would be useful. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: [1.0i] pager or quoted-printable encoding issue (funky characters)
Clint Olsen <[EMAIL PROTECTED]> wrote: > > Well, shouldn't I see this character as it is (+/-), or should the > builtin pager emit a '?' instead? A '?' is currently what I'm seeing > on this machine right now. If I fail to set my $LANG environment variable to a locale that includes iso-8859-1 characters (currently I set it to "en_US.iso88591" on my HP-UX box), then I see "?" in the pager for that character. By telling my OS that I can and want to see these characters, Mutt picks up on this and shows them to me. The fact that "vi" and "less" show the character regardless of locale setting, means that those programs ignore locales. Mutt believes that the world is much larger than your local Unix box, so it wants you to tell it about your locale, and tries to use your OS's localization routines to their fullest. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: [1.0i] pager or quoted-printable encoding issue (funky characters)
Clint Olsen <[EMAIL PROTECTED]> wrote: > > Mutt is not correctly coding this message since it contains a character > inserted (probbably) by vi :digraph. Should this be marked as "quoted- > printable"? Depends on how you set "allow_8bit", doesn't it? > can you see the plus/minus character: ± ? It looks like a +/- character to me. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Clicking http- and ftp-Links in mutt?
Rob Reid <[EMAIL PROTECTED]> wrote: > > I use rxvt 2.4.5 patched with something called "dingus", or > active-rxvt. I never could get that working. > It works really well (i.e. much better than urlview), and doesn't > interfere with selecting (left button) or pasting (middle button). Am > I missing something that the right button would normally do? Normally the right-button is used to *extend* the current selection. For instance, you select some text with the left-button, and then if you decide you really wanted more, instead of reselecting, you can click or drag with the right-button to modify the selection. I use it on a very occasional basis. > Unfortunately applying the patch to newer versions of rxvt was so > difficult that I gave up. Indeed, on HP-UX I was never able to get past the compile/patching stage, so I gave up, too. > I should note that it only fully works in Linux or other OSes using > /proc. It's usable in Solaris for URLs, though. Hmm, curious, why is /proc required? Oh well.. Mikko Hänninen <[EMAIL PROTECTED]> wrote: > > I have no idea how xterm is supposed to know this, but apparently it's > still a supported feature. I know because lynx does this (version > 2.8.1rel.2). Yes, an application can put the xterm into a special mode in which mouse-clicks are reported to it. Slang supports this, but I'm not sure if Ncurses does. > I find it actually very annoying when I can't copy/paste to/from an > xterm window running lynx! Actually, you can; xterm allows the normal cut/paste actions to be performed, if you hold the SHIFT key. Still annoying to have to remember that. :) Bruno Daniel <[EMAIL PROTECTED]> wrote: > > Midnight commander solves it by allowing cut and paste by holding the > shift key during selection. Actually it's xterm that is allowing that behavior. But I suppose that, in MC, you are more likely to want to click on something than select some text. In a mail-reader program like Mutt, the opposite is probably true. > We could do it the other way round: normal clicks for selection and > Shift-Click on an URL for opening netscape windows. That sounds nice, but xterm doesn't work that way, to my knowledge. At any rate, a dingus or gnome-terminal type solution seems to be the best one I've seen. Modifying Mutt doesn't seem like the best way to solve this problem. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Abort current operation
Mikko Hänninen <[EMAIL PROTECTED]> wrote: > > > "^Zkill %1" > > This works if you're starting Mutt from a shell, but is not really an > alternative when you're launching Mutt with "xterm -e mutt" like me. > Or is there some way to get that work there too? Xterm's have a Ctrl-Mouse-1 menu, with a "Send TERM signal" option, that does the same as above. Of course, expect the xterm to go away after that; might as well just close the xterm and re-open it. > In any case it's a bit of a kludge. True, but the case doesn't come up all that often, and if it really bothers you, perhaps smaller folders are the answer. Anyway, as always, you know where the code is. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Clicking http- and ftp-Links in mutt?
Bruno Daniel <[EMAIL PROTECTED]> wrote: > > Is it possible to implement opening a Netscape window upon clicks onto > http- and ftp-Links in mutt? Sure! > What's your opinion? Please have the code written up and bug-tested by this weekend. :) On a more serious note: Mouse-clicks already have a defined meaning within xterm: They are used for cutting, selecting, and pasting text! So how is your xterm supposed to know when you're clicking in order to select some text, or clicking in order to pass the information to the inner program, Mutt, so that it can search for a URL to go to? In the old, old days of Mutt, it supported mouse-clicks, not for URL's, but for simple message navigation. Most everyone hated it. It was removed. Basically, people realized that they wanted the cut-n-paste functionality a lot more than they wanted the point-n-click functionality. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Abort current operation
Rob Reid <[EMAIL PROTECTED]> wrote: > > At 6:14 AM EDT on October 27 Martin Julian DeMello sent off: > > It'd be nice if mutt had an 'abort' key, > > It does. Control g It doesn't abort reading a huge folder. In fact, nothing does. Once you start to read that 20 MB folder, you're going to be there until it's done. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: bug in 1.0i?
J. Lasser <[EMAIL PROTECTED]> wrote: > > Hmmm... in 1.0i, if I'm in the message index, it will occasionally > beep at me that I've got new mail in a folder, but by the time I hit a > key, the Inc: 1 line in the status bar goes away, and if I hit > hange mailbox, it's not waiting there as the default answer. Mutt uses the timestamps on the folders (try "ls -l
Re: masq of hostname
Martin Högman <[EMAIL PROTECTED]> wrote: > > Whenever I send a message to certain servers, they return the classic > message "hostname unknown" to me. Does the hostname really exist, or not? If it does, then you should try to figure out why your DNS server says it doesn't. If it doesn't exist, then this is of course a correct error. > I've set up the REPLYTO parameter in my shell (bash) to > [EMAIL PROTECTED], I've set the my_hdr Reply-To: [EMAIL PROTECTED] , > so that should be correct too... I'm sure it doesn't matter what you set your reply-to to... you're sending mail, not receiving it. > Strangely, this does only happen with mutt, not with, say, pine or any > other mail program... Utilizing mutt1.0pre3 from a RH 6.1 > distribuion... Mutt and Elm should use exactly the same method to send mail. That is, if Elm can send mail without errors, Mutt should do as well, because they both pipe the mail directly to your local sendmail daemon. Whereas, Pine delivers mail to whatever mail server you specify, and that server routes it to the correct destination. Which would explain why Pine behaves differently. Of course, the easy thing to do is to configure your local sendmail daemon to simply route all mail through the same server that Pine would've used, since that is probably the mail hub for your site anyway. Simply use that server as a "smart host." -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Colorized headers and the fu of TERM
Phil Stracchino <[EMAIL PROTECTED]> wrote: > > Mutt uses color, and displays everything else correctly as well, if > TERM=color_xterm, but pico breaks with this value for TERM. You didn't say how pico breaks. Does it claim that it can't figure out what the terminal setting means? Maybe pico uses termcap instead of terminfo, so you could fix this by adding a synonym for "xterm" called "color_xterm" in your /etc/termcap file. Change this: vs|xterm|xterm-24|vs100|xterm (X Window System):\ to look more like this: vs|xterm|xterm-24|color_xterm|vs100|xterm (X Window System):\ -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Floating point exception
Vincent Lefevre <[EMAIL PROTECTED]> wrote: > > And you could avoid the division with: > > (info->lobin + info->hibin + info->ascii)*4 > < ((info->lobin + info->hibin)*3 + info->ascii)*3 But then you risk integer overflow. Which the division helps avoid, and in fact, floating-point helps avoid it even more. :) But if you're attaching files that big... errf.. :) -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Change the content-type from the command line
Ryan Claycamp <[EMAIL PROTECTED]> wrote: > > I am setting up a script file to fetch a web page every day and mail > it to a friend. I do great getting the file with wget. When I pipe > it to mutt, it sends it through as plain text. This is pretty much a limitation of Mutt's batch mode. > If I was doing this manually, I discovered that I could edit-type to > text/html. How do I do this from the command line, so I can run it > from cron? Somehow I doubt this can be done, but some of Mutt's users are pretty clever... One way to do this would be to send the wget output to a file, then attach that file in batch mode, using the -a switch to Mutt. But your message will still need a text/plain part to make up the main body, to which the HTML will be attached. A tool which is better-suited to your particular task, is mpack. You might want to give it a try. Mutt isn't *always* the answer to your E-mail needs, you know. :) -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: "Error sending message, child exited 70 (Internal error.)" messages
Winston Moy <[EMAIL PROTECTED]> wrote: > > Thanks for the info... I was able to locate the cause, while I was > tailing the active syslog... I had a corrupt alias database... once > the database was cleaned up, Mutt was happy... Wow, that's amazing: > > > "Error sending message, child exited 70 (Internal error.)" when sending out. The "Internal Error" message was actually correct! It's just that, from the way the message is reported, it's not terribly obvious that the child process is sendmail, and that it was sendmail that had the internal error. :) -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: "Error sending message, child exited 70 (Internal error.)" messages
Winston Moy <[EMAIL PROTECTED]> wrote: > > "Error sending message, child exited 70 (Internal error.)" when sending out. Sendmail doesn't like the command line it's being given by Mutt. Here's a simple shell script: #!/bin/sh echo "Args: " "$@" >> /tmp/sendmail.log Save this script, then in Mutt, "set sendmail=/path/to/script". Then, send a dummy message, and when finished, check the /tmp/sendmail.log file to see what arguments sendmail was supposed to be called with. Then try calling sendmail with those arguments and see why it fails. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Broken MUAs and the "encoding" flag
Lalo Martins <[EMAIL PROTECTED]> wrote: > > Is there some way to tell mutt to fix that somehow? I, too, have wished I could change the broken encoding on some received messages. Windows-1250 seems to be a common one that's misrepresented as us-ascii. > Perhaps ignore ``encoding'' when it's us-ascii, or when it's obviously > wrong? The trouble is, knowing it's wrong isn't too hard, but how do you know what the right encoding is, then? -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Terminal problem
Vincent Lefevre <[EMAIL PROTECTED]> wrote: > > Because I like this behavior with other programs (e.g. less), and > even with Mutt when I quit Mutt (but not when I pipe a message or > reply to a message). You are fickle. :) At any rate, Mutt does not really have the level of control that you seem to want. Mutt is talking to the curses library, and curses sends the escape sequences to swap screens. Mutt only knows to call initscr() when it wants curses to manage the screen, and endwin() when it wants to stop. When calling another program that will take over the screen (i.e. your editor), Mutt must call endwin() to stop using the screen, then initscr() again when it regains control. As far as I know, there's no endwin_but_dont_swap_to_the_default_screen(), or initscr_but_pretend_were_already_on_the_background_screen() functions. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Terminal problem
Vincent Lefevre <[EMAIL PROTECTED]> wrote: > > When I pipe a message or when Mutt starts the editor (in another > window), the current screen is removed and the screen before I started > Mutt is displayed. Can this be changed (without changing my > terminfo)? If you don't like this behavior, why don't you want to change your terminfo? That's where the curses library is getting its information from... At any rate, I use Mutt in an xterm, and I have this resource enabled: XTerm*titeInhibit: true That causes xterm to ignore the ti/te escape sequences which would swap it between the primary and alternate screen displays. I've never liked that behavior, in Mutt or otherwise, so I turn it off. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Sending attachments without invoking editor
Marcin J. Kraszewski <[EMAIL PROTECTED]> wrote:
>
> Is there a way in mutt to send an attachment from the command line,
> without invoking an editor?
echo "message text" | mutt -a attachment_file \
[ -a attachment_2 ] \
-s "Subject Line" \
[EMAIL PROTECTED] [...]
--
David DeSimone | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED] | that there is no man really clever who has not
Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson
UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: save-hook stuff?
Mikko Hänninen <[EMAIL PROTECTED]> wrote: > >T~s \[LUG\];s=lug > > [...] You need to escape the square brackets or Mutt will interpret > that as "any character of L, U or G". [...] Since you mentioned backslashes, I feel the need to point out that you can easily get in trouble with them, since Mutt's parser likes to eat backslashes for breakfast. For instance, while processing the 'macro' command above, the backslashes will be removed while examining the macro text, unless you use 'single quotes' around the text of the macro. But also, when the macro is evaluated, the input parse will scan for backslashes, and eat some more of them. So the correct way to get the above working would be something like this: macro index'T~s \\[LUG\\];s=lug' or if you used double-quotes, macro index"T~s [LUG];s=lug" -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: how to set up alternate SMTP server
Edmund GRIMLEY EVANS <[EMAIL PROTECTED]> wrote: > > Or, preferably, mutt should handle POP3 mailboxes in the same way that > it handles IMAP and other mailboxes. So messages remain on the server > until the user asks them to be deleted. There was some talk of this on mutt-dev. The consensus seemed to be that it would end up confusing users, because POP marks a message as no longer NEW when you read it, and there is no way to mark the message NEW again, like you can for any of the other mailbox types. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: printing messages from maildir directories (enscript integration?)
Keith Harbaugh <[EMAIL PROTECTED]> wrote: > > Within a folder, sometimes I would like to be able to print out > selected messages, but using the capablility of enscript Why not set print_command to be "enscript --whatever-args", then tag the messages you want to print, and use the tag-print command? -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: managing folders
Eric Smith <[EMAIL PROTECTED]> wrote: > > Byrial - > | mutt -f folder-to-expire -e 'set delete;push D~r>20dq' > > Been looking for something like this for ages - great to put into a > cron job script that iterates through a list of folders. I don't think this will work from a cron job, because there will be no connecting tty, and Mutt will not be able to initialize cursses. Do things like this really work from cron? -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: how to set up alternate SMTP server
Shao Zhang <[EMAIL PROTECTED]> wrote: > > So why mutt implements a pop3 protocol? Why do we need this when we > have fetchmail? It's not needed. It should be removed. Mutt's POP3 support went in before fetchmail was really existent/stable. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: managing folders
Mikko Hänninen <[EMAIL PROTECTED]> wrote: > > > > Or to limit the number of messages a folder will hold, so when new > > > messages are added old messages scroll off? > > If the messages are saved in the folder with a filtering program > such as procmail or maildrop, it might be possible to create a > folder-injection program that ensures this If using maildir format folders, one could easily create a cron job that counts how many messages are in the folder, and then deletes the oldest of them, based on timestamps. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: mutt overwriting folders
Stijn de Bekker <[EMAIL PROTECTED]> wrote: > > > Mutt doesn't have an "unbind" command. > > It does not have the unbind command but you can bind a key to noop to > unbind it: > > bind generic N noop That is true, but he already did a "bind generic N" to the function that he wanted (search-opposite), and it didn't work. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: mutt overwriting folders
Jeroen Ruigrok/Asmodai <[EMAIL PROTECTED]> wrote: > > unbind N first? Mutt doesn't have an "unbind" command. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: filtering again
Loren Schooley <[EMAIL PROTECTED]> wrote: > > Anyone know of a good FAQ with the subject of filtering mailbox's > included in it? http://www.faqs.org/faqs/mail/filtering-faq/index.html Try using a web search tool sometime. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Reply-To
John Poltorak <[EMAIL PROTECTED]> wrote: > > When a msg comes from a mailing-list and there is a 'To:' line in the > header but no 'Reply-To:', is there any way to get mutt to reply to > the 'To:' line rather than the 'From:' line? list-reply ? -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: Editing a bounced message
rex <[EMAIL PROTECTED]> wrote:
>
> If the message is edited ("e"), the bounce function is disabled, and
> "b" results in a Bcc: query instead of bouncing the message as it
> normally would.
As someone else pointed out, what I mean was to edit the message, save
the edited message back to the folder, then bounce that message.
Since I don't use edit-message very often, it didn't occur to me that it
would be difficult to tell the original from the new (edited) message in
the folder. I thought edit-message marked the old message for deletion,
or somesuch. Ah well...
> I've looked at $@. Mutt passes "--", then the address(es), and .muttrc
> includes "-oi -oem" in the sendmail call, so they may be needed (I
> have no idea what they do, and couldn't find them in the sendmail docs
> I have).
Just FYI, "-o" is used to turn on options that can also be enabled with
the "O" command in the sendmail.cf file. The two options are "i"
(ignore a single "." if it appears in the input), and "em" (if there are
errors, report them via E-mail). Without those command-line options, a
message which happens to have a single "." on a line by itself, will
prematurely terminate the message. And if there are delivery problems,
sendmail will try to print errors on your terminal, which wreaks havoc
with curses-based programs like Mutt. So we choose to bounce the error
messages in E-mail instead, and users are accustomed to that, anyway.
> I'll remove the "-t" and use "$@", as you suggest, however I want to
> dump the first argument ("--") first, as it makes premail choke. A
> shift command should handle that, eh?
That would do the trick.
--
David DeSimone | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED] | that there is no man really clever who has not
Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson
UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
