Re: Cyrus-2.1 + murder: can't disable apop.

From: Ken Murchison (no email)
Date: Tue Apr 04 2006 - 09:14:05 EDT

  • Next message: Kjetil Torgrim Homme: "Re: Allow plaintext and TLS"

    Alexander Vlasov wrote:
    > Hello everyone,
    > We're trying to migrate from single-server setup to murder and we faced the
    > following problem: setting 'allowapop: no' has no effect on murder setup. This
    > option is set to 'no' on all backends and frontend/murder; when I try to connect
    > to backends apop seems to be disabled
    > wolf:~# telnet n1 110
    > Trying
    > Connected to n1.mail.internal.
    > Escape character is '^]'.
    > +OK pop3 server ready
    > but on frontend greetings looks like apop-enabled
    > wolf:~# telnet localhost 110
    > Trying
    > Connected to localhost.localdomain.
    > Escape character is '^]'.
    > +OK Cyrus POP3 Murder v2.1.18-IPv6-Debian-2.1.18-1.0.0.gala.0
    > server ready <>
    > despite allowapop is disabled
    > wolf:~# grep allowapop: /etc/imapd.conf
    > allowapop: no
    > With apop, I'll quickly run out of randomness and cyrus will stuck.
    > Can anyone explain me how to disable apop in my case?

    Its entirely possible that the ALLOWPOP code wasn't put in pop3proxyd in
    Cyrus 2.1. I'd recommed that you upgrade to Cyrus 2.2, or you'll have
    to patch pop3proxyd.c yourself.

    Kenneth Murchison
    Systems Programmer
    Project Cyrus Developer/Maintainer
    Carnegie Mellon University
    Cyrus Home Page:
    Cyrus Wiki/FAQ:
    List Archives/Info:

  • Next message: Kjetil Torgrim Homme: "Re: Allow plaintext and TLS"

    Hosted Email Solutions

    Invaluement Anti-Spam DNSBLs

    Powered By FreeBSD   Powered By FreeBSD