General Questions

HSPHERE Accounts:

1) Do you allow subftp?

2) What type of email redundancy do you have in place? If the mail server were to crash, would email bounce or is there a relay in place that would capture mail until a secondary server kicked in?

Here is a response I got from DIY:
<< The primary mail server can handle approx. 24k emails per day, without breaking a 0.2 load because of it's write-speed. When it gets to the point where the mail server starts breaking past 30k emails per day, we'll add another duplicate mail server (mail2.)

The moment the main mail server becomes unresponsive, traffic immediately goes to the backup(s).

It's done at router level, so it's rather easy to do. If one block becomes unresponsive, the router/firewall/balancer will realise it has to reroute the calls to the backup mail server, which has all settings from the primary, sent there three times a day.
>>

Do you do something like this???

3) Is Hard disk space based on usage or allocation?

4) Do you have clients that utilize DotNetNuke? And if so how does it run on your windows servers?

5) Do you have any limits on the number of emails that can be sent at a time or during the day? I don't ask because I plan to spam, but I have a customer that on occasion sends out 1000 emails as a part of our church newsletter. Everyone has agreed to receive the email.

6) Several hosts I have been at routinely have to reset IIS or restart the web server saying that there is bad code on one of the clients domains.

Is this something has to be dealt with regularly at JodoHost?
How do you handle these types of problems?

7) What applications / objects do you have installed on each of your servers? Do you have a script that we can run to see what exists?

Thanks

1) Do you allow subftp?

# Yes, In Hsphere you can create additional sub-ftp accounts for linux from control panel itself. For windows you need to create a ticket to get additional ftp account (1-2 sub-ftp accounts/domain is allowed).

2) What type of email redundancy do you have in place? If the mail server were to crash, would email bounce or is there a relay in place that would capture mail until a secondary server kicked in?

Here is a response I got from DIY:
<< The primary mail server can handle approx. 24k emails per day, without breaking a 0.2 load because of it's write-speed. When it gets to the point where the mail server starts breaking past 30k emails per day, we'll add another duplicate mail server (mail2.)

The moment the main mail server becomes unresponsive, traffic immediately goes to the backup(s).

It's done at router level, so it's rather easy to do. If one block becomes unresponsive, the router/firewall/balancer will realise it has to reroute the calls to the backup mail server, which has all settings from the primary, sent there three times a day.
>>

Do you do something like this???

# Yes, we also have a secondry mail server to take over in case primary fails.

3) Is Hard disk space based on usage or allocation?

# Usage based.

4) Do you have clients that utilize DotNetNuke? And if so how does it run on your windows servers?

# Yes, Infact we are one of the most popular DNN host. Clients just installs DNN and we set necessary permission for their DNN site.

5) Do you have any limits on the number of emails that can be sent at a time or during the day? I don't ask because I plan to spam, but I have a customer that on occasion sends out 1000 emails as a part of our church newsletter. Everyone has agreed to receive the email.

# Yes, 100 email/domain/day. But if you fill mass mail disclaimer that restriction is waived off for that domain. The form is located at http://support.jodohost.com/showthread.php?t=3708

6) Several hosts I have been at routinely have to reset IIS or restart the web server saying that there is bad code on one of the clients domains.

Is this something has to be dealt with regularly at JodoHost?
How do you handle these types of problems?

# On a shared server it is not uncommon to have bad codes. If that kind of code is found, that site is put in isolated pool and customer is informed to correct his code.

7) What applications / objects do you have installed on each of your servers? Do you have a script that we can run to see what exists?

# Most of the components are mentioned at our site for each operating system under their respective shared plan page. If you need specific information on anything you can send us a mail at sales @ jodohost.com (without spaces around @)

<< # Yes, we also have a secondry mail server to take over in case primary fails. >>

I think I am going to need more detail.

1) If the primary server fails... is their an immediate failover to another server without any down time??

2) If the second server does not come online immediately... meaning it requires Jodo to put it in place, then what happens to the mail that is trying to be delivered to us during the down time? Unless you have a relay server or something that kicks in we will lose email.

Please give as much detail as you can in regards to this please.

sure.. I will be glad to share that information with you

If primary fails, mails get queued on secondary server with high priority MX. Meanwhile we up the standby mail server. In this way mails could delay (a bit) but no mail is lost.

LookingForHost said:

2) If the second server does not come online immediately... meaning it requires Jodo to put it in place, then what happens to the mail that is trying to be delivered to us during the down time? Unless you have a relay server or something that kicks in we will lose email.

Click to expand...

Any decent delivering mailserver will attempt to transmit the email at a later time if the error is of a temporary nature. It will keep doing this for at least a day in most mail configurations.
Being unable to connect to the remote server is one of those temporary errors. (if it does connect to the server, but the server says the mailbox doesn't exist, that would be a permanent error and the mail would immediately bounce)

SubSpace said:

Any decent delivering mailserver will attempt to transmit the email at a later time if the error is of a temporary nature. It will keep doing this for at least a day in most mail configurations.
Being unable to connect to the remote server is one of those temporary errors. (if it does connect to the server, but the server says the mailbox doesn't exist, that would be a permanent error and the mail would immediately bounce)

Click to expand...

Yes... I understand this, but some places do not have it set for that long.... plus I would rather have it queued up instead of bouncing back. When we get mail bounced back we are told that it has bounced back and will continue to attempt delivery for x amount of time. I just don't want folks seeing that...

The problem comes when they are trying to get a new unit in place and they have problems or that server fails... again delaying the time to get the system online. It has happened!

Ok,

From what I understand here.

When the primary mail server fails, jodo up's the secondary mail server.

This seocndary mail server works prefectly with all of our email accounts, in case the primary does not come up for hours.

for example:

primary fails, how long to get the secondary up and running with all emails. working properly

if worst case scenario happens primary fails and crashes. What would happen to all the imap email on there.

If I am not understanding please correct me.

Thank you,

Erik