Displaying 20 results from an estimated 100 matches similar to: "New imap assertion failure"
2005 May 03
0
Segfault in imap
I'm running the current CVS version, as of April 26. There have been a few
of these with the same problem.
There was a NULL pointer dereference at mail-index-view.c:603
view->map == NULL
Here's the log entry, etc.
dovecot: May 03 08:30:08 Error: 10195 IMAP(support): UIDVALIDITY changed (1115122813 -> 1115123383) in mbox file /mailhome/new/m/2/support/mbox
dovecot: May 03
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 =
2005 Jul 12
0
Altering newly created mailboxes
There seems to be a bug in updating uid/uidvalidity when copying mail to an
empty or newly created mailbox:
<new connection>
. OK Logged in.
. CREATE testfolder4
. OK Create completed.
. SUBSCRIBE testfolder4
. OK Subscribe completed.
. SELECT otherfolder
* FLAGS (\Answered \Flagged \Deleted \Seen \Draft)
* OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags
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
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,
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
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
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
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
2005 Apr 07
1
imap segfault in mail-cache.c
Found an imap crash. I'm using the CVS copy from March 23. This is
running under Linux, kernel 2.6.11.something. We use mbox over NFS,
everything is on the NFS server. There is currently only one dovecot
server accessing the mailbox.
Here's the log messages:
dovecot: Apr 05 13:11:20 Error: 27911 IMAP(support): UIDVALIDITY changed (1112720886 -> 1112721068) in mbox file
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 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 Apr 27
0
Assertion Failures in Current CVS version
I've attached a few assertion errors in imap. Any fixes or advice on
where to look are appreciated.
This is with the CVS version, current as of April 27.
Todd Burroughs
-------------- next part --------------
dovecot: Apr 27 00:00:45 Error: 5714 IMAP(chairman): file mail-index-transaction.c: line 808 (mail_index_update_ext): assertion failed: (seq > 0 && (seq <=
2010 Aug 26
1
Investigating suspected cache corruption
Hi David and all,
I?ve read the mail you posted in the Dovecot list.
We?re are having this same problem in a site which is very similar to yours.
We also migrated from Courier to Dovecot nearly 9 months ago, and every now and then users complain about slowness in
the imap connection. We fix it by removing the index files in the user's maildir.
We use Horde as webmail, but the problem
2009 Oct 14
1
Investigating suspected cache corruption
Hi All,
I'm running Dovecot 1.1.11 for a site of about 7000 active users with
a Squirrelmail frontend. We migrated from Courier (big shout to
everyone who worked on the wonderful part of the Dovecot wiki that
deals with Courier migration) and I have been extremely happy with the
performance gains Dovecot has given us. Not only is the IMAP part of
Squirrelmail faster, but our same
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
2015 Jul 30
1
doveadm import - strange warning
Am 27.07.2015 um 11:41 schrieb Ralf Hildebrandt:
> * Daniel Tr?der <troeder at univention.de>:
>
>> Just guessing?
>>
>> The signature of the command is:
>> doveadm [-Dv] import [-S socket_path] [-s] -u user source_location
>> dest_parent search_query
>>
>> You supply "" as dest_parent which I guess could mean ".", and that