Rajesh Dharmalingam wrote:
>
> OldSSL enable
> DeclareMonitor 192.168.1.21
> AdminPort 5200
> ClientPort 5222
> ServerPort 5269
> SSLCertificateFile
/usr/local/chat/DJabberd-0.83/server-cert.pem
> SSLCertificateKeyFile
/usr/local/chat/DJabberd-0.83/server-key.pem
> <VHost test.com <http://test.com>>
> S2S enable
> #S2S false
> RequireSSL yes
> #RequireSSL no
> <Plugin DJabberd::Authen::HTDigest>
> Realm djabberd
> HtDigest
/usr/local/chat/DJabberd-0.83/djabberd.users
> </Plugin>
> <Plugin DJabberd::Authen::AllowedUsers>
> Policy accept
> AllowedUsers AAA BBB test
> </Plugin>
> <Plugin DJabberd::RosterStorage::SQLite>
> Database /usr/local/chat/DJabberd-
0.83/djabberd.sqlite
> </Plugin>
> #<Plugin DJabberd::RosterStorage::InMemoryOnly
/>
>
> </VHost>
>
The best thing I can think of right now is to try adding the
delivery
plugins explicitly:
<Plugin DJabberd: elivery:
:Local />
<Plugin DJabberd: elivery:
:S2S />
This shouldn't be necessary since they should load by
default in the
absense of any other plugins of this type, but it's probably
best to
eliminate this before trying anything more complicated.
It would also be useful if you could get your logging output
to show the
full set of logging levels so that we can see the debug
output. Sadly,
I've forgotten how the logging configuration works, but if
you look up
Log4perl on CPAN hopefully there will be some explanation
there.
Cheers,
Martin
|