jesuralem

I did put a smiley in my message ! 🙂

Yes this was totally on the sendinblue side and they agreed to it.
Basically they made some change to be able to track mail openers and clicks and this screwed IPS links. They proposed to reverse the change but were insisting that the links were screwed because IPS did not accept the _se parameter they added.
Rather than fighting with them in order to explain that the real problem was that they screwed the &, i chose to cancel my subcription with them and move to AWS, and i saved quite a few bucks doing so 🙂

Yes this was totally on the sendinblue side and they agreed to it.
Basically they made some change to be able to track mail openers and clicks and this screwed IPS links. They proposed to reverse the change but were insisting that the links were screwed because IPS did not accept the _se parameter they added.
Rather than fighting with them in order to explain that the real problem was that they screwed the &, i chose to cancel my subcription with them and move to AWS, and i saved quite a few bucks doing so 🙂

Yes this was totally on the sendinblue side and they agreed to it.
Basically they made some change to be able to track mail openers and clicks and this screwed IPS links. They proposed to reverse the change but were insisting that the links were screwed because IPS did not accept the _se parameter they added.
Rather than fighting with them in order to explain that the real problem was that they screwed the &, i chose to cancel my subcription with them and move to AWS, and i saved quite a few bucks doing so 🙂

i used sendinblue and i moved to Amazon SES. So i did not really solve the problem...

I use both and they run independently of each other. Newsletters uses your sending method and this AWS app changes the default sending method. Works fine.

A quick idea : admins and moderators should be exempted from automatic bounces actions : if for some reason the mail server was to bounce for admins, admin accounts may be flagged as spammer or disabled which could end up in the ACP being unaccessible to anyone...
This would be very bad :).

A quick idea : admins and moderators should be exempted from automatic bounces actions : if for some reason the mail server was to bounce for admins, admin accounts may be flagged as spammer or disabled which could end up in the ACP being unaccessible to anyone...
This would be very bad :).

Three of the most active third party devs have been active on this very discussion. At least two of them clearly stating this would impact their future projects.
Honestly, how many active devs is there ? what would-it cost to give free licenses to developper having more than xx downloads/intalls of their apps/themes/plugins ?

Received-Spf: SoftFail (protection.outlook.com: domain of transitioning example.com discourages use of 209.85.216.68 as permitted sender)  
Setting a correct spf entry on your dns should definitely improve email deliverability.

For help and support with the AWS Simple Email Service Application. Ticket and Forum support can also be obtained at https://www.deschutesdesigngroup.com/support.
Installation Instructions: Instructions can be found on the marketplace page. Click the link below.
 

email delivery is always complicated.
What i do is use https://www.mail-tester.com/ to check my dkim and spf records are OK. you should give a try.
it will give you an idea of what is going wrong.

OK never mind, my smtp relay is actually screwing up my emails...
I disable it for the moment and will open a ticket with them. Sorry for the false issue...

OK never mind, my smtp relay is actually screwing up my emails...
I disable it for the moment and will open a ticket with them. Sorry for the false issue...

i had a feeling that &amp was a bad guy !
I changed my language and will be back as soon as i have a notification 🙂

I obviously didn't make myself clear. It was a general observation about people having to complain before action is taken where a bit of foresight and planning could have avoided the mess. I think this is the biggest grip people have right now.
I genuinely believe the IPS staff are doing a great job. I recently had my VB migration issues resolved by @Stuart Silvester and my forum has never been better.
Going against the grain here and I know the decision has been reverted but yearly payment was another non issue for me, shame we can't have both options. I like to pay my bills and not have to worry about them but I understand people don't like change and if that's the way its always been done here in the past so be it.

You are gonna kill me but it was actually a good change for those of us who have to account invoices etc...
Is there any way we could choose between 6 months and 1 year ?
 
BTW, i have to say i have the most respect for what you have been doing for 2 days answering to everybody here.

Given the fact that you provide no valuable info on how to configure the server, you should expect that.
Maybe i missed it but i never saw a list of basic Mysql/apache/php key config items for IPS. Providing basic key settings value for typical community sizes would help a lot. Theses settings depend on the code so nobody can guess the best settings for IPS.
By the way, most of the time the hoster says it is a code issue and you say it is a server issue. And this is often right for both as optimization on both sides would probably solve the problem.
 

For those of you who have accounting back office overhead (I get it!) I would say just do an account credit pre-pay equivalent to a year and then you're good to go.

You are gonna kill me but it was actually a good change for those of us who have to account invoices etc...
Is there any way we could choose between 6 months and 1 year ?
 
BTW, i have to say i have the most respect for what you have been doing for 2 days answering to everybody here.

You are gonna kill me but it was actually a good change for those of us who have to account invoices etc...
Is there any way we could choose between 6 months and 1 year ?
 
