EmailServer is an enterprise-strength tool for automating both
mass-emailing and single email processing tasks. Arnica EmailServer also provides functionality for performing either scheduled or on-demand download of incoming emails for multiple accounts and storing them in easy-to-access database tables through specially created database APIs. All email queue, mass-mail and incoming email management is done through a web browser interface.
Sending Individual Emails
Arnica EmailServer allows you to avoid direct interfacing with low-level SMTP subsystems by providing a high-level easy-to-use application programming interface. You may publish emails into an outgoing queue (or mark them to be sent immediately) using web requests with posted XML provided by Arnica EmailServer, which includes email content together with sender/recipient information as well as other data required for sending an email. Alternatively, you may publish emails using a database API (via a stored procedure call), which adds an email item to email queue; this method is especially useful when sending emails directly from custom databases.
Mass Mailing Campaigns
EmailServer may be used to manage and execute mass-emailing campaigns with any number of recipients, from hundreds and thousands to millions. Integration with Arnica UnifiedLogon allows for effective management of recipient pools. With UnifiedLogon's flexible user (recipient) profile management features, creating highly customizable mass-emailing solutions becomes easy and efficient.
At the core of mass-email campaign management, Arnica EmailServer connects templates with a pool of recipients. Email templates are evaluated at run-time (when emailing is executed), thus making it possible to use individual recipient profile properties to alter email content for each instance of outgoing email.
Mass-emailing takes into account subscription opt-in flags, which are maintained per each recipient, and allows managing specialized subscriptions (per category), for example, a recipient may have enabled subscriptions for technical mailings, but not for sales and advertising mailings. By classifying mailings in administrator-defined categories, Arnica EmailServer sends emails only to qualified subscribers in any given pool.
Managing Incoming Email
EmailServer can also capture incoming emails and save them in
easy-to-access database tables. One example of such use is downloading reply emails after mass-emailing campaigns; recipients reply to the email
they receive, sending replies to the email box specified as sender
email address in the original email. Multiple email campaigns may use
different sender email addresses, EmailServer will monitor these
accounts and download emails arriving in corresponding email boxes. Downloaded emails may then be analyzed for various business purposes.
True Thin Client
Arnica EmailServer is a true thin client solution: administration, template design, and
are all done through a web browser. Remote
management through a web browser provides a high level of flexibility and opportunities for both internal and
outsourced types of administration.
Application Programming Interface (API) and Integration
functionalities of Arnica EmailServer are provided either via
Administrator module interface, or via application programming interface
(API). Arnica EmailServer includes a rich set of web services (REST)
and database APIs (views and stored procedures), which may be used by
administrators and programmers to integrate their applications with Arnica EmailServer.
Central Database Repository
Arnica EmailServer stores its meta data and content (templates, content processing scripts, etc.) in a central
database repository (based on Microsoft SQLServer or free SQLServer
Express Edition) and allows certain operations to be performed simultaneously against
multiple templates at design time, for
example, meta search and
ability to use global parameters shared by multiple templates, etc.
Activity Log and Monitoring
EmailServer publishes detailed email life-cycle information into central database
repository, enabling you to perform statistical analysis of activity by
various parameters. For each email, database repository maintains its original email content, recipient/sender information, number of send attempts, send result (success/failure) information, mailing reference (whether email was sent using mass-emailing), template reference (whether email was sent using a particular email template), etc. If email template contains backtracking code to capture events when a recipient opens the email, then EmailServer also provides this data via database API.