similar to: Crash in dovecot/auth with backtrace

Displaying 20 results from an estimated 60 matches similar to: "Crash in dovecot/auth with backtrace"

2015 Apr 23
0
Crash in dovecot/auth with backtrace
On 23 Apr 2015, at 17:34, Ralf Hildebrandt <Ralf.Hildebrandt at charite.de> wrote: > > I'm seeing this odd crash with "USER\t531\t*@liquid-scan.de\tservice=quota-status" > Which looks like something is being tested against our quota-status -- > but I fail to see why an NON LOCAL address is being tested.... Oh, that's not very good. Fixed:
2007 Aug 01
3
dovecot: child 1690 (auth-worker) killed with signal 11
Hi there, I've been seeing this for quite a while now, but only today finally got off my lazy you-know-what and did a backtrace. Here's the requested info as per http://dovecot.org/bugreport.html: * Dovecot version [root at airframe]:~# dovecot --version 1.0.3 * Operating system or Linux distribution name Slackware 10.2, both kernel 2.6.21.3 and dovecot self-compiled * CPU
2013 Feb 27
2
how to talk with doveadmin unix socket
Hello, I would like to get mailbox quota by doveadm unix socket (/var/run/dovecor/doveadm-server). I get from strace syntax of comunication: write(9, "VERSION\t1\t0\nUSER\t1\tpiotr.rotter at active24.pl\tservice=doveadm\n", 60) = 60 read(9, "VERSION\t1\t1\nSPID\t20805\n", 8192) = 23 read(9, "USER\t1\tpiotr.rotter at active24.pl\temail=piotr.rotter at
2012 Jul 22
2
maildir_copy_with_hardlinks on v.2.0.19
Hi, I'm trying to get the so-called "single instance store" (I think cyrus has got the name for the first time) with dovecot --version = 2.0.19 binary package installed from ubuntu 12.04 lts official repo. I have checked that "maildir_copy_with_hardlinks" is enabled ("dovecot -a|grep hard" shows "yes") then I have installed and enabled the lmtp
2008 Nov 12
1
Sieve authentication / directory issue after upgrade to 1.0.13.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, I have come across a problem after upgrading from 1.0.rc17 to 1.0.13 (debian builds 1.0.13 is from etch-backports). I initially upgraded as 1.0.rc17 isn't compiled with regex support, so vacation messages that were uploaded via horde were being rejected. (Everything else was working fine, just messages that required regex functions
2005 Mar 30
2
test65 killed by SIGSEV
Hi, I had successfully set up dovecot-1.0-test62 + ldap pass/user db, but now I'm encoutering a SIGSEV problem with a similar set up of a brand new dovecot-1.0-test65 installation. The auth process is killed by a SIGSEV as reported in the error log file : dovecot: Mar 30 17:06:59 Error: child 28291 (auth) killed with signal 11 To be precise, the problem occurs in the
2009 Jun 10
0
1.2rc5, another crash: Backtrace:dovecot-auth
Another crahs with backtrace: GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was
2009 Jun 10
1
1.2rc5 crash: Backtrace:dovecot-auth
GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as
2016 Nov 21
2
Exim still accepting emails to nonexistent users
Hi, Heiko Schlittermann <hs at schlittermann.de> (Mo 21 Nov 2016 11:50:13 CET): > a) Routing stage > You need to interact with the user database dovecot uses. > Either you access the user database directory (flat file, LDAP, > whatever) or you use the ${readsocket?} feature of Exim to talk to > dovecot. The readsocket trick doesn't seem to work anymore. Using $
2009 Aug 31
1
dovecot-auth segfault with vpopmail 5.5.0 on amd64
Seeing dovecot-auth segfault on amd64 dovecot is 1.2.4 pertinent details below: ldd /usr/local/libexec/dovecot/dovecot-auth linux-vdso.so.1 => (0x00007fffef1fe000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x00007fe8e6bae000) libvpopmail.so => /usr/lib/libvpopmail.so (0x00007fe8e6986000) libdl.so.2 => /lib/libdl.so.2 (0x00007fe8e6782000) librt.so.1 => /lib/librt.so.1
2009 Feb 24
4
dovecot1.2 segfault
I've tried 2 builds of dovecot, based on a amd64 rebuild of the experimental package on http://xi.rename-it.nl/debian/ I've tried to include as much useful info as possible, sorry if I've missed out anything of use. Let me know as I'm more then happy to assist in any way possible. $ telnet host 110 Escape character is '^]'. +OK Dovecot ready. USER ian at domain.com +OK
2011 Nov 15
3
Seg fault in dovecot/auth 2.0.15
Folks: I've been running Dovecot 2.0.7 on a Qmail / Vpopmail installation built on Debian Squeeze, with no problems for about a year. Dovecot is used for IMAP/S auth only. Dovecot is built from source. I just upgraded to 2.0.15 but it segfaults whenever an IMAP auth is attempted, regardless of the user who tries to login, whether by webmail (Roundmail) Android phone (K-9 Mail) or iPad
2016 Nov 23
0
Exim still accepting emails to nonexistent users
Hi Heiko, Sorry for using your private email address. :/ I managed to get this working using local_user changes by adding ldap user verification there: local_user: debug_print = "R: local_user LDAP lookup for $local_part@$domain" driver = accept domains = +local_domains condition = CHECK_VIRTUAL_USER transport = dovecot_lmtp cannot_route_message = Unknown user Where
2008 Mar 12
1
deliver fails - passdb doesn't support lookups?
Hello, I'm trying to get `deliver` (the LDA) to function properly. I can get it to work without doing a user lookup, but for my own sense of sanity, I want to know what I'm doing wrong getting user lookups working. (I'm using dovecot 1.0.10). Here's what I have in the "auth default" section: auth default { mechanisms = plain login passdb ldap
2010 Jun 24
2
Work with auth socket
I need to use Dovecot auth socket from my perl script to validate user's passwords (for jabber server). Is there any information about how to communicate with dovecot auth socket?
2010 Feb 26
2
segfault with vpopmail 5.5.0
Hi, version: 1.2.10 OS: Debian unstable/x86_64 [118905.528497] dovecot-auth[3856]: segfault at 0 ip (null) sp 00007fff6666ad98 error 14 in dovecot-auth[400000+61000] 2010-02-26 22:17:45 dovecot: Error: child 3856 (auth) killed with signal 11 (core dumped) (gdb) bt full #0 0x0000000000000000 in ?? () No symbol table info available. #1 0x0000000000423b0e in vpopmail_lookup_vqp
2013 Oct 24
1
Problems with userdb lookup
Hello, since few days there are problems with the userdb lookup. The problem occur if the recipient user is unknown (here test at xtlv.cn) doveconf -n # 2.2.6 (f89e645cba90): /etc/dovecot/dovecot.conf # OS: Linux 3.2.45.stk32 i686 Debian jessie/sid ext3 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = digest-md5 cram-md5 auth_username_translation = %Lu auth_verbose = yes
2008 Jan 20
3
Exim Dovecot Authentication Problem
Having a hard time figuring out something that is supposed to be easy. Tryiong to configure Dovecot so that it provides authentication to Exim for outgoing smtp. Tried different things and getting authentication socket protocol error dovecot_plain: driver = dovecot public_name = PLAIN server_socket = /var/run/dovecot/auth-client server_set_id = $auth1 auth default { # Space
2016 Nov 21
2
Exim still accepting emails to nonexistent users
Hi Heiko, Here is the router: virtual_aliases: driver = redirect debug_print = "R: Check address using virtual_aliases for $local_part@$domain" allow_fail allow_defer hide data = CHECK_VIRTUAL_ALIASES user = vmail group = mail local_user: debug_print = "R: local_user for $local_part@$domain" driver = accept
2011 Apr 16
3
calling dovecot exported auth from Java
As far as I have been able to figure out, dovecot auth always works over a Unix domain socket. I believe it is not currently possible to operate dovecot auth over an Internet domain (TCP) socket. Am I correct? I want to call dovecot's exported authentication from a Java application. Java doesn't natively know how to talk to a Unix domain socket, so there are inconveniences. There