lbeachmike

Not sure if I can edit my previous post. After some further testing, it appears that it was simply the Exim restart (and not the parameter change) that actually solved this issue.

WHMCS was perfectly happy reporting successful imports despite blank emails that all were assigned to the same department. This turned out to be an Exim configuration issue that I am trying to better understand. In a nutshell, the error in the mail delivery logs that led to solving it was - discover_sender_information failed to set the from header rewrite for email@address.com it was solved by turning off the 'From: header rewrite' feature mentioned in update #28 of the below thread - https://forums.cpanel.net/threads/spam-email-from-self.635073/page-2 I believe the issue was related to using have this header rewrite feature active + DNS forwarding, but that's not yet clear. The feature in Exim Basic Config is this one - EXPERIMENTAL: Rewrite From: header to match actual sender - If you enabled this option, the From: header will be rewritten to be the email address of the actual message sender. If you choose the "remote" option, only messages that are being sent to remote destinations will be affected. Hope this helps somebody out.

I migrated WHMCS from one server to another server configured with an identical environment. After migration, an email sent to support will show in the logs that it was imported successfully, but it will import just a blank email to the wrong department. The pipe command is identical on both servers. The cpanel transfer tool was used to transfer the site. I've transferred this WHMCS between servers before without issue. There were no errors associated with the transfer. Everything else works normally. Any ideas? Thanks.

I've experienced this first hand. And in fact it almost appears as if they are generating user need for support instead of thwarting that need. For example, there are errors in the documentation which cause you to encounter problems for which you would then typically need to reach out for help with. Simply correction of the erroneous documentation would eliminate that need. But then there goes those support fees.

Their support will most definitely improve when they have half as many customers to support 🙂

The customer doesn't care, but the small business owner cares - because of reliance on such products to simplify billing and server management. Of course there will always be alternative solutions that will happily take over once the existing solutions of choice run themselves into the ground by greed. We can see this on a macro level with many very big brand name companies that used to be relevant have become irrelevant. Nobody is safe from such fate. WHMCS simply has accelerated their own disruption.

Absolutely. Per my previous point, you'll see a lot of small businesses get squeezed into consolidation. This would initially hurt them, but they've tried to insure for themselves that it won't matter since they can migrate to the model you speak of and collect no matter where those customers go. Unless those customers are being billed by Blesta.

You raise many excellent points here. Many bad side effects come out of this. Some small businesses won't be able to cut it with this pricing and will choose to sell to a larger business, so you'll have consolidation. Although there are good alternatives like Blesta, some small businesses will simply give up. Also, cPanel is an investor in WHMCS. Although cPanel has been a class act for many years, their association to this can't be overlooked. WHMCS can't set a precedent here that you can violate customers to this extent and raise pricing to this extent, or many other greedy companies will take notice. It is important not to let this happen.

I was able to successfully complete this upgrade. There is no need to rename the template and module directories. The full installation will overwrite the outdated files. There is one exception to this. In admin/lang, if there is a file named adminlangupdate.php, it must be removed or renamed or it will cause problems.

Why was it recommended to move the existing modules and templates directories out of the way, when uploading the new full install will overwrite everything that is outdated? Is there something I'm overlooking? Having some problems upgrading from the same version. Thanks. Mike

Imagine this - You buy a brand new car. You own the car. You intend to keep it for many years. After a couple of years, the car manufacturer announces that your car can no longer pass annual state inspections without a $200/month maintenance subscription fee. Your car still works fine. You just wouldn't be able to use it. Can you imagine that happening? That scenario would be identical to what WHMCS has done here.

Want, not need.

Technically the took your investment in your licenses and made them valueless. I would not continue to make the differentiation you are making. They did some math, and figured out how many people will leave, figured out how much money will come in via the remaining customer base at new pricing versus previous, and cared only about the money. In 2021, success seems to simply yield greed for more. Anybody with a conscience would not have simply discarded the customers that got them here, which clearly are all of us with the owned licenses. Class and integrity in business are scarce in 2021. Greed is in great abundance.

Rendering your software obsolete is no different than taking it away. WHMCS forgot to whom they owe their success.

I am in the same situation, with multiple WHMCS installations for small client bases. I have four owned licenses. I too do not see how it is legal or ethical to sell somebody an owned license, that you later render useless. It is basically a bait and switch. You can't pay for one thing, and have it morph into another thing.