I'm testing out cyrus murder with v2.2.12 and I noticed that lmtpproxyd
doesn't seem to support the -a (preauth) option that the regular lmtpd
does.
On my standalone cyrus system, I use lmtpd -a to accept mail from our
campus mail relays running postfix, and I use tcpwrappers to block all
use with uw-imapd. They can then access their mail folder without
having to authenticate themselves.
Attached is a quick proof-of-concept patch against the current CVS
(2.2.x) which allows the services to be run outside of master and
implements PREAUTH for imapd and allows EXTERNAL to be used
their mail folder without
having to authenticate themselves.
Attached is a quick proof-of-concept patch against the current CVS (2.2.x)
which allows the services to be run outside of master and implements PREAUTH
for imapd and allows EXTERNAL to be used for pop3d and nntpd. In order for
the services
/imapd is
what we now use with uw-imapd. They can then access their mail folder
without having to authenticate themselves.
Attached is a quick proof-of-concept patch against the current CVS
(2.2.x) which allows the services to be run outside of master and
implements PREAUTH for imapd and allows
Derrick J Brashear wrote:
On Tue, 28 Sep 2004, Ken Murchison wrote:
Derrick J Brashear wrote:
I guess you assume then that imapd is setuid, otherwise, how is a
user expected to run it and have access to the mail store? that's
fine, i just want to know your expectations up front are in line with
use kerberos auth in sasl and pam to automatically get a ticket (or
kinit manually).. *poof* no password/username prompt. If you already run
kerberos this is fairly easy to setup.
Christiaan den Besten wrote:
Cyrus doesn't support running imapd from the command line. All process
are
