Bugzilla

> AFAIK there are two mailbox formats: the mbox and maildir. 
The maildir is technically supported and even our default storage format, but I am pretty sure it diverged too far to be actually useful in such a setup.

> AFAIK inotify does not work for NFS but I may be wrong.
I am considering automatic fallback options, but you are free to disable the push and set any polling interval you like the standard way.

> As soon as Thundebird detects a new complete mail it should move it to the designated inbox (the global one in the simple setup) 
In my implementation, it is effectively a cross between a local folder and an account, but internally it is an account type and will show up by default as its own inbox as $username@$hostname, but can be renamed later.

> I suppose this "complete mail" requirement is a tricky one. Thunderbird should not start moving the mail as soon as it detects a mbox file modification (an IN_MODIFY event in inotify parlance). 
I am implementing the [standard locking mechanism](https://man.freebsd.org/cgi/man.cgi?query=mbox#end), I am not even sure whether there is a client widely disregarding that.

> As there is resource contention between movemail and mbox appending agents, some file locking mechanisms should be used but I don't know how well these work on network file systems.
I will make sure it works in the way FreeBSD describe it, but if Mutt can't handle it sanely, chances are neither will we.

Thank you so much for your input. 🤩

> AFAIK there are two mailbox formats: the mbox and maildir. 

The maildir is technically supported and even our default storage format, but I am pretty sure it diverged too far to be actually useful in such a setup.

> AFAIK inotify does not work for NFS but I may be wrong.

I am considering automatic fallback options, but you are free to disable the push and set any polling interval you like the standard way.

> As soon as Thundebird detects a new complete mail it should move it to the designated inbox (the global one in the simple setup) 

In my implementation, it is effectively a cross between a local folder and an account, but internally it is an account type and will show up by default as its own inbox as $username@$hostname, but can be renamed later.

> I suppose this "complete mail" requirement is a tricky one. Thunderbird should not start moving the mail as soon as it detects a mbox file modification (an IN_MODIFY event in inotify parlance). 

I am implementing the [standard locking mechanism](https://man.freebsd.org/cgi/man.cgi?query=mbox#end), I am not even sure whether there is a client widely disregarding that.

> As there is resource contention between movemail and mbox appending agents, some file locking mechanisms should be used but I don't know how well these work on network file systems.

I will make sure it works in the way FreeBSD describe it, but if Mutt can't handle it sanely, chances are neither will we.

Thank you so much for your input. 🤩