Hello all!
Anyone wants working AV solution for use with Cyrus IMAPD and sendmail?
I am using it for few months - it works fine. It based AVP for BSD/FreeBSD
software by Kaspersky Lab. http://www.kaspersky.com If it's intresting to
someone, I'll send step-by-step install instructions, to the list
Quoting Mobeen Azhar <[EMAIL PROTECTED]>:
> I have not been able to use deliver since I upgraded from 1.5 to 2.x.
> and
> had to revert to using sieve.
It's written in the upgrade notice, that deliver is only a wrapper to
the lmtp server and that a lmtp client is required.
I also have a filteri
Werner Reisberger wrote:
>
> Quoting Mobeen Azhar <[EMAIL PROTECTED]>:
>
> > I have not been able to use deliver since I upgraded from 1.5 to 2.x.
> > and
> > had to revert to using sieve.
>
> It's written in the upgrade notice, that deliver is only a wrapper to
> the lmtp server and that a l
Cyrus imapd works great, but I have a couple outstanding issues where
users are getting unexpected behavior. The problems are not reproducible
but happen occasionally. I suspect the client (Outlook) or the user.
Now if I look in the log files, I can see people logging in, but not
what commands ar
On Tue, Feb 13, 2001 at 10:31:49AM +0100, Werner Reisberger wrote:
> - drop procmail completly
Well, if you have ever looked into procmail's source code you would not
hesitate... It is _ugly_.
Gabor
--
Gabor Gombas Eotvos Lorand University
E-mail: [EMAIL
This is a result of the file descriptor problem we were having; I
posted a patch several days ago. Let me know if you can't find it.
Larry
Date: Tue, 13 Feb 2001 00:23:31 -0500 (EST)
From: "Marc G. Fournier" <[EMAIL PROTECTED]>
Just tried going back to db 3.1.17, to see if that makes
I have /usr/cyrus/bin/lmtpd listed as an lmtp listener (server) in my
/etc/cyrus.conf.
The problem, I believe, is that procmail cannot act as an lmtp client.
Therefore, when procmail is introduced in the picture, there is no way for
procmail to deliver mail to lmtpd.
Either way, I could not get
What's concerning me actually does appear to be a difference in the
command-line interface. With the deliver binary from my 1.5.2 build, I can
do:
$ deliver -a malallen -m user.malallen.test < some.msg
and the mail will be delivered directly to the user.malallen.test mailbox.
I can't get this
On 13-Feb-01 at 02:45, Werner Reisberger ([EMAIL PROTECTED]) wrote:
> Quoting Mobeen Azhar <[EMAIL PROTECTED]>:
>
> > I have not been able to use deliver since I upgraded from 1.5 to 2.x.
> > and
> > had to revert to using sieve.
>
> It's written in the upgrade notice, that deliver is only a wra
This might be obvious to everyone, but I thought I'd post it anyway.
I wanted to allow encrypted imap connections from everywhere, but
unencrypted sessions only from my internal network. TCP Wrappers seemed
an obvious solution, but since the current Cyrus code sets the daemon name
to check to th
grab'd latest CVS and all is well again ... thanks :)
On Tue, 13 Feb 2001, Lawrence Greenfield wrote:
> This is a result of the file descriptor problem we were having; I
> posted a patch several days ago. Let me know if you can't find it.
>
> Larry
>
>Date: Tue, 13 Feb 2001 00:23:31 -0500
On Tue, Feb 13, 2001 at 10:06:12AM -0500, Ken Murchison wrote:
> > It's written in the upgrade notice, that deliver is only a wrapper to
> > the lmtp server and that a lmtp client is required.
>
> This is NOT true. Deliver's sole purpose in life in 2.x is so that you
> do NOT need an LMTP client
Ok, here's my situation (and it's simple). I already
have the latest berkeley DB installed. What I'm looking
to obtain is the configure for both SASL and IMAPD to not
use /etc/passwd (have all users stored in /etc/sasldb).
I'm on redhat 6.2 and use pam and md5. What is the configure
options f
Marcel Landman wrote:
>
> Cyrus imapd works great, but I have a couple outstanding issues where
> users are getting unexpected behavior. The problems are not reproducible
> but happen occasionally. I suspect the client (Outlook) or the user.
>
> Now if I look in the log files, I can see people
> On Tue, 13 Feb 2001 15:01:14 -0500 (EST),
> Bitt Faulk <[EMAIL PROTECTED]> (bf) writes:
bf> This might be obvious to everyone, but I thought I'd post it anyway.
bf> I wanted to allow encrypted imap connections from everywhere, but
bf> unencrypted sessions only from my internal network.
On 13-Feb-01 at 14:49, Werner Reisberger ([EMAIL PROTECTED]) wrote:
> On Tue, Feb 13, 2001 at 10:06:12AM -0500, Ken Murchison wrote:
> > > It's written in the upgrade notice, that deliver is only a wrapper to
> > > the lmtp server and that a lmtp client is required.
> >
> > This is NOT true. Del
[EMAIL PROTECTED] wrote:
>
> On 13-Feb-01 at 14:49, Werner Reisberger ([EMAIL PROTECTED]) wrote:
> > On Tue, Feb 13, 2001 at 10:06:12AM -0500, Ken Murchison wrote:
> > > > It's written in the upgrade notice, that deliver is only a wrapper to
> > > > the lmtp server and that a lmtp client is req
Ok, I REALLY need this server up and running but I can't
get the authentication right! And I've tried almost
everything I can possibly do here. I'm looking to
use /etc/sasldb for logins but I NEED to know the
configure options for imapd-2.0.11 and sasl-1.5.24
to do this. PAM is what I'm using on
18 matches
Mail list logo
