E-mail - How to trust?

[lameid]

It has been a long while since they added the automation restrictions and a long while since I had to think about it.

I read that CDO is off the table, hit a brick wall signing my code (Access 2013) and found a general lack of current relevant information on the e-mail topic. You simply can't sign access code since 2010 - thanks MS - can we have the builder back in Access vba now that it works differently?

Is there a way to send e-mails these days in an environment where Outlook is set to always prompt without the prompts?

I have not gone down the path, yet, but I was thinking maybe a signed Excel project that is automated to run the send but I am not sure that would work out as intended. Excel over other applications because I tend to have to automate Excel from time to time anyways.

 

[strongm]

>I read that CDO is off the table

Can you clarify? CDO still works fine for me - but you perhaps have requirements that make it unsuitable? or perhaops you are referring to CDO 1.2.1.

>hit a brick wall signing my code (Access 2013)

Surely just [tt]Tools>Digital Signature[/tt] in the VBA IDE? Or [tt]File>Save & Publish>Save Database As>Package and Sign[/tt] - actually in 2013, that moved that slightly ...erm .. [tt]File>Save As>Save Database As>Package and Sign[/tt]. Assumes you have a relevant certificate available ... Of course this no longer packages the db with the Access runtime, but you seemed to simply be interested in signing.##

>a long while since they added the automation restriction

Indeed - but they also latterly added some opt outs under Trust Center>Programmatic Access. Of course, if what you are saying is that that has to be set to always prompt then things are a little trickier (presumably this is being enforced by the IS department, and probably with good reason). You can work around this with products such as Outlook Redemption, but this may mean your are messing with company policy.

 

[lameid]

I think my trusted locations started to behave again so this became moot. I am not sure what was going on there other than yet another security product was installed. That being said, digging back into the issue I read somewhere that CDO support was removed. It seems like you are saying a specific version was and I stumbled on a thread somewhere in that period.

Regarding digital signatures, I am interested in signing the code for trust at execution time which would be trusted code by signature vs. trust by location. I have a certificate, grabbed it when my Organization started requiring Excel macros to be signed... Or was it Word? In any case, what you are suggesting creates a special signed Access file that can have the original Access file extracted from for use, the kind that can be ran. That puts me back where I started, a file that has code that is not trusted. I can sign Excel code for trust, why not Access? - That is the issue I was mentioning. I would be happy to be wrong.

 

[strongm]

That's why I provided 2 options, as it was unclear (to me) what your exact requirements were. The first option - Tools>Digital Signature in the IDE - should provide the functionality you latterly describe (although forgot to mention it only works with mdb files though, not with accdb)

 

[lameid]

Right Access 2013 => ACCDB: Signing (Publishing) is not a useful option for anything other than downloading the file with a browser.

If you have CDO code that works to send and optionally attach a file, I would be curious to give it a try in my environment but like I said everything seems to be working as expected now so looking for alternatives is not a priority... at least until the next time it does not work.