example-config.xml

<muc>
  <!--
  This is a config file for palaver.  

  This format is currectly backwards compatible with the JCR mu-conference
  config file format, as long as you surround the file with the <muc> tag.
  If you switching to palaver from JCR mu-conference, just add the
  surrounding <muc> and </muc> tags and you can use the same file.
  Note: several JCR fields may be unused in palaver.  This file
  includes only options that are actually used.
  -->

  <name>chat.localhost</name>  <!-- the name of our component -->
  <ip>localhost</ip>           <!-- the server to connect to -->
  <port>5347</port>            <!-- the port to connect to -->
  <secret>secret</secret>      <!-- the secret :) -->

  <!-- the storage backend configuration -->
  <backend>
   <type>dir</type> <!-- possibilities are: dir, memory -->
  </backend>

  <!-- postgresql storage mechanism -->
  <!--
  <backend>
    <type>pgsql</type>
    <dbuser>muc</dbuser>
    <dbname>muc</dbname>
    <!-- <dbpass>secret</dbpass> -->
    <!-- <dbhostname>localhost</dbhostname> -->
   
  </backend>
  -->

  <!-- spool is the directory where filesystem based backends store data -->
  <spool>/var/lib/jabberd/chat.localhost</spool>

   <conference xmlns="jabber:config:conference">
    <sadmin>
      <user>user@host.tld</user>
    </sadmin>  
  </conference>

</muc>