LassoMailer uses a staged batch event system, driven by an authenticated URL to trigger these events.
Once a list is "released" to the campaign for delivery to recipients, the following takes place:
The system is designed to avoid overwhelming the LassoMailer and SMTP servers during large mailouts, or in environments where there are multiple LassoMailer installations on the same server.
The list view displays the process name, a brief description, when it was last executed, and its status.
Process | Description |
---|---|
Assemble | Build individual emails. |
Queue for delivery | Move assembled messages to the global batch send process. |
GetBounces | Check bounce accounts for failed deliveries. |
GeoLocate | Determine geographic location of click or view event (based on IP address). |
These processes trigger server-wide activities and are common to all LassoMailer installations on a single server.
Process | Description |
---|---|
Global delivery queue | Batch processing of global delivery queue. |
Clean delivery queue | Clean up global queue database and release locked rows. |
The global queue keeps 7 days of queue history to assist in prevention of duplicates. Messages older than 7 days are cleared from the queue history. Rows are locked during various stages of the batch processes, and clearing these locks is required if a service interruption has occurred. Locks older than 2 hours are cleared by running the "Clean delivery queue" process.
©LassoSoft Inc 2015 | Web Development by Treefrog Inc | Privacy | Legal terms and Shipping | Contact LassoSoft