Re: Max Msgs: Count
Corey -- ...and then Corey G. said... % I have many email files with over 100,000 messages and counting. Wow! % However, I cannot get Mutt to indicate over 99,999 messages. It simply Hmmm... % chops off the last number making it appear that I have much less. Is % there a way to expand this field to handle very large mail volume? Have you played with $status_format in your muttrc? I'm sure it's controlled by a variable format setting, and the manual sez that status_format controls that line... You might have to explicitly allow for more digits than the default... HTH HAND :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: Aborted unmodified message.
Suresh Ramasubramanian ([EMAIL PROTECTED]) wrote: : I rather suspect that the path to vim is wrong in his .muttrc : Especially if he had an rpm install which would dump vim in /bin or /usr/bin - : and then compiled a new vim from a tarball, that'd put it into /usr/local/bin : : Use `which vim` to locate where the vim is on your box - and edit the editor : variable in your .muttrc to reflect the new location. That wasn't it. The ``path'' to vim was correct---It was using an alias. I explicitly set the path to where vim resides but that didn't work. Thanks. Regards, Marc van Dongen
Re: Aborted unmodified message.
Marc van Dongen proclaimed on mutt-users that: That's not the problem. Mutt doesn't seem to let me edit at all. With this setting, I can postpone a message for later, then recall it and use `e` to edit but mutt won't let me Then check if your tmpdir directory is set properly, or is over-full. Especially if your copy of vi makes backups of each post ... -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI The meeting of two personalities is like the contact of two chemical substances: if there is any reaction, both are transformed. -- Carl Jung
Re: Aborted unmodified message.
Marc -- ...and then Marc van Dongen said... % David T-G ([EMAIL PROTECTED]) wrote: % % : % Aborted unmodified message. % : % % : % Any suggestions how to overcome this problem? % : % : You might start by checking your $editor setting in your muttrc and your % % My editor setting points to an existing vim which works. Hokay. That's a good start... % % : $EDITOR and $VISUAL settings in your shell; if they're still pointing to % % EDITOR=VISUAL= That shouldn't matter much if your $editor is explicit, but at least it's not confusing. % % : setting to "yes" instead of one of the other possibilities) so mutt will % : throw it away. % % I can see that. Good enough. % % : If you can't figure out what's up, try setting mutt's $editor to a % : quickie script which calls vim and then waits for a keypress before % : exiting so that you can see any error messages that go by. % % I changed the editor setting to a script that prints something, % reads a line and then starts to edit. It doesn't seem to be % called when I press `e.' I still get the `unmodified' message. No, make sure that you *first* call vim and you *then* wait. You need to see that vim is really called and see what messages, if any, it returns. % % So should I set EDITOR and VISUAL to something? I just upgraded % to a higher solaris 8. Maybe that has to do something with the % problem as well. Possbile, but not probable. I'm still betting on a vim config, though a full /tmp as already mentioned might be a good place to start (my vim tmpdir is $HOME/tmp; I forget about the defaults sometimes :-) % % Regards, HTH HAND % % % Marc van Dongen :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: Aborted unmodified message.
David T-G ([EMAIL PROTECTED]) wrote: [snip] : % : If you can't figure out what's up, try setting mutt's $editor to a : % : quickie script which calls vim and then waits for a keypress before : % : exiting so that you can see any error messages that go by. : % : % I changed the editor setting to a script that prints something, : % reads a line and then starts to edit. It doesn't seem to be : % called when I press `e.' I still get the `unmodified' message. : : No, make sure that you *first* call vim and you *then* wait. You need to : see that vim is really called and see what messages, if any, it returns. I overlooked the purpose of you suggestion. It doesn't make any difference. The script doesn't get called. [snip] : Possbile, but not probable. I'm still betting on a vim config, though a : full /tmp as already mentioned might be a good place to start (my vim : tmpdir is $HOME/tmp; I forget about the defaults sometimes :-) I'll have a look at that. Thanks. Regards, Marc van Dongen
Re: sending mail
Suresh Ramasubramanian [EMAIL PROTECTED] wrote on Wed, 27 Sep 2000: Well... Thanks for this quick answer, but what choice do I have ? Making my machine to resolve in the outside world, or have mails bounce, or having this authentication warning ? What a choice ! Take it, or leave it ;) I think there is one more choice left out the list here: replace the MTA (sendmail). Or perhaps you can also reconfigure it. My personal preference would be to just install something else on it (qmail, masqmail, nullmailer, depending on the system setup). 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 / "Out of my mind. Back in five minutes."
Re: Aborted unmodified message.
Marc -- ...and then Marc van Dongen said... % David T-G ([EMAIL PROTECTED]) wrote: % % [snip] % % : % : quickie script which calls vim and then waits for a keypress before % : % % : % I changed the editor setting to a script that prints something, % : % reads a line and then starts to edit. It doesn't seem to be % : % called when I press `e.' I still get the `unmodified' message. % : % : No, make sure that you *first* call vim and you *then* wait. You need to % : see that vim is really called and see what messages, if any, it returns. % % I overlooked the purpose of you suggestion. It doesn't % make any difference. The script doesn't get called. Oho; I see what you mean. Now *that* is an interesting one. That answer will require some thought :-) % % [snip] % % : Possbile, but not probable. I'm still betting on a vim config, though a % : full /tmp as already mentioned might be a good place to start (my vim % : tmpdir is $HOME/tmp; I forget about the defaults sometimes :-) % % I'll have a look at that. Thanks. Sure thing... % % % Regards, % % % Marc van Dongen :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: Aborted unmodified message.
Marc van Dongen [EMAIL PROTECTED] wrote on Wed, 27 Sep 2000: I changed the editor setting to a script that prints something, reads a line and then starts to edit. It doesn't seem to be called when I press `e.' I still get the `unmodified' message. What doesn't get called when you press e, the script? (Just making sure I got that right..) One way to try to figure out things is to check the current $editor value from within Mut: :set ?editor This will give you the current editor setting, so you can verify it's correct. If it's correct, you can check that Mutt can execute it, with the ! command: !/path/to/your/editor/here You don't say what the values are, so something to try (if you haven't yet) is to put full paths into the settings. Maybe our PATH setting isn't set up the way you think it is, if you're launching Mutt via some graphical shell for instance. This shouldn't be a problem if it's started from a shell window though. Still worth a try... Hope this helps, 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 / Any sufficiently advanced magic is indistinguishable from technology.
Re: Aborted unmodified message.
Mikko Hänninen ([EMAIL PROTECTED]) wrote: : Marc van Dongen [EMAIL PROTECTED] wrote on Wed, 27 Sep 2000: : I changed the editor setting to a script that prints something, : reads a line and then starts to edit. It doesn't seem to be : called when I press `e.' I still get the `unmodified' message. : : What doesn't get called when you press e, the script? (Just making : sure I got that right..) The script to which the editor setting in my .muttrc points doesn't get called. : correct. If it's correct, you can check that Mutt can execute it, with : the ! command: : : !/path/to/your/editor/here Good one. I hadn't thought of trying that. It fails Other shell commands fail as well : You don't say what the values are, so something to try (if you haven't : yet) is to put full paths into the settings. Maybe our PATH setting The path is set up properly. As a matter of fact, the editor setting in the .muttrc is an absolute pathname. : isn't set up the way you think it is, if you're launching Mutt via some : graphical shell for instance. This shouldn't be a problem if it's I'm launching mutt from the command-line prompt in a ``regular'' window. Thanks. Regards, Marc van Dongen
Re: Aborted unmodified message.
Marc van Dongen [EMAIL PROTECTED] wrote on Wed, 27 Sep 2000: : !/path/to/your/editor/here Good one. I hadn't thought of trying that. It fails Other shell commands fail as well Well, that's the "reason" then why your editor isn't getting called. I have no idea why you couldn't run any commands from within Mutt though, I've never heard of this kind of problem. Can you even start /bin/sh (or your own shell)? 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 / Get a life? Well, once I nearly found one, but the link was broken.
Re: Aborted unmodified message.
Mikko Hänninen ([EMAIL PROTECTED]) wrote: [snip] : Good one. I hadn't thought of trying that. It fails : Other shell commands fail as well [snip] : I have no idea why you couldn't run any commands from within Mutt : though, I've never heard of this kind of problem. Can you even : start /bin/sh (or your own shell)? Nope. All commands fail. As I mentioned earlier on, I upgraded from sparc-sun-solaris-2.7 to sparc-sun-solaris-2.8 and rebuilt mutt from scratch. I did this before as well without serious problems. I haven't gor a clue what is going on here. Maybe this is an operating system related problem. I am using the CDE desktop at the moment but the problem also manifests itself if I use the openwindows desktop. Regards, Marc van Dongen
Re: Content-Disposition
No, it's currently not possible, unfortunately. Too bad. Wouldn't a variable like "disposition-default" be a good idea? Are any developers listening here? :-) Or maybe an extension to mailcap like copiousoutput, or like netscape is doing it with the "x-mozilla-flags"? Andy. -- E-Mail: [EMAIL PROTECTED] URL: http://andy.spiegl.de PGP/GPG: see headers o _ _ _ - __o __o /\_ _ \\o (_)\__/o (_) --- _`\,__`\,__(_) (_)/_\_| \ _|/' \/ -- (_)/ (_) (_)/ (_) (_)(_) (_)(_)' _\o_ ~~~ Everyone you meet deserves to be greeted with a smile.
Re: Aborted unmodified message.
Marc van Dongen proclaimed on mutt-users that: Maybe this is an operating system related problem. I am using the CDE desktop at the moment but the problem also manifests itself if I use the openwindows desktop. Get out of both desktops into the sun shell... try mutt there. -- Suresh Ramasubramanian + Wallopus Malletus Indigenensis mallet @ cluestick.org + Lumber Cartel of India, tinlcI To avoid criticism, do nothing, say nothing, be nothing. -- Elbert Hubbard
Re: sending mail
Emmanuel Anne [[EMAIL PROTECTED]] wrote: I am just starting to use mutt, and noticed something : it is quite hard to configure when you have an email adress different from your unix account. Generally, you end up using the sendmail "-f" switch, but in a case like this you get an "Authentication-Warning" with some mail agents like postfix (as you can see in the headers of this message). First note that you shouldn't need the -f switch to just change the From: header. You only need this if you actually want to change the envelope sender for some reason. If you just want to change the From: header, Mutt has various methods for doing this during message composition -- see the manual regarding $from, my_hdrs, $alternates/$reverse_name, etc. I did not check very far, but apparently some other programs take the approach of sending mail by communicating with sendmail via the port 25, and not by calling it directly. Apparently, they avoid the -f switch, and thus the warning. xfmail takes this approach. Mutt doesn't speak SMTP because it isn't a mail transfer agent. It is a mail reader and as such doesn't know anything about mail transfer protocols, just mailbox formats. This lets it be very versatile as far as which mail transfer agent you use with it and lets the developers spend time on making the mail reading features better instead of chasing mail transfer protocol development that other projects are already doing quite well. But maybe I did something wrong ? If you really need the envelope sender changed you might consider reconfiguring your MTA to omit this warning if you don't want it. If it doesn't allow this, or your setup doesn't allow it, this is a limitation of your MTA/setup, not Mutt. -- Jeremy Blosser | [EMAIL PROTECTED] | http://jblosser.firinn.org/ -+-+-- the crises posed a question / just beneath the skin the virtue in my veins replied / that quitters never win PGP signature
Re: Aborted unmodified message.
Suresh Ramasubramanian ([EMAIL PROTECTED]) wrote: : Get out of both desktops into the sun shell... try mutt there. No success either:-( Regards, Marc van Dongen
Re: Q: Why no replies to my post??
On 2000.09.27, in [EMAIL PROTECTED], "Byrial Jensen" [EMAIL PROTECTED] wrote: On Tue, Sep 26, 2000 at 09:08:23 -0500, David Champion wrote: Me, too. I take a different approach: I have a short wrapper script that I use for invoking mutt. It sets LANG, then returns LC_COLLATE to C so that sorting works correctly. :) Mutt disregards the setting of LC_COLLATE and always sorts according to the C locale. But of course it is good to be prepared Yes, but Mutt's subprocesses don't. :) if this bug someday should be fixed. :-) (It can easily be fixed by replacing a few mutt_strcasecmp() calls with strcoll() calls in sort.c, I think). That sounds like it would be good, although I'd never take advantage, personally. -- -D.[EMAIL PROTECTED]NSITUniversity of Chicago
Re: sending mail
On Wed, Sep 27, 2000, Mikko Hänninen wrote: Suresh Ramasubramanian [EMAIL PROTECTED] wrote on Wed, 27 Sep 2000: Well... Thanks for this quick answer, but what choice do I have ? Making my machine to resolve in the outside world, or have mails bounce, or having this authentication warning ? I think there is one more choice left out the list here: replace the MTA (sendmail). Or perhaps you can also reconfigure it. My personal You can just reconfigure it, it's trivial. Remove authwarnings from PrivacyOptions, that's it. There are other ways to get rid of the message, but this isn't a sendmail list.
Fwd: mutt question.
-- Jeremy Blosser | [EMAIL PROTECTED] | http://jblosser.firinn.org/ -+-+-- the crises posed a question / just beneath the skin the virtue in my veins replied / that quitters never win Hi I have the folowing options set in my muttrc unset collapse_unread folder-hook . 'push \eV' #collapse all threads when entering a folder What I want is to have all threads collapsed except for those who have new mail. What happens is almost that, except that mail marked O is also treated as new. I get a lot of mail and dont read the mail that's not interesting, but I have seen them and don't want them treated as new. I think it's a great idea that they are marked O and so, but is there a way to have mutt to behave the way I want? Not treating O as new. //Snaggen -- Mattias Eriksson E-mail: [EMAIL PROTECTED] Tvistevägen 26 [EMAIL PROTECTED] 907 36 UMEA Tel:090-198800 SWEDEN 070-5636769 'I don't fight for a cause Hemsida: http://www.acc.umu.se/~snaggen I fight for the fight' PGP: http://www.acc.umu.se/~snaggen/snaggen.asc PGP signature
bcc header not saved
When I write a mail with a Bcc: header, this header does not get saved to the Fcc-file. Is there a way to tell mutt to do that? Thanks, Andy. -- E-Mail: [EMAIL PROTECTED] URL: http://andy.spiegl.de PGP/GPG: see headers o _ _ _ - __o __o /\_ _ \\o (_)\__/o (_) --- _`\,__`\,__(_) (_)/_\_| \ _|/' \/ -- (_)/ (_) (_)/ (_) (_)(_) (_)(_)' _\o_ ~~~ 43rd Law of Computing: Anything that can go wr fortune: Segmentation violation -- Core dumped
Re: bcc header not saved
On Wed, Sep 27, 2000 at 05:40:06PM +0200, Andy Spiegl wrote: When I write a mail with a Bcc: header, this header does not get saved to the Fcc-file. Is there a way to tell mutt to do that? :set write_bcc 43rd Law of Computing: Anything that can go wr fortune: Segmentation violation -- Core dumped Good one. -- - Bruce
Re: Aborted unmodified message.
On Wed, Sep 27, 2000 at 04:09:04PM +0100, Marc van Dongen wrote: Suresh Ramasubramanian ([EMAIL PROTECTED]) wrote: : Get out of both desktops into the sun shell... try mutt there. No success either:-( And what does :set ?shell return? -- - Bruce
Re: Aborted unmodified message.
Bruce DeVisser ([EMAIL PROTECTED]) wrote: : And what does :set ?shell return? shell="/usr/bin/bash" which is correct. Regards, Marc van Dongen
sort index by alpha
How to sort index ( where I see my mailboxes by alpha ) ? I'd like to keep other folder sorting methods( some folder by date some by thread ). Thanks Attila -- -- - Mail: [EMAIL PROTECTED]; Debian 2.2 Linux / 2.2.13 / exim- - Get my PGP key: gpg --keyserver keys.pgp.com --recv-key 0x2cc33acb -
Re: sending mail
On Wed, Sep 27, 2000 at 10:17:17AM +0530, Suresh Ramasubramanian wrote: Emmanuel Anne proclaimed on mutt-users that: it is quite hard to configure when you have an email adress different from your unix account. Generally, you end up using the sendmail "-f" switch, but in a case like this you get an "Authentication-Warning" with some mail agents like postfix (as you can see in the headers of this message). Should that matter? Anyone who filters on an X- header like that should, erm, re-evaluate his priorities :) I missed the beginning of this, but if Emmanuel has root access he can comment out/edit the line: O PrivacyOptions=authwarnings in sendmail.cf, which should prevent "X-Authentication-Warning..." from being added to the headers, after sendmail is restarted. Regards, -rex -- If you think C++ is not overly complicated, just what is a protected abstract virtual base pure virtual private destructor, and when was the last time you needed one? -- Tom Cargil, C++ Journal.
RE: sort index by alpha
How to sort index ( where I see my mailboxes by alpha ) ? I'd like to keep other folder sorting methods( some folder by date some by thread ). while looking at your folder's message headers: o. (Reverse order: O.) I discovered this (and many other things I wondered about) by pressing ? for help and then / to search the help pages for a particular string. Bob DuCharme
my_hdr From: vs. set reverse_name
In my .muttrc, "my_hdr From:" seems to override my set reverse_name heading, but I want it to be the other way around. I only want the "my_hdr From:" return address used for new mail and the reverse_name one used for replies. Any suggestions? (Warning: I haven't used Mutt macros yet--is there a little tutorial on them anywhere?) thanks, Bob DuCharme
Re: bcc header not saved
:set write_bcc Wow, you are right, it works! I had found this switch in the manual, but it says: Controls whether mutt writes out the Bcc header when preparing messages to be sent. Exim users may wish to use this. So I thought this is talking about the menu you get to see before you send off the mail. Never even bothered to try it. Maybe that should be rewritten??? Thanks, Andy. -- E-Mail: [EMAIL PROTECTED] URL: http://andy.spiegl.de PGP/GPG: see headers o _ _ _ - __o __o /\_ _ \\o (_)\__/o (_) --- _`\,__`\,__(_) (_)/_\_| \ _|/' \/ -- (_)/ (_) (_)/ (_) (_)(_) (_)(_)' _\o_ ~~~ Hiroshima 45, Tschernobyl 86, Windows 98
Re: xterm window resizing
OK. I think I've managed to fix this problem by re-compiling 1.2.5 with slang (v1.3.7) instead of ncurses. And BOY, does it have a different idea about colors! I couldn't believe some of the wacky things I had in my .muttrc that I guess just weren't being recognized before (I suppose). I had to do some tweaking just so I could read messages. :^ Anyway, thanks for the help ya'll. On Tue, Sep 26, 2000 at 05:55:58PM -0500, Jeff Howie wrote: Hi all. I've noticed a really annoying problem, that I can't seem to be able to resize the xterm that is running mutt. I've experienced -- -- | THKS : | Federated Insurance | | Jeff Howie | Information Systems - PC | | Int Programmer/Analyst | 204.786.6431.x.217| --
PGP/MIME headers
I know know PGP stuff is supposed to be specified via MIME headers. I'm just not sure which technique is best. Mutt is attaching a Content-Type header like this: Content-Type: multipart/encrypted; protocol="application/pgp-encrypted"; boundary="FoLtEtfbNGMjfgrs" Content-Disposition: inline Which shows up as an attachment if viewed in Pine. Messages sent from Pine, however, use a header format like this: Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Type: application/pgp; format=text; x-action=encrypt Which shows up inline. From my perusal of RFC1806, it sounds like the Content-Disposition header combined with a multipart MIME message should, indeed, be displayed as an attachment. -- 2.5 Content-Disposition and Multipart If a Content-Disposition header is used on a multipart body part, it applies to the multipart as a whole, not the individual subparts. The disposition types of the subparts do not need to be consulted until the multipart itself is presented. When the multipart is displayed, then the dispositions of the subparts should be respected. -- Is my interpretation of that snippet correct? If so, it seems it would be preferrable to not set up PGP encrypted messages as multipart so they can be viewed inline by Pine and other MUAs. Since mutt has a record of being extremely correct in it's observation of RFCs, I'm assuming that my understanding of the situation is incorrect. I would be very interested in an explanation of my (presumed) misunderstanding. I also would appreciate any recommendations that I could use to configure mutt to allow "inline" viewing of encrypted messages by other less correct MUAs. Thanks, Ben -- Ben Beuchler [EMAIL PROTECTED] MAILER-DAEMON (612) 321-9290 x101 Bitstream Underground www.bitstream.net
Undecoded attachment names
Hi, I think somebody asked about this earlier but the problem apparently persists: mutt does not decode attachment names. Example: [-- Attachment #2: =?ISO-8859-2?Q?mar=BBa=2Ejpg?= --] [-- Type: image/jpeg, Encoding: base64, Size: 33K --] Obviously, when trying to save this, mutt offers the nonsense string as the name. Assuming the name encoding was done correctly by the sender's mailer, can this be fixed or worked around in mutt? Thanks, Petr
Re: xterm window resizing
On Wed, 27 Sep 2000, Jeff Howie wrote: OK. I think I've managed to fix this problem by re-compiling 1.2.5 with slang (v1.3.7) instead of ncurses. And BOY, does it have a different idea about colors! I couldn't believe some of the wacky that's mostly in the mutt code (the differences in colors). -- T.E.Dickey [EMAIL PROTECTED] http://dickey.his.com ftp://dickey.his.com
Re: Aborted unmodified message.
On 27, Sep, 2000 at 01:36:46PM +0100, Marc van Dongen wrote: David T-G ([EMAIL PROTECTED]) wrote: [snip] : % : If you can't figure out what's up, try setting mutt's $editor to a : % : quickie script which calls vim and then waits for a keypress before : % : exiting so that you can see any error messages that go by. : % : % I changed the editor setting to a script that prints something, : % reads a line and then starts to edit. It doesn't seem to be : % called when I press `e.' I still get the `unmodified' message. : : No, make sure that you *first* call vim and you *then* wait. You need to : see that vim is really called and see what messages, if any, it returns. I overlooked the purpose of you suggestion. It doesn't make any difference. The script doesn't get called. [snip] : Possbile, but not probable. I'm still betting on a vim config, though a : full /tmp as already mentioned might be a good place to start (my vim : tmpdir is $HOME/tmp; I forget about the defaults sometimes :-) I'll have a look at that. Thanks. This _is_ a long shot, but: what happens when you try to invoke vim from your shell? Just a thought I got reading this thread, and I know I myself has overlooked the blindingly obvious at times ... HTH, HAND Morten -- UNIX, reach out and grep someone!
request
Is there a way to tag messages before they're saved in the "mbox" or which ever mail box? There have been a few instances where I did/don't have enough time to reply to the message but would like to write myself a note as to what the reply should contain. Another application would be if the sender didn't leave a descriptive enough subject and one would want to append some personal reminders. thanks, tw
tags -- error in manual?
In: The Mutt E-Mail Client by Michael Elkins [EMAIL PROTECTED] version 1.2.5 In: Section 4.3 It is stated that "control-T" is used for tag-pattern. It seems wrong---on my system "T" is used for tag-pattern and "control-t" for untagging. I'm using mutt 1.0.1. BTW.: I'm not on the mailing-list.
Re: sending mail
* Emmanuel Anne ([EMAIL PROTECTED]) [27 Sep 2000 12:15]: Maybe I shoud have sent this to mutt-users... I am just starting to use mutt, and noticed something : it is quite hard to configure when you have an email adress different from your unix account. Generally, you end up using the sendmail "-f" switch, but in a case like this you get an "Authentication-Warning" with some mail agents like postfix (as you can see in the headers of this message). Possibly the easiest way of fixing it is to add the following line (well, suitably modified) to your .muttrc file: send-hook . my_hdr From: Emmanuel Anne [EMAIL PROTECTED] I've not noticed it causing Authentication-Warning header lines (but I may not have noticed; plus we run postfix here rather than sendmail). cheers, -- iain truskett, aka Koschei.http://eh.org/~koschei/ What's a book? Everything or nothing. The eye that sees it all. Ralph Waldo Emerson
Core dump for 1.2.5i
This happened when opening a mailbox, on a RedHat 6.2 system: This GDB was configured as "i386-redhat-linux"... Core was generated by `/usr/local/bin/mutt'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libncurses.so.4...done. Reading symbols from /lib/libc.so.6...done. Reading symbols from /lib/ld-linux.so.2...done. Reading symbols from /lib/libnss_files.so.2...done. Reading symbols from /usr/lib/gconv/ISO8859-1.so...done. #0 strcmp (p1=0x6164612d Address 0x6164612d out of bounds, p2=0x81814a0 "[EMAIL PROTECTED]") at ../sysdeps/generic/strcmp.c:38 38 ../sysdeps/generic/strcmp.c: No such file or directory. (gdb) bt #0 strcmp (p1=0x6164612d Address 0x6164612d out of bounds, p2=0x81814a0 "[EMAIL PROTECTED]") at ../sysdeps/generic/strcmp.c:38 #1 0x80867f6 in mutt_strcmp (a=0x6164612d Address 0x6164612d out of bounds, b=0x81814a0 "[EMAIL PROTECTED]") at lib.c:544 #2 0x8062090 in hash_insert (table=0x8624948, key=0x81814a0 "[EMAIL PROTECTED]", data=0x8181350, allow_dup=0) at hash.c:79 #3 0x806cdd1 in mx_update_context (ctx=0x8626110) at mx.c:1457 #4 0x806739f in mbox_parse_mailbox (ctx=0x8626110) at mbox.c:363 #5 0x8067520 in mbox_open_mailbox (ctx=0x8626110) at mbox.c:421 #6 0x806bf86 in mx_open_mailbox (path=0xbfffeda0 "[mailbox location]", flags=0, pctx=0x0) at mx.c:639 #7 0x805746f in mutt_index_menu () at curs_main.c:977 #8 0x8066b53 in main (argc=1, argv=0xb984) at main.c:709 Adam
Re: Aborted unmodified message.
Marc -- ...and then Marc van Dongen said... % Bruce DeVisser ([EMAIL PROTECTED]) wrote: % % : And what does :set ?shell return? % % shell="/usr/bin/bash" % % which is correct. It may be correct, but it isn't stock :-) Try settin $shell to /sbin/sh, which is guaranteed to be completely self-contained. If *that* works, then try using /bin/sh to see if your shared libs are all healthy. If *that* works, then it's all bash's fault. Note that I don't want to start a shell war; in fact, as much as I hate to admit it, I think I'm becoming a bash convert because of ksh limitations :-) % % Regards, HTH HAND % % % Marc van Dongen :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: Undecoded attachment names
On 2000-09-27 13:29:35 -0500, Petr Hlustik wrote: I think somebody asked about this earlier but the problem apparently persists: mutt does not decode attachment names. Example: [-- Attachment #2: =?ISO-8859-2?Q?mar=BBa=2Ejpg?= --] [-- Type: image/jpeg, Encoding: base64, Size: 33K --] Obviously, when trying to save this, mutt offers the nonsense string as the name. Assuming the name encoding was done correctly by the sender's mailer, can this be fixed or worked around in mutt? Actually, that use of the rfc2047 encoding is prohibited in the standard. However, as a workaround, you can set the $rfc2047_parameters variable. -- Thomas Roessler [EMAIL PROTECTED]
Re: request
On Tue, Sep 26, 2000 at 08:13:56PM -0500, Tim Whitehead wrote: Is there a way to tag messages before they're saved in the "mbox" or which ever mail box? There have been a few instances where I did/don't have enough time to reply to the message but would like to write myself a note as to what the reply should contain. Another application would be if the sender didn't leave a descriptive enough subject and one would want to append some personal reminders. I generally like to keep incoming messages pristine, but you do have the option to edit them (normally 'e'). -- - Bruce
Re: bcc header not saved
On Wed, Sep 27, 2000 at 10:40:41PM +0300, Mikko Hänninen wrote: BTW, I wonder if $write_bcc affects both the Fcc copy of the email as well as the message that gets piped to the MTA? Although well-behaved MTAs of course remove the Bcc header. Apparently not (experimentally derived answer). My copy of sendmail leaves the Bcc: line present (but empty) if one is piped to it (I used cat to test); but no Bcc: line appeared at all when I used Mutt to test. -- - Bruce
Re: Incorrect encoding of letter's headings
On Tue, Sep 26, 2000 at 09:47:26PM +0400, Vitaly A. Repin wrote:
When I write the subject of my letter in russian (koi8-r encoding),
the following transformation occurs with letters of the "Subject" field:
Subject: =?koi8-r?B?9MXT1CDS1dPTy8/HzyDawcfPzM/Xy8E=?=
What's the problem? And how can I solve it?
As far a I remember this occures when the body of the message is in,
for example, in win-1251 and headers are in koi8-r.
If in the Content-Type header there is charset=win-1251 or something
like that then I'm right, if not then not right. :)
You've got to syncronize somehow charsets in headers and body.
--
Eugene Paskevich | *==(--- | "Alrighty then!"
[EMAIL PROTECTED]| ---)==* |-- Ace Venture
Public PGP key: mailto:[EMAIL PROTECTED]?subject=publicpgpkey
{Mutt 1.2.4i}Moderator of [EMAIL PROTECTED] Be afraid. ;)
##
I bought some used paint. It was in the shape of a house.
-- Steven Wright
##
Re: Aborted unmodified message.
Morten Liebach ([EMAIL PROTECTED]) wrote: [snip] : This _is_ a long shot, but: what happens when you try to invoke vim from : your shell? It works great! [snip] Regards, Marc van Dongen
Re: Undecoded attachment names
Petr Hlustik [EMAIL PROTECTED] wrote on Wed, 27 Sep 2000: I think somebody asked about this earlier but the problem apparently persists: mutt does not decode attachment names. Assuming the name encoding was done correctly by the sender's mailer, can this be fixed or worked around in mutt? Sure. set rfc2047_parameters The manual states that parameter names in fact should not be encoded, so the sender's mailer is not "doing it correctly". But the workaround should make your life easier anyway. Hope this helps, 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 / Signature under construction, beware of falling letters!
Re: bcc header not saved
Andy Spiegl [EMAIL PROTECTED] wrote on Wed, 27 Sep 2000: I had found this switch in the manual, but it says: Controls whether mutt writes out the Bcc header when preparing messages to be sent. Exim users may wish to use this. So I thought this is talking about the menu you get to see before you send off the mail. Never even bothered to try it. Maybe that should be rewritten??? Maybe it should, feel free to submit a patch. :-) BTW, I wonder if $write_bcc affects both the Fcc copy of the email as well as the message that gets piped to the MTA? Although well-behaved MTAs of course remove the Bcc header. 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 / Woe unto them that rise up early in the morning -- Isaiah 5:11
Re: PGP/MIME headers
Ben -- The short answer is that, as you state, mutt is extremely correct. You are not wrong in your understanding, and so you can see that the only other possibility is that other mailers are wrong in their implementation. Gee, go figure :-) In order to communicate with such Outhouse losers, you might find it handy to set $pgp_create_traditional via a send-hook; instead of creating a MIME-attached signature of the MIME-attached body, mutt will have pgp sign the body in armored form and use the whole thing as the text body, which LookOut! and other broken can then understand. :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: Aborted unmodified message.
David T-G ([EMAIL PROTECTED]) wrote: : It may be correct, but it isn't stock :-) Try settin $shell to /sbin/sh, : which is guaranteed to be completely self-contained. If *that* works, I am assuming you are asking me to write a wrapper script around mutt to set the shell. That didn't work. Now I am assuming you are asking me put a shell= line in my .muttrc. That didn't work either. : then try using /bin/sh to see if your shared libs are all healthy. : If *that* works, then it's all bash's fault. That didn't work for the wrapper nor for the shell= variant. : Note that I don't want to start a shell war; in fact, as much as I : hate to admit it, I think I'm becoming a bash convert because of ksh : limitations :-) Good lad! Thanks again. Regards, Marc van Dongen
Re: Aborted unmodified message.
Marc van Dongen [EMAIL PROTECTED] wrote on Wed, 27 Sep 2000: Bruce DeVisser ([EMAIL PROTECTED]) wrote: : And what does :set ?shell return? shell="/usr/bin/bash" which is correct. OK.. And you can get a shell (via a terminal window), so you know the binary is executable etc.? Marc van Dongen [EMAIL PROTECTED] wrote on Wed, 27 Sep 2000: : I have no idea why you couldn't run any commands from within Mutt : though, I've never heard of this kind of problem. Can you even : start /bin/sh (or your own shell)? Nope. All commands fail. Well, this is obviously the problem here. :-) Unfortunately it doesn't help yet that much in knowing the solution. But not being able to start any programs is Very Bad. As I mentioned earlier on, I upgraded from sparc-sun-solaris-2.7 to sparc-sun-solaris-2.8 and rebuilt mutt from scratch. I did this before as well without serious problems. I haven't gor a clue what is going on here. Maybe this is an operating system related problem. I don't know the exact details (haven't looked at the source), but I would guess that the way Mutt starts an external program is with the system() sytem-function-call. If your Mutt can't run programs this way, then something is Seriously Wrong in your setup. Trying to debug this gets quite hairy though. On Linux, I would run Mutt with strace and trace the syscalls it makes, in the hope that I could see what's the status of the system() function. For Sun, I don't know what the system call trace program is called -- truss maybe, or was that some other OS? It may not have one (installed). Like I said, if your Mutt can't start programs, things are Seriously Wrong, and because of it gets quite complex to try to figure out what is going wrong. I am using the CDE desktop at the moment but the problem also manifests itself if I use the openwindows desktop. Like someone else suggested, try getting a shell without a windowing environment, and then try with that. That way you can check the values of PATH etc., and know for sure it's not the windowing environment getting in the way. I don't actually think it is, however since weird things are happening I'd try to eliminate every potential source of confusion. 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 / "The last good thing written in C was Franz Schubert's Symphony #9."
Re: Aborted unmodified message.
On Wed, Sep 27, 2000 at 10:57:14PM +0300, Mikko Hänninen wrote: I don't know the exact details (haven't looked at the source), but I would guess that the way Mutt starts an external program is with the system() sytem-function-call. If your Mutt can't run programs this way, then something is Seriously Wrong in your setup. The help doc mentions /bin/sh -c in relation to mime mailcap stuff... hopefully that is not a hard-coded path and if so hopefully only used in a limited place. I have not checked the source (obviously). -- - Bruce
Re: sort index by alpha
I'd like it from .muttrc How to sort index ( where I see my mailboxes by alpha ) ? I'd like to keep other folder sorting methods( some folder by date some by thread ). while looking at your folder's message headers: o. (Reverse order: O.) I discovered this (and many other things I wondered about) by pressing ? for help and then / to search the help pages for a particular string. I know the help lama.
Re: Core dump for 1.2.5i
Can you create a minimal mailbox which permits reproducing that behaviour? On 2000-09-27 16:51:50 +0100, Adam Huffman wrote: Date: Wed, 27 Sep 2000 16:51:50 +0100 From: Adam Huffman [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Core dump for 1.2.5i User-Agent: Mutt/1.2.5i Organization: University of Manchester This happened when opening a mailbox, on a RedHat 6.2 system: This GDB was configured as "i386-redhat-linux"... Core was generated by `/usr/local/bin/mutt'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libncurses.so.4...done. Reading symbols from /lib/libc.so.6...done. Reading symbols from /lib/ld-linux.so.2...done. Reading symbols from /lib/libnss_files.so.2...done. Reading symbols from /usr/lib/gconv/ISO8859-1.so...done. #0 strcmp (p1=0x6164612d Address 0x6164612d out of bounds, p2=0x81814a0 "[EMAIL PROTECTED]") at ../sysdeps/generic/strcmp.c:38 38 ../sysdeps/generic/strcmp.c: No such file or directory. (gdb) bt #0 strcmp (p1=0x6164612d Address 0x6164612d out of bounds, p2=0x81814a0 "[EMAIL PROTECTED]") at ../sysdeps/generic/strcmp.c:38 #1 0x80867f6 in mutt_strcmp (a=0x6164612d Address 0x6164612d out of bounds, b=0x81814a0 "[EMAIL PROTECTED]") at lib.c:544 #2 0x8062090 in hash_insert (table=0x8624948, key=0x81814a0 "[EMAIL PROTECTED]", data=0x8181350, allow_dup=0) at hash.c:79 #3 0x806cdd1 in mx_update_context (ctx=0x8626110) at mx.c:1457 #4 0x806739f in mbox_parse_mailbox (ctx=0x8626110) at mbox.c:363 #5 0x8067520 in mbox_open_mailbox (ctx=0x8626110) at mbox.c:421 #6 0x806bf86 in mx_open_mailbox (path=0xbfffeda0 "[mailbox location]", flags=0, pctx=0x0) at mx.c:639 #7 0x805746f in mutt_index_menu () at curs_main.c:977 #8 0x8066b53 in main (argc=1, argv=0xb984) at main.c:709 Adam -- Thomas Roessler [EMAIL PROTECTED]
Re: About PGP public key service. (With P.S.)
Bya godzina 21:43:20 w wtorek 26 wrzesie, gdy do autobusu wsiad kanar i wrzasn:"Dan Boger!!! Bilecik do kontroli!!!" A on(a) na to: Set your mutt/gpg to automatically get keys from a keyserver (like wwwkeys.pgp.net) and then when it encounters a key it doesn't know, it'll try and get it and automatically verify it. it's pretty cool. :) And if you have not got a hard-wire? What then? I just call my teleco to download mail and read offline. By. -- |/ |_, _ .- --,2:480/135@fido[EMAIL PROTECTED] |__ |_|. | \ |_|. ._' /_. 101:1000/135@unholy ... Droga wrd jaboni prowadzi w nieznane...
Re: my_hdr From: vs. set reverse_name
DuCharme, Robert muttered: In my .muttrc, "my_hdr From:" seems to override my set reverse_name heading, but I want it to be the other way around. I only want the "my_hdr From:" return address used for new mail and the reverse_name one used for replies. This is the intented behavior. If you want to set a default From: header use $realname and $from. You can use send-hooks with my_hdr From:, too. In this case you nedd a default send-hook where any userset From: header will be removed first. I have this settings in my muttrc: # Configure From: set realname="Michael Tatge" set from="[EMAIL PROTECTED]" set use_from# create From: Header set reverse_name# reply with the address the # message was send to set envelope_from # use MTA -f From: Header send-hook . 'unmy_hdr From:'# remove user created From: send-kook '~C some.guy@some_host' 'my_hdr From: me [EMAIL PROTECTED]' If I reply to a message from some.guy@some_host always me [EMAIL PROTECTED] is used regardless of the adresse I received to original message was send to. In all other cases reverse_name will work. Any suggestions? (Warning: I haven't used Mutt macros yet I don't see no reason for a macro here. :) --is there a little tutorial on them anywhere?) Well, you have the manual. That's all you need. HTH, Michael -- Ignorance is bliss. -- Thomas Gray Fortune updates the great quotes, #42: BLISS is ignorance. PGP-fingerprint: DECA E9D2 EBDD 0FE0 0A65 40FA 5967 ACA1 0B57 7C13
Re: Aborted unmodified message.
Mikko Hänninen ([EMAIL PROTECTED]) wrote: : OK.. And you can get a shell (via a terminal window), so you know the : binary is executable etc.? I am not exactly sure what you mean. External programs, like knews can start vim as an external program to compose an email message. [snip] : Like someone else suggested, try getting a shell without a windowing : environment, and then try with that. That way you can check the values : of PATH etc., and know for sure it's not the windowing environment : getting in the way. I don't actually think it is, however since weird : things are happening I'd try to eliminate every potential source of : confusion. That doesn't work there either. Thanks. Regards, Marc van Dongen
Re: mutt-users-digest V1 #526
Quoting ?iso-8859-1?Q?Mikko_H=E4nninen?= [EMAIL PROTECTED] -- Date: Wed, 27 Sep 2000 15:44:46 +0300 From: =?iso-8859-1?Q?Mikko_H=E4nninen?= [EMAIL PROTECTED] Subject: Re: sending mail Suresh Ramasubramanian [EMAIL PROTECTED] wrote on Wed, 27 Sep 2000: Well... Thanks for this quick answer, but what choice do I have ? Making my machine to resolve in the outside world, or have mails bounce, or having this authentication warning ? What a choice ! Take it, or leave it ;) I think there is one more choice left out the list here: replace the MTA (sendmail). Or perhaps you can also reconfigure it. My personal preference would be to just install something else on it (qmail, masqmail, nullmailer, depending on the system setup). 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 / "Out of my mind. Back in five minutes." -- Hmmm. Not sure I understand the problem completely, but is it that your mail goes out with a domain name which can't be resolved? IE, you are [EMAIL PROTECTED], but your host isn't known to your provider; you normally receive mail as [EMAIL PROTECTED]? What I do is modify my sendmail.cf to have Dj$m This will strip off the host part so your address will be [EMAIL PROTECTED], and this will resolve. Of course if I've misunderstood the problem (likely, as I haven't seen anyone else suggest this solution) then "nevermind". /joel -- joel wittenberg [EMAIL PROTECTED] [work] [EMAIL PROTECTED] [permanent]
edit message from compose menu
Hello. How to edit the body of the message from the compose menu otherway than postpone the message? Thanks Hans
Re: Aborted unmodified message.
Marc -- ...and then Marc van Dongen said... % David T-G ([EMAIL PROTECTED]) wrote: % % : It may be correct, but it isn't stock :-) Try settin $shell to /sbin/sh, % : which is guaranteed to be completely self-contained. If *that* works, % % I am assuming you are asking me to write a wrapper script around % mutt to set the shell. That didn't work. Nope, that wasn't it. % % Now I am assuming you are asking me put a shell= line in my .muttrc. % That didn't work either. Yep, that was what I meant. Did you try a simple :set shell=/sbin/sh from within mutt? Did you try :set ?shell to see what mutt thinks $shell is holding? % % : then try using /bin/sh to see if your shared libs are all healthy. % : If *that* works, then it's all bash's fault. % % That didn't work for the wrapper nor for the shell= variant. How interesting... With a valid $shell setting you can't even !ls manually, eh? Still more thinking on my part :-) % % : Note that I don't want to start a shell war; in fact, as much as I % : hate to admit it, I think I'm becoming a bash convert because of ksh % : limitations :-) % % Good lad! *grin* % % Thanks again. HTH HAND % % Regards, % % % Marc van Dongen :-D -- David T-G * It's easier to fight for one's principles (play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie (work) [EMAIL PROTECTED] http://www.bigfoot.com/~davidtg/Shpx gur Pbzzhavpngvbaf Qrprapl Npg! The "new millennium" starts at the beginning of 2001. There was no year 0. Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh* PGP signature
Re: Aborted unmodified message.
On Wed, Sep 27, 2000 at 22:57:14 +0300, Mikko Hänninen wrote: I don't know the exact details (haven't looked at the source), but I would guess that the way Mutt starts an external program is with the system() sytem-function-call. Mutt has its own implementaion of system() to have better control on signal handling and redirection. It uses execl() like this to execute a program: execl (EXECSHELL, "sh", "-c", cmd, NULL); EXECSHELL can be set with the configure script, and the compiled-in value can be seen with "mutt -v". I advise to check this as a bad value for EXECSHELL can prevent Mutt from executing any external program. -- Byrial http://home.worldonline.dk/~byrial/
Re: edit message from compose menu
On Wed, Sep 27, 2000 at 09:34:46AM +0200, Hans Ginzel wrote: How to edit the body of the message from the compose menu otherway than postpone the message? Hit "e". Once you've tried that, hit "?". It will list all the commands that are valid for that menu. Ben -- Ben Beuchler [EMAIL PROTECTED] MAILER-DAEMON (612) 321-9290 x101 Bitstream Underground www.bitstream.net
Re: Aborted unmodified message.
At 22:57 +0300 27 Sep 2000, Mikko Hänninen [EMAIL PROTECTED] wrote: For Sun, I don't know what the system call trace program is called -- truss maybe, or was that some other OS? It may not have one (installed). truss is correct. I'd probably use: truss -o /tmp/mutt.truss -f -t exec mutt -- Aaron Schrab [EMAIL PROTECTED] http://www.execpc.com/~aarons/ C makes it easy for you to shoot yourself in the foot. C++ makes that harder, but when you do, it blows away your whole leg. -- Bjarne Stroustrup
