Re: dovecot-uidlist invalid data

2020-10-26 Thread Maciej Milaszewski
Hi
Any idea ? or solutions ?

> Hello
> I have a problem with Invalid data
> System debian10 dovecot-2.2.36.4
>
> # 2.2.36.4 (baf9232c1): /etc/dovecot/dovecot.conf
> # Pigeonhole version 0.4.24.rc1 (debaa297)
> # OS: Linux 4.19.0-12-amd64 x86_64 Debian 10
>
>
> Oct 23 15:57:52 dovecot6 dovecot:
> lmtp(33973,media4_js,2KEXD2Dhkl+1hAAAe3x6RQ): Error: Broken file
> /vmail/me/media4_js/Maildir/dovecot-uidlist line 6875: Invalid data:
>
> In debian9 - kernel-4.9.0-13 - problem exists
> In debian10 - kernel-4.19.0-12 - problem exist
>
> In debian8 - kernel 3.16.0-11-amd64 - problem not exists
> In debian9 - kernel 3.16.0-11-amd64 - problem not exists
>
> storage mount from storage NetApp
>
> storage:/vmail on /vmail type nfs
> (rw,noexec,noatime,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=120,acregmax=120,acdirmin=120,acdirmax=120,hard,nocto,nordirplus,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.19.19.19,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=10.19.19.19)
>
> cat /etc/fstab
> storage:/vmail    /vmail    nfs   
> rw,sec=sys,noexec,noatime,tcp,hard,rsize=65536,wsize=65536,intr,nordirplus,nfsvers=3,tcp,actimeo=120,nocto
>    
> 0    0
>
> Probably somthing in kernel or mount options. Any idea ?
>



dovecot-uidlist invalid data

2020-10-23 Thread Maciej Milaszewski
Hello
I have a problem with Invalid data
System debian10 dovecot-2.2.36.4

# 2.2.36.4 (baf9232c1): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.24.rc1 (debaa297)
# OS: Linux 4.19.0-12-amd64 x86_64 Debian 10


Oct 23 15:57:52 dovecot6 dovecot:
lmtp(33973,media4_js,2KEXD2Dhkl+1hAAAe3x6RQ): Error: Broken file
/vmail/me/media4_js/Maildir/dovecot-uidlist line 6875: Invalid data:

In debian9 - kernel-4.9.0-13 - problem exists
In debian10 - kernel-4.19.0-12 - problem exist

In debian8 - kernel 3.16.0-11-amd64 - problem not exists
In debian9 - kernel 3.16.0-11-amd64 - problem not exists

storage mount from storage NetApp

storage:/vmail on /vmail type nfs
(rw,noexec,noatime,vers=3,rsize=65536,wsize=65536,namlen=255,acregmin=120,acregmax=120,acdirmin=120,acdirmax=120,hard,nocto,nordirplus,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=10.19.19.19,mountvers=3,mountport=635,mountproto=tcp,local_lock=none,addr=10.19.19.19)

cat /etc/fstab
storage:/vmail    /vmail    nfs   
rw,sec=sys,noexec,noatime,tcp,hard,rsize=65536,wsize=65536,intr,nordirplus,nfsvers=3,tcp,actimeo=120,nocto
   
0    0

Probably somthing in kernel or mount options. Any idea ?



Error: Mailbox INBOX: Broken file dovecot-uidlist: Invalid data

2019-10-29 Thread Dirk via dovecot
Hi list,

today a user reported messages are disappearing from his INBOX and I discovered 
a two digit number of mailboxes with broken dovecot-uidlist files.

The log says:

Oct 29 08:51:34 mail02 dovecot: 
lmtp(i...@example.com)<5270>: Error: Mailbox INBOX: 
Broken file /var/vmail/example.com/info/dovecot-uidlist line 88: Invalid data:

And the respective files do look broken:

4596 :1572344253.M529133P14861.mail03.example.com,S=53053,W=54233
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@4597
 :1572344797.M93833P15905.mail03.example.com,S=126866,W=129256

Setup : Behind a director I am running two dovecot backend servers sharing the 
vmail directory via NFS.

Do you have an idea where this might come from? How can I debug this further?

Cheers,
Dirk



Re: dovecot-uidlist invalid data

