similar to: dovecot 2.0.19 Panic: file mail-index-sync-ext.c: line 209 (sync_ext_reorder): assertion failed: (offset < (uint16_t)-1)

Hi, Today's core dump from 1.0alpha1 came from a syslog message of: IMAP(user): pool_data_stack_realloc(): stack frame changed gdb info on the resulting core dump attached. Question: how many people are building/using dovecot 1.0alpha1 with gcc 4.0.1 versus gcc 3.4.x? I am wondering if these issues come from the compiler instead of dovecot itself? Jeff Earickson Colby College

Hi Timo & everyone, I'm trying out a 2-node director setup, but I keep getting the following error: Oct 3 16:11:29 imapdir1 dovecot: master: Dovecot v2.0.15 starting up (core dumps disabled) Oct 3 16:11:34 imapdir1 dovecot: director: Error: connect(132.198.100.150:9090) failed: Invalid argument Oct 3 16:11:41 imapdir1 last message repeated 3 times Both nodes report this error. The

Hi Timo & Dovecot users, We have a 2-node director setup which front-ends for 4 nodes which share a clustered filesystem (GFS). All nodes run Dovecot 2.0.18. Approximately 40k users, but typically only a few thousand active at any time. The director nodes run sendmail, which deliver mail "locally" using LMTP to the director, which then feeds to SMTP on the real servers (also

Hello, I current using dovecot with mdbox and on one account i get this error: doveadm(user at domain): Panic: file mail-index-sync-ext.c: line 209 (sync_ext_reorder): assertion failed: (offset < (uint16_t)-1) doveadm(user at domain): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x3fd8a) [0x7fae684fdd8a] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x32)

Here's a couple of assertion failures from CVS version as of Oct. 6. There's also a segfault but the core file was empty so I don't know if the log entries are much help. BTW, the searching speed using pine has dramatically improved, nice work! Todd ----------------------------------------- dovecot: Oct 12 12:04:28 Error: 20278 imap(username): file mail-index-sync-ext.c: line 155

Hello, After fixing configuration and other issues I'm still having one problem with imap executable and pine: less .pinerc # Changed config: #rsh-command=/usr/sbin/dovecot --exec-mail imap rsh-command=/usr/local/bin/imap Calling imap still fails as non root: imap /usr/bin/ld: cannot open output file /usr/local/bin/.libs/2612-lt-imap: Permission denied collect2: ld returned 1 exit statusn

