On 3.8.2010, at 22.09, Pašek Ladislav wrote:
> Thanks for hint. This is output from gdb bt full but I have no clue what to
> find in it:
>
> #0 0x003129a32ce2 in unsetenv () from /lib64/libc.so.6
Oh. This again. Just make sure the first setting in your dovecot.conf isn't
"something=no". M
On 30.7.2010, at 18.44, Ladislav Pašek wrote:
> Thanks for hint. So I checked with strace and its output is here:
Strace output isn't very helpful for crashes. gdb backtrace would show exactly
where it crashes. If you can crash it by running
deliver ..params.. < mail-file
then easiest way to g
Thanks for hint. So I checked with strace and its output is here:
http://www.volny.cz/vykupitel/Pictures/mail/dovecot.err
I think that the most interesting part is on the end. It segfault on the
parameter mail_full_filesystem_access = no.
.
.
.
uname({sys="Linux", node="mail.valbek.cz", ...})
On 07/30/2010 05:58 PM Pašek Ladislav wrote:
> According to my previous email, is it possible to somehow debug delivery
> process to find out why is this happening?
>
> Command died with signal 11: "/usr/libexec/dovecot/deliver"
>
> Thanks in Advance
>
> Ladislav
See http://dovecot.org/bugrep
Hello,
I have configured Dovecot 1.2.12 with Postfix 2.6.5 and everything is working fine. But tomorrow I wanted to run IMAP
ALCs and from log I found that this plugin is conflicting with parameter mail_full_filesystem_access = yes in my config.
But when I set mail_full_filesystem_access = no
