Matt J Bradshaw wrote:
>
> hello all,
>
> i'm running into some (painful!) problems with my fresh cyrus-imap 2.0.15
> installation and would *really* appreciate any guru-advice i can get.
>
> master starts up fine (or at least appears to) and is listening on its
> specified ports (143 and 993). however, any connection to those ports
> hangs waiting for the greeting and the spawned imapd process dies. it
> leaves this in the syslog:
>
> process 17601 exited, signalled to death by 11
>
> ouch. that's pretty much all the diagnostics i have. it's not a system
> issue, packet-filtering and tcpwrappers are both fine. :)
What is the logging level set to in syslog.conf. I recommend setting
local6.debug to get as many messages as possible. Make sure that
[x]inetd is not also listening on these ports (either check
[x]inetd.conf or run 'fuser -n tcp 143' and check the pids).
> build information:
>
> redhat-linux-6.2 (kernel2.2.16)
> cyrus-imap-2.0.15
> cyrus-sasl-1.5.24
> BerkeleyDB-3.2.9
> openssl-0.9.6b
>
> /etc/imapd.conf:
>
> configdirectory: /var/imap
> partition-default: /var/spool/imap
> admins: cyrus
> sasl_pwcheck_method: passwd
> tls_cert_file: /var/imap/server.pem
> tls_key_file: /var/imap/server.pem
> allowplaintext: yes
>
> the only funny compile option was to disable libwrap (--without-libwrap i
> believe) as i thought tcpwrapper support was broken bc of past experience.
> btw, you *may* want to change your use of tcpwrappers to bring it in line
> with standard use. this is with regard to the service name usually being
> the process name (*not* the service name).
The tcpwrappers code _should_ use the service name from cyrus.conf, and
not the process name. For example,
imaps cmd="imapd -s" listen="993"
would use 'imaps' as the service name.
Ken
--
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
