i have an outbound email that keeps failing with a file permission error. civi created the file with (600 running as nobody) and the cronjob (running as the account owner) can't access that file.
i think this is new behaviour as the user reports that emails with attachments worked before our latest upgrade (458->468)
anyway can i force civi to create attachments with (666) ? this allows the cron user to access the file (which i tested by resending the email -- changing the permission on the attachment manually -- and then scheduling for immediate send)
(and yes i know it's "bad practice" to attach files to bulk emails -- but this is a valid use case. user is sending audition packets to potential members of one of our performing ensembles. only 58 recipients. which BTW is a good reason the hard-limit on direct emails to contacts should be a user-adjustable setting not a hard-coded value in a core file! )