Help with basic configuration

[Maurí­cio CA]

(This is really begginer question. If this is not
the right place to ask that, please excuse and warn me
so I won't bother again.)

This is my current attempt at file '~/.frm':

mailbox {
   mailbox-pattern "imaps://mauricio.antunes%40gmail.com@...";
}

(%40 stands for @, as I saw in a message in this list.)

With this config (and apparently no system config, as
there's no /etc/mailutils.rc) I get this message:

frm: Could not create default mailbox: No registered handler

Parsing of ~/.frm is okay. It doesn't ask me for a password,
so I believe I'm doing something really wrong. But I can't
find what.

Thanks,
Maurício



_______________________________________________
Bug-mailutils mailing list
Bug-mailutils@...
http://lists.gnu.org/mailman/listinfo/bug-mailutils

[Wojciech Polak-2]

On Tue, 2009-07-28 at 20:05 -0300, Maurí­cio CA wrote:

> mailbox {
>    mailbox-pattern "imaps://mauricio.antunes%40gmail.com@...";
> }
>
> (%40 stands for @, as I saw in a message in this list.)
>
> With this config (and apparently no system config, as
> there's no /etc/mailutils.rc) I get this message:
>
> frm: Could not create default mailbox: No registered handler

Secure IMAP (imaps) requires TLS support in Mailutils.
Can you see "WITH_GNUTLS" string in `frm --show-config-options' output?

Regards,
Wojciech





_______________________________________________
Bug-mailutils mailing list
Bug-mailutils@...
http://lists.gnu.org/mailman/listinfo/bug-mailutils

[Maurí­cio CA]

>> With this config (and apparently no system config, as
>> there's no /etc/mailutils.rc) I get this message:
>>
>> frm: Could not create default mailbox: No registered handler

> Secure IMAP (imaps) requires TLS support in Mailutils.
> Can you see "WITH_GNUTLS" string in `frm --show-config-options' output?

Thanks. I recompiled with ./configure --with-gnutls.


I now get "Segmentation fault" a few seconds after running 'frm' (or
after typing my password if it's not in config file). I tried
clonning the git repository, and got this after './bootstrap'.

----------
./bootstrap: aclocal --force  -I m4 -I am ...
./bootstrap: autoconf --force ...
configure.ac:29: error: possibly undefined macro: AM_DEFAULT_VERBOSITY
       If this token and others are legitimate, please use m4_pattern_allow.
       See the Autoconf documentation.
configure.ac:813: error: possibly undefined macro: AM_GNU_RADIUS
----------

If you wan't me to give a more complete error report, just
tell me what to do.

Best,
Maurício



_______________________________________________
Bug-mailutils mailing list
Bug-mailutils@...
http://lists.gnu.org/mailman/listinfo/bug-mailutils

[Wojciech Polak-2]

On Wed, 2009-07-29 at 15:24 -0300, Maurí­cio CA wrote:

> Thanks. I recompiled with ./configure --with-gnutls.
>
> I now get "Segmentation fault" a few seconds after running 'frm' (or
> after typing my password if it's not in config file).

Could you possibly try to debug with gdb?
After you install frm, you can run `gdb frm', then type
"run SOME-MAILBOX-URL", and see what happens next. You should
see some stacktrace, which should be quite helpful for us.

> ----------
> ./bootstrap: aclocal --force  -I m4 -I am ...
> ./bootstrap: autoconf --force ...
> configure.ac:29: error: possibly undefined macro: AM_DEFAULT_VERBOSITY
>        If this token and others are legitimate, please use m4_pattern_allow.
>        See the Autoconf documentation.
> configure.ac:813: error: possibly undefined macro: AM_GNU_RADIUS
> ----------

When bootstrapping, you need to copy radius.m4 to am/ from GNU Radius
project. See
http://lists.gnu.org/archive/html/bug-mailutils/2009-02/msg00005.html

Regards,
Wojciech





_______________________________________________
Bug-mailutils mailing list
Bug-mailutils@...
http://lists.gnu.org/mailman/listinfo/bug-mailutils

[Simon Josefsson-2]

Wojciech Polak <polak@...> writes:

>> ----------
>> ./bootstrap: aclocal --force  -I m4 -I am ...
>> ./bootstrap: autoconf --force ...
>> configure.ac:29: error: possibly undefined macro: AM_DEFAULT_VERBOSITY
>>        If this token and others are legitimate, please use m4_pattern_allow.
>>        See the Autoconf documentation.
>> configure.ac:813: error: possibly undefined macro: AM_GNU_RADIUS
>> ----------
>
> When bootstrapping, you need to copy radius.m4 to am/ from GNU Radius
> project. See
> http://lists.gnu.org/archive/html/bug-mailutils/2009-02/msg00005.html

Adding radius.m4 to Mailutils' am/ directory would prevent people from
running into this problem over and over again.

/Simon


_______________________________________________
Bug-mailutils mailing list
Bug-mailutils@...
http://lists.gnu.org/mailman/listinfo/bug-mailutils

[Sergey Poznyakoff-2]

Simon Josefsson <simon@...> ha escrit:

> Adding radius.m4 to Mailutils' am/ directory would prevent people from
> running into this problem over and over again.

Radius simply should have been listed in bootstrapping prerequisites,
which I overlooked.

Regards,
Sergey


_______________________________________________
Bug-mailutils mailing list
Bug-mailutils@...
http://lists.gnu.org/mailman/listinfo/bug-mailutils

[Maurí­cio CA]

>> Adding radius.m4 to Mailutils' am/ directory would prevent people from
>> running into this problem over and over again.
>
> Radius simply should have been listed in bootstrapping prerequisites,
> which I overlooked.

I added radius.m4 to am/, but got this, which
looks like the old message but without the
reference to RADIUS:

./bootstrap: aclocal --force  -I m4 -I am ...
./bootstrap: autoconf --force ...
configure.ac:29: error: possibly undefined macro: AM_DEFAULT_VERBOSITY
       If this token and others are legitimate, please use m4_pattern_allow.
       See the Autoconf documentation.


Maurício



_______________________________________________
Bug-mailutils mailing list
Bug-mailutils@...
http://lists.gnu.org/mailman/listinfo/bug-mailutils

[Maurí­cio CA]

>> Thanks. I recompiled with ./configure --with-gnutls.
>>
>> I now get "Segmentation fault" a few seconds after running 'frm' (or
>> after typing my password if it's not in config file).
>
> Could you possibly try to debug with gdb?
> After you install frm, you can run `gdb frm', then type
> "run SOME-MAILBOX-URL", and see what happens next. You should
> see some stacktrace, which should be quite helpful for us.

OK. If I run frm with local mail box (i.e., without a
configuration file), I have no problems. If I run frm with my
google imaps configuration, but type an invalid password, I also
have no segmentation fault (i.e., I just get a message saying
wrong password). So, I do need to type my password and have it
authenticated to get a problem, and so I just need to ask if the
output from gdb can reveal my password somehow, and if it does,
what would be the measures I should take to avoid that. (I imagine
maybe just changing my password to something else while testing
frm would be enough, unless imaps or tls make use of something
else.)

Maurício




_______________________________________________
Bug-mailutils mailing list
Bug-mailutils@...
http://lists.gnu.org/mailman/listinfo/bug-mailutils

[Sergey Poznyakoff-2]

Maurí­cio CA <mauricio.antunes@...> ha escrit:

> configure.ac:29: error: possibly undefined macro: AM_DEFAULT_VERBOSITY
>       If this token and others are legitimate, please use m4_pattern_allow.
>       See the Autoconf documentation.
>

Your Automake version is too old. Mailutils requires at least automake
1.11. See README-hacking, for more prerequisites.

Regards,
Sergey



_______________________________________________
Bug-mailutils mailing list
Bug-mailutils@...
http://lists.gnu.org/mailman/listinfo/bug-mailutils

[Maurí­cio CA]

>> configure.ac:29: error: possibly undefined macro: AM_DEFAULT_VERBOSITY
>>       If this token and others are legitimate, please use m4_pattern_allow.
>>       See the Autoconf documentation.
>>
>
> Your Automake version is too old. Mailutils requires at least automake
> 1.11. See README-hacking, for more prerequisites.

Now I get an error while building (see below the end of
the messages output from 'make').

I think it's better if I just send you the information
from gdb Wojciech asked before using the release version,
since there will probably be less variables involved (like
my build environment). What do you think of the security
issue I sugested in my other message?

Thanks,
Maurício

-------------

Making all in testsuite
make[2]: entrant dans le répertoire « /home/mauricio/mailutils/testsuite »
make[2]: Rien à faire pour « all ».
make[2]: quittant le répertoire « /home/mauricio/mailutils/testsuite »
Making all in mailbox
make[2]: entrant dans le répertoire « /home/mauricio/mailutils/mailbox »
/bin/bash ../mu-aux/gylwrap "yacc -vt" parsedate.y \
                   y.tab.c parsedate.c y.output parsedate.y.output \
                   -- -yy pd_yy

  fatal error:illegal option: t, <nil>:1
make[2]: *** [parsedate.c] Erreur 1
make[2]: quittant le répertoire « /home/mauricio/mailutils/mailbox »
make[1]: *** [all-recursive] Erreur 1
make[1]: quittant le répertoire « /home/mauricio/mailutils »
make: *** [all] Erreur 2



_______________________________________________
Bug-mailutils mailing list
Bug-mailutils@...
http://lists.gnu.org/mailman/listinfo/bug-mailutils

[Sergey Poznyakoff-2]

Maurício CA <mauricio.antunes@...> ha escrit:

> Now I get an error while building (see below the end of
> the messages output from 'make').
[...]
> /bin/bash ../mu-aux/gylwrap "yacc -vt" parsedate.y \
>                   y.tab.c parsedate.c y.output parsedate.y.output \
>                   -- -yy pd_yy

Maurício, in order to bootstrap Mailutils from Git you need to
have a set of certain tools. In particular, GNU bison is required.
The .y grammars Mailutils uses will not compile with usual
Berkeley yacc.

Please, refer to the file README-hacking for the complete list of
utilities needed and make sure you have them installed before trying
to bootstrap the sources.

> I think it's better if I just send you the information
> from gdb Wojciech asked before using the release version,
> since there will probably be less variables involved (like
> my build environment).

As you wish.

> What do you think of the security issue I sugested in my other message?

The gdb traces may reveal lots of potentially security-sensitive
information, including passwords. Make sure these are not visible
before you send traces to the list.

Also, before trying to use gdb, make sure Mailutils is compiled with
debugging information. This is achieved by using --enable-debug
option to configure.

Regards,
Sergey



_______________________________________________
Bug-mailutils mailing list
Bug-mailutils@...
http://lists.gnu.org/mailman/listinfo/bug-mailutils

[Maurí­cio CA]

> Please, refer to the file README-hacking for the complete list of
> utilities needed and make sure you have them installed before trying
> to bootstrap the sources.
>

Thanks, Sergey. I was able to build from git
and the segmentation fault doesn't happen in
that version.

(If a core dump of the release version is still
usefull, just send me a message. I'll rebuild
the release version and try to reproduce the
problem in a clean user and e-mail account to
avoid any security risks.)

Best,
Maurício



_______________________________________________
Bug-mailutils mailing list
Bug-mailutils@...
http://lists.gnu.org/mailman/listinfo/bug-mailutils