I need to automatically add text to emails sent by users. The text CANNOT be added as a signature in outlook, but has to be added after the users click 'send' in outlook. My company uses Microsoft Exchange Server.
Any ideas?
Thanks!
If this is Exchange Server 2007 you can add a thing called a Transport Rule (in the Exchange Management Console) to do this. What you're looking for is called a "disclaimer" since most companies do this so that they can add a legal disclaimer to the bottom of outgoing email.
I would expect that this could be done with a Microsoft Outlook add-in if you have access to be able to distribute such things. Adding it as an addin at the client level may be easier than adding something to the server, and would certainly be less likely to cause problems with the server itself.
If memory serves, Visual Studio allows you the ability to create Microsoft Office addins.
Here's a link to an MSDN article about programming for Outlook 2003 in C#
http://msdn.microsoft.com/en-us/library/aa289167.aspx
Related
We are looking at moving to VSTS from Fogbugz/Kiln for item tracking and source control.
The one issue that I don't see parity in VSTS is that today with Fogbugz, our users can email foo#bar.com and it creates a work item in our system. Then from that point, whoever is working on that bug can reply from within the system and the system sends the email and the correspondence is tracked along with the work item. If the user replies, because the subject has "Item:1234" it knows to add the new email to the correspondence for Item 1234, not to create a new work item.
In looking online, it seems most people talk about addins that allow for creating a work item from Outlook, which is quite different from having the system manage the back-and-forth with the user, and allow the user to update the item just by replying to an email.
Does anyone know of a way to achieve this, or an addon/extension that would support this functionality in VSTS?
It is not supported for VSTS, also there isn’t add-in or extension support this.
You can create an outlook add-in to capture ItemSend event and Get/Create/Update/Delete a work item by using VSTS Work Items REST API.
I was wondering if its possible to create a powershell script to log into a specific outlook mail box and than add the script to the scheduled task so that no user has to be logged on.
If you need to open an arbitrary Exchange mailbox, you can either
Use Outlook Object Model (which cannot be used in a service, such as the Scheduler) to log to a predefined profile (Namespace.Logon) and call Namespace.GetSharedDefaultFolder. If the set of mailboxes is always the same, you can add these static mailboxes to the profile (open them as delegate mailboxes) and access them programmatically using the Namespace.Stores collection. Again, Outlook should not be used in a service/scheduler.
Exchange Web Services - it is HTTP based, so you can use it from a service
Graph - just like EWS, it is HTTP based, so you can use it from a service
Extended MAPI (C++ or Delphi only). native API used by Outlook itself. It can be used in a service.
Redemption (I am its author - it wraps Extended MAPI and can be used in any language from a service). It lets you dynamically log to an Exchange mailbox using RDOSession.LogonExchangeMailbox / LogonExchangeHostedMailbox (no existing profile required). Other mailboxes can be opened using RDOSession.GetSharedMailbox.
Yes, you can log on to a specific user profile programmatically. The Logon method of the Namespace class logs the user on to MAPI, obtaining a MAPI session.
Be aware, Microsoft does not currently recommend, and does not support, Automation of Microsoft Office applications from any unattended, non-interactive client application or component (including ASP, ASP.NET, DCOM, and NT Services), because Office may exhibit unstable behavior and/or deadlock when Office is run in this environment.
If you are building a solution that runs in a server-side context, you should try to use components that have been made safe for unattended execution. Or, you should try to find alternatives that allow at least part of the code to run client-side. If you use an Office application from a server-side solution, the application will lack many of the necessary capabilities to run successfully. Additionally, you will be taking risks with the stability of your overall solution. You can read more about that in the Considerations for server-side Automation of Office article.
Instead, you may consider using a low level API on which Outlook is built - Extended MAPI. Or use any third-party wrappers around that API.
We currently have a block list for Lync 2010 that contains all file extensions because someone at the company accidentally sent a malicious link to someone else. Long story short, none of the developers can send links and management is hesitant to back off the block list.
For them to back off the block list I need to build a lync extension/tool that can be used to parse and validate the url before it's sent to the IM recipient. I've downloaded the Lync 2010 sdk, am well-versed in c# and would like some advice.
Can you recommend how to setup dev environment to build lync extensions?
Can I do this in VS?
Can you point me to an example on how to parse text or links from an IM conversation?
Thanks for your time,
Chris
Use MSPL (Microsoft SIP Processing Language). You can filter messages passing through Front End Server. For more idea read blog of Michael Greenlee on following url:
http://blog.greenl.ee/2011/12/30/modifying-sip-headers-managed-sip-application-api/
I need to implement a feature in my application to process an email, that I need to read by logging into the Exchange server. My question is what is the way to make my solution to work in both Exchange 2003 and 2010?
In near future my exchange sever may get upgraded
Note: I cannot use Imap, POP, etc...
I can use only Mapi or EWS.
There appear to be several options in Java to do this but no groovy specific ones. Pick one of them and use it from your groovy code. I haven't tried any of these but have a look at all the exchange providers listed on this page
Anyone doing any work using "offline" forms? We have an application that requires inputting data from outside our company. I was thinking about sending a form out via email, allowing the form to be filled out then sent back. Obviously a web application would be the best solution, but management doesn't seem ready to build the infrastructure and security to support that. I've read a little about PDF forms is that a good solution or are there other solutions?
Have you considered InfoPath? These can be created and distributed through email. And then the data can be collated automatically.
Also, consider using Google Spreadsheets with Google Forms. It's free and infrastructure is outsourced.
PDF forms can work as well.
Another possibility is to use Microsoft SharePoint. If your company uses Microsoft Office for the people filling the forms you referring to, you could deploy an Office based solution and gather information with Sharepoint Server.
Check this link out.