Re: slightly off topic: reformatting rude mail
On Fri, Dec 03, 1999 at 02:29:36PM -0600, Timothy Ball wrote: > Anyone got a way to reformat mail so that it's <80 cols? I figured this > was a common problem and someone would have a pre-made solution. > I use 'par' as my parameter formatting tool, which is very fancy and does all the jobs you like. It's controlled via an environment variable (PARINIT). PARINIT=rT4w70bgqR B=.?_A_a Q=_s>| This one will wrap my paragraphs at 70 characters, also it handels quoted text very well. Holger -- + PGP || GnuPG key -> finger [EMAIL PROTECTED] + +++ Debian/GNU Linux <[EMAIL PROTECTED]> +++ ICQ: 2882018 +++
Re: slightly off topic: reformatting rude mail
* Timothy Ball <[EMAIL PROTECTED]> wrote: > Anyone got a way to reformat mail so that it's <80 cols? I > figured this was a common problem and someone would have a > pre-made solution. Yup. Many good text editors have this functionality. I use jed, and wrap text at 64 characters, which is the width of my signature. To do this, I have mutt invoke jed with "jed -f mail_mode", and I've put the contributed mail mode sources in my jed scripts directory. There are a few reasons I picked jed: - It's like emacs, but... - It starts up fast. - It works well in a terminal, and has nice colors. - The paragraph-fill function respects quoting. (it wrapped your original message from 2 to 3 lines, and did all the quoting and formatting automatically) But use whatever you like. It can be a bit annoying at times to hit alt-q on each quoted paragraph I want to reformat, but it's much better than leaving it long or manually wrapping. _ _ _ _ ___ ___ "Use the source, Luke!"- ( \/ ( \/ (__ (__ ) | Scott Scriven (Toy Keeper / XYZZ)| \ / \ / // // | mailto:[EMAIL PROTECTED] | / \ / / //_ //_ | irc:serdevian.dyn.omnipotent.net | (_/\_(_/ (___(___) | http://www.vis.colostate.edu/~scriven/ |
Re: slightly off topic: reformatting rude mail
On Fri, Dec 03, 1999 at 02:29:36PM -0600, Timothy Ball wrote: > Anyone got a way to reformat mail so that it's <80 cols? I figured this > was a common problem and someone would have a pre-made solution. Well, you can probably use command line tools for this.. for instance, cat message | fold -sw 60 To strip off any linefeeds (0x0A), just add this into the equation: cat message | tr '\n' ' ' | fold -sw 60 That switches linefeeds for spaces.. It could [and probably will] garble your lines :) See the manpages for more. Caveat: this may screw up long header lines (see the In-Reply-To header in this message for instance.) Solution: Put it in a procmail filter. Both less work and more efficient. First, you create a file to use as a filter. ~/foofilter: :0 fhw | fold -sw 60 Then you either cat /var/spool/mail/foouser | procmail -m ~/foofilter (might want to copy your mailbox to some other file so you won't get 2 copies of every mail.) Now just see your Mail system's manual for information on how you can implement this, I believe you can simple ln -s ~/foofilter ~/.procmailrc for most mailers like Sendmail.. Regards, candy -- Never have so many owed so much to so few.. -- Winston Churchill PGP signature
slightly off topic: reformatting rude mail
Anyone got a way to reformat mail so that it's <80 cols? I figured this was a common problem and someone would have a pre-made solution. --timball -- Send mail with subject "send pgp key" for public key. pub 1024R/CFF85605 1999-06-10 Timothy L. Ball <[EMAIL PROTECTED]> Key fingerprint = 8A 8E 64 D6 21 C0 90 29 9F D6 1E DC F8 18 CB CD
Re: suggestion for sender-hook
On 03-Dec-1999, Aaron Schrab wrote: > At 15:51 -0600 02 Dec 1999, Ronny Haryanto <[EMAIL PROTECTED]> wrote: > > I still find it not trivial to do this: "If I am sending the message > > as , regardless of in which folder I am, then do this and > > that". > How are you modifying the From header? If you're using reverse name, > send-hooks work fine for this, at least in the development version > (there have been some changes in this area, so it might be different in > 1.0). reverse_name only works when you *reply* messages, not compose. FWIW, I'm modifying the "From:" header using my_hdr. Thanks, -- Ronny Haryanto
Re: Happy with mutt, but...
> The second is gpg (but is not gpg specific). I am sending my mail from my > laptop (sendmail), but receiving it from a POP3 server via > fetchmail/procmail. 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. Probably I have to make a send-hook to remove the bcc, so it only gets > saved locally? set record="+sent-mail-`date +%Y-%m`" you also will want to add an encrypt-to option in your .gnupg/options file to encrypt it to you as well. -b
Re: A hook for a separate compose window?
Hi, Thanks for your help, folks. This doesn't seem to be as simple as I thought. The ''A'' - trick is a good way to go around this. Is Mutt a "stateful" program in such a sense, that when writing a message, you can not do anything else with the "folder index" view? What a about changing the compose functionality so, that it would launch just a script that would then launch an editor with all the desired email header fields? After the composition, the script would continue and call mutt with just the "send email" flag? But would this isolate the new message from the Mutt functinalities like adding an attachment and using PGP? I think I will use the 'postpone' method like I did in Pine, or the 'Add message' method... OR I can always have two X-terms and one instance of Mutt in each of them. :-) Thanks for your help! Tom Thomas Roessler wrote: > > There is no simple solution for this; you'll have to start a new > instance of mutt, or you'll have to play a bit with postpone/reply. > > On 1999-12-02 11:58:48 +0200, Tom Weckström wrote: > > Date: Thu, 2 Dec 1999 11:58:48 +0200 (EET) > > From: Tom Weckström <[EMAIL PROTECTED]> > > To: [EMAIL PROTECTED] > > Subject: A hook for a separate compose window? > > > > > > > > Hi, > > > > I would not like to reinvetn the wheel, and I am sure someone has already > > done this: > > > > I need a hook to have a separate compose window when composing a new > > message. At the same time I need to be able to view the messages in my > > folders (e.g. to gather some more information about the issue at hand) > > > > I browsed through a couple of example configs but couldn't find any hint > > for this kind of a hook. I am quite a beginner with Mutt, so help would be > > greatly appreciated. > > > > Please respond to my own email address, too. I am not a member on the > > mutt-users list. > > > > Thanks in advance! :-) > > > > > > Tom > > > > > > > > -- > > Tom Weckström [EMAIL PROTECTED] > > Otakaari 20 B 39Helsinki University of Technology > > 02150 Espoo Department of Computer Science > > 09-4683249/040-5642709 http://www.niksula.cs.hut.fi/~tweckstr > > > > -- > http://www.guug.de/~roessler/ -- Tom Weckström [EMAIL PROTECTED] Otakaari 20 B 39Helsinki University of Technology 02150 Espoo Department of Computer Science 09-4683249/040-5642709 http://www.niksula.cs.hut.fi/~tweckstr
Happy with mutt, but...
Hello, I have just downloaded and compiled the newest version of mutt and gpg. They work fine together, but I was not able to configure everything well. I am Hungarian, so I would like to use accented letters (8 bit). I inserted set allow_8bit and set charset="iso-8859-2" into .muttrc, but nothing happened. I do I do this well? The second is gpg (but is not gpg specific). I am sending my mail from my laptop (sendmail), but receiving it from a POP3 server via fetchmail/procmail. 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. Probably I have to make a send-hook to remove the bcc, so it only gets saved locally? Thanks, Zsombor (private reply as well, please) -- Zsombor Gergely Junior Research Fellow Hungarian Academy of Sciences, Institute of Economics Phone: (36-1) 309-2659 P.O. Box 262, H-1112 Budapest, Hungary Fax: (36-1) 319-3136
An error in the manual
The manual says: To subscribe to one of the following mailing lists, send a message with the word subscribe in the subject to [EMAIL PROTECTED] ^^^ Majordomo says: Commands must be in message BODY, not in HEADER. Commands in the "Subject:" line are NOT processed. Best Regards, Marius Gedminas -- Those who don't understand Linux are doomed to reinvent it, poorly.
Bug report on mutt 1.0
Hello,
I just compiled and installed mutt 1.0 (upgrading from mutt 1.0pre4)
and discovered a small bug in the use of colors. The 'default' color is
not recognized anymore. As a result, a lot of color settings I use are
now considered invallid :(
Below you find the output of 'mutt -v' for mutt 1.0pre4 followed by
the output of mutt 1.0:
Mutt 1.0pre4i (1999-10-11)
Copyright (C) 1996-9 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.
System: SunOS 5.6 [using ncurses 5.0]
Compile options:
-DOMAIN
-HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK
-USE_IMAP -USE_POP -HAVE_REGCOMP +USE_GNU_REGEX +HAVE_COLOR
+HAVE_PGP5 +HAVE_PGP2 -BUFFY_SIZE
-EXACT_ADDRESS +ENABLE_NLS
SENDMAIL="/usr/lib/sendmail"
MAILPATH="/var/mail"
SHAREDIR="/home/upz/share/mutt"
SYSCONFDIR="/home/upz/etc"
ISPELL="/swuser/bin/ispell"
_PGPPATH="/home/upz/bin/pgp"
_PGPV2PATH="/home/upz/bin/pgp"
_PGPV3PATH="/home/upz/bin/pgp"
To contact the developers, please mail to <[EMAIL PROTECTED]>.
Mutt 1.0i (1999-10-22)
Copyright (C) 1996-9 Michael R. Elkins and others.
Mutt comes with ABSOLUTELY NO WARRANTY; for details type `mutt -vv'.
Mutt is free software, and you are welcome to redistribute it
under certain conditions; type `mutt -vv' for details.
System: SunOS 5.6 [using ncurses 5.0]
Compile options:
-DOMAIN
-HOMESPOOL -USE_SETGID +USE_DOTLOCK +USE_FCNTL -USE_FLOCK
-USE_IMAP -USE_POP -HAVE_REGCOMP +USE_GNU_REGEX +HAVE_COLOR
+HAVE_PGP5 +HAVE_PGP2 -BUFFY_SIZE
-EXACT_ADDRESS +ENABLE_NLS
SENDMAIL="/usr/lib/sendmail"
MAILPATH="/var/mail"
SHAREDIR="/home/upz/share/mutt"
SYSCONFDIR="/home/upz/etc"
ISPELL="/swuser/bin/ispell"
_PGPPATH="/home/upz/bin/pgp"
_PGPV2PATH="/home/upz/bin/pgp"
_PGPV3PATH="/home/upz/bin/pgp"
To contact the developers, please mail to <[EMAIL PROTECTED]>.
Greetings,
Peter van der Zanden.
:{)
P.s. I am NOT subscribed to [EMAIL PROTECTED]
--
Senseless sentence: VHF and UHF TVs for unix hackers wearing sneakers
watching Tie-fighter battles instead of white noise.
Peter van der Zanden phone: +31-(0)40 230 47 07
ASML, Veldhoven, the Netherlandse-mail: [EMAIL PROTECTED]
Re: Multiple Personalities
On Thu, 02 Dec 1999, 18:44, Robert Chien wrote: Hi Robert, > > Now when I reply to a message sent to [EMAIL PROTECTED], the custom > > headers (From, Reply-To and Organization) and other settings for > > [EMAIL PROTECTED] should be used. > Check out section 4.4 on "Using Hooks" > http://www.mutt.org/doc/manual/manual-4.html#ss4.4 Got it; I'll check it out. > Depending on your situation, hooks can be tricky. I noticed :) > A general > rule-of-thumb is to remember that hooks are "sticky". In > most cases, you want to set up a default hook. Read the > manual, it should help. Thanks. I'll do that and let you know what I found. Ray -- [EMAIL PROTECTED] ICQ: 2987375
Re: s(ave) default mbox
On Fri, Dec 03, 1999 at 05:56:47AM -0700, Charles Curley wrote: > Yes, it's a very lame excuse. Some of us also barely have time to read a > newspaper, never mind do your research for you. I for one would like to > see some evidence that you have done a bit of research before you ask the > list. off topic, but its interesting... Its not my intention to let other people do the research that i should have done myself, but i know there are ppl who know these things by heart so whats wrong asking them? Next time someone else asks, ik can answer this question to him/her too, and i will :-) jan
Re: s(ave) default mbox
Yes, it's a very lame excuse. Some of us also barely have time to read a newspaper, never mind do your research for you. I for one would like to see some evidence that you have done a bit of research before you ask the list. Also, while we are on netiquette, I would appreciate it if people would follow Jan's example below: post solutions or confirm correct solutions to the list so that they end up in the archive. The archive should be a tool people can use before asking the list. On Fri, Dec 03, 1999 at 11:49:27AM +0100, Jan Houtsma wrote: -> On Fri, Dec 03, 1999 at 11:32:37AM +0200, Mikko Hänninen wrote: -> > Jan Houtsma <[EMAIL PROTECTED]> wrote on Fri, 03 Dec 1999: -> > > Can i change this default in muttrc that any email from person -> > > 'xxx' should always be going to mailbox '=school' ?? -> > -> > save-hook xxx =school -> -> Thanks! -> -> > -> > Or something like that, read the manual for more info on save-hooks. -> > -> -> i know i know. I hardly have time to read the newspaper at the moment. -> Its a lame excuse i know. But sometimes its easier if someone can just -> immedeiatelly tell you by head than to read a whole document :-) -> -> jan -- -- C^2 No windows were crashed in the making of this email. Looking for fine software and/or web pages? http://w3.trib.com/~ccurley
Re: send_charset does not work for Subject line
On 1999-12-03 13:58:34 +0200, Marius Gedminas wrote:
> I send a letter to myself and include some iso-8859-13 characters
> both in the body and in the Subject line. I get these headers:
> Subject: =?iso-8859-13?Q??=
> Content-Type: text/plain; charset=iso-8859-4
> Now the bug is this: the characters in *are* translated to
> iso-8859-4, but Mutt says they're in iso-8859-13.
The attached patch should help.
--
http://www.guug.de/~roessler/
Index: rfc2047.c
===
RCS file: /home/roessler/cvsroot/mutt/rfc2047.c,v
retrieving revision 2.6
diff -u -u -r2.6 rfc2047.c
--- rfc2047.c 1999/08/20 08:24:02 2.6
+++ rfc2047.c 1999/12/03 12:19:11
@@ -44,7 +44,7 @@
if(hibit)
{
snprintf (charset, sizeof (charset), "=?%s?Q?",
- mutt_strcasecmp ("us-ascii", Charset) == 0 ? "unknown-8bit" :
NONULL(Charset));
+ mutt_strcasecmp ("us-ascii", send_charset) == 0 ? "unknown-8bit" :
+NONULL(send_charset));
}
else
strfcpy(charset, "=?us-ascii?Q?", sizeof(charset));
send_charset does not work for Subject line
Scenario (Mutt-1.1.1i): set charset=iso-8859-13 set send_charset=iso-8859-4 I send a letter to myself and include some iso-8859-13 characters both in the body and in the Subject line. I get these headers: Subject: =?iso-8859-13?Q??= Content-Type: text/plain; charset=iso-8859-4 Now the bug is this: the characters in *are* translated to iso-8859-4, but Mutt says they're in iso-8859-13. Best Regards, Marius Gedminas -- In order to get a loan you must first prove you don't need it. P.S. I just switched to Mutt-1.1.1 and, of course, forgot that `lists' command changed semantics... So my other mail about an error in the manual (which incorrectly states to send the word `subscribe' in the subject instead of the body to mutt-*[EMAIL PROTECTED]) went straight to the moderator for approval.
Re: index colors
On Thu, Dec 02, 1999 at 04:05:49PM -0600, Jeremy Blosser wrote:
> > Subject: this is the subject
> > ^^^
> > this is highlighted
>
> This is yet another concept from the ones discussed above. Just so we keep
> track of what's being talked about, there have been 3 color issues
> mentioned so far:
>
> 1) Q: Can Mutt color different parts of the same line different colors in the
> message index?
>A: No.
>
> 2) Q: Can Mutt color different headers different colors in the pager?
>A: Yes.
>
> and now we have:
>
> 3) Q: Can Mutt color different parts of the same header line different
> colors in the pager?
>A: No.
Let's add another one:
4) Q: Can Mutt color different parts of the header like it can do with
the body (color body foo bar regexp)?
A: No.
(3) is very similar to (4) and could be accomplished like this:
color header color2 ... ^Subject:.*$
color header-part color1 ... ^Subject:
color header-part color3 ... my@email\.address # to show it's more
# powerful ;)
Would result in this:
Subject: foo bar [EMAIL PROTECTED] baz
color1 color3
Everything else is in color2.
It would be pretty easy to implement. I think. A patch is attached.
Well, maybe not that easy. The problem is that MT_COLOR_HEADER
overloads syntax[0].color for its default color. And continuation lines
use syntax[0].first/last for their own purposes.
I added a new field to the syntax_t structure (int def_color) to
overcome the first problem. And I think the second is not really a
problem because continuation lines are already successfully used with
syntax chunks in the body. However I'm not sure if these two lines are
needed for anything else besides providing default color for
MT_COLOR_HEADER:
pager.c line 306 (after applying my patch), function append_line:
(lineInfo[n+1].syntax)[0].color = (lineInfo[n].syntax)[0].color;
pager.c line 713, function resolve_types:
(lineInfo[n].syntax)[0].color = (lineInfo[n-1].syntax)[0].color;
A patch is included (against vanilla mutt-1.1.1i). This is my first try
to hack mutt, so I'd appreciate comments. I should have probably
subscribed to mutt-dev before sending patches, but this one was not
planned. After writing "it would be pretty easy to implement", I
decided to check if this was really so ;)
Marius Gedminas
--
I doubt, therefore I might be.
diff -urN mutt-1.1.1.orig/color.c mutt-1.1.1/color.c
--- mutt-1.1.1.orig/color.c Wed Jul 7 00:40:25 1999
+++ mutt-1.1.1/color.c Fri Dec 3 12:47:47 1999
@@ -29,6 +29,7 @@
int ColorQuoteUsed;
int ColorDefs[MT_COLOR_MAX];
COLOR_LINE *ColorHdrList = NULL;
+COLOR_LINE *ColorHdrPartList = NULL;
COLOR_LINE *ColorBodyList = NULL;
COLOR_LINE *ColorIndexList = NULL;
@@ -82,6 +83,7 @@
{ "tilde", MT_COLOR_TILDE },
{ "markers", MT_COLOR_MARKERS },
{ "header", MT_COLOR_HEADER },
+ { "hdrpart", MT_COLOR_HDRPART },
{ "body",MT_COLOR_BODY },
{ "message", MT_COLOR_MESSAGE },
{ "attachment", MT_COLOR_ATTACHMENT },
@@ -679,7 +681,8 @@
/* extract a regular expression if needed */
- if (object == MT_COLOR_HEADER || object == MT_COLOR_BODY || object ==
MT_COLOR_INDEX)
+ if (object == MT_COLOR_HEADER || object == MT_COLOR_HDRPART ||
+ object == MT_COLOR_BODY || object == MT_COLOR_INDEX)
{
if (!MoreArgs (s))
{
@@ -714,6 +717,8 @@
if (object == MT_COLOR_HEADER)
r = add_pattern (&ColorHdrList, buf->data, 0, fg, bg, attr, err,0);
+ else if (object == MT_COLOR_HDRPART)
+r = add_pattern (&ColorHdrPartList, buf->data, 1, fg, bg, attr, err, 0);
else if (object == MT_COLOR_BODY)
r = add_pattern (&ColorBodyList, buf->data, 1, fg, bg, attr, err, 0);
else if (object == MT_COLOR_INDEX)
diff -urN mutt-1.1.1.orig/doc/manual.sgml.head mutt-1.1.1/doc/manual.sgml.head
--- mutt-1.1.1.orig/doc/manual.sgml.headThu Sep 23 23:01:43 1999
+++ mutt-1.1.1/doc/manual.sgml.head Fri Dec 3 12:47:37 1999
@@ -949,8 +949,9 @@
body (match bold (hiliting bold patterns in the body of messages)
error (error messages printed by Mutt)
-header (match header (match hdrdefault (default color of the message header in the pager)
+hdrpart (match index (match indicator (arrow or bar used to indicate the current item in a menu)
markers (the ``+'' markers at the beginning of wrapped lines in the pager)
diff -urN mutt-1.1.1.orig/doc/muttrc.man.head mutt-1.1.1/doc/muttrc.man.head
--- mutt-1.1.1.orig/doc/muttrc.man.head Wed Aug 18 08:54:13 1999
+++ mutt-1.1.1/doc/muttrc.man.head Fri Dec 3 12:47:47 1999
@@ -132,8 +132,8 @@
If your terminal supports color, these commands can be used to
assign \fIforeground\fP/\fIbackgound\fP combinations to certain
objects. Valid objects are:
-.BR attachment ", " body ", " bold ", " header ", "
-.BR hdrde
Re: s(ave) default mbox
On Fri, Dec 03, 1999 at 11:32:37AM +0200, Mikko Hänninen wrote: > Jan Houtsma <[EMAIL PROTECTED]> wrote on Fri, 03 Dec 1999: > > Can i change this default in muttrc that any email from person > > 'xxx' should always be going to mailbox '=school' ?? > > save-hook xxx =school Thanks! > > Or something like that, read the manual for more info on save-hooks. > i know i know. I hardly have time to read the newspaper at the moment. Its a lame excuse i know. But sometimes its easier if someone can just immedeiatelly tell you by head than to read a whole document :-) jan
Re: s(ave) default mbox
Jan Houtsma <[EMAIL PROTECTED]> wrote on Fri, 03 Dec 1999: > Can i change this default in muttrc that any email from person > 'xxx' should always be going to mailbox '=school' ?? save-hook xxx =school Or something like that, read the manual for more info on save-hooks. Regards, Mikko -- // Mikko Hänninen, aka. Wizzu // [EMAIL PROTECTED] // http://www.iki.fi/wiz/ // The Corrs list maintainer // net.freak // DALnet IRC operator / // Interests: roleplaying, Linux, the Net, fantasy & scifi, the Corrs / Don't you hate it when life doesn't follow the manuals?
Re: Odd problem when bouncing a message from an IMAP server
On Thu, Dec 02, 1999 at 04:54:19PM +, Chris Green wrote: > On Thu, Dec 02, 1999 at 05:37:33PM +0100, Thomas Roessler wrote: > > On 1999-12-02 15:20:54 +, Chris Green wrote: > > > > > I've found out that the same occurs when bouncing messages from > > > other non-inbox folders on my local drive. Bouncing a message > > > from my inbox is OK though. > > > > Is it remotely possible that your mail system looks at the "Date" > > header of messages and makes problems when that one is too far in > > the past? > > > I suppose that's possible but it seems unlikely, I'll try manually > fudging a message to look as if it's in the past though. This is a > pretty straightforward Solaris 2.6 system in a large installation. > Hmph! "it seems unlikely" but you're right, the stupid MTA at my work is rejecting the message. I've tried both in to work and out from work and in both cases the message gets bounced by the same MTA. Sending a message in to work it negotiates all the intermediate systems between here (x-1.net) and my work and then gets bounced there so the generality of MTAs don't bounce a message with an 'old' Date: header. Is there any clever trick I can do in mutt to 'bounce' a message but with a new Date: header? The whole point of the exercise is to effectively forward a message somewhere else with the minimum of keystrokes. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
s(ave) default mbox
If i receive an email from say person 'xxx' and i wanna save that message i press 's'. This defaults to mailbox '=xxx'. Can i change this default in muttrc that any email from person 'xxx' should always be going to mailbox '=school' ?? thanks, jan
Re: suggestion for sender-hook
At 15:51 -0600 02 Dec 1999, Ronny Haryanto <[EMAIL PROTECTED]> wrote: > I still find it not trivial to do this: "If I am sending the message > as , regardless of in which folder I am, then do this and > that". How are you modifying the From header? If you're using reverse name, send-hooks work fine for this, at least in the development version (there have been some changes in this area, so it might be different in 1.0). -- Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/ Bus error -- please leave by the rear door.
