FernpostWeb

It retries for an hour, and if it still cannot go you get an email rather than finding out later. The issue returns to your queue with everyone who already received it marked, so re-sending never writes to the same person twice.

Because Outlook renders email with a word processor rather than a browser, which is as strange as it sounds. Fernpost writes markup that survives it, so the layout holds, but very fine spacing and some rounded corners will differ.

Send yourself a test before anything you care about. It goes through the same path as the real send.

Any time, from Settings, as a CSV with every field you have on each person including their signup source and date. No notice, no email to me, no export fee.

Your issues export too, as Markdown with the original dates, so an archive you rebuild elsewhere still reads in the right order.

No. Nothing you write is read, shared or used to train anything, and your list is never rented, sold or borrowed for anyone else's sending.

The only time I would open an account is if you ask me to while we are working through a problem together, and I will say so first.

Nothing, for two weeks. Scheduled issues keep going out and you keep full access while I retry the payment and email you about it.

After fourteen days sending pauses, but nothing is deleted, and everything resumes when the payment goes through.

Yes, and I would recommend it. Add the domain in Settings, add the three DNS records it gives you, and Fernpost checks them every few minutes until they are live.

Until then your issues send from a Fernpost address, so nothing is blocked while you wait.

Not on the plan itself. The limit is what your sending provider allows, which for most people is far more than they have.

Not yet, and it is being built now. A second person will get their own login rather than sharing yours, and each issue records who wrote it.

Until then the honest answer is that people share a password, which I would rather they did not have to.