Re: mutt+imap
On Mon, Jan 18, 1999 at 01:35:53PM +0100, Markus Hofmann wrote: > Quoting Heikki Kantola <[EMAIL PROTECTED]>: > > According to Markus Hofmann <[EMAIL PROTECTED]>: > > > i'm trying to read mails from a M$-Exchange Server with imap. it works > > > but the german-umlauts aren't displayed correctly. > > > > How are those shown? > > something like '=20D'. > > the header seems to be correct: > MIME-Version: 1.0 > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable Looks ok. > > > > > > any hints? > > > > If those 8-bit characters appear as question marks there's at least > > two possiblities: > > 1) The messages you're reading have faulty character set (eg. us-ascii > > instead of ISO Latin 1) defined in MIME headers. > > 2) If MIME-headers are ok, then it can be that you've compiled Mutt on > > system with broken locale support, if that's the case recompile Mutt > > with "--enable-locales-fix" configure switch. > > I've compiled it with --enable-locales-fix but the problem is still > there. btw. I'm using linux 2.0.35 (suse 5.3). The mail is not decoded, i.e. mutt is obviously unable to recognize the header correctly. Although the snippet above looks good, it is possible that the mail is of type multipart and something wrong with it (I actually saw broken mails from M$-Exchange this way). Please send us a copy of the header and, if there, the MIME frame of the relevant mail part (you can anonymize private content), then we'll see ... Gero -- > Hi! I'm Signature Virus 99! Copy me into your signature and join the fun!
Re: mutt & pgp
Warning Could not process message with given Content-Type: multipart/signed; boundary=nqkreNcslJAfgyzk; micalg=pgp-md5;protocol="application/pgp-signature"
from address
ok I know that set hostname changes the domain name in the from: field but how do you change the username? -- Brian Bray | Mutt 0.95i (1998-12-12) [EMAIL PROTECTED][EMAIL PROTECTED] | Copyright (C) 1996-8 Michael R. Elkins and others System: Debian Linux 2.0.35 | Mail on Steroids IMHO
Suggestions for mutt?
I have a suggestion for mutt in the future, and this is the only place I can think to send it. By the way, thanks to those who helped me fix that problem with my headers. I've gotten it to do everything the way I want it, (if this mail ever gets where it's supposed to go) On rare occasions, because of some problem with sendmail, or whatever it might be, mutt hangs while it trys to send a mail and goes to a blank screen normally the switch back is instantaneous, but when somethings up with yoru mailer, it can hang for 4-5 secs. It would be cool if mutt did something about that...i.e. forked a copy of itself to send the mail while presentin g the UI back to the user as the mail just sent was being mailed, etc. Just a suggestion. :) -- David Allen http://members.xoom.com/uruk/index.html When I say the magic word to all these people, they will vanish forever. I will then say the magic words to you, and you, too, will vanish -- never to be seen again. -- Kurt Vonnegut Jr., "Between Time and Timbuktu"
Re: Suggestions for mutt?
David Allen <[EMAIL PROTECTED]> wrote: > > When something;s up with your mailer, it can hang for 4-5 secs. It > would be cool if Mutt did something about that...i.e. forked a copy > of itself to send the mail while presenting the UI back to the user as > the mail just sent was being mailed, etc. What a great idea. From the manual: 6.3.136. sendmail_wait Type: number Default: 0 Specifies the number of seconds to wait for the ``sendmail'' process to finish before giving up and putting delivery in the background. Mutt interprets the value of this variable as follows: >0 number of seconds to wait for sendmail to finish before continuing 0 wait forever for sendmail to finish <0 always put sendmail in the background without waiting Note that if you specify a value other than 0, the output of the child process will be put in a temporary file. If there is some error, you will be informed as to where to find the output. -- 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 Convex Division |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
attaching multiple files in one go
Hi mutt I have a list of files in a dir that are showing up in the attachment select file view. How do I tag all of them (or perhaps even by filemask select some) and then attach them _all_ with a single command. In my experimentation I pressed to get xv with the image of the target file slam up on the screen - mutt is a thrill a minute thanx mutt -- Eric Smith ([EMAIL PROTECTED]) Tel 0027 82 780 7888 (vodacom)
mutt+imap
i'm trying to read mails from a M$-Exchange Server with imap. it works but the german-umlauts aren't displayed correctly. any hints? markus
Re: mutt+imap
According to Markus Hofmann <[EMAIL PROTECTED]>: > i'm trying to read mails from a M$-Exchange Server with imap. it works > but the german-umlauts aren't displayed correctly. How are those shown? > any hints? If those 8-bit characters appear as question marks there's at least two possiblities: 1) The messages you're reading have faulty character set (eg. us-ascii instead of ISO Latin 1) defined in MIME headers. 2) If MIME-headers are ok, then it can be that you've compiled Mutt on system with broken locale support, if that's the case recompile Mutt with "--enable-locales-fix" configure switch. -- Heikki "Hezu" Kantola, <[EMAIL PROTECTED]> Lähettämällä mainoksia tai muuta asiatonta sähköpostia yllä olevaan osoitteeseen sitoudut maksamaan oikolukupalvelusta FIM500 alkavalta tunnilta.
Re: mutt+imap
Quoting Heikki Kantola <[EMAIL PROTECTED]>: > According to Markus Hofmann <[EMAIL PROTECTED]>: > > i'm trying to read mails from a M$-Exchange Server with imap. it works > > but the german-umlauts aren't displayed correctly. > > How are those shown? something like '=20D'. the header seems to be correct: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable > > > any hints? > > If those 8-bit characters appear as question marks there's at least > two possiblities: > 1) The messages you're reading have faulty character set (eg. us-ascii > instead of ISO Latin 1) defined in MIME headers. > 2) If MIME-headers are ok, then it can be that you've compiled Mutt on > system with broken locale support, if that's the case recompile Mutt > with "--enable-locales-fix" configure switch. I've compiled it with --enable-locales-fix but the problem is still there. btw. I'm using linux 2.0.35 (suse 5.3). regards, markus
Re: comments on 0.95.1i
Adam M. Costello on Sat, Jan 16, 1999 at 03:45:58AM +: > In the pager, next-line and previous-line appear to repaint the entire > screen instead of scrolling it. Scrolling it would be a lot faster. > The same might be true for the index. This may be dependent on your curses implementation (I don't know about slang). For ncurses-4.2, a number of development/experimental options have to be explicitly compiled in for it to work optimally with mutt (scrolling was one of these issues). If I gather correctly, linking to slang instead solves some or all of these problems as well. But, I don't use slang. > The documentation says nothing about the dangers (or lack thereof) of > running multiple instances of Mutt. How about running two Mutts on > different machines accessing the same spool file via NFS? Appropriate locking needs to be compiled in; usually configure will take care of this. Mutt does seem to have code for multiple instances manipulating the same mailbox, and re-reads to update after a mailcheck (I use buffy-size compile time option; default is atime check), and will interacts properly AFAICT. > When Mutt is suspended and resumed, it sometimes ends up in a bad > state. I think the terminal is no longer in non-canonical (raw) mode, > because Mutt doesn't react to my keystrokes until I press return. Again this may be the cursor library. I have also noticed, though, that mutt -> urlview -> lynx, suspended, will invariably leave the result in a strange state. > It would be nice to have a function for the index screen that causes a > check for new mail to happen right now (like the inc command of > mailx). One would then have the option of setting mail_check to a > larger (possibly infinite) value. Sync. Default is `$'. > When Mutt first starts up, the index is scrolled so that the selection > is at the bottom of the window, but it would be nicer if it were in > the middle of the window. Sometimes after I change folders the index > is scrolled so that only the last item is shown, at the top of the > window. Again, it would be nicer if the selected item started out in > the middle of the window. Setting pager_context high enough might do it. > I hate tabs because they're rendered differently in different > environments, I love tabs because one can use their preferred indent length. If it appears wrong you simply change the tab stops. It's also easy to change source that uses tabs since they are only single characters. I've always thought using spaces is ugly, except for in places where you want to guarantee the appearance regardless of the viewer and its ability to compensate (ie, in a source file, use tabs; in a mail post of that source, use spaces, or enough tabs that either 4 or 8-space tab stops can be used). It's also a lot less space taken up in the actual file. > so text that looks aligned in one environment will look misaligned in > another. I make it a policy never to use tabs (except in Makefiles, > where it's required). Mutt uses tabs to fold long header fields, so I > edited the source to make it use spaces instead: It may be required by the RFCs (if you're talking about things like receive, etc). Might be worth a look. -- Scott
Re: comments on 0.95.1i
: > When Mutt first starts up, the index is scrolled so that the selection : > is at the bottom of the window, but it would be nicer if it were in : > the middle of the window. Sometimes after I change folders the index : > is scrolled so that only the last item is shown, at the top of the : > window. Again, it would be nicer if the selected item started out in : > the middle of the window. : Setting pager_context high enough might do it. This problme doesn't involve pager_context and is osmehting that was reported to mutt-dev a month or so ago (I think). As of yet I don't think nayhting has happened with it. randy -- Five hundred, twenty-five thousand six hundred minutes, how do you measure...? [EMAIL PROTECTED] http://www.louisville.edu/~rjmill01/ Triangle Fraternity http://www.louisville.edu/rso/triangle/ Golden Key National Honor Society http://www.louisville.edu/rso/goldenkey/
Re: Bugs in bind / help screen [was: comments on 0.95.1i]
: > There is apparently no way to truly unbind a key. Binding it to : > noop does not allow it to fall through to the generic map. I'm : > currently working around this by creating bindings that duplicate : > the generic bindings. : Thats right. binding a key to 'noop' unbinds that key. Why do you : expect it to "fall through" to the generic map? What exactly are you : trying to do? Try the following experiment: :bind index noop Notice that when you hit return, you get "Key not bound", but when you look at help, it says that is bound to select-entry (in the generic bindings section). Another experiment: :bind index next-line Notice it works just like you think it should. Look at the help again. Notice that is bound twice. Once in the generic section and one in the index section. Both of these seem really counter intuitive. randy -- Five hundred, twenty-five thousand six hundred minutes, how do you measure...? [EMAIL PROTECTED] http://www.louisville.edu/~rjmill01/ Triangle Fraternity http://www.louisville.edu/rso/triangle/ Golden Key National Honor Society http://www.louisville.edu/rso/goldenkey/
Re: comments on 0.95.1i
Adam M. Costello <[EMAIL PROTECTED]> wrote: > > The suspend variable causes Mutt to ignore the susp key (usually > ctrl-Z) the first time I press it, but not the second time. After > this is fixed, check whether Mutt will also ignore the dsusp key > (usually ctrl-Y). I run Mutt from a shell script that disables the susp and dsusp keys, so that I don't end up suspending Mutt by mistake. > It would be nice to have a function for the index screen that causes a > check for new mail to happen right now (like the inc command of > mailx). For me, Mutt checks for mail whenever I press any key in the index. Is this not what you want? > When Mutt first starts up, the index is scrolled so that the selection > is at the bottom of the window, but it would be nicer if it were in > the middle of the window. Sometimes after I change folders the index > is scrolled so that only the last item is shown, at the top of the > window. Again, it would be nicer if the selected item started out in > the middle of the window. Mutt tends to model Elm in this respect. It treats each group of messages as a "screen's" worth. Say, if your screen can hold 20 lines of index, then the group of messages will be broken into groups of 20, and each group is displayed as distinctly as possible, even if there is only one message in each group. Those of us who are old Elm users are used to this behavior. It seems that other users may not find this intuitive or logical. I thought I recalled someone writing a function or patch to change this behavior, but I can't seem to find it now. > It would be nice if Mutt, when it executes the bind and macro > commands, would notice if a character is a tty special character and > reconfigure the tty to disable that character. I simply disable those characters before running Mutt, using my shell script approach. This doesn't /need/ to be in 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 Convex Division |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Re: mutt & pgp
Well just one more time :))) On Mon, Jan 18, Thomas Roessler wrote: > On Mon, Jan 18, 1999 at 04:14:54PM +, SteelOnIce wrote: > > > When I use Mutt together with pgp it attaches my signatures and / > > or encrypted mails as files... I want the pgp message to be the > > main message body! How can I change that??? > > Not at all. Mutt generates MIME-encapsulated PGP messages as > defined in RFC 2015. Putting PGP information into a message's body > leads to problems with content type and character set tagging, and > it leads to problems with software which is MIME, but not PGP aware. Hmm... all I want to do is send a plain text message, which contains the pgp message NO ATACHMENTS... Why does that lead to content problems? I recived Mails containing a pgp sig. at the bottom before... or Mails, where all I can see in the message is that pgp stuff. I never had any problems... But Mutt sends attachments... people are already copmplaining about that! There got to be a way!!! Thanks again Andy -- "Nothing can be loved or hated unless it is first understood" Leonardo da Vinci 1452 - 1519 > Hi! I'm Signature Virus 99! Copy me into your signature and join the fun!
Re: comments on 0.95.1i
(This message responds to several in the thread.) I had said: > In the pager, next-line and previous-line appear to repaint the entire > screen instead of scrolling it. Scrolling it would be a lot faster. > The same might be true for the index. Scott McDermott <[EMAIL PROTECTED]> replied: > This may be dependent on your curses implementation (I don't know > about slang). For ncurses-4.2, a number of development/experimental > options have to be explicitly compiled in... That was indeed the problem: rebuilding ncurses-4.2 with --enable-hashmap fixed it. The suspend/resume problem went away earlier, when I switched from Solaris curses to ncurses. > > It would be nice to have a function for the index screen that causes a > > check for new mail to happen right now (like the inc command of > > mailx). > > Sync. Doh, of course. I had been thinking of that function as "write my changes back to the file", without realizing that even if I've made no changes, it syncs in both directions. > > Mutt uses tabs to fold long header fields, so I edited the source to > > make it use spaces instead: > > It may be required by the RFCs (if you're talking about things like > receive, etc). RFC 822 regards spaces and tabs as equivalent. Vikas Agnihotri <[EMAIL PROTECTED]> wrote: > folder-hook . 'push ' Excellent, thank you. > Remember that you can use the token '' only in the 'macro' > command, not the 'bind' command. 'bind'. expects the RHS to be Mutt > _functions_. I was referring to the LHS, for example: bind index previous-page This started working when I switched from Solaris curses to ncurses. Before that I had to use \cH instead of . > > It would be nice if I could override the tty special characters via > > bind and macro commands. > > Hm. I would like this also. Is this even possible? vi and less both use ctrl-Y as a normal key even if it's the tty's dsusp character. I don't know enough about termio and curses to guess what they're doing. David DeSimone <[EMAIL PROTECTED]> wrote: > For me, Mutt checks for mail whenever I press any key in the index. > Is this not what you want? That sounds great. I didn't know this was happening (it's not documented). I thought it was only using the mail_check timeout. > > It would be nice if Mutt, when it executes the bind and macro > > commands, would notice if a character is a tty special character and > > reconfigure the tty to disable that character. > > I simply disable those characters before running Mutt, using my shell > script approach. This doesn't /need/ to be in Mutt. There are four tty special characters that generate signals: intr, quit, susp, and dsusp. Suppose one wanted to allow the susp key to suspend mutt, but wanted the keys normally bound to intr, quit, and dsusp to do other things in mutt. Invoking mutt from a shell script that first disables those characters, then restores them after mutt returns, almost gives the correct behavior, but not quite, because after you suspend mutt the other special keys are still disabled. AMC
Re: mutt & pgp
On Mon, Jan 18, 1999 at 07:04:33PM +, SteelOnIce wrote: > Hmm... all I want to do is send a plain text message, which > contains the pgp message NO ATACHMENTS... Why does that lead to > content problems? I recived Mails containing a pgp sig. at the > bottom before... or Mails, where all I can see in the message is > that pgp stuff. I never had any problems... But Mutt sends > attachments... people are already copmplaining about that! There > got to be a way!!! Think character sets. -- Thomas Roessler · 74a353cc0b19 · dg1ktr · http://home.pages.de/~roessler/ 2048/CE6AC6C1 · 4E 04 F0 BC 72 FF 14 23 44 85 D1 A1 3B B0 73 C1 > Hi! I'm Signature Virus 99! Copy me into your signature and join the fun!
Re: Bugs in bind / help screen [was: comments on 0.95.1i]
Vikas Agnihotri <[EMAIL PROTECTED]> wrote: > There seems to be some confusion regarding the 'generic' map. Indeed. Is "bind generic" just shorthand for "bind pager", "bind alias", "bind attach"... ? Or is there really a separate generic map, and mutt thinks "X was just pressed, but X is not bound in the current map, so let's consult the generic map"? I've been assuming the latter, and the help screen suggests that there really is a generic map. > Guess the manual needs to explain all this better. Even if the manual is improved, the help screen strangeness that Randy described is also a concern. By the way, here's what I'm doing that prompted my original comment: I'm totally redoing all the keybindings. What I really wanted was something like "unbind_all compose" or "unbind_all *" so I could start from a clean slate. The next best thing would be "unbind compose X". Then I could unbind each key listed in the manual to get my clean slate, and redo each menu separately. But I can't unbind keys, so for each key I don't to include in a map, I have to check whether it's bound in the generic map, and if so, bind it to the same function, otherwise bind it to noop. So if I ever change the generic map, I have to update all the other maps to stay consistent with it. AMC
Re: comments on 0.95.1i
On Mon, Jan 18, 1999, David DeSimone ([EMAIL PROTECTED]) said: | | Mutt tends to model Elm in this respect. It treats each group of | messages as a "screen's" worth. Say, if your screen can hold 20 lines | of index, then the group of messages will be broken into groups of 20, | and each group is displayed as distinctly as possible, even if there is | only one message in each group. | | Those of us who are old Elm users are used to this behavior. It seems | that other users may not find this intuitive or logical. I thought I | recalled someone writing a function or patch to change this behavior, | but I can't seem to find it now. Yes, I did. Last time it was posted was somewhere around the .85-.88 timeframe. One of these days, I'll update from 0.88.14i, to the current revision, and update all my patches, which I'm fairly sure will need considerable tweaking ... which is, of course, why I'm still running the down-level version. /kim
Re: comments on 0.95.1i
On Sat, Jan 16, 1999, Adam M. Costello ([EMAIL PROTECTED]) said: | | In the index, half-up and half-down behave strangly near the top and | bottom. Usually, they scroll the viewable region without affecting | the selection, unless the selection is scrolled out of the window, | in which case the selection is moved as little as possible in order | to make it visible. But when the first (for half-up) or last (for | half-down) entry is already visible, then no scrolling happens, and | the first/last entry becomes selected. I think it would make much | more sense if half-down were exactly equivalent to doing next-line | w/2 times, where w is the window size. Use of the half-up/half-down ops when the first/last message is already on-screen, does the same thing as what the previous-page/next-page ops (left-arrow/right-arrow) do. Or at least they behaved in a consistent fashion, back in the 0.8x days, when I revised the half-op code (I'm still running 0.88.14i, so I don't know if the behaviors have diverged since then). /kim
Re: comments on 0.95.1i
On Mon, Jan 18, 1999 at 21:23:11 +, Adam M. Costello wrote: > David DeSimone <[EMAIL PROTECTED]> wrote: > > > For me, Mutt checks for mail whenever I press any key in the index. > > Is this not what you want? > > That sounds great. I didn't know this was happening (it's not > documented). I thought it was only using the mail_check timeout. Here is my understanding of when mail checking is done: At every key press and after a keyboard timeout (see the "timeout" variable) Mutt checks if it should check for new mail now. It then decices to check for new mail if there have passed "mail_check" seconds or more since the last check for new mail. The sync-mailbox function will not per se force a check for new mail. Only if some changes in the mailbox state are to be written, Mutt first checks if the mailbox have changed. Regards, - Byrial
Re: Problems with mutt and editor in Terminal
Hi, On Sun, Jan 17, 1999 at 13:56 +0100, Holger M. Fuessler wrote: > Now I'd like to use mutt with a terminal-based editor (like > joe). Unfortunately this doesn't seem to work: > While joe works fine in a terminal (like rxvt), it doesn't when > launched by mutt. The rows and columns are wrecked and the background > is bright white. I already updated ncurses and tried a bunch of Try export JOETERM=linux; mutt that fixed the wrecked joe menus for me. I don't know if it's possible to change the background color of an xterm/rxvt on the fly. But you can set the color when starting it. Or switch to jed, it uses a lightgrey background. Ciao, Stefan
Re: from address
Hi, On Sun, Jan 17, 1999 at 23:22 -0600, Brian Bray wrote: > ok I know that set hostname changes the domain name in the from: field but how > do you change the username? Use something like my_hdr From: Brian Bray <[EMAIL PROTECTED]> Ciao, Stefan
Re: comments on 0.95.1i
Byrial Jensen <[EMAIL PROTECTED]> wrote: > The sync-mailbox function will not per se force a check for new > mail. Only if some changes in the mailbox state are to be written, > Mutt first checks if the mailbox have changed. Okay, that's what I thought originally. > Here is my understanding of when mail checking is done: > > At every key press and after a keyboard timeout (see the "timeout" > variable) Mutt checks if it should check for new mail now. It then > decices to check for new mail if there have passed "mail_check" > seconds or more since the last check for new mail. Thanks, I never would have gotten that from the manual. But I've just done some experiments, and changing mail_check doesn't seem to have any effect. Mutt notices new mail within a few seconds of any keypress, even if mail_check and timeout are both 300. AMC
text/x-vcard attachments
Hi! How to correctly display text/x-vcard attachments? I use Mutt 0.93.2i, procmail and Lynx. TIA. Please, reply me by email. I'll sumarize. -- ___ Daniel González Gasull __|_|__"Un sólo muerto es [EMAIL PROTECTED](o o) ya demasiado." PGP RSA key 1024/EEA93A69 ( - ) -- Nelson Mandela ( . ) ( . ) (_) Fight Spam! Join CAUCE! == http://www.cauce.org/ Outlaw Junk Email! Support HR 1748. PGP signature
mutt & pgp
Hi there... When I use Mutt together with pgp it attaches my signatures and / or encrypted mails as files... I want the pgp message to be the main message body! How can I change that??? Also, when I recive a pgp encrypted mail I can't read it! It shows me the pgp message as the body but doesn't ask for my passphrase... Thanks a lot... Andy -- "Nothing can be loved or hated unless it is first understood" Leonardo da Vinci 1452 - 1519
Re: mutt & pgp
On Mon, Jan 18, 1999 at 04:14:54PM +, SteelOnIce wrote: > When I use Mutt together with pgp it attaches my signatures and / > or encrypted mails as files... I want the pgp message to be the > main message body! How can I change that??? Not at all. Mutt generates MIME-encapsulated PGP messages as defined in RFC 2015. Putting PGP information into a message's body leads to problems with content type and character set tagging, and it leads to problems with software which is MIME, but not PGP aware. > Also, when I recive a pgp encrypted mail I can't read it! It shows > me the pgp message as the body but doesn't ask for my passphrase... Read doc/PGP-Notes.txt. tlr -- Thomas Roessler · 74a353cc0b19 · dg1ktr · http://home.pages.de/~roessler/ 2048/CE6AC6C1 · 4E 04 F0 BC 72 FF 14 23 44 85 D1 A1 3B B0 73 C1 > Hi! I'm Signature Virus 99! Copy me into your signature and join the fun!
mutt for usenet
Well, I decided to write some perl to help out here. I grabbed Brandon's patch to give some news functionality to mutt (like the 'P' command to post news, and the ability to monify the Newsgroups: line, as well as the notion of the inews variable. I wrote some perl that does the following: spools articles from subscribed newsgroups into mbox folders (and by necessity manages .newsrc files), and posts news as a drop-in substitute for inews. If anyone is interested in seeing these, I'll clean the code up and post it somewhere. Let me know. -- Phil Humpherys <[EMAIL PROTECTED]> DriverSoft Unix Systems Administrator Mobile: +1.801.725.3257 The more control, the more that requires control.