BTW, i have to say i have the most respect for what you have been doing for 2 days answering to everybody here.

I think this distinction is very hard to make.
My site is a hobby in the sense that i don't exepct to live or even earn money from it. Yet it has advertsiement revenue that i use to pay for hosting, licenses and web developpement (and accounting...).
Where would you put it ? my accountant costs 10 times what IPS is costing, the price increase is around what a corporate credit card costs, it is definitely not a problem per se.

Given the fact that you provide no valuable info on how to configure the server, you should expect that.
Maybe i missed it but i never saw a list of basic Mysql/apache/php key config items for IPS. Providing basic key settings value for typical community sizes would help a lot. Theses settings depend on the code so nobody can guess the best settings for IPS.
By the way, most of the time the hoster says it is a code issue and you say it is a server issue. And this is often right for both as optimization on both sides would probably solve the problem.
 

Wow...  spent the last hour or so reading through the 16 page thread so that I would not just post the same thing that has been said a million times already and hopefully bring some constructive feedback.
Communication
Using terms such as "modest" when describing an increase of 48% (if someone licensed all applications) and anywhere from 36-60% on a per product basis struck me in a bad way.  Statements like "It's not bad news" also did not sit well.  In fact, reading the entire message there was nothing at all that came across as "positive".  If you're going to break a bunch of bad news, it might help to drop in some "good" tidbit of something to look forward to.  Bring both the carrot AND the stick.   I understand costs are higher and this is a quality service.  I love the product and I have supported the company for literally decades.  (I've actually met and spent nearly a week with Matt/Charles/Lindy several years back when I was considering working for IPS.)  However instead of simply noting the price change is effective immediately, I would have suggested having it take place after the following renewal.  Whenever your NEXT immediate renewal is, it would renew at the existing rate, however on the SUBSEQUENT renewal, the new price would take effect.  This gives people time to adjust and prepare.  At the end of the day, it won't break the bank for me... however it would have been much more appreciated to have had a bit more heads up.   Support
I generally try to come to the forums and find the answers to my questions first by searching before I've ever opened a ticket.  I also appreciate the fact you're trying to simplify the support process.  One thing I might suggest you consider is having a section within the support forums be configured as "Users can see topics posted by other users?" being set to no. This would allow the forums to be utilized, but also allow individuals to ask questions in a more private fashion.  Information that is helpful and could be of benefit to the community could be exported using a moderation rule to the "public" forum or into whatever KB system you're looking to implement.   What is going to happen to the Support tool within the ACP?  One of the features that I loved was that if I had to create a ticket, at the same time a support login was created.  By needing to visit the community, there is no way to allow the support team to quickly login and check what is going on.  I foresee the following situation playing out: I have a problem and come to the community asking for help.  Given that I would have already searched for an answer before posting, I'll create a thread.   If it's not a general "how do I" question and instead is "something is broken" situation, the IPS support person will need to create a ticket on my behalf and collect information.  They'll also have to ask me to create a support login for them most likely.   This will then put the delay back on me to get this information and reply to support who can then engage to help. If this is a situation where "something is broken", typically it's more urgent than a "how do I" question where minutes can matter.  If my site is offline or if a major feature is working, having a delay of a full round of back and forth can be painful.  Can we come up with a way to reduce this step?  If the support tech IS going to create a ticket on my behalf, he/she should have access to everything they need to engage without feeling like we're starting over.  I'm hoping those tickets that are created by staff are prioritized so that not only do we have to wait for a ticket to be manually created for us, but then also assigned to someone to actually help. Developers
Having the Marketplace and the developer community is a feature I see as being critical to my ability to be successful.  There are certain features that are VERY important to my community that I understand that does not make sense to include in the base product.  So having 3rd parties that can customize your product in a way that makes me successful is super important for me. Matt noted about it being difficult to determine how to support developers in terms of who should be able to get free licenses, etc.  My suggestion on this front is to consider something like Microsoft and some other large software companies do....  offer a tiered developer program.  The base developer account gets you a base set of features and access to the developer forums.  The next tier includes maybe access to a private slack channel, etc.  And the "gold" tier developers might get that a free license as well as maybe something like priority app review.  You can define milestones to reach each tier such as XX in sales or YY number of installs.  I'm most likely not the best one to suggest what those milestones would be, but I think that would be a great conversation to have with your 3rd party developers.  This would make a fair system and reward those that drive the most value within your developer community.  It would also provide incentives/goals for those newer developers to reach those higher standards.  (You're making an effort to gamify communities, maybe this is an opportunity to do the same thing within the developer community here?) I appreciate no one likes getting bad news and that these are hard things to do when they need to happen.  Hopefully some of my notes above can help as you move forward.  Finally I hope my feedback is received as it's intended... as thoughtful constructive suggestions and not a general "b***h fest".   Good luck and here's to the next twenty years.