CEO wrote:
I guess it would be best to start setting all my clients MX records to my
server.email.com then.
And not worry about the headers so the TLS will validate etc.
Thanks Guys,
They can all have their own MX records. You just have to set a default
domain for the machine to answer the HELO and SMTP messages as, as well
as say who the error message is being generated by.
I have a server that has 25 or so domains pointed to it. Each domain
has it's own MX record that all point to the same IP address and
everything is fine. When they do get an error message from my machine
it uses my domain name and they know they can contact me for more
details or if there is a problem.
The TLS cert will just be for your default domain. It doesn't matter if
you use server.email.com for your default domain - you can still accept
messages for bobsyouruncle.com or whoever. TLS will just be established
using the server.email.com cert which is perfectly acceptable.
The only people that see the SMTP/HELO responses are those that look in
the headers (and as Phil said most of them don't even know they exist)
and someone like me who reads the logs.
---------------------------------------------------------------------
QmailToaster hosted by: VR Hosted <http://www.vr.org>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
