similar to: Panic on one specific user

(I will not make a joke about the streets of Carlyle) Jan 13 19:09:07 mail dovecot: lda(john at example.com): Panic: file mail-transaction-log-file.c: line 1148 (mail_transaction_log_file_get_highest_modseq_at): assertion failed: (offset <= file->sync_offset) Jan 13 19:09:08 mail kernel: pid 8435 (dovecot-lda), uid 89: exited on signal 6 (core dumped) Jan 13 19:14:16 mail dovecot: lda(john

Hello Timo, I'm having a problem with mbox that opening folder is slow when new mails are delivered to a folder. I'm delivering through the deliver program. Deliver updates index files but IHMO not completely correct. Therefore I compared index files before and after: 1.) Just delivered 2.) After accessing through imap via Thunderbird diff looks like (stripped down to the relevant

In V1.1.15 that I fell back to. Again: # 1.1.15: /usr/local/etc/dovecot.conf # OS: AIX 3 0001378F4C00 listen: *:143 ssl_listen: *:993 disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_processes_count: 12 login_max_processes_count: 774 max_mail_processes: 1024 verbose_proctitle: yes first_valid_uid: 200

Two nights ago I took a leap and extended my testing of dovecot 1.1 by replacing 1.0 for the approx 15 users I had on 1.0. At that time I also for the first time tried dovecot 1.1 in a load balanced 2 server configuration with indexes on NFS. I was hoping I did this right, using the mail_nfs params and 1.1 so fchown etc would flush the access cache, but I am getting a number of messages and

On 21.07.2017 20:47, Bruce Guenter wrote: > 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

Am 21.07.2017 um 19:47 schrieb Bruce Guenter: > > 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. you should avoid this one solution is to use loadbalancers

I got the following panic on 1.2.3: Panic: file mail-transaction-log-append.c: line 88 (log_buffer_move_to_memory): assertion failed: (file->buffer_offset + file->buffer->used == file->sync_offset) It's probably related to the file system holding the indexes being full.

Hi, I'm experiencing a problem I need some pointers to debug. I'm running Dovecot 2.0.15 and have a client which keeps causing log-entries like: Nov 4 15:10:42 mail dovecot: imap (test at aaaone.net): Error: Corrupted transaction log file /mail/3340444/.TestMails/dovecot.index.log seq 2: indexid changed 1320419300 -> 1320419441 (sync_offset=0) Nov 4 15:10:42 mail dovecot:

mail dovecot: lda(user at domain)<955><rPK3B2Gr4Vy7AwAAIdGjjQ>: msgid=<4562Sm6YyYzvmrD at mail.covisp.net>: save failed to INBOX: Mailbox INBOX: open(/usr/local/virtual/user at domain/tmp/1558293345.M130062P955.mail.covisp.net) failed: Permission denied The permissions on /usr/local/virual have not changed and are still owed by user/group 89/89 dovecot-sql.conf.ext: user_query

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

Timo (and anyone else who feels like chiming in), I was just wondering if you'd be able to tell me if the amount of corruption I see on a daily basis is what you consider "average" for our current setup and traffic. Now that we are no longer experiencing any core dumps with the latest patches since our migration from courier two months ago, I'd like to know what is expected

Hi, I am getting IMAP FETCH FLAGS in response to SORT and SEARCH commands for my INBOX. See the following transcript between dovecot (marked with S:) and an imap client (marked with C:) for an example SEARCH command. C: A004 UID SEARCH CHARSET ISO-8859-1 ALL TEXT {4} C: test S: + OK S: * SEARCH 5 13 20 21 22 23 24 30 37 39 56 64 77 82 93 94 96 103 109 110 118 135 136 158 160 165 171 174

Hi, I know that is not possible make a stepwise procedure using REML in R, I can use ML for this. For nested design it may be very dangerous due the difference in variance structure, mainly in a splitplot design. ML make significative variables that REML dont make. I read an article that is made a stepwise procedure using GENSTAT. from article: "Terms were dropped from a model in a

I'm seeing this periodically in my logs for a specific user (followed by a backtrace which I've deleted from this post): Panic: file dovecot-1.2.11/src/lib-index/mail-transaction-log-view.c: line 290 (mail_transaction_log_view_set): assertion failed: (min_file_seq != max_file_seq || max_file_seq != view->head->hdr.file_seq || max_file_offset != (uoff_t)-1 || min_file_offset <=

I'm running Dovecot version 1.2.11 and getting this assertion error on a user's mail: Panic: file /home/durket/dovecot-1.2.11/src/lib-index/mail-transaction-log-view.c: line 290 (mail_transaction_log_view_set): assertion failed: (min_file_seq != max_file_seq || max_file_seq != view->head->hdr.file_seq || max_file_offset != (uoff_t)-1 || min_file_offset <=

Hi everybody, I'm runing dovecot 2.2.12 and a user mailbox got the "broken sync positions in index file" error twice in the last 20 days. this is an extract from the maillog maillog First Error -------------------- Mar 23 16:13:25 andromeda dovecot: pop3-login: Login: user=<myuser at mydomain.com>, method=PLAIN, rip=187.237.107.24, lip=207.7.90.83, mpid=3983,

My mail server consumed all of its configured file table slots and started returning ENFILE ("Too many open files in system") for many operations. This wreaked havoc with dovecot-1.1.13. Here are some areas where dovecot should detect and more gracefully handle ENFILE error returns: 1. Deliver should report an error more helpful than "Unknown internal error" when

On Sun, Mar 8, 2020 at 4:36 PM Piviul via samba <samba at lists.samba.org> wrote: > > Il 07/03/20 21:27, Reindl Harald ha scritto: > > but given that such machines must not be in the normal environment > > anyways why do you need the latest and greatest samba? > but the same user can work on an old winxp or latest win10 machine and > have to share and access the same

Hello I run dovecot 2.0.6 on a two-machine cluster using OCFS2 as the file system. I have some error messages like these in my log: Oct 25 01:07:50 box5 dovecot: lmtp(8886, suporte=100br.com at lmtp1.prv.f1.k8.com.br): Error: Corrupted transaction log file /var/lib/imap/user/a3/suporte=100br.com/stor age/dovecot.map.index.log seq 29: Transaction log corrupted unexpectedly at 21536: Invalid size

Hi I came across this error which happend immedately after a mail delivery to the inbox. Should I look for the problem externally to dovecot (ie. file system, operating system) or within dovecot? I never saw this error before installing 2.2.1, with 2.2.2 I seemed to get even more of them so currently back on 2.2.1 Thanks John Jun 11 00:00:05 rosalia dovecot: imap(myemail at mydomain): Error: