Email server setup question..

[rabbidrabbit]

OK.

The mail server is win2003 and is not on a domain. Its name is www1.
For DNS and Imail (the mail server) setup fully qualified domain name I entered mail.mydomain.com.

When I send to a user@mydomain.com I get the error, 550 error xx.xx.15.14 does not like recipient.  When I send to user@mail.mydomain.com it goes through. I'm assuming at this point I should just reset the DNS and Imail setup to mydomain.com and drop the mail..

Is this the trick? I assume I don't need the www1.mydomain.com entered anywhere.

thanks!

one last question.. doesn't that mess up web access?

sorry about being so newbish.. like I said its my first mail server....

[AKcurly]

Originally posted by rabbidrabbit
OK.

The mail server is win2003 and is not on a domain. Its name is www1.
For DNS and Imail (the mail server) setup fully qualified domain name I entered mail.mydomain.com.

When I send to a user@mydomain.com I get the error, 550 error xx.xx.15.14 does not like recipient.  When I send to user@mail.mydomain.com it goes through. I'm assuming at this point I should just reset the DNS and Imail setup to mydomain.com and drop the mail..

Is this the trick? I assume I don't need the www1.mydomain.com entered anywhere.

thanks!

one last question.. doesn't that mess up web access?

sorry about being so newbish.. like I said its my first mail server....

I guess I'm confused.  If you don't have a registered domain, who is doing your routing?  I guess they could send e-mail to rabid-rabbit@198.17.44.233 (or whatever.)  However, if the address block assigned to you isn't routed by your ISP, then even that won't work.

Who provides your DNS?  It makes no sense to set DNS to mydomain.com unless mydomain.com is prepared to resolve dns queries.

curly

[rabbidrabbit]

the "mydomain.com"  is a generic way of putting in a placeholder for a real domain you don't want to punch up on a message board...>

The domain is registered and I have the a and MX records pointing to mail."mydomain.com" now.  Does this make more sense?

The gut of the question is how do I set up my mail server on a domain.  By Domain I don't mean an internal network Domain rather, I mean a mydomainname.com Domain.

What I have now is the fully qualified domain name as mail."mydomain.com" but this is messing up the routing to the mail server.

[AKIron]

I'd add an "a" record for mail.mydomain.com, then point the mx lookup to that.

[rabbidrabbit]

yup... its pointing to the mail."mydomain.com" . it seems to get there when i address the email to user@mail."mydomain.com" but not when the email is addressed to user@"mydomain.com".  I'm trying to make it work on the later but am not sure how I could check mail via the web if i set everything to "mydomain.com".  Does this makes sense ?

[AKIron]

Not sure what you mean by "set everything". You might try an "a" record using the actual name of your server. An mx lookup pointing to that name should work. Do you have mx pointers to other servers?

[rabbidrabbit]

the actual name of the server, both web and mail is www1.  Should i have the MX and A records point to www1."mydomain.com"?   If I do this won't i have to address the email to user@www1."mydomain.com"?

[AKIron]

No, you should be able to address mail to user@mydomain.com. The "a" record(s) are machines in the domain "mydomain.com". The mx lookup is referenced for email delivery.

[rabbidrabbit]

OK, I may well have it mixed up a bit.  Here is whats in place now.

A records:

"mydomain.com"
mail."mydomain.com"
http://www."mydomain.com"

all point to the IP address of the web/mail server.

the MX record points to

mail."mydomain.com"

in doing this I run into the issue above..  any pointers?

[AKIron]

Hmmmm, should work. You're not expecting any changes you make to be effective immediately right? They usually take several hours and sometimes days to be effective. The quotes are for our benefit right, and not actually used?

If you'll email me the actual domain name I'll take a look at your settings.

[rabbidrabbit]

ya.. the quotes denote the not actual name...


I'm expecting a 24 hr TTL to make changing DNS entries a slow progress.  What I'm seeing with this is the email getting rejected with this "550 error xx.xx.15.14 does not like recipient" when I'm sending to user@"mydomain.com" but it works when I address it to user@mail."mydomain.com"

[AKIron]

Originally posted by rabbidrabbit
ya.. the quotes denote the not actual name...


I'm expecting a 24 hr TTL to make changing DNS entries a slow progress.  What I'm seeing with this is the email getting rejected with this "550 error xx.xx.15.14 does not like recipient" when I'm sending to user@"mydomain.com" but it works when I address it to user@mail."mydomain.com"

It could be the server rejecting the email. I'm not familiar with the email server you are using. That is why I suggested using the name of the actual server in the "a" record which you are, but also point the mx lookup to that name.

[rabbidrabbit]

ya.. thats what I'm saying.. the server rejects the email pointing to just "mydomain.com" but lets it through when is send the email to mail."mydomain.com".


the mail server is Imail...

what I'm hoping to have is email addressed to user@"mydomain.com" to go through while being able to check mail via the web.

[AKIron]

Sounds like it should work. Sometimes it's something simple overlooked. Send me the domain name and I'll be glad to look. Nothing that anyone else on the web can't do if they know the name.

[AKIron]

Are you familiar with the send mail commands while telnetted into a server? You may want to troubleshoot using this method, can help you quickly determine if it's a dns issue or a server configuration issue.

This should get you started if you're unfamiliar with them:
http://www.cs.cf.ac.uk/Dave/PERL/node175.html