similar to: LDA bouncing mails after upgrade

Hi Timo, some time ago (2007-03-24 and following) I asked whether it was intended that Dovecot deliver bounces mails (by terminating with status 89) if the deliver version is older than the rest of the dovecot installation. You replied that it was a bug, and that it had been fixed in <URL:http://dovecot.org/list/dovecot-cvs/2007-March/008346.html>. When I upgraded from Dovecot 1.0.2 to

Hi, this is a repost of a previous question - since then I have tried rebuilding my Xen0 kernel numerous times and trying different configurations, but I haven''t yet ever got a single DomU to boot so I really don''t even know what is supposed to happen, let alone how to start debugging it... Can someone please speculate on how to debug this further? It''s a gentoo

Hello all, I have a problem with an incosistent mdbox: Oct 24 10:43:23 two dovecot: imap-login: Login: user=<...>, method=PLAIN, rip=..., lip=..., mpid=4977, TLS Oct 24 10:43:23 two dovecot: imap(listen at mjh.name): Error: mdbox map .../mdbox/storage/dovecot.map.index corrupted: Unexpectedly lost INBOX uid=638 map_uid=809891 Oct 24 10:43:23 two dovecot: imap(listen at mjh.name): Error:

Has anyone written a script or function to read data from NODC?s World Ocean Database files? (I know there are simple Fortran and C programs to read these files, but the output is not suitable for easy analysis) Thanks, Franz _____________________________________________________ Dr. Franz J. Mueter School of Fisheries and Ocean Sciences, Juneau Center University of Alaska Fairbanks 11120

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I complained some time ago that a the dom0-kernel (2.6.9-based) inside Xen would wait forever when trying to detect the hard disks connected via the S-ATA controller, which is provided by the nForce 250Gb chipset. The problem guessed by Keir (IIRC) was that the interrupt routing didn''t work because Xen didn''t use ACPI to do

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, Is the sata_nv (based on SCSI) driver supposed to work with Xen? When I tried to boot my dom0 kernel recompiled with the sata_nv drivers enabled my kernel locks up, I guess when probing the first drive connected via S-ATA. ("Screenshot" here: <URL:http://mjh.name/xen.lock.1.jpg>) (Kernel also says that partition tables of the

Dear R Users - R is a wonderful software package. CRAN provides a variety of tools to work on your data. But R is not apt to utilize all the public databases in an efficient manner. I observed the most tedious part with R is searching and downloading the data from public databases and putting it into the right format. I could not find a package on CRAN which offers exactly this fundamental

Hey, when I try to run the setup for Republic the Revolution using the latest version of wine and intrepid I get this output from the terminal > ~$ wine /media/cdrom/setup.exe > fixme:advapi:LookupAccountNameW (null) L"chris" (nil) 0x32bdf0 (nil) 0x32bdf4 0x32bde8 - stub > fixme:advapi:LookupAccountNameW (null) L"chris" 0x180f30 0x32bdf0 0x181300 0x32bdf4 0x32bde8 -

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 No-one out there who can give me any tips for this? (Then the space to do experiments will finally be used in other ways. And I hope this mail won't be consired to impolite...) On Mon, 6 Dec 2004 15:23:15 +0100 Milan Holz?pfel <lists at mjh.name> wrote: > Hello, > > I got an IDE-drive which decided to get broken. Part of

Hi! On 2020-06-16 12:37 -0000, Stuart Henderson wrote: > On 2020-06-15, Alexander Strasser <eclipse7 at gmx.net> wrote: > > I had some imap crashes (sig11) starting at the end of 2019 after > > an upgrade of dovecot. > > > > I found out, that I didn't have any problems using version v2.3.8, > > but any version v2.3.9 and higher would trigger the crashes.

Hi all! This is my first post on this list. Please pardon me if I overlooked or misunderstood some things. I had some imap crashes (sig11) starting at the end of 2019 after an upgrade of dovecot. I found out, that I didn't have any problems using version v2.3.8, but any version v2.3.9 and higher would trigger the crashes. After investigating more deeply and creating a core dump, I saw that

And more fixes. * Dovecot now fails to load plugins that were compiled for different Dovecot version, unless version_ignore=yes is set. This needs to be explicitly set in plugins, so out-of-tree plugins won't have this check by default. - pop3_lock_session=yes could cause deadlocks, and with maildir the uidlist lock could have been overridden after 2 minutes causing problems

And more fixes. * Dovecot now fails to load plugins that were compiled for different Dovecot version, unless version_ignore=yes is set. This needs to be explicitly set in plugins, so out-of-tree plugins won't have this check by default. - pop3_lock_session=yes could cause deadlocks, and with maildir the uidlist lock could have been overridden after 2 minutes causing problems

Hello, upgrade Dovecot from v1.2.10 to v2.0.8, after build a new configuration file following instructions of http://wiki2.dovecot.org/Upgrading/2.0 run dovecot I get this: auth: Error: Fatal: Dovecot version mismatch: Master is v2.0.8, dovecot-auth is v1.2.10 (if you don't care, set version_ignore=yes) log: Error: service(auth): child 3389 returned error 89 (Fatal failure) master: Error:

Hello, When upgrading Dovecot, I get this: Dovecot version mismatch: Master is v2.0.6, imap-login is v2.0.7 (if you don't care, set version_ignore=yes) This should not occur as version_ignore=yes is in dovecot.conf, at the top. Cheers, Olivier

hi list I upgraded to 1.1.3, and have my logs turned off for some time, but turned it back on when someone complained about moving emails. I saw this in the logs. Seems strange. Using gentoo on AMD 64 bit. All is working fine, but is this a cause for alarm. dovecot: Jun 05 17:10:32 Fatal: imap-login: Dovecot version mismatch: Master is v1.1.rc6, login is v1.1.rc8 (if you don't care, set

My unit's firmware: library 05.03, tape d22h, shows the device as set to random mode. But mtx -f /dev/st0 status gives an error that google says the device is in sequential mode. dmesg|grep -i hp does reflect CentOS thinks the device is a sequential unit. I've tried this with Fedora 8, too, and both show the same, so it is either an issue with CentOS/Fedora RPMs, or the version of

Dear all, I am trying to use Samba with LDAP support so I can't use the CIFS binaries. I are having an issue with compiling samba-2.27.a (patched) on our HPUX server. I am configuring it with these Samba option flags: --prefix=/opt/samba --libdir=/etc/opt/samba --localstatedir=/var/opt/samba --with-privatedir=/var/opt/samba/private --with-lockdir=/var/opt/samba/locks

I''m getting an odd kernel panic which I cannot get the whole error for, I believe it has something to do with a designation for the root filesystem. About the time it would be mounting the root filesystem, there is a kernel panic and it reboots less than 1 second later. I have lokoed around for dmesg logs and tried using the magic PAUSE, but with no luck. Recommendations? I

Hi, I was trying to run a guest OS with multiple partitions. I added a line like disk=[''phy:hda6,hda6,w''] in the configuration file. The disk was not mounted in the host OS. However, the kernel refuses to boot with an error message which says "kernel not syncing... attempted to kill init... rebooting...". When I remove that line, everything works. Is there