Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #29652 Exceptions raised when sending mails must be logged as error
    Actions
    Infos
    #29652
    Yannis ROSSETTO (rossettoy)
    2022-12-08 13:25
    2022-12-06 15:53
    31249
    Details
    Exceptions raised when sending mails must be logged as error

    Currently, when there is an error while sending a mail, this is logged as debug, so only few platforms will have this error logged by default. It must be logged as error in the mail_syslog file.

    Other
    All
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Yannis ROSSETTO (rossettoy)
    Closed
    2022-12-08
    Attachments
    Artifact links

    Releases

    Fixed in

    Artifact ID Project Tracker Summary Status Last Update Date Submitted By Assigned to
    rel #29214 Tuleap Releases 14.4 Delivered 2023-01-05 15:24 Manuel Vacelet (vaceletm)
    Empty
    References
    Referencing request #29652

    Git commit

    tuleap/tuleap/stable

    chore: Fix request #29652 Exceptions raised when sending mails must be logged as error c77bca1fe2
    User avatar Yannis ROSSETTO (rossettoy) , 2022-12-06 16:21
    Merge commit 'refs/changes/99/27399/2' of ssh://gerrit.tuleap.net:29418/tuleap bdab0b0512
    User avatar Manuel Vacelet (vaceletm) , 2022-12-08 11:15
    Capture full exception context when logging notification failures 4395747228
    User avatar Thomas Gerbet (tgerbet) , 2022-12-08 11:28
    Display settings

    Follow-ups

    User avatar
    Yannis ROSSETTO (rossettoy)2022-12-06 16:04
    • Summary
      -Exceptions rasied when sending mails must be logged as error 
      +Exceptions raised when sending mails must be logged as error 
    User avatar
    Yannis ROSSETTO (rossettoy)2022-12-06 15:55

    A patch has been submitted for review: gerrit #27399

    • Original Submission
      Something went wrong, the follow up content couldn't be loaded
      Only formatting have been changed, you should switch to markup to see the changes
    • Status changed from Under implementation to Under review