Have I made a mistake?
Drop me a PM early tomorrow and I'll make sure I pick this up first thing for you. I suspect a wider issue with the removal script TBH as I've seen a similar thing to this happen in the past.
Speaking honestly I could never recommend hosting your own website on Plusnet servers or using their Email servers for anything important. These are clearly the weakest parts of the service which Plusnet offer.
I myself moved my Email (apart from some newsletter subscriptions) and website out a few years back and am glad I did do as there have been continued problems with both the web and Email platforms.
They do appear to be moving in the direction of providing a first class services but it looks like we are some way off. Still no PHP5 in sight for example
Everything else is great though.
Might be worth looking elsewhere for a hosting company for your Email and website with the cash you've saved switching to Plusnet for Broadband?
I myself moved my Email (apart from some newsletter subscriptions) and website out a few years back and am glad I did do as there have been continued problems with both the web and Email platforms.
They do appear to be moving in the direction of providing a first class services but it looks like we are some way off. Still no PHP5 in sight for example
Everything else is great though.
Might be worth looking elsewhere for a hosting company for your Email and website with the cash you've saved switching to Plusnet for Broadband?
I could do with an update - not by email (its still not working).
Hopefully someone is tasked with getting my email working and not puzzling over the script that disabled it in the first place. That can come after my domains are functional again - please?
Actually I've figured out why it happened (paranoid mode on):
Anyone who wants to get taken off Postini gets their email totally screwed for a couple of days so the word goes round and nobody wants to take the risk. Better losing the odd email than the lot.
C'mon - own up...
I've had no more complaints about bounced email today and all the mx records seem to be pointing to the right place.
Thanks for getting me off Postini.
Hopefully the move back once the appropriate controls are available will be less dramatic!
I have a question:
The spam control options in my member console - are they linked into Postini and therefore inactive as far as my account is concerned (since my email no longer goes through that loop)?
Just curious...
Thanks for getting me off Postini.
Hopefully the move back once the appropriate controls are available will be less dramatic!
I have a question:
The spam control options in my member console - are they linked into Postini and therefore inactive as far as my account is concerned (since my email no longer goes through that loop)?
Just curious...
Quote from: Bob
Quote from: Firejack They do appear to be moving in the direction of providing a first class services but it looks like we are some way off. Still no PHP5 in sight for example
Have you seen the thread over on TBB here?
Yes thanks Bob. It's just a pity that such a Topic gets a better response on TBB than in the Community or PUG forums. JELV has been particularly active for some time in pushing for a Timeline for changes. I understand that a solution is now under discussion - but time is passing and lack of a solution will have a knock on effect on the proposed implementation of a User development area on the Community. Most SDK's and PHP Classes are now PHP5.
An outline of planned activities would be very helpful.
Ta.
Maurice
Whilst I don't (at present) have any use for PHP,
What was Plan A?
What benefits does/did the custom kernel give?
What was Plan A?
What benefits does/did the custom kernel give?
Plan A and Plan B are similar. If plan B comes off you will appreciate why I'm being cagey about it. - It's nothing sinister, and you can probably read between the lines, but I hope you can appreciate that I only don't say things when there are commercial sensitivities, and here there are.
The custom kernel means we can offer the CGI service in the way we do, and keep the service secure in an environment where 10K+ users all access one platform. Giving people access to things like a proper SSH shell and loads of other stuff in a jailed, resilient way was why the decision was made to build it like we did. Remember that was done in the days when systems like Plesk and ISPconfig were significantly less mature than now, and as such there weren't any other options.
If we were to rebuild from scratch today then we would do it very differently certainly. However, as we have many thousands of live customer sites to support, rebuilding from scratch isn't the most compelling of options. It could come to that but personally I hope it doesn't, given the time that it would take to get a new solution right. As has been said, that's time we don't really have.
For now, I'll continue to work on solving the underlying problem. When I can say more, I will.
Ian
- It's nothing sinister, and you can probably read between the lines, but I hope you can appreciate that I only don't say things when there are commercial sensitivities, and here there are. The custom kernel means we can offer the CGI service in the way we do, and keep the service secure in an environment where 10K+ users all access one platform. Giving people access to things like a proper SSH shell and loads of other stuff in a jailed, resilient way was why the decision was made to build it like we did. Remember that was done in the days when systems like Plesk and ISPconfig were significantly less mature than now, and as such there weren't any other options.
If we were to rebuild from scratch today then we would do it very differently certainly. However, as we have many thousands of live customer sites to support, rebuilding from scratch isn't the most compelling of options. It could come to that but personally I hope it doesn't, given the time that it would take to get a new solution right. As has been said, that's time we don't really have.
For now, I'll continue to work on solving the underlying problem. When I can say more, I will.
Ian