I have remerged the exim after removing /var/log/exim. Now I don't have this
problem.
Thank you for your time.
... Necktwi
> On 28-Sep-2019, at 3:36 PM, Niels Dettenbach via Exim-users
> wrote:
>
> Am Samstag, 28. September 2019, 03:26:27 EDT schrieb Graeme Fowler via Exim-
> users:
>> On
Am Samstag, 28. September 2019, 03:26:27 EDT schrieb Graeme Fowler via Exim-
users:
> On 28 Sep 2019, at 07:48, necktwi via Exim-users
wrote:
> > you made me to compramise my identity? does strace.log and exim.log even
> > contain my private key?
> No, he’s not “made” you do anything, he
On 28 Sep 2019, at 07:48, necktwi via Exim-users wrote:
> you made me to compramise my identity? does strace.log and exim.log even
> contain my private key?
No, he’s not “made” you do anything, he suggested some diagnostics be provided
for the issue you’ve reported.
Luckily for you the
> On 27-Sep-2019, at 12:49 AM, Jeremy Harris via Exim-users
> wrote:
>
> On 26/09/2019 19:41, Heiko Schlittermann via Exim-users wrote:
>> Jeremy Harris via Exim-users (Mi 25 Sep 2019 10:26:14
>> EDT):
>>> Problem A) you have a corrupt file. The message even advises what to
>>> do; did
On 26/09/2019 19:41, Heiko Schlittermann via Exim-users wrote:
> Jeremy Harris via Exim-users (Mi 25 Sep 2019 10:26:14
> EDT):
>> Problem A) you have a corrupt file. The message even advises what to
>> do; did you do that?
>
> While we still should consider external influence as a root cause
Jeremy Harris via Exim-users (Mi 25 Sep 2019 10:26:14
EDT):
> Problem A) you have a corrupt file. The message even advises what to
> do; did you do that?
While we still should consider external influence as a root cause for
this database corruption, I got reports of a major Exim user, that
On 26 Sep 2019, at 15:57, necktwi via Exim-users wrote:
> but i don't think i've seen any improvement. Below is the log after the
> change
That's a small snippet which is not showing the submission of messages. I
suggested lines to look for in my previous message to the list.
Graeme
--
##
On 25 Sep 2019, at 15:43, necktwi via Exim-users wrote:
> How to run recovery? I tried rm -rf /var/spool/exim/db/* and started the exim
That’s one perfectly valid way, although there are others specific to the
Berkeley DB tools you have installed (or can install).
However:
> These messages
