cyradm has wildcard support:
host> cm user/first.last/Trash
host> cm user/first.last/Sent
host> cm user/first.last/Read
192.168.2.11> listacl user/f*
user/first.last:
first.last.todelete lrswipkxtecdan
user/first.last/Read:
first.last.todelete lrswipkxtecdan
user/first.last/Sent:
first.last.to
I'm trying to fix the mailboxes with something like this:
imap_setacl ($mbox, "user/".$argv[1]."/*",
$wrongname."todelete", "");
imap_setacl ($mbox, "user/".$argv[1]."/*", $argv[1],
"lrswipkxtea");
But it seems imap_setacl can't use wildcards. And I can't write one by
one by
On 01/22/2018 07:55 PM, Heiler Bemerguy via Info-cyrus wrote:
The way I interpret it is that the / means unixhierarchysep is on.
Just tested this on 2.4.18 and the same thing happens. When you
rename back no messages are listed and reconstruct does nothing.
Ah. As suspected the rights are w
The way I interpret it is that the / means unixhierarchysep is on.
Just tested this on 2.4.18 and the same thing happens. When you
rename back no messages are listed and reconstruct does nothing.
Ah. As suspected the rights are wrong. You just need to set the rights
back to the real user. Y
Em 22/01/2018 19:47, Dan White
escreveu:
On
01/22/18 19:02 -0300, Heiler Bemerguy via Info-cyrus wrote:
Em 22/01/2018 18:46, Dan White escreveu:
On 01/22/18 17:44 -0300, Heiler Bemerguy
via Info-cyrus wrote:
imap
On 01/22/2018 07:01 PM, Patrick Boutilier wrote:
On 01/22/2018 06:02 PM, Heiler Bemerguy via Info-cyrus wrote:
Em 22/01/2018 18:46, Dan White escreveu:
On 01/22/18 17:44 -0300, Heiler Bemerguy via Info-cyrus wrote:
imap_renamemailbox($mbox, "$mailbox", "$mailbox"."TODELETE")
Was this perform
On 01/22/2018 06:02 PM, Heiler Bemerguy via Info-cyrus wrote:
Em 22/01/2018 18:46, Dan White escreveu:
On 01/22/18 17:44 -0300, Heiler Bemerguy via Info-cyrus wrote:
imap_renamemailbox($mbox, "$mailbox", "$mailbox"."TODELETE")
Was this performed as an admin?
Yes. In a huge list of imap acco
On 01/22/18 19:02 -0300, Heiler Bemerguy via Info-cyrus wrote:
Em 22/01/2018 18:46, Dan White escreveu:
On 01/22/18 17:44 -0300, Heiler Bemerguy via Info-cyrus wrote:
imap_renamemailbox($mbox, "$mailbox", "$mailbox"."TODELETE")
Was this performed as an admin?
Yes. In a huge list of imap ac
Em 22/01/2018 18:46, Dan White escreveu:
On
01/22/18 17:44 -0300, Heiler Bemerguy via Info-cyrus wrote:
imap_renamemailbox($mbox, "$mailbox",
"$mailbox"."TODELETE")
Was this performed as an admin?
Yes. In a
On 01/22/18 17:44 -0300, Heiler Bemerguy via Info-cyrus wrote:
imap_renamemailbox($mbox, "$mailbox", "$mailbox"."TODELETE")
Was this performed as an admin?
Some mailboxes were erroneusly renamed to "loginTODELETE" and I need
to put them back to the original name.
I reverted this command, li
Simon Matter wrote:
>> Simon Matter wrote:
>>
Dear list,
this is my first ever mail to the cyrus group. Hope to get some help.
I am using cyrus-imapd-2.2.12-27.6 in Suse 10.1 I have configured cyrus
to work with LDAP authentication where
the admin user "cyrus
Simon Matter wrote:
>> Simon Matter wrote:
>>
Dear list,
this is my first ever mail to the cyrus group. Hope to get some help.
I am using cyrus-imapd-2.2.12-27.6 in Suse 10.1 I have configured cyrus
to work with LDAP authentication where
the admin user "cyrus
> Simon Matter wrote:
>>> Dear list,
>>>
>>> this is my first ever mail to the cyrus group. Hope to get some help.
>>>
>>> I am using cyrus-imapd-2.2.12-27.6 in Suse 10.1 I have configured cyrus
>>> to work with LDAP authentication where
>>> the admin user "cyrus" is based on simple pam authenticat
Simon Matter wrote:
>> Dear list,
>>
>> this is my first ever mail to the cyrus group. Hope to get some help.
>>
>> I am using cyrus-imapd-2.2.12-27.6 in Suse 10.1 I have configured cyrus
>> to work with LDAP authentication where
>> the admin user "cyrus" is based on simple pam authentication. So I
> Dear list,
>
> this is my first ever mail to the cyrus group. Hope to get some help.
>
> I am using cyrus-imapd-2.2.12-27.6 in Suse 10.1 I have configured cyrus
> to work with LDAP authentication where
> the admin user "cyrus" is based on simple pam authentication. So I have
> both PAM_Unix and P
On Fri, 8 Jul 2005, Bartosz Jozwiak wrote:
On 7/7/05, Bartosz Jozwiak <[EMAIL PROTECTED]> wrote:
I am running web-cyradm with Cyrus SASL 2.1.17 and Cyrus impad 2.1.16
I have an issue with case sensitive usernames.
To solve that problem, is there only one way to upgrade cyrus sasl and
On Fri, 8 Jul 2005, Bartosz Jozwiak wrote:
On 7/7/05, Bartosz Jozwiak <[EMAIL PROTECTED]> wrote:
I am running web-cyradm with Cyrus SASL 2.1.17 and Cyrus impad 2.1.16
I have an issue with case sensitive usernames.
To solve that problem, is there only one way to upgrade cyrus sasl and
cyru
On 7/7/05, Bartosz Jozwiak <[EMAIL PROTECTED]> wrote:
I am running web-cyradm with Cyrus SASL 2.1.17 and Cyrus impad 2.1.16
I have an issue with case sensitive usernames.
To solve that problem, is there only one way to upgrade cyrus sasl and
cyrus
impad ?
You may wish to consider the fol
Hi Philip
Thanks for the mail. One of my raid arrays was indeed
having a problem but was used for nothing more than
mp3 storage. I totaly discounted the idea that it
might be responcable for Cyrus's problems but it
was. If I bring the server up without that array
mounted Cyrus works like it
Thanks Simon. I did upgrade to 2.2.8 later in the day. I think our
problems may have had a basis in the 2.2.5 version we were running, but
I also think the power outage and filesystem errors also played a big
role. For those who would like to know, most of the IOERRORs I was
getting were tra
> We recently had a power failure during a storm and the server required
> an fsck before it would mount up the file systems (eventhough I did have
> logging/journaling turned on). After running 2 fscks it seems clean,
> but there are issue with the cyrus files themselves. I had a problem
> with
> Here are the bonnie results...
Hm, this is bonnie 1.x, which is okay, but it has 2Gb filesize limit. Your
big box has 2Gb of Ram, right? How big was your file size with bonnie? To
make this test work, boot both boxes with mem=128M as kernel parameter so
it will only use 128M of the memory. Then,
Here are the bonnie results...
This is the "beefy" machine
---Sequential Output ---Sequential Input--
--Random--
-Per Char- --Block--- -Rewrite-- -Per Char- --Block---
--Seeks---
MachineMB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec
%CPU
> Today, we upgraded the machine to the latest redhat ES 3.0
> with kernel Linux 2.4.21-15.ELsmp -- no luck... imtest -z still took 19
> seconds to run... compared to 2-3 seconds on the cheapie machine.
Hm, you said SCSI Raid - that can mean alot.
Could you run a good old bonnie on both boxes and
Today, we upgraded the machine to the latest redhat ES 3.0
with kernel Linux 2.4.21-15.ELsmp -- no luck... imtest -z still took 19
seconds to run... compared to 2-3 seconds on the cheapie machine.
I generated the traces requested, but I'm not really sure what I'm looking
for... Mostly because I d
> On Sat, 2004-07-31 at 23:33, [EMAIL PROTECTED] wrote:
>
>> Does this information help? What other info can I provide?
>
> Yep. Can you please run 'vmstat 1' while the test is running, and
> redirect the output to a file? vmstat can help spot all sorts of issues.
>
> Also, what filesystem and dis
> I'm really stumped here.
>
> I have two seperate machines... one very high end, dual CPU machine, raid
> 5, etc, the other is a piece of crud (standard low end workstation).
>
> Both machines are running Redhat Enterprise Server 3...
> the SMP machine is running the redhat 2.4.21-4.ELsmp stock ke
On Sat, 2004-07-31 at 23:33, [EMAIL PROTECTED] wrote:
> Does this information help? What other info can I provide?
Yep. Can you please run 'vmstat 1' while the test is running, and
redirect the output to a file? vmstat can help spot all sorts of issues.
Also, what filesystem and disks are you u
On Sat, 2004-07-31 at 02:20, [EMAIL PROTECTED] wrote:
> I'm really stumped here.
>
> I have two seperate machines... one very high end, dual CPU machine, raid
> 5, etc, the other is a piece of crud (standard low end workstation).
>
> Both machines are running Redhat Enterprise Server 3...
> the S
> More recent kernel versions have improved memory management and I
> wouldn't have expected RH ES 3.0 to be affected. What does top tell
> you? Does the load get high? How much CPU time do the kernel tasks use
> up?
> --
Top shows zero load on the machine (its just sitting there running cyrus
Hi,
-- [EMAIL PROTECTED] is rumored to have mumbled on Samstag, 31. Juli
2004 3:20 Uhr -0400 regarding Please help with Simon's Cyrus RPMS (2.2.8),
SMP, and really slow performance:
I have two seperate machines... one very high end, dual CPU machine, raid
5, etc, the other is a piece of crud (s
Java Rockx wrote:
I see that.
I'm using perl-Mail-IMAPClient-2.1.4-1
Latest version on CPAN is 2.2.9
You could install that and see if it helps?
Paul.
---
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/m
Hi again,
You have several, possibly related, error messages here.
As far as I can see, Cyrus is returning an error in response to an
Append operation that the imapsync tool is attempting.
You're also getting errors from the Perl interpreter itself -
It sounds like either imapsync, or perhaps the
I see that.
I'm using perl-Mail-IMAPClient-2.1.4-1
--- Paul Gargan <[EMAIL PROTECTED]> wrote:
> Hi again,
>
> You have several, possibly related, error messages here.
>
> As far as I can see, Cyrus is returning an error in response to an
> Append operation that the imapsync tool is attempting.
Paul,
Thank You!! When I did the imapsync I did not include the --syncinternaldate
option.
Anyhow, when I include that option I get the following messages returned from
imapsync and messages are not actually transferred.
Any clues?
Paul
+ Copying msg #1332:2501 to folder INBOX.INBOX
flags from
Java Rockx wrote:
It does not work when using Outlook or Outlook
Express. When using either of these mail clients, the
"recieved date" never seems to match the message
headers, but rather shows when the actual mail message
was migrated.
Hi,
We had a similar problem (same sync tool, same issue) at o
I don't think you want or need to include the version or architecture in
your path. And I think you want a space after the I. So try:
x) exec perl -MCyrus::IMAP::Shell -I /usr/lib/perl5/site_perl -e shell -- ${1+"$@"} ;;
And frankly, that path is already probably in your include path (try perl
On Fri, 28 May 2004, Kent L. Nasveschuk wrote:
> This is what I added but I get the same db_version error :(
> I have yet to get this to run, very frustrating. It obviously works
> people use it. I'm so close on this...
>
>
> case "x$BASH_VERSION" in
> x) exec perl -MCyrus::IMAP::Shell
> -I/usr/
On Fri, 28 May 2004, Kent L. Nasveschuk wrote:
> This is what I added but I get the same db_version error :( I have yet
> to get this to run, very frustrating. It obviously works people use it.
> I'm so close on this...
Yes, when you said "path problem", I assumed that it was the same as
mine.
This is what I added but I get the same db_version error :(
I have yet to get this to run, very frustrating. It obviously works
people use it. I'm so close on this...
case "x$BASH_VERSION" in
x) exec perl -MCyrus::IMAP::Shell
-I/usr/lib/perl5/site_perl/5.8.0/i486-linux -e shell -- ${1+"$@"} ;;
*)
On Fri, 28 May 2004, Kent Nasveschuk wrote:
> Hello,
> You had a perl path problem back in April in cyradm (Cyrus IMAP) that it
> seems many people had. I was just wondering if you solved it and exactly
> what you did to solve it. I have Cyrus 2.2.4 installed and working on a
> test machine with e
Hello,
You had a perl path problem back in April in cyradm (Cyrus IMAP) that it
seems many people had. I was just wondering if you solved it and exactly
what you did to solve it. I have Cyrus 2.2.4 installed and working on a
test machine with exception of cyradm. Any help would be appreciated,
Hello,
I have the same problem on AIX 5.2. Configure for cyrus-sasl-2.1.18 and
cyrus-imapd-2.2.3
cannot find Berkeley DB 4.2. I used switch --with-bdb-libdir but this not helps.
I do not have a lot of experience in compiling. So any comments or suggestions will be
highly appreciated.
Thank you
Jim,
Sorry, the version I am trying to install is 2.1.18 not 2.0.18.
Thanks
Original Message
Subject: Re: Please help
From:"Jim Levie" <[EMAIL PROTECTED]>
Date:Wed, May 12, 2004 10:28 pm
To: [EMAIL PROTECTED]
C
On Wed, 2004-05-12 at 00:54, Fatemeh Taj wrote:
> Dear All,
> I want move to cyrus imapd 2.2.3 with sasl2.0.18 and Berkeley DB4.2.1 on
> Linux Redhat Enterprise 3.
Why are you trying to use an old version of SASL instead of the one
(2.1.15-3) furnished with RHEL 3.0? Cyrus IMAP 2.2.3 is quite happ
> On Tue, 20 Apr 2004, Joe Rhett wrote:
> > But if you will accept a patch that modifies the makemaker stuff, I'll hack
> > one out over the next week or so, just so that we can stop getting the same
> > FAQ from everyone ;-)
On Tue, Apr 20, 2004 at 03:37:02PM -0400, Rob Siemborski wrote:
> Yes.
On Tue, 20 Apr 2004, Joe Rhett wrote:
> > On Tue, 20 Apr 2004, Joe Rhett wrote:
> > > But if you will accept a patch that modifies the makemaker stuff, I'll hack
> > > one out over the next week or so, just so that we can stop getting the same
> > > FAQ from everyone ;-)
>
> On Tue, Apr 20, 2004 a
On Tue, 20 Apr 2004, Joe Rhett wrote:
> No, mostly because I'm not that good with makemaker. When I wrote the
> original I was hoping to inspire someone to Do The Right Thing. But after
> looking at the layout, I'm not sure what you gain -- you'll have to add the
> Makemaker stuff to the autocon
There's nothing like coming back to your own words a while later to make
you realize what a wining b-otch you sounded like when you said: (more below)
> On Thu, 15 Apr 2004, Joe Rhett wrote:
> > This has been an ongoing bug that is indecently easy to fix, but Rob won't
> > accept any patches on it
On Thu, 15 Apr 2004, Joe Rhett wrote:
> This has been an ongoing bug that is indecently easy to fix, but Rob won't
> accept any patches on it. He evidently thinks that installing modules into
> the sitewide perl installation is the right idea. I believe that it's
> plain wrong, and want to use t
cyradm and really any script you run that fails because of the error you
listed. And yes, the lines that execute perl.
On Fri, Apr 16, 2004 at 09:29:03AM +0100, Neil Marjoram X 663711 wrote:
> Joe,
>
> Thanks for this, can you tell me which files I need to change. I assume
> that you mean cyradm
Joe,
Thanks for this, can you tell me which files I need to change. I assume
that you mean cyradm and to change the lines that execute the perl
command.
Thanks,
Neil.
On Thu, 2004-04-15 at 15:55, Joe Rhett wrote:
> Neil, open the files in question and modify the four real lines of the
> script
Neil, open the files in question and modify the four real lines of the
script so that you have -I/install/location/lib to where the perl modules are.
This has been an ongoing bug that is indecently easy to fix, but Rob won't
accept any patches on it. He evidently thinks that installing modules in
Some further information :
Cyrus was configured with :
./configure --with-openssl=/usr/local/ssl --with-libwrap=/usr/local
--with-sasl=/usr/local
I had to move the sasl header files into the imap source tree under
sasl/ otherwise it complained they were not present.
The configure complained a
Thanks for that, I have now recompiled SASL and imap in the default
location, it seems the PREFIX is set in the Perl makefile for imap, and
thus it loads in the Cyrus tree instead of the Perl tree. My recompile
used default locations and now all is installed where I think it should
be. How ever it
On Thursday 15 April 2004 12:37, Neil Marjoram X 663711 wrote:
> I have found the Cyrus Perl module located in the directory I installed
> cyrus in : /opt/cyrus/lib/perl5/site_perl/5.8.0/sun4-solaris/. How do I
> get it installed in the Perl tree?
Did you install cyrus imap from a precompiled pack
Ilya Basin wrote:
On Wednesday 19 November 2003 20:03, Ken Murchison wrote:
I'd like to disable plaintext auth at all.
Keep in mind that there is a difference between allowing plaintext
authentication and allowing plaintext authentication mechanisms. You
can enable plaintext authentication mec
On Wednesday 19 November 2003 20:03, Ken Murchison wrote:
I'd like to disable plaintext auth at all.
I've changed the conf as you suggested to auxprop and t start to work FINE.
THANK YOU som much. I shame of myself.
> Ilya Basin wrote:
> > Hi,
> > I've spent a week trying to configure cyrus-
Ilya Basin wrote:
Hi,
I've spent a week trying to configure cyrus-imapd-2.1.15
to work with MS Outlook 2000 over TLS/SSL.
I see no way to fix it... maybe I've missed something?
System:
Slackware 9.1
openssl-09.7c
cyrus-imapd-cyrus-sasl-2.1.15
cyrus-imapd-2.1.15
compiled with no errors.
Mozilla
On Wednesday 19 November 2003 19:14, Ilya Basin wrote:
I have some additional info.
Sorry to provide you with so big bunch of info...
ALL imtest passed with OK, like:
[EMAIL PROTECTED]:~$ imtest -u ilya -p 993 -s localhost -m digest-md5
verify error:num=18:self signed certificate
TLS connection e
On Mon, 18 Nov 2002 19:53:17 +0100
Carsten Hoeger <[EMAIL PROTECTED]> wrote:
> > I apply the patch and 'make clean' && re-compile db3, SASL and imapd
> > but it doesnt work for me:
> >
> Sure that you installed the recompiled sasl libraries?
Sure :) I found the error. There where an old installa
On Mon, Nov 18, Marc Sebastian Pelzer wrote:
> > You need the attached patch for the bdb3.
>
> I apply the patch and 'make clean' && re-compile db3, SASL and imapd but
> it doesnt work for me:
>
> Nov 18 17:08:55 prime master: setrlimit: Unable to set file descriptors
> limit to 2147483647: Oper
On Mon, 18 Nov 2002 14:20:51 +0100
Carsten Hoeger <[EMAIL PROTECTED]> wrote:
Hi,
thanks to Carsten for the quick answer.
> > i successfully compiled cyrus-imapd 2.1.9 with SASL 2.1.9 and
> > Berkeley DB 3.1.17 on a Sun Sparc 10 with SuSE 7.3 and 128MB RAM and
> > get the following errors in /var
On Mon, Nov 18, Marc Sebastian Pelzer wrote:
> i successfully compiled cyrus-imapd 2.1.9 with SASL 2.1.9 and Berkeley
> DB 3.1.17 on a Sun Sparc 10 with SuSE 7.3 and 128MB RAM and get the
> following errors in /var/log/messages after starting the
> '/usr/cyrus/bin/master' process and try to test i
This is what I did to fix the problem. Nick your idea of using reconstruct
on the user gave me a brainstorm and it worked. The first thing I
did was to run reconstruct -f and from there I wrote down the directory
structure of the user. ie. user.joe.sent, user.joe.draft, user.joe.trash.
Whereev
Reklama.
You can either:
1)
cd /usr/cyrus/bin
su cyrus
./reconstruct user.
2)
go to cyradm,
sam user. c
dm user.
Nick
> I am using Redhat 7.1 running cyrus 2.0.9 with Postfix. I dame a
> mistake and deleted a user's directory and can't get it off a backup.
> When I go into cyradm
Quoting "P.Agenbag" <[EMAIL PROTECTED]>:
> Please, it is urgent, I need documentation for cyrus to tell me how to
> maintain user mailboxes, ie. deleting mailboxes, rebuilding deleting
> individual boxes etc.
Most mailbox maintenance is done via 'cyradm'. Rebuilding corrupted mailboxes
is don
Fatemeh Taj wrote:
>
> Hi everybody,
>
> I have problem with compiling "agentx-v1.4.1" on RedHat 6.2. It generates a lot
> of errors. Does anyone know what I should do to port it to RedHat (as it
> mentioned that it was compiled only in Solaris 2.5 and it really did, I checked
> it on Solaris)?
68 matches
Mail list logo
