fix: remap logger to our own for transporter (per nodemailer/nodemail…

…er#1489)
forwardemail · Sep 13, 2023 · 00c11cb · 00c11cb
1 parent 7b00438
commit 00c11cb
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 2 deletions.
diff --git a/app/models/emails.js b/app/models/emails.js
@@ -50,9 +50,12 @@ const BYTES_15MB = bytes('15MB');
 
 const transporter = nodemailer.createTransport({
   streamTransport: true,
-  buffer: true
+  buffer: true,
+  logger: true
 });
 
+transporter.logger = logger;
+
 const scanner = new SpamScanner({
   logger,
   clamscan: env.NODE_ENV === 'test'

diff --git a/helpers/get-transporter.js b/helpers/get-transporter.js
@@ -207,7 +207,7 @@ async function getTransporter(connectionMap = new Map(), options = {}, err) {
       : {}),
     secure: false,
     secured: false,
-    logger,
+    logger: true, // NOTE: we remap this to our own logger below
     host: mx.host,
     port: mx.port,
     connection: mx.socket,
@@ -218,6 +218,9 @@ async function getTransporter(connectionMap = new Map(), options = {}, err) {
     tls
   });
 
+  // remap because shared logger does not use logger properly
+  transporter.logger = logger;
+
   const pool = {
     truthSource,
     mx,