Hi --
On 04.03.2012, at 12:35, Timo Sirainen wrote:
> On 4.3.2012, at 13.31, Michael Grimm wrote:
>> That doesn't work in my ssh setup, because I'm using a different ssh port
>> and thus have to run:
>>
>> ssh -p 1234 vm...@remote-host.tld
>>
>> Sorry, I should have mentioned that before.
>>
>> In your other mail about 'dsync replication' you refer to a config option:
>> #dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u
>> -l%{lock_timeout} -n%{namespace}
>>
>> Would that allow for ssh options to be set?
>
> Yes.
Good news.
>>>> Now, I will stick to 2.1.x because syncing is done without loss of mails
>>>> (after 10 days of testing).
>>>> The only inconvenience remaining is reappearing of deleted and
>>>> "undeletable" mail. But it seems that
>>>> I'm the only one reporting that. How could I help to debug this issue?
>>>
>>> Is anything else besides Dovecot modifying the mailboxes? Especially
>>> deleting mails? No cronjobs or
>>> other scripts that "rm" mails?
>>
>> No. Only dovecot is allowed to deliver mail (lmtp). Sieve's 'copy:' and
>> 'fileinto' are used as well.
>> But no scripts or such are used to remove mail. I'm running mdbox only.
>
> By "undeletable" do you mean you have mails that always come back after
> expunging them?
Yes. Deleting by the client will return them after the next dsync run.
> I'd like to get dovecot.index and dovecot.index.log files from those
> mailboxes from both servers, they
> don't contain any sensitive information.
From all mailboxes? I can do that if you wish. But that will need some time
(tomorrow).
Thanks and regards,
Michael
