At 13:32 -0400 Rob Siemborski wrote:
>Also, Squirrelmail does support TLS connections (but not IMAPs), from a
>brief read of their source (atleast in the 1.4 series).
True, but it requires PHP 4.3 which isn't in a supported Red Hat Linux
release (you can find it in rawhide though :).
Another option is to use stunnel (stunnel.org) on both side of the
connection.
Thanks
Rich Houston
> 11 Èþíü 2003 19:16, Mark London íàïèñàë:
>> I would like to restrict Cyrus to only allow users to use IMAPS, not
>> plain
>> IMAP. However, I was told that would break Squirrelmail, unless I
>>
On 11 Jun 2003, Mark London writes:
> I would like to restrict Cyrus to only allow users to use IMAPS, not
> plain IMAP. However, I was told that would break Squirrelmail,
> unless I opened access to IMAP (port 143) for the node that
> Squirrelmail was running on.
Iptables would probably be the
On Wed, 11 Jun 2003, Mark London wrote:
> I would like to restrict Cyrus to only allow users to use IMAPS, not plain
> IMAP. However, I was told that would break Squirrelmail, unless I opened
> access to IMAP (port 143) for the node that Squirrelmail was running on.
> But I'm running XINETD on R
Rob Siemborski wrote:
On Wed, 11 Jun 2003, Mark London wrote:
I would like to restrict Cyrus to only allow users to use IMAPS, not plain
IMAP. However, I was told that would break Squirrelmail, unless I opened
access to IMAP (port 143) for the node that Squirrelmail was running on.
But I'm run
11 Июнь 2003 19:16, Mark London написал:
> I would like to restrict Cyrus to only allow users to use IMAPS, not plain
> IMAP. However, I was told that would break Squirrelmail, unless I opened
> access to IMAP (port 143) for the node that Squirrelmail was running on.
> But I'm running XINETD on Re
Mark,
Why not use iptables to block all port 143 access except the node that
Squirrelmail is running on?
Mark London wrote:
I would like to restrict Cyrus to only allow users to use IMAPS, not plain
IMAP. However, I was told that would break Squirrelmail, unless I opened
access to IMAP (port
On Wed, 11 Jun 2003, Bob Jones wrote:
> Hello all. I've been tasked with looking at changing our mail
> services and one of the options is Cyrus. One question that will
> greatly impact the decision is this:
>
> How many copies of a message are saved in the message store? I know
> Cyrus has a d
On Wed, 11 Jun 2003, Mark London wrote:
> I would like to restrict Cyrus to only allow users to use IMAPS, not plain
> IMAP. However, I was told that would break Squirrelmail, unless I opened
> access to IMAP (port 143) for the node that Squirrelmail was running on.
> But I'm running XINETD on Re
Hello all. I've been tasked with looking at changing our mail
services and one of the options is Cyrus. One question that will
greatly impact the decision is this:
How many copies of a message are saved in the message store? I know
Cyrus has a db backend, so we're wondering if one message is
I would like to restrict Cyrus to only allow users to use IMAPS, not plain
IMAP. However, I was told that would break Squirrelmail, unless I opened
access to IMAP (port 143) for the node that Squirrelmail was running on.
But I'm running XINETD on Redhat, and I've read Cyrus doesn't use that.
I wou
On Wed, 11 Jun 2003, Matt Bernstein wrote:
> I was wondering how much space Cyrus' hard-linking tricks saved us.. as an
> academic department (with about 800 users) a lot of e-mail goes out to
> student lists, for example. So.. while waiting for an fsck after a major
> power cut I wrote this natty
Brasseur Valéry wrote:
did someone know if there exist a IMAp server who would be able to use a
POP3 server for the INBOX folder and his normal folders for all others !
note : i need something like this for a migration purpose !
The basic problem is that you cannot implement the IMAP protocol u
did someone know if there exist a IMAp server who would be able to use a
POP3 server for the INBOX folder and his normal folders for all others !
note : i need something like this for a migration purpose !
thanks
On Wed, 11 Jun 2003, Ted Fines wrote:
> Unless the imap connection has a mailbox open. That ties up a potentially
> very large memory resource (depending on the size of the mailbox) on the
> server.
>
> I have to say I don't know for certain whether that's true for the cyrus
> imapd, but for othe
Bernd Nies wrote:
What do these Cyrus LMTPD log messages mean?
It means you're logging DEBUG messages that you don't need to see. Both
of these messages have to do with duplicate supression.
--
Kenneth Murchison Oceana Matrix Ltd.
Software Engineer 21 Princeton Place
716-662-8973 x26
I'm not sure how the httpd processes are being tied up, but "tied up"
imapds that are otherwise idle don't cost you anything except some swap
and a process table entry. They're basicly free.
Unless the imap connection has a mailbox open. That ties up a potentially
very large memory resource (dep
Hi,
On Wed, 11 Jun 2003, Christian Schlaefcke wrote:
> Hi all,
>
> checking for krb.h... no
> configure: warning: No Kerberos V4 found
> installed without errors. I tried with several options (--disable-krb,
> --without-krb, --includedir=path_to_krb4_headers) with no luck.
>
> What can I do?
>
I was wondering how much space Cyrus' hard-linking tricks saved us.. as an
academic department (with about 800 users) a lot of e-mail goes out to
student lists, for example. So.. while waiting for an fsck after a major
power cut I wrote this natty little perl script:
#!/usr/bin/perl -w
use strict
Hi all,
when I run ./configure it stops with the following error:
checking for krb.h... no
configure: warning: No Kerberos V4 found
configure: error: Kerberos not found for authorization module
I searched google I couldn´t find any help. I have berkeley-db and sasl
installed without errors. I tr
What do these Cyrus LMTPD log messages mean?
Thanks in advance.
--
+-+
Bernd Nies mailto:[EMAIL PROTECTED]
System Engineering Dipl. El.-Ing. HTL
AdNovum Informatik
Simon Brady schrieb:
>
> Hello world,
>
> We're planning to retire our Solaris mail server at the end of the year
> and move Cyrus to Linux. I'd intended to move to RH7.3, which we use
> widely and understand quite well, but Red Hat's support policies have
> killed that idea.
>
> Is anyone curre
22 matches
Mail list logo
