Re: mbox / inbox & xterm colors
On Tue, Jan 18, 2000 at 09:14:17PM -0600 or thereabouts, Bram Shirani wrote: > Howdy all, I've got two questions. Eek, can you put line breaks in? This came out as five lines long when I started to reply :) > When I get new mail, it does not go to 'mbox'. I assume, therefore, it > goes to a directory I'll call inbox for now, just to keep them separate. Arriving mail is stored in somewhere like /var/spool/mail/username (the exact path depends on what OS and flavour you're using, I believe) until you start to read email with mutt or pine or something. Some (many?) people use programs like procmail to sit around, inspect anything that arrives in that file and do things like putting it into a different file as it arrives on the machine. There may well be a simpler program than procmail to use if you just want to put incoming email in a different place. I like to leave most of mine there in case a mailing list explodes, because /home and /var are different partitions on my machine :) Not sure on how you move stuff from the spool file (which you can reach again with "c!") to mbox in mutt, nor whether you can. I use procmail for that. > From there I took the color schemes and changed them a bit to suit > my tastes. These work fine when I load mutt on a console, or telnet > into my box through the network, but when I load mutt in an xterm, > eterm, gnome-terminal, or rxvt, I don't get any colors. All the ls > colors work fine without any adjustments to my terms, so I'm wondering I don't think it's very clearly marked in the FAQ, but there is something about this there. You may have a mutt compiled against slang rather than ncurses (libraries which deal with moving the cursor round the screen and colouring things and stuff, I believe). If so, try this: export COLORFGBG="default;default" Then try mutt again. If it's doing the right colours now, stick that line in your .bash_profile. (This is assuming you're using Linux, which comes with bash. If not, in the dotfile for whatever shell you're using.) Telsa
Re: mbox / inbox & xterm colors
On 2000-01-18 21:14:17 -0600, Bram Shirani wrote: > When I get new mail, it does not go to 'mbox'. I assume, > therefore, it goes to a directory I'll call inbox for now, just > to keep them separate. New mail comes in, it gets put in inbox. > Say I exit mutt and come back later - those messages are then > stored in mbox, (I have it set to do this when I exit...) but any > new messages are again stored in "inbox." My question is how do I > get all new messages automaticlly put into mbox, and then have > mutt start in that directory by default? You'll have to tweak your local mail delivery agent to put messages into ~/mbox directly. However, why not use inbox for this purpose directly and set $hold? > My second question: I used a mixture of muttrc's, one coming from > the mutt home page. From there I took the color schemes and > changed them a bit to suit my tastes. These work fine when I load > mutt on a console, or telnet into my box through the network, but > when I load mutt in an xterm, eterm, gnome-terminal, or rxvt, I > don't get any colors. All the ls colors work fine without any > adjustments to my terms, so I'm wondering if there is a special > option I need to load these terms with. I know this isn't quite a > mutt question, but I got the idea for the colors off the mutt > homepage so I figured I'd give it a whirl. Thanks in advance. Most probably, you'll have to set the TERM environment variable to appropriate values. For instance, TERM=xterm won't give you colors on many systems. Note that this is actually a Good Thing for those who are telnetting around from elderly xterms running on commercial Unices (for example) - imagine, for instance, a stock X11R5 xterm which is suddenly confronted with the latest and greatest Xfree86 xterm's color control sequences. You don't want this. Now, what's the solution? Find out what termcap entry you need for your terminal. Make sure it's set. For xterm on a Debian 2.1 sytem, I'm doing this in my ~/.Xresources: #ifdef COLOR *customization: -color *termName: xterm-xf86-v33 #endif -- http://www.guug.de/~roessler/
mbox v inbox
Ok...I've noticed that mbox and inbox are two separate entities, at least the way I've got mutt configured. What I would like to do is get rid of the "inbox" (where new messages are automaticlly sent) and consolidate them into mbox, which will make procmail much easier to use, and I won't have to switch back and forth between boxes. It'll also be easier when I change to a directory, then want to go back to my new mail, whereas before I quit and opened mutt again, because "inbox" doesn't exist in my list of folders. Can anyone point me in the right direction of how to get started? I'm afraid that if I attempt it, I'll be losing quite a bit of mail for a few days until I figure it out... Thanks in advance, Bram. -- Bram Shirani <[EMAIL PROTECTED]> "UNIX *is* user-friendly, it's just selective of it's friends."
[Announce] mutt-1.0.1 is out.
Mutt-1.0.1 has been released. This is a maintenance release of the stable branch. Changes against Mutt-1.0 include a couple of bug fixes (including the y2k bug), and the addition of some translations. Mutt-1.0.1 has been translated into the following languages: cs, de, el, eo, es, fr, gl, id, it, ko, nl, pl, pt_BR, ru, sk, sv, uk, zh_TW.Big5. There is no reason to upgrade if you don't experience any problems with 1.0. You can immediately download this version of mutt from the following URL: ftp://ftp.mutt.org/pub/mutt/ The new release should propagate to the usual mirror sites within a day of two. Known mirrors include: * ftp://ftp.gbnet.net/pub/mutt-international/ * ftp://ftp.fu-berlin.de/pub/unix/mail/mutt/ * ftp://ftp.gwdg.de/pub/unix/mail/mutt/international/ * ftp://ftp.iks-jena.de/pub/mitarb/lutz/crypt/software/pgp/mutt/ * ftp://uiarchive.cso.uiuc.edu/pub/packages/mail/mutt/ * ftp://ftp.lip6.fr/pub/unix/mail/mutt/ * ftp://ftp.42.org/pub/unix/mail/mutt/ * ftp://gd.tuwien.ac.at/infosys/mail/mutt/ * ftp://ftp.demon.co.uk/pub/mirrors/mutt/ * ftp://ftp.ntua.gr/pub/net/mail/mutt/ * ftp://ftp.cdrom.com/pub/unixfreeware/email/mutt/ * ftp://ftp.kfki.hu/pub/packages/mail/mutt/ * ftp://sunsite.uio.no/pub/mail/mutt/ * ftp://pgp.rasip.fer.hr/pub/mutt/ * ftp://ftp.arch.pwr.wroc.pl/pub/mutt/ * ftp://ftp.uib.no/pub/mutt/ * ftp://ftp.spyda.net/pub/mutt/ * ftp://ftp.linux.it/pub/mirrors/mutt/ * ftp://ftp3.linux.it/pub/mirrors/mutt/ * ftp://ftp.funet.fi/pub/unix/mail/mutt/ * ftp://ftp.is.co.za/networking/mail/mua/mutt/ * ftp://ftp.medasys-digital-systems.fr/pub/unix/mutt/ * ftp://ftp.strasbourg.linuxfr.org/pub/mutt/ * ftp://ftp.parodius.com/pub/mutt/ * ftp://dimonieta.udg.es/mirror/mutt/ * ftp://ftp.jp.qmail.org/mutt/ (Japanese) -- http://www.guug.de/~roessler/ PGP signature
Re: Colour via telnet/ssh
On Tue, Jan 18, 2000 at 04:28:16PM -0600, David DeSimone wrote: > Chris Green <[EMAIL PROTECTED]> wrote: > > > > However, I may not have made myself clear, but running slrn across the > > ssh connection I *do* get colours, whereas running mutt across the > > same link I *don't* get colours. > > You made yourself clear. What perhaps was not made clear to you is > that, unlike slrn, Mutt is a rather pedantic application, and does not > attempt to work around broken terminfo databases. Slrn has the -C > option to force color, even if the terminfo database fails to mention > color. Mutt has no such option, because Mutt believes that you should > fix your terminfo database instead of trying to teach every application > about colors. It is, indeed, the better solution, and Mutt simply takes > a stand that forces you to fix the root problem, rather than treat the > symptoms. > I had sort of realised this and I have fixed it now. I have mutt compiled with S-Lang here and S-Lang gives me the ability to bodge (?) it as required. All I needed to do was to set the environment COLORTERM and to put sensible valuse in COLORFGBG and now I have mutt working in colour across my ssh connection. -- Chris Green ([EMAIL PROTECTED]) Home: [EMAIL PROTECTED] Work: [EMAIL PROTECTED] WWW: http://www.isbd.co.uk/
Re: mbox v inbox
On 2000-01-18 17:48:10 -0600, Bram Shirani wrote: > It'll also be easier when I change to a directory, then want to > go back to my new mail, whereas before I quit and opened mutt > again, because "inbox" doesn't exist in my list of folders. Try ! as the folder name. It's a shortcut for your inbox. -- http://www.guug.de/~roessler/
Coming back to previously _seen_ message
When in a folder with new messages you can go from one to the next new message just pressing "TAB" key. How to come back to the previous new message? Another thing that would be very interesting it to come back to the prior message you've seen. Let's say that if you were reading message 20 and pressed TAB going to message 25. Pressing "come-back-to-last-message" would bring me back to message 20. I know that I can do that with the "goto-message" key, but I need to know the message numbers to use that... Thanks, -- Godoy. <[EMAIL PROTECTED]> GPG Fingerprint 851B B620 626D 2AD0 E783 "Ser poeta não é minha ambição, E932 1330 BE6D A4A3 0625 é minha maneira de estar sozinho" - Fernando Pessoa. Except where explicitly stated I speak on my own behalf. Exceto onde explicitado as declarações aqui feitas são apenas minhas.
Saving complete threads to other mailboxes, possible ?
Hi List, is is possible to save a complete thread to another mailbox in a manner like marking it read (ESC r) ? If so, how ? Kind regards, Lukas
gnupg and mutt
Hello all, I want to use mutt and gnupg (gpg) together, I have seen the "Using PGP from within mutt" at http://www.mutt.org/doc/PGP-Notes.txt and there it says Support for gpg is currentlybeing worked on. Has there been any developments on this front, or does anyone know of a workaround to get gpg working properly? Thanks in advance, -Emil Bjorsell -- IT Manager Ship Company Ltd. http://www.ship.ie/ Phone: +353 26 41314 FAX:+353 1 6335778 Voice Mail: +353 1 6335778 PGP Public Key: http://www.ship.ie/emil.pkr
Re: Saving complete threads to other mailboxes, possible ?
Lukas Ruf <[EMAIL PROTECTED]>: > Hi List, > > is is possible to save a complete thread to another mailbox in a manner > like marking it read (ESC r) ? If so, how ? With the standard key bindings it's: ESC t ; s
Re: problems sending mail w/ mutt, emacs
On Wed, Jan 19, 2000 at 01:31:36PM -0500, [EMAIL PROTECTED] wrote: > i am having problems sending mail. after i have composed a message, > it saves the message as an attachment. is this right, or is there a > way around this? i am using emacs as my editor. also, after i have > sent mail, it always comes back saying that it couldn't be delivered. > i noticed that it is giving the wrong "From:" address. it should read > [EMAIL PROTECTED], but instead it is > [EMAIL PROTECTED] any suggestions? This should also be included in the FAQ (if it isn't there...). The attachment is correct. The problem with "localhost.localdomain" is a misconfiguration of your SMTP. Fix it in sendmail or in the program you use. It's not mutt's fault. It might be possible that your machine is misconfigured (hostname). The right address for sending messages to this list is [EMAIL PROTECTED] -- Godoy. <[EMAIL PROTECTED]> GPG Fingerprint 851B B620 626D 2AD0 E783 "Ser poeta não é minha ambição, E932 1330 BE6D A4A3 0625 é minha maneira de estar sozinho" - Fernando Pessoa. Except where explicitly stated I speak on my own behalf. Exceto onde explicitado as declarações aqui feitas são apenas minhas.
problems sending mail w/ mutt, emacs
i am having problems sending mail. after i have composed a message, it saves the message as an attachment. is this right, or is there a way around this? i am using emacs as my editor. also, after i have sent mail, it always comes back saying that it couldn't be delivered. i noticed that it is giving the wrong "From:" address. it should read [EMAIL PROTECTED], but instead it is [EMAIL PROTECTED] any suggestions?
Re: mbox v inbox
Bram Shirani <[EMAIL PROTECTED]> wrote: > > Ok...I've noticed that mbox and inbox are two separate entities, at > least the way I've got mutt configured. What I would like to do is > get rid of the "inbox" (where new messages are automaticlly sent) and > consolidate them into mbox I suggest you do the opposite, and consolidate all your messages into your "inbox". Add a "set move=no" command to your ~/.muttrc file, so that Mutt will stop moving the messages into "mbox". Then, you'll always find your new mail in your "inbox" and don't have to go looking for it. Mutt defaults to looking at your "inbox" whenever you start it. To get your message out of "mbox", open that folder in Mutt, tag all the message (T, all), then tag-save them to the folder called "!" (which is a synonym for your "inbox"). Press ";" to begin a tagged operation, then "s" to save, and enter "!" as the folder to save the messages to. -- David DeSimone | "The doctrine of human equality reposes on this: [EMAIL PROTECTED] | that there is no man really clever who has not Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson UX WTEC Engineer |PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
Question on cc
I wanted to set mutt up so ever email I wrote was either copied into a file specified by myself, or if I can set it up to send a carbon copy to myslef and be able to set it up so it iwll automatically put the mail in a specified file. Thanks.
Re: Question on cc
On Wed, Jan 19, 2000 at 03:45:10PM -0500, [EMAIL PROTECTED] wrote: > I wanted to set mutt up so ever email I wrote was either copied into a file > specified by myself, or if I can set it up to send a carbon copy to myslef > and be able to set it up so it iwll automatically put the mail in a specified > file. Thanks. try putting this line in your .muttrc set record=+sent-mail (note: the '+' means to put the sent-mail file in your default mail directory) -- - Nick Jennings Email: [EMAIL PROTECTED] Web : http://nick.namodn.com -
Re: Question on cc
Nick Jennings <[EMAIL PROTECTED]> wrote on Wed, 19 Jan 2000: > try putting this line in your .muttrc > > set record=+sent-mail Also check out the variable $copy, setting $record doesn't do anything if $copy is "no". You probably want to also have set copy=yes or perhaps: set copy=ask-yes, if you want to be prompted whether to save a copy or not. The default value for $copy is "yes", but maybe you have it set to some other value. 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 / jfortune: cannot run. Cookie jar empty.
Re: Question on cc
On Wed, Jan 19, 2000 at 01:15:18PM -0800, Nick Jennings wrote: Thank you very much for your help, it worked. Thanks. > On Wed, Jan 19, 2000 at 03:45:10PM -0500, [EMAIL PROTECTED] wrote: > > I wanted to set mutt up so ever email I wrote was either copied into a file > > specified by myself, or if I can set it up to send a carbon copy to myslef > > and be able to set it up so it iwll automatically put the mail in a specified > > file. Thanks. > > try putting this line in your .muttrc > > set record=+sent-mail > > > (note: the '+' means to put the sent-mail file in your default mail > directory) > > > -- > - Nick Jennings > Email: [EMAIL PROTECTED] > Web : http://nick.namodn.com > -
web page links
Several links to patches/etc. have gone by in the last week or two... unfortunately I've been busy and haven't had a lot of time to monitor the list lately. I did add the following to http://www.mutt.org/links.html: http://alcor.concordia.ca/~rich/mutt/ http://www.albedo.art.pl/~kbryd/mutt/ http://www.linuxstart.com/~jheinonen/abook/ If there are others any of you think should be added, please mail me directly and let me know. For those that have been asking, the latter two of the above deal with extended address book handling. One is a patch, the other is an external program. -- Jeremy Blosser | [EMAIL PROTECTED] | http://jblosser.firinn.org/ -+-+-- "If Microsoft can change and compete on quality, I've won." -- L. Torvalds PGP signature
Question on Attachments
I was trying to open an email image attachment. When I went to open it it tried to open it with Electric Eyes. I do not use electric eyes and I cannot find a line in the rc file that deals with changing which program handles images or files. Thanks.
Re: Question on Attachments
[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote on Wed, 19 Jan 2000: > I was trying to open an email image attachment. When I went to open it > it tried to open it with Electric Eyes. I do not use electric eyes and I > cannot find a line in the rc file that deals with changing which program > handles images or files. Thanks. Mutt uses the "mailcap" file on your system to determine what to do with each kind of file in a MIME-message. This is usually either /etc/mailcap or ~/.mailcap (or both together). You can also tell Mutt where to look for the mailcap file by setting the $mailcap_path variable in your .muttrc, though usually the default value works just fine. Anyway, the reason why Electric Eyes is attempted to use for whatever type of image you tried to view, it was because your system's existing mailcap file has a definition that says that for that kind of image, Electric Eyes is used. If you don't have or don't want to use Electric Eyes, you should modify the mailcap settings accordingly. 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 / Mathematician, n: A machine for converting coffee into formulas.
Re: Saving complete threads to other mailboxes, possible ?
Lukas Ruf [[EMAIL PROTECTED]] wrote: > Hi List, > > is is possible to save a complete thread to another mailbox in a manner > like marking it read (ESC r) ? If so, how ? > > Kind regards, > > Lukas > I use the following macro to do it: bind index ssave-message bind index t tag-thread macro index S "t;s" "Save whole thread, and then delete the thread" -- Shao Zhang - Running Debian 2.1 ___ _ _ Department of Communications/ __| |_ __ _ ___ |_ / |_ __ _ _ _ __ _ University of New South Wales \__ \ ' \/ _` / _ \ / /| ' \/ _` | ' \/ _` | Sydney, Australia |___/_||_\__,_\___/ /___|_||_\__,_|_||_\__, | Email: [EMAIL PROTECTED] |___/ _
Re: mutt/vim/sigdashes question
On Tue 01/18/00 at 10:00 AM -0500, David T-G <[EMAIL PROTECTED]> wrote:
> Since you reference lines 2/3 you are probably not using edit_headers and
> wouldn't be interested in setting your editor variable to something like
> set editor="vim +/^$"
> to put the cursor at the first blank line. But it might help.
It did help. I decided to start using edit_headers because without them
I always wondered, as I was writing a mail, if I had the correct address on
the 'To:' header-line. I'd have to wait til I got into the compose menu,
after writing the mail, to see it. And sometimes I'd forget to look at it
before sending a mail.
But I'm still not sure how to make a mutt macro to automatically put me
into vim in insert mode. Right now I have this .muttrc macro:
(where '_A' is mapped to mutt's original 'm' command):
# Start cursor at line 8 (with edit_headers set)
# in vim's insert mode when composing new mails ('m'):
macro index m":set editor='vim +8'^M_A" "compose a new mail message"
macro pager m":set editor='vim +8'^M_A" "compose a new mail message"
The problem is that almost anything I put after 'vim ... is read as a
filename. Not sure how to get around that, any tips appreciated.
--
// [EMAIL PROTECTED] //
