Rocketseed for Exchange (R4E)
R4E is an Exchange transport agent that intercepts outgoing emails and represents the mime encoding in xml format before sending the file via http to a web service residing on Rocketseed. The Rocketseed web service interacts with the branding engine running on a Rocketseed system and then returns the modified content to the R4E agent on Exchange. R4E reassembles the email and sends it off for delivery from Exchange.
With R4E, internal emails from an Exchange user destined for another Exchange user in the same environment can now be branded.
Rocketseed for Exchange installs a transport in conjunction with a DLL on the Exchange server. These components intercept emails before delivery and route them to a Rocketseed server, which adds the email branding components to the message, and then returns it to Exchange for delivery. The customer’s IT department is completely in control of mail flow, and all delivery logs are accessed from within the Exchange admin console.
Installing and registering the R4E DLL is a matter of a few commands in Windows PowerShell. A configuration settings file contains XML settings to indicate the location of the Rocketseed server and to control which sender groups will route to it.
In addition to the R4E DLL itself, the installation requires setting up a Rocketseed Email Media appliance. This is a standalone server running Linux; installation can be performed by Rocketseed staff, or in the case of a virtual machine, Rocketseed can provide a preconfigured image ready for launch.
If desired, a shared Rocketseed server can be used in place of a dedicated installation. This makes sense for smaller engagements and those which do not require an exclusive resource.
Exchange Server 2016 RTM(15.01.0225.042) and CU1(Version 15.1 Build 396.30)
R4E works with Exchange 2013 Cumulative Update 8, 9,10,11 and 13
SP1 and SP3 (UR5 UR6 UR12 and UR14) have been tested.
Support for Exchange 2007 is projected for availability Q42016.
Administrators can specify one or more Active Directory groups whose emails will be routed to Rocketseed. Senders who are not part of the specified AD group will be completely unaffected by the presence of Rocketseed in the Exchange environment.
It is recommended to configure R4E to be applied to internal receivers only. Users with R4E configured would only have their mails to internal receivers branded
In this setup, mails sent to outside domains are processed normally via SMTP, and could be routed to a convention Rocketseed server acting as a downstream smarthost. In this way completely distinct branding rules and reporting can be configured for internal and external mails.
The performance impact on the Exchange server is minimal. Other than passing each mail body to Rocketseed and receiving back an updated version, the Exchange server does no extra work, All database calls and other expensive activities occur within the Rocketseed server.
Accreditation and Certification
R4E is certified by Microsoft for Windows Server 2012 R2.
Appication ID 12885011412