[Dovecot] mail_log_events, but who exactly triggered events?
Hi. mail_log_events is nice addition but how to log who exactly triggered particular event? For example 5 users from 5 IP addresses uses single imap user/mailbox. One of them deletes email and I'm logging delete related events. The only logged thing is: dovecot: imap(user): delete: box=INBOX, uid=673287, msgid=some@thing, size=1230 which tells me nothing about who triggered it actually (note all 5 users were logged in at deletion time) How to solve this problem? Thanks, -- Arkadiusz Miśkiewicz, arekm / maven.pl
Re: [Dovecot] mail_log_events, but who exactly triggered events?
Am 30.01.2014 10:50, schrieb Arkadiusz Miśkiewicz: mail_log_events is nice addition but how to log who exactly triggered particular event? For example 5 users from 5 IP addresses uses single imap user/mailbox. One of them deletes email and I'm logging delete related events. The only logged thing is: dovecot: imap(user): delete: box=INBOX, uid=673287, msgid=some@thing, size=1230 which tells me nothing about who triggered it actually (note all 5 users were logged in at deletion time) How to solve this problem? do not share user-logins don't do that for any service, not only mail that's why ACL / shared mailboxes exists because in that case you have the unique username in the logs instead always the same one signature.asc Description: OpenPGP digital signature
Re: [Dovecot] New global ACL mailbox pattern feature in HG
* Thomas Leuxner t...@leuxner.net 2014.01.28 08:29:
$ cat global-acl
INBOX owner lrwstiekxap
Public* group=PublicMailboxAdmins lrwsik
Following up on this, there seems to be an issue with separators. Mailbox
creation crashes, while it used to work fine with the same configuration w/o
the 'global-acl' file. Interestingly enough same syntax works for the public
namespace (e.g. mailbox create -u t...@leuxner.net Public/Test ):
$ doveadm acl get -u t...@leuxner.net INBOX
IDGlobal Rights
owneradmin create delete expunge insert lookup post read write
write-deleted write-seen
$ doveadm mailbox create -u t...@leuxner.net Shops/Test
doveadm(t...@leuxner.net): Panic: file acl-global-file.c: line 163
(acl_global_file_find_rights): assertion failed: (file-last_refresh_time != 0)
doveadm(t...@leuxner.net): Error: Raw backtrace:
/usr/lib/dovecot/libdovecot.so.0(+0x6b34f) [0x7f7de43bf34f] -
/usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x2a) [0x7f7de43bf42a]
- /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f7de4378e8e] -
/usr/lib/dovecot/modules/lib01_acl_plugin.so(+0xc692) [0x7f7de3799692] -
/usr/lib/dovecot/modules/lib01_acl_plugin.so(acl_global_file_have_any+0x1a)
[0x7f7de3799bfa] - /usr/lib/dovecot/modules/lib01_acl_plugin.so(+0x9f92)
[0x7f7de3796f92] -
/usr/lib/dovecot/modules/lib01_acl_plugin.so(acl_mailbox_list_have_right+0xed)
[0x7f7de379c44d] - /usr/lib/dovecot/modules/lib01_acl_plugin.so(+0xda69)
[0x7f7de379aa69] - /usr/lib/dovecot/libdovecot-storage.so.0(+0x93027)
[0x7f7de46bc027] -
/usr/lib/dovecot/libdovecot-storage.so.0(mailbox_create+0x38) [0x7f7de46aa048]
- doveadm() [0x418124] - doveadm() [0x41358d] -
doveadm(doveadm_mail_try_run+0x251) [0x414251] - doveadm(main+0x3c8)
[0x413138] - /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)
[0x7f7de3fe8ead] - doveadm() [0x413351]
Aborted
namespace {
list = yes
location = mdbox:/var/vmail/public:INDEXPVT=~/mdbox/public
prefix = Public/
separator = /
subscriptions = no
type = public
}
namespace inbox {
hidden = no
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
mailbox Sent {
special_use = \Sent
}
mailbox Sent Messages {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
prefix =
separator = /
type = private
}
signature.asc
Description: Digital signature
Re: [Dovecot] mail_log_events, but who exactly triggered events?
On Thursday 30 of January 2014, Reindl Harald wrote: Am 30.01.2014 10:50, schrieb Arkadiusz Miśkiewicz: mail_log_events is nice addition but how to log who exactly triggered particular event? For example 5 users from 5 IP addresses uses single imap user/mailbox. One of them deletes email and I'm logging delete related events. The only logged thing is: dovecot: imap(user): delete: box=INBOX, uid=673287, msgid=some@thing, size=1230 which tells me nothing about who triggered it actually (note all 5 users were logged in at deletion time) How to solve this problem? do not share user-logins I'm not sharing. Customers are. don't do that for any service, not only mail That impossible to make. Customer creates login abc on my server and gives it to 10 employees to watch that mailbox. 10 employees log in to that single accound and do some actions. One of them is bad and deletes important mail. I want to be able to figure which one. I have no control over customers. Also I see no sensible reason to disallow such work style. that's why ACL / shared mailboxes exists because in that case you have the unique username in the logs instead always the same one When customers log in: dovecot: pop3-login: Login: user=someone1, method=PLAIN, rip=xxx, lip=yyy, mpid=11680, session=MR9D9y3xhwBb6rD1 dovecot: imap-login: Login: user=someone2, method=PLAIN, rip=aaa, lip=yyy, mpid=11682, TLS, session=U1lD9y3xoQBPuvZx session id is logged. Now how to get that id logged in mail_log_events lines? -- Arkadiusz Miśkiewicz, arekm / maven.pl
[Dovecot] Is replication broken?
Hi,
Apologies for this being my 248th post about replication...
The current error I'm getting is:
Jan 30 12:10:54 Server1 dovecot: dsync-local(MailUser1): Error: dsync(
Server2.test.com): read() failed: read((fd)) failed: Connection reset by
peer
Subsequent errors are:
Jan 30 12:15:47 Server1 dovecot: dsync-local(MailUser1): Error: read(
Server2.test.com) failed: EOF
The above error is seen on Server1, after the initial sync completes of the
first mailbox (Sent folder to be precise).
Does anyone have an ideas as to what might be causing it? These are brand
new rebuilds, running the latest build - I just can't seem to get this
working.
Bug maybe?
Configs are as follows:
Server1:
# 2.2.10: /usr/pkg/etc/dovecot/dovecot.conf
# OS: NetBSD 5.2 cobalt
auth_mechanisms = plain login
doveadm_password = secret
doveadm_port = 12345
first_valid_uid = 1003
last_valid_uid = 1020
listen = 192.168.1.1
login_greeting = test.com
mail_location = mbox:~/mail:INBOX=/var/mail/%u
mail_plugins = notify replication
passdb {
driver = passwd
}
plugin {
mail_replica = tcp:Server2.test.com
}
protocols = imap
service aggregator {
fifo_listener replication-notify-fifo {
mode = 0666
}
unix_listener replication-notify {
mode = 0600
}
}
service auth {
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
}
user = root
}
service imap-login {
inet_listener imap {
port = 0
}
}
service replicator {
process_min_avail = 1
unix_listener replicator-doveadm {
mode = 0600
}
}
ssl_cert = /etc/openssl/certs/Server1.test.crt
ssl_key = /etc/openssl/private/Server1.test.key
userdb {
driver = passwd
}
protocol lda {
postmaster_address = postmas...@test.com
}
ServerB:
# 2.2.10: /usr/pkg/etc/dovecot/dovecot.conf
# OS: NetBSD 5.1 cobalt
auth_mechanisms = plain login
doveadm_password = secret
doveadm_port = 12345
listen = 192.168.1.2
login_greeting = test.com
mail_location = mbox:~/mail:INBOX=/var/mail/%u
passdb {
driver = passwd
}
protocols = imap
service aggregator {
fifo_listener replication-notify-fifo {
mode = 0666
}
unix_listener replication-notify {
mode = 0600
}
}
service auth {
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
}
user = root
}
service doveadm {
inet_listener {
port = 12345
}
}
service imap-login {
inet_listener imap {
port = 0
}
}
service replicator {
process_min_avail = 1
unix_listener replicator-doveadm {
mode = 0600
}
}
ssl_cert = /etc/openssl/certs/Server2.test.com.crt
ssl_key = /etc/openssl/private/Server2.test.com.key
userdb {
driver = passwd
}
protocol lda {
postmaster_address = postmas...@test.com
}
Re: [Dovecot] mail_log_events, but who exactly triggered events?
Am 30.01.2014 12:04, schrieb Arkadiusz Miśkiewicz: On Thursday 30 of January 2014, Reindl Harald wrote: Am 30.01.2014 10:50, schrieb Arkadiusz Miśkiewicz: mail_log_events is nice addition but how to log who exactly triggered particular event? For example 5 users from 5 IP addresses uses single imap user/mailbox. One of them deletes email and I'm logging delete related events. The only logged thing is: dovecot: imap(user): delete: box=INBOX, uid=673287, msgid=some@thing, size=1230 which tells me nothing about who triggered it actually (note all 5 users were logged in at deletion time) How to solve this problem? do not share user-logins I'm not sharing. Customers are. don't do that for any service, not only mail That impossible to make. Customer creates login abc on my server and gives it to 10 employees to watch that mailbox. 10 employees log in to that single accound and do some actions. One of them is bad and deletes important mail. I want to be able to figure which one. I have no control over customers. Also I see no sensible reason to disallow such work style than your answer to them is simply i can't tell who did what as long they insist on that work style - how is that your problem? signature.asc Description: OpenPGP digital signature
Re: [Dovecot] mail_log_events, but who exactly triggered events?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 30 Jan 2014, Reindl Harald wrote: Am 30.01.2014 12:04, schrieb Arkadiusz Miśkiewicz: On Thursday 30 of January 2014, Reindl Harald wrote: Am 30.01.2014 10:50, schrieb Arkadiusz Miśkiewicz: mail_log_events is nice addition but how to log who exactly triggered particular event? For example 5 users from 5 IP addresses uses single imap user/mailbox. One of them deletes email and I'm logging delete related events. The only logged thing is: dovecot: imap(user): delete: box=INBOX, uid=673287, msgid=some@thing, size=1230 which tells me nothing about who triggered it actually (note all 5 users were logged in at deletion time) How to solve this problem? do not share user-logins I'm not sharing. Customers are. don't do that for any service, not only mail That impossible to make. Customer creates login abc on my server and gives it to 10 employees to watch that mailbox. 10 employees log in to that single accound and do some actions. One of them is bad and deletes important mail. I want to be able to figure which one. I have no control over customers. Also I see no sensible reason to disallow such work style than your answer to them is simply i can't tell who did what as long they insist on that work style - how is that your problem? (Y) @Arkadiusz, please tell us, if 10 people use the same account name and password, how would you as a server behind the internet with a human brain differ those 10 individuals? The only idea I, personally, have is the IP address: Do they connect from different IP addresses _all_ the time? No NAT involved? Do you know who uses which IP address _all_ the time? If so, Dovecot logs the IP address during login and you can associate a PID with an IP address, IMHO you can add the remote IP address to the log string. Check out the variables page in the Wiki. But, frankly, _if_ you have someone, who is bad and deletes important mail, you should see sensible reason to disallow such work style. The next time you see yet another IP address and don't know the user again. - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUuo7dXD1/YhP6VMHAQJdBAf8CEvum1A4mZsCj2I1bJbEalvNupHJl6UQ SwXmpXa42ldOcg5UDbUG6Xy/PyBzHjGGwFsCA6feFBwDoigM9M0kXJNFw5gfrmk5 cUzAQVEMHGrWNDD/fj9I/7JmBds8/bO7sziPPwwnNtlzva98dwG9RlNdFF09+FcR TxHq9q8RRgFtWKvh0LtmIcGdJ3+YDTA4I/pZKGKeVXLnsb8+4f1Ep0W2PSMg75Dy nZ82+CKTwgzROrCMEdAFhIYJTJMDmVd939539Dexp94KsuPhkIKEF59q4NOfvZ0V OLiymyCGf3DgeCySxONU/E55ihD3RTQX3wmNk10rNOPAKD3Tg4kP0g== =6ok/ -END PGP SIGNATURE-
Re: [Dovecot] Is replication broken?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 30 Jan 2014, IT geek 31 wrote: Apologies for this being my 248th post about replication... The current error I'm getting is: Jan 30 12:10:54 Server1 dovecot: dsync-local(MailUser1): Error: dsync( Server2.test.com): read() failed: read((fd)) failed: Connection reset by peer this is a generic network error: http://stackoverflow.com/questions/1434451/what-does-connection-reset-by-peer-mean The other side of the communication channel closed the connection. It also does not neccessarily mean that other end point did it, but it could be a firewall, router, whatever in between as well. - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUuo9BHD1/YhP6VMHAQLnZgf+LZPlLEvqf1RKui2tf3/a6w1u5pk9E0I2 k9fy4GRGCLQzrEhr0X2ayCyZmr6gLrfcqB1txwrlNw/YfZ/TpQwVIfCwQZOiDw49 Yr2sPP8tZtWqX4Ebk4L0577m9kscG3Hf2vWEP+t/m9RDUztGAEUweZvmMYOazk1p J5RQI1iAA0AnJesRL89xHv3c9cjCFCMrNs6V0nWpa+bPYbntq5NHB2nESZaifjWL 5dAMOevek/P0QGFrkHA1cLAaOe7qtJwdkOZ8eShXaIm+qPtrsSTZdSsi0dzC4DgU 612St0YTcfpcLnkYBLV14HlcuGaUA33kEnRt/ICVvE5fNRLyHrCFlA== =WeHN -END PGP SIGNATURE-
Re: [Dovecot] Is replication broken?
Hi Steffen, Thanks for getting back to me. Do you know why I am now getting: Jan 30 12:50:43 Server1 dovecot: dsync-local(MailUser1): Error: read( Server2.test.com) failed: EOF Thanks, On 30 January 2014 12:52, Steffen Kaiser skdove...@smail.inf.fh-brs.dewrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 30 Jan 2014, IT geek 31 wrote: Apologies for this being my 248th post about replication... The current error I'm getting is: Jan 30 12:10:54 Server1 dovecot: dsync-local(MailUser1): Error: dsync( Server2.test.com): read() failed: read((fd)) failed: Connection reset by peer this is a generic network error: http://stackoverflow.com/questions/1434451/what-does- connection-reset-by-peer-mean The other side of the communication channel closed the connection. It also does not neccessarily mean that other end point did it, but it could be a firewall, router, whatever in between as well. - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUuo9BHD1/YhP6VMHAQLnZgf+LZPlLEvqf1RKui2tf3/a6w1u5pk9E0I2 k9fy4GRGCLQzrEhr0X2ayCyZmr6gLrfcqB1txwrlNw/YfZ/TpQwVIfCwQZOiDw49 Yr2sPP8tZtWqX4Ebk4L0577m9kscG3Hf2vWEP+t/m9RDUztGAEUweZvmMYOazk1p J5RQI1iAA0AnJesRL89xHv3c9cjCFCMrNs6V0nWpa+bPYbntq5NHB2nESZaifjWL 5dAMOevek/P0QGFrkHA1cLAaOe7qtJwdkOZ8eShXaIm+qPtrsSTZdSsi0dzC4DgU 612St0YTcfpcLnkYBLV14HlcuGaUA33kEnRt/ICVvE5fNRLyHrCFlA== =WeHN -END PGP SIGNATURE-
Re: [Dovecot] Is replication broken?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 30 Jan 2014, IT geek 31 wrote: On 30 January 2014 12:52, Steffen Kaiser skdove...@smail.inf.fh-brs.dewrote: On Thu, 30 Jan 2014, IT geek 31 wrote: Apologies for this being my 248th post about replication... The current error I'm getting is: Jan 30 12:10:54 Server1 dovecot: dsync-local(MailUser1): Error: dsync( Server2.test.com): read() failed: read((fd)) failed: Connection reset by peer this is a generic network error: http://stackoverflow.com/questions/1434451/what-does- connection-reset-by-peer-mean The other side of the communication channel closed the connection. It also does not neccessarily mean that other end point did it, but it could be a firewall, router, whatever in between as well. Do you know why I am now getting: Jan 30 12:50:43 Server1 dovecot: dsync-local(MailUser1): Error: read( Server2.test.com) failed: EOF First you get Connection reset by peer, the system closes the file descriptot, Dovecot reads further from the handle and gets EOF. It's a subsequent error, IMHO. - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUupTvXD1/YhP6VMHAQJxAggAyeX8kLK1AaoTsGPzIFfVW9GZKKF/eMpT kgzL1UlY86ht0N3c2mvcOLBqjV15QSjNLaAV7wN4wPflMeescLScPUga21hrKKJV 077T8ggLZE8Du6qTrkGej48/g6SdE/ZuyKiG/h/7s9OcdHJXHSIaqzVL7i+SNRmp g0lo2n0axIk9M1mLLHw3SbbKEN1kDcrOGtdqh2Pl2wohLWNTJ+ZN1YpcBzJgOlq2 hIQeuVqvUXHLP8/S7CFngPVeZM+Kxr12HpOOt95/eqf4VEhyF1C1KXFVUXMbGkfX +6bifTBkoGIzwznGHOIsigmJWrk9a7RM0rk5stFLvyGfdjxyN0VYCg== =HOzr -END PGP SIGNATURE-
Re: [Dovecot] Is replication broken?
Okay.. so how do I fix it? :-)
Here are the errors on the remote server (the last two are a different
mailbox!):
Jan 30 13:25:16 Server2 dovecot: dsync-server(MailUser1): Panic: file
mbox-lock.c: line 799 (mbox_lock): assertion failed: (lock_type == F_RDLCK
|| mbox-mbox_lock_type != F_RDLCK)
Jan 30 13:25:16 Server2 dovecot: dsync-server(MailUser1): Fatal: master:
service(doveadm): child 26627 killed with signal 6 (core not dumped - set
service doveadm { drop_priv_before_exec=yes })
Jan 30 13:25:17 Server2 dovecot: dsync-server(MailUser2): Error:
net_connect_unix(/var/run/dovecot/replicator-doveadm) failed: Permission
denied
Jan 30 13:25:51 Server2 dovecot: dsync-server(MailUser2): Error: Sync
failed for mbox file /var/mail/mark: UID inserted in the middle of mailbox
(334045 328601, seq=8220, idx_msgs=16554)
Any help is appreciated.
On 30 January 2014 14:29, Steffen Kaiser skdove...@smail.inf.fh-brs.dewrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 30 Jan 2014, IT geek 31 wrote:
On 30 January 2014 12:52, Steffen Kaiser skdove...@smail.inf.fh-brs.de
wrote:
On Thu, 30 Jan 2014, IT geek 31 wrote:
Apologies for this being my 248th post about replication...
The current error I'm getting is:
Jan 30 12:10:54 Server1 dovecot: dsync-local(MailUser1): Error: dsync(
Server2.test.com): read() failed: read((fd)) failed: Connection reset
by
peer
this is a generic network error:
http://stackoverflow.com/questions/1434451/what-does-
connection-reset-by-peer-mean
The other side of the communication channel closed the connection. It
also
does not neccessarily mean that other end point did it, but it could be a
firewall, router, whatever in between as well.
Do you know why I am now getting:
Jan 30 12:50:43 Server1 dovecot: dsync-local(MailUser1): Error: read(
Server2.test.com) failed: EOF
First you get Connection reset by peer, the system closes the file
descriptot, Dovecot reads further from the handle and gets EOF. It's a
subsequent error, IMHO.
- -- Steffen Kaiser
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
iQEVAwUBUupTvXD1/YhP6VMHAQJxAggAyeX8kLK1AaoTsGPzIFfVW9GZKKF/eMpT
kgzL1UlY86ht0N3c2mvcOLBqjV15QSjNLaAV7wN4wPflMeescLScPUga21hrKKJV
077T8ggLZE8Du6qTrkGej48/g6SdE/ZuyKiG/h/7s9OcdHJXHSIaqzVL7i+SNRmp
g0lo2n0axIk9M1mLLHw3SbbKEN1kDcrOGtdqh2Pl2wohLWNTJ+ZN1YpcBzJgOlq2
hIQeuVqvUXHLP8/S7CFngPVeZM+Kxr12HpOOt95/eqf4VEhyF1C1KXFVUXMbGkfX
+6bifTBkoGIzwznGHOIsigmJWrk9a7RM0rk5stFLvyGfdjxyN0VYCg==
=HOzr
-END PGP SIGNATURE-
Re: [Dovecot] Is replication broken?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 30 Jan 2014, IT geek 31 wrote:
Here are the errors on the remote server (the last two are a different
mailbox!):
Jan 30 13:25:16 Server2 dovecot: dsync-server(MailUser1): Panic: file
mbox-lock.c: line 799 (mbox_lock): assertion failed: (lock_type == F_RDLCK
|| mbox-mbox_lock_type != F_RDLCK)
Jan 30 13:25:16 Server2 dovecot: dsync-server(MailUser1): Fatal: master:
service(doveadm): child 26627 killed with signal 6 (core not dumped - set
service doveadm { drop_priv_before_exec=yes })
follow the advice, set ulimit -c unlimited, get a core dump, then
gdb /usr/.../binary core
bt full
post the output and use some subject line, e.g.
dsync-server(MailUser1): Panic: file mbox-lock.c: line 799 with coredump
to get Timos attension, that you have information for the panic.
Any help is appreciated.
provide Timo any information about the core dump, give it an useful title,
e.g. BUG Panic: file mbox-lock.c: with backtrace to catch his attention
during his busy phases of work. Bumping the subject is not useful.
I found only this:
http://thr3ads.net/dovecot/2013/05/2645571-dsync-assert-failure-in-2.2.2
which says Appears to work properly again in 2.2.4..
On 30 January 2014 14:29, Steffen Kaiser skdove...@smail.inf.fh-brs.dewrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 30 Jan 2014, IT geek 31 wrote:
On 30 January 2014 12:52, Steffen Kaiser skdove...@smail.inf.fh-brs.de
wrote:
On Thu, 30 Jan 2014, IT geek 31 wrote:
Apologies for this being my 248th post about replication...
The current error I'm getting is:
Jan 30 12:10:54 Server1 dovecot: dsync-local(MailUser1): Error: dsync(
Server2.test.com): read() failed: read((fd)) failed: Connection reset
by
peer
this is a generic network error:
http://stackoverflow.com/questions/1434451/what-does-
connection-reset-by-peer-mean
The other side of the communication channel closed the connection. It
also
does not neccessarily mean that other end point did it, but it could be a
firewall, router, whatever in between as well.
Do you know why I am now getting:
Jan 30 12:50:43 Server1 dovecot: dsync-local(MailUser1): Error: read(
Server2.test.com) failed: EOF
First you get Connection reset by peer, the system closes the file
descriptot, Dovecot reads further from the handle and gets EOF. It's a
subsequent error, IMHO.
- -- Steffen Kaiser
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
iQEVAwUBUupTvXD1/YhP6VMHAQJxAggAyeX8kLK1AaoTsGPzIFfVW9GZKKF/eMpT
kgzL1UlY86ht0N3c2mvcOLBqjV15QSjNLaAV7wN4wPflMeescLScPUga21hrKKJV
077T8ggLZE8Du6qTrkGej48/g6SdE/ZuyKiG/h/7s9OcdHJXHSIaqzVL7i+SNRmp
g0lo2n0axIk9M1mLLHw3SbbKEN1kDcrOGtdqh2Pl2wohLWNTJ+ZN1YpcBzJgOlq2
hIQeuVqvUXHLP8/S7CFngPVeZM+Kxr12HpOOt95/eqf4VEhyF1C1KXFVUXMbGkfX
+6bifTBkoGIzwznGHOIsigmJWrk9a7RM0rk5stFLvyGfdjxyN0VYCg==
=HOzr
-END PGP SIGNATURE-
- --
Steffen Kaiser
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.11 (GNU/Linux)
iQEVAwUBUupbcXD1/YhP6VMHAQIPvwgAt/vLcy5rW9CuUIWuePrK4X3lr9930YM4
A1gs57G++lLEWkJAYN5uxQ/rODbluAq+7yXfR6HUoeOQu+ZCuxIjSnG5Dqo9iwYE
eJudAOs7oJIEBASfv3EaYtCCh44M8sZ6u+Y0+VFnNUbpqmr2hQn+OL67srsqnCFQ
J3xFEHFvdyLK8QrIhtMucSYh6KwmmPjKRNCy6/L71aq7ZCEfG0UR55gnv7XQ/BDF
kfTaC1pRUcZImO2WyTDwD8jXFjIhoH5bBiEbh7z2EKoKborpLK/hnSSpLvfhBZwf
A09Ep4fXP/wFmXuDsbrWyc4BZVl1a76Nq21IOPtTL5foP8SjALQHRg==
=PxdB
-END PGP SIGNATURE-
Re: [Dovecot] Dsync Errors
Maybe this error sheds some light on it: Panic: file dsync-brain-mailbox-tree-sync.c: line 111 (dsync_brain_mailbox_tree_sync_change): assertion failed: (brain-no_backup_overwrite)
Re: [Dovecot] Dsync Errors
I see Timo addressed this problem with this reply ( from thread [Dovecot] reproducible dsync backup panic (dovecot 2.2.7)/Fri Dec 20 00:37:21 EET 2013)/, but basically I don't understand how to go about doing this: Can you get it to dump core and use gdb /usr/bin/doveadm core bt full fr 5 p *change / The command I'm using to back up individual user's mail is something like: // // sudo -u vmail dsync -v -uuser at server.com http://dovecot.org/cgi-bin/mailman/listinfo/dovecot -R backup ssh -i sshid-filelogin at server.com http://dovecot.org/cgi-bin/mailman/listinfo/dovecot sudo -u vmail dsync -v -uuser at server.com http://dovecot.org/cgi-bin/mailman/listinfo/dovecot / Probably an easier way would be if you could copy the local and remote mdboxes to e.g. /tmp/mdbox-local and /tmp/mdbox-remote. Then you should be able to do: gdb --args doveadm -o mail=mdbox:/tmp/mdbox-local backup -R mdbox:/tmp/mdbox-remote run bt full fr 5 p *change
Re: [Dovecot] possible quota bug ?
I was researching deeper this issue, activated debug logs and when I move a message from one folder to another the message size is different Jan 30 18:48:07 imap(xxx@xxx): Info: copy from INBOX: box=INBOX.Sent, uid=17, msgid=5520ed0fedee4e3386d08c98d249a...@lab.imap, size=1048 Jan 30 18:48:07 imap(xxx@xxx): Info: expunge: box=INBOX, uid=3, msgid=5520ed0fedee4e3386d08c98d249a...@lab.imap, size=1898 This is exactly the sizes I see in the maildirsize. But I think these values should be equals. 1073741824S 2136 1 1048 1 -1898 -1 Att Fernando De: fernando.fig...@uol.com.br Enviada: Quarta-feira, 15 de Janeiro de 2014 15:11 Para: dovecot@dovecot.org Assunto: [Dovecot] possible quota bug ? Hi, I'm using dovecot 2.2.5 with quota (maildir backend), zlib and expunge plugins. When I list maildirsize file, I get: 1073741824S 17952 16 If I receive a new message (example: 1204 bytes compressed and 2524 bytes plain text), the quota file is write correctly (2524 1 entry). When I move the message to trash folder (or between user custom folders) the file have wrong entries: 1073741824S 17952 16 2524 1 1204 1 (this is the size of the compressed message) -2524 -1 I coudn't find any relation with the config settings causing this problem and checked the changelog since 2.2.5. Had someone had this same problem? Thanks, Fernando
