Initially tried clicking and dragging from EagleFiler to Finder, which worked for up to 50 messages at a time attempting more than that resulted in a textClipping file containing the subject lines instead (dragging in batches of 50 is not ideal, especially as filename collisions result in only Skip, Stop, or Replace options). Tom Floeren's "Export Selected Mail Messages" AppleScript (four duplicate messages, i.e., those containing the same Message ID and date/time stamp as other messages, were not exported)Ĥ. * Created a new mailbox in Mail and copied 172 messages containing Japanese characters from other Mail mailboxes into it.ģ. Here is the result of some cursory testing:
#Foxmail 5.0 mac
If the script retrieves the source as a Unicode string and then writes it to a file, the non-ASCII bytes will be altered.Īpple Mail AppleScript Bug E-mail EagleFiler Mac macOS 12 Monterey Thanks for your reply. Mail types the source AppleScript property as text when really it should be treated as raw data. Many scripts, such as the mentioned Export Selected Mail Messages, will corrupt message data because they don’t properly handle a bug/oddity in Mail’s AppleScript support. Unlike Mail it doesn’t fail for messages with long subjects. You can also do this to export messages from EagleFiler, if you want to convert them from mbox to. Click and drag multiple messages from Mail to Finder I have not seen the “some messages could not be imported” error when importing properly formed mbox files, such as those generated by EagleFiler.Ģ. I’m not sure what’s causing the importing problem that he mentions, but historically the Export Mailbox… command has not generated valid mbox files.
Of course, I recommend EagleFiler for this, which offers a variety of ways of importing from Apple Mail. Mail’s built-in export (and import) methods suffer from various limitations and bugs the following tests were run under macOS 12.4 and Mail 16.0 Exporting/Archiving E-mail From Apple Mail
0 kommentar(er)
