How to build mutt
I know it should be as simple as './configure [some options]' followed by 'make install', but I am at a loss knowing which options I should apply in order to have the same capabilities as another build's. For example in order to have +BUFFY_SIZE -DEBUG -DL_STANDALONE -DOMAIN +ENABLE_NLS -EXACT_ADDRESS +HAVE_BKGDSET +HAVE_COLOR +HAVE_CURS_SET -HAVE_GETADDRINFO +HAVE_GETSID +HAVE_ICONV +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_META +HAVE_PGP +HAVE_REGCOMP +HAVE_RESIZETERM +HAVE_START_COLOR +HAVE_TYPEAHEAD -HAVE_WC_FUNCS -HOMESPOOL -ICONV_NONTRANS -ISPELL +LOCALES_HACK -SUN_ATTACHMENT -USE_DOTLOCK +USE_FCNTL -USE_FLOCK +USE_GNU_REGEX -USE_GSS +USE_IMAP +USE_POP -USE_SASL -USE_SETGID +USE_SSL are all the capabilities included using "--enable-WHATEVER"? if so, why do some final results start with USE, some with HAVE, and others nothing special at all? If not, how do I enable/disable them? Additionally, is it possible to not build/install the documentation somehow? Trying to do that here gives me an error and then make stops *sigh* make[2]: Entering directory `/usr/src/mutt/doc' ##test -f manual.html || make manual.html || cp ./manual*.html ./ cp ./manual*.html ./ cp: cannot stat `./manual*.html': No such file or directory make[2]: *** [try-html] Error 1 make[2]: Leaving directory `/usr/src/mutt/doc' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/usr/src/mutt' make: *** [install] Error 2 Why would anyone want to copy ./ to the same place anyway? Any why on earth would they expect that to succeed?
Re: Mutt and multiple imap accounts
On Sat, Feb 20, 2010 at 02:57:41PM +0100, Zeerak Waseem wrote: > Hey, > > I'm having some difficulties with mutt and multiple imaps; I've been > trying to set it up for my private mail and my uni mail, but I can't seem > to get it to work. I've been following two entries from the wiki (mainly) > this (http://wiki.mutt.org/?MuttGuide/UseIMAP) and this > (http://wiki.mutt.org/?UserStory/GmailMultiIMAP), if I purely follow the > first link, then mutt responds with there being no maildir. > If I purely follow the second link then it recognizes the maildir, but it > shows that there are no mailboxes. > A finesse to this is that my uni mail has a different ending from the imap > server (the other is a gmail account). Could someone help me point out the > flaws in my configuration? > > # Base hook to reset account variables to known state before activating > new ones > account-hook . 'unset preconnect imap_user imap_pass imap_authenticators; > set ssl_starttls=ask-yes' > > account-hook imaps://imap.gmail.com:993/ 'set imap_user=Gmail-user > imap_pass=Pass' > folder-hook imaps://imap.gmail.com:993/ 'set > folder=imaps://imap.gmail.com/INBOX record=+Sent from="My Name > "' > > account-hook imaps://uni-imap-server.com/ 'set imap_user=Uni-user > imap_pass=Pass2' > folder-hook imaps://uni-imap-server.com/ 'set > folder=imaps://uni-imap-server.com/INBOX record=+Sent from="My Name > "' > > If I add a folder and a spoolfile line (independent of the hooks) then > this setup works, but would I need to set a spoolfile and a folder for > both accounts? I think I tried it, but I'm not quite certain. The folder and spoolfile you set would be your defaults that get open when you start mutt. You only need to set these for one of your accounts. A few days back I posted in this mailing list my configuration to handle multiple Gmail accounts. Search the archives for a subject like "Simple Mutt with Eee PC 701". You may find it useful. > > Any help would be appreciated :-) > > > -- > Zeerak -- regards, Horacio Sanson
Re: Deletion flag lost when leaving the folder
Here is the patch. I wrote this back in 2006 and haven't looked at it
since then. I am sure if fixes the problem for the mbox format (that
is what I use) and some other mailboxes, but I am not 100% sure I
attempted to change the code for Maildir formats.
Since it is so old the patch only patches sucessfully against the
stable version. Maybe I will look at how to bring it up todate if
people think it will be a nice feature to have.
Yours,
Nick
On Thu, Feb 18, 2010 at 11:17:57PM -0500, Jean-Luc Wasmer wrote:
> I'm using the Maildir format...
>
> Do you know why it happens:
> - everytime when I set the deletion flag with Mutt
> - once in a while when the deletion flag was set before opening the folder
> with Mutt?
>
> Can you send me the patch? Thanks!
>
> Jean-Luc
>
> On Thu, Feb 18, 2010 at 05:55:00PM -0600, Nicholas Longo wrote:
> > Hi this is "expected" behavior for certain mailboxes. So a possible
> > work around is to switch the mailbox type you use. At some point I
> > submitted a patch for this behavior which created an option
> > "save_dflag" for which could be set to save deletion flags on mbox
> > style mailboxes.
> >
> > Maybe we could try again to get this patch (or something like it) into the
> > source.
> >
> > Yours,
> > Nick
> >
> > PS Sorry if your getting this twice Jean-Luc, I wanted to send one
> > copy to mutt-users.
> >
> >
> > On Thu, Feb 18, 2010 at 06:02:28PM -0500, Jean-Luc Wasmer wrote:
> >
> > > Hi,
> > >
> > > If I set one or more messages with the deletion flag, and answer "no" to
> > > the purge confirmation, Mutt undeletes the messages when leaving the
> > > folder.
> > >
> > > Is this an expected behavior?
> > >
> > > Once in a while, Mutt will undelete messages that already had the
> > > deletion flag set (before entering the folder). This also happens when
> > > leaving the folder and answering "no" to the purge confirmation. This is
> > > really annoying since I have the deletion flag set by procmail based on
> > > spam rules and Mutt clears them (I usually have over a hundred deleted
> > > email in some folders, I only purge after some time).
> > >
> > > Thanks for your help!
> > > Jean-Luc
Index: PATCHES
===
RCS file: /home/roessler/cvs/mutt/PATCHES,v
retrieving revision 3.6
diff -u -r3.6 PATCHES
--- PATCHES 9 Dec 2002 17:44:54 - 3.6
+++ PATCHES 14 Mar 2006 16:10:15 -
@@ -0,0 +1 @@
+patch-cvs.nl.save_dflag.1
\ No newline at end of file
Index: copy.c
===
RCS file: /home/roessler/cvs/mutt/copy.c,v
retrieving revision 3.27
diff -u -r3.27 copy.c
--- copy.c 21 Oct 2005 04:35:37 - 3.27
+++ copy.c 14 Mar 2006 16:10:15 -
@@ -444,7 +444,7 @@
return (-1);
}
- if (h->flagged || h->replied)
+ if (h->flagged || h->replied || h->deleted)
{
if (fputs ("X-Status: ", out) == EOF)
return (-1);
@@ -460,6 +460,12 @@
if (fputc ('F', out) == EOF)
return (-1);
}
+
+if (h->deleted && option (OPTSAVEDFLAG))
+ {
+ if (fputc ('D', out) == EOF)
+ return (-1);
+ }
if (fputc ('\n', out) == EOF)
return (-1);
Index: init.h
===
RCS file: /home/roessler/cvs/mutt/init.h,v
retrieving revision 3.95
diff -u -r3.95 init.h
--- init.h 9 Jan 2006 19:43:58 - 3.95
+++ init.h 14 Mar 2006 16:10:15 -
@@ -2921,6 +2921,14 @@
** messages to be sent. Exim users may wish to unset this.
*/
/*--*/
+ { "save_dflag", DT_BOOL, R_NONE, OPTSAVEDFLAG, 0},
+ /*
+ ** .pp
+ ** Controls whether mutt writes out a D in the X-Status when
+ ** synchronizing mbox mailboxes.
+ */
+ /*--*/
+
{ NULL }
};
Index: mbox.c
===
RCS file: /home/roessler/cvs/mutt/mbox.c,v
retrieving revision 3.11
diff -u -r3.11 mbox.c
--- mbox.c 21 Oct 2005 04:35:37 - 3.11
+++ mbox.c 14 Mar 2006 16:10:15 -
@@ -667,7 +667,7 @@
* 0 success
* -1 failure
*/
-int mbox_sync_mailbox (CONTEXT *ctx, int *index_hint)
+int mbox_sync_mailbox (CONTEXT *ctx, int *index_hint, int purge)
{
char tempfile[_POSIX_PATH_MAX];
char buf[32];
@@ -785,7 +785,7 @@
oldOffset[i-first].lines = ctx->hdrs[i]->lines;
oldOffset[i-first].length = ctx->hdrs[i]->content->length;
-if (! ctx->hdrs[i]->deleted)
+if (! (ctx->hdrs[i]->deleted && purge) )
{
j++;
if (!ctx->quiet && WriteInc && ((i % WriteInc) == 0 || j == 1))
Index: mutt.h
===
RCS file: /home/roessler/cvs/mutt/mutt.h,v
retrieving revision 3.63
diff -u -r3.63 mutt.h
--- mutt.h 9 Jan 2006 19:43:59 - 3.63
+++ mutt.h 14 Mar 2006 16:10:15
Re: Mutt and multiple imap accounts
On Mon, Feb 22, 2010 at 09:42:19AM +0900, Horacio Sanson wrote: > On Sat, Feb 20, 2010 at 02:57:41PM +0100, Zeerak Waseem wrote: > > Hey, > > > > I'm having some difficulties with mutt and multiple imaps; I've been > > trying to set it up for my private mail and my uni mail, but I can't seem > > to get it to work. I've been following two entries from the wiki (mainly) > > this (http://wiki.mutt.org/?MuttGuide/UseIMAP) and this > > (http://wiki.mutt.org/?UserStory/GmailMultiIMAP), if I purely follow the > > first link, then mutt responds with there being no maildir. > > If I purely follow the second link then it recognizes the maildir, but it > > shows that there are no mailboxes. > > A finesse to this is that my uni mail has a different ending from the imap > > server (the other is a gmail account). Could someone help me point out the > > flaws in my configuration? > > > > # Base hook to reset account variables to known state before activating > > new ones > > account-hook . 'unset preconnect imap_user imap_pass imap_authenticators; > > set ssl_starttls=ask-yes' > > > > account-hook imaps://imap.gmail.com:993/ 'set imap_user=Gmail-user > > imap_pass=Pass' > > folder-hook imaps://imap.gmail.com:993/ 'set > > folder=imaps://imap.gmail.com/INBOX record=+Sent from="My Name > > "' > > > > account-hook imaps://uni-imap-server.com/ 'set imap_user=Uni-user > > imap_pass=Pass2' > > folder-hook imaps://uni-imap-server.com/ 'set > > folder=imaps://uni-imap-server.com/INBOX record=+Sent from="My Name > > "' > > > > If I add a folder and a spoolfile line (independent of the hooks) then > > this setup works, but would I need to set a spoolfile and a folder for > > both accounts? I think I tried it, but I'm not quite certain. > > The folder and spoolfile you set would be your defaults that get open > when you start mutt. You only need to set these for one of your > accounts. > > A few days back I posted in this mailing list my configuration to handle > multiple Gmail > accounts. Search the archives for a subject like "Simple Mutt with Eee > PC 701". You may find it useful. > > > > > Any help would be appreciated :-) > > > > > > -- > > Zeerak > > -- > regards, > Horacio Sanson Ah yes, I found it :-) And I've gotten it working now :-) I also created a blog to document how to set it up, and anything else useful I needed. :-) -- Zeerak Waseem pgpwNeNXoRaUV.pgp Description: PGP signature
Set a default To value based on current folder name?
Hello, When composing a new mail, is it possible to specify a default To address based on the current folder name ? For example, when I am in the folder "list.mutt", I would like the "To:" field to be prefilled with the "mutt-users@mutt.org" value when composing a new mail. Thanks, -- Nicolas
Re: Set a default To value based on current folder name?
On Mon, Feb 22, 2010 at 12:51:55PM +0100, Nicolas KOWALSKI wrote: > Hello, > > When composing a new mail, is it possible to specify a default To > address based on the current folder name ? > > For example, when I am in the folder "list.mutt", I would like the "To:" > field to be prefilled with the "mutt-users@mutt.org" value when > composing a new mail. > > Thanks, > -- > Nicolas I don't know if that can be done, but couldn't a work around be that you specified the list in your alias file? -- Zeerak Waseem pgpvrq6iBYSxb.pgp Description: PGP signature
Re: Set a default To value based on current folder name?
On Mon, Feb 22, 2010 at 01:10:57PM +0100, Zeerak Mustafa Waseem wrote: > On Mon, Feb 22, 2010 at 12:51:55PM +0100, Nicolas KOWALSKI wrote: > > > > When composing a new mail, is it possible to specify a default To > > address based on the current folder name ? > > > > For example, when I am in the folder "list.mutt", I would like the "To:" > > field to be prefilled with the "mutt-users@mutt.org" value when > > composing a new mail. > > > I don't know if that can be done, but couldn't a work around be that > you specified the list in your alias file? I have already. I just would like to automate the process for all my mailing-lists folders, if possible. -- Nicolas
Re: Set a default To value based on current folder name?
On 22.02.10,14:07, Nicolas KOWALSKI wrote: > On Mon, Feb 22, 2010 at 01:10:57PM +0100, Zeerak Mustafa Waseem wrote: > > On Mon, Feb 22, 2010 at 12:51:55PM +0100, Nicolas KOWALSKI wrote: > > > > > > When composing a new mail, is it possible to specify a default To > > > address based on the current folder name ? > > > > > > For example, when I am in the folder "list.mutt", I would like the "To:" > > > field to be prefilled with the "mutt-users@mutt.org" value when > > > composing a new mail. > > > > > I don't know if that can be done, but couldn't a work around be that > > you specified the list in your alias file? > > I have already. > > I just would like to automate the process for all my mailing-lists > folders, if possible. > Have you tried with folder-hook and my_hdr? - Jostein
Re: Set a default To value based on current folder name?
On Mon, Feb 22, 2010 at 03:45:32PM +0100, Jostein Berntsen wrote: > On 22.02.10,14:07, Nicolas KOWALSKI wrote: > > On Mon, Feb 22, 2010 at 01:10:57PM +0100, Zeerak Mustafa Waseem wrote: > > > On Mon, Feb 22, 2010 at 12:51:55PM +0100, Nicolas KOWALSKI wrote: > > > > > > > > When composing a new mail, is it possible to specify a default To > > > > address based on the current folder name ? > > > > > > > > For example, when I am in the folder "list.mutt", I would like the > > > > "To:" > > > > field to be prefilled with the "mutt-users@mutt.org" value when > > > > composing a new mail. > > > > > > > I don't know if that can be done, but couldn't a work around be that > > > you specified the list in your alias file? > > > > I have already. > > > > I just would like to automate the process for all my mailing-lists > > folders, if possible. > > > > Have you tried with folder-hook and my_hdr? Thanks for the tip! With the following it works perfectly: folder-hook . 'unmy_hdr to' folder-hook =list.debian'my_hdr To: debian-u...@lists.debian.org' folder-hook =list.debian-backports 'my_hdr To: backports-us...@lists.backports.org' folder-hook =list.debian-french 'my_hdr To: debian-user-fre...@lists.debian.org' folder-hook =list.mutt 'my_hdr To: mutt-users@mutt.org' ...[and so on]... Thanks a lot, -- Nicolas
Re: Set a default To value based on current folder name?
=- Jostein Berntsen wrote on Mon 22.Feb'10 at 15:45:32 +0100 -= > > > > When composing a new mail, is it possible to specify a > > > > default To address based on the current folder name ? > > > > I just would like to automate the process for all my > > mailing-lists folders, if possible. > > Have you tried with folder-hook and my_hdr? ... or folder-hook with macro? -- © Rado S. -- You must provide YOUR effort for your goal! EVERY effort counts: at least to show your attitude. You're responsible for ALL you do: you get what you give.
Re: How to build mutt
On Mon, Feb 22, 2010 at 10:19:56AM +0100, Gary wrote: > I know it should be as simple as './configure [some options]' followed > by 'make install', but I am at a loss knowing which options I should > apply in order to have the same capabilities as another build's. For > example in order to have > > +BUFFY_SIZE -DEBUG -DL_STANDALONE -DOMAIN +ENABLE_NLS -EXACT_ADDRESS > +HAVE_BKGDSET +HAVE_COLOR +HAVE_CURS_SET -HAVE_GETADDRINFO +HAVE_GETSID > +HAVE_ICONV +HAVE_LANGINFO_CODESET +HAVE_LANGINFO_YESEXPR +HAVE_META > +HAVE_PGP +HAVE_REGCOMP +HAVE_RESIZETERM +HAVE_START_COLOR > +HAVE_TYPEAHEAD -HAVE_WC_FUNCS -HOMESPOOL -ICONV_NONTRANS -ISPELL > +LOCALES_HACK -SUN_ATTACHMENT -USE_DOTLOCK +USE_FCNTL -USE_FLOCK > +USE_GNU_REGEX -USE_GSS +USE_IMAP +USE_POP -USE_SASL -USE_SETGID > +USE_SSL > > are all the capabilities included using "--enable-WHATEVER"? if so, why > do some final results start with USE, some with HAVE, and others nothing > special at all? If not, how do I enable/disable them? The USE_* options are typically controlled via --enable-* or --with-* options to configure. The HAVE_* are system aspects that the configure script automatically detects are are not typically user configurable. The items without a prefix are primarily items which the user *may* need to override (most of these are old, but would probably be better labeled with a USE_ prefix). > Additionally, is it possible to not build/install the documentation > somehow? Trying to do that here gives me an error and then make stops > *sigh* I am not sure, but you may be able to remove the "doc" item from the SUBDIRS variable in the Makefile. Typically it's better to just install the docbook packages so you can build the docs. See doc/devel-notes.txt for the complete list of packages required. > make[2]: Entering directory `/usr/src/mutt/doc' > ##test -f manual.html || make manual.html || cp ./manual*.html ./ > cp ./manual*.html ./ > cp: cannot stat `./manual*.html': No such file or directory > make[2]: *** [try-html] Error 1 > make[2]: Leaving directory `/usr/src/mutt/doc' > make[1]: *** [install-recursive] Error 1 > make[1]: Leaving directory `/usr/src/mutt' > make: *** [install] Error 2 > > Why would anyone want to copy ./ to the same place anyway? > Any why on earth would they expect that to succeed? The build system does not assume that you are building in the same directory where the sources reside. For example, if you are building mutt for multiple architectures or even different options for testing, you might create several build directories. The make target for the documentation copies from the source directory to the build directory. In the example you noted above, they are the same directory so it looks odd, but it is not in error. me
Re: How to build mutt
On Mon, Feb 22, 2010 at 08:10:17AM -0800, Michael Elkins wrote: > On Mon, Feb 22, 2010 at 10:19:56AM +0100, Gary wrote: > > are all the capabilities included using "--enable-WHATEVER"? if so, why > > do some final results start with USE, some with HAVE, and others nothing > > special at all? If not, how do I enable/disable them? > > The USE_* options are typically controlled via --enable-* or --with-* Err. In the sense I can use whichever form I like, or in the sense that one or other will work, depending on which option I am trying to include? > options to configure. The HAVE_* are system aspects that the configure > script automatically detects are are not typically user configurable. > The items without a prefix are primarily items which the user *may* need > to override (most of these are old, but would probably be better labeled > with a USE_ prefix). Okay, thanks for that info. Sorry for asking, but I couldn't find this info anywhere. Maybe my google-fu is a bit off at the moment. So --enable-LOCALES_HACK for example, would result in +LOCALES_HACK in the binary, I guess. > > Additionally, is it possible to not build/install the documentation > > somehow? Trying to do that here gives me an error and then make stops > > *sigh* > > I am not sure, but you may be able to remove the "doc" item from the > SUBDIRS variable in the Makefile. Will try. Thanks. > Typically it's better to just install the docbook packages so you can build the docs. Actually I have (even though 'grep -iIr docbook *' in the src directory returns no results). It doesn't help. > > make[2]: Entering directory `/usr/src/mutt/doc' > > ##test -f manual.html || make manual.html || cp ./manual*.html ./ > > cp ./manual*.html ./ > > cp: cannot stat `./manual*.html': No such file or directory > > make[2]: *** [try-html] Error 1 > > make[2]: Leaving directory `/usr/src/mutt/doc' > > make[1]: *** [install-recursive] Error 1 > > make[1]: Leaving directory `/usr/src/mutt' > > make: *** [install] Error 2 > > > > Why would anyone want to copy ./ to the same place anyway? > > Any why on earth would they expect that to succeed? > > The build system does not assume that you are building in the same > directory where the sources reside. Okay. > In the example you noted above, they are the same directory so it looks > odd, but it is not in error. Well, make appears to disgree with you on that. It just stops after the errors noted above and I don't get a binary or whatever documentation it's trying to build. Admittedly, I have an old version, so it might not be a current problem (it's also the Cygwin version, so it might not even really be *your* problem). Okay, so I tried this removing the doc entry from SUBDIR in the Makefile and that seems to work fine. Thanks for your help. I'll see to getting the configure options sorted out correctly now.
Re: How to build mutt
On Mon, Feb 22, 2010 at 06:21:52PM +0100, Gary wrote: > On Mon, Feb 22, 2010 at 08:10:17AM -0800, Michael Elkins wrote: > > The USE_* options are typically controlled via --enable-* or --with-* > > Err. In the sense I can use whichever form I like, or in the sense that > one or other will work, depending on which option I am trying to > include? In the latter sense. --enable-* typically controls a feature that Mutt can provide. --with-* is used to control other software which Mutt might make use of (e.g. openssl, qdbm). This is typicaly of software which uses autoconf. > > Typically it's better to just install the docbook packages so you can > build the docs. > > Actually I have (even though 'grep -iIr docbook *' in the src directory > returns no results). It doesn't help. I'm unsure why you get that result since there are many references to docbook in the doc/ subdirectory. > > In the example you noted above, they are the same directory so it looks > > odd, but it is not in error. > > Well, make appears to disgree with you on that. It just stops after the > errors noted above and I don't get a binary or whatever documentation > it's trying to build. Admittedly, I have an old version, so it might not > be a current problem (it's also the Cygwin version, so it might not even > really be *your* problem). The problem is not the cp, but the fact that the documentation failed to build. The 'stat' error is saying the source file does not exist. me
Bounce message from a different from address.
I send a long email to a mailing list but after sending it I realized I send the email using the wrong from: address. Of course the message got bounced back because that address is not registered in the mailing list. Now this should be easy to do but I have not found a simple way to resend the message with a different from: address. The message is stored in my Sent folder but using the bounce function on it asks me to input a new destination (to:) address but what I want is to change the from: address and resend the message intact as it is. How to achieve this feat? -- regards, Horacio Sanson
Re: Bounce message from a different from address.
On Tue, Feb 23, 2010 at 09:34:51AM +0900, Horacio Sanson wrote: > I send a long email to a mailing list but after sending it I realized I > send the email using the wrong from: address. Of course the message got > bounced > back because that address is not registered in the mailing list. > > Now this should be easy to do but I have not found a simple way to > resend the message with a different from: address. The message is stored > in my Sent folder but using the bounce function on it asks me to input a > new destination (to:) address but what I want is to change the from: > address and resend the message intact as it is. > > How to achieve this feat? On my Mutt, e is bound to "resend-message". You can use that to edit and "resend" the message. HTH. Kumar -- Your idol is shattered in the dust to prove that God's dust is greater than your idol. - Rabindranath Tagore (Stray Birds, 1916) signature.asc Description: Digital signature
Re: Bounce message from a different from address.
On Mon, Feb 22, 2010 at 06:45:48PM -0600, Kumar Appaiah wrote: > On Tue, Feb 23, 2010 at 09:34:51AM +0900, Horacio Sanson wrote: > > I send a long email to a mailing list but after sending it I realized I > > send the email using the wrong from: address. Of course the message got > > bounced > > back because that address is not registered in the mailing list. > > > > Now this should be easy to do but I have not found a simple way to > > resend the message with a different from: address. The message is stored > > in my Sent folder but using the bounce function on it asks me to input a > > new destination (to:) address but what I want is to change the from: > > address and resend the message intact as it is. > > > > How to achieve this feat? > > On my Mutt, e is bound to "resend-message". You can use that to > edit and "resend" the message. > Thanks, I knew was something easy... > HTH. > > Kumar > -- > Your idol is shattered in the dust to prove that God's dust is greater than > your idol. > - Rabindranath Tagore (Stray Birds, 1916) -- regards, Horacio Sanson
