binding F1 to manual, Eterm vs. Xterm
This works fine in Xterm, however in Eterm this brings up a mod menu for the Eterm I am working in. Does anyone know how to change this behavior? -- /Jason G Helfman "At any given moment, you may find the ticket to the circus that has always been in your possession." Fingerprint: 6A32 3774 E390 33B5 8C96 2AA1 2BF4 BD71 35A1 C149 GnuPG http://www.gnupg.org Get Private! 1024D/35A1C149
PGP and mutt
I've installed mutt and included pgp6.rc from mutt doc directory in .muttrc. I have pgp 6.5.8 freeware installed and working. I've added header rewrite rules for pgp messages (non-mime) in .procmailrc. When I open such a message, mutt tries to invoke pgp on it but pgp failes on recieve of signal 11. It failes with pgp mime messages either. PGP-Notes.txt from mutt.org web mentions some utilities (pgpring...) that I also have in /usr/bin. Documetation states that inclusion of pgp6.rc should be enough to have it working. Is pgp 6.5.8 what mutt means as pgp6? Am I to install some former version? (I tried to build pgp5 but it failed and binary package is not on pgpi web).
Re: PGP and mutt
yes PGP is working, I use it on saved messages. Btw. it also says cat: write error: Broken pipe And it worked with pine well (with pgp4pine addon) On Thu, Mar 01, 2001 at 12:51:28AM -0800, Jay Rossiter / Signe wrote: On 03/01, Jan Hudak spat into the ether: Date: Thu, 1 Mar 2001 09:41:36 +0100 From: Jan Hudak [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: PGP and mutt Mail-Followup-To: Jan Hudak [EMAIL PROTECTED], [EMAIL PROTECTED] User-Agent: Mutt/1.2.5i I have pgp 6.5.8 freeware installed and working. When I open such a message, mutt tries to invoke pgp on it but pgp failes on recieve of signal 11. Signal 11 is a segmentation fault. It's crashing. Have you tested PGP standalone yet to see if it's working outside of mutt? -- PGP Key available on Keyservers - UIN: 1878946 ID: 0x81279EE9 - WebPage: http://www.speakeasy.org/~signe Fingerprint: CB63 1EB8 8150 A01A F017 C79B 1DC5 3BFF 8127 9EE9
Re: Replying to From: address
* Dirk Laurie [EMAIL PROTECTED] [010301 09:43]:
Very properly, mutt replies to the "Reply-To" address if one is set.
I belong to some mailing lists where "Reply-To" is set to the list.
This is OK if I wish to send to the sender and the list ("g") or to
the list only ("r") but not if I wish to reply to the sender only.
E.g. "Listen old chap, I don't want to be nasty but this sort of
drivel really makes you look a fool" and "Why don't the pair of us get
together at Luciano's tonight?" fall into that category.
Is there a mutt function that lest me reply to the "From" address even
when "Reply-To" is provided?
Make sure $reply_to is set to ask-yes in your .muttrc.
, [ mutt manual ]
| 6.3.171. reply_to
|
| Type: quadoption
| Default: ask-yes
|
| If set, Mutt will ask you if you want to use the address
| listed in the Reply-To: header field when replying to a
| message. If you answer no, it will use the address in the
| From: header field instead. This option is useful for
| reading a mailing list that sets the Reply-To: header field
| to the list address and you want to send a private message
| to the author of a message.
`
You might also want to take a look at mutts mailing list features
(e.g. the lists and subscribe commands).
chris
--
christian r. mollsthe rain descended,
[EMAIL PROTECTED] and the floods came
Re: F flag(false positive)
Well, I know I can change my localhost to be a weired name... That is not point. (faking host name with exim is easy too.) But, jeff you are not even doing it either Received: (from jeff@localhost) My question is how I can change Mutt behavior deciding on which mail are from local machine. I bet if I create jeff in my machine account, and send mail to you, it shall be marked F. Regards, Osamu On Wed, Feb 28, 2001 at 04:01:11PM -0500, Jeff Abrahamson wrote: On Tue, Feb 27, 2001 at 11:15:16PM -0800, Osamu Aoki wrote: Suppose someone send mail from account "debian" from "localhost" and I recieve it here in account "debian" on "localhost", it showup as if it came from myself in my Mutt. Is there any good way to avoid this? Any suggestion? Name your machine. Create an account for yourself. -- Jeff Jeff Abrahamson http://www.purple.com/jeff/ -- + Osamu Aoki [EMAIL PROTECTED], GnuPG-key: 1024D/D5DE453D + + Fingerprint: 814E BD64 3288 40E7 E88E 3D92 C3F8 EA94 D5DE 453D + + http://www.aokiconsulting.com/pc/ Cupertino, CA USA +
Re: Getting accented characters etc. to work in mutt pager
On Wed, Feb 28, 2001 at 08:51:16AM +, Chris Green wrote: Maybe what I'm seeing is my *local* system displaying the characters correctly (I'm doing this via telnet) and cat, more and vi are simply sending the 8-bit characters "as is" whereas mutt and less are being 'correct' and saying "I can't display this". So maybe the question I should be asking is:- How do I make the mutt pager send the 8-bit characters "as is" rather than changing them to "?". Does anyone have any ideas about this? It does seem as if this is what is happening so how do I tell the mutt pager to do nothing to 8-bit characters? -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: binding F1 to manual, Eterm vs. Xterm
+ Jason Helfman [EMAIL PROTECTED]: This works fine in Xterm, however in Eterm this brings up a mod menu for the Eterm I am working in. Does anyone know how to change this behavior? Had this problem, too. Someone on this list helped me (sorry, forget who exactly). Add this lines to your theme.cfg: cut here --- # F1 - F4 since xterm sends different codes for these mutt is looking for them # instead of what Eterm sends by default. keysym 0xFFBE "^[OP" keysym 0xFFBF "^[OQ" keysym 0xFFC0 "^[OR" keysym 0xFFC1 "^[OS" cut here --- Kai. -- mail | [EMAIL PROTECTED] pgp: [EMAIL PROTECTED] icq: 102024972 | http://www.glorybox.de/
Re: Fix broken threading
On Thu, Mar 01, 2001 at 12:28:56AM +0100, Christian R Molls wrote: I usually read my mail sorted by threads. Once in a while (on some lists the while is pretty short), threading breaks because some moron hit the "Reply"-Button not to reply but to compose a message completely unrelated to the one he is replying to. His messages and the replies to it subsequently clutter the original thread. As I swa no replies to you inquire I have one loosy suggestion that works but is a PITA. Use the E key to edit the raw message adn delete the lines. Also if you have the time and streanght try to educate thease lusers as they appear everwhere.
Re: Fix broken threading
* Jan Johansson [EMAIL PROTECTED] [010301 14:47]: On Thu, Mar 01, 2001 at 12:28:56AM +0100, Christian R Molls wrote: I usually read my mail sorted by threads. Once in a while (on some lists the while is pretty short), threading breaks because some moron hit the "Reply"-Button not to reply but to compose a message completely unrelated to the one he is replying to. His messages and the replies to it subsequently clutter the original thread. As I swa no replies to you inquire I have one loosy suggestion that works but is a PITA. Use the E key to edit the raw message adn delete the lines. Actually, I got a private response from Ulf Erikson [0]. He made a pretty nifty macro for that matter. It uses formail as editor for the edit command. I added "change-folder^Enter", which re-reads the folder after the message has been edited. You'll need Byrial Jensen's current shortcut patch for that to work. It can be found on his homepage [1]. Although written for mutt 1.2, it works for later versions without problems. Regards, chris macro index ,U "enter-commandset editor=\ 'formail -R References Old-References -R In-Reply-To Old-In-Reply-To\ %s /tmp/mutt-fix.$$;mv /tmp/mutt-fix.$$ %s; sleep 1; touch %s'enter\ editenter-commandset editor=vimenterchange-folder^Enter" \ "remove current message's \"References:\" header" [0] [EMAIL PROTECTED] [1] http://home.worldonline.dk/~byrial/mutt/patches/ -- christian r. mollsthe rain descended, [EMAIL PROTECTED] and the floods came
Re: Setting From: when replying
I am still trying to get this to work and it is not. I also get mail at different address and would like mutt to change the From: field to that address the email to which I am replying to was sent. I have 'set reverse_name' and 'set alternatives' with the address set, and it still puts in the my_hdr I have set. Thanks. -Ken -- [EMAIL PROTECTED]AIM: ScopusFest
Re: Fix broken threading
On Thu, Mar 01, 2001 at 02:41:25PM +0100, Jan Johansson wrote: On Thu, Mar 01, 2001 at 12:28:56AM +0100, Christian R Molls wrote: I usually read my mail sorted by threads. Once in a while (on some lists the while is pretty short), threading breaks because some moron hit the "Reply"-Button not to reply but to compose a message completely unrelated to the one he is replying to. His messages and the replies to it subsequently clutter the original thread. As I swa no replies to you inquire I have one loosy suggestion that works but is a PITA. Use the E key to edit the raw message adn delete the lines. Also if you have the time and streanght try to educate thease lusers as they appear everwhere. There was a correspondence on the list last November on this topic. It included a macro for fixing things up; it's still on my TODO list :(. Try the URL: http://groups.yahoo.com/group/mutt-users/message/15348 and links therefrom. HTH HAND -- Martin Hillyer Powered by Debian GNU/Linux 2.2.18 Communications by mutt-1.3.12i ~~ QOTD: If Robert Di Niro assassinates Walter Slezak, will Jodie Foster marry Bonzo??
Re: Fix broken threading
On Thu, Mar 01, 2001 at 12:28:56AM +0100, Christian R Molls
[EMAIL PROTECTED] wrote:
I know that I have read about this matter before, but had no luck
searching the archives: what possibilities are there to fix that
issue? Im thinking of a macro/script combination called from withing
mutt that deletes the misleading "In-Reply-To:" and "Reference" headers
in the mbox file that holds the thread, and makes mutt re-read the
folder, now with two separate threads. Anyone done that before?
Yup. I wrote a patch to mutt to "break threads" when the subject
line changes (except for things like "re:", of course). I've been
running with my patch for months now. The best part is that it leaves
your original messages intact, and you can toggle between the two modes
if you want. I mostly use the patch because on some mailing lists
people change the subject of thread that has wandered off-target, but
the References and In-Reply-To fields keep the message in the same
thread. Applying my patch and turning subj_breaks_thread on will put
messages with different subject lines in different threads.
I never did get much of a response for my patch. I've attached it
if you'd like to apply it.
--
Bob Bell [EMAIL PROTECTED]
-
"In theory, theory and practice are the same.
In practice, they are different."
-- Larry McVoy
diff -ru -x CVS mutt-cvs/commands.c mutt/commands.c
--- mutt-cvs/commands.c Wed Jun 21 05:55:24 2000
+++ mutt/commands.c Wed Sep 20 17:09:26 2000
@@ -472,6 +472,7 @@
char buffer[LONG_STRING], errbuf[SHORT_STRING];
int r;
int old_strictthreads = option (OPTSTRICTTHREADS);
+ int old_subjnothread = option (OPTSUBJNOTHREAD);
int old_sortre = option (OPTSORTRE);
buffer[0] = 0;
@@ -493,6 +494,7 @@
mutt_error ("%s", errbuf);
}
if (option (OPTSTRICTTHREADS) != old_strictthreads ||
+ option (OPTSUBJNOTHREAD) != old_subjnothread ||
option (OPTSORTRE) != old_sortre)
set_option (OPTNEEDRESORT);
}
diff -ru -x CVS mutt-cvs/init.h mutt/init.h
--- mutt-cvs/init.h Tue Sep 5 11:01:09 2000
+++ mutt/init.h Wed Sep 20 16:51:39 2000
@@ -1997,6 +1997,16 @@
** personal mailbox where you might have several unrelated messages with
** the subject ``hi'' which will get grouped together.
*/
+ { "subj_breaks_thread", DT_BOOL, R_RESORT|R_INDEX, OPTSUBJNOTHREAD, 0 },
+ /*
+ ** .pp
+ ** If set, a message that would normally be a member of a thread will
+ ** not be a member of that thread if the subject has changed. This is
+ ** useful when a message reply updates the ``References'' and/or
+ ** ``In-Reply-To'' fields, but the sender changes the subject line
+ ** with the intent to indicate that the subject of discussion has
+ ** changed.
+ */
{ "suspend", DT_BOOL, R_NONE, OPTSUSPEND, 1 },
/*
** .pp
diff -ru -x CVS mutt-cvs/mutt.h mutt/mutt.h
--- mutt-cvs/mutt.h Fri Jul 28 15:25:58 2000
+++ mutt/mutt.h Thu Sep 21 10:27:24 2000
@@ -354,6 +354,7 @@
OPTSORTRE,
OPTSTATUSONTOP,
OPTSTRICTTHREADS,
+ OPTSUBJNOTHREAD,
OPTSUSPEND,
OPTTHOROUGHSRC,
OPTTILDE,
@@ -582,6 +583,7 @@
unsigned int display_subject : 1; /* used for threading */
unsigned int fake_thread : 1; /* no ref matched, but subject did */
unsigned int threaded : 1;/* message has been threaded */
+ unsigned int subj_broke_thread : 1; /* not with thread due to subject change */
unsigned int recip_valid : 1; /* is_recipient is valid */
unsigned int active : 1; /* message is not to be removed */
diff -ru -x CVS mutt-cvs/thread.c mutt/thread.c
--- mutt-cvs/thread.c Wed May 10 13:16:43 2000
+++ mutt/thread.c Thu Sep 21 11:53:28 2000
@@ -504,6 +504,7 @@
ctx-hdrs[i]-child = NULL;
ctx-hdrs[i]-threaded = 0;
ctx-hdrs[i]-fake_thread = 0;
+ctx-hdrs[i]-subj_broke_thread = 0;
}
ctx-tree = NULL;
}
@@ -557,15 +558,37 @@
CUR-parent = NULL;
insert_message (ctx-tree, CUR, usefunc);
}
-else if (!CUR-threaded)
+/* Check if (1) message is not yet threaded, or (2) a change in
+ * subject broke the thread but that option has been turned off,
+ * or (3) if the message is a candidate to break from the thread
+ * and the option is currently set
+ */
+else if (!CUR-threaded ||
+(CUR-subj_broke_thread !option (OPTSUBJNOTHREAD)) ||
+(!CUR-subj_broke_thread option (OPTSUBJNOTHREAD)
+ CUR-subject_changed CUR-parent != NULL))
{
+ if (CUR-threaded)
+ {
+ unlink_message (CUR-parent-child, CUR);
+ CUR-parent = NULL;
+ }
if ((tmp = find_reference (CUR, ctx)) != NULL)
{
- CUR-parent = tmp;
if (CUR-env-real_subj tmp-env-real_subj)
CUR-subject_changed = mutt_strcmp (tmp-env-real_subj,
CUR-env-real_subj) ? 1 : 0;
else
CUR-subject_changed = (CUR-env-real_subj ||
Re: binding F1 to manual, Eterm vs. Xterm
On Thu, Mar 01, 2001 at 02:37:26PM +0100, Kai Weber wrote: + Jason Helfman [EMAIL PROTECTED]: This works fine in Xterm, however in Eterm this brings up a mod menu for the Eterm I am working in. Does anyone know how to change this behavior? Had this problem, too. Someone on this list helped me (sorry, forget who exactly). Add this lines to your theme.cfg: cut here --- # F1 - F4 since xterm sends different codes for these mutt is looking for them # instead of what Eterm sends by default. keysym 0xFFBE "^[OP" keysym 0xFFBF "^[OQ" keysym 0xFFC0 "^[OR" keysym 0xFFC1 "^[OS" cut here --- I just had this problem as well, but I decided to configure mutt for Eterm instead of what Kai suggested. If you bind your manual macro to "\e[11~" in your ~/.muttrc, you can use F1 in Eterm to view the manual. All the key codes generated by Eterm for the special keys are listed in the documentation installed with Eterm as well. -- Jeremy A. GrayA434 Chemical and Life Sciences Laboratory Graduate Student--Chemical PhysicsUniversity of Illinois at Urbana-Champaign [EMAIL PROTECTED]http://www.students.uiuc.edu/~jagray/ "Remember the Pueblo. " -- The Fourth Law of Marvin
Re: How to read mutt-users-digest
I have a question about your formail suggestion. The individual messages that make up the digest only have 2 headers: "From" and "Subject". So when I run formail, the resulting messages don't have anything unique that procmail can use to identify them as being from mutt-users. Other list's digests typically do one of two things: * Include other headers in the individual messages, such as "To" or "Cc", or * Prepend something to the subject, like "[wm-users] Original subject here". How do you handle this when using formail to split the mutt-users digest? Kevin On Wed, Feb 28, 2001 at 11:55:34PM +0100, Christian R Molls wrote: snip The mutt-users list is available both digested and as separate mails. You might want to unsubscribe from the the digest and make a new subscription for regular mails. Check out www.mutt.org for advice. However, if you want to keep receiving the digest, you could still split it locally. "formail", which is part of the "procmail" package, can split incoming digests. Check out the procmailex manpage, in case procmail is already installed on your system, otherwise get it from www.procmail.org. - -- christian r. mollsthe rain descended, [EMAIL PROTECTED] and the floods came
Re: Replying to From: address
Dirk Laurie muttered:
Very properly, mutt replies to the "Reply-To" address if one is set.
I belong to some mailing lists where "Reply-To" is set to the list.
This is OK if I wish to send to the sender and the list ("g") or to
the list only ("r") but not if I wish to reply to the sender only.
E.g. "Listen old chap, I don't want to be nasty but this sort of
drivel really makes you look a fool" and "Why don't the pair of us
get together at Luciano's tonight?" fall into that category.
Is there a mutt function that lest me reply to the "From" address
even when "Reply-To" is provided?
For this purpose set ignore_list_reply_to. Maybe in combination with
sent- or folder-hook.
HTH,
Michael
--
"I once witnessed a long-winded, month-long flamewar over the use of
mice vs. trackballs...It was very silly."
(By Matt Welsh)
PGP-Key: http://www-stud.ims.uni-stuttgart.de/~tatgeml/public.key
OPENSSL_VERSION_NUMBER problem in mutt_ssl.c (CVS v2.5)
Hi! I noticed a problem with mutt_ssl.c when compiling latest CVS version. An #if directive was comparing OPENSSL_VERSION_NUMBER against a constant that was missing a trailing zero. This caused a feature to be used that was not available in my version of OpenSSL. I have included below a patch that corrects the version number. Steven Skovran --- Index: mutt_ssl.c === RCS file: /home/roessler/cvs/mutt/mutt_ssl.c,v retrieving revision 2.5 diff -u -p -r2.5 mutt_ssl.c --- mutt_ssl.c 2001/02/23 09:13:53 2.5 +++ mutt_ssl.c 2001/03/01 20:10:57 @@ -303,7 +303,7 @@ int ssl_negotiate (sslsockdata* ssldata) int err; const char* errmsg; -#if OPENSSL_VERSION_NUMBER = 0x0090600 +#if OPENSSL_VERSION_NUMBER = 0x00906000L /* This only exists in 0.9.6 and above. Without it we may get interrupted * reads or writes. Bummer. */ SSL_set_mode (ssldata-ssl, SSL_MODE_AUTO_RETRY);
Changing Index Colors
How can I make new messages to me one color, and new messages in general another color? I also want old messages to me to be yet another color. Im trying... color indexcyandefault "(~p) ~N" color indexbrightcyan default "~p" color indexgreen default "~N" color indexbrightgreen default "~O" color indexred default "~D" thanks, -- Murray Maxwell Dancey, [EMAIL PROTECTED] icq. 106790920
Re: How to read mutt-users-digest
* [EMAIL PROTECTED] [EMAIL PROTECTED] [010301 21:44]: I have a question about your formail suggestion. The individual messages that make up the digest only have 2 headers: "From" and "Subject". So when I run formail, the resulting messages don't have anything unique that procmail can use to identify them as being from mutt-users. Other list's digests typically do one of two things: * Include other headers in the individual messages, such as "To" or "Cc", or * Prepend something to the subject, like "[wm-users] Original subject here". How do you handle this when using formail to split the mutt-users digest? The trick is to run formail from your .procmailrc. I'll post the example from the procmailex manpage: :0: * ^Subject:.*surfing.*Digest | formail +1 -ds surfing All messages containing "surfing" and "Digest" in the Subject: header (that condition should match the surfing list digests) are piped to formail which splits them, skipping what it considers the first message. The output, ie the separate messages, are appended to folder "surfing". So all the messages from one digest go into one mailbox. No more filtering is necessary. For mutt-users you would use something like: :0: * ^Subject:.*mutt-users-digest | formail +1 -ds mutt-users chris -- christian r. mollsthe rain descended, [EMAIL PROTECTED] and the floods came
Re: Changing Index Colors
* Murray Maxwell Dancey [EMAIL PROTECTED] [010301 23:51]: How can I make new messages to me one color, and new messages in general another color? I also want old messages to me to be yet another color. # messages to me (requires $alternates) color index cyan default ~p # new messages color index red default ~N # old messages to me color index green default "~p ~O" chris -- christian r. mollsthe rain descended, [EMAIL PROTECTED] and the floods came
still can't get off the list - sorry
Me again. I recevie the mutt-users list in digest form- and it has been a terrific help. But now I wish to unsubscribe. Steve Kennedy helped me out with the suggestion that I mail to [EMAIL PROTECTED] with unsubscribe in the body of the message, and I get a polite message telling me that I am NOT subscribed! I suppose one way would be to bounce the mail till the postmaster gets fed up and takes me off the list, but I'd rather do it properly. Can anyone tell what to do? Might be best to send the mail straight to me - the digest takes a day or to arrive. TIA Glyn M -- so here we are then http://members.tripod.co.uk/Christchurch2000uk Running Debian/Gnu Linux 9:05pm up 13:09, 2 users, load average: 0.01, 0.06, 0.05
Re: PS docs
* Alex Povolotsky [EMAIL PROTECTED] [13 Feb 01 12:41]: Does anyone have mutt manual in PS format, A4 page? I have converted the ANSI text into .sdw (StarOffice) whcih I would be pleased to send you. I use US Letter paper myself, but you could change that to A4. I hove no experience with printing to PostScript, but I am rather sure that StarOffice can do that. -- Good Hunting! Kipling+ (Linux Newbie since 24 Dec 00)
Re: still can't get off the list - sorry
On Thu, Mar 01, 2001 at 09:10:01PM +, Glyn Millington wrote: I recevie the mutt-users list in digest form- and it has been a terrific help. But now I wish to unsubscribe. Steve Kennedy helped me out with the suggestion that I mail to [EMAIL PROTECTED] with unsubscribe in the body of the message, and I get a polite message telling me that I am NOT subscribed! Try mutt-users-digest-request Steve -- NetTek Ltd tel +44-(0)20 7483 1169 fax +44-(0)20 7483 2455 Flat 2,43 Howitt Road, Belsize Park,London NW3 4LU mobile 07775 755503 Epage [EMAIL PROTECTED] [body only]
invalid preceding regular expression
I thought I would send this again, since there were no takers the first time. Hi all, I just changed boxes, copied my home directory to the new box, fired up mutt and things seem to be working well. However, I am seeing a message I have never seen before (or else I wasn't paying very good attention. I have also bumped my mutt version from 1.2.4 to 1.2.5 using one of the RPM packages. Mutt now reports: invalid preceding regular expression every time I start it or change mailboxes. Any clues would be appreciated. -- Stand Fast, tjg. Timothy Grant [EMAIL PROTECTED] Red Hat Certified Engineerwww.exceptionalminds.com Avalon Technology Group, Inc. (503) 246-3630 Linux, because rebooting is *NOT* normal
Re: Replying to From: address
On 03/01/01, 09:45:10PM +0100, Michael Tatge wrote: Dirk Laurie muttered: Is there a mutt function that lest me reply to the "From" address even when "Reply-To" is provided? For this purpose set ignore_list_reply_to. Maybe in combination with sent- or folder-hook. Hey this is cool. I'd missed this one for a couple of years. Thanks, Michael! John -- John P. Verel Norwalk, CT
