Dear David, Thank you. I did attempt to rebuild from the source, although I am having trouble with the links at the mutt.org website. Neither of the mutt-1.x.tar.gz links will load, and at sourceforge I can only find the dev or 1.4.2.2i versions. I tried to build both the dev version and a 1.4.2.3 tar that I found elsewhere (legitimate-looking), but both failed at the make install phase. I do not have the errors in front of me now, as I am at my work computer (I am trying to build from my home laptop).
Basic question, is there any reason for a novice computer-er like me to use mutt beyond the novelty of emailing in Terminal, or am I in over my head with mail servers and the like? Thank you all for your hard work keeping this sort of project going. I follow other open source communities, as well, and the work that all of you do is both amazing and exciting! Best, Conor Cook On Mon, Jan 26, 2015 at 10:34 AM, David Champion <[email protected]> wrote: > * On 26 Jan 2015, Conor Cook wrote: >> >> In what I have discovered online, the problem seems to be related to >> "-USE_IMAP." Unfortunately, nothing I can find online tells me how to >> change that and the related variables to "+USE_IMAP." I am in my >> command line infancy, so I have gotten in over my head. Is there >> anything you can suggest to remedy the issue? > > That's exactly right. These are compile-time options, unfortunately, so > what it means is that your mutt was built without IMAP (or POP) support. > If you need this, you'll need a different packager build, or else to > compile yourself from source. Add --enable-imap (--enable-pop) to the > ./configure command to activate this feature set in your build. > > -- > David Champion • [email protected]
