I am using Cyrus-IMAP 2.0.16 with Sieve enabled, and managing it with
websieve. For this mailing list, I set up the following rule using
websieve (as displayed by the "current rules" page):
IF 'To' contains 'info-cyrus' OR field: 'CC' contains 'info-cyrus' THEN
File Into 'INBOX.Cyrus-IMAP'
T
On Fri, 22 Feb 2002, Christopher Wong wrote:
> I am using Cyrus-IMAP 2.0.16 with Sieve enabled, and managing it with
> websieve. For this mailing list, I set up the following rule using
> websieve (as displayed by the "current rules" page):
>
> IF 'To'
6 Dec 2001, Matt Kenigson wrote:
> Yeah, we've got an exactly identical entry in our /etc/cyrus.conf file. I'm
> stumped.
>
> Matt
>
> - Original Message -
> From: "Christopher Wong" <[EMAIL PROTECTED]>
> To: "Matt Kenigson" <[
why.
Chris
On Wed, 26 Dec 2001, Matt Kenigson wrote:
> It looks as if we do have the sieve port listed in /etc/services. We had so
> hoped that was all it was -- thank you for the advice. Any other ideas?
>
> Matt Kenigson
> [EMAIL PROTECTED]
>
> - Original Message -
Is Sieve running? RH 7.2 does not have the sieve port defined in
/etc/services by default, so unless you edit that file, Sieve will not
work. I'm using the cyrus-imapd-2.0.16-2rm RPM from
http://rmrpms.tripod.com/cyrus-imapd.
Chris
On Fri, 21 Dec 2001, Matt Kenigson wrote:
> Incidentally, this
On Tue, 18 Dec 2001, Pascal Longrais wrote:
> I am using cyrus imap v2.0.9 on a linux server.
>
> I can without any problem move mails from Inbox to drafts or sent or
> templates subfolders.
>
> but when I want to send a mail, netscape reports "permission denied"
> when it tries to store a copy
Does anyone find it tricky setting up Pine to work with Cyrus-IMAP? I just
set up pine-4.33 with cyrus-imapd-2.0.16. The folder/collections behavior
is confusing. The inbox path was easy enough: I set it to
"{imaphost/user=myuserid}inbox". At this point, Pine would show the inbox,
but none of the
On Monday 19 November 2001 01:54 pm, Ken Murchison wrote:
> Cyrus users,
>
> We are getting close to releasing Cyrus v2.1 (yeah, I know I've said
> this a bunch of times already) and we are leaning towards making it
> dependent on SASL v2. We would like to do this for a number of
> reasons:
>
> 1
On Wednesday 19 September 2001 06:26, Oyku Gencay wrote:
> Hi,
>
> I've successfully installed and set up Cyrus to authenticate from PAM
> by 1. changing group of imapd to shadow
> 2. changing group for /etc/shadow to shadow (it's root by default)
> and chmod g+r
>
> Whenever I change a password f
On Wednesday 12 September 2001 13:06, Lawrence Greenfield wrote:
> (lots of questions)
Looks like I am not expressing myself well. My main concern here is:
"Why should I bother running pwcheck?"
Chris
On Tuesday 11 September 2001 21:19, Jeremy Howard wrote:
> Having said that, the argument that pwcheck is "practically useless"
> still doesn't make sense. Access to the pwcheck socket can be
> restricted to the Cyrus user, and as a unix socket it is only
> accessible if you have local access to t
On Monday 10 September 2001 18:26, Christopher Audley wrote:
> saslauthd is an evolution of pwcheck available with the 1.5.27 and
> 2.0.x versions of the sasl library (available from CVS). Saslauthd
> basically takes the core of pwcheck and adds forking so that each
> request is handled by a diff
On Monday 10 September 2001 14:17, Lawrence Greenfield wrote:
> Nothing stops you from running pwcheck/saslauthd as a non-root user
> with shadow privileges.
That's good to know. I wouldn't have known from the documentation,
which only tells me to run it as root.
I still don't see what using p
On Monday 10 September 2001 12:56, Amos Gouaux wrote:
>
> True, but the cyrus user is potentially more exposed to the outside
> environment than pwcheck/saslauthd. These daemons are after all
> listening on a UNIX domain socket, not an INET socket.
Having internal access is bad enough (IMAP acce
On Monday 10 September 2001 11:54, Amos Gouaux wrote:
>
> Seems to me the more permissions that are granted to user cyrus, the
> more you loose any benefit of the Cyrus software running as non-root.
The "shadow" method gives "shadow" privileges to a Cyrus daemon. The
pwcheck method requires root
On Monday 10 September 2001 10:51, Amos Gouaux wrote:
> > On Mon, 10 Sep 2001 16:31:49 +0200 (CEST),
> > Tarjei Huse <[EMAIL PROTECTED]> (th) writes:
>
> th> - cyrus-imapd-2.0.16 doesn't set process ids correctly;
> th> it only sets uid, not gid, neither supplementary gids
> th> - detect
On Wednesday 05 September 2001 09:27, Joe Ellis wrote:
> Hi all,
>
> Haim Dimermanas and myself finished setting up the ultimate email
> solution using postfix and cyrus. The big change from the previous
> version
> is that users can now use their email address as their username. That
> makes
> a
On Tuesday 28 August 2001 12:40, nrvale0 wrote:
> The problem:
>
> I have some users who would like to be able to check their mail
> through a web-based IMAP interface sometimes but use
> mutt/pine/elm/etc. in non-IMAP mode at other times.
>
> The solution(?):
WU-IMAP.
You can't do that with Cyr
On Wednesday 15 August 2001 16:29, Martin Justra wrote:
> Hello,
> I tried to install cyrus. I finally finished it with an rpm
> (compiling I get a message that db.h is not there --> Solution ?).
> Now I cannot authenticate for the imapd.
> The Server doesn't show any AUTH=. either. Why ? Who
Could someone explain what Cyrus-IMAP does with /var/imap/db? I
upgraded to the latest Cyrus-IMAP 2.0.16 RPMs (for Red Hat) and
everything seems to work fine. I have been testing this IMAP server
setup with the intention of deploying it in the indeterminate
future. The largest test account has les
20 matches
Mail list logo
