We've recently switched to SmarterMail from Mdaemon, and am quite happy about that move. However, one thing that we liked and took advantage of from Mdaemon was the fact that their log files actually had the subject line of the email being sent embedded in their log files for the transaction that was going on at the time.
We have a few e-newsletters that are BPA audited, which simply means we have our mailing list verified. We say we're sending to 15,791 people, and the log files match that. It helps with gaining advertisements.
We would take period of days, and supply the log files to the auditor, along with the subject of the email blast, and they would then be able to compare the numbers they find in the SMTP log with the subject line, versus the number we're telling our advertisers that we're sending to.
Unfortunately, with the switch to SmarterMail, we've lost this ability. We've come up with another solution for the time being, that parses the emails and tries to make heads or tails out of things - and not get confused with other email blasts that could be going on at the same time, but it's nowhere near accurate.
So, I'm suggesting the ability, maybe it could be an option for the people who don't need this added benefit?, to add the subject line to the SMTP log.
Thanks for the consideration!
Here is a sample of a transaction from Mdaemon's logs with the subject line reddened:
Fri 2016-02-05 00:00:03: Parsing message <c:\mdaemon\queues\remote\pd50023255823.msg>
Fri 2016-02-05 00:00:03: * From: newsletter@mail.photonics.com
Fri 2016-02-05 00:00:03: * To: ejames@ameritech.net
Fri 2016-02-05 00:00:03: * Subject: Special from Photonics.com: SPIE Photonics West 2016 Sneak Preview Issue 2
Fri 2016-02-05 00:00:03: * Size (bytes): 88352
Fri 2016-02-05 00:00:03: * Message-ID:
Fri 2016-02-05 00:00:03: Attempting SMTP connection to [ameritech.net]
Fri 2016-02-05 00:00:03: Resolving MX records for [ameritech.net] (DNS Server: 10.0.0.52)...
Fri 2016-02-05 00:00:03: * P=010 S=003 D=ameritech.net TTL=(5) MX=[ff-ip4-mx-vip2.prodigy.net]
Fri 2016-02-05 00:00:03: Attempting SMTP connection to [al-ip4-mx-vip1.prodigy.net:25]
Fri 2016-02-05 00:00:03: Resolving A record for [al-ip4-mx-vip1.prodigy.net] (DNS Server: 10.0.0.52)...
Fri 2016-02-05 00:00:03: * D=al-ip4-mx-vip1.prodigy.net TTL=(25) A=[144.160.235.143]
Fri 2016-02-05 00:00:03: Attempting SMTP connection to [144.160.235.143:25]
Fri 2016-02-05 00:00:03: Waiting for socket connection...
Fri 2016-02-05 00:00:03: * Connection established (10.0.0.61:62255 -> 144.160.235.143:25)
Fri 2016-02-05 00:00:03: Waiting for protocol to start...
Fri 2016-02-05 00:00:04: <-- 220 alph153.prodigy.net ESMTP Sendmail 8.14.4 IN nd2 TLS/8.14.4; Thu, 4 Feb 2016 23:57:00 -0500
Fri 2016-02-05 00:00:04: --> EHLO mail.photonics.com
Fri 2016-02-05 00:00:04: <-- 250-alph153.prodigy.net Hello mailer.mail.photonics.com [64.213.107.3], pleased to meet you
Fri 2016-02-05 00:00:04: <-- 250-ENHANCEDSTATUSCODES
Fri 2016-02-05 00:00:04: <-- 250-PIPELINING
Fri 2016-02-05 00:00:04: <-- 250-8BITMIME
Fri 2016-02-05 00:00:04: <-- 250-SIZE 31981568
Fri 2016-02-05 00:00:04: <-- 250-STARTTLS
Fri 2016-02-05 00:00:04: <-- 250-DELIVERBY
Fri 2016-02-05 00:00:04: <-- 250 HELP
Fri 2016-02-05 00:00:04: --> MAIL From:<b@mail.photonics.com> SIZE=88352
Fri 2016-02-05 00:00:04: <-- 250 2.1.0 <b@mail.photonics.com>... Sender ok
Fri 2016-02-05 00:00:04: --> RCPT To:<ejames@ameritech.net>
Fri 2016-02-05 00:00:04: <-- 250 2.1.5 <ejames@ameritech.net>... Recipient ok
Fri 2016-02-05 00:00:04: --> DATA
Fri 2016-02-05 00:00:04: <-- 354 Enter mail, end with "." on a line by itself
Fri 2016-02-05 00:00:04: Sending <c:\mdaemon\queues\remote\pd50023255823.msg> to [144.160.235.143]
Fri 2016-02-05 00:00:06: Transfer Complete
Fri 2016-02-05 00:00:10: <-- 250 2.0.0 u154v0ND017735 Message accepted for delivery
Fri 2016-02-05 00:00:10: --> QUIT
Fri 2016-02-05 00:00:10: <-- 221 2.0.0 alph153.prodigy.net closing connection
Fri 2016-02-05 00:00:10: SMTP session successful (Bytes in/out: 556/88481)