The copyeditor reports she’ll be done fixing my innumerable errors around 15 July.1
My goal is to get ebooks out before 4 August, and print in later August.
Crime writer. Many of those crimes involve computers.
General publishing announcements
The copyeditor reports she’ll be done fixing my innumerable errors around 15 July.1
My goal is to get ebooks out before 4 August, and print in later August.
You can now preorder “Run Your Own Mail Server” at tiltedwindmillpress.com.
The last time I did a print sale (for OpenBSD Mastery: Filesystems), I offered options. From that sale, I learned that I am easily confused and should not offer options. This time I’m keeping things simple.
You can order a paperback or a hardback. It’s slightly more expensive than retail, because managing shipping is actual work that takes me away from writing.
When the books are ready to print, I will close this sale and order the sponsor, Kickstarter, and direct order copies in one gigantic heap. I will send out the ebooks a day or two after that.
Books will be shipped to me. I will open the boxes and sign them one after the other. I will print shipping labels, stuff books into envelopes, and request the post office schedule the Pickup Of Doom.
That’s it. Nothing fancy. No extra books, sorry.
This is the only way you can now get a signed book without finding me in meatspace. I am looking at ways to integrate drop-shipping print books into my web store, but none of them are quite satisfactory yet. Several printers are close–but not quite there. Either they have great Woocommerce integration but only ship from one location, or they dropship globally but have terrible integration. It’s very frustrating.
I should probably also mention that, while Kindle-friendly versions will be available from several retailers, Run Your Own Mail Server will not be on Amazon’s Kindle store, for the same reasons OpenBSD Mastery: Filesystems is not. This is a larger Mastery title and ebooks will retail for $15.
All I can say is “what?”1966 backers. $76,833.
I have never received that much for a single title in a single lump. The Absolute books might each $40,000 over their publishing lifetime, spread over years, occasionally boosted by Humble Bundles and the like. This is stunning.
My gratitude to everyone.
Some comments, in no particular order. I could put them in order, if my brain wasn’t fried from screaming NUMBER GO UP! NUMBER GO UP! all weekend.
The catch with Kickstarter is, of course, that I don’t get to keep the money. Half of it goes to fulfillment. Half of what remains gets held back for taxes. What remains is a nice chunk of cash, but I need a new car and some roof work. (I’m 57 years old and the roof is a 45-degree slope, I no longer climb up there.)
This has convinced me to run every single dang book through Kickstarter, though. Because lightning does strike twice.
If you missed the Kickstarter and want to preorder a print/ebook combo, I’ll have that up on tiltedwindmillpress.com in a few days.
So, uh, this is a thing.
Admittedly, about half of this will go to fulfillment and half of what remains will be held for taxes. (Taxes will probably be less than that, but self-employed people must always have tax money on hand. Always.) Still, I’ve never had a chunk of money this large for a single book hit my account all at once.
Thanks to backers sharing the word and saying nice things about me, all backers will get six books: Run Your Own Mail Server, Networking for System Administrators, $ git commit murder, Ed Mastery, PAM Mastery, and Sudo Mastery. Plus another “book,” but we don’t talk about that one.
That’s a lot of ebooks for $15. Or print, for a bit more. How much more? Depends on where I have to ship them.
There might be more. That depends entirely on other people, I have no control, so I don’t know.
The Kickstarter ends Sunday, 9 June 2024, at 8PM EDT–or, if you prefer, 0:00 UTC. Which you do prefer, if you’re the target audience for this book.
Pessimism is the path to happiness. Either you have the pleasure of being correct, or you are delightfully surprised.
I had hoped that the Run Your Own Mail Server Kickstarter might bring in several thousand dollars. I dreamed that if I was lucky, over the twenty days it would raise as much as the Prohibition Orcs Kickstarter. After all, this book had been heavily sponsored. I had exhausted my market.
But Kickstarter is a discovery platform, and was worth trying.
One week into this thing and it’s raised $29,731 from 719 people.
I am stunned. And my family can sure use the money.
Anyone who backs the campaign at $15 or more gets not just RYOMS, but ebooks of Networking for Systems Administrators, Ed Mastery, and $ git commit murder. At $32,500, I’ll add an ebook of PAM Mastery.
I would appreciate folks sharing this Kickstarter on their social media, discussion boards, chat rooms, IRCs, or whatever y’all use. It’s one heck of a deal.
People talk about “life changing money.” This isn’t that. But it will let me take a long, deep breath and relax.
Thank you.
Run Your Own Mail Server is the most heavily sponsored book I’ve written. Mostly that’s because sponsorships were open for longer than any other book. This gave me doubts about running a Kickstarter. Was I going back to the same people? Would anybody back it?
I launched the Kickstarter at 7:04 EDT today, and just had to update the banner image.
So, yeah. The people who will sponsor are not the same as the people who will back on Kickstarter. Though it occurs to me that during the backer survey, I should ask folks if they want to be on my sponsor mailing list. And my nonfiction mailing list.
Pretty much what the subject says. The Kickstarter page is up. If you do Kickstarter and want to know when this goes live, hit the button.
Why do both sponsorships and a Kickstarter? Different people have different comfort levels with different options. Some folks want to make the book exist. Some folks want to get the book as soon as it exists. Some of you want a vague awareness that the book exists so yuo can more easily avoid it.
If the Kickstarter does well enough backers will get an online launch party/Q&A, additional ebooks, and more. Rewards will include the book in ebook, paperback, or hardcover, signed or unsigned, Eddie Sharam’s original cover art, or (for the truly deranged) a complete set of all current IT Mastery books.
I will not be doing direct sales off my web site, the way I did with OpenBSD Mastery: Filesystems. Trying this instead, to see if the social element outweighs Kickstarter’s 8% fee. Even if you’re not a Kickstarter user, I’d appreciate you sharing the link with those who might be interested. Thank you.
I just finished the first draft of “Run Your Own Mail Server.” Copies have gone to my volunteer tech reviewers and my sponsors.
When I need to mass-mail my sponsors, I normally can only mail a dozen or so at a time without making Google and Microsoft throw a fit. This time, I mailed all 147 sponsors at once. None of the big providers even looked askance.
Requested feedback by 15 April, just to make tax day extra special. That’ll let me open the Kickstarter by Penguicon.
Working through the tail of Run Your Own Mail Server has led me to a couple things I’d like to see. Maybe some reader would like to hack on one of them.
1) The best way to generate a list of hosts that should bypass Postfix’s intrusive protocol checks, or anything that resembling greylisting, is the postwhite. Postwhite has been abandoned for years, though. This isn’t exactly a problem, as it’s feature-complete and does the job. The configuration is clunky, though. It supports a long-obsolete list of Yahoo mailer addresses. The list of domains it generates lists for is hard-coded in the script, and artificially broken up into categories like “legit bulk mailers,” “social media,” and so on. You should not have to edit the script to remove a domain, because who accepts mail from LinkedIn these days? You shouldn’t have to edit the script for anything. The last edit to this was six years ago, so I suspect it’s basically abandoned.
Moving the domains to an external file and dropping the defunct Yahoo page would be good. If you have to fork it, using a meaningful name like “greyskip” or somesuch would be nice.
2) Postfix on FreeBSD supports blacklistd. That’s grand. Log parsers are inherently fragile, and libblacklist is the smart way for an application to declare that an IP address is misbehaving. The Postfix support only applies to authentication attempts on smtpd, however. I’m in favor of that, but I’d also like to see postscreen grow libblacklistd support. A host on a trusted DNSBL pokes our mail port? Block it.
I could do #1, but I lack the time and refuse to recommend my fault-oblivious code for production. I lack both skills and time for #2.
The truth is, we’ve limped along like this for years. We could limp for many more years. But hey, someone out there might want to make the world suck slighly less.
Open source software has been adjusting its language. In a world without systemic racism, technologists could use words like “master” and “slave” without worries. While the Internet’s primordial developers chose those words without malice2, we don’t live in that world. Much of the software in Run Your Own Mail Server is older, however. Many people who don’t speak English natively don’t fully understand the implications of “black list” and “white list” and don’t want to go through the annoyance of changing them in large code bases.
Part of my job is to be easily approachable to all readers who connect with my voice.3 That means using language correctly. block list.
Another part of my job is to tell the truth. The software calls it black list. No matter how hard you search, you will not find rspamd’s block list.
I’m not going to reject rspamd or postwhite because of their language. To do so would inflict extra pain on my readers. So I’m putting this (raw, unedited) text in Chapter 0.
Today, we use the term “allow list” for entities that are permitted to skip a layer of protections, and “block list” for entities that are categorically refused. Many older programs and some software developed by non-native English speakers, still use the older blacklist and whitelist. This book uses modern language except when configuring those programs. Do please encourage your favorite developers to update their language to the 21st century, however.
This is the same approach I used in the latest Absolute FreeBSD with my beloved blacklistd, but made explicit. Also, blacklistd has been renamed. Even we greybeards can do better.
I much prefer using consistent language throughout, but reality has its own opinions.
Comments defending the old language will be summarily deleted. You also acted without malice? Fine. Now you know better. Do better.