[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 = postmaster@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 = postmaster@test.com }
-----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-pee...
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-----
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 <skdovecot@smail.inf.fh-brs.de>wrote:
-----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-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 30 Jan 2014, IT geek 31 wrote:
On 30 January 2014 12:52, Steffen Kaiser <skdovecot@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-----
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 <skdovecot@smail.inf.fh-brs.de>wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 30 Jan 2014, IT geek 31 wrote:
On 30 January 2014 12:52, Steffen Kaiser <skdovecot@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-----
-----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 <skdovecot@smail.inf.fh-brs.de>wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Thu, 30 Jan 2014, IT geek 31 wrote:
On 30 January 2014 12:52, Steffen Kaiser <skdovecot@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-----
Timo wrote this last month:
mbox format + dsync replication apparently doesn't work because of lock ordering issues. Might not be easy to fix, or in any case it's pretty low priority for me for now.
Sorry for "bumping the subject" again but is there any chance this has moved up the priority list?
I don't know if anyone else feels the same... but replication is number one on our Christmas wish list right now :-)
-Mark
On 30 January 2014 15:02, Steffen Kaiser <skdovecot@smail.inf.fh-brs.de>wrote:
-----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 <skdovecot@smail.inf.fh-brs.de
wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 30 Jan 2014, IT geek 31 wrote:
On 30 January 2014 12:52, Steffen Kaiser <skdovecot@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-----
On 3/13/2014 10:55 AM, IT geek 31 <itgeek31@googlemail.com> wrote:
Timo wrote this last month:
mbox format + dsync replication apparently doesn't work because of lock ordering issues. Might not be easy to fix, or in any case it's pretty low priority for me for now.
Sorry for "bumping the subject" again but is there any chance this has moved up the priority list?
I don't know if anyone else feels the same... but replication is number one on our Christmas wish list right now :-)
I think Timo's point is the fact that this is strictly mbox related.
Maybe switch to mdbox is an option?
--
Best regards,
Charles
Oh agreed. I assumed that to be what he meant :-)
I'll have a hunt for a numpties guide for migrating from mbox to mdbox.
I found this:
http://wiki2.dovecot.org/Migration/MailFormat
But I think that is hinting at going mbox ---> Maildir ---> mdbox. Not ideal.
-Mark
On 13 March 2014 16:11, Charles Marcus <CMarcus@media-brokers.com> wrote:
On 3/13/2014 10:55 AM, IT geek 31 <itgeek31@googlemail.com> wrote:
Timo wrote this last month:
mbox format + dsync replication apparently doesn't work because of lock ordering issues. Might not be easy to fix, or in any case it's pretty low priority for me for now.
Sorry for "bumping the subject" again but is there any chance this has moved up the priority list?
I don't know if anyone else feels the same... but replication is number one on our Christmas wish list right now :-)
I think Timo's point is the fact that this is strictly mbox related.
Maybe switch to mdbox is an option?
--
Best regards,
Charles
On 3/13/2014 2:27 PM, IT geek 31 <itgeek31@googlemail.com> wrote:
I found this:
http://wiki2.dovecot.org/Migration/MailFormat
But I think that is hinting at going mbox ---> Maildir ---> mdbox. Not ideal.
Look at the three sentences directly before the examples there. It specifically says:
"With dsync you can convert between any two mailbox formats that Dovecot supports. As much of the mailbox state is preserved as possible. Typically it's everything. See Tools/Dsync <http://wiki2.dovecot.org/Tools/Dsync> for full documentation, here are only a couple of examples: "
So...
a) You can convert between ANY TWO mail,box formats
and
b) The following examples are ONLY TWO.
What you are supposed to do is extrapolate.
--
Best regards,
Charles
Look at the three sentences directly before the examples there. It specifically says:
"With dsync you can convert between any two mailbox formats that Dovecot supports. As much of the mailbox state is preserved as possible. Typically it's everything. See Tools/Dsync <http://wiki2.dovecot.org/Tools/Dsync> for full documentation, here are only a couple of examples: "
So...
a) You can convert between ANY TWO mail,box formats
and
b) The following examples are ONLY TWO.
What you are supposed to do is extrapolate.
Thank you for clearing that up for me.
It might have been quicker to type "Yeah buddy, it can convert any two mailbox formats". But hey, why be succinct when you can be patronising? :-)
I'll give it a whirl now.
Thanks,
-Mark
On 3/17/2014 8:50 AM, IT geek 31 <itgeek31@googlemail.com> wrote:
It might have been quicker to type "Yeah buddy, it can convert any two mailbox formats".
Actually, it would have been much quicker had you simply read the text that I ended up pointing out to you, without wasting everyone else's time making it painfully obvious that you didn't bother to actually read it.
But hey, why be succinct when you can be patronising?:-)
Actually asked another way, "why should I waste time rtfm when I can just be lazy and waste everyone else's time with questions that I could otherwise easily answer myself?"...
Sorry, but it is a pet peeve of mine when someone provides an answer that makes it painfully obvious that they didn't even *try* to answer the question themself.
Actually asked another way, "why should I waste time rtfm when I can just be lazy and waste everyone else's time with questions that I could otherwise easily answer myself?"...
Actually pal that's utter bollocks. I did RTFM, but I think it's widely recognised the Dovecot wiki (Replication especially) isn't as informative as it could be. If it was I wouldn't be asking for help.
Sorry, but it is a pet peeve of mine when someone provides an answer that makes it painfully obvious that they didn't even *try* to answer the question themself.
And that's fine. Despite your patronising tone, I appreciate you contribute heavily this thread and where you do offer help it is appreciated.
Look... I'm not looking for a spat here. This mailing list already has a few unhelpful toads without us adding to the list :-)
I plan to follow your advice and migrate a test mailbox to mdbox using the following command:
dsync -v -u username mirror mbox:~/mail:INBOX=/var/mail/username
And adding the following to my dovecot.conf:
mail_location = mdbox:~/mdbox
According to http://wiki2.dovecot.org/MailboxFormat/dbox, the Inbox will then be moved under $HOME:/mdbox/mailboxes/INBOX.
Before I do this, my question is this - will Postfix automatically know where to find the inbox, or will I have to do modify my Postfix config somehow?
Thanks,
-Mark
Before I do this, my question is this - will Postfix automatically know where to find the inbox, or will I have to do modify my Postfix config somehow?
To answer my own question, I have to edit my Postfix main.cf file with the following command:
mailbox_command = /usr/pkg/libexec/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT"
More info can be found here:
http://wiki2.dovecot.org/LDA/Postfix
I'm still having permission issues though:
(Command died with status 126: "/usr/pkg/libexec/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT"". Command output: sh: /usr/pkg/libexec/dovecot/dovecot-lda: permission denied )
More to follow.
-Mark
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On Wed, 2 Apr 2014, IT geek 31 wrote:
To answer my own question, I have to edit my Postfix main.cf file with the following command:
mailbox_command = /usr/pkg/libexec/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT"
More info can be found here:
http://wiki2.dovecot.org/LDA/Postfix
I'm still having permission issues though:
(Command died with status 126: "/usr/pkg/libexec/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT"". Command output: sh: /usr/pkg/libexec/dovecot/dovecot-lda: permission denied )
Honestly, for most setups I would recommend LMTP nowadays. I don't use Postfix, but that page looks good: http://wiki2.dovecot.org/HowTo/PostfixDovecotLMTP
You do not need to do anything special in postfix, if you use Dovecot's LDA or LMTP, when you change the storage backend. Most importantly, that way you can let UserDB return a different mail_location per recipient without postfix knowing anything about the difference.
BTW: If the Wiki seems missing information, add it once you've acquired the info. :-)
Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux)
iQEVAwUBUzz/pXD1/YhP6VMHAQID+ggAjib19D7JsUKKySdbj3bFx8NyEFmjexQI G3iwRBKnQYANp/KQdnJL+N0jnxmQNrl9MrjdciYxFO2dln0pcehz8QlsK6VGbIcf Lz0o5Ht7RMJD1kIxfeug+lIREqd5s7FJZ3JdZPkE/IfF/50cTJgL4G//KdA4wo1e s+5PHar+60eVo1BAMN/VK35jasI/JM7VCR8n86dsI2aJ6KNGqg8l6yaIVMKaqXUd +Hs1zYSDzL8PFLsrzTJLXKD9dHQiOqEnUhVfVyC951YyZVfp5HV/XxiP9QSXiU0h HtYcszoOPAfPW/MTld2BxmZ+UvaXHDEVe1GUtV1Y1rDfCiRQnXwPeg== =vfi7 -----END PGP SIGNATURE-----
On 30.1.2014, at 8.31, IT geek 31 <itgeek31@googlemail.com> wrote:
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)
mbox format + dsync replication apparently doesn't work because of lock ordering issues. Might not be easy to fix, or in any case it's pretty low priority for me for now.
participants (4)
-
Charles Marcus
-
IT geek 31
-
Steffen Kaiser
-
Timo Sirainen