net-im/jabberd/files/multiple.xml (8c4e5b8) - keks-overlay.git

multiple.xml

<jabber>
  <!--
  This is the Jabber server configuration file. The file is
  broken into different sections based on the services being 
  managed by jabberd, the server daemon. Most of the important 
  sections have comments and are easy to modify.

At http://jabberd.jabberstudio.org/1.4/ you find further
  instructions including an annotated version of this con-
  figuration file and an installation guide.
  
  Note that when you see a tag like "jabberd:cmdline", it's
  automatically replaced on startup with the command line flag
  passed in to jabberd. This enables you to override para-
  meters set in this configuration file if necessary or de-
  sired. Also note as you comment things in and out that
  jabberd does not like comments within comments, so be care-
  ful with your XML. :)
  -->
 
 
 <!-- 
  The following <service/> section is for the session manager, 
  the most important component within the server. This section
  contains the following types of information:

* the server's hostname
    * other basic server information
    * the location of the session log file
    * email addresses for server administrators 
    * registration instructions for new users
    * a welcome message for new users
    * a list of agents with which users can register
    * load rules for the modules within the session manager

-->

<service id="sessions">
    <!-- 
    Replace all occurrences of "localhost" in this file by
    the hostname of your Jabber server. Be aware changing
    the server's name is all but impossible once users start
    to use the server. So choose a name that is permanent
    (especially no Intranet hostnames or IP addresses).

Multiple <host/> entries are allowed - each one is for a 
    separate virtual server. Note that each host entry must 
    be on one line, the server doesn't like it otherwise! :)
    Use lowercase for the hostname.
    -->

<host><jabberd:cmdline flag="h">localhost</jabberd:cmdline></host>

<filter>
          <default/>
          <max_size>100</max_size>
          <allow>
              <conditions>
                  <ns/>
                  <unavailable/>
                  <from/>
                  <resource/>
                  <subject/>
                  <body/>
                  <show/>
                  <type/>
                  <roster/>
                  <group/>
              </conditions>
              <actions>
                  <error/>
                  <offline/>
                  <forward/>
                  <reply/>
                  <continue/>
                  <settype/>
              </actions>
          </allow>
      </filter>
	
      <vCard>
        <FN>localhost</FN>
        <DESC>localhost</DESC>
        <URL>http://localhost/</URL>
      </vCard>

<welcome>
        <subject>Welcome!</subject>
        <body>Welcome to the Private Jabber server at localhost -- we hope you enjoy this service! For Questions and Remarks, please contact Foo Bar [ foobar@localhost ]. </body>
      </welcome>

<!-- 
      IDs with admin access - these people will receive admin 
      messages (any message to="yourhostname" is an admin
      message).  These addresses must be local ids, they cannot
      be remote addresses.

Note that they can also send announcements to all
      users of the server, or to all online users. To use
      the announcement feature, you need to send raw xml and be
      logged in as one of the admin users. Here is the syntax 
      for sending an announcement to online users:

<message to="yourhostname/announce/online">
          <body>announcement here</body>
        </message>

<message to="yourhostname/announce/motd">
          <body>message (of the day) that is sent only once to all users that are logged in and additionally to new ones as they log in</body>
        </message>

Sending to /announce/motd/delete will remove any existing
      motd, and to /announce/motd/update will only update the motd
      without re-announcing to all logged in users.

The <reply> will be the message that is automatically
      sent in response to any admin messages.
      -->

<admin>
        <read>foobar@localhost</read>
        <write>foobar@localhost</write>
        <reply>
          <subject>Auto Reply</subject>
          <body>This is a special administrative address.  Your message was received and forwarded to server administrators.</body>
        </reply>
      </admin>

<!-- An example that would setup a Jabber User Directory could be:

<service type="jud" jid="jud.localhost" name="Jabber User Directory">
        <ns>jabber:iq:search</ns>
        <ns>jabber:iq:register</ns>
</service>

-->
	</browse>
	</jsm>

<load main="jsm">
      <jsm>/usr/lib/jabberd/jsm.so</jsm>
      <mod_echo>/usr/lib/jabberd/jsm.so</mod_echo>
      <mod_roster>/usr/lib/jabberd/jsm.so</mod_roster>
      <mod_time>/usr/lib/jabberd/jsm.so</mod_time>
      <mod_vcard>/usr/lib/jabberd/jsm.so</mod_vcard>
      <mod_last>/usr/lib/jabberd/jsm.so</mod_last>
      <mod_version>/usr/lib/jabberd/jsm.so</mod_version>
      <mod_announce>/usr/lib/jabberd/jsm.so</mod_announce>
      <mod_agents>/usr/lib/jabberd/jsm.so</mod_agents>
      <mod_browse>/usr/lib/jabberd/jsm.so</mod_browse>
      <mod_admin>/usr/lib/jabberd/jsm.so</mod_admin>
      <mod_filter>/usr/lib/jabberd/jsm.so</mod_filter>
      <mod_offline>/usr/lib/jabberd/jsm.so</mod_offline>
      <mod_presence>/usr/lib/jabberd/jsm.so</mod_presence>
      <mod_auth_plain>/usr/lib/jabberd/jsm.so</mod_auth_plain>
      <mod_auth_digest>/usr/lib/jabberd/jsm.so</mod_auth_digest>
      <mod_log>/usr/lib/jabberd/jsm.so</mod_log>

      <mod_xml>/usr/lib/jabberd/jsm.so</mod_xml>
    </load>

