Hello
Dudi,
Thanks
for your help.
The
following syntax is working for me:
su -
cyrus -c "/usr/lib/cyrus/bin/squatter -r -v user/*"
Can
you tell me please if this process (squatter -r) is time consuming, cause
I've read on the net, that people decided not to use of th
On 9/20/05, Scott <[EMAIL PROTECTED]> wrote:
> Right now I have a Sun box that has been running Cyrus for about 4
> years. The box has 8 Sparc v9 @ 400MHz and 6GB of memory. About 2
> years ago we put all of the mail queue, DB, seen and sub files onto a
> 2GB solid state drive. This setup has be
Etienne Goyer wrote:
Scott wrote:
Right now I have a Sun box that has been running Cyrus for about 4
years. The box has 8 Sparc v9 @ 400MHz and 6GB of memory. About 2
years ago we put all of the mail queue, DB, seen and sub files onto a
2GB solid state drive. This setup has been running f
Scott wrote:
Right now I have a Sun box that has been running Cyrus for about 4
years. The box has 8 Sparc v9 @ 400MHz and 6GB of memory. About 2
years ago we put all of the mail queue, DB, seen and sub files onto a
2GB solid state drive. This setup has been running fine, supporting
about 2
Hey everyone. I am in need of some help in moving off a Sun system to a
Linux system for Cyrus. My knowledge of the hardware is pretty limited,
so I'm hoping you folks can help me avoid a major blunder.
Right now I have a Sun box that has been running Cyrus for about 4
years. The box has 8
On Tue, 20 Sep 2005, John Madden wrote:
I don't completely agree here, there are ways to do snapshots without any
downtime for example in a SAN environment or using filesystem or LVM based
snapshot methods. However, it does not mean your snapshots are really
consistent from the aplications poin
Hello Cyrus people,
posting this here because no one had a solution at the Kolab mailing list.
I am trying to use ipurge with Kolab. I am not successful when giving an
"mboxpattern" though:
su kolab-r -c "/kolab/bin/ipurge -b 0 -f user/test"
There's no output and nothing is deleted! I wonder
> I don't completely agree here, there are ways to do snapshots without any
> downtime for example in a SAN environment or using filesystem or LVM based
> snapshot methods. However, it does not mean your snapshots are really
> consistent from the aplications point of view.
And that's the big quest
On Monday 19 September 2005 05:18 pm, Wil Cooley wrote:
[...]
> Sorry, I think I took your subject line too literally; are you using the
> 'cyrus' service from master.cf or LMTP for mailbox delivery, or are you
> using maildrop, local or other direct-delivery service service?
> The '/b/' directory
Hi,
This is what people say on kolab list on TSQUAT failed' issue
http://www.kolab.org/pipermail/kolab-devel/2005-August/004233.html:
QUOTE:
"It simply means that the foler is not indexed, and the logging is turned on at
debug level, I have long sicne changed the logging to be at info level it i
On Tue, 2005-09-20 at 12:33 +0300, [EMAIL PROTECTED] wrote:
> Hello All,
>
> I keep getting these kind of messages in my logs, when using horde IMP
> with Cyrus-IMAP server.
>
> Sep 20 12:06:24 mail imap[19540]: SQUAT failed to open index file
> Sep 20 12:06:24 mail imap[19540]: SQUAT failed
>
Hi,
I'm on
SLES 9, Horde IMP is on another machine, managed by another
person.
I'm
running web-cyradm + Cyrus-IMAP.
When
using regular Imap Clients like Kmail, OE etc. there is no 'SQUAT failed' error, so I think it's somthing connected to
the IMP.
Any
Ideas welcomed.
Hi,
I would suggest to use the solution from web-cyradm list:
http://www.web-cyradm.org/pipermail/web-cyradm/2004-November/017965.html
There is very nice and multipurpose script to deal with quotas.
It's abaut integration of quota management for MTA (postfix) + Cyrus.
Regards,
Leon Kolchinsky
Hi,
I would like to implement the quota checking within my MTA which is exim
and not use cyrus quota
what would be the less consuming way to do it ?
- check the quota.db and extract the current mailboxe size for a
particular user ?
- connect with tcp on imap and read the current quota valu
Hello
All,
I keep getting these
kind of messages in my logs, when using horde IMP with Cyrus-IMAP
server.
Sep 20 12:06:24 mail imap[19540]: SQUAT failed to
open index fileSep 20 12:06:24 mail imap[19540]: SQUAT failed
Could anyone
tell me how to deal with it?
Please also
tell me ho
Hello All,
Thanks for all responses.
After reading your posts on the issue and reading some more stuff, I'll make a
summary below:
1) I'll make a dump of all mailboxes to the text file:
su - cyrus -c "ctl_mboxlist -d" > /var/lib/imap/mailboxlist.txt
And I can restore it with:
su - cyrus -c "c
> On Mon, 2005-09-19 at 17:48 +0300, [EMAIL PROTECTED] wrote:
>
>> Thank you Vittorio for your script, but you are stopping the cyrus and
>> I think it's very problematic in production environment.
>
> I think the point is that, short of using some of the replication stuff
> from pre-2.3 in CVS, th
17 matches
Mail list logo
