Yes, this patch fixed that problem.
Thank you!
>> # 1.2.14: /usr/local/etc/dovecot.conf
> ..
>> #0 0x00483340 in message_parser_parse_next_block ()
>> No symbol table info available.
>> #1 0x00444fe4 in index_mail_cache_parse_continue ()
>> No symbol table info available.
>> #2
On Wed, 2010-10-13 at 17:05 +0300, Michael M Galapchuk wrote:
> # 1.2.14: /usr/local/etc/dovecot.conf
..
> #0 0x00483340 in message_parser_parse_next_block ()
> No symbol table info available.
> #1 0x00444fe4 in index_mail_cache_parse_continue ()
> No symbol table info available.
Hello list,
When trying to deliver a big message (which over-quota user limit), I always
get segmentation faults.
Others common delivers work fine. This only happens with messages,
which over-quota user limit.
Here is more details:
/var/log/maillog:
...
** u...@fakedomain.ua R=virtual_user
Il giorno 07/ott/2010, alle ore 09.06, Andre ha scritto:
> Hi to all.
> Since version 2.0.3 (now I am running 2.0.5) I have experienced segfaults on
> mail delivery, either with dovecot-lda and lmtp.
>
> At least I succeded in having a core dump, here is the backtrace:
>
> #0 0x7f1cca3501
Andre schreef:
Hi to all.
Since version 2.0.3 (now I am running 2.0.5) I have experienced segfaults on
mail delivery, either with dovecot-lda and lmtp.
At least I succeded in having a core dump, here is the backtrace:
#0 0x7f1cca350160 in maildir_sync_set_new_msgs_count () from
/usr/lib
Hi to all.
Since version 2.0.3 (now I am running 2.0.5) I have experienced segfaults on
mail delivery, either with dovecot-lda and lmtp.
At least I succeded in having a core dump, here is the backtrace:
#0 0x7f1cca350160 in maildir_sync_set_new_msgs_count () from
/usr/lib/dovecot/libdoveco
Hello list,
When trying to deliver a big message (which over-quota user limit), I always
get segmentation faults.
Others common delivers work fine. This only happens with messages,
which over-quota user limit.
Here is more details:
/var/log/maillog:
...
** u...@fakedomain.ua R=virtual_user
Hello Stephan,
This fix works. Thank you for that.
Cheers,
Olivier
On 29/09/2010 18:11, Stephan Bosch wrote:
>
>> Hello again,
>>
>> I've added the -d and -f flags to the command line and this time I got a
>> trace.
>>
>> (gdb) r
>> Starting program: /usr/libexec/dovecot/dovecot-lda -p
>> exa
Hello again,
I've added the -d and -f flags to the command line and this time I got a
trace.
(gdb) r
Starting program: /usr/libexec/dovecot/dovecot-lda -p
example-message.eml -f u...@domain.com -d u...@domain.com
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbo
On 29/09/2010 16:40, Stephan Bosch wrote:
> Op 29-9-2010 17:35, Stephan Bosch schreef:
>> Op 29-9-2010 17:33, interfaSys sàrl schreef:
>>> (gdb) bt full
>>> #0 0x000800e70140 in seff_flags_merge () from
>>
>> According to this, you have a require "imap4flags"; somewhere on top
>> of your S
Op 29-9-2010 17:35, Stephan Bosch schreef:
Op 29-9-2010 17:33, interfaSys sàrl schreef:
(gdb) bt full
#0 0x000800e70140 in seff_flags_merge () from
According to this, you have a require "imap4flags"; somewhere on top
of your Sieve script right?
Also, it's apparently running in multis
Op 29-9-2010 17:33, interfaSys sàrl schreef:
Hello again,
I've added the -d and -f flags to the command line and this time I got a
trace.
(gdb) r
Starting program: /usr/libexec/dovecot/dovecot-lda -p
example-message.eml -f u...@domain.com -d u...@domain.com
(no debugging symbols found)...(no d
Hello again,
I've added the -d and -f flags to the command line and this time I got a
trace.
(gdb) r
Starting program: /usr/libexec/dovecot/dovecot-lda -p
example-message.eml -f u...@domain.com -d u...@domain.com
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols
Hello,
I tried to do a trace but it didn't seem to work.
(gdb) r
Starting program: /usr/libexec/dovecot/dovecot-lda -p example-message.eml
(no debugging symbols found)...(no debugging symbols found)...(no
debugging symbols found)...(no debugging symbols found)...(no debugging
symbols founn
Progr
OK, I'll give the trace a try. Thanks for the instructions.
In the meantime, here is more info.
The sieve script does a redirect and a local save. It works fine if only
the redirect is in place.
if true {
redirect "some.em...@domain.com";
}
if true {
keep;
stop;
}
I'm using mdbox as
Op 29-9-2010 14:42, interfaSys sàrl schreef:
Hello,
One account couldn't get emails all the sudden.
dovecot-lda was crashing with "signal 11 (segmentation fault)".
There was absolutely nothing in the dovecot logs, even with mail_debug=yes.
I found out that it was because of the following lin
Hello,
One account couldn't get emails all the sudden.
dovecot-lda was crashing with "signal 11 (segmentation fault)".
There was absolutely nothing in the dovecot logs, even with mail_debug=yes.
I found out that it was because of the following lines in a sieve script
that were generated by a scr
17 matches
Mail list logo