Starting with the 2.1.0 release (any any builds via CVS), please supply
the following information when reporting a problem with Cyrus:
1. Output of the cyradm(1) 'version' command. If you are having
problems with Perl, then connect to the server with imtest(1) and use
the command:
a ID NIL
This info will show us the timestamp of the source code, the server
platform, as well as most (if not all) of the compile-time options.
2. Contents of imapd.conf. This will show us the run-time
configuration.
3. Contents of cyrus.conf. This will show us how your services are
configured.
Peter Pilsl wrote:
>
> while doing a stresstest on our mailserver we had a big problem after
> the first 100mails (sent in 2 seconds) due to the fact that one of two
> running lmtpd-processes consumed 1GB of memory, which was to much
> for our system and resulted in neverending swapping until I killed all
> related mail-processes.
>
> I couldnt reproduce the problem and on further tests there was no
> similar problem. (oh yes, we had other problems - I'm not happy with
> our emailserver - it cannot deal with more than 3mails per second in
> average for one hour or so. While this is not a realistic number and
> we dont have a problem with our 100 mails per hour I expected it to
> handle a bigger load.)
>
> Nevertheless I'm worried if this happens again - even on less load.
>
> lmtpd is invoked via cyrus-master-process when deliver is called from
> our procmailscript.
>
> thnx,
> peter
>
> --
> mag. peter pilsl
>
> phone: +43 676 3574035
> fax : +43 676 3546512
> email: [EMAIL PROTECTED]
> sms : [EMAIL PROTECTED]
>
> pgp-key available
--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26 Orchard Park, NY 14127
--PGP Public Key-- http://www.oceana.com/~ken/ksm.pgp
