similar to: imap segfault in mail-cache.c

Displaying 20 results from an estimated 140 matches similar to: "imap segfault in mail-cache.c"

2006 Jan 27
1
gcc 2.95 compile errors
Timo, This is what I get when I compile 1.0-beta2 with gcc 2.95. It looks like I can then open my problem mbox even without your mbox-sync patch. It turns out I'd been using gcc 3.2.2 inadvertently, probably via some sort of shell bug - I'd accidentally set an environment variable called "PATH=/opt/RDGgcc3/bin:/usr/bin ..." and I guess some script had mistaken it for the real
2005 Apr 10
0
imap segfault in mail-index-sync.c
Our support team seems to have caused another crash. They treat this mailbox like a shared one, so there may be a few people accessing it at once. They are mostly using dovecot, but some could be using uw-imap. These are the only two ways that this box is accessed. I know that this doesn't really work with mbox, but it doesn't appear to corrupt the mailbox. It seems to be a good stress
2005 Oct 02
0
can't access dovecot IMAP account w/TBird ... ok w/ other clients
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi all, i'm using dovecot --version 1.0.alpha3 dovecot --build-options Build options: ioloop=poll openssl postgresql Passdb: checkpassword pam passwd passwd-file sql Userdb: checkpassword passdb passwd passwd-file sql static on OSX 10.4.2. i've set up for maildir: format PLAIN text AUTH, w/ "disable_plaintext_auth =
2012 May 11
2
multi-instance doveadm user -m woes
I'm having difficulty with the doveadm who command on a multi-instance setup of dovecot. When I run the who command on the non-standard instance with the -m flag (to see their mail location), this happens: [root at wardentest3 dovecot]# doveadm -i mailtest user -m warden doveadm(root): Error: user warden: Initialization failed: Namespace 'INBOX.': Ambiguous mail location setting,
2008 Sep 08
6
error in 1.1.2
Ive been getting a LOT of these errors since 1.1.2: So far ive seen this with 1800 customers, and we're getting active complaints about errors in imap clients. When I check the users log I always see this error.. This always happens with COPY commands in Squirrelmail. Sep 2 20:09:35 userimap4.xs4all.nl dovecot: IMAP(xxxxxxx):
2010 Dec 21
3
doveadm "-S <socket_path>" option enabled in 2.0.8?
I apologize if this is a stupid question but I just compiled 2.0.8 and am trying to use doveadm to get the quota for a user using the -S <socket_path> option because I have different options for the various local IPs that dovecot listens on. For example, my default quota is filesystem (NFS rquota) and I can get that by doing: doveadm quota get -u warden which tells me: Quota name
2005 Aug 30
0
New imap assertion failure
This is from the CVS version as of Aug. 28. It's the first time I've seen this assertion failure. Prior to this, I was using the CVS version from Aug. 15. dovecot: Aug 30 16:07:52 Error: 24929 IMAP(support): UIDVALIDITY changed (1125327213 -> 1125430510) in mbox file /mailhome/new/s/b/support/mbox dovecot: Aug 30 16:08:13 Error: 24929 IMAP(support): UIDVALIDITY changed
2005 Jun 04
0
Crash and Assertion Error
I've attached two backtraces, one from a segfault and another from an assertion error in imap. I've seen a couple of the same assertion and this is the only segfault. It looks like they could be related. They both have to do with indexing anyway... The code is from CVS as of May 30. The segfault happened while imap was doing searches for my pine filters. I've also noticed that in
2005 Feb 03
1
help troubleshooting inconsistencies in back up sizes
Hello list, I'll first describe my set up: server1 : live server server2 : backup server3 : backup of the backup so the data set is copied in this order server1->server2->server3 they are not done at the same time so there would be no collisions. I use this shell script to back up: for i in a b c d e f g h i j k l m n o p q r s t u v w x y z `seq 0 9`; do
2020 Aug 18
2
INBOX sharing does not work
Hello! INBOX sharing does not seem to work, although all other mailboxes work. User bar at example.de has shared a few mailboxes: # doveadm acl get -u bar at example.de INBOX ID Global Rights user=foo at example.de lookup read write-seen # doveadm acl get -u bar at example.de Sent ID Global Rights user=foo at example.de
2005 Mar 26
0
Another imap crash...
The segfault problem that was happening seems to be fixed. I'm still getting some "(imap) killed with signal 6" errors. I just noticed that it did get one segfault. Unfortunately, I don't have a core file. I'll try to get one if this happens again. Here's the error messages, not sure if it will help. I'm using the CVS copy from March 24. dovecot: Mar 26
2006 Nov 09
1
Using Substring Width with Mailhome Variables
Hello All, I am currently running Dovecot v1.0.rc13 from dovecot-1.0-0_31.rc13.fc5.at.i386.rpm on Linux HOST 2.6.17-1.2157_FC5 #1 Tue Jul 11 22:55:46 EDT 2006 i686 i686 i386 GNU/Linux. I am trying to install Dovecot in a large mail hosting environment and running into troubles. I have specified my mail home in dovecot.conf as follows: default_mail_env =
2012 Apr 25
2
stats + fts squat plugins, indexer-worker error on message indexing
On RHEL 6.2 + dovecot 2.1.5 with the stats and fts (squat) plugins enabled and each user having their own uid on the system I get the following error in the logs when the indexer-worker process indexes some messages: Apr 25 09:56:19 wardentest3 dovecot: imap-login: Login: user=warden, method=PLAIN, rip=137.238.60.164, lip=137.238.2.240, lport=1993, mpid=19464, encryption=TLS Apr 25 09:56:26
2008 Mar 08
3
1.1 master auth not expanding static userdb variables
Can dovecot-1.1 deliver work with static userdb? I'm currently running dovecot-1.0.12 and postfix-2.4.6, with virtual users' maildirs all owned by vmail and mail_location = maildir:/var/mail/%Lu. The following definition of the dovecot transport in postfix/master.conf works fine with dovecot-1.0: dovecot unix - n n - 1 pipe flags=DRh
2020 Aug 19
0
INBOX sharing does not work
Hi, try setting mail_shared_explicit_inbox=yes https://doc.dovecot.org/settings/core/#mail-shared-explicit-inbox <https://doc.dovecot.org/settings/core/#mail-shared-explicit-inbox> Sami > On 18. Aug 2020, at 23.56, Torsten <dovecot.lists at saldyn.net> wrote: > > Hello! > > INBOX sharing does not seem to work, although all other mailboxes work. > > User bar
2009 Sep 23
1
strange split behavior?
Hi, Please see the command with a comment below. I don't find 'A630039F22Rik' in y. But 'A630039F22Rik' is in z. Can somebody let me know what the problem is? Regards, Peng > str(x) int [1:365494] 6 7 8 14 15 18 19 21 25 29 ... > str(y) Factor w/ 29904 levels "0610005C13Rik",..: 17261 28617 15927 15462 8988 23500 16577 20250 27911 13981 ... >
2005 Mar 23
2
Segfault in imap process
We've been testing dovecot for a while and I noticed yesterday that imap crashes quite often. It seems to be about even with SIGABRT and SIGSEGV. This one was SIGSEGV. Our system is SuSE Linux 9.2, 2.6.11.5 kernel (also happened with an older 2.6 kernel). Dovecot version is 1.0-test64 and was compiled with: "./configure --prefix=/services/dovecot --disable-ipv6" It's using
2005 Oct 18
0
A Couple Assertion Failures
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
2005 May 11
1
Segfault in imap process
I'm running the CVS version from May 9. I've seen these errors in the log file before (every time I open my mailbox), but this is the first time it crashed. Todd dovecot: May 11 15:00:18 Error: 8438 IMAP(todd.bluegenesis.com): Corrupted index cache file /mailhome/new/t/b/todd.bluegenesis.com/.imap/INBOX/dovecot.index.cache: Duplicated field in header: hdr.RESENT-TO dovecot: May 11
2010 Sep 25
1
password_query, user_query and unrelated userid and emails
Let's say one has a SQL table with following fields for John Doe: login: u0007 password: {SHA1}... mailhome: /path/to/joeshome email: john.doe at example.com To log in, for internal policy reasons, John MUST make use of his userid "u0007". So, in the password_query, one would need something like: ... WHERE login = '%u' ... On the other hand, for receiving mail thru