Return-Path: 
 <log4j-dev-return-38324-apmail-logging-log4j-dev-archive=logging.apache.org@logging.apache.org>
X-Original-To: apmail-logging-log4j-dev-archive@www.apache.org
Delivered-To: apmail-logging-log4j-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 560EF18899
	for <apmail-logging-log4j-dev-archive@www.apache.org>;
 Tue,  3 Nov 2015 16:22:28 +0000 (UTC)
Received: (qmail 71937 invoked by uid 500); 3 Nov 2015 16:22:28 -0000
Delivered-To: apmail-logging-log4j-dev-archive@logging.apache.org
Received: (qmail 71817 invoked by uid 500); 3 Nov 2015 16:22:28 -0000
Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:log4j-dev-unsubscribe@logging.apache.org>
List-Help: <mailto:log4j-dev-help@logging.apache.org>
List-Post: <mailto:log4j-dev@logging.apache.org>
List-Id: "Log4J Developers List" <log4j-dev.logging.apache.org>
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Delivered-To: mailing list log4j-dev@logging.apache.org
Received: (qmail 71676 invoked by uid 99); 3 Nov 2015 16:22:28 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 03 Nov 2015 16:22:28 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id B78822C1F6A
	for <log4j-dev@logging.apache.org>; Tue,  3 Nov 2015 16:22:27 +0000 (UTC)
Date: Tue, 3 Nov 2015 16:22:27 +0000 (UTC)
From: =?utf-8?Q?J=C3=B6rg_Bretschneider_=28JIRA=29?= <jira@apache.org>
To: log4j-dev@logging.apache.org
Message-ID: <JIRA.12910031.1446566794000.138264.1446567747749@Atlassian.JIRA>
In-Reply-To: <JIRA.12910031.1446566794000@Atlassian.JIRA>
References: <JIRA.12910031.1446566794000@Atlassian.JIRA>
 <JIRA.12910031.1446566794306@arcas>
Subject: [jira] [Updated] (LOG4J2-1192) Dynamic Subject for SMTP Appender
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/LOG4J2-1192?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:all-tabpanel ]

J=C3=B6rg Bretschneider updated LOG4J2-1192:
---------------------------------------
    Description:=20
It is annoying to have log messages sent to users via SMTP Appender with a =
static subject, requiring recipients to open each of possibly a vast amount=
 of log emails in order to find out what went wrong.

Users should be able to insert runtime diagnostic context information to th=
e message text AND to the message subject. While the first seems to be work=
ing with Patternlayout using the mechanism with the %X{<key>} pattern based=
 on a NDC or MDC <key> in the "ConversionPattern" parameter, it does NOT wo=
rk with the "Subject" parameter with log4j (neither 1.2 nor 2.x), though so=
me bloggers suggest it.

See http://stackoverflow.com/questions/29435825/log4j2-custom-email-subject=
-from-map as an example where others found this also.

This issue should have been fixed long ago.

I suggest to extend SMTP appender in order to be able to use %X and other P=
attern conversion in the "Subject" parameter properly.=20

http://openutils.sourceforge.net/openutils-log4j/smtpappender.html=20
has already done the part for applying PatternLayout to the SMTP Appender "=
Subject". I didn't test of this works properly.=20
Maybe this work can be included into log4j with minimal effort?


  was:
It is annoying to have log messages sent to users via SMTP Appender with a =
static subject, requiring recipients to open each of possibly a vast amount=
 of log emails in order to find out waht went wrong.
The mechanism with the %X{<key>} pattern based on a NDC or MDC <key>, as de=
veloped for PatternLayout in order to insert runtime context information to=
 the message, does not work with log4j (neither 1.2 nor 2.x) properly. (See=
 http://stackoverflow.com/questions/29435825/log4j2-custom-email-subject-fr=
om-map) as an example where others found this also.
This issue should have been fixed long ago.


> Dynamic Subject for SMTP Appender
> ---------------------------------
>
>                 Key: LOG4J2-1192
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1192
>             Project: Log4j 2
>          Issue Type: New Feature
>          Components: Appenders
>    Affects Versions: 2.4.1
>         Environment: ALL
>            Reporter: J=C3=B6rg Bretschneider
>              Labels: features
>
> It is annoying to have log messages sent to users via SMTP Appender with =
a static subject, requiring recipients to open each of possibly a vast amou=
nt of log emails in order to find out what went wrong.
> Users should be able to insert runtime diagnostic context information to =
the message text AND to the message subject. While the first seems to be wo=
rking with Patternlayout using the mechanism with the %X{<key>} pattern bas=
ed on a NDC or MDC <key> in the "ConversionPattern" parameter, it does NOT =
work with the "Subject" parameter with log4j (neither 1.2 nor 2.x), though =
some bloggers suggest it.
> See http://stackoverflow.com/questions/29435825/log4j2-custom-email-subje=
ct-from-map as an example where others found this also.
> This issue should have been fixed long ago.
> I suggest to extend SMTP appender in order to be able to use %X and other=
 Pattern conversion in the "Subject" parameter properly.=20
> http://openutils.sourceforge.net/openutils-log4j/smtpappender.html=20
> has already done the part for applying PatternLayout to the SMTP Appender=
 "Subject". I didn't test of this works properly.=20
> Maybe this work can be included into log4j with minimal effort?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org