v6.6.2

#365 Resolve log4j vulnerability in Simple Java Mail's CLI module

v6.6.1

• v6.6.1 (12-June-2021): #321 Ignore malformed recipient addresses and continue parsing email data

v6.6.0

#320 Added default S/MIME signing to Mailer lever and fixed crippling performance bug

v6.5.4

• v6.5.4 (22-May-2021): #315 Enhancement: Nested attachments of Outlook message attachments are now preserved as standard EML MimeMessage attachments

  NOTE: This removes the Kryo dependency

v6.5.3

• v6.5.3 (4-May-2021): #314 Bugfix: Nested attachments of Outlook message attachments are now preserved, by utilizing Kryo

  NOTE: This add Kryo as extra dependency to the outlook-module

v6.5.2

#311 Bugfix: text/calendar as string -> ClassCastException (if calendar type is not Inputstream)

v6.5.1

#307 / #310 Bugfix: embedded image resource name got mangled

v6.5.0

v6.5.0 (16-February-2021)

• #298 Enhancement: Nested Outlook messages are no to discarded anymore, but parsed to serialized Email objects
• #292 Bugfix: NullPointerException in SmimeUtilFixed when protocol is missing (which is valid)
• #289 Bugfix: Support multiple headers with same key

This release breaks all GET/SET api regarding headers used as map (Map<String, T> -> Map<String, Collection)
This release might break api in the rare case you relied on the attachment list and you have nested Outlook .msg attachments (previously omitted in the results)

v6.4.5

• #306 Maintenance: Update outlook-message-parser to 1.7.9
  • v1.7.9 - outlook-message-parser/issues/#28 / outlook-message-parser/issues/#36 bugfix NumberFormatException on parsing .msg files
  • v1.7.8 - outlook-message-parser/issues/#35 Clarify permission to publish project using Apache v2 license
  • v1.7.7 - outlook-message-parser/issues/#34 Wrong encoding for bodyHTML
• #304 Regression bugfix: batch-module needed for sending mails async, basic version should work without
• #303 Bugfix: EML Attachments are modified/have the wrong size

v6.4.4

• #294 Always invoke async success/exception handlers even if set after sending email (behaving more like promises/futures)
• #291 On Exception only log the email ID at error level and log the whole email at trace level
• #290 Only perform expensive logging logic if respective logging level is enabled