On 17.08.2012 12:06, dof at projektfabrik.com wrote: > Hi everybody, > > trying to get the Dovecot antispam_plugin to work and I must be doing > something wrong, because as soon as it is enabled with a certain > backend, imap logins do not work anymore (the session is immediately > closed after a successful login). Interestingly, pipe and spool2dir > are working (that is, the

While testing an upgrade from Dovecot 1.2.9 (on Ubuntu 10.04 LTS) to 2.0.19 (12.04 LTS) I encountered the following change in behaviour: In both setups, mail_location is defined as follows: mail_location = maildir:~/domains/%d/%n/.Maildir:LAYOUT=fs No other mail_location-related settings are set in the config. On 1.2.9 this leads to new mail being delivered to this example directory:

Hi, In my company, we have several failover clusters (~50k accounts per cluster) with Ubuntu12.04 and Dovecot-2.0.19 (without dsync, replication at block level with DRBD). We are migrating to active/active clusters with Ubuntu14.04 and Dovecot-2.2.15 with replication via dovecot-dsync. Each new cluster consists of two machines and each machine runs two instances of Dovecot (one for backend

Hello, I am currently still running an older dovecot (2.0.19apple1 on Mac OS X 10.8.5) and I want to migrate my users to a new server (macOS 10.12 with Server 5, which contains dovecot 2.2.24 (a82c823)). Basically, I want to create a new server installation on the new server so I don't bring any junk over (new user accounts, with the same uid/gid (still need to figure that one out), but

Hi I have installed the package dovecot-postfix on Ubuntu 12.04 LTS: dovecot --version: 2.0.19 postconf -d | grep version: 2.9.6 and receiving email works very fine, but relaying email does not work. I think the problem is that after STARTTLS the authentication is not being executed 250-AUTH PLAIN 250-AUTH=PLAIN which means using telnet returns telnet mx2.wyona.com 587 Trying

Hi everybody, trying to get the Dovecot antispam_plugin to work and I must be doing something wrong, because as soon as it is enabled with a certain backend, imap logins do not work anymore (the session is immediately closed after a successful login). Interestingly, pipe and spool2dir are working (that is, the session won't be closed), dspam-exec and crm114-exec are not. If this happens,

hi, I can't compile DoveCot 2.0.19 with dbox enabled on our Solaris 10/U9: LDFLAGS="-L/opt/csw/lib -L/usr/lib -R/opt/csw/lib/" ./configure --prefix=/usr/local/dovecot/2.0.19 --with-ssl=openssl --with-rundir=/var/run/dovecot --with-storages=maildir,mbox,dbox --with-ldap=yes gmake -> ========================== [... ../../src/lib-storage/mailbox-list.h:250: warning: parameter has

I am trying to get dovecot 2.0.19 authenticate users via LDAP (OpenLDAP 2.4.28) and using Wireshark to debug the process. It looks like the basic configuration of dovecot is fine, but it doesn't pull it off to send the right request to the LDAP server. First of all, this is how my LDAP-entries look: # ht dn: dc=ht objectClass: top objectClass: dcObject objectClass:

Does anyone remember if there is a way to coerce the ISC DHCPD version 2 (2.0pl5) to send options to a PXE client that does not explicitly request them. I can do this in version 3 of DHCPD via the vendor-option-space mechanism, but this is not available in version 2 of the server (the version my network switch uses). I want to be able to specify the PXE filename via option 209 (plus option 208

On Friday 25 Mar 2011 21:21:18 Marcus Grando wrote: > >> Script is something like that: > >> > >> #!ipxe > >> ifopen net0 > >> set net0/ip 192.168.0.10 > >> set net0/netmask 255.255.255.0 > >> set net0/gateway 192.168.0.1 > >> set net0/dns 8.8.8.8 > >> set 209:string pxelinux.cfg/default > >> set 210:string

On Wed, Jun 5, 2013 at 8:29 PM, Gerardo Exequiel Pozzi <vmlinuz386 at yahoo.com.ar> wrote: > Hello, > > First, this setup works fine without any error in syslinux 4.06 as show > below. > > For convenience, both versions of syslinux 4.06 [#1] and 5.10 [#2] > directories (~2MB each) are uploaded ready for test. > > As said before, this is tested on qemu-1.5.0 +

Am 06.06.2013 07:00, schrieb Gene Cumm: > iPXE details. My testing was with an Intel PXE OROM in a VMware > hosted platform with 0 issues. > >> 1370470692 192.168.0.90 "GET /arch/boot/syslinux/pxelinux.0" 200 26813 >> "" "iPXE/1.0.0+ (09c5)" This is the iPXE version that comes bundled with qemu as the default qemu boot rom. -------------- next

On 06/06/2013 01:25 AM, Thomas B?chler wrote: > Am 06.06.2013 07:00, schrieb Gene Cumm: >> iPXE details. My testing was with an Intel PXE OROM in a VMware >> hosted platform with 0 issues. >> >>> 1370470692 192.168.0.90 "GET /arch/boot/syslinux/pxelinux.0" >>> 200 26813 "" "iPXE/1.0.0+ (09c5)" > > This is the iPXE

Am 06.06.2013 22:42, schrieb H. Peter Anvin: > On 06/06/2013 01:25 AM, Thomas B?chler wrote: >> Am 06.06.2013 07:00, schrieb Gene Cumm: >>> iPXE details. My testing was with an Intel PXE OROM in a VMware >>> hosted platform with 0 issues. >>> >>>> 1370470692 192.168.0.90 "GET /arch/boot/syslinux/pxelinux.0" >>>> 200 26813