Win,
I think this is quite a broad question. For example, poor code could result in you hammering an exchange server with requests. Would it not be easier to speak to the IT services people and ask them what their concerns are? That way at least you would be able to either answer them or go away and research the issues they have raised and get back to them.
Martin | [reply] |
Since you said it would be automated, a security issue would be how you plan on storing the password. I would hope you planned on putting it into a encrypted file. Depending on your company's policies that may or may not be enough.
Also, IIRC Microsoft Exchange server is particular about the package sizes and you may have to work with your IT service team to see what is the optimal packet size for the server the way they have it set.
Lastly, you say you are going to download attachments. Is your script set to always download all attachments or to just download those it has not already downloaded? If each time it runs, it re-downloads all the attachments, your program can quickly become hog on the server and the network depending on how often you plan on running it. | [reply] |
Using Win32::CryptData should help regarding the password issue. Anyway, if you just want to remove the attachments, well, probably would be better if the server never received then. But I don't have any idea to how to handle this using MS Exchange server.
Alceu Rodrigues de Freitas Junior
---------------------------------
"You have enemies? Good. That means you've stood up for something, sometime in your life." - Sir Winston Churchill
| [reply]
[d/l] |