Ok (My Opinion Only)
NFS in general does not work well on active servers, although dovecot
allows for various locking mech's they do generally trip over each other.
This occurs on NFS mounts using a single server and just goes down hill
from there if you have 2 servers talking to the same NFS file mount.
Simply put its a crap shoot what will work and when
I know this is a touchy subject but this is what replication was used
for and works well between 2 or more servers updating email boxes in
real time
It does require a proper database (MySql or Postgresql) and prefereably
a dedicated private network between the two mail servers running dovecot.
I tried everything noted in this post and it just does not work.
Have A Happy Monday !!!
Thanks - Paul Kudla (Manager SCOM.CA Internet Services Inc.)
Scom.ca Internet Services <http://www.scom.ca>
004-1009 Byron Street South
Whitby, Ontario - Canada
L1N 4S3
Toronto 416.642.7266
Main 1.866.411.7266
Fax 1.888.892.7266
Email p...@scom.ca
On 11/6/2023 9:54 AM, Aki Tuomi via dovecot wrote:
On 06/11/2023 16:48 EET lejeczek via dovecot <dovecot@dovecot.org> wrote:
Hi guys.
I see that with mailboxes stored on a network mount-point
and more than one box with Dovecot using such a mailbox,
Dovecots step on each others toes.
...
lmtp(minem...@lemko.xyz)<2674357><uATxGqbaSGW1zigAn4O9eQ>:
Error: lmtp-server: conn unix:pid=2600068,uid=89 [2]: rcpt
minemail@my.private: Mailbox INBOX: Corrupted transaction
log file /VMAIL/my.private/minemail/dovecot.index.log seq 4:
ext intro: name_size too large (sync_offset=6368)
...
Above happened if the same one user was having mail
delivered on two Postfix+Dovecot servers at the same time.
I hope experts who know Dovecot's internals better can tell...
having such multiple node/server Dovecots "talking" to that
same network mount-point but!..
only one Dovecot being active - having Postfix using it
and other, however many, Dovecots only "idling" - not having
Postifx using it (+ no client connections is a goal too)
Would that make such multi-Dovecot setup safe & free from
errors as above & any storage related ones?
Or perhaps there are other ways to have many Dovecots with
the same user-base, using same networked storage simultaneously?
many thanks, L.
Hi guys.
I see that with mailboxes stored on a network mount-point and more than one box
with Dovecot using such a mailbox, Dovecots step on each others toes.
...
lmtp(minem...@lemko.xyz)<2674357><uATxGqbaSGW1zigAn4O9eQ>: Error: lmtp-server:
conn unix:pid=2600068,uid=89 [2]: rcpt minemail@my.private: Mailbox INBOX:
Corrupted transaction log file /VMAIL/my.private/minemail/dovecot.index.log seq
4: ext intro: name_size too large (sync_offset=6368)
...
Above happened if the same one user was having mail delivered on two
Postfix+Dovecot servers at the same time.
I hope experts who know Dovecot's internals better can tell...
having such multiple node/server Dovecots "talking" to that same network mount-
point but!..
only one Dovecot being active - having Postfix using it
and other, however many, Dovecots only "idling" - not having Postifx using it
(+ no client connections is a goal too)
Would that make such multi-Dovecot setup safe & free from errors as above & any
storage related ones?
Or perhaps there are other ways to have many Dovecots with the same user-base,
using same networked storage simultaneously?
many thanks, L.
Hi!
See https://doc.dovecot.org/configuration_manual/nfs/
This applies to other shared mountpoints too.
Aki
_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
_______________________________________________
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
