On 11/1/10 7:26 PM, Bron Gondwana wrote:
> On Sun, Oct 31, 2010 at 10:40:13PM -0400, Chris Pepper wrote:
>> Bron,
>>
>> My Cyrus is from RPM, and I am just nursing it along until my users
>> finish migrating off and FastMail manages to complete my own
>> migration, so I don't want to build fro
On Sun, Oct 31, 2010 at 10:40:13PM -0400, Chris Pepper wrote:
> Bron,
>
> My Cyrus is from RPM, and I am just nursing it along until my users
> finish migrating off and FastMail manages to complete my own
> migration, so I don't want to build from source. Why would IMAP/S
> block on empty /d
On 01/11/10 11:27 -0400, Chris Pepper wrote:
>On 11/1/10 10:41 AM, Dan White wrote:
>>On 31/10/10 20:51 -0400, Chris Pepper wrote:
>>>Alternatively, is there a way to make sure Cyrus requires STARTTLS on
>>>143? I was blocking external access to it to make sure users always use
>>>encryption to con
On 11/1/10 11:21 AM, Simon Matter wrote:
>> On 11/1/10 10:46 AM, Simon Matter wrote:
Bron,
My Cyrus is from RPM, and I am just nursing it along until my users
finish migrating off and FastMail manages to complete my own migration,
so I don't want to build from source. Wh
On 11/1/10 10:41 AM, Dan White wrote:
> On 31/10/10 20:51 -0400, Chris Pepper wrote:
>> Alternatively, is there a way to make sure Cyrus requires STARTTLS on
>> 143? I was blocking external access to it to make sure users always use
>> encryption to connect, but port 143 with STARTTLS required woul
> On 11/1/10 10:46 AM, Simon Matter wrote:
>>> Bron,
>>>
>>> My Cyrus is from RPM, and I am just nursing it along until my users
>>> finish migrating off and FastMail manages to complete my own migration,
>>> so I don't want to build from source. Why would IMAP/S block on empty
>>> /dev/random,
On Monday, November 01, 2010 03:46:38 pm Simon Matter wrote:
> > Bron,
> >
> > My Cyrus is from RPM, and I am just nursing it along until my users
> >
> > finish migrating off and FastMail manages to complete my own migration,
> > so I don't want to build from source. Why would IMAP/S block o
On 11/1/10 10:46 AM, Simon Matter wrote:
>> Bron,
>>
>> My Cyrus is from RPM, and I am just nursing it along until my users
>> finish migrating off and FastMail manages to complete my own migration,
>> so I don't want to build from source. Why would IMAP/S block on empty
>> /dev/random, while
> Bron,
>
> My Cyrus is from RPM, and I am just nursing it along until my users
> finish migrating off and FastMail manages to complete my own migration,
> so I don't want to build from source. Why would IMAP/S block on empty
> /dev/random, while IMAP+STARTTLS works? FWIW, SASL2 seems to use
On 31/10/10 20:51 -0400, Chris Pepper wrote:
> Alternatively, is there a way to make sure Cyrus requires STARTTLS on
>143? I was blocking external access to it to make sure users always use
>encryption to connect, but port 143 with STARTTLS required would be an
>acceptable alternative.
You c
On Sun, 31 Oct 2010, Chris Pepper wrote:
> But my /dev/random does seem quite low. Still surfing and looking for a
> good way to fill it on a mostly headless server -- I haven't found a
> good solution yet.
http://www.entropykey.co.uk/
Very good hardware, first-class Linux support, and wi
Bron,
My Cyrus is from RPM, and I am just nursing it along until my users
finish migrating off and FastMail manages to complete my own migration,
so I don't want to build from source. Why would IMAP/S block on empty
/dev/random, while IMAP+STARTTLS works? FWIW, SASL2 seems to use urando
12 matches
Mail list logo