Project

General

Profile

Actions

Feature #62420

closed

improved configuration for mail notification

Added by Daniel Minder about 10 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Reports
Target version:
-
Start date:
2014-10-23
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

On my system, open_basedir is set and some PHP functions are disabled for security reasons (standard for ISPconfig on Debian). According to the install tool, this is not a problem. Also, the report module in BE shows notices only.

However, the report task sends me a mail every time it is run by the scheduler.

I see 3 possible solutions:

1. possibility to configure the severity level for the mail notification, i.e. send mail also for notices, or only for warnings and error, or even only for errors (probably not recommended)
2. possibility to disable the mail notification for certain checks. however, warnings or errors could be missed if a check is disabled because it usually reports only (harmless) warnings.
3. possibility to send mail notifications only if something changes in the report, i.e. if an additional check fails.

option 1 should be quite easy to implement, option 2 has issues (see above), option 3 would be the best solution IMO.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #55694: System-status-updates sends emails about same "errors" over and over againClosed2014-02-05

Actions
Actions #1

Updated by Clemens Riccabona almost 10 years ago

Me too, I permanently get warnings about correctly configured open_basedir restrictions by mail.

And yeah it's annoying me. And I have only one of my TYPO3 installations ported to 6.2 (this is one of the showstoppers).

Actions #2

Updated by Riccardo De Contardi over 5 years ago

  • Related to Bug #55694: System-status-updates sends emails about same "errors" over and over again added
Actions #3

Updated by Riccardo De Contardi over 5 years ago

I added #55694 as related; can it be considered the same issue?

Actions #4

Updated by Christian Kuhn almost 3 years ago

  • Status changed from New to Closed

Hey. I'm gonna close this as being the same issue as #55694, which got an improvement meanwhile and has been closed.
I hope this is ok, please notify if we're missing something, or - even better - open a new issue.

Actions

Also available in: Atom PDF