On 02/03/2019 10:43 AM, holger krekel wrote:
Hi Marco,
On Sun, Feb 03, 2019 at 03:47 +0100, Marco Vittorini Orgeas wrote:
[...] let's say user@domain1 is happily
exchanging
mails with user@domain2, then user@domain1 starts to use delta to reply to
user@domain2, over-taking ownership of future communications with
user@domain2.
What happens if user@domain1 want to continue using its MUAs to communicate
with user@domain2 ?
If user@domain1 mails with a non-DC MUA then those messages
remain
in the INBOX [*] -- so accessible to user@domain1's MUA. They are also
shown in DC as a chat -- is that what you take issue with?
So any mail from a
contact already in the INBOX remains in the INBOX
when using Delta? This would litter the INBOX with a myriad of "small"
delta chat messages, avoiding which is the whole purpose of the shared
scenario.
Quoting you from the original post on recommending dedicated accounts
(the web archive has lost it) :
There has been a lot of negative feedback related to
"shared accounts" ...
just the freshest one from today's IRC from a new user dropping in:
if I send a chat to Joe, he answers, he is on my contact list.
Then he sends me a normal email, it will show up in Delta chat, which I
don't expect to, unless it is a reply to the chat.
This is just one of the
many things that could go wrong in a mixed setup!
Sharing DC and regular MUA usage with the same account are complex
to handle because there are many different MUA setups out there.
The complexity
arise from the unsound scope of delta, which tries to act
as a full MUA.
Holger, point is, you can share an IMAP mailbox with more than one MUA
as long as those can be configured to "move" things in a meaningful way.
Delta is essentially a "dumb" MUA with preset filters, chances are high
will cause problems in a shared scenario and I've suggested some
workarounds in the previously linked following-up analysis.
holger
[*] apart from problems arising from inter-MUA communication and DC bugs.
"inter-MUA" communication ?
--
Marco