Manually Setting References
I often want to associate one or more other emails with one which I am editing to send. I expect to be able to grab the references from the `Message-ID:' headers and include them in a `References:' header line which I add to the message I'm editing. I do this by pressing `E' in the compose window which is bound to the `edit-headers' command. However afterwards it has silently dropped the References:' header! What can be done? -- -Vance
Re: Manually Setting References
On Wed, Sep 28, 2011 at 09:24:09AM -0400, Patrick Shanahan wrote: } Another thought came to mind, you are *editing* (adding/altering) the } *existing* References: header, yes ? No, I'm adding attempting to add the `References:' header as there isn't one in a new message. I did see your `abcd' so I guess it does work to edit an existing `References:' header. -- -Vance
Re: Manually Setting References
The reason I use mutt is to have the greatest control over my email. If I say there is a thread there is a thread! On Thu, Sep 29, 2011 at 12:30:03AM -0400, Patrick Shanahan wrote: } Right, need to be a thread, 1 msg, for the References: header to exist } :^) A single, new message has nothing to refer to. -- -Vance
Re: [Feat Req] reverse_alias workalike for replies
On Mon, Feb 15, 2010 at 02:45:19AM +0100, 725...@gmail.com wrote: } I'd like Mutt to rewrite the Real name part of the addresses } with the corresponding neat and tidy names in my ~/.mail_aliases file: That would be awesome! -- -Vance
Re: default color transparency broken in Snow Leopard
On Thu, Sep 10, 2009 at 03:15:52PM -0500, Kyle Wheeler wrote: } I do it by adding the following to my ~/.bashrc file: } } export TERM=nsterm-16color I see now that setting the terminal type in Preferences - Advanced - Emulation - Declare terminal as: is really just setting the environment variable and not changing the emulation behaviour as I had assumed. I tried the above and experienced the same results. } I don't notice that any of my backgrounds are non-transparent, though. Very odd indeed. I'm looking for other ncurses based programs to see if they also fail on transparency. -- -Vance
Re: default color transparency broken in Snow Leopard
On Wed, Sep 09, 2009 at 02:32:53PM -0500, Kyle Wheeler wrote: } What's your TERM setting? I usually use dtterm, which as I understood it was the most compatible with Terminal.app. I just tried all of ansi, xterm, xterm-color, rxvt and vt100. All of them show the same color problem except the latter which comes up in black and white. } I use nsterm-16color for Apple's Terminal.app I don't know how you do that as there is a short list available in the preferences window and that's not on it. Can you try opening up a stock Terminal.app window and see if you get similiar issues? -- -Vance
default color transparency broken in Snow Leopard
Since upgrading to Snow Leopard my colour definitions are messed up. Anywhere where I set the colour I use 'default' for the background colour so that it remains whatever the current background colour is. With the upgrade this no longer works, the background gets set to ANSI white (grey). For example in my .muttrc file I have: color error brightred default Where I a black on white Terminal.app screen the error will be red on grey. Using 'default' for the background is supposed to leave it set as it was. In this way, by just setting foreground colors, the same settings may be usable with different background colors in Terminal.app (e.g. white on black). Apparently this functionality is provided by an extension to curses provided in ncurses; use_default_colors(). I aquired the latest source and built it myself, I had been using macports, and I see that it sets HAVE_USE_DEFAULT_COLORS and links against Apple's ncurses library. Has anyone any idea what is wrong here? -- -Vance
Status flags in attachment menu
What is the meaning of the flag in the attachment menu? I see 'I' and 'A' but I con't find any description of these flags in the documentation. -- -Vance
Re: where does it search
Bill, Something which is undocumented, as far as I can see, is that when working with an IMAP mail store you can search conduct the search on the server. If you do a /~b it will have to download all the messages to do the search. If you replace '~' with '=' in your search pattern (e.g. /=b foo) it will compile a search function and send it to the server. This should really make it into the manual as it's very important for IMAP users. -Vance On Fri, Sep 26, 2008 at 12:03:12AM +0800, bill lam wrote: } In index page, / or T can search a pattern or regex, and there are } modifiers like ~h ~b to force searching inside header or body etc. } But what is the context for searching without any such modifiers, does } it search the header or body or just what is visible of the index } screen?
Re: where does it search
Kyle, I have been using a bookmark for http://www.mutt.org/doc/manual. I now see that a more up to date manual is here http://dev.mutt.org/doc/manual.html where this is documented. -Vance On Thu, Sep 25, 2008 at 11:48:17AM -0500, Kyle Wheeler wrote: } From the muttrc man page: } } =b STRING messages which contain STRING in the message body. If } IMAP is enabled, searches for STRING on the server, } rather than downloading each message and searching it } locally.
Re: Configuring sendmail on Mac OS X (Leopard)?
On Mon, Sep 08, 2008 at 09:50:25AM +0200, [EMAIL PROTECTED] wrote: } I have to use certain e-mail addresses when sending mail to specific } sites (i.e.: university and gmail, for example). I was using: } } my_hdr From: Joan university address Instead of changing the value of mutt's configuration variable 'sendmail' from the default you should set the configuration variable 'envelope_from'. If that is set, the default is not, if you have set the 'From:' header as above it will add the -f Joan university address to the call to sendmail. To handle multiple mailboxes you set folder hooks: http://www.mutt.org/doc/manual/manual-3.html#ss3.5 First set the default state to something reasonable: folder-hook . set folder=~/Mail folder-hook . set signature=.signature folder-hook . set envelope_from=no folder-hook . unmy_hdr from organization Then set folder hooks to set things specific to each folder: folder-hook gmail\\.com set folder=imaps://imap.gmail.com folder-hook gmail\\.com my_hdr Organization: Scrapbook Club folder-hook gmail\\.com my_hdr From: Scrappy [EMAIL PROTECTED] folder-hook gmail\\.com set envelope_from=yes folder-hook university\\.edu set folder=imaps://mail.university.edu folder-hook university\\.edu my_hdr Organization: University of the Universe folder-hook university\\.edu my_hdr From: Dean Serious [EMAIL PROTECTED] folder-hook university\\.edu set envelope_from=yes Each time you enter a folder matching 'gmail\\.com' you will adopt the 'Scrappy' identity. Switching to a folder matching 'university\\.edu' adopts the 'Dean Serious' identity. Changing to a folder which does not match one of the above matches '.' and unsets the folder specific settings. That handles incoming. Now to get outgoing mail sent to the right mail server you need to deal with postfix. In OS X Leopard you are lucky enough to have a recent enough version of postfix to use 'sender_dependent_relayhost_maps'. Configure your default outgoing mail settings in /etc/postfix/main.cf. For example: mydomain = deanserious.org myorigin = $mydomain relayhost = [mail.deanserious.org]:587 smtp_use_tls = yes smtp_sasl_auth_enable = yes smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd tls_random_source = dev:/dev/urandom The above sets up a default mail submission port (587) using STARTTLS to secure the channel and then authenticates the user using the plain text passwords stored in /etc/postfix/sasl_passwd: mail.deanserious.orgdeans:My Password has spaces smtp.gmail.com scrappy:9secret7 mail.university.edu seriousd:a6RtF42po7rt9 The plain text sasl_passwd file must be hashed into 'sasl_passwd.db': $ postmap /etc/postfix/sasl_passwd You don't want your passwords readable by guest users: $ chown 600 /etc/postfix/sasl_passwd $ chown 600 /etc/postfix/sasl_passwd.db Add configuration for sender specific maps in /etc/postfix/main.cf: sender_dependent_relayhost_maps = hash:/etc/postfix/sender_relay Map matching from addresses to outgoing mail servers to use in the plain text /etc/postfix/sender_relay file: @gmail.com [smtp.gmail.com]:587 @university.edu [mail.university.edu]:587 And finally hash the sender relay maps: $ postmap /etc/postfix/sender_relay Outgoing mail will now be sent to mail.deanserious.org unless it matches '@gmail.com' or '@university.edu' in which case it will be sent to the mail submission port (587) on 'smtp.gmail.com' and 'mail.university.edu' respectively. -Vance
