Results 1 to 8 of 8
  1. #1
    Join Date
    Aug 2002
    Location
    Lakeland, Florida
    Posts
    99

    Question Help setting up an offsite mail server using Plesk 7.5 Windows

    I've got a client that wants to host with me however they want to run their own off-site mail server. I've never set this up before using Plesk (7.5.6) for Windows and I was wondering if anyone might be able to point me in the right direction.

    Since I won't be hosting the mail server but I will be the NS, I'm assuming my MX records will need to point to the correct mail server. The current offsite MX records are:

    0 mx1.mysuperpageshosting.com. [TTL=14400] IP=64.29.145.105 (No Glue) [TTL=60523] [US]
    20 mx2.mysuperpageshosting.com. [TTL=14400] IP=64.29.145.110 (No Glue) [TTL=60523] [US]
    30 mx3.mysuperpageshosting.com. [TTL=14400] IP=64.29.145.111 (No Glue) [TTL=60523] [US]
    40 mx4.mysuperpageshosting.com. [TTL=14400] IP=64.29.145.112 (No Glue) [TTL=60523]

    I've done this a long time ago on Linux/Cpanel so I think I understand the basic concept (then again, you never know). I guess the problem is I'm unable to enter the above settings (mx1.mysuperpageshosting.com) when editing the DNS records for the account via Plesk. It only lets me apply x.domain.com (eg. mail.domain.com) for mx records.

    This leads me to think I'm going about this the wrong way. Can anyone offer any insight? I just found out about this and they want to go live this weekend.

    Thanks

  2. #2
    Join Date
    Aug 2002
    Location
    Lakeland, Florida
    Posts
    99
    Just a quick bump.

  3. #3
    Join Date
    May 2006
    Location
    Florida, USA
    Posts
    362
    The simplified answer:

    MX = mail.thedomain.com
    A record mail.thedomain.com = the.destination.IP.address of your client.

    Basically, point the MX to the domain (it doesn't have to be mail.thedomain.com.... it could be mywebmail.thedomain.com if you want) but then you have to point that to the final destination mail server IP.

    Hope that helps.
    Host, YES!
    Reselling? Partner for profit instead!

  4. #4
    Join Date
    Aug 2002
    Location
    Lakeland, Florida
    Posts
    99
    Thanks. I assumed that's what I had to do and did set it up this way. The only problem I'm having now is that mailenable Pro is still trying to handle mail for the account. Because of this it's bouncing messages sent to any email account handled by the offsite mail server:

    "Diagnostic-code: smtp;550 Requested action not taken: mailbox unavailable or not local"

    Since the DNS is still propping, I can't verify for certain that it's being handled the way it should. But regardless, here's the DNS i used where client.com is my client and myhost.com is me.

    123.123.123.123 / 24 PTR Client.com.
    ftp.Client.com. CNAME Client.com.
    mail.Client.com. A 64.29.145.111
    Client.com. A 123.123.123.123
    mail.Client.com. MX (0) mx1.mysuperpageshosting.com
    Client.com. NS ns1.myhost.com.
    Client.com. NS ns2.myhost.com.
    mssql.Client.com. A 123.123.123.123
    sitebuilder.Client.com. A 123.123.123.123
    webmail.Client.com. A 123.123.123.123
    www.Client.com. CNAME Client.com.

  5. #5
    If you login to Plesk and go to the domain and click the mail icon you should see a disable button. Click this just to disable the mail services on your server for this domain.
    Paul Carter | ehosting Limited
    Domain Registration, Windows and Linux Shared hosting, Virtuozzo based VPS, and Dedicated Servers

  6. #6
    Join Date
    Aug 2002
    Location
    Lakeland, Florida
    Posts
    99
    Well it looks like my client is able to receive email from 3rd parties and they can see the site so DNS is propigated for them (it would seem).

  7. #7
    Join Date
    May 2006
    Location
    Florida, USA
    Posts
    362
    Here's what jumps out at me:

    123.123.123.123 / 24 PTR Client.com.
    ftp.Client.com. CNAME Client.com.
    mail.Client.com. A 64.29.145.111
    Client.com. A 123.123.123.123
    mail.Client.com. MX (0) mx1.mysuperpageshosting.com
    Client.com. NS ns1.myhost.com.
    Client.com. NS ns2.myhost.com.
    mssql.Client.com. A 123.123.123.123
    sitebuilder.Client.com. A 123.123.123.123
    webmail.Client.com. A 123.123.123.123
    www.Client.com. CNAME Client.com.
    try it like this:

    123.123.123.123 / 24 PTR Client.com.
    ftp.Client.com. CNAME Client.com.
    mail.Client.com. A 64.29.145.111
    Client.com. A 123.123.123.123
    Client.com. MX (0) mail.client.com
    Client.com. NS ns1.myhost.com.
    Client.com. NS ns2.myhost.com.
    mssql.Client.com. A 123.123.123.123
    sitebuilder.Client.com. A 123.123.123.123
    webmail.Client.com. A 123.123.123.123
    www.Client.com. CNAME Client.com.

    If you are sending mail from the server itself (online email or script based email), then you might also need to do what PaulC-ehosting recommended.
    Host, YES!
    Reselling? Partner for profit instead!

  8. #8
    Join Date
    Aug 2002
    Location
    Lakeland, Florida
    Posts
    99
    Ahh, I see what I did. Thanks. I think this fix should work.

    /Crosses fingers.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •