I have a window service that reads the reply of mail and classify them based on the hidden fields into the replied email body. But while replying from outlook messenger or any other web servers other than the browsers, the hidden fields are not received into the email body of replied mail. I want the solution that why the hidden fields are not sent back to my email body while replying from outlook messenger or any other web email servers other than browser. Need help. Thanks in advance.
It is not clear what code you use at the moment in a service, but 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. Read more about that in the Considerations for server-side Automation of Office article.
You may consider using a low-level API on which Outlook is based - Extended MAPI or any other third-party wrappers around that API (for example, Redemption). In case if you deal only with Exchange servers consider using the EWS Managed API, EWS, and web services in Exchange.
Related
A client insists on moving from Notes/Domino to Office365 (no further comments on that please). There are some mail agents that provide automated functionality. In one case, it is an agent in a mail database that, when it receives a mail, it responds with a mail that contains a unique reference for the mail just received. It's their way to generate unique mail references.
How to create an alternative solution, in Office 365? Can one develop an agent in Office365?
If it must be an equivalent solution, does it have to be an Outlook client that's always on?
Or are there other ways to generate reply mails from a special mail account?
Can one send a mail to an SQL server, for instance?
I'm open to all your suggestions! Thanks.
I'd do some research into what's currently available for Office365 users via Exchange Web Services - or better yet, the Exchange Web Services Managed API.
Assuming that you Office365 gives you full access through Exchange Web Services, you can write code to use the subscription/notification services for the mailboxes that you want to monitor, and then have your code send the emails.
There may also be better ways.
I need a little help understanding a task I have been given.
I started work on a 'SharePoint focused' team and we are trying to create a SharePoint portal that would house/manage all incoming mail to a specific company email address.
We have had a couple of issues setting up SharePoint to accept incoming mail, so have begun looking at other possible options.
1 option that was suggested was to 'write a job' that would read our mailbox server (on Office 365), and then find, pull and migrate/copy selected emails onto the sharepoint site.
(something else we are also interested in doing is seeing what info we can grab from these emails at this stage which we can use to create various mail objects in sharepoint with the mail metadata. Not sure what limitations there are to what can be accessed, if anything)
Is somebody able to explain a little more the type of process or work that is required to do this (access Office 365 mail via some API which we can create a timed job for), and any experience or advice around it? Where would I start looking or how would I start implementing it, etc.
Thanks!
You combine couple of things together. SP can read incoming emails through locally installed and configured SMTP server. You can then setup document library or list to store them or create event listener to handle incoming emails completely by your own.
But both cases (OOTB functionality or event receiver) rely on local SMTP. If you want process emails from other server like Exchange Online you must either forward these emails to local SMTP server installed beside SP or you must create your own code. It can be SP job or any other type like windows service or console application executed by windows schedule, ... calling Exchange online API (designed specially for Exchange online) or MAPI or POP3 (generic using libraries) to get emails and calling SP API (CSOM, REST API) to store emails.
I tried and searched a lot to track email client but i am getting to use other bananatag or mailchimp tool. I dont want to use other tools. i only want to track which email client is being used or on which email client the mail has been opened.
I tried capturing via HTTP_USER_AGENT but did not get only got the browser information. Used document.referrer too but it returned "" .
How do mailchimp , banantag and other campaign tools figure out the mail client?
Every email client will send a user agent string, but Google Analytics is optimized for web browser hits. The email tracking vendors have accumulated the user-agent signatures of the most common email clients and do the mapping for you. (See for instance Udger Email Client List.)
The GA interface does not give you direct access to the user-agent strings of your hits, so you can't implement this mapping yourself.
One can hope that as more clients use the GA measurement protocol for email tracking the GA team will see the need to provide alternative mappings. When you know your hits are coming from email clients, it makes very little sense to map to web browsers.
As an particularly insidious example, Google's own GMail product identifies itself with this user-agent string:
mozilla/5.0 (windows nt 5.1; rv:11.0) gecko firefox/11.0 (via ggpht.com googleimageproxy)
Which ends up making it look like your hits came from Firefox v. 11 running on Windows NT, according to the canonical GA mapping. :P
You can't track this information with Google Analytics. You'll have to survey your users and use statistical analysis to determine which e-mail client(S) they use.
You can track offsite activities with Google Analytics Measurement Protocol. So you can fool your email template to include a blank image that sends out a hit to Google Analytics on each open of the email.
<img src="https://www.google-analytics.com/collect?v=1&tid=UA-XXXXXXX-Y&cid=*|UNIQID|*&t=event&ec=email&ea=open&el=*|UNIQID|*&cs=email&cm=email&cn=*|CAMPAIGN_UID|*&cm1=1" />
(example from a Mailchimp newsletter template)
Then you can select as a dimension in your event reports the Browser/Browser version and have a look at them
This is based on this article from Lunametrics
A company I am developing for needs an email service provider where its own non-technical design staff can create an email template using the provider's design web interface. Transactional emails are to be sent to a single recipient specifying the stored template plus insert values.
This is currently being done using MadMimi, and the company wants to also use a second provider for backup.
I have examined the SendGrid documentation, but apparently its web design tool produces templates which can be used only for email sent to lists, not to individual recipients.
(Note: I am coding in Ruby on Rails, but that is irrelevant to this issue.)
Can anyone suggest alternative providers which fit the requirements? Thanks!
In fact, SendGrid's Transactional Template engine allows non-technical people to edit emails meant to be sent to individual people. More can be found on SendGrid's product page and documentation pages.
There are a lot of programs out there that can access yahoo's mailbox and notify you for new mail. How do these programs work? Yahoo doesn't provide POP or IMAP access.
I'd imagine these programs are taking advantage of the Yahoo! Mail Web Service
There are examples given in a number of different programming languages on the Yahoo! Mail Web Service website that Jamie's talking about:
C#
Perl
PHP
Python
Java JAX-WS
Java Axis2
These code examples show how it's possible to access Yahoo mail using code, without requiring the redirect you mention.