infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-15103) Detecting issues with mboxer system
Date Mon, 19 Feb 2018 12:00:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-15103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16369048#comment-16369048
] 

Sebb commented on INFRA-15103:
------------------------------

Huh? I created both tickets; they are definitely related.
Neither are about a limit of 5GB.
The fact that INFRA-15100 was resolved is irrelevant.

This ticket is about detecting such failures in future rather than waiting until someone happens
to notice the problem.

> Detecting issues with mboxer system
> -----------------------------------
>
>                 Key: INFRA-15103
>                 URL: https://issues.apache.org/jira/browse/INFRA-15103
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Mail Archives
>            Reporter: Sebb
>            Priority: Major
>
> See INFRA-15100
> The mboxer system failed to create a couple of mailboxes due to exceeding the maximum
file size.
> This was not noticed for 3 days, and it was only noticed by accident.
> There needs to be proper monitoring for mboxer errors, as it may not always be possible
to recover lost mails if a fault is left uncorrected for long.
> This particularly applies in the case of mail aliases as there are no ezmlm archives
to fall back on.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message