Re: Stream Error
debarshi kumar banerjee <[email protected]> Thu, 25 Oct 2012 11:34:34 +0530
| Newsgroups | gmane.network.jabber.admin |
|---|---|
| Message-ID | <CAHdCetnwcSsJRXRhAu9iDVQfbramqLbprt3XBxRd_XOP67+KgA@mail.gmail.com> |
--===============0719484346== Content-Type: multipart/alternative; boundary=047d7b6d89c238b2dd04ccdbfa10 --047d7b6d89c238b2dd04ccdbfa10 Content-Type: text/plain; charset=ISO-8859-1 Hi Herbert, Thanks a lot for sharing your jabber.xml with me. I need another help. I have since then uninstalled the jabberd and downloaded jabber14 1.6.1.1 from the website and tried to build it from source instead of installing from rpm. Now according to the requirements I installed gnu pth 2.0.7 but when i run *make* after running *./configure *it says i get *No targets specified and no makefile found. *I read the docs inside out i cannot figure out what i am doing wrong. regards. Debarshi On Wed, Oct 24, 2012 at 12:10 AM, herbert langhans <[email protected]>wrote: > Hi Debarshi, > there must be some file with the contents what I listed below. Possibly > with some xml-extension - but the extension may differ. Find it. > > Have you taken a look at: > http://jabberd.org/1.4/doc/adminguide > > - and at the end you find my /usr/pkg/etc/jabberd/jabber.xml > Where I had insert jabber.youhost.com you have to put your (registered) > domain in. If your website is http://yourhost.com you have to put in > jabber.youhost.com or whatever you invent instead of 'jabber'. > > ####### jabber.xml (from a NetBSD server) follows ######## > > > > <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. You can find > full instructions in the server howto, which is available at > http://docs.jabber.org/. 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 parameters set in this configuration file if > necessary or desired. Also note as you comment things in and > out that jabberd does not like comments within comments, so > be careful 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 > * the location of the server that provides update information > * 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"> > > <!-- > Change hostname below to something other than "localhost", > i.e., to the hostname or IP address of your Jabber server. > 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! :) > --> > > <!-- > <host><jabberd:cmdline flag="h">localhost</jabberd:cmdline></host> > --> > <host><jabberd:cmdline flag="h">jabber.yourhost.com > </jabberd:cmdline></host> > > <!-- > This is the custom configuration section for the > Jabber session manager, a.k.a. "JSM". > --> > > <jsm xmlns="jabber:config:jsm"> > > <!-- > The <filter/> section below determines settings > for mod_filter, a server-side module built into > JSM that enables users to set delivery rules for > messages they receive (not yet supported by all > clients. The <allow/> subsection specifies which > conditions and actions to enable. High-level > descriptions of each setting can be found below > (see docs.jabber.org for full details): > > * <default/> - a user cannot delete this one, it's > the default rule for delivering messages > * <max_size/> - the maximum number of rules in a > user's rule set (we don't want to overdo it!) > * conditions... > * <ns/> - matches the query xmlns attrib on an iq packet > * <unavailable/> - matches when user is unavailable > * <from/> - matches the sender of the message > * <resource/> - matches the receiver's resource > * <subject/> - matches the subject of the message > * <body/> - matches the body of the message > * <show/> - matches the show tag on the receiver's presence > * <type/> - matches the type of the message > * <roster/> - matches if the sender is in your roster > * <group/> - matches if the sender is in the specified group > * actions... > * <error/> - replies with an error > * <offline/> - stores the messages offline > * <forward/> - forwards the message to another jid > * <reply/> - sends a reply to the sender of the message > * <continue/> - continues processing of the rules > * <settype/> - changes the type of the message > --> > <filter> > <default/> > <max_size>100</max_size> > <allow> > <conditions> > <ns/> <!-- Matches if the iq's xmlns is the > same as the specified namespace --> > <unavailable/> <!-- Flag that matches when the reciever > is unavailable (offline) --> > <from/> <!-- Matches if the sender's jid is the > specified jid --> > <resource/> <!-- Matches if the sender's resource > (anything after the / in a jid) is the specified resource --> > <subject/> <!-- Matches if the message's subject is > the specified subject (no regex yet) --> > <body/> <!-- Matches if the message body is the > specified body (no regex yet) --> > <show/> <!-- Matches if the receiver's presence > has a show tag that is the same as the specified text --> > <type/> <!-- Matches if the type of the message > is the same as the specified text ("normal" is okay) --> > <roster/> <!-- Flag that matches when the sender is > in the receiver's roster --> > <group/> <!-- Matches when the sender is in the > specified group --> > </conditions> > <actions> > <error/> <!-- Sends back an error message to the > sender, with the specified text --> > <offline/> <!-- Flag that stores the message offline > --> > <forward/> <!-- forwards the message to the > specified jid --> > <reply/> <!-- Sends back a reply to the sender > with the specified text in the body --> > <continue/> <!-- Flag that continues rule matching, > after a rule matches --> > <settype/> <!-- Changes the type of message to the > specified type, before delivery to the receiver --> > </actions> > </allow> > </filter> > > <!-- The server vCard --> > > <vCard> > <FN>Jabber Server</FN> > <DESC>A Jabber Server!</DESC> > <URL>http://jabber.yourhost.com/</URL> > </vCard> > > <!-- > Registration instructions and required fields. The > notify attribute will send the server administrator(s) > a message after each valid registration if it is set > to "yes". > --> > > <register notify="yes"> > <instructions>Choose a username and password to register with this > server.</instructions> > <name/> > <email/> > </register> > > <!-- > A welcome note that is sent to every new user who registers > with your server. Comment it out to disable this function. > --> > > <welcome> > <subject>Welcome!</subject> > <body>Welcome to the Jabber server at http://jabber.youhost.com-- we hope you enjoy this service! For information about how to use Jabber, > visit the Jabber User's Guide at http://jabber.org/</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>support@localhost</read> > <write>admin@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> > --> > > <!-- > This is the resource that checks for updated versions > of the Jabber server software. Note that you don't lose > any functionality if you comment this out. Removing the > <update/> config is especially a good strategy if your > server is behind a firewall. If you want to use this > feature, change 'localhost' to the hostname or IP address > of your server, making sure that it is the same as your > entry for <host/> above. > --> > > <!-- > <update><jabberd:cmdline > flag="h">localhost</jabberd:cmdline></update> > --> > > <!-- > This enables the server to automatically update the > user directory when a vcard is edited. The update is > only sent to the first listed jud service below. It is > safe to remove this flag if you do not want any users > automatically added to the directory. > --> > > <vcard2jud/> > > <!-- > The <browse/> section identifies the transports and other > services that are available from this server. Note that each > entity identified here must exist elsewhere or be further > defined in its own <service/> section below. These services > will appear in the user interface of Jabber clients that > connect to your server. > --> > > <browse> > > <!-- > This is the default agent for the master Jabber User > Directory, a.k.a. "JUD", which is located at jabber.org. > You can add separate <service/> sections for additional > directories, e.g., one for a company intranet. > --> > > <!-- > <service type="jud" jid="users.jabber.org" name="Jabber User > Directory"> > <ns>jabber:iq:search</ns> > <ns>jabber:iq:register</ns> > </service> > --> > > <!-- > The following services are examples only, you will need to > create/modify them to get them working on your Jabber > server. See the README files for each service and/or the > server howto for further information/instructions. > --> > > <!-- we're commenting these out, of course :) > > <conference type="private" jid="conference.localhost" > name="Private Conferencing"/> > > <service type="aim" jid="aim.localhost" name="AIM Transport"> > <ns>jabber:iq:gateway</ns> > <ns>jabber:iq:register</ns> > </service> > > <service type="yahoo" jid="yahoo.localhost" name="Yahoo! > Transport"> > <ns>jabber:iq:gateway</ns> > <ns>jabber:iq:register</ns> > </service> > > end of <service/> examples --> > > </browse> > > </jsm> > > <!-- > The following section dynamically loads the individual > modules that make up the session manager. Remove or > comment out modules to disable them. Note that the order > of modules is important, since packets are delivered > based on the following order!! > --> > > <load main="jsm"> > <jsm>/usr/pkg/lib/jabberd/jsm.so</jsm> > <mod_echo>/usr/pkg/lib/jabberd/jsm.so</mod_echo> > <mod_roster>/usr/pkg/lib/jabberd/jsm.so</mod_roster> > <mod_time>/usr/pkg/lib/jabberd/jsm.so</mod_time> > <mod_vcard>/usr/pkg/lib/jabberd/jsm.so</mod_vcard> > <mod_last>/usr/pkg/lib/jabberd/jsm.so</mod_last> > <mod_version>/usr/pkg/lib/jabberd/jsm.so</mod_version> > <mod_announce>/usr/pkg/lib/jabberd/jsm.so</mod_announce> > <mod_agents>/usr/pkg/lib/jabberd/jsm.so</mod_agents> > <mod_browse>/usr/pkg/lib/jabberd/jsm.so</mod_browse> > <mod_admin>/usr/pkg/lib/jabberd/jsm.so</mod_admin> > <mod_filter>/usr/pkg/lib/jabberd/jsm.so</mod_filter> > <mod_offline>/usr/pkg/lib/jabberd/jsm.so</mod_offline> > <mod_presence>/usr/pkg/lib/jabberd/jsm.so</mod_presence> > <mod_auth_plain>/usr/pkg/lib/jabberd/jsm.so</mod_auth_plain> > <mod_auth_digest>/usr/pkg/lib/jabberd/jsm.so</mod_auth_digest> > <mod_auth_0k>/usr/pkg/lib/jabberd/jsm.so</mod_auth_0k> > <mod_log>/usr/pkg/lib/jabberd/jsm.so</mod_log> > <mod_register>/usr/pkg/lib/jabberd/jsm.so</mod_register> > <mod_xml>/usr/pkg/lib/jabberd/jsm.so</mod_xml> > </load> > > </service> > > <!-- OK, we've finished defining the Jabber Session Manager. --> > > <!-- The <xdb/> component handles all data storage, using the > filesystem. --> > > <xdb id="xdb"> > <host/> > <load> > <xdb_file>/usr/pkg/lib/jabberd/xdb_file.so</xdb_file> > </load> > <xdb_file xmlns="jabber:config:xdb_file"> > <spool><jabberd:cmdline > flag='s'>/var/spool/jabberd</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 > > * 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 > and/or see docs.jabber.org. These are the low settings and > apply per connection/socket and can be changed as desired. > --> > > <service id="c2s"> > <load> > > <pthsock_client>/usr/pkg/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> > <penalty>-6</penalty> > <restore>10</restore> > </karma> > > <!-- > Use these to listen on particular addresses and/or ports. > <ip port="5222">127.0.0.1</ip> > --> > <ip port="5222"/> > > <!-- > The <ssl/> tag acts pretty much like the <ip/> tag, > except it defines that SSL is to be used on the > ports and IP addresses specified. You must specify > an IP address here, or the connections will fail. > <ssl port='5223'>127.0.0.1</ssl> > <ssl port='5224'>192.168.1.100</ssl> > --> > > </pthcsock> > </service> > > <!-- > This is the default server error logging component, > which copies to a file and to STDERR. > --> > > <log id='elogger'> > <host/> > <logtype/> > <format>%d: [%t] (%h): %s</format> > <file>/var/log/jabberd/error.log</file> > <stderr/> > </log> > > <!-- > This is the default server record logging component, > which logs general statistical/tracking data. > --> > > <log id='rlogger'> > <host/> > <logtype>record</logtype> > <format>%d %h %s</format> > <file>/var/log/jabberd/record.log</file> > </log> > > <!-- The following two services are for handling server-to-server > traffic. --> > > <!-- External asychronous DNS resolver --> > > <service id="dnsrv"> > <host/> > <load> > <dnsrv>/usr/pkg/lib/jabberd/dnsrv.so</dnsrv> > </load> > <dnsrv xmlns="jabber:config:dnsrv"> > <resend service="_jabber._tcp">s2s</resend> <!-- for supporting > SRV records --> > <resend>s2s</resend> > </dnsrv> > </service> > > <!-- > The following 's2s' config handles server connections and > dialback hostname verification. The <legacy/> element is > here to enable communication with old 1.0 servers. The > karma settings are a little higher here to handle the > higher traffic of server-to-server connections (read > the io section below for more details, medium settings). > --> > > <service id="s2s"> > <load> > <dialback>/usr/pkg/lib/jabberd/dialback.so</dialback> > </load> > <dialback xmlns='jabber:config:dialback'> > <legacy/> > <!-- Use these to listen on particular addresses and/or ports. > <ip port="7000"/> > <ip port="5269">127.0.0.1</ip> > --> > <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> > > <!-- > If you identified additional agents in the main <service/> > section (see examples above), you'll need to define each > of them here using a separate <service/> section for each > <agent/> you identified. Note that the <agent/> sections > determine what gets shown to clients that connect to your > server, whereas the following <service/> sections define > these services within the server itself. The following are > examples only, you will need to create/modify them to get > them working on your Jabber server. See the README files > for each agent and/or the server howto for further > information/instructions. > --> > > <!-- we're commenting these out, of course :) > > <service id="conference"> > <load> > <groupchat>/path/to/groupchat.so</groupchat> > </load> > <host>conference.localhost</host> > </service> > > <service id="irc"> > <host>irc.localhost</host> > </service> > > <service id="aim.localhost"> > <accept> > <ip/> > <port>7009</port> > <secret>jabber-rocks</secret> > </accept> > </service> > > <service id="yahoo.localhost"> > <accept> > <ip/> > <port>9001</port> > <secret>jabber-rocks</secret> > </accept> > </service> > > end of <service/> examples --> > > <!-- > The following <io/> config initializes the top-level > I/O, otherwise known as MIO (Managed Input/Output). > --> > > <io> > > <!-- Set the default karma for *all* sockets --> > <!-- 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. > > --> > <!-- Example of Low Karma Limits > Avg. Throughput: 1k-2k/s > Burst Allowed To: 5.5k/s > Max Sustained Rate: 485b/s > Seconds to Recover from Burst: 20 > Penalty Length: 12 seconds > <karma> > <heartbeat>2</heartbeat> > <init>10</init> > <max>10</max> > <inc>1</inc> > <dec>1</dec> > <penalty>-6</penalty> > <restore>10</restore> > </karma> > --> > > <!-- Example of Medium Karma Limits > Avg. Throughput: 5k-10k/s > Burst Allowed: 125.5k/s > Max Sustained Rate: 12.6k/s > Seconds to Recover From Burst: 25 > Penalty Length: 10 seconds > <karma> > <heartbeat>2</heartbeat> > <init>50</init> > <max>50</max> > <inc>4</inc> > <dec>1</dec> > <penalty>-5</penalty> > <restore>50</restore> > </karma> > --> > > <!-- Example of High Karma Limits > Avg. Throughput: 5k-10k/s > Burst Allowed: 206k/s > Max Sustained Rate: 34.3k/s > Seconds to Recover from Burst: 21 > Penalty Length: 6 seconds > <karma> > <heartbeat>2</heartbeat> > <init>64</init> > <max>64</max> > <inc>6</inc> > <dec>1</dec> > <penalty>-3</penalty> > <restore>64</restore> > </karma> > --> > > <!-- > Set rate limits to monitor the number of connection > attempts from a single IP, any more than [points] > within [time] will engage the limit. This setting > applies to all incoming connections to any service, > unless otherwise overridden by that service. > --> > > <rate points="5" time="25"/> > > <!-- > The following section initializes SSL for top-level I/O. > This works only when the server is compiled with openssl! > --> > <!-- > <ssl> > <key ip='192.168.1.1'>/path/to/cert_and_key.pem</key> > <key ip='192.168.1.100'>/path/to/other/cert_and_key.pem</key> > </ssl> > --> > > <!-- > The following section is used to allow or deny > communications from specified IP networks or > addressses. If there is no <allow/> section, > then *all* IPs will be allowed to connect. If > you allow one block, then only that block may > connect. Note that <allow/> is checked before > <deny/>, so if a specific address is allowed > but the network for that address is denied, > then that address will still be denied. > --> > <!-- > <allow><ip>127.0.0.0</ip><mask>255.255.255.0</mask></allow> > <allow><ip>12.34.56.78</ip></allow> > <deny><ip>22.11.44.0</ip><mask>255.255.255.0</mask></deny> > --> > > </io> > > <!-- > This specifies the file to store the pid of the process in. > <pidfile>/var/run/jabber.pid</pidfile> > <pidfile>/var/run/jabberd/jabber.pid</pidfile> > --> > > </jabber> > > ############### end of jabber.xml ################## > _______________________________________________ > JAdmin mailing list > Info: http://mail.jabber.org/mailman/listinfo/jadmin > Unsubscribe: [email protected] > _______________________________________________ > --047d7b6d89c238b2dd04ccdbfa10 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Herbert,<div><br></div><div>Thanks a lot for sharing your jabber.xml wit= h me. I need another help. I have since then uninstalled the jabberd and do= wnloaded jabber14 1.6.1.1 from the website and tried to build it from sourc= e instead of installing from rpm. Now according to the requirements I insta= lled gnu pth 2.0.7 but when i run <i>make</i> after running <i>./configure = </i>it says i get <i>No targets specified and no makefile found. </i>I read= the docs inside out i cannot figure out what i am doing wrong.</div> <div><br></div><div>regards.</div><div>Debarshi<br><br><div class=3D"gmail_= quote">On Wed, Oct 24, 2012 at 12:10 AM, herbert langhans <span dir=3D"ltr"= ><<a href=3D"mailto:[email protected]" target=3D"_blank">[email protected]= m.pl</a>></span> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex">Hi Debarshi,<br> there must be some file with the contents what I listed below. Possibly<br> with some xml-extension - but the extension may differ. Find it.<br> <br> Have you taken a look at:<br> <a href=3D"http://jabberd.org/1.4/doc/adminguide" target=3D"_blank">http://= jabberd.org/1.4/doc/adminguide</a><br> <br> - and at the end you find my /usr/pkg/etc/jabberd/jabber.xml<br> Where I had insert <a href=3D"http://jabber.youhost.com" target=3D"_blank">= jabber.youhost.com</a> you have to put your (registered)<br> domain in. If your website is <a href=3D"http://yourhost.com" target=3D"_bl= ank">http://yourhost.com</a> you have to put in<br> <a href=3D"http://jabber.youhost.com" target=3D"_blank">jabber.youhost.com<= /a> or whatever you invent instead of 'jabber'.<br> <br> ####### jabber.xml (from a NetBSD server) follows ########<br> <br> <br> <br> <jabber><br> <br> =A0 <!--<br> =A0 This is the Jabber server configuration file. The file is<br> =A0 broken into different sections based on the services being<br> =A0 managed by jabberd, the server daemon. Most of the important<br> =A0 sections have comments and are easy to modify. You can find<br> =A0 full instructions in the server howto, which is available at<br> =A0 <a href=3D"http://docs.jabber.org/" target=3D"_blank">http://docs.jabbe= r.org/</a>. Note that when you see a tag like<br> =A0 "jabberd:cmdline", it's automatically replaced on startup= <br> =A0 with the command line flag passed in to jabberd. This enables<br> =A0 you to override parameters set in this configuration file if<br> =A0 necessary or desired. Also note as you comment things in and<br> =A0 out that jabberd does not like comments within comments, so<br> =A0 be careful with your XML. :)<br> =A0 --><br> <br> <br> =A0 <!--<br> =A0 The following <service/> section is for the session manager,<br> =A0 the most important component within the server. This section<br> =A0 contains the following types of information:<br> <br> =A0 =A0 * the server's hostname<br> =A0 =A0 * other basic server information<br> =A0 =A0 * the location of the session log file<br> =A0 =A0 * email addresses for server administrators<br> =A0 =A0 * the location of the server that provides update information<br> =A0 =A0 * registration instructions for new users<br> =A0 =A0 * a welcome message for new users<br> =A0 =A0 * a list of agents with which users can register<br> =A0 =A0 * load rules for the modules within the session manager<br> <br> =A0 --><br> <br> =A0 <service id=3D"sessions"><br> <br> =A0 =A0 <!--<br> =A0 =A0 Change hostname below to something other than "localhost"= ,<br> =A0 =A0 i.e., to the hostname or IP address of your Jabber server.<br> =A0 =A0 Multiple <host/> entries are allowed - each one is for a<br> =A0 =A0 separate virtual server. Note that each host entry must<br> =A0 =A0 be on one line, the server doesn't like it otherwise! :)<br> =A0 =A0 --><br> <br> =A0 =A0 <!--<br> =A0 =A0 <host><jabberd:cmdline flag=3D"h">localhost&l= t;/jabberd:cmdline></host><br> =A0 =A0 --><br> =A0 =A0 <host><jabberd:cmdline flag=3D"h"><a href=3D"= http://jabber.yourhost.com" target=3D"_blank">jabber.yourhost.com</a></j= abberd:cmdline></host><br> <br> =A0 =A0 <!--<br> =A0 =A0 This is the custom configuration section for the<br> =A0 =A0 Jabber session manager, a.k.a. "JSM".<br> =A0 =A0 --><br> <br> =A0 =A0 <jsm xmlns=3D"jabber:config:jsm"><br> <br> =A0 =A0 =A0 <!--<br> =A0 =A0 =A0 The <filter/> section below determines settings<br> =A0 =A0 =A0 for mod_filter, a server-side module built into<br> =A0 =A0 =A0 JSM that enables users to set delivery rules for<br> =A0 =A0 =A0 messages they receive (not yet supported by all<br> =A0 =A0 =A0 clients. The <allow/> subsection specifies which<br> =A0 =A0 =A0 conditions and actions to enable. High-level<br> =A0 =A0 =A0 descriptions of each setting can be found below<br> =A0 =A0 =A0 (see <a href=3D"http://docs.jabber.org" target=3D"_blank">docs.= jabber.org</a> for full details):<br> <br> =A0 =A0 =A0 * <default/> - a user cannot delete this one, it's<br= > =A0 =A0 =A0 =A0 the default rule for delivering messages<br> =A0 =A0 =A0 * <max_size/> - the maximum number of rules in a<br> =A0 =A0 =A0 =A0 user's rule set (we don't want to overdo it!)<br> =A0 =A0 =A0 * conditions...<br> =A0 =A0 =A0 =A0 * <ns/> - matches the query xmlns attrib on an iq pac= ket<br> =A0 =A0 =A0 =A0 * <unavailable/> - matches when user is unavailable<b= r> =A0 =A0 =A0 =A0 * <from/> - matches the sender of the message<br> =A0 =A0 =A0 =A0 * <resource/> - matches the receiver's resource<b= r> =A0 =A0 =A0 =A0 * <subject/> - matches the subject of the message<br> =A0 =A0 =A0 =A0 * <body/> - matches the body of the message<br> =A0 =A0 =A0 =A0 * <show/> - matches the show tag on the receiver'= s presence<br> =A0 =A0 =A0 =A0 * <type/> - matches the type of the message<br> =A0 =A0 =A0 =A0 * <roster/> - matches if the sender is in your roster= <br> =A0 =A0 =A0 =A0 * <group/> - matches if the sender is in the specifie= d group<br> =A0 =A0 =A0 * actions...<br> =A0 =A0 =A0 =A0 * <error/> - replies with an error<br> =A0 =A0 =A0 =A0 * <offline/> - stores the messages offline<br> =A0 =A0 =A0 =A0 * <forward/> - forwards the message to another jid<br= > =A0 =A0 =A0 =A0 * <reply/> - sends a reply to the sender of the messa= ge<br> =A0 =A0 =A0 =A0 * <continue/> - continues processing of the rules<br> =A0 =A0 =A0 =A0 * <settype/> - changes the type of the message<br> =A0 =A0 =A0 --><br> =A0 =A0 =A0 <filter><br> =A0 =A0 =A0 =A0 =A0 <default/><br> =A0 =A0 =A0 =A0 =A0 <max_size>100</max_size><br> =A0 =A0 =A0 =A0 =A0 <allow><br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 <conditions><br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <ns/> =A0 =A0 =A0 =A0 =A0<!-- = Matches if the iq's xmlns is the same as the specified namespace -->= <br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <unavailable/> <!-- Flag that = matches when the reciever is unavailable (offline) --><br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <from/> =A0 =A0 =A0 =A0<!-- Ma= tches if the =A0sender's jid is the specified jid --><br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <resource/> =A0 =A0<!-- Matche= s if the sender's resource (anything after the / in a jid) is the speci= fied resource --><br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <subject/> =A0 =A0 <!-- Matche= s if the message's subject is the specified subject (no regex yet) --&g= t;<br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <body/> =A0 =A0 =A0 =A0<!-- Ma= tches if the message body is the specified body (no regex yet) --><br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <show/> =A0 =A0 =A0 =A0<!-- Ma= tches if the receiver's presence has a show tag that is the same as the= specified text --><br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <type/> =A0 =A0 =A0 =A0<!-- Ma= tches if the type of the message is the same as the specified text ("n= ormal" is okay) --><br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <roster/> =A0 =A0 =A0<!-- Flag= that matches when the sender is in the receiver's roster --><br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <group/> =A0 =A0 =A0 <!-- Matc= hes when the sender is in the specified group --><br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 </conditions><br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 <actions><br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <error/> =A0 =A0 =A0 <!-- Send= s back an error message to the sender, with the specified text --><br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <offline/> =A0 =A0 <!-- Flag t= hat stores the message offline --><br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <forward/> =A0 =A0 <!-- forwar= ds the message to the specified jid --><br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <reply/> =A0 =A0 =A0 <!-- Send= s back a reply to the sender with the specified text in the body --><br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <continue/> =A0 =A0<!-- Flag t= hat continues rule matching, after a rule matches --><br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 <settype/> =A0 =A0 <!-- Change= s the type of message to the specified type, before delivery to the receive= r --><br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 </actions><br> =A0 =A0 =A0 =A0 =A0 </allow><br> =A0 =A0 =A0 </filter><br> <br> =A0 =A0 =A0 <!-- The server vCard --><br> <br> =A0 =A0 =A0 <vCard><br> =A0 =A0 =A0 =A0 <FN>Jabber Server</FN><br> =A0 =A0 =A0 =A0 <DESC>A Jabber Server!</DESC><br> =A0 =A0 =A0 =A0 <URL><a href=3D"http://jabber.yourhost.com/" target= =3D"_blank">http://jabber.yourhost.com/</a></URL><br> =A0 =A0 =A0 </vCard><br> <br> =A0 =A0 =A0 <!--<br> =A0 =A0 =A0 Registration instructions and required fields. The<br> =A0 =A0 =A0 notify attribute will send the server administrator(s)<br> =A0 =A0 =A0 a message after each valid registration if it is set<br> =A0 =A0 =A0 to "yes".<br> =A0 =A0 =A0 --><br> <br> =A0 =A0 =A0 <register notify=3D"yes"><br> =A0 =A0 =A0 =A0 <instructions>Choose a username and password to regis= ter with this server.</instructions><br> =A0 =A0 =A0 =A0 <name/><br> =A0 =A0 =A0 =A0 <email/><br> =A0 =A0 =A0 </register><br> <br> =A0 =A0 =A0 <!--<br> =A0 =A0 =A0 A welcome note that is sent to every new user who registers<br> =A0 =A0 =A0 with your server. Comment it out to disable this function.<br> =A0 =A0 =A0 --><br> <br> =A0 =A0 =A0 <welcome><br> =A0 =A0 =A0 =A0 <subject>Welcome!</subject><br> =A0 =A0 =A0 =A0 <body>Welcome to the Jabber server at <a href=3D"http= ://jabber.youhost.com" target=3D"_blank">http://jabber.youhost.com</a> -- w= e hope you enjoy this service! For information about how to use Jabber, vis= it the Jabber User's Guide at <a href=3D"http://jabber.org/" target=3D"= _blank">http://jabber.org/</a></body><br> =A0 =A0 =A0 </welcome><br> <br> =A0 =A0 =A0 <!--<br> =A0 =A0 =A0 IDs with admin access - these people will receive admin<br> =A0 =A0 =A0 messages (any message to=3D"yourhostname" is an admin= <br> =A0 =A0 =A0 message). =A0These addresses must be local ids, they cannot<br> =A0 =A0 =A0 be remote addresses.<br> <br> =A0 =A0 =A0 Note that they can also send announcements to all<br> =A0 =A0 =A0 users of the server, or to all online users. To use<br> =A0 =A0 =A0 the announcement feature, you need to send raw xml and be<br> =A0 =A0 =A0 logged in as one of the admin users. Here is the syntax<br> =A0 =A0 =A0 for sending an announcement to online users:<br> <br> =A0 =A0 =A0 =A0 <message to=3D"yourhostname/announce/online"&g= t;<br> =A0 =A0 =A0 =A0 =A0 <body>announcement here</body><br> =A0 =A0 =A0 =A0 </message><br> <br> =A0 =A0 =A0 =A0 <message to=3D"yourhostname/announce/motd">= <br> =A0 =A0 =A0 =A0 =A0 <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 i= n</body><br> =A0 =A0 =A0 =A0 </message><br> <br> =A0 =A0 =A0 Sending to /announce/motd/delete will remove any existing<br> =A0 =A0 =A0 motd, and to /announce/motd/update will only update the motd<br= > =A0 =A0 =A0 without re-announcing to all logged in users.<br> <br> =A0 =A0 =A0 The <reply> will be the message that is automatically<br> =A0 =A0 =A0 sent in response to any admin messages.<br> =A0 =A0 =A0 --><br> <br> =A0 =A0 =A0 <!--<br> =A0 =A0 =A0 <admin><br> =A0 =A0 =A0 =A0 <read>support@localhost</read><br> =A0 =A0 =A0 =A0 <write>admin@localhost</write><br> =A0 =A0 =A0 =A0 <reply><br> =A0 =A0 =A0 =A0 =A0 <subject>Auto Reply</subject><br> =A0 =A0 =A0 =A0 =A0 <body>This is a special administrative address. = =A0Your message was received and forwarded to server administrators.</bo= dy><br> =A0 =A0 =A0 =A0 </reply><br> =A0 =A0 =A0 </admin><br> =A0 =A0 =A0 --><br> <br> =A0 =A0 =A0 <!--<br> =A0 =A0 =A0 This is the resource that checks for updated versions<br> =A0 =A0 =A0 of the Jabber server software. Note that you don't lose<br> =A0 =A0 =A0 any functionality if you comment this out. Removing the<br> =A0 =A0 =A0 <update/> config is especially a good strategy if your<br= > =A0 =A0 =A0 server is behind a firewall. If you want to use this<br> =A0 =A0 =A0 feature, change 'localhost' to the hostname or IP addre= ss<br> =A0 =A0 =A0 of your server, making sure that it is the same as your<br> =A0 =A0 =A0 entry for <host/> above.<br> =A0 =A0 =A0 --><br> <br> =A0 =A0 =A0 <!--<br> =A0 =A0 =A0 <update><jabberd:cmdline flag=3D"h">local= host</jabberd:cmdline></update><br> =A0 =A0 =A0 --><br> <br> =A0 =A0 =A0 <!--<br> =A0 =A0 =A0 This enables the server to automatically update the<br> =A0 =A0 =A0 user directory when a vcard is edited. =A0The update is<br> =A0 =A0 =A0 only sent to the first listed jud service below. =A0It is<br> =A0 =A0 =A0 safe to remove this flag if you do not want any users<br> =A0 =A0 =A0 automatically added to the directory.<br> =A0 =A0 =A0 --><br> <br> =A0 =A0 =A0 <vcard2jud/><br> <br> =A0 =A0 =A0 <!--<br> =A0 =A0 =A0 The <browse/> section identifies the transports and other= <br> =A0 =A0 =A0 services that are available from this server. Note that each<br= > =A0 =A0 =A0 entity identified here must exist elsewhere or be further<br> =A0 =A0 =A0 defined in its own <service/> section below. These servic= es<br> =A0 =A0 =A0 will appear in the user interface of Jabber clients that<br> =A0 =A0 =A0 connect to your server.<br> =A0 =A0 =A0 --><br> <br> =A0 =A0 =A0 <browse><br> <br> =A0 =A0 =A0 =A0 <!--<br> =A0 =A0 =A0 =A0 This is the default agent for the master Jabber User<br> =A0 =A0 =A0 =A0 Directory, a.k.a. "JUD", which is located at <a h= ref=3D"http://jabber.org" target=3D"_blank">jabber.org</a>.<br> =A0 =A0 =A0 =A0 You can add separate <service/> sections for addition= al<br> =A0 =A0 =A0 =A0 directories, e.g., one for a company intranet.<br> =A0 =A0 =A0 =A0 --><br> <br> =A0 =A0 =A0 =A0 <!--<br> =A0 =A0 =A0 =A0 <service type=3D"jud" jid=3D"<a href=3D"h= ttp://users.jabber.org" target=3D"_blank">users.jabber.org</a>" name= =3D"Jabber User Directory"><br> =A0 =A0 =A0 =A0 =A0 <ns>jabber:iq:search</ns><br> =A0 =A0 =A0 =A0 =A0 <ns>jabber:iq:register</ns><br> =A0 =A0 =A0 =A0 </service><br> =A0 =A0 =A0 =A0 --><br> <br> =A0 =A0 =A0 =A0 <!--<br> =A0 =A0 =A0 =A0 The following services are examples only, you will need to<= br> =A0 =A0 =A0 =A0 create/modify them to get them working on your Jabber<br> =A0 =A0 =A0 =A0 server. See the README files for each service and/or the<br= > =A0 =A0 =A0 =A0 server howto for further information/instructions.<br> =A0 =A0 =A0 =A0 --><br> <br> =A0 =A0 =A0 =A0 <!-- we're commenting these out, of course :)<br> <br> =A0 =A0 =A0 =A0 <conference type=3D"private" jid=3D"confe= rence.localhost" name=3D"Private Conferencing"/><br> <br> =A0 =A0 =A0 =A0 <service type=3D"aim" jid=3D"aim.localhos= t" name=3D"AIM Transport"><br> =A0 =A0 =A0 =A0 =A0 <ns>jabber:iq:gateway</ns><br> =A0 =A0 =A0 =A0 =A0 <ns>jabber:iq:register</ns><br> =A0 =A0 =A0 =A0 </service><br> <br> =A0 =A0 =A0 =A0 <service type=3D"yahoo" jid=3D"yahoo.loca= lhost" name=3D"Yahoo! Transport"><br> =A0 =A0 =A0 =A0 =A0 <ns>jabber:iq:gateway</ns><br> =A0 =A0 =A0 =A0 =A0 <ns>jabber:iq:register</ns><br> =A0 =A0 =A0 =A0 </service><br> <br> =A0 =A0 =A0 =A0 end of <service/> examples --><br> <br> =A0 =A0 =A0 </browse><br> <br> =A0 =A0 </jsm><br> <br> =A0 =A0 <!--<br> =A0 =A0 The following section dynamically loads the individual<br> =A0 =A0 modules that make up the session manager. Remove or<br> =A0 =A0 comment out modules to disable them. Note that the order<br> =A0 =A0 of modules is important, since packets are delivered<br> =A0 =A0 based on the following order!!<br> =A0 =A0 --><br> <br> =A0 =A0 <load main=3D"jsm"><br> =A0 =A0 =A0 <jsm>/usr/pkg/lib/jabberd/jsm.so</jsm><br> =A0 =A0 =A0 <mod_echo>/usr/pkg/lib/jabberd/jsm.so</mod_echo><br= > =A0 =A0 =A0 <mod_roster>/usr/pkg/lib/jabberd/jsm.so</mod_roster>= ;<br> =A0 =A0 =A0 <mod_time>/usr/pkg/lib/jabberd/jsm.so</mod_time><br= > =A0 =A0 =A0 <mod_vcard>/usr/pkg/lib/jabberd/jsm.so</mod_vcard><= br> =A0 =A0 =A0 <mod_last>/usr/pkg/lib/jabberd/jsm.so</mod_last><br= > =A0 =A0 =A0 <mod_version>/usr/pkg/lib/jabberd/jsm.so</mod_version&= gt;<br> =A0 =A0 =A0 <mod_announce>/usr/pkg/lib/jabberd/jsm.so</mod_announc= e><br> =A0 =A0 =A0 <mod_agents>/usr/pkg/lib/jabberd/jsm.so</mod_agents>= ;<br> =A0 =A0 =A0 <mod_browse>/usr/pkg/lib/jabberd/jsm.so</mod_browse>= ;<br> =A0 =A0 =A0 <mod_admin>/usr/pkg/lib/jabberd/jsm.so</mod_admin><= br> =A0 =A0 =A0 <mod_filter>/usr/pkg/lib/jabberd/jsm.so</mod_filter>= ;<br> =A0 =A0 =A0 <mod_offline>/usr/pkg/lib/jabberd/jsm.so</mod_offline&= gt;<br> =A0 =A0 =A0 <mod_presence>/usr/pkg/lib/jabberd/jsm.so</mod_presenc= e><br> =A0 =A0 =A0 <mod_auth_plain>/usr/pkg/lib/jabberd/jsm.so</mod_auth_= plain><br> =A0 =A0 =A0 <mod_auth_digest>/usr/pkg/lib/jabberd/jsm.so</mod_auth= _digest><br> =A0 =A0 =A0 <mod_auth_0k>/usr/pkg/lib/jabberd/jsm.so</mod_auth_0k&= gt;<br> =A0 =A0 =A0 <mod_log>/usr/pkg/lib/jabberd/jsm.so</mod_log><br> =A0 =A0 =A0 <mod_register>/usr/pkg/lib/jabberd/jsm.so</mod_registe= r><br> =A0 =A0 =A0 <mod_xml>/usr/pkg/lib/jabberd/jsm.so</mod_xml><br> =A0 =A0 </load><br> <br> =A0 </service><br> <br> =A0 <!-- OK, we've finished defining the Jabber Session Manager. --&= gt;<br> <br> =A0 <!-- The <xdb/> component handles all data storage, using the = filesystem. --><br> <br> =A0 <xdb id=3D"xdb"><br> =A0 =A0 <host/><br> =A0 =A0 <load><br> =A0 =A0 =A0 <xdb_file>/usr/pkg/lib/jabberd/xdb_file.so</xdb_file&g= t;<br> =A0 =A0 </load><br> =A0 =A0 <xdb_file xmlns=3D"jabber:config:xdb_file"><br> =A0 =A0 =A0 <spool><jabberd:cmdline flag=3D's'>/var/spo= ol/jabberd</jabberd:cmdline></spool><br> =A0 =A0 </xdb_file><br> =A0 </xdb><br> <br> =A0 <!--<br> =A0 The following service manages incoming client socket connections.<br> =A0 There are several items you can set here to optimize performance:<br> <br> =A0 =A0 * authtime - default is unlimited, but you can set this to<br> =A0 =A0 =A0 limit the amount of time allowed for authentication to be<br> =A0 =A0 =A0 completed, e.g., <authtime>10</authtime> for 10 sec= onds<br> <br> =A0 =A0 * karma - this is an input/output rate limiting system that<br> =A0 =A0 =A0 the Jabber team came up with to prevent bandwidth hogging.<br> =A0 =A0 =A0 For details about karma, read the io section at the bottom<br> =A0 =A0 =A0 and/or see <a href=3D"http://docs.jabber.org" target=3D"_blank"= >docs.jabber.org</a>. These are the low settings and<br> =A0 =A0 =A0 apply per connection/socket and can be changed as desired.<br> =A0 --><br> <br> =A0 <service id=3D"c2s"><br> =A0 =A0 <load><br> =A0 =A0 =A0 <pthsock_client>/usr/pkg/lib/jabberd/pthsock_client.so<= ;/pthsock_client><br> =A0 =A0 </load><br> =A0 =A0 <pthcsock xmlns=3D'jabber:config:pth-csock'><br> =A0 =A0 =A0 <authtime/><br> =A0 =A0 =A0 <karma><br> =A0 =A0 =A0 =A0 <init>10</init><br> =A0 =A0 =A0 =A0 <max>10</max><br> =A0 =A0 =A0 =A0 <inc>1</inc><br> =A0 =A0 =A0 =A0 <dec>1</dec><br> =A0 =A0 =A0 =A0 <penalty>-6</penalty><br> =A0 =A0 =A0 =A0 <restore>10</restore><br> =A0 =A0 =A0 </karma><br> <br> =A0 =A0 =A0 <!--<br> =A0 =A0 =A0 Use these to listen on particular addresses and/or ports.<br> =A0 =A0 =A0 <ip port=3D"5222">127.0.0.1</ip><br> =A0 =A0 =A0 --><br> =A0 =A0 =A0 <ip port=3D"5222"/><br> <br> =A0 =A0 =A0 <!--<br> =A0 =A0 =A0 The <ssl/> tag acts pretty much like the <ip/> tag,= <br> =A0 =A0 =A0 except it defines that SSL is to be used on the<br> =A0 =A0 =A0 ports and IP addresses specified. You must specify<br> =A0 =A0 =A0 an IP address here, or the connections will fail.<br> =A0 =A0 =A0 <ssl port=3D'5223'>127.0.0.1</ssl><br> =A0 =A0 =A0 <ssl port=3D'5224'>192.168.1.100</ssl><br> =A0 =A0 =A0 --><br> <br> =A0 =A0 </pthcsock><br> =A0 </service><br> <br> =A0 <!--<br> =A0 This is the default server error logging component,<br> =A0 which copies to a file and to STDERR.<br> =A0 --><br> <br> =A0 <log id=3D'elogger'><br> =A0 =A0 <host/><br> =A0 =A0 <logtype/><br> =A0 =A0 <format>%d: [%t] (%h): %s</format><br> =A0 =A0 <file>/var/log/jabberd/error.log</file><br> =A0 =A0 <stderr/><br> =A0 </log><br> <br> =A0 <!--<br> =A0 This is the default server record logging component,<br> =A0 which logs general statistical/tracking data.<br> =A0 --><br> <br> =A0 <log id=3D'rlogger'><br> =A0 =A0 <host/><br> =A0 =A0 <logtype>record</logtype><br> =A0 =A0 <format>%d %h %s</format><br> =A0 =A0 <file>/var/log/jabberd/record.log</file><br> =A0 </log><br> <br> =A0 <!-- The following two services are for handling server-to-server tr= affic. --><br> <br> =A0 <!-- External asychronous DNS resolver --><br> <br> =A0 <service id=3D"dnsrv"><br> =A0 =A0 <host/><br> =A0 =A0 <load><br> =A0 =A0 =A0 <dnsrv>/usr/pkg/lib/jabberd/dnsrv.so</dnsrv><br> =A0 =A0 </load><br> =A0 =A0 <dnsrv xmlns=3D"jabber:config:dnsrv"><br> =A0 =A0 =A0 =A0 <resend service=3D"_jabber._tcp">s2s</re= send> <!-- for supporting SRV records --><br> =A0 =A0 =A0 =A0 <resend>s2s</resend><br> =A0 =A0 </dnsrv><br> =A0 </service><br> <br> =A0 <!--<br> =A0 The following 's2s' config handles server connections and<br> =A0 dialback hostname verification. =A0The <legacy/> element is<br> =A0 here to enable communication with old 1.0 servers. The<br> =A0 karma settings are a little higher here to handle the<br> =A0 higher traffic of server-to-server connections (read<br> =A0 the io section below for more details, medium settings).<br> =A0 --><br> <br> =A0 <service id=3D"s2s"><br> =A0 =A0 <load><br> =A0 =A0 =A0 <dialback>/usr/pkg/lib/jabberd/dialback.so</dialback&g= t;<br> =A0 =A0 </load><br> =A0 =A0 <dialback xmlns=3D'jabber:config:dialback'><br> =A0 =A0 =A0 <legacy/><br> =A0 =A0 =A0 <!-- Use these to listen on particular addresses and/or port= s.<br> =A0 =A0 =A0 <ip port=3D"7000"/><br> =A0 =A0 =A0 <ip port=3D"5269">127.0.0.1</ip><br> =A0 =A0 =A0 --><br> =A0 =A0 =A0 <ip port=3D"5269"/><br> =A0 =A0 =A0 <karma><br> =A0 =A0 =A0 =A0 <init>50</init><br> =A0 =A0 =A0 =A0 <max>50</max><br> =A0 =A0 =A0 =A0 <inc>4</inc><br> =A0 =A0 =A0 =A0 <dec>1</dec><br> =A0 =A0 =A0 =A0 <penalty>-5</penalty><br> =A0 =A0 =A0 =A0 <restore>50</restore><br> =A0 =A0 =A0 </karma><br> =A0 =A0 </dialback><br> =A0 </service><br> <br> =A0 <!--<br> =A0 If you identified additional agents in the main <service/><br> =A0 section (see examples above), you'll need to define each<br> =A0 of them here using a separate <service/> section for each<br> =A0 <agent/> you identified. Note that the <agent/> sections<br= > =A0 determine what gets shown to clients that connect to your<br> =A0 server, whereas the following <service/> sections define<br> =A0 these services within the server itself. The following are<br> =A0 examples only, you will need to create/modify them to get<br> =A0 them working on your Jabber server. See the README files<br> =A0 for each agent and/or the server howto for further<br> =A0 information/instructions.<br> =A0 --><br> <br> =A0 <!-- we're commenting these out, of course :)<br> <br> =A0 <service id=3D"conference"><br> =A0 =A0 <load><br> =A0 =A0 =A0 <groupchat>/path/to/groupchat.so</groupchat><br> =A0 =A0 </load><br> =A0 =A0 <host>conference.localhost</host><br> =A0 </service><br> <br> =A0 <service id=3D"irc"><br> =A0 =A0 <host>irc.localhost</host><br> =A0 </service><br> <br> =A0 <service id=3D"aim.localhost"><br> =A0 =A0 <accept><br> =A0 =A0 =A0 <ip/><br> =A0 =A0 =A0 <port>7009</port><br> =A0 =A0 =A0 <secret>jabber-rocks</secret><br> =A0 =A0 </accept><br> =A0 </service><br> <br> =A0 <service id=3D"yahoo.localhost"><br> =A0 =A0 <accept><br> =A0 =A0 =A0 <ip/><br> =A0 =A0 =A0 <port>9001</port><br> =A0 =A0 =A0 <secret>jabber-rocks</secret><br> =A0 =A0 </accept><br> =A0 </service><br> <br> =A0 end of <service/> examples --><br> <br> =A0 <!--<br> =A0 The following <io/> config initializes the top-level<br> =A0 I/O, otherwise known as MIO (Managed Input/Output).<br> =A0 --><br> <br> =A0 <io><br> <br> =A0 =A0 <!-- Set the default karma for *all* sockets --><br> =A0 =A0 <!-- definition of terms:<br> <br> =A0 =A0 =A0 * Avg. Throughput - The number of bytes you can<br> =A0 =A0 =A0 =A0 send every second without incuring any penalty.<br> <br> =A0 =A0 =A0 * Burst Allowed - The maximum number of bytes you<br> =A0 =A0 =A0 =A0 can send in 2 seconds without incurring any penalty.<br> <br> =A0 =A0 =A0 * Max Sustained Rate - If you send data as fast as<br> =A0 =A0 =A0 =A0 you can, you will hit penalty, and will not be<br> =A0 =A0 =A0 =A0 able to send for 10 seconds; the max sustained<br> =A0 =A0 =A0 =A0 rate is the average rate you can dump data when<br> =A0 =A0 =A0 =A0 you are dumping as much data as you can, as fast<br> =A0 =A0 =A0 =A0 as you can.<br> <br> =A0 =A0 =A0 * Seconds to Recover from Burst - The amount of time<br> =A0 =A0 =A0 =A0 it will take to reach Avg. Throughput capability<br> =A0 =A0 =A0 =A0 after sending a max burst of data.<br> <br> =A0 =A0 =A0 * Penalty Length - The length of your penalty is<br> =A0 =A0 =A0 =A0 determined according to this formula:<br> =A0 =A0 =A0 =A0 =A0 =A0 =A0 abs(penalty) * Heartbeat seconds<br> =A0 =A0 =A0 =A0 E.g., a penalty of -5 and heartbeat of 2 will<br> =A0 =A0 =A0 =A0 cause your penalty length to be 10 seconds.<br> =A0 =A0 =A0 =A0 Note that a penalty CANNOT be less than -100,<br> =A0 =A0 =A0 =A0 otherwise strange things might happen.<br> <br> =A0 =A0 --><br> =A0 =A0 <!-- Example of Low Karma Limits<br> =A0 =A0 =A0 =A0 Avg. Throughput: 1k-2k/s<br> =A0 =A0 =A0 =A0 Burst Allowed To: 5.5k/s<br> =A0 =A0 =A0 =A0 Max Sustained Rate: 485b/s<br> =A0 =A0 =A0 =A0 Seconds to Recover from Burst: 20<br> =A0 =A0 =A0 =A0 Penalty Length: 12 seconds<br> =A0 =A0 <karma><br> =A0 =A0 =A0 <heartbeat>2</heartbeat><br> =A0 =A0 =A0 <init>10</init><br> =A0 =A0 =A0 <max>10</max><br> =A0 =A0 =A0 <inc>1</inc><br> =A0 =A0 =A0 <dec>1</dec><br> =A0 =A0 =A0 <penalty>-6</penalty><br> =A0 =A0 =A0 <restore>10</restore><br> =A0 =A0 </karma><br> =A0 =A0 --><br> <br> =A0 =A0 <!-- Example of Medium Karma Limits<br> =A0 =A0 =A0 =A0 Avg. Throughput: 5k-10k/s<br> =A0 =A0 =A0 =A0 Burst Allowed: 125.5k/s<br> =A0 =A0 =A0 =A0 Max Sustained Rate: 12.6k/s<br> =A0 =A0 =A0 =A0 Seconds to Recover From Burst: 25<br> =A0 =A0 =A0 =A0 Penalty Length: 10 seconds<br> =A0 =A0 <karma><br> =A0 =A0 =A0 <heartbeat>2</heartbeat><br> =A0 =A0 =A0 <init>50</init><br> =A0 =A0 =A0 <max>50</max><br> =A0 =A0 =A0 <inc>4</inc><br> =A0 =A0 =A0 <dec>1</dec><br> =A0 =A0 =A0 <penalty>-5</penalty><br> =A0 =A0 =A0 <restore>50</restore><br> =A0 =A0 </karma><br> =A0 =A0 --><br> <br> =A0 =A0 <!-- Example of High Karma Limits<br> =A0 =A0 =A0 =A0 Avg. Throughput: 5k-10k/s<br> =A0 =A0 =A0 =A0 Burst Allowed: 206k/s<br> =A0 =A0 =A0 =A0 Max Sustained Rate: 34.3k/s<br> =A0 =A0 =A0 =A0 Seconds to Recover from Burst: 21<br> =A0 =A0 =A0 =A0 Penalty Length: 6 seconds<br> =A0 =A0 <karma><br> =A0 =A0 =A0 <heartbeat>2</heartbeat><br> =A0 =A0 =A0 <init>64</init><br> =A0 =A0 =A0 <max>64</max><br> =A0 =A0 =A0 <inc>6</inc><br> =A0 =A0 =A0 <dec>1</dec><br> =A0 =A0 =A0 <penalty>-3</penalty><br> =A0 =A0 =A0 <restore>64</restore><br> =A0 =A0 </karma><br> =A0 =A0 --><br> <br> =A0 =A0 <!--<br> =A0 =A0 Set rate limits to monitor the number of connection<br> =A0 =A0 attempts from a single IP, any more than [points]<br> =A0 =A0 within [time] will engage the limit. =A0This setting<br> =A0 =A0 applies to all incoming connections to any service,<br> =A0 =A0 unless otherwise overridden by that service.<br> =A0 =A0 --><br> <br> =A0 =A0 <rate points=3D"5" time=3D"25"/><br> <br> =A0 =A0 <!--<br> =A0 =A0 The following section initializes SSL for top-level I/O.<br> =A0 =A0 This works only when the server is compiled with openssl!<br> =A0 =A0 --><br> =A0 =A0 <!--<br> =A0 =A0 <ssl><br> =A0 =A0 =A0 <key ip=3D'192.168.1.1'>/path/to/cert_and_key.pem= </key><br> =A0 =A0 =A0 <key ip=3D'192.168.1.100'>/path/to/other/cert_and= _key.pem</key><br> =A0 =A0 </ssl><br> =A0 =A0 --><br> <br> =A0 =A0 <!--<br> =A0 =A0 The following section is used to allow or deny<br> =A0 =A0 communications from specified IP networks or<br> =A0 =A0 addressses. If there is no <allow/> section,<br> =A0 =A0 then *all* IPs will be allowed to connect. If<br> =A0 =A0 you allow one block, then only that block may<br> =A0 =A0 connect. Note that <allow/> is checked before<br> =A0 =A0 <deny/>, so if a specific address is allowed<br> =A0 =A0 but the network for that address is denied,<br> =A0 =A0 then that address will still be denied.<br> =A0 =A0 --><br> =A0 =A0 <!--<br> =A0 =A0 <allow><ip>127.0.0.0</ip><mask>255.255.255.= 0</mask></allow><br> =A0 =A0 <allow><ip>12.34.56.78</ip></allow><br> =A0 =A0 <deny><ip>22.11.44.0</ip><mask>255.255.255.= 0</mask></deny><br> =A0 =A0 --><br> <br> =A0 </io><br> <br> =A0 <!--<br> =A0 This specifies the file to store the pid of the process in.<br> =A0 <pidfile>/var/run/jabber.pid</pidfile><br> =A0 <pidfile>/var/run/jabberd/jabber.pid</pidfile><br> =A0 --><br> <br> </jabber><br> <br> ############### end of jabber.xml ##################<br> <div class=3D"HOEnZb"><div class=3D"h5">___________________________________= ____________<br> JAdmin mailing list<br> Info: <a href=3D"http://mail.jabber.org/mailman/listinfo/jadmin" target=3D"= _blank">http://mail.jabber.org/mailman/listinfo/jadmin</a><br> Unsubscribe: <a href=3D"mailto:[email protected]">JAdmin-unsubs= [email protected]</a><br> _______________________________________________<br> </div></div></blockquote></div><br></div> --047d7b6d89c238b2dd04ccdbfa10-- --===============0719484346== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ JAdmin mailing list Info: http://mail.jabber.org/mailman/listinfo/jadmin Unsubscribe: [email protected] _______________________________________________ --===============0719484346==--