On 2017-08-21 08:57, Egoitz Aurrekoetxea wrote:
> Have you copied from another machine or similar the quota database??
>
>
> You should never do that
No. The mailstore was transferred with imapsync many months ago.
The test enviroment behaves identical, ie. the MUA'a and bin/quota with
and
Have you copied from another machine or similar the quota database??
You should never do that
Best regards,
El 21/8/17 a las 8:42, Per olof Ljungmark escribió:
On 2017-08-21 08:11, Egoitz Aurrekoetxea wrote:
Good morning,
What happens if you launch the cyradm from a remote machine?.
On 2017-08-21 08:11, Egoitz Aurrekoetxea wrote:
Good morning,
What happens if you launch the cyradm from a remote machine?. For
instance in a FreeBSD with another Perl version?. Does it work?.
No, tried that and results are the same. Current line of thought is that
something is not right wi
Good morning,
What happens if you launch the cyradm from a remote machine?. For
instance in a FreeBSD with another Perl version?. Does it work?.
Best regards,
El 19/8/17 a las 13:18, Per olof Ljungmark escribió:
Hi all,
Wonder if someone can offer help.
Host is FreeBSD 11.0-STABLE #0 r3
Hi all,
Wonder if someone can offer help.
Host is FreeBSD 11.0-STABLE #0 r316644M and cyrus 2.5.11 in a jail.
If I run cyradm as user cyrus (admin) and issue the lq command, usually
there is a proper response at first, but subsequent commands fail. This
could very well be a FreeBSD problem but I
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
Sounds like your /dev/random is empty. You can compile with /dev/urandom or add
a source of entropy...
"Chris Pepper" wrote:
> mail.reppep.com (CentOS 5) is running cyrus-imapd-2.3.7-7.el5_4.3,
>along with SquirrelMail, postfix, etc. Last night, I noticed that when I
>sent mail from Thu
mail.reppep.com (CentOS 5) is running cyrus-imapd-2.3.7-7.el5_4.3,
along with SquirrelMail, postfix, etc. Last night, I noticed that when I
sent mail from Thunderbird, it was not able to file copies in the Sent
mailbox, although they did reach the recipients, so postfix was
accepting ma
I have what's probably a very silly problem with a new Cyrus installation.
I am in the process of setting up a new server to take over the duties of
an older machine doing same. I have perl scripts which allow me to
create/delete and move mailboxes, and I am having problems getting these to
w
Date: Mon, 04 Nov 2002 14:31:41 -0800
From: Paul Ramsey <[EMAIL PROTECTED]>
[...]
Yes, I am running 1.6.24. To head off any "just upgrade" comments, I
would like to note that all the rename() and cyrus.seen code in the
2.1.x tree seems to be identical to the code in the 1.6.24 tree
On a similar note, we are running the same kernel with XFS and I get
similar problems -- no solution here, but a cry for info as well.
We are running imap v.2.1.5 and sasl 2.1.7, redhat kernel 2.4.19
The problem is with the seen as well, randomly entire folders will
suddenly be marked unread, o
I recently moved my imap archive to a new machine, but with an identical
version of cyrus imapd (1.6.24). The old machine was a linux 2.2.19
kernel and the new one is a 2.4.19 kernel. On both machines, the archive
is on an ext2 filesystem.
The new system is finding it impossible to maintain th
23 matches
Mail list logo
