Alt-Mailhost / SMTP Routes Question...

Hi All,
I have a query on SMTP routing when using the Alt-Mailhost command in a Message Filter...
Our configuration in overview is two Ironport devices (C650's at AsyncOS 6.4) at separate sites, configured as a cluster (all config is common across sites). At each site, there also exists a 3rd party mail host.
So, I have a message filter which selects messages based on some criteria and I also know which Ironport received it. When I have a match, I want to route this message to the 3rd party mail host on the _local_ site......but if that mail host is down, I want to route it to the 3rd party mail host on the other site. Simple as that!
At the moment, my Alt-Mailhost command looks like this;
<message has been selected> {
<if "Site A" Ironport used> {
alt-mailhost('bogusdomain1.net');
<else>{
alt-mailhost('bogusdomain2.net');
...in my SMTP Routes I'd _like_ to have this;
bogusdomain1.net     <3rd-Party-Box-at-Site-A>, <3rd-Party-Box-at-Site-B>
bogusdomain2.net     <3rd-Party-Box-at-Site-B>, <3rd-Party-Box-at-Site-A>
...but this doesn't work because multiple hosts in an SMTP route are tried in numerical / alphabetical order...no matter what order you put them into the SMTP Route definition (is this a bug?)....so in reality, they both have to look like this;
bogusdomain1.net     <3rd-Party-Box-at-Site-A>, <3rd-Party-Box-at-Site-B>
bogusdomain2.net     <3rd-Party-Box-at-Site-A>, <3rd-Party-Box-at-Site-B>
..which is no use.
My only other idea is that I could just have this in the SMTP Routes for those domains;
bogusdomain1.net     USEDNS
bogusdomain2.net     USEDNS
...and configure my DNS with the above domains, such that there really _is_ a difference in the order of the MX for those domains.
So my question is, how can I do this without using 'USEDNS' and the associated DNS config...i.e. just via the Ironport devices?
Hope the collective can help!
Cheers, Chris.

Check out the latest release notes...
Enhanced: Prioritized SMTP Routes
AsyncOS 7.0 allows you to prioritize the destination hosts for your SMTP routes. AsyncOS will attempt to deliver the message to a destination host in order based on priority. Destinations with identical priority will be used in a “round-robin” fashion.

Similar Messages

  • Ironport alt-mailhost filter and bounced emails.

    Hello!
    I have problem with ironport configuration and hope someone help me )
    I use filter with alt-mailhost rule for users within domain but located on another server.
    It's work fine. But... i have problem with bounced emails. They don't affected by filter and use smtp route.
    How to attach my filter with bounced emails?
    Thanks for any help.

    Hello,
    bounce email messages are handled outside the work queue so they are not subject to Message Filter or Content Filter processing. Only SMTP routes will apply here, an alt-mailhost action is not possible.
    The only possible workaround would be to loop the delivered bounce message over the appliance again (e.g an SMTP route that points to a secondary listener on the appliance), so that it can be reprocessed by alt-mailhost. Please note that looping certain messages over the appliance again bears the risk of an endless mail loop so you may need to adjust your filters accordingly to prevent this.
    Hope this helps. If not, please let us know.
    Regards,
    Martin

  • Alt-Mailhost Query

    Hi, I need to re-route inbound messages from a certain domain to an alternative internal IP address. Looks easy enough to do with the alt-mailhost action, but there’s a line in the IronPort help file that confuses the issue slightly:
    “Note that any additional routing information specified by the smtproutes command still affects the routing of the message”
    I have 2 static inbound SMTP routes defined for our domain – what I need to do is override this for one specific sender domain. Will alt-mailhost do this or will it be overridden by the SMTP routing table?
    Any advice appreciated.

    The "smtproutes" will get the last say in routing.
    With alt-maillhost(), you may want to try and send it directly to the internal IP address.
    From our Advance User Guide:
    Alter Delivery Host Action
    The alt-mailhost action changes the IP address for all recipients of the selected message to the numeric IP address or hostname given. The following example filter redirects recipient addresses to the host example.com for all messages.
    localRedirectFilter:
    if(true)
    alt-mailhost('example.com');
    Thus, a message directed to [email protected] is delivered to the mailhost at example.com with the Envelope To address [email protected] Note that any additional routing information specified by the smtproutes command still affects the routing of the message. (See “Routing Email for Local Domains” on page 38.)
    local2Filter:
    if(true)
    alt-mailhost('192.168.12.5');
    Hi, I need to re-route inbound messages from a certain domain to an alternative internal IP address. Looks easy enough to do with the alt-mailhost action, but there’s a line in the IronPort help file that confuses the issue slightly:
    “Note that any additional routing information specified by the smtproutes command still affects the routing of the message”
    I have 2 static inbound SMTP routes defined for our domain – what I need to do is override this for one specific sender domain. Will alt-mailhost do this or will it be overridden by the SMTP routing table?
    Any advice appreciated.

  • SMTP routing table

    Hello,
    Solaris 8/ Iplanet Messaging Server 4.X
    Solaris 8 / SunOne Messaging Server 5.2
    My question is about SMTP routing table and for
    iMS4.x AND SMS5.2
    Question:
    In my SunOne Messaging Server 5.X I have 10 domains.
    mydomain0.com, mydomain1.com to mydomain9.com
    I try to have this:
    all peoples from mydomain0.com, send mail to internet,
    mail is send to smtp.relay0.com
    all peoples from mydomain1.com, send mail to internet,
    mail are send to smtp.relay1.com
    etc...
    And I have 10 relays
    Can I do this, and how (I don't see in documentation or
    FAQ)
    thank you
    Christophe Damoy

    is this entry valid for routing table in nms v 4.15 p6
    * : anotherhot.mydomain.com:5000
    assuming that my anotherhost is listening and accepting on port 5000 for smtp connections. and i wanna forward all the mails to that host
    regards
    Prashant

  • SMTP route priority

    Hi,
    I've a general question about SMTP routes. Suppose, that I've 3 SMTP routes
    - Domain foo.bar, configured via Network->SMTP routes
    - Domain *.foo.bar, configured via Network->SMTP routes
    - Domain foo.bar, configured via LDAP routing query
    Which one has the highest priority?
    Thanks,
    Axel

    LDAP routing has priority over static SMTP routes except in the instance where you have defined the ALL: route which then overrides LDAP.

  • TLS mutual authentication and Separate default SMTP routes per listener - IronPort c370

    Dear all ,
    We have two IronPort C370 ESAs , formed in a cluster.
    We are in a need to route e-mails targeted to a special group using TLS Required/Verify.
    I have two questions :
    1.  Is TLS mutual authentication possible on both incoming and outgoing ?
    2.  Due to the nature of the TLS need the existing listener cannot be used. So I created a new listener and respective filters to decide when the recipient requirements are met. The new listener is going to be configured with a policy specifying TLS required/verify. Problem is that  there is always a default SMTP route pointing specifically to a cloud service rather than directly to the Internet while for the new listener usedns is required. Is it possible to have two different default SMTP routes assigned to different listeners ?
    Thanks and kind regards ,
    Gino.
    PS : Please bear with me and questions. I am making my first steps in Iron Port administration.

    I have made some sort of progress but I would also like to have your expert opinions.
    I have came to understand that in order to present TLS mutual authentication for the incoming traffic I will just have to trust the sender(s) CA ( containing SANs etc for both the SMTP domain and the ESA itself ) while if I spread own SANs to the counterparts I will also have TLS mutual authentication on the outgoing traffic as well. Issue is that I will have to declare it in destination controls and it cannot be generic.
    Is there any way to make TLS required/verify with mutual authentication the default without having to set destination contol(s) ?
    As for my second question I have came to understand that the additional listener is not an aditional MTA and concequently I cannot have separate default SMTP route ( default = what is called as "ALL" in IronPort ). Still if anyone knows something more it would be really helpful if it was shared.

  • SMTP routing table does not seem to be working correctly.

    Why isn't the SMTP routing table working properly?
    <P>
    First, make sure you have the routing table setup correctly.
    Entries in the Routing table are in the following format:
    <P>
    <incoming recipient domain>:<route to this host>
    <P>
    For example, if you want all mail addressed to [email protected]
    to be routed to mailhost1.realdomain.com, you would add the following
    line to the SMTP routing table:
    <P>
    virtualdomain.com:mailhost1.realdomain.com
    <P>
    With the above option, any mail coming in addressed to <anyone>@virtualdomain.com
    will be routed to mailhost1.realdomain.com. The recipient email
    address will not be re-written, so mailhost1.realdomain.com needs to
    accept mail addressed to the original address, @virtualdomain.com,
    even though it is in realdomain.com.
    <P>
    Before adding, changing or deleting any SMTP routing table entries, double-check
    with the DNS Administrator that the host names you specify are valid,
    registered host names. If in doubt, you can use IP addresses for the
    "route to" host, but not for the "incoming recipient domain".
    <P>
    Wild cards can be used in mail routing table options, but they indicate that a
    hostname <B>will</B> fill that spot. For example:
    <P>
    *.domain.com:mailserver1.domain.com
    <P>
    In the above example, any mail addressed to <anyone>@<anyhost>.domain.com
    will be routed to mailserver1.domain.com. However, mail addressed to
    <anyone>@domain.com will not be routed. To fix this, add this
    line:
    <P>
    domain.com:mailserver1.domain.com
    <P>
    <B>Note:</B> You cannot use the SMTP routing table to route all mail
    addressed to a specific domain to a specific account. You would need to use
    a "Mail Pool" account for this, which is only available in Messaging Server
    3.5+.

    is this entry valid for routing table in nms v 4.15 p6
    * : anotherhot.mydomain.com:5000
    assuming that my anotherhost is listening and accepting on port 5000 for smtp connections. and i wanna forward all the mails to that host
    regards
    Prashant

  • Ironport back-up smtp routes

    Hi Guys,
    I have 2 lotus notes servers. Is it possible on the ESA to add these two servers on the SMTP routes while using the same domain name?
    How will the ESA forward incoming mail then? Some sort of load balancing, or will it be a priority thing?
    Thanks,
    Adrian

    Hi Adrian,
    Q:
    I have 2 lotus notes servers. Is it possible on the ESA to add these  two servers on the SMTP routes while using the same domain name?
    A:
    Yes. Please use SMTP Routes option, under Network > SMTP Routes.
    Q:
    How will the ESA forward incoming mail then? Some sort of load balancing, or will it be a priority thing?
    A:Whenever the appliance accept the connection and the message from the sender host, it will check the destination domain of the recipients and look up for SMTP route to reach that destination domain. If there is a SMTP route the appliance will then use the information configured on how to reach the destination. If you have version 7.x of the AsynOS which allows priorization, then the appliance will follow the configuration. If both destiantion servers configured have the same priority, round-robin fashion will be applied.
    If you are running a version prior of AsyncOS 7.x then the appliance will connect to the first server configured. If that server is unreachable then it will try the next one configured.
    SMTP Routes Overview
    SMTP Routes allow you to redirect all email for a particular domain to a different mail exchange (MX) host. For example, you could make a mapping from example.com to groupware.example.com. This mapping causes any email with @example.com in the Envelope Recipient address to go instead to groupware.example.com. The system performs an “MX” lookup on groupware.example.com, and then performs an “A” lookup on the host, just  like a normal email delivery. This alternate MX host does not need to  be listed in DNS MX records and it does not even need to be a member of  the domain whose email is being redirected. The Cisco IronPort AsyncOS  operating system allows up to forty thousand (40,000) SMTP Route  mappings to be configured for your Cisco IronPort appliance. (See SMTP Routes Limits.)
    This feature also allows host “globbing.” If you specify a partial domain, such as .example.com, then any domain ending in example.com matches the entry. For instance, [email protected] and [email protected] both match the mapping.
    If a host is not found in the SMTP Routes table, an MX lookup is performed using DNS. The result is not re-checked against the SMTP Routes table. If the DNS MX entry for foo.domain is bar.domain, any email sent to foo.domain is delivered to the host bar.domain. If you create a mapping for bar.domain to some other host, email addressed to foo.domain is not affected.
    In other words, recursive entries are not followed. If there is an entry for a.domain to redirect to b.domain, and a subsequent entry to redirect email for b.domain to a.domain, a mail loop will not be created. In this case, email addressed to a.domain will be delivered to the MX host specified by b.domain, and conversely email addressed to b.domain will be delivered to the MX host specified by a.domain.
    "The SMTP Routes table is read from the top down for every email delivery. The most specific entry that matches a mapping wins. For example, if there are mappings for both host1.example.com and .example.com in the SMTP Routes table, the entry for host1.example.com will be used because it is the more specific entry — even if it appears after the less specific .example.com entry. Otherwise, the system performs a regular MX lookup on the domain of the Envelope Recipient."
    From our documentation:
    "A receiving domain can have multiple destination hosts, each assigned a priority number, much like an MX  record. The destination host with the lowest number identifies as the  primary destination host for the receiving domain. Other destination  hosts listed will be used as backup.
    Destinations with identical priority will be used in a “round-robin” fashion. The round-robin process is based  on SMTP connections, and is not necessarily message-based. Also, if one  or more of the destination hosts are not responding, messages will be  delivered to one of the reachable hosts. If all the configured  destination hosts are not responding, mail is queued for the receiving  domain and delivery to the destination hosts is attempted later. (It  does not fail over to using MX records)."
    I hope this helps.
    Cheers,
    Valter

  • SMTP Routes, DNS and Failover

    Hi !
    I'm configuring an outgoing server (i.e. only a private listener) on ESA C370 with AsyncOS 8.0.1.
    I use the Internet's Root DNS Servers, and my default SMTP route is empty. My ESA is connected to 3 networks : production (default gateway), administration and failover (1 interface/network).
    I would like to deploy a failover solution with an extra ESA on the failover network : if I lose my internet connection (impossible to join DNS and remote MX), my ESA would redirect all its mails to the extra ESA.
    How can I do that ?
    Thank you for your help.
    Best Regards
    Quentin

    The ESA has no way to automatically fallback to a static IP if DNS in unreachable.  The best on-box solution I can suggest is manually changing the 'All Other Domains' SMTP Routes entry when such an event occurs.
    I hope this helps!
    - Jackie

  • Ironport Management appliance and smtp routes

    Hi Guys,
    I'm configuring M170 management appliance for two mail security Ironports (for centralized quarantine).
    while going through the configuration, i have found that there is SMTP route can be configured, why do i need to configure SMTP route under the management appliance?
    As i know it should be confgured on the Ironport email security appliances, but why on management? Do i need it?
    Thanks & Regards,
    Rami

    Hi,
    Thanks for your reply, just want to confirm, this is will be used even for end users Quarantine notification, correct?
    I mean that Management appliance will send quarantine notifications to end users by using this smtp route, am i right?
    Regards,
    Rami

  • IMS 5.2 SMTP routing

    How to setup SMTP routing on iMS 5.2?
    For example:
    For domain1.com MX is server1.domain1.com
    server1.domain1.com (iMS 5.2) have one user (email: [email protected]).
    I want to server1.domain1.com route messages for other users to server2.domain1.com.
    How to do this?
    Peter

    In order to route your mails to server2.domain1.com, you need to edit your LDAP domain entry (should be cn=domain1,cn=com,o=internet or so) and add a "mailroutingsmarthost" attribute pointing to server2.domain1.com.
    then imsimta refresh
    That's it.
    Good Luck
    Vincent MAZARD
    DML France (Sun Partner)
    Notes :
    If your server is working in Direct LDAP mode,
    apply patch 1 before adding the attribute.
    If server2 is an old version, I suggest you add the "dequeue_removeroute" keyword in your tcp_local and tcp_intranet channels definitions (imta.cnf file) or you'll get rewriting errors from the old server.

  • SMTP routing iMS 5.2

    A simple question, how can I specify the MX ip address of a particular destination domain ( bypassing dns MX lookup )
    Ims version 5.2P1 Ids 5.1.
    This setting was possible in NMS 4.x editing local.conf file
    es : service.smtp.smtp-routernsmsghostrewrites: testdomain.com:10.10.10.2
    thanks

    Another way in the imta.cnf you could have done
    testdomain.com $U%$D@tcp_other-daemon
    then create a tcp_channel for this domain
    tcp_other smtp daemon 10.1.1.1 subdirs 25 ..etc.
    tcp_other-daemon
    and route the mail to host 10.1.1.1 that way.
    But the hosted domain method probably is better
    in the long run. Easier to modify ldap than
    editing the imta.cnf each time.

  • Agent Selection/Routing Question

    Hello:
    I wanted to run a question by the group to get some feedback on a question I have surrounding Agent routing within UCCX (8.5 su4).
    Here is the setup of the environment:
    CSQ1: General
    Routing Criteria: LAA
    CSQ2: Spanish
    Routing Criteria: Most Skilled
    Agent1
    has Skills of General and Spanish. 
    Their competency is the same within both skills.
    Question: Calls are in queue for both CSQ's, although the call in the spanish CSQ has been in queue longer.  And agent 1 goes ready.  Whats currently happening is that agent 1 is getting another call from the General Queue as opposed to getting it from the spanish queue.
    How do I ensure that agent 1 gets the call from the spanish CSQ over the general CSQ?  Each CSQ needs to keep the Routing Criteria the same.
    My thought is that it has to be one of these two items, if not a combination of both.
    Decrease the Competency of all General agents to a (5) and Making the Spanish competency higher then 5.
    in the script, for Spanish Calls use the Set Priority Node to increase Spanish queued calls to be at like a 5, to ensure all spanish calls have a higher priority then general Calls.
    Any feedback would be appreciated! 

    Hi Sean
    All calls on the system if you are not using priority steps already should be answered FIFO... provided that there are agents available in the queue that the first call came in (i.e. they meet the minimum competency). Competency, skills/LAA and all those algorythms only affect who gets the call, not which one is served first. The exception to that is if the competency excludes some agents from the CSQ completely.
    So a call that arrives in 'Spanish' first should be routed to agents first, as long as there are agents available. Does the same apply if the agent is 'ready' but on a call for example? E.g. call voicemail as the agent, then put a call in to spanish, then one in general, and see which one comes through first.
    Priority will work, but will mean that Spanish calls alway queue jump. Priority is absolute, so a p2 call will jump in front of all other lower-priority calls regardless of how long they have been there.
    If you just want first-come-first-served, then that's what you should have by default.
    Aaron

  • BT Infinity - HG612 and second router question

    Hi,
    I've got an odd question. I have BT Infinity and have the HG612 VDSL modem. Does anyone know if and how it can be configured to bridge its WAN connection to another router? For work I need site-to-site VPN access, which is performed by this other router. Unfortunately it needs to own the WAN address, so I need to configure the HG612 to bridge the address with it. Has anyone does this? Is the HG612 even capable of doing this?
    I can't find any user manuals on it.
    Thanks, 
    Simon

    Hi Andy and welcome
    In THIS POST Phil recently wrote.-
    "Very proud of myself this afternoon.  I'm not much of an expert when it comes to DIY but I have managed to hardwire the router from the back of my house to the office on the first floor at the front.  After much contemplation, I decided to buy some external cat5e cable and run this along the same points as the SKY feed.  The result looks pretty good and I can now get 37.5Mbps upstairs as well as down. Result."
    Phil is very friendly I am sure if you have any questions it might be worth dropping him a PM ( philt1808 ) PM = Private Message if you click on the link philt1808 in brackets on the right you'll see SEND THIS USER A PRIVATE MESSAGE click on that.
    Mention it's PC's fault your contacting him... 
    Edit this thread has some info on cables http://community.bt.com/t5/BT-Infinity/Master-Socket-gt-Modem-gt-Hub-Router-cabling/td-p/408439
    Please Click On any Text in Blue as that automatically links to information.
    PC (NDEGR)

  • ESB routing question

    Hi,
    I have a question on the service that we are writing for the ESB. We are doing some simple transformations on the messages that the ESB consumes through AQ, then outputs to various end points(file adapter, soap adapter, DB adapter) after going through a routing service.
    My question is that it seems like the message delivery to the end points is very sequential. I thought that the message was suppose to hit all the end points, regardless of it's state, and move on to the next end point, and only retry the end points that failed. But this does not seem to be the case. Is there a way to achieve this with Oracle ESB?
    Thanks.

    The issue is that the routing service is sequential. We have a few adapters on the same routing service, and we observe that the message moves through the adapters sequentially.
    We are going to try to break out the routing service and end points so that each process dequeues from AQ, goes to one routing service, and one end point. Hopefully this way, there won't be any blocking, and all RS and endpoint can execute independently. The concern then is having a multi-consumer AQ, and I'm not sure if there are any issues with it.

Maybe you are looking for