2019-08-14 Thread Timo Sirainen via dovecot
On 4 Aug 2019, at 22.57, Király Balázs via dovecot  wrote:
> 
> Hi!
>  
> I’m struggling with the following error: 
>  
> Aug  4 21:32:00 mx02 dovecot: imap(x...@xxx.tld)<17693>: 
> Error: Mailbox INBOX: Broken file /home/vmail/xxx.tld/xxx/dovecot-uidlist 
> line 6246: Invalid data:
> Aug  4 21:49:22 mx02 dovecot: imap(x...@xxx.tld)<21879>: 
> Error: Mailbox INBOX: Broken file /home/vmail/xxx.tld/xxx/dovecot-uidlist 
> line 6249: Invalid data:
>  
> It seems the first part is not incremented properly and sometimes it has a 
> jump in it, like the line 6246:
>  
> 18810 :1564935891.M816284P8904.mx01.m.ininet.hu,S=12145,W=12409
> 18812 :1564947092.M542714P2651.mx01.m.ininet.hu,S=12275,W=12517

Is there ever anything after the "Invalid data:" text? It seems anyway that 
concurrent reading/writing isn't working as expected in dovecot-uidlist. Most 
likely something to do with NFS.

Can you reproduce this easily by just running "imaptest" with some test account 
(it'll delete mails)? See https://imapwiki.org/ImapTest - it's also available 
in dovecot-imaptest package in repo.dovecot.org.



dovecot-uidlist invalid data

2019-08-04 Thread Király Balázs via dovecot
Hi!

 

I'm struggling with the following error: 

 

Aug  4 21:32:00 mx02 dovecot: imap(x...@xxx.tld)<17693>:
Error: Mailbox INBOX: Broken file /home/vmail/xxx.tld/xxx/dovecot-uidlist
line 6246: Invalid data:

Aug  4 21:49:22 mx02 dovecot: imap(x...@xxx.tld)<21879>:
Error: Mailbox INBOX: Broken file /home/vmail/xxx.tld/xxx/dovecot-uidlist
line 6249: Invalid data:

 

It seems the first part is not incremented properly and sometimes it has a
jump in it, like the line 6246:

 

18810 :1564935891.M816284P8904.mx01.m.ininet.hu,S=12145,W=12409

18812 :1564947092.M542714P2651.mx01.m.ininet.hu,S=12275,W=12517

 

Even though I deleted all the dovecot* files the error comes back. I have
the maildirs through NFS, but I set to store the INDEX files locally. 

 

I have failover configuration, that means when one of my servers die another
one takes the active IP and start to serve dovecot users, so its always one
server that serves all the users, no load balacing.

 

Any idea what am I missing or how could I fixed this problem?

 

uname -a

Linux mx02.m.mydomain.tld 4.19.0-5-amd64 #1 SMP Debian 4.19.37-5
(2019-06-19) x86_64 GNU/Linux

 

dovecot -n

# 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf

# Pigeonhole version 0.5.4 ()

# OS: Linux 4.19.0-5-amd64 x86_64 Debian 10.0 nfs

# Hostname: mx02.m.mydomain.tld

auth_mechanisms = plain login

auth_verbose = yes

default_client_limit = 1

default_process_limit = 1000

dict {

  quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext

}

disable_plaintext_auth = no

mail_fsync = always

mail_location = maildir:/home/vmail/%d/%n:INDEX=/var/indexes/%d/%n

mail_plugins = " quota"

mail_privileged_group = mail

mmap_disable = yes

namespace inbox {

  inbox = yes

  location =

  mailbox Drafts {

auto = subscribe

special_use = \Drafts

  }

  mailbox Sent {

auto = subscribe

   special_use = \Sent

  }

  mailbox "Sent Messages" {

special_use = \Sent

  }

  mailbox Spam {

auto = subscribe

special_use = \Junk

  }

  mailbox Trash {

auto = subscribe

special_use = \Trash

  }

  prefix = INBOX.

  separator = .

  type = private

}

passdb {

  args = /etc/dovecot/dovecot-sql.conf.ext

  driver = sql

}

plugin {

  quota = dict:User quota::proxy::quota

  sieve = /home/vmail/default.sieve

  sieve_default = /home/vmail/default.sieve

  sieve_extensions = +editheader

  sieve_global_dir = /var/lib/dovecot/sieve

}

protocols = " imap pop3"

service auth-worker {

  user = vmail

}

service auth {

  unix_listener /var/spool/postfix/private/auth {

group = postfix

mode = 0660

user = postfix

  }

  unix_listener auth-userdb {

mode = 0600

user = vmail

  }

  user = $default_internal_user

}

service dict {

  unix_listener dict {

group = vmail

mode = 0600

user = vmail

  }

}

service imap-login {

  inet_listener imaps {

port = 993

ssl = yes

  }

}

service imap {

  process_limit = 1024

}

service pop3 {

  process_limit = 1024

}

service stats {

  unix_listener stats-reader {

group = vmail

mode = 0660

user = vmail

  }

  unix_listener stats-writer {

group = vmail

mode = 0660

user = vmail

  }

}

ssl_cert =