Exporting and Importing Destination Controls Error

[Bighead81]

When I export table within destination control and import the table to another Ironport again within destination control I receive error - "Wrong format of the destination config file: ip_sort_pref is required for the global settings."

We are updating the ASYNC on each of our de clustered Ironport.  So when one is not in use we need the other to handle all the traffic, including domain controls.

The output displays

[ABCDE.com]
max_host_concurrency = 500
limit_apply = system
limit_type = host
max_messages_per_connection = 50 ......

How can I import this without losing or altering the data within.

^^^^^^^^^^^^^^^^^^^^^^

Solution

We upgrade one of our SMTP ASYNC to 8.0.1 which creates a additional line within default of the upgraded Ironport exported control destination table that is named... wait for it.... ip_sort_pref. Just add it.

[Jdubya_817]

We are implementing a new system currently and I am trying to import 54 TLS domains which my company does business with . Can someone tell me how to properly format a file that will successfully import all these domains? I added 3 manually and then used the export table button to manually export the configuration. I then saved the exported file to csv and added the domains. When I went to import, I received an error message saying " Wrong format of the destination config file: That value is not valid".  I saved the file as an ini file and was finally able to make enough changes to get it to read the file and now it simply says " "Wrong format of the destination config file: File contains no section headers" Please help

Thanks

JDubya

[marc.luescherFRE]

The standard import file format is something like this :

[DEFAULT]
table_tls = on_verify
dane_option = off
certificate = outboundcert.domain.com
max_messages_per_connection = 50
recipient_minutes = 60
max_host_concurrency = 500
limit_type = host
ip_sort_pref = REQUIRE_V4
limit_apply = VG
send_tls_req_alert = on
recipient_limit = 0
bounce_validation = off

[domain1.gov]
recipient_minutes = 60
table_tls = require
limit_apply = VG
recipient_limit = 0
limit_type = host

[domain2.com]
recipient_minutes = 60
table_tls = require
limit_apply = VG
recipient_limit = 0
limit_type = host

[domain3.com]
recipient_minutes = 60
table_tls = require
limit_apply = VG
recipient_limit = 0
limit_type = host

etc

We copied the text blocks and just inserted the required domains into the list and have been able to move this list around accross test, QA and prod clusters.

I would also highly recommend to add both ESA servers to a cluster so that this step has only to be performed once per cluster.