- WHY WONT APPLE MAIL DOWNLOAD ATTACHMENTS WHEN USING MOHAVE PDF
- WHY WONT APPLE MAIL DOWNLOAD ATTACHMENTS WHEN USING MOHAVE CODE
Insofar as my approach being a workaround, that is true for saving the attachments, but a necessary one.
WHY WONT APPLE MAIL DOWNLOAD ATTACHMENTS WHEN USING MOHAVE CODE
I do not think my code was in error, but am open to hearing from you if you have a better way to do this so I can learn. My script is quite straightforward, and uses code similar to that already posted in this discussion, eg setting a variable to “every mail attachment of theMessage” checking to ensure the resulting list is not empty repeating through each attachment and saving it to the associated file. In fact, the workflow I described started with an AppleScript to save the attachments, but after I find it unreliable (two successive emails, each from the same person, each with a single attached Pages document, for one the script worked, for the other it failed getting the attachment) I switched to the implementation described. I have found it consistently occurring through Mojave. When I first ran into problems I found numerous other reports and descriptions of this problem, with no fix from Apple. This is a known bug that has been reported for years over multiple OS X and MacOS versions. I should have been a bit clearer: the issue is related to obtaining and saving attachments to mail message via AppleScript.
I am not convinced that the script quality is the issue. I hope this workflow is for the followup.
WHY WONT APPLE MAIL DOWNLOAD ATTACHMENTS WHEN USING MOHAVE PDF
I also take the mail pdf as “email”, the raw file as “rawemail” and each attachment as “attachment.” If there are attachments I also add a “hasattachment” tag to the mail pdf. Based on the account it came from I assign a tag to each file. Use the account name to assign tags to the files thus created.Rename the mail pdf using the prefix as above.Use KM user interface scripting to have Mail.app save the email itself to a PDF on the desktop.Return from the script the filename prefix, the raw file name, and the name of each attachment file. Rename the file containing the raw file using the prefix with _raw appended (I keep that because it is easy to search via grep). Run the python script which takes the raw file and saves the attachments on the desktop, using the filename prefix above as computed.Otherwise, save the account name in a KM variable. Check for the error codes and display error messages and quit.Return from the script the accountName found above (or an error code if there is a problem, like more than one message selected). Use AppleScript to find the current selected message (make sure there is only one) and write the entire message content to a file on the Desktop.
I tie the entire thing together in a Keyboard Maestro macro (that I will likely post on the MPU forum once I have a bit of time. Where theMessage is the selected message in Mail.app. Set accountName to the name of the account of the mailbox of theMessage To be able to sort the email messages, from AppleScript I use: I name the files using the format YYYY-MMDD_MD5_filename where YYYY-MMDD is the date the mail was sent, MD5 is the MD5 hash of the entire mail content (that makes sure that all saved files are unique to the email message, and filename is the filename for the attachment.
My approach is to save the entire email message (the raw content) to a file and run a python script that pulls out the attachments and saves them to disk. This problem has existed for years and never been fixed by Apple, and for that reason my workflow for saving emails is NOT based on using AppleScript to save the attachments.
I have found that Mail.app’s AppleScript support is highly flakey, especially when it comes to saving attachments reliably.
0 kommentar(er)
