Amazon SES send management

Mailbluster sends campaigns through a connected Amazon SES account, so cost and throughput follow SES limits. A Beam agent watches for a queued campaign, reads its recipient segment and the account's SES sending status, and applies your approved rule for when a batch may go out, for example holding a send until the previous one clears or staying inside a daily cap you set. It updates the campaign's schedule or pauses it, and notes the reason on the record. A send that would exceed your SES limits, or one flagged for unusual recipient counts, goes to a person before release.

Lead and segment records

Mailbluster stores subscribers as leads with tags, fields, and segment membership. A Beam agent reads incoming lead data from a form or import, checks it against your approved rules for tagging and placement, and writes the lead into the right segment with its fields set. It can retag a lead when its activity changes or move it out of a segment once a condition is met. Leads with conflicting tags, missing required fields, or an address your rules mark as risky are set aside for a person to resolve rather than filed automatically.

Bounce and complaint handling

Every send through Amazon SES returns bounce and complaint signals that Mailbluster records against each lead. A Beam agent reads those results after a campaign, applies your rule for what counts as a hard failure, and suppresses matching addresses so later campaigns skip them. It can tag repeat soft bounces for a warming pause and note the count on the lead. A sudden spike in complaints, or a domain bouncing across many leads at once, is routed to a person, since that often signals a deliverability problem rather than a single bad address.