x-mailer header
my messages carry a "x-mailer: mutt" header that i'd like to get rid of. how do i do that? -- clemens [EMAIL PROTECTED] do D4685B884894C483
Re: x-mailer header
On Sat, May 20, 2000 at 10:39:21AM +0200, clemensF wrote: my messages carry a "x-mailer: mutt" header that i'd like to get rid of. how do i do that? unset user_agent (mutt 1.2 only) Reinhard
Re: support for compressed folders in 1.2?
Zhendong: folders. After I've changed the mutt folders to gz format, procmail still delivers mails as uncompressed format, they can not work well together. then run the mails through gzip. the line "| gzip folder" will append compressed data to the folder. this has nothing to do with mutt. furthermore, the attitude behind the statement "...they can not work well together" drives me up the wall. do you really silently expect any program to foresee every users needs and integrate all possible solutions? this is the opposite of unix thinking, where a number of independant little programs to their speciality bound into a framework by a smart and small operating system, which operates the same way. your statement reveals micro$oft thinking: give the users one big babel tower, and if they can't get their tasks done with it, it cannot be done at all! gzip does not even have to uncompress the target file to append new data, it handles compressed data streams well. -- clemens [EMAIL PROTECTED] do D4685B884894C483
Re: x-mailer header
Reinhard Foerster proclaimed on mutt-users that: On Sat, May 20, 2000 at 10:39:21AM +0200, clemensF wrote: my messages carry a "x-mailer: mutt" header that i'd like to get rid of. how do i do that? unset user_agent (mutt 1.2 only) +That+ will get rid of the User-Agent: Mutt 1.2i. I doubt if it will get rid of the X-Mailer tag (which is not generated by newer mutts anyway). -- Suresh Ramasubramanian | sureshr at staff.juno.com An idea is not responsible for the people who believe in it.
Re: support for compressed folders in 1.2?
clemensF proclaimed on mutt-users that: the opposite of unix thinking, where a number of independant little programs to their speciality bound into a framework by a smart and small operating system, which operates the same way. your statement reveals micro$oft thinking: give the users one big babel tower, and if they can't get their tasks done with it, it cannot be done at all! heresy Sounds a lot like emacs thinking to me :) g,dr -- Suresh Ramasubramanian | sureshr at staff.juno.com An idea is not responsible for the people who believe in it.
Re: support for compressed folders in 1.2?
Yuzhendo Zhendong (perhaps one and the same) -- ...and then [EMAIL PROTECTED] said... % Can we use Procmail to play with the compressed mail folders? Since I % found that even when mutt can deal with compressed folders, procmail % will not deliver mails in compressed format. So there will some % problems. ...and then Zhendong said... % % Then what about the supporting for compressed mail folders in procmail % when using mutt? I use procmail to deliver mails to different mail % folders. After I've changed the mutt folders to gz format, procmail % still delivers mails as uncompressed format, they can not work well % together. I'll leave the explanation from our friend clemens alone and also leave all of the credit for the rant :-) Yes, you can use procmail with compressed folders by compressing your incoming mail (| gzip -c) before it writes to the folder ( box.gz). Be sure that you do sufficient locking (no, I still haven't really figured out procmmail locking and when I should specifiy a lock and when not and ...) to guarantee that only one stream at a time is appended to your mailbox; mixing two at once is bad even if the file doesn't get wiped. Before messing with all of that, though, I'd ask "why on earth are you delivering to a compressed folder??" because it's just one more step to handle. In order for mutt to read the compressed folder it's going to have to uncompress it to a temp file first, and you certainly don't want to have to mess with that every time you go to read mail. Why not deliver to an uncompressed mailbox (of some sort -- mbox, maildir, MH) as usual, read your mail as usual, and then archive (perhaps with good old $move though you may have to do some tweaking to tell it how to move from box to box.gz) to a compressed folder? The mail is still available in case you need to go back in time, but the stuff you're likely to use regularly is *easy* to use. Just my twenty millibucks; YMMV. 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: x-mailer header
clemens -- ...and then clemensF said... % my messages carry a "x-mailer: mutt" header that i'd like to get rid of. % how do i do that? I'd try something like my_hdr X-Mailer: "" to generate an empty header, which mutt will then not include. I don't think there's a $variable for that in versions which still have that (instead of User-Agent: as some have already shown how to remove). % % -- % clemens [EMAIL PROTECTED] % do D4685B884894C483 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: Interesting From: header problem
Mikko Hänninen: I guess what I'm basically looking for is a reply-hook. Something that I can use to change things based on the message I'm replying to. Does anything like that exist? Nope, sorry. There's been talk of ways to solve this, and I think even the best way has been figured out (creating a pseudo-operator which tells that the next pattern operator should match against the headers of the replied-to message, not the current message, which could then be used in send-hooks). It's just that nobody's done it yet. there's always the possibility to pipe the mess thru some external program, either in the editor or perhaps with some construct involving ":source program |". -- clemens [EMAIL PROTECTED]
Re: support for compressed folders in 1.2?
Hi clemensF, David T-G Thank you for pointing me out :) David T-G wrote: I'll leave the explanation from our friend clemens alone and also leave all of the credit for the rant :-) Yes, you can use procmail with compressed folders by compressing your incoming mail (| gzip -c) before it writes to the folder ( box.gz). Be sure that you do sufficient locking (no, I still haven't really figured out procmmail locking and when I should specifiy a lock and when not and ...) to guarantee that only one stream at a time is appended to your mailbox; mixing two at once is bad even if the file doesn't get wiped. Before messing with all of that, though, I'd ask "why on earth are you delivering to a compressed folder??" because it's just one more step to handle. In order for mutt to read the compressed folder it's going to have to uncompress it to a temp file first, and you certainly don't want to have to mess with that every time you go to read mail. Why not deliver to an uncompressed mailbox (of some sort -- mbox, maildir, MH) as usual, read your mail as usual, and then archive (perhaps with good old $move though you may have to do some tweaking to tell it how to move from box to box.gz) to a compressed folder? The mail is still available in case you need to go back in time, but the stuff you're likely to use regularly is *easy* to use. Just my twenty millibucks; YMMV. 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*
Re: Interesting From: header problem
clemensF [EMAIL PROTECTED] wrote on Sat, 20 May 2000: there's always the possibility to pipe the mess thru some external program, either in the editor or perhaps with some construct involving ":source program |". How does that help in the situation we were discussing? Well, I guess you could do a script that reads the message-to-be-replied to, writes a template reply email out to a file, and then this could be used with the resend-message (or edit-postponed) in Mutt as a basis of the new email... It would work, but you'd be taking all the intelligence with regards to lists and send-hooks and all that outside of Mutt. And it would be quite a bit of work, probably, to do such a script. 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 only substitute for good manners is fast reflexes.
Re: Interesting From: header problem
Mikko Hänninen proclaimed on mutt-users that: clemensF [EMAIL PROTECTED] wrote on Sat, 20 May 2000: there's always the possibility to pipe the mess thru some external program, either in the editor or perhaps with some construct involving ":source program |". How does that help in the situation we were discussing? Well, I guess you could do a script that reads the message-to-be-replied to, writes a template reply email out to a file, and then this could be used with the resend-message (or edit-postponed) in Mutt as a basis of Stupidest solution possible - set edit-headers :) -- Suresh Ramasubramanian | sureshr at staff.juno.com Alas, I am dying beyond my means. -- Oscar Wilde, as he sipped champagne on his deathbed
more colors
Is it possible to have mutt recognise more than the "standard" colors. Like I can get vim to display all the colors like lightblue or darkcyan etc? -- Eric Smith also on 082 373 1224
Re: more colors
Eric Smith proclaimed on mutt-users that: Is it possible to have mutt recognise more than the "standard" colors. Like I can get vim to display all the colors like lightblue or darkcyan etc? Take a look at this - scarfed from an old post on mutt-users. Tim, if you;re reading this - I _love_ your color settings ... # Tim Waugh's .muttrc # Colours color quoted green default color signature red default color indicator brightyellow red color error brightred default color status yellow blue color tree magenta default # the thread tree in the index menu color tilde magenta default color message brightcyan default color markers brightcyan default color attachment brightmagenta default color search default green # how to hilite search patterns in the pager color body magenta default "(ftp|http)://[^ )]+" # point out URLs color body magenta default [-a-z_0-9.]+@[-a-z_0-9.]+# e-mail addresses color underline brightgreen default # Mail from people in my company (but not listed in the scores file) # should appear with a red background. ;-) color index default red '(~f @redhat\.com) | (~f @redhat\.de) | (~f @cygnus\.com)' # Put high-scoring messages in bold color index brightwhite default '~n 4-' # I'm interested in messages containing the word 'parport' in the body, # especially if they don't come from the linux-parport list (those are # the hard ones to spot). So colour them green. I love mutt. ;-) color index brightgreen default '!(~B owner-linux-parport) ~b parport' # Hmm, pine can do this better.. # I want different people's text to appear in different colours. So # the colour depends on the number of times it's been quoted.. color body blue default "^ * * *.*" # quoted quoted quoted color body red default "^ * *.*" # quoted quoted hth hand -- Suresh Ramasubramanian | sureshr at staff.juno.com Alas, I am dying beyond my means. -- Oscar Wilde, as he sipped champagne on his deathbed
Re: support for compressed folders in 1.2?
On Sat, 20 May 2000, Zhendong wrote: Then what about the supporting for compressed mail folders in procmail when using mutt? I use procmail to deliver mails to different mail folders. After I've changed the mutt folders to gz format, procmail still delivers mails as uncompressed format, they can not work well together. It's possible to append mails to gzipped folders by something like | gzip folder in your .procmailrc. BUT DON'T DO THIS, if you do not want to loose mail! IIRC, there is no mechanism to merge changes in the compressed folder into the temporary uncompressed folder, so if you have a compressed folder open for reading, while a new mail arrives and is appended to this compressed folder, it will never been shown, but simply overwritten, when leaving the compressed folder with mutt. I suggest to use compressed folders only for archive folders but not for incoming folders. Tscho Roland -- * [EMAIL PROTECTED] * http://www.spinnaker.de/ *
A word about submitting patches.
When submitting patches for the mutt code, please make sure you follow a couple of elementary guidelines: - Post your patch to mutt-dev, and make sure they are marked somehow in the subject of the message. While I generally try to read mutt-dev completely, this will make it more difficult to miss patches. - Please make sure you stick to the code formatting conventions used throughout the rest of the mutt code. - Please document your changes. - Please read doc/devel-notes.txt before patching, it has some important notes on where to change things and where not to change things. (This is mostly important with documentation, since it's partially autogenerated, and changing generated files won't help.) Thanks. -- http://www.guug.de/~roessler/ PGP signature
Re: support for compressed folders in 1.2?
Roland Rosenfeld: | gzip folder BUT DON'T DO THIS, if you do not want to loose mail! IIRC, there is no mechanism to merge changes in the compressed folder into the temporary uncompressed folder, so if you have a compressed folder open for reading, while a new mail arrives and is appended to this compressed folder, it will never been shown, but simply overwritten, when leaving the compressed folder with mutt. I suggest to use compressed folders only for archive folders but not for incoming folders. an exception might be allowed if the folder is protected by a lock. but when looking at the details, updating a compressed folder while it's uncompressed temporary image is open for reading will not damage anything. but when the folder isn't locked and =updated= by the viewer when mail is appended at the same time, things might well go wrong. -- clemens [EMAIL PROTECTED]
Re: x-mailer header
Reinhard Foerster: On Sat, May 20, 2000 at 10:39:21AM +0200, clemensF wrote: my messages carry a "x-mailer: mutt" header that i'd like to get rid of. how do i do that? unset user_agent (mutt 1.2 only) oh no, nono, please, there =has= to be a way! please, save me! do i have to set sendmail='/local/bin/mutt-go-away | sendmail'? -- clemens [EMAIL PROTECTED] do D4685B884894C483
Re: x-mailer header
Suresh Ramasubramanian: unset user_agent (mutt 1.2 only) +That+ will get rid of the User-Agent: Mutt 1.2i. I doubt if it will get rid of the X-Mailer tag (which is not generated by newer mutts anyway). i think you repeat exactly what he said, and i'm not really sure if i am grateful for it. anyways, folks, i will undertake the task of pipapatching mutt away from mutt! -- clemens [EMAIL PROTECTED]
Re: x-mailer header
David T-G: I'd try something like my_hdr X-Mailer: "" no go. recompiled the whole s**t. bet'ya can't see no heada! -- clemens [EMAIL PROTECTED]
Re: support for compressed folders in 1.2?
Suresh Ramasubramanian: heresy Sounds a lot like emacs thinking to me :) g,dr you, youDANGEROUS PERSON!
Re: Interesting From: header problem
Mikko Hänninen: Well, I guess you could do a script that reads the message-to-be-replied to, writes a template reply email out to a file, and then this could be used with the resend-message (or edit-postponed) in Mutt as a basis of the new email... It would work, but you'd be taking all the intelligence with regards to lists and send-hooks and all that outside of Mutt. And it would be quite a bit of work, probably, to do such a script. ...which might be worth it if we find a general principal behind the problem which lets us use the solution in more than just this case. sorry, but my imagination fails me on this one, i just thought this thread might need a turn. -- clemens [EMAIL PROTECTED]
