I guess the underlying case here is that we want "some kind of monitoring" to alert us of failed imports, but do not insist too hard which solution that is.
Is there already something new present and working that will replace the old mailing feature?
I know it was off recently, but dropping it entirely from the codebase without a successor feels odd indeed.
If there is a plan or even code already we could - while dropping the mail feature - at least outline a bit like "this used to use mails summarizing the fail reason which no more works because X<reason>, instead as part of version x.y <plan> it will switch to report such issues via Y<solution that fits better because>".
If we do not yet have an Y, maybe we should keep X for now (even disabled)?
I guess the underlying case here is that we want "some kind of monitoring" to alert us of failed imports, but do not insist too hard which solution that is.
Is there already something new present and working that will replace the old mailing feature?
I know it was off recently, but dropping it entirely from the codebase without a successor feels odd indeed.
If there is a plan or even code already we could - while dropping the mail feature - at least outline a bit like "this used to use mails summarizing the fail reason which no more works because X<reason>, instead as part of version x.y <plan> it will switch to report such issues via Y<solution that fits better because>".
If we do not yet have an Y, maybe we should keep X for now (even disabled)?