</service>

<xdb id="xdb">
    <host/>
    <load>
      <xdb_file>/usr/lib/jabberd/xdb_file.so</xdb_file>
    </load>
    <xdb_file xmlns="jabber:config:xdb_file">
      <spool><jabberd:cmdline flag='s'>/var/spool/jabber</jabberd:cmdline></spool>
    </xdb_file>
  </xdb>

<!--
  The following service manages incoming client socket connections.
  There are several items you can set here to optimize performance:

* authtime - default is unlimited, but you can set this to
      limit the amount of time allowed for authentication to be
      completed, e.g., <authtime>10</authtime> for 10 seconds

* heartbeat - default is to not send out heartbeat packets
      to the clients.  This option allows you to specify that
      you want heartbeats to happen every x seconds.  This is
      useful if you have a lot of dial-up or laptop users who
      may drop their connection without logging off of jabber.
      Otherwise the server won't notice that they are offline until
      someone tries to send a packet to them (and the message is
      lost).  Example: <heartbeat>60</heartbeat>

* karma - this is an input/output rate limiting system that
      the Jabber team came up with to prevent bandwidth hogging.
      For details about karma, read the io section at the bottom.
      These are the low settings and apply per connection/socket
      and can be changed as desired.
      To disable rate limiting just delete the <karma/> section.
  -->

<service id="c2s">
    <load>
      <pthsock_client>/usr/lib/jabberd/pthsock_client.so</pthsock_client>
    </load>
    <pthcsock xmlns='jabber:config:pth-csock'>
      <authtime/>
      <karma>
        <init>10</init>
        <max>10</max>
        <inc>1</inc>
        <dec>1</dec>
	<heartbeat>60</heartbeat>
        <penalty>-6</penalty>
        <restore>10</restore>
      </karma>

<ip port="5222"/>

</pthcsock>
  </service>

<log id='elogger'>
    <host/>
    <logtype/>
    <format>%d: [%t] (%h): %s</format>
    <file>/var/log/jabber/error.log</file>
    <stderr/>
  </log>

<log id='rlogger'>
    <host/>
    <logtype>record</logtype>
    <format>%d %h %s</format>
    <file>/var/log/jabber/record.log</file>
  </log>

<service id="dnsrv">
    <host/>
    <load>
      <dnsrv>/usr/lib/jabberd/dnsrv.so</dnsrv>
    </load>
    <dnsrv xmlns="jabber:config:dnsrv">
    	<resend service="_jabber._tcp">s2s</resend> 
    	<resend>s2s</resend>
    </dnsrv>
  </service>
  
  
  <service id="s2s">
    <load>
      <dialback>/usr/lib/jabberd/dialback.so</dialback>
    </load>
    <dialback xmlns='jabber:config:dialback'>
      <legacy/>
      <ip port="5269"/>
      <karma>
        <init>50</init>
        <max>50</max>
        <inc>4</inc>
        <dec>1</dec>
        <penalty>-5</penalty>
        <restore>50</restore>
      </karma>
    </dialback>
  </service>

<service id="update.jabber.org">
    <host>update.jabber.org</host>
    <null/>
  </service>

<io>
    
    <!-- definition of terms:

* Avg. Throughput - The number of bytes you can
        send every second without incuring any penalty.

* Burst Allowed - The maximum number of bytes you
        can send in 2 seconds without incurring any penalty.

* Max Sustained Rate - If you send data as fast as 
        you can, you will hit penalty, and will not be 
        able to send for 10 seconds; the max sustained 
        rate is the average rate you can dump data when 
        you are dumping as much data as you can, as fast 
        as you can.

* Seconds to Recover from Burst - The amount of time 
        it will take to reach Avg. Throughput capability 
        after sending a max burst of data.

* Penalty Length - The length of your penalty is
        determined according to this formula:
              abs(penalty) * Heartbeat seconds
        E.g., a penalty of -5 and heartbeat of 2 will 
        cause your penalty length to be 10 seconds. 
   Note that a penalty CANNOT be less than -100, 
        otherwise strange things might happen.

-->

<rate points="5" time="25"/>

<ssl>
      <key ip="64.57.168.155">/etc/jabber/gentoo.pem</key>
    </ssl>

</io>

<pidfile>/var/run/jabber.pid</pidfile>

</jabber>

keks-overlay.git

A keks * initial commit