Hosting Mail on a different server.

I have a question before I jack up my DNS settings

I am bringing another client site to discountasp, but they want to keep their mail services with their ISP. They have a good relationship with their ISP (Redwire), whohandles extremely large email attachments for the client (print shop that gets large art files).

After finding out who the registrar was, I went in to update the DNS, to point everything to DASP except the MX record (keeping at Redwire). Problem is, they dont seperate out the MX record... all I can do is specify DNS by subdomain (*.telecardinc.net). I sent them an email, and they said email the hosting company. Personally, I think it should be done at the registrar level, but oh well.

I've looked in the DASP control panel, and see where i can update the MX records, etc. My current plan is to log into the registrar, point the entire domain (including MX, as I can't seperate it) to DASP, and then point the MX to Redwire from DASP.

A) Does this sound right?

B) Do I need toadjust either the imap., pop3., or smtp. in the DNS control panel?

C) How long does it take for changes in the DNS control panel to take place? There's nothing that's actually propogating, the info is staying on a DASP server, correct? Im asking because I want to first make the DNS change here and make sure it is in place before I forward the entire domain here from the registrar, minimizing mail downtime.

Thanks for any help... haven't had to seperate out sections of the domain like this before.

Mike Reilly

 

All you should have to do is point your MX records to them. I think they have given you bad information.

You need to find out what the name of their mail server is ie mail.whathost.com and create an mx record like this...

(assuming your domain is abc123.com)

domain name destination
abc123.com mail.whathost.com


Joel Thoms
DiscountASP.NET
http://www.DiscountASP.NET

 

OK, I logged into OpenSRS.net and updated my primary and secondaryDNS to ns1/ns2.discountasp.com


In the DASP DNS manager, I have updated the MX record for telecardinc.net to point to postal.redwire.net (confirmed MX server name with them).


Now I get this message when I attempt to send mail...



Delivery to the following recipient failed permanently:
[email protected]
Technical details of permanent failure:
PERM_FAILURE: SMTP Error (state 9): 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)</BLOCKQUOTE>
What have I done wrong? How do I troubleshoot the location of the error? In theory, nothing should've changed on Redwire's end, I never "stopped" services, I simply pointed the domain to DASP and pointed the MX from here to Redwire.

I've got to get this figured out, as their customers are now getting messages bounced.

Mike

 

Hmmmm...



I havechecked NSLOOKUP and CheckDNS.net, and both show that the MX record IS pointing to postal.redwire.net, but I am still getting errors. I have a support request into them as well, as I think it's probably on their end. But if anybody here has any input, I'd appreciate it!


Mike

 

http://www.yuki-onna.co.uk/email/smtp.html

go to this url. Telnet to port 25 of their smpt server and try to manually send the email.

What are the results of this send?


Where do you see this error message and what are you doing to get it?


Joel Thoms
DiscountASP.NET
http://www.DiscountASP.NET

 

I'm having a similar problem. Even though I've added a new mx record with the mail server I want to use and removed the two default mail servers (mx1.internetmailserver.net and mx2.internetmailserver.net) I still get returned mail frommta00 or mta01.internetmailserver.net telling me it can't find the account I'm sending mail to. Of course it can't - I never set it up because I'm not supposed to be using that mail server! Is there some other setting I need to do to make it actually use that mx record? Is there some kind of caching I've got to get around? I did create a ticket for this, but thought I'd post here too in case some other regular user type person has had the same issue and found a fix.