Hi,

I would like to test that our Secondary MX server to make sure that it is
working correctly. When I send email, is there a way to force it to the
secondary mx server by putting something in the the header of the email or
something like that?

Thanks,

Jimmy

jimmy [at] NOSPAMsoundzmedia.com wrote:

> Hi,
>
> I would like to test that our Secondary MX server to make sure that it is
> working correctly. When I send email, is there a way to force it to the
> secondary mx server by putting something in the the header of the email or
> something like that?
>
> Thanks,
>
> Jimmy
>
>
Configure a mail client to submit directly to your secondary?

--
Clem
"If you push something hard enough, it will fall over."
- Fudd's first law of opposition

jimmy [at] NOSPAMsoundzmedia.com wrote:
> Hi,
>
> I would like to test that our Secondary MX server to make sure that it is
> working correctly. When I send email, is there a way to force it to the
> secondary mx server by putting something in the the header of the email or
> something like that?

When I want to force mail to be sent to a secondary mail exchange
(mainly for testing), I use the % [at] routing method. Of all the routed
mail address method available, it's the only one I can ever remember how
it works.

Like: user%domain.com [at] non-primary-mx-of.domain.com

Will send first to: non-primary-mx-of.domain.com, then will be treated
by that machine based on the user%domain.com part.

Routed address may not work very well in all case, it is worth a try.
Check the headers and logs to confirm it works.

jimmy [at] NOSPAMsoundzmedia.com wrote:
> I would like to test that our Secondary MX server to make sure that it is
> working correctly. When I send email, is there a way to force it to the
> secondary mx server by putting something in the the header of the email or
> something like that?

Since you'll probably want to check your MXes from an offsite machine,
how about temporarily giving that machine host routes for the primary
MX's IPs that lead nowhere, or shutting communication with the primary
MX down by means of firewalling? Should be the closest thing to an
actual primary MX failure, even including the failover timeout ...

Regards,
J. Bern