A
AlexT
Folks
Please bear with me - I'm not a real ASP pro...
I need some advice about the following problem:
I have "inherited" of a working ASP site which is hosted on a
collocated IIS machine.
At some point the site offers the possibility for any user to fill a
form and upload a file that is then dispatched, with the content of the
form, to an e-mail address.
The "legacy" code uses Scripting.FileSystemObject to transfer
(write) the file from the user POST to a local directory of the IIS
server. An e-mail message is then created, the said file attached and
the message submitted.
Our hosting company has recently replaced the IIS server and they are
very reluctant to give IUSR_<machinename> (the user running the ASP
code) write access to the local directory we were using.
So my question is: what is the best practice in such cases ?
Any info / pointer most welcome
Regards
--alexT
Please bear with me - I'm not a real ASP pro...
I need some advice about the following problem:
I have "inherited" of a working ASP site which is hosted on a
collocated IIS machine.
At some point the site offers the possibility for any user to fill a
form and upload a file that is then dispatched, with the content of the
form, to an e-mail address.
The "legacy" code uses Scripting.FileSystemObject to transfer
(write) the file from the user POST to a local directory of the IIS
server. An e-mail message is then created, the said file attached and
the message submitted.
Our hosting company has recently replaced the IIS server and they are
very reluctant to give IUSR_<machinename> (the user running the ASP
code) write access to the local directory we were using.
So my question is: what is the best practice in such cases ?
Any info / pointer most welcome
Regards
--alexT