Hello all,
I would like to ask for some comments on issues I have
compiling/installing mutt in my $HOME.
I do this:
{{{
% hg sum
parent: 6346:3306cb186f49 tip
Merge stable into default
branch: default
commit: 1 modified, 3 unknown
update: (current)
% ./configure --prefix=${HOME}/
On h, jan 06, 2014 at 12:05:06 +0100, Bastian wrote:
> Hello all,
[...]
> These are the problems I see at the moment:
[...]
> C.
> my mutt version does not display UTF8 properly. Umlauts are not
> printed in the pager.
> Do I miss a configuration or a library?
[...]
This is a long shot, but
Hello Mick,
On Sun, Jan 05, 2014 at 08:34:52PM +, Mick wrote:
I found the description of those fields in smime.c:
/* 0=email 1=name 2=nick 3=intermediate 4=trust */ (line 397)
Just wondering why "smime_keys add_p12" didn't insert the
intermediate certificate ("?").
Could it be that the in
On Monday 06 Jan 2014 12:22:49 Heiko Heil wrote:
> Hello Mick,
>
> On Sun, Jan 05, 2014 at 08:34:52PM +, Mick wrote:
> >> I found the description of those fields in smime.c:
> >> /* 0=email 1=name 2=nick 3=intermediate 4=trust */ (line 397)
> >> Just wondering why "smime_keys add_p12" didn't i
On 06Jan14 12:37 +0100, LEVAI Daniel wrote:
> > my mutt version does not display UTF8 properly. Umlauts are not
> > printed in the pager.
> > Do I miss a configuration or a library?
>
> This is a long shot, but did you link with the wide-char ncurses lib?
> ie.: $ ldd ${HOME}/local/bin/mutt
On 2014-01-04, Ulrich Lauther wrote:
> Recent posts made me aware of the fact, that mutt supports SMPT. So
> far I have been using postfix for mail transport. Which way is
> better, and why?
[I'm assuming you're using postfix only for outbound mail. If you're
using Postfix to handle incoming ma
