Og2List and Cpanel/WHM????

the install instructions for exim integration are a bit vague. i have enlisted help from civicspace but would still like to know how to do this myself...
I'll bet I could get it with just a few hints.
When I tried to enter the settings verbatim all email just stopped. When i rolled back my exim.conf.. all emails that were delayed got delivered...

1. there are a few parts I don't understand.. in the parts where it says local_part@domain... do i change domain to mine?
2. does "localhost/drupal/dbuser/dbpass" need to be changed with server specific info?
3. it says the router order is important.. what is typically first.
4. perhaps an example of the changes made to an exim.conf would be helpful.

i just saw killes posted a 4.7 version of og2list.
i'd love to try this out on my sites! some are 4.7 and others are 4.6

will i be able to run multiple domains thru og2list on my dedicated host? i mean i just do the og2list user, exim.conf and then each domain's drupal install has its og2list.module so it should work right?

cool!
ryan.

Integration into MTA setup (Exim 4.x)

Global
The global section of Exim's configuration file is the place to
define variables and installation-specific parameters such as the
SQL location below.
See Section 9.21 of the Exim specification for details.

The user/group ID and the home directory need not match any other
user account on the system, in particular not the webserver's or the
web application's user. mail-in.pl only needs to access its
configuration file and the og2list_* tables in the SQL database for
which the credentials are stored in the configuration file.

OG2LIST_HOME = /home/og2list
OG2LIST_UID  = og2list
OG2LIST_GID  = og2list

hide mysql_servers = localhost/drupal/dbuser/dbpass

Router
Routers are rules that determine how a destination address should be
handled. The following piece of code assigns addresses to a
transport rule called og2list_transport which is defined below.
Note that the since Routers are evaluated one after anotehr, their
order in the configuration file will most likely affect overall
behavior.

See section 3.8 of the Exim specification for details.

og2list:
  debug_print "R: og2list from $return_path \
    for $local_part@$domain"
  driver = accept
  transport = og2list_transport
  condition = ${lookup mysql{SELECT 1 FROM og2list_groups \
                             WHERE recipient \
                             LIKE '$local_part@$domain'} \
                       {$value} \
                       fail}

If Exim has been built without MySQL support, the following
condition statement should work:

  condition = ${run{/path/to/valid-recipient.pl $local_part@$domain}{1}{0}}

Transport
Transports are the rules that determine by what means a message
should be delivered that has been assigned to this transport by a
router.
og2list_transport:
debug_print "T: og2list_transport from \
$return_path for $local_part@$domain"
driver = pipe
freeze_exec_fail
log_output
command = OG2LIST_HOME/mail-in.pl \
-f $return_path -t $local_part@$domain
current_directory = OG2LIST_HOME
user = OG2LIST_UID
group = OG2LIST_GID