Simply put, the recieved email protocols don’t support listing of attachments, or file types. This is where you’re Email bot will need to loop through each email, for each email the attachments will be downloaded in to the indicated folder on the device, and you’ll need to write the logic to check each file in a folder to determine the extension and find the files you’re looking for. You’ll want to empty the folder before going to the next email message.
Simply put, the recieved email protocols don’t support listing of attachments, or file types. This is where you’re Email bot will need to loop through each email, for each email the attachments will be downloaded in to the indicated folder on the device, and you’ll need to write the logic to check each file in a folder to determine the extension and find the files you’re looking for. You’ll want to empty the folder before going to the next email message.
Well, i specifically want to avoid the unnecessary traffic in this, as already stated in my question:
Downloading attachments for every email and constructing a list causes a lot of unnecessary traffic, so it is to be avoided at all cost.
I also know that MAPI etc. support listing of email attachments, so the reason why this package’s protocols can’t do it is unclear to me.
You’d want to make an enhancement request for this, if the current package doesn’t contain the options. I’m unsure what the APIs return from MAPI.