[BlueOnyx:11049] Re: Why does mx record override Smart Relay host?

[Dogsbody]

Apologies if you know this but it isn't clear from your message so I 
want to check...

A smart relay uses MX records.  A lot of people don't know this and in 
some cases an A record can work but it is designed for and is supposed 
to use MX records.

If you need to use mx.example.com for something else then use whatever 
you like (smarthost.example.com) as the smarthost entries and change it 
in the GUI.

It's actually really handy being able to use MX records for the 
smarthost as you can use the priority values to create backups so there 
isn't a single point of failure.

Dan

On 30/07/2012 20:17, Chad Bersche wrote:
> I recently updated my DNS provider, and as part of that update, the DNS
> provider created mx host entries (i.e. mx.domainname.com) that pointed
> to their mail forwarding service (which I do use).  However, the odd
> thing is that after this happened, I noticed in my outgoing mail log
> that the relay host is now using mx.domainname.com rather than the Smart
> Relay host that I had set up (and which I want outgoing mail routed
> through at my ISP).
>
> Why is sendmail using relay=mx.domainname.com (in maillog) when a
> different Smart Relay host has been set up?  This seems incorrect,
> especially since I have specified a smart relay host.  I've hacked
> around it for right now with a local DNS entry that points
> mx.domainname.com to the IP address of my smart relay host, but that's a
> true hack, and one that I don't think I should have to make.  I also
> need to keep the mx.domainname.com entries in my DNS so that my external
> mail fowarding/spam filter can process the mail before it routes to me...

-- 
Find me online : http://www.dogsbody.info/