You own your mail. Your servers. Your control.
The panel installs KumoMTA on the machine you add. That is a sending engine in the same class as PowerMTA: queue, speed and your own IPs. On top is the cabinet the bare engine does not have: letters, lists, campaigns, warmup and the day’s report. You set the name in the letter. You see the numbers.
The shift pause and the send window follow this clock.
System features every section of the cabinet →
Company
North WorkshopThis is the cabinet menu after you sign in. A campaign does not start by itself. Server warmup does not send to your list.
The day
The first screen. Your company only: how many letters left, what is in the queue, which servers and campaigns are alive.
Each send is its own row: which machine, which address, what the receiving mailbox answered. You see today’s sending, not a vague “delivered somewhere”.
Opens, clicks and delivery for a campaign. A row can be opened and exported. The full event stream stays in the journal.
Letters and people
The text a person sees, and the sender name. A letter is built in blocks: preview, a mailbox check, and a score before it goes to the list.
Who you write to. Import people from a file or a paste: email, first name, last name. The list stays yours and does not mix with another company.
Subscribe and unsubscribe for the shop site. The form has a first name and a last name. You set width and height in pixels, and the background, text, button and button text. The site gets embed code. The cabinet does not open there.
Not the whole list at once. A filter for the people this letter actually fits. A campaign can go to a segment.
A stop list. An excluded address does not get the campaign, and the working lists stay intact. Unsubscribes and complaints land here.
Two versions of one letter. You see which text is livelier by opens and clicks, and you keep that one.
Sending
A new campaign stays a draft. Test first, then you start it. Until you start it, the list is quiet. The send window and the shift pause use the clock you chose at sign-in. Outside the window, letters do not go.
A check before the list. The test goes to check addresses, not to the whole customer list.
A first wave and a next letter for people who did not open or click. This is a campaign plan, not the auto-warmup conversation.
A ready sending plan so you do not start from an empty card. The campaign still starts only when you start it.
Warmup
A daily limit on each of your servers, three months of 30 days. Delivery and bounces are counted apart. An invalid address does not use the limit. Until you start a campaign, this warmup does not mail the list.
Your own letters in the company name. The chain follows the pauses you set and does not wait for a reply. Turn the chain off and only the first letter goes. A reminder is a different letter, only to people who did not reply. A reply stops reminders, not the chain. You can run several companies. The from-name is separate. Replies are read from the server mailbox.
Your machines
Your machines, not a shared service address. You add a server and the panel installs KumoMTA, step by step: machine, domain, DNS, test. The tracker name is chosen by the panel. Reply mail is installed apart: the IMAP tab, pick a server, install.
The address a letter leaves from. It needs SPF, DKIM and DMARC. The cabinet shows whether DNS is checked, and you can copy the tracker address.
The IPs of the chosen server. These are your machine’s addresses, not a pool shared with other clients.
Sending rules on your server. You can open them and edit them by hand. Kumo rereads the rules without reinstalling the machine.
Account
The term and the plan. One company cabinet: your servers, lists and reports do not mix with anyone else’s. If the term ends, the cabinet still opens, and sending and tests stop until the plan is renewed.
Registered · you are in
Next in the menu: overview, journal, campaigns, letters, lists, forms, reports, warmup, auto-warmup, servers, domains.