@whartung I have two points to make about the "subsidy is a precondition for mail" approach.
The first point is ... that everything being discussed in those passages about Cr5000 per ton (max 5 tons) mail delivery contracts is that they are precisely that ... CONTRACTS. The ship is
contractually obligated to carry mail. What is the mechanism used to guarantee that the terms of the contract will be honored? The subsidy agreement.
So you've got a little bit of a chicken vs egg thing going on. The subsidy can run the mail that requires a subsidy so it can run the mail that needs a subsidized ship to be a mail carrier.
Now ... start reading between those lines a little bit (you don't need to go too far) and the intention behind the reasoning for that ought to become clear. Mail contracts are going to require what amount to "routine deliveries" even if the route (per se) isn't decided from the outset. In other words, ships that can "go anywhere" like a tramp freighter are not going to be suitable candidates for mail contracts.
For simplicity purposes of illustration ... let's say a ship gets mail contracts with destinations A, B and C.
So long as the ship makes deliveries to those destinations ... A, B, and C ... they'll be given mail to deliver to those destinations.
But if the ship "wanders off" to go to destinations D, E and F (which are outside the mail delivery destinations) then the ship won't be given mail to take to destinations D, E and F (and so on).
In other words, a tramp freighter that isn't "tied" to a particular set of destinations would not be suitable for a mail contract.
Conversely, a ship that is operating within a defined range of systems (say ... 2-12 of them, for example?) can be set up to operate with mail contracts for those systems.
Basically, the subsidy is there to ensure that a ship operated by Players isn't going to wander "too far off the reservation" while under contract to deliver mail. What is the mechanism for doing that? Game mechanically speaking, the binding obligations of a subsidy, to keep them operating within a defined range among a specific set of destinations (the subsidy locations).
Now ... everything that I've outlined there is backdrop consistent with how interstellar mail presumably would be set up to operate. The Postal Unions involved don't want ships wandering off with their mail. The rules system provided in the LBBs (and now LWBs) are what a Player and a Referee needs to know in order to run a campaign and set the expectations appropriately within that campaign. Players are "ornery cusses" who are highly prone to "wander off the reservation" ... especially when the scent of adventure can be smelled in the (recycled) air, and not all of them like being "tied down" to a specific location on the map.
However, companies (megacorp and below) aren't "Players" in the same sense as the people sitting around a table with dice are "Players" in this context. Private companies would be perfectly capable of setting up contracts with Postal Unions
just like a subsidy ship would except that the mail contracts are a private contractual obligation rather than a subsidized one. The only real difference is that a private enterprise funds the ship involved, rather than a government (and given that government code: 1 is a corporate government, how much of a distinction really needs to be made here on this point?).
So instead of a government paying for a ship and the captain is under contract to run it ... a company pays for a ship and the captain is under contract to run it. The only difference as far as the financing of the ship is concerned is who is paying for the mortgage payments (assuming the ship isn't paid off in cash upon delivery from the shipyard). Bank loan, subsidy or private cash payout is immaterial with respect to what the ship can be hired to do. However, the frequency with which a ship will be expected to visit specific ports of call ... that is very much a determining factor as to whether or not a ship ought to be given a mail contract with a Postal Union.
At the outside, 12 systems in a subsidy creates an expectation of ~2 trips to each destination per year (on average) minimum per system. In actual operation it will probably wind up being that some systems are visited by the ship no more than once per year, while other systems in the grouping get visited multiple times ... but the point I'm wanting to make here is an expectation that a ship contractually obligated to deliver mail ought to be visiting each destination it has a mail contract with an AVERAGE of twice per year (preferred) and a minimum of at least ONCE per year (mandatory). That should be the contractual minimum obligation of mail deliveries to get a mail contract
for each destination ... and you need a mail contract for each destination you plan to deliver mail to.
Now a subsidy can do all of that setup legwork for you (it's baked into the subsidy and the subsidizing government does the legwork to make it happen) ... but there's nothing which says that a private operator couldn't set themselves up with mail contracts on their own if they meet the qualifications (two deliveries per year preferred, one delivery per year minimum, 5 tons dedicated cargo space set aside, armed, gunner in crew) but an independent operator would need to go to each of the destinations and sign contracts with each of them individually to deliver mail to them. This CAN BE DONE ... but there's more "hassle" involved (from a Player at the gaming table's perspective, since you have to jump through hoops to make it happen) so it's more complex than the subsidy route. However, accepting the option necessarily means that any ship running mail under contract is going to be more "firmly tied" to a specific collection of worlds (minimum 2, with the useful maximum probably being 12) ... which starts sounding an awful lot like a subsidy arrangement at that point (except the financing for the ship is either private or bank financed instead of subsidized).
Now ... all of that more in depth explanation needed A LOT more word count to make it clear than would have been available in the LBB format, but you need that fuller understanding and insight to properly grasp what would be involved with a mail contract that does not rely on a subsidy. I think it's fair to say that the whole notion wasn't considered all that deeply (I may have put more thought into it here in this post than the original writers of the LBBs did) so rather than expound on the nuances in a way that could enrich the game experience and setting, the whole thing got simplified down to what amounts to "bone shavings" as far the details were concerned.
After all ... how many adventures can the MAILMAN get up to ... am I right?
The whole thing with the "other ships can carry private messages" thing is pretty obviously intended to be used as a Plot Hook and means for PCs to encounter and interact with Patron NPCs. It literally is a case of "using alternate channels" for messaging (via Carrier Pigeon Packet Protocol) that hopefully will not be intercepted. It also gives the Referee a chance for a "don't shoot the messenger!" setup for a campaign adventure.
In computer gaming, there's a phrase that I think we are all familiar with and dread hearing ...
Working As Intended.
What programmers often mean by that phrase is that something is
WORKING as intended ... which basically amounts to saying that a bit of code isn't causing fatal errors that crash the program to desktop (or the Blue Screen Of Death™). The programming WORKS is the important thing for a lot of developers (and game designers).
What players often times key in on is whether something is
working as INTENDED ... which gets to questions of the INTENT behind exactly HOW and WHY something is working the way that it does. It is perfectly possible for a system to "work" while utterly failing at its "intended" purpose (so it "works" but not the way people want it to).
In order for congruence of perspective to be achieved, a system not only needs to WORK well but also requires its INTENT to be understood congruently by both/all parties.
Sometimes, even when something is WORKING you need to more closely examine the INTENT operating behind it to truly grasp the proper context and meaning (and achieve the deeper understanding of enlightenment ... blah blah blah). When something "works" but doesn't do what you "want" (or intended it to do) that's a different flavor of problem that requires understanding the intent (more completely) before you can solve the problem of making things work "the way they should" in the proper context.
And it's at this point that the electrical engineer who wants to resist the current thinking begins chanting "Ohm. Ohm. Ohm..."