On 2023-06-05 at 20:19:19 UTC-0400 (Mon, 5 Jun 2023 19:19:19 -0500) Robert Nicholson via Exim-users <[email protected]> is rumored to have said:
What defines when the “data” format is used to store the message?
A message file in an interoperable Maildir/Maildir++ structure is a text file, as defined by RFC822 and its successors as well as the suite of RFCs defining MIME.
There's a good description of Maildir at https://www.courier-mta.org/maildir.html
The message ends up in some binary encoding and that makes it harder for me to test it thru my own filters with.
Many messages are partially or fully encoded with Base64 or Quoted-printable to allow for non-ASCII content. See the MIME RFCs.
Is there a way to convert such messages to the text format to make testing easier?
That depends on what the message contains and why it was encoded.
For example of the messages looks like this 1686008819.M92410P2445.lhvm02.lizardhill.com,S=72137,W=74032:2, file 1686008819.M92410P2445.lhvm02.lizardhill.com,S=72137,W=74032:2, 1686008819.M92410P2445.lhvm02.lizardhill.com,S=72137,W=74032:2,: data
Try actually looking at it yourself. The 'file' utility is imperfect at identifying email as such.
as opposed to messages that look like this 1686009696.6909_0.lhvm02:2,S file 1686009696.6909_0.lhvm02:2,S 1686009696.6909_0.lhvm02:2,S: RFC 822 mail, ASCII text
The difference in name formats is a function of how the specific message was delivered, i.e. what tool created the message file. See the link above for details.
-- Bill Cole [email protected] or [email protected] (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Not Currently Available For Hire -- ## subscription configuration (requires account): ## https://lists.exim.org/mailman3/postorius/lists/exim-users.lists.exim.org/ ## unsubscribe (doesn't require an account): ## [email protected] ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://wiki.exim.org/
