We have setup an email trigger using the EWS exchange connection and are using it to save down both the email and the attachment. This works great when we use a specified folder, however when using the default folder the job is triggered and the email saved, but the attachment does not get saved (an empty attachment folder is created). Could you advise us on how we might resolve this issue?

I will forward this to one of our developers for testing. Thanks

---

Thanks Henrik, were you able to replicate this issue or does it appear to be specific to our setup?

It is a bit complicated. In short, the problem is that the network path, where you want to save the email and attachment is too long for Windows. You can solve it by solving it in a shorter base path for now. We are working with the component provider to provide a workaround for long paths but this might take some time.

---

Ok thanks Henrik. We did notice an odd naming convention of the folders created that look like a string of random characters, short for the sub-folder and very long for the default directory. Is this folder generated and named by the VisualCron task, and if so is this needed? With the location to save the attachment already specified in the task setup, we would prefer it to save at this level rather than within a sub folder here.

Can you add a screenshot of base folder and down so we can see the full context of folders?

---

Hi Henrik, my apologies it looks like our issue is resolved by checking the "Is public folder" box under Email Trigger->Main settings. It is without that box checked where we noted the email & attachment being saved down in a new folder with a randomly generated name.

Glad it was resolved!

---