"rgjawanda" wrote:
I just spent an hour on the phone with my provider. They finally admitted that the megamailserver.com was their mail hosting solution and that they pointed the 3 MX records for my domains were pointing there.
ie: mail was always going to their servers
They only admitted this after I yelled at them and told them that I could prove it with my mail headers from their hosting service to yahoo. They didn't even want to look at the headers and they said "ok.. it is ours". Not sure why they didn't want to admit it.
el bastados, I knew it.
I told them to change the MX records to point to my mail server. This is where I sort of get lost because I am not an admin (but may be shortly if I keep having all these problems because I am learning a lot).
I told them MX=mail.itpartners.ca
Now I have to figure out how to do that .
I have a router that I changed the hostname to (mail) and the domain to itpartner.ca
do you think this will work. They put that in the MX records. Im not actually sure what MX records are.
Yeah, MX are a pain, and you better hope they support a "SPF" text record, or your mail will get filtered in yahoo, and probably numerous other mail providers, as bulk or spam, but I would at least get the first part, i.e. the MX working first before you worry about that.
MX=mail.itpartners.ca, should work
yeah, I get a little lost on the hostname, domain name, etc also.
you could name your server mail
or name it mail.itpartners.ca
might work with your router, but your adding another layer of complexity, you might get it working without the router if possible first, if possible
heres an example of our MX records(tweaked)
C:\Documents and Settings\user1\Desktop>nslookup
Default Server: ns2.ph.cox.net
Address: 68.2.16.25
>
> set type=mx
> domain.com
Server: ns2.ph.cox.net
Address: 68.2.16.25
Non-authoritative answer:
domain.com MX preference = 1, mail exchanger = mail.yourhostingaccount.com
domain.com nameserver = b.ns.interland.net
domain.com nameserver = c.ns.interland.net
domain.com nameserver = a.ns.interland.net
a.ns.interland.net internet address = 64.226.28.33
b.ns.interland.net internet address = 209.237.137.10
c.ns.interland.net internet address = 64.77.127.42
>
> mail.domain.com
Server: ns2.ph.cox.net
Address: 68.2.16.25
Non-authoritative answer:
mail.domain.com MX preference = 1, mail exchanger = mail.domain.com
domain.com nameserver = b.ns.interland.net
domain.com nameserver = c.ns.interland.net
domain.com nameserver = a.ns.interland.net
mail.domain.com internet address = 216.122.169.143
a.ns.interland.net internet address = 64.226.28.33
b.ns.interland.net internet address = 209.237.137.10
c.ns.interland.net internet address = 209.237.137.10
>
>
> my.domain.com
Server: ns2.ph.cox.net
Address: 68.2.16.25
Non-authoritative answer:
my.domain.com MX preference = 1, mail exchanger = my.domain.com
domain.com nameserver = a.ns.interland.net
domain.com nameserver = b.ns.interland.net
domain.com nameserver = c.ns.interland.net
my.domain.com internet address = 216.122.169.142
a.ns.interland.net internet address = 64.226.28.33
b.ns.interland.net internet address = 209.237.137.10
c.ns.interland.net internet address = 64.77.127.42
the first lookup, is our corporate mail, which is currently hosted elsewhere
the second lookup, is going to be our corporate mail, when we get it going, it will be hosted on a server that has 10 ip addresses bound to 1 NIC, note the associated IP addy
the third lookup, is our application mail server, it is live, and works, and it is bound to same NIC, but a different IP
you can have several Mail Exchange records, you can order them by priority/preference for redundancy
whole point, and may help you figure out issues with you router experiment, the mail server, that connects to gmail, must not lie about it's IP address or name, as well, the connection it creates to server, i.e. actual connection over NIC, must also be using the IP that is listed in the MX record
the my.domain.com, as well as mail.domai.com, both work, the only issue i have, as stated previously, is a bug in the ristretto pkg, which will probably affect you also, the bug is caused by ristretto, just grabbing the wrong ip, if you have multiple IP's, which it then communicates to the other mail server. in your case, it will probably grab the 192.168.X.X as it is doing, this shouldnt be a problem, at least the mail shouyld go through,
but gmail will classify it as bulk, hence those two headers x-originating-ip and x-bulk whatever...
but I would worry about that later
So I now see light at the end of the tunnel.
They say it won't be stopped until 24 hours.
Thanks GOD and Jason Glass
Or maybe they are one in the same :)
Awe shucks, thanks. Pleasure to be of assitance, and remember me, if I am ever out of work(or if you need any contract work!)!
Later Man
