Below is an example config file for the script. It should be located at /etc/getcrr.conf if you are using the default configuration. You can always specify another config file on the command line. 
# General Config
#

# The temp dir that getcrr will use when building up the final map fil
+es
# Note: This directory must exist, it will not be created
Libdir        /etc/postfix/crr

# Path/file for the pid file
PIDFile        /var/run/getcrr.pid

# The logfile location and filename
LogFile        /var/log/getcrr.log

# Turn Debugging on in the log file
Debug 0

# The maximum number of processes that should be allowed to fork off t
+o
# to be used by the forking manager
MaxProc        5

# Email address of the administrator (Leave commented to not receive e
+mail)
# 
AdminEmail    "Eric Lubow" <admin@server.com>
#AdminEmailCC    "Tech Reports" <tech@server.com>


# Postfix Config
#
# Note: All postfix map files are created in pcre format.
#    Ensure your main.cf matches accordingly
#

# This is the base dir of your postfix configuration
PostfixBase    /etc/postfix

# Path/file for the postfix relay domains file
RelayDomains    ${PostfixBase}/relay_domains

# Path/file for the postfix mynetworks file
MyNetworks    ${PostfixBase}/mynetworks

# Path/file for the postfix relay recipients file
RelayRecipients    ${PostfixBase}/relay_recipients

# Path/file for the postfix transport maps file
TransportMaps    ${PostfixBase}/transport

# List any backup mail servers here
BackupMX    mail2.server.com

# Amavis/SpamAssassin/DSpam Config
#

# If you are using amavisd and SPAM Assassin to filter SPAM, then it
# would be a good idea to use this option.  In amavisd it is necessary
# to setup the @score_sender_maps array.  This is a by-recipient hash
# lookup table.  Add the line:
#   read_hash("/etc/amavis/sender_scores_sitewide"),
# where /etc/amavis/sender_scores_sitewide is the location of the
# external hashfile that will be generated by this script.
# Comment this out for the file not to be created
SenderScoresFile    /etc/amavis/sender_scores_sitewide

# All messsages that appear to be coming from one of our domains, but
# from an invalid recipient will get this threshold added
BLLocalSenderScore    1.0

# Scoring change on a message sent by a whitelisted sender listed in
# the sender_scores_sitewide file
WLSenderScore        -5.0

# An additional list of white list senders
WLSenders mom@myfamily.com \
      dad@myfamily.com

# An additional list of white list senders & their score
BLSenders example@example.com
BLSenderScore 4.5

# Server Listings
#
Password    MyPass

# Exchange Server
<Server ex01>
  Company    Exchange Examples
  Host        ex01.server.com
  IP        192.168.1.10
  Type        Exchange
  Base        dc=Example,dc=com
  User        ex@example
  Pass        ${Password}
  Active    1
  Comment    Example Exchange Server
  ExcludeDomain    vtext.com mobile.mycingular.com
</Server>

# Nitix Server
<Server consolco-clifton>
  Company    Nitix Examples
  Host        nitix.server.com
  IP        192.168.2.10
  Type        Nitix
  Base        dc=server,dc=com
  User        ex@dc=server,dc=com
  Attrib    mail
  Active    1
  Comment    Nitix Example Server
</Server>

[download]

In reply to Example Config File by madbombX
in thread Exchange to Postfix Firewall Configuration by madbombX

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.