Depending on incoming vs. outgoing --- just create a content filter w/ alt-mailhost... and then also be sure to create an SMTP route for that alt-mailhost domain...
Similar to --->
SMTP route --->
In my example --- I'm not really routing anywhere --- so, I am using /dev/null.
Testing --- standard SMTP telnet --->
mail from: harry@flip.com
250 sender <harry@flip.com> ok
rcpt to: robsherw@cisco.com
250 recipient <robsherw@cisco.com> ok
data
354 go ahead
subject: THIS IS A TEST
HELLO
.
250 ok: Message 202 accepted
Watching mail_logs --->
Tue Apr 29 18:11:36 2014 Info: MID 202 ICID 610 From: <harry@flip.com>
Tue Apr 29 18:11:41 2014 Info: MID 202 ICID 610 RID 0 To: <robsherw@cisco.com>
Tue Apr 29 18:11:49 2014 Info: MID 202 Subject 'THIS IS A TEST'
Tue Apr 29 18:11:49 2014 Info: MID 202 ready 153 bytes from <harry@flip.com>
Tue Apr 29 18:11:49 2014 Info: MID 202 matched all recipients for per-recipient policy DEFAULT in the inbound table
Tue Apr 29 18:11:49 2014 Info: MID 202 interim verdict using engine: CASE spam negative
Tue Apr 29 18:11:49 2014 Info: MID 202 using engine: CASE spam negative
Tue Apr 29 18:11:49 2014 Info: MID 202 Outbreak Filters: verdict negative
Tue Apr 29 18:11:49 2014 Info: MID 202 queued for delivery
Tue Apr 29 18:11:49 2014 Info: Delivery start DCID 0 MID 202 to RID [0]
Tue Apr 29 18:11:49 2014 Info: Message done DCID 0 MID 202 to RID [0]
Tue Apr 29 18:11:49 2014 Info: MID 202 RID [0] Response '/dev/null'
Tue Apr 29 18:11:49 2014 Info: Message finished MID 202 done
Message is sent where I wanted it... /dev/null.
I hope this helps!
-Robert
(*If you have received the answer to your original question, and found this helpful/correct - please mark the question as answered, and be sure to leave a rating to reflect!)
