ppkarwasz commented on issue #3704: URL: https://github.com/apache/logging-log4j2/issues/3704#issuecomment-3067242002
Hi @sidhantmourya, Thanks for volunteering! We really appreciate contributions — all issues are open for community help, especially since we receive more requests than we can handle on our own. For this specific issue, here are a few pointers to get you started: - In Log4j Core, each appender is typically split into two components: the `Appender` (which mostly handles configuration) and an associated `AbstractManager`. - The `HttpAppender`, for example, accepts additional headers via a `Property[]` array. - These headers are processed in [`HttpURLConnectionManager`](https://github.com/apache/logging-log4j2/blob/2.x/log4j-core/src/main/java/org/apache/logging/log4j/core/appender/HttpURLConnectionManager.java), where they are applied to each request. - A similar approach is needed for `SmtpAppender`, particularly in its interaction with [`MailManager`](https://github.com/apache/logging-log4j2/blob/2.x/log4j-core/src/main/java/org/apache/logging/log4j/core/net/MailManager.java). - One caveat: `MailManager` is an abstract class with two concrete implementations — one targeting Java EE and another for Jakarta EE (located in the `log4j-jakarta-smtp` module). For help with building and debugging the codebase, please see our [`BUILDING.md`](https://github.com/apache/logging-log4j2/blob/2.x/BUILDING.adoc) guide. Let me know if you run into any questions! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
