/etc/pyaimt.conf.xml is in pyaimt 0.8.0.1-4.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 | <pyaimt>
<!-- The JabberID of the transport. -->
<jid>aim.example.org</jid>
<!-- The JabberID of the conference room handler. -->
<!-- GROUPCHAT IS NOT STABLE YET -->
<confjid>chatrooms.aim.example.org</confjid>
<!-- The component JID of the transport. Unless you're doing clustering, leave this alone -->
<!-- <compjid>aim1</compjid> -->
<!-- The IP address of the main Jabber server -->
<mainServer>127.0.0.1</mainServer>
<!-- The JID of the main Jabber server -->
<mainServerJID>jabber.localhost</mainServerJID>
<!-- The website of the Jabber service -->
<website>http://jabber.localhost/</website>
<!-- The TCP port to connect to the Jabber server on -->
<!-- (this is the default for Jabberd2) -->
<port>5347</port>
<!-- The TCP port that the web admin interface will answer on -->
<!-- (uncomment to enable) -->
<!-- <webport>12345</webport> -->
<!-- The authentication token to use when connecting to the Jabber server -->
<secret>secret</secret>
<!-- The default language to use (for error/status messages) -->
<lang>en</lang>
<!-- The hostname of the AOL login server you wish to connect to -->
<aimServer>login.oscar.aol.com</aimServer>
<!-- The port of the AOL server you wish to connect to -->
<aimPort>5190</aimPort>
<!-- The name of Socks Proxy if connecting thru a proxy -->
<!-- <socksProxyServer>im-proxy2</socksProxyServer> -->
<!-- The Socks Proxy port to use when connecting thru a proxy -->
<!-- <socksProxyPort>1080</socksProxyPort> -->
<!-- Send greeting on login (enter text to be sent to users here) -->
<!-- <sessionGreeting>enter message here</sessionGreeting> -->
<!-- Send message on successful registration -->
<!-- <registerMessage>You have successfully registered with PyAIMt</registerMessage> -->
<!-- Allow users of AIM gateway to chat with ICQ users -->
<!-- (uncomment to enable) -->
<!-- <crossChat/> -->
<!-- Disable registration with the transport -->
<!-- (uncomment to disable) -->
<!-- <disableRegister/> -->
<!-- Enable automatic invitation to reconnect on restart -->
<!-- (uncomment to enable) -->
<!-- <enableAutoInvite/> -->
<!-- Disable xhtml support (messages with fonts and colors) -->
<!-- (uncomment to disable) -->
<!-- <disableXHTML/> -->
<!-- Disable mail notifications -->
<!-- (uncomment to disable) -->
<!-- <disableMailNotifications/> -->
<!-- Disable use of default avatar if none is specified -->
<!-- (uncomment to disable) -->
<!-- <disableDefaultAvatar/> -->
<!-- Disable use of iq-based avatars (JEP-0008) -->
<!-- (uncomment to disable) -->
<!-- <disableIQAvatars/> -->
<!-- Disable use of vcard-based avatars (JEP-0153) -->
<!-- (uncomment to disable) -->
<!-- <disableVCardAvatars/> -->
<!-- Disable use of PEP-based avatars (JEP-0084) -->
<!-- (uncomment to disable) -->
<!-- NOT IMPLEMENTED YET -->
<!-- <disablePEPAvatars/> -->
<!-- You can choose which users you wish to have as administrators. These users can perform some tasks with Ad-Hoc commands that others cannot -->
<admins>
<!--<jid>admin@host.com</jid>-->
</admins>
<!-- You can select which event loop PyAIMt will use. It's probably safe to leave this as the default -->
<!-- Use epoll for high-load Linux servers running kernel 2.6 or above -->
<!--<reactor>epoll</reactor>-->
<!-- Use kqueue for high-load FreeBSD servers -->
<!--<reactor>kqueue</reactor>-->
<!-- Use poll for high-load Unix servers -->
<!--<reactor>poll</reactor>-->
<!-- You can select which spool storage method you wish to use -->
<!-- Available methods are: -->
<!-- xmlfiles: single xml files in the spool directory in hashed dirs (default)-->
<!-- legacyaimtransport: compatible with c-based aim transport, less functionality -->
<!-- mysql: registration information stored in a MySQL database -->
<!--<xdbDriver>xmlfiles</xdbDriver>-->
<!-- For MySQL -->
<!--<xdbDriver>mysql</xdbDriver>-->
<!--<xdbDriver_mysql>-->
<!--<username>pyaimt</username>-->
<!--<password>pyaimt</password>-->
<!--<database>pyaimt</database>-->
<!--<server>localhost</server>-->
<!--<format>encrypted</format>--> <!-- Enable encryption of passwords -->
<!--</xdbDriver_mysql>-->
<!-- For XMLFiles -->
<!--<xdbDriver>xmlfiles</xdbDriver>-->
<!--<xdbDriver_xmlfiles>-->
<!--<format>encrypted</format>--> <!-- Enable encryption of passwords -->
<!--</xdbDriver_xmlfiles>-->
<!-- Only grab avatars when a chat is initiated. -->
<!-- <avatarsOnlyOnChat/> -->
<!-- Disable all avatar functionality. Might be necessary if you -->
<!-- do not have PIL installed. -->
<!-- <disableAvatars/> -->
<!-- Disable automatic send (via im) of away message when away set. -->
<!-- Note that away messages are -in addition to- the away status -->
<!-- message. -->
<!-- <disableAwayMessage/> -->
<!-- Use Jabber.com's XCP component protocol extensions. -->
<!-- <useXCP/> -->
<!-- SASL username used to bind to Jabber server. -->
<!-- secret, above, is used for sasl password -->
<!-- NOTE: This does not work with Twisted > 2.2.0. -->
<!-- <saslUsername>username</saslUsername> -->
<!-- Use external component binding. -->
<!-- This dodges the need to manually configure all jids that talk to this transport. -->
<!-- Jabberd2 requires saslUsername and useRouteWrap for this to work. -->
<!-- Wildfire as of 2.6.0 requires just this. -->
<!-- <useComponentBinding/> -->
<!-- Wrap stanzas in <route> stanza. -->
<!-- Jabberd2 requires this for useComponentBinding. -->
<!-- <useRouteWrap/> -->
<!-- JID of message archive service -->
<!-- <messageArchiveJID>datasink.example.org</messageArchiveJID> -->
<!-- If registration authentication is used, enter the method -->
<!-- Auth configs often require additional options to be specified. -->
<!-- See associated config entries per authRegister example. -->
<!-- NOTE: limited to LDAP for now -->
<!-- THIS IS UNTESTED AS OF YET -->
<!-- <authRegister>LDAP</authRegister> -->
<!-- For LDAP auth, make sure to uncomment <authRegister_LDAP> -->
<!-- and </authRegister_LDAP> and fill out the options in between. -->
<!-- <authRegister_LDAP> -->
<!-- The fqdn or ip address of the LDAP server -->
<!-- <server>ldap.example.org</server> -->
<!-- The Root DN to be used to perform LDAP searches -->
<!-- <rootDN>CN=Administrator,CN=Users,DC=example,DC=org</rootDN> -->
<!-- The password for the Root DN -->
<!-- <password>SECRET</password> -->
<!-- The Base DN to search for users -->
<!-- <baseDN>DC=example,DC=org</baseDN> -->
<!-- The attribute to search for the user ID. -->
<!-- 'samAccountname' in Windows, 'uid' on most other systems -->
<!-- <uidAttr>samAccountname</uidAttr> -->
<!-- </authRegister_LDAP> -->
</pyaimt>
|