Re: disable double clicking attachments

From: jd142 (jd142_at_hotmail.com)
Date: 01/10/05


Date: 9 Jan 2005 17:27:09 -0800


Vanguard wrote:

> So they cannot remember in the 5 seconds between when they specified
> WHERE to save the attachment in the Save dialog that pops up to when
> they then want to use the saved file?

That's not what happens. Double click a file and the app opens.
There's no prompt to save it before the default action takes place.
And that's what I want to stop.

> They now cannot
> remember where they just specified to save the file?

Since they save it in the same directory where the temp file is,
windows hides this from them. By default, Outlook 2003 makes temp
files in c:\documents and settings\%username%\local
settings\temp\out<differentnumber>. By default, the c: drive is hidden
when they go to my computer. And by default the local settings folder
and temp folders are too. I'm not opening up the hard drive to them so
they can browse down to copy the files.

> When the attachment is a hazardouse filetype, they do not have the
> option to open it.

Obviously I'm not talking about a hazardous file type.

> That was
> the first prompt.

Except it isn't the first prompt.

> Them navigating to and opening the file themself
> separate of the e-mail is the second prompt. There will be users
that
> open files even if there were a hundred prompts.

Nope. You don't understand the situation.

> So everyone gets to see everyone else's attachments?

What, you've never heard of private network space? Why would you
assume the default location is a shared one? It's trivial to tell
Word, Excel, Access, and Powerpoint that they should use
\\servname\%username%\ as the default file location, and only that user
gets access to that directory. Or do you not know how to use
environment variables and gpos to control office apps?

> You can't do what you want in Outlook. You are asking to change
> behavior of its code to emulate the behavior of some completely
> unrelated e-mail product. Different e-mail clients have different
> behaviors. That's why there is choice.

Sometimes there isn't choice when central IT forces programs but leaves
implementation up to individual departments. You must use *this* app,
but how you customize it for your users is up to you.

> And how are you going to stop them from opening them when they got
> stripped an put into some holding store where they then access and
open
> them?

I specifically said I wanted them to open the app, then the attachment.
I don't want to stop them from opening the app, I just want them
forced to save it only.

> Your solution doesn't stop them from running attachments, either.
> The executable filetypes are prevented from executing from within
> Outlook.

It does once you flag their attachment directory as deny execute. Duh.
Just use ntfs permissions on \\server\%username%\attachments and deny
all execute. It's a trivial solution to the prevention of executables,
scripts, and IIRC even .scr files sent as attachments from running.

But I'm not concerned about that. I could have made that clearer, I
guess, but since the default in Outlook as been to deny running
executables for a couple of versions now, I thought anyone who had more
experience with Outlook would understand that.

Just because you think you know what you're talking about but don't
have any actual useful information, doesn't mean you still have to
post. dumbass.



Relevant Pages

  • Re: VBA not executing
    ... unsigned db app is opened in Access 2007 there's a bar ... On computer one it still opens and runs as expected. ... appears that VBA is not executing. ... buttons on the form will execute the underlying VBA code. ...
    (microsoft.public.access.forms)
  • IE 7 (64-bit) Hijacks App
    ... We developed a VS2008 application using the COM WebBrowser. ... being displayed in the App, IE 7 opens up and displays ... When we execute the program on a Win 32 platform, ...
    (microsoft.public.dotnet.languages.vc)
  • Requested Registry Access is Not Allowed
    ... We have several applications that will be executing on multiple machines. ... will execute the apps. ... There are Permission Sets within the framework configuration tool, ... The app fails on the WriteEntry and the exception that is thrown is ...
    (microsoft.public.dotnet.framework)
  • RE: Requested Registry Access is Not Allowed
    ... > We have several applications that will be executing on multiple machines. ... > will execute the apps. ... > There are Permission Sets within the framework configuration tool, ... > machine that the app will run. ...
    (microsoft.public.dotnet.framework)
  • Re: Excel Automation
    ... password to prevent folks who are not supposed to execute the code from doing ... which is what workbook_open event would do every time someone opens ... So I don't think digitally signing the workbook is relevant. ... Excel and run the macro. ...
    (microsoft.public.excel.programming)