On 18-11-14 12:38, Anatoly wrote:
> 94%: Checks: 17, Failures: 1, Errors: 0
> check_dbmail_imapd.c:448:F:ImapSession:test_imap_get_envelope_koi:0:
> encode/decode/encode loop failed
> [("Thu, 01 Jan 1970 00:00:00 +0000" "test"
> (("=?koi8-r?b?4c7Uz84g7sXIz9LP28nI?=" NIL "bad" "foo.ru"))
> (("=?koi8-r?b?4c7Uz84g7sXIz9LP28nI?=" NIL "bad" "foo.ru"))
> (("=?koi8-r?b?4c7Uz84g7sXIz9LP28nI?=" NIL "bad" "foo.ru")) ((NIL NIL
> "nobody" "foo.ru")) NIL NIL NIL NIL)] !=
> [("Thu, 01 Jan 1970 00:00:00 +0000" "test"
> (("=?iso-8859-5?b?sN3i3t0gvdXl3uDe6Njl?=" NIL "bad" "foo.ru"))
> (("=?iso-8859-5?b?sN3i3t0gvdXl3uDe6Njl?=" NIL "bad" "foo.ru"))
> (("=?iso-8859-5?b?sN3i3t0gvdXl3uDe6Njl?=" NIL "bad" "foo.ru")) ((NIL NIL
> "nobody" "foo.ru")) NIL NIL NIL NIL)]
I think you can safely ignore that one. Looks like that test should be
updated to accept both iso-8859-5 of koi8-r encoded results. Not sure
why my systems always return 8859-5 though...
> (2)Second:
> Sometimes dbmail-imapd crashed with message:
> (some clients try reload informaition)
> kernel: pool[18542]: segfault at 38 ip 000000000041552d sp
> 00007f06f9ffad80 error 6 in dbmail-imapd[400000+7b000]
I've seen more reports like this (horde?). I'd love to see the IMAP
command that triggers this, or a GDB backtrace.
> (3)Third:
> I try add user with '-p md5-hash' option
>
> dbmail-users -a [email protected] -s [email protected] -w 12345 -p
> md5-hash
>
> Then connect to imap, dbmail-imapd crashed with message
>
> kernel: pool[1009]: segfault at 8 ip 00007f17537287e1 sp
> 00007f1747ffe168 error 4 in libc-2.17.so[7f17536a2000+1b6000]
Works for me. But it should be real easy to provide a gdb backtrace for
this one.
--
________________________________________________________________
Paul J Stevens pjstevns @ gmail, twitter, github, linkedin
www.nfg.nl/[email protected]/+31.85.877.99.97
_______________________________________________
DBmail mailing list
[email protected]
http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail
