Skip to main content

Creating Emails based on a Twitter feed / Friends timeline status updates

Continuing on from my previous post about posting your current Exchange calendar appointments as twitter status updates this script explores some more creative uses of the Twitter and Exchange 2007 API's. This script will read your current Twitter account details and grab your friend’s timeline and then create emails in your inbox (or other folder of choice) for each update in your friends twitter timelines (or the people your following). To match up the Received time of the email with the time the status update is posted on Twitter the script sets the necessary mapi properties to make the message appear that it was received at the same time as the status update was posted. To keep track of which updates have been created as email it downloads the latest feed and then on each run it uses Xpath to read the XML file and loads a hashtable which is used to ensure that no status update is created as an email twice. To access Exchange and create the messages in the inbox from the twitter status update it uses some precanned Exchange Web Services code I’ve added to my EWSUtil powershell library.

How does it work?

A quick run through of the script logic is it will first check to see if there is a temp directory on the C:\ and then it will see if there is a file called twitstatus.xml in this directory. If there is no file then the script knows this is the first run and it won’t bother the check to see if the status updates being read from the friend’s timeline have already been created. If the twitstatus.xml file does exist the file is read and a hashtable of the status Id’s is created. The script then reads the twitter friends timeline feed for the configured account and then using Xpath runs through all the status updates in the feed it does a compare to make sure that your own feed Status updates are excluded and also checks the hashtable to ensure that duplicates aren’t created. If it determines that an email should be added from the status update it calls a EWSUtil method that will create a sent email in the folder specified it does a conversion of the internal Twitter date/time to a date/time that can be use used in .NET and Exchange and handles the conversion to UTC. The Twitter Status text is added to both the Subject and the Body of the message this allows any URL to be accessed that are included in the status update.

Using this script

To use this script you need to have a twitter account where your following other peoples twitter updates. If you have no twitter friends try your Federal politicians. You need to configure the following two variables with your twitter account details

$twitterusername = "username"
$twitterpassword = "password"

Then you need to fill out the following Exchange variables in

$ExchangeServername = "servername"

Put the serverName of youy CAS server Then

$emEmailAddress = “twittest@domain.com”

Put the email address of the Exchange Mailbox where you want to create the updates.In

$userName = "twittest"
$password = "Password"
$domain = "domain"

Put a Username and password that has access to this account if you’re using a Cloud mailbox such as a microsoftonline.com account set the domain to blank and use something like

$emEmailAddress = "twittest@youdomain.microsoftonline.com"
$userName = "twittest@youdomain.microsoftonline.com"
$password = "youpassword"
$domain = ""

This script requires the latest copy of the EWSUtil which you can download from here I’ve put a download of the script here the script itself looks like.

$twitterusername = "username"
$twitterpassword = "password"
$ExchangeServername = "servername"
$emEmailAddress = "twittest@domain.com"
$userName = "twittest"
$password = "Password"
$domain = "domain"

$casURL = "https://" + $ExchangeServername + "/EWS/Exchange.asmx"
[void][Reflection.Assembly]::LoadFile("C:\temp\EWSUtil.dll")

$statushash = @{ }

function convertTwitterTime($ptim){
$year = $ptim.Substring(26,4)
$month = $ptim.Substring(4,3)
$day = $ptim.Substring(0,3)
$dayNum = $ptim.Substring(8,2)
$time = $ptim.Substring(11,8)
$combTime = $day + " " + $dayNum + " " + $month + " " + $year + " " + $time + " GMT"
$convertedTime = [DateTime]::Parse($combTime)
return $convertedTime.ToLocalTime()
}


$TempDir = "c:\Temp"
if (!(Test-Path -path $TempDir))
{
New-Item $TempDir -type directory
}
$StatusFile = $TempDir + "\twitStatus.xml"
if (!(Test-Path -path $StatusFile))
{
"Non Status File First Run ?"
}
else{
"Status Found"
[xml]$StatusXmlDoc = Get-Content $StatusFile
foreach($status in $StatusXmlDoc.statuses.status){
$statushash.Add($status.id.ToString(),1)
}

}
$ewc = new-object EWSUtil.EWSConnection($emEmailAddress,$false, $userName, $password,$domain, $casURL)
[System.Net.ServicePointManager]::Expect100Continue = $false
$request = [System.Net.WebRequest]::Create("http://twitter.com/statuses/friends_timeline.xml")
$request.Credentials = new-object System.Net.NetworkCredential($twitterusername,$twitterpassword)
$request.Method = "GET"
$request.ContentType = "application/x-www-form-urlencoded"
$response = $request.GetResponse()
$ResponseStream = $response.GetResponseStream()
$ResponseXmlDoc = new-object System.Xml.XmlDocument
$ResponseXmlDoc.Load($ResponseStream)
$StatusNodes = @($ResponseXmlDoc.getElementsByTagName("status"))
for($snodes=0;$snodes -lt $StatusNodes.Length;$snodes++){
if ($statushash.Containskey($StatusNodes[$snodes].id) -eq $false){
if ($twitterusername -ne $StatusNodes[$snodes].user.screen_name){
[EWSUtil.EWS.DistinguishedFolderIdType] $dType = new-object EWSUtil.EWS.DistinguishedFolderIdType
$dType.Id = [EWSUtil.EWS.DistinguishedFolderIdNameType]::inbox
$time = convertTwitterTime($StatusNodes[$snodes].created_at)
$ewc.CreateTwitMail($dType,$time,$StatusNodes[$snodes].user.Name.Replace(" ","") + "@twitterexdev.com",$StatusNodes[$snodes].user.Name,$StatusNodes[$snodes].text)
}
}
}
$ResponseXmlDoc.Save($TempDir + "\twitStatus.xml")

Popular posts from this blog

The MailboxConcurrency limit and using Batching in the Microsoft Graph API

If your getting an error such as Application is over its MailboxConcurrency limit while using the Microsoft Graph API this post may help you understand why. Background   The Mailbox  concurrency limit when your using the Graph API is 4 as per https://docs.microsoft.com/en-us/graph/throttling#outlook-service-limits . This is evaluated for each app ID and mailbox combination so this means you can have different apps running under the same credentials and the poor behavior of one won't cause the other to be throttled. If you compared that to EWS you could have up to 27 concurrent connections but they are shared across all apps on a first come first served basis. Batching Batching in the Graph API is a way of combining multiple requests into a single HTTP request. Batching in the Exchange Mail API's EWS and MAPI has been around for a long time and its common, for email Apps to process large numbers of smaller items for a variety of reasons.  Batching in the Gr...

Sending a Message in Exchange Online via REST from an Arduino MKR1000

This is part 2 of my MKR1000 article, in this previous post  I looked at sending a Message via EWS using Basic Authentication.  In this Post I'll look at using the new Outlook REST API  which requires using OAuth authentication to get an Access Token. The prerequisites for this sketch are the same as in the other post with the addition of the ArduinoJson library  https://github.com/bblanchon/ArduinoJson  which is used to parse the Authentication Results to extract the Access Token. Also the SSL certificates for the login.windows.net  and outlook.office365.com need to be uploaded to the devices using the wifi101 Firmware updater. To use Token Authentication you need to register an Application in Azure https://msdn.microsoft.com/en-us/office/office365/howto/add-common-consent-manually  with the Mail.Send permission. The application should be a Native Client app that use the Out of Band Callback urn:ietf:wg:oauth:2.0:oob. You ...

How to test SMTP using Opportunistic TLS with Powershell and grab the public certificate a SMTP server is using

Most email services these day employ Opportunistic TLS when trying to send Messages which means that wherever possible the Messages will be encrypted rather then the plain text legacy of SMTP.  This method was defined in RFC 3207 "SMTP Service Extension for Secure SMTP over Transport Layer Security" and  there's a quite a good explanation of Opportunistic TLS on Wikipedia  https://en.wikipedia.org/wiki/Opportunistic_TLS .  This is used for both Server to Server (eg MTA to MTA) and Client to server (Eg a Message client like Outlook which acts as a MSA) the later being generally Authenticated. Basically it allows you to have a normal plain text SMTP conversation that is then upgraded to TLS using the STARTTLS verb. Not all servers will support this verb so if its not supported then a message is just sent as Plain text. TLS relies on PKI certificates and the administrative issue s that come around certificate management like expired certificates which is why ...
All sample scripts and source code is provided by for illustrative purposes only. All examples are untested in different environments and therefore, I cannot guarantee or imply reliability, serviceability, or function of these programs.

All code contained herein is provided to you "AS IS" without any warranties of any kind. The implied warranties of non-infringement, merchantability and fitness for a particular purpose are expressly disclaimed.