Re: [newbie] Hostname, localhost.localdomain
Glenn Bajana wrote: ... I've ``set hostname=curly''. This only appears in the Mutt message-ids, i.e., local mail I compose for tests shows in vi as glenn@curly, but when received it appears as [EMAIL PROTECTED] Local emails (in Mail as well as Mutt) show localhost.localdomain in the message-ids. ... Hi, I think you need to setup masquerading for sendmail as previously suggested but if you want the headers to show glenn@curly and curly.localdomain instead of [EMAIL PROTECTED] and localhost.localdomain you could try putting this in /etc/HOSTNAME: curly.localdomain and in /etc/hosts put: 127.0.0.1 localhost 127.0.0.2 curly.localdomain curly Hope this helps. Michael
Re: [newbie] Hostname, localhost.localdomain
On Mon, Apr 24, 2000 at 02:30:23AM -0400, Michael Hong wrote: Glenn Bajana wrote: ... I think you need to setup masquerading for sendmail as previously suggested but if you want the headers to show glenn@curly and curly.localdomain instead of [EMAIL PROTECTED] and localhost.localdomain you could try putting this in /etc/HOSTNAME: curly.localdomain and in /etc/hosts put: 127.0.0.1 localhost 127.0.0.2 curly.localdomain curly Sendmail should do this for him if the masquerading is set up properly. The MASQUERADE_AS and masquerade_envelope feature ensure this. I've had the occasional problem in mutt as it attempts to handle the from field, but judicious use of "hostname" or "hidden_host" seemed to put sendmail back in control. Mike
Re: feature request: graft and prune functions
On Wed, Apr 19, 2000 at 09:03:44AM +0200, Thomas Roessler muttered: - On 2000-04-19 00:18:22 -0400, David T-G wrote: - - Thoughts? - - Real men use edit-message for this functionality. But - then again, real men also read their e-mail with dd(1). - - :-) _REAL_ programmers read their email in braille by passing their fingers over the magnetic domains on the hard drive platter. :-) -- -- C^2 No windows were crashed in the making of this email. Looking for fine software and/or web pages? http://w3.trib.com/~ccurley
Re: [newbie] Hostname, localhost.localdomain
Rishi was happy when ;-) Michael Hong wrote this on Mon, Apr 24, 2000 at 02:30:23AM -0400 Glenn Bajana wrote: ... I've ``set hostname=curly''. This only appears in the Mutt message-ids, i.e., local mail I compose for tests shows in vi as glenn@curly, but when received it appears as [EMAIL PROTECTED] Local emails (in Mail as well as Mutt) show localhost.localdomain in the message-ids. ... Hi, I think you need to setup masquerading for sendmail as previously suggested but if you want the headers to show glenn@curly and curly.localdomain instead of [EMAIL PROTECTED] and localhost.localdomain you could try putting this in /etc/HOSTNAME: curly.localdomain and in /etc/hosts put: 127.0.0.1 localhost 127.0.0.2 curly.localdomain curly This is fine with me and works to send the mails to the previous nonresponsive domains but it has created a problem now i cant poll my ISP which is bom7.vsnl.net.in and defined in my /etc/hosts file as 127.0.0.2 so i have to poll at the IP address. No problem but the entire setup looks ugly Hope this helps. Michael -- Signature Follows :-: -- Rishi Maker Tel No. 91-22-5374892 Carpe Diem --- Q: What do you say to a New Yorker with a job? A: Big Mac, fries and a Coke, please!
Re: [newbie] Hostname, localhost.localdomain
On Mon, Apr 24, 2000 at 09:20:06PM +0530, Rishi Maker wrote: Rishi was happy when ;-) Michael Hong wrote this on Mon, Apr 24, 2000 at 02:30:23AM -0400 Glenn Bajana wrote: ... I've ``set hostname=curly''. This only appears in the Mutt message-ids, i.e., local mail I compose for tests shows in vi as glenn@curly, but when received it appears as [EMAIL PROTECTED] Local emails (in Mail as well as Mutt) show localhost.localdomain in the message-ids. ... Hi, I think you need to setup masquerading for sendmail as previously suggested but if you want the headers to show glenn@curly and curly.localdomain instead of [EMAIL PROTECTED] and localhost.localdomain you could try putting this in /etc/HOSTNAME: curly.localdomain and in /etc/hosts put: 127.0.0.1 localhost 127.0.0.2 curly.localdomain curly This is fine with me and works to send the mails to the previous nonresponsive domains but it has created a problem now i cant poll my ISP which is bom7.vsnl.net.in and defined in my /etc/hosts file as 127.0.0.2 so i have to poll at the IP address. No problem but the entire setup looks ugly Why, would you want your ISP to be 127.0.0.2 ? Change that /etc/hosts entry to the correct IP and you'll be fine. Michael -- Recursion is the root of computation since it trades description for time. PGP-fingerprint: DECA E9D2 EBDD 0FE0 0A65 40FA 5967 ACA1 0B57 7C13
Re: Hostname, localhost.localdomain
I think you need to setup masquerading for sendmail as previously suggested but if you want the headers to show glenn@curly and curly.localdomain instead of [EMAIL PROTECTED] and localhost.localdomain you could try putting this in /etc/HOSTNAME: The problem with doing sendmail masquerading is that then you end up having the wrong address in secondary email headers, eg. Mail-Followup-To, if that ever gets used... Sendmail masquerading doesn't know to change the MFT header. So it's better indeed to set up things so that the email headers are correct already when Mutt sends the email. (just a general comment to the thread...) 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 / Free the mallocs!
Re: source $TERM ?
On Sat, Apr 22, 2000 at 09:21:58PM +0200, Steffan Hoeke wrote: I know, but I copied a $TERM for a xterm from that site, but when I started mutt in an xterm I got NO color, so I wanted to check if I copied the file correcty. [...] That might well be due to the setting of $TERM itself. I had problems with that with an ncurses-linked mutt, where ncurses wouldn't recognise my xterms or rxvts as colour-capable (with TERM set to "xterm"). For the time being, I'm using a wrapper script which sets TERM to "xterm-color" before starting mutt itself - that gave me the colours. I know it's not the best of all solutions, but it does the job... :-} HTH, Thomas -- - Thomas Ribbrockhttp://www.bigfoot.com/~kaytanICQ#: 15839919 "You have to live on the edge of reality - to make your dreams come true!"
Multiple Folder Locations (Local IMAP)
Is there a way to specify multiple locations for folders for mutt. Eg. Fetchmail pulls mail from pop server I want to be able to save these messages locally. I also have e-mail on an imap server when I save a message from the imap server I want to save it to an imap folder. Is this doable? -- Michael Donaghy Treasurer, NCSU ACM/AITP, 1999-2001 [EMAIL PROTECTED]Webmaster, Linux User's Group @ NCSU (919) 512-1144 COE Computer Committee U-Grad. Rep. N.C. State UniversityCSC Student
gzip format
Hi, What should I add in my .muttrc so that I can read the gziped folders ? Thanks Jayan -- \\\|/// \\ _ _ // ( @ @ ) +--oOOo-(_)-oOOo--+ | A.V.JAYANTHAN | |[EMAIL PROTECTED] | |URL : http://www.math.iitb.ernet.in/~jayan | | | | Dept. of Mathematics, IIT(B), Powai, Mumbai-76.| | | | Ph. 022 - 5781007, 5779719 R. No. 262.| +Oooo-+ oooO ( ) ( )) / \ ((_/ \_)
Help with color
I have these lines: color index brightwhite default * color index yellow default '~l' color index brightyellowdefault '~N ~l' in my .muttrc file. As most of you know, messages that are from a list (defined in .muttrc) are yellow. "New" list messages are bright yellow. My problem is after the message has been read, it changes to a color that makes the text literally illegible. This may be related to my mutt window (under X-Windows) being an Eterm window with an image background. Regardless, I want to know how to define a color for "read" "list" messages. How do I do that ?? I *tried* this: color index green default '~R ~l' I made an assumption that "~R" would get "read" messages... but I was wrong. ;-) Any help is appreciated. Regards, Hall
http://www.mutt.org/
How do i make my mutt not READ-ONLY?
Re: http://www.mutt.org/
Christoffer -- ...and then Christoffer A. Elo said... % How do i make my mutt not READ-ONLY? You will need to install mutt_dotlock with mail group execute permissions so that it can make changes in the mail spool directory where you, the normal user, cannot. In short, have root install it for you or do the "make install" as root yourself. :-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: Multiple Folder Locations (Local IMAP)
Michael -- ...and then Michael Donaghy said... % Is there a way to specify multiple locations for folders for mutt. % % Eg. Fetchmail pulls mail from pop server I want to be able to save % these messages locally. I also have e-mail on an imap server when I % save a message from the imap server I want to save it to an imap folder. % % Is this doable? In short, read up on folder-hooks, which do things (like change settings) based on the folder you're reading (versus a send-hook, which keys from your recipients, for example). They are documented in the manual.txt file that comes with mutt. % % -- % Michael Donaghy Treasurer, NCSU ACM/AITP, 1999-2001 % [EMAIL PROTECTED]Webmaster, Linux User's Group @ NCSU % (919) 512-1144 COE Computer Committee U-Grad. Rep. % N.C. State UniversityCSC Student :-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: Help with color
Hall Stevenson [EMAIL PROTECTED] wrote on Mon, 24 Apr 2000: I *tried* this: color index green default '~R ~l' I made an assumption that "~R" would get "read" messages... but I was wrong. ;-) I don't know about Mutt 1.0, although I think it should be the same, but in Mutt 1.1.9 at least ~R is indeed "read messages". So without actually trying anything, "~R ~l" should work. You could also try !~N instead of ~R, ie. "not new". 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 / After the prices hit the ceiling they go through the roof.
Re: Help with color
* Mikko Hänninen ([EMAIL PROTECTED]) [000424 09:47]: Hall Stevenson [EMAIL PROTECTED] wrote on Mon, 24 Apr 2000: I *tried* this: color index green default '~R ~l' I made an assumption that "~R" would get "read" messages... but I was wrong. ;-) I don't know about Mutt 1.0, although I think it should be the same, but in Mutt 1.1.9 at least ~R is indeed "read messages". So without actually trying anything, "~R ~l" should work. You could also try !~N instead of ~R, ie. "not new". Well, actually they *both* work... ;-) It turns out that my choice of color(s) was the problem !! But, at this point, I'm using your way, the "!~N" flag. Thank you very much ! Hall
