Displaying 20 results from an estimated 3000 matches similar to: "Squirrelmail - messages not marked as read"
2004 Nov 18
1
Only one malfunction in months - now running dovecot-1.0-test52
Dont think there has been even one failure in some months of use
but tonight we're seeing this running test-52
While running squirrelmail 1.5.1-CVS a certain message causes:
dovecot: Nov 17 22:25:14 Error: IMAP(kimc): file ostream-file.c: line
643 (_send_istream): assertion failed: (instream->v_offset <=
in_size)
dovecot: Nov 17 22:25:14 Error: child 72172 (imap) killed with signal
6
2004 Nov 20
1
imap: assertion failed
This error is returned when reading a certain message using
Squirrelmail.
Any help on tracing the cause of this is greatly appreciated.
>From the logs:
dovecot: Nov 20 13:00:29 Error: IMAP(kimc): file ostream-file.c: line
643 (_send_istream): assertion failed: (instream->v_offset <=
in_size)
dovecot: Nov 20 13:00:29 Error: child 27873 (imap) killed with
signal6
-kim
2004 Dec 05
3
(_send_istream): assertion failed:
This is on FreeBSD 5.3, is this fixed in -test or CVS ?
Log message is below..
dovecot: Dec 05 07:48:08 Error: IMAP(kimc): file ostream-file.c: line
643 (_send_istream): assertion failed: (instream->v_offset <=
in_size)
dovecot: Dec 05 07:48:08 Error: child 42086 (imap) killed with signal
6
-kim
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo!
2008 Feb 27
4
Index corruption with squirrelmail.
Hi.
I don't know if the problem is related with squirrelmail or not, but I
started to have index corruption when I started to try squirrelmail.
Some informaton about my instalation:
dovecot 1.0.5-1 debian package with maildir
squirrelmail 1.4.9a-2 debian package
Some log information:
dovecot: 2008-02-27 08:39:39 Warning: IMAP(<please don't send spam to
me>): fscking index file
2009 May 04
2
mail_index_sync_map error on 1.1.14
Seen this error a few times from dovecot-1.1.14, Mac OS X, 64-bit
Intel. NFS may have been used.
Panic: IMAP(user): file mail-index-sync-update.c: line 843
(mail_index_sync_map): assertion failed: (map->hdr.indexid == index-
>indexid || map->hdr.indexid == 0)
Two different backtraces to this error are:
0 libSystem.B.dylib 0x00007fff87b775ea __kill + 10
1
2003 Jun 16
2
more newline related errors
Should I be concerned about these errors?
imap(msun): Jun 13 13:21:38 Error: Error indexing mbox file /home/msun/mail/Deleted Messages: LF not found where expected
imap(msun): Jun 13 13:39:08 Error: Corrupted binary tree for index /home/msun/mail/.imap/INBOX/.imap.index: lookup returned index outside range (1 >= 0)
imap(msun): Jun 13 13:44:07 Error: IndexID mismatch for binary tree file
2004 Jul 27
2
Errors with a blackberry
Hi -
We tried to access a dovecot-0.99.10.7 IMAPS server with a Blackberry
7230. The Blackberry was on loan so we don't have much access to it for
testing.
We got the following in our logs:
Jul 27 12:30:27 xserv imap-login: Login: testuser [xxx.xxx.xxx.xxx]
Jul 27 12:30:27 xserv imap(testuser): IndexID mismatch for binary tree
file /home/testuser/mail//.imap/INBOX/.imap.index.tree
Jul 27
2018 Aug 08
1
dovecot Panic: file mail-index-sync-update.c: line 1013
An email came to several users but one user didn't receive it and we got
'Mail delivery failed' message.
As I see from the log below, there were broken index file.
Then dovecot repaired that index and we got the error:
Panic: file mail-index-sync-update.c: line 1013 (mail_index_sync_map):
assertion failed: (map->hdr.indexid == index->indexid || map->hdr.indexid
== 0)
It was
2005 Dec 30
1
Compile problem on FreeBSD 6.0-STABLE
Trying to update to dovecot-1.0.alpha5 and seeing this at compile time:
mech-gssapi.o mech-gssapi.c; then mv -f ".deps/mech-gssapi.Tpo"
".deps/mech-gssapi.Po"; else rm -f ".deps/mech-gssapi.Tpo"; exit 1; fi
mech-gssapi.c:30:27: gssapi/gssapi.h: No such file or directory
mech-gssapi.c:42: error: syntax error before "gss_ctx_id_t"
mech-gssapi.c:51: error:
2017 Jul 21
4
Corrupt index files
I am running Dovecot IMAP on Linux, on a LizardFS storage cluster with
Maildir storage. This has worked well for most of the accounts for
several months.
However in the last couple of weeks we are seeing increasing errors
regarding corrupted index files. Some of the accounts affected are
unable to retrieve messages due to timeouts.
It appeared the problems were due to the accounts being accessed
2012 Mar 27
1
2.1.2 Corrupted squat uidlist
Hi Timo and All,
after upgrading to 2.1.2 i'm getting a lot of these messages:
Error: Corrupted squat uidlist file XXXXXX wrong indexid
I did not have them before.
Ideas?
Luca
2009 Sep 30
3
Some issues in Dovecot 1.2.5 after upgrade from 1.0.15
We upgraded from Dovecot 1.0.15 to 1.2.5 last night, on Solaris 10 using
mboxes, mostly without issues.
However I had to trash the index/cache files (too many folders were
showing corruption issues which is especially bad for Prayer Webmail
".prayer" folders that store preferences; Prayer sees a disconnection as
the folder being missing!).
I've had one imap process panic in mailbox
2005 Feb 25
4
corruption and errors in dovecot-stable
Hi,
We switched from dovecot 0.99.something to 1.0-stable (on FreeBSD 4.10)
a few days ago and have been seeing many errors and one corrupted
mailbox so far. Almost everyone uses mbox format, and most users
primarily use SquirrelMail; I use Apple Mail and Thunderbird, as well
as accessing the mailboxes locally with Mutt, and have not noted any
visible problems.
There have been several of
2005 Dec 31
3
Using dovecot auth with Postfix
Attempting to setup smtpd auth for Postfix using the Dovecot authorization
unix socket.
Some info is at: http://www.postfix.org/SASL_README.html
To enable operation when Postfix is chrooted, a method from the
reference above is to locate the socket at: /var/spool/postfix/private/auth
To do this, I have this configuration in dovecot.conf:
# listener sockets will be created by Dovecot's
2004 Dec 16
2
Just delete that index
I get a few messages of this ilk each day:
Dec 16 01:56:31 aurora dovecot: IMAP(doug): Corrupted index cache file
/home/doug/Maildir/.users.joe/dovecot.index.cache: indexid changed
I usually address this by deleting dovecot.* in the directory of issue. I
was thinking that I could instead just have the server delete these files
and attempt to recreate them, and skipping that error message
2006 May 22
1
beta8: cores on corrupted index file
Timo,
I saw a couple of these cores over the weekend. The syslog says:
May 21 19:04:48 emerald dovecot: [ID 107833 mail.error] IMAP(user): Corrupted index cache file /home/students/s/user/.imap/sent-mail-apr-2004/dovecot.index.cache: indexid changed
With a resulting core file from imap at this time. I also discovered
a remaining lock file on the person's imap file:
-rw------- 1 user
2006 May 28
1
FreeBSD Digium g.729 codec seg faults on rev 30652
Greetings-
Was running the Digium FreeBSD g.729 codec until recently when the latest
Asterisk bits were obtained via svn:
svn checkout http://svn.digium.com/svn/asterisk/trunk asterisk
This produced:
Checked out revision 30652
This on FreeBSD 6.1-RELEASE
Attempting to start asterisk it returns:
== Registered custom function URIENCODE
[codec_g729a.so]May 27 13:29:59 WARNING[71884]:
2005 Aug 29
2
Sig11 and some corrupted indexes after 1.0-stable -> 1.0.alpha1
I just upgraded my production box from 1.0-stable to 1.0.alpha1. I've
noted some new errors in my dovecot logs:
Aug 28 23:23:56 cliff dovecot: IMAP(rsferra): Corrupted index cache
file /mail/mcad.edu/rsferra/Maildir/.Sent Items/dovecot.index.cache:
indexid changed
Aug 28 23:33:57 cliff dovecot: IMAP(acarr): Corrupted transaction log
file /mail/mcad.edu/acarr/Maildir/.Deleted
2005 Jun 07
1
Multiserver config
Hi!
I need use dovecot on 3 servers. Home directory and mail spool shared
over NFS in pop3/pop3s only mode (no imap).
What details for dovecot config need set?
When I try 2-servers config, some time I get in log:
Jun 7 04:31:01 cluster2 pop3(andy at atomail.com): IndexID mismatch for
binary tree file
/home/plasma/andy at atomail.com/mail//.imap/INBOX/.imap.index.tree
But mail client not
2005 Sep 07
1
1.0alpha1: corrupted cache file complaints?
Hi,
I have seen the following in my syslogs for 1.0alpha1:
Corrupted index cache file [filename]: record points outside file
and
: indexid changed
: record list is circular
: Cache record offset 9772 points outside file
: invalid record size
Are these errors minor? Major? Self-healing? Should the
cache files be blown away to fix these errors?
Jeff Earickson
Colby College