I have a solaris 2.6 box with cyrus-imapd 1.5.19.
Someone removed all the files of an imap folder. The folder
has subfolders that are still there and available.
I restored the backup but now the messages can't be
retrieved. Netscape communicator tells me there are
some messages there but when I
Have you checked to make sure the file permissions were restored correctly?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Francesc
Guasch Ortiz
Sent: Monday, November 19, 2001 08:39
To: [EMAIL PROTECTED]
Subject: Restoring backup
I have a solaris 2.6
Gareth Blades escribió:
Thank you very much for answering Gareht.
Have you checked to make sure the file permissions were restored correctly?
Yes, that was the very first I did after restoring.
It was okay. I tested delivering to the mailbox and
it worked. But I can't read any message. Even
Francesc Guasch Ortiz wrote:
Have you checked to make sure the file permissions were restored correctly?
Yes, that was the very first I did after restoring.
It was okay. I tested delivering to the mailbox and
it worked. But I can't read any message. Even the
ones delivered after the
If it is an ACL problem, ACL's are stored in the mailboxes file.Take a look at the
lines for the user's mailboxes, they should look somehing like this:
user.jdoe 1 jdoe lrswipcda
user.jdoe.Trash 1 jdoelrswipcda
The first entry is the mailbox name, the second
Esh, Thomas D (Tom) schrieb am Mon, Nov 19, 2001 at 10:26:22AM -0500:
*
* We are evaluating the possibility of using cyrus for a
* commercial product.
*
* Therefore, I'm looking licensing issues with Cyrus and the Berkeley DB
* product must be licensed if the source code of the product
* using
Cyrus users,
We are getting close to releasing Cyrus v2.1 (yeah, I know I've said
this a bunch of times already) and we are leaning towards making it
dependent on SASL v2. We would like to do this for a number of reasons:
1. Take advantage of the benefits of SASL v2 (improvements in memory
Ken Murchison [EMAIL PROTECTED] writes:
The biggest (only?) downside for existing installations is that any
secrets stored in sasldb would have to migrated to the new format. This
will require resetting all of the users passwords because they can not
be extracted from the old sasldb (unless
Hi,
On Mon, 19 Nov 2001 13:54:11 -0500
Ken Murchison [EMAIL PROTECTED] said:
ken We are getting close to releasing Cyrus v2.1 (yeah, I know I've said
ken this a bunch of times already) and we are leaning towards making it
ken dependent on SASL v2. We would like to do this for a number of
i'm looking to gather more information about implementing the
cyrus-graphtools for my site, management likes to see pretty graphs. i'm
running ucd-snmp-4.2 which i compiled from source distributed with
redhat 7.1, i configued with the
--with-mib-modules=agentx after reading a post to the list.
Ken Murchison wrote:
The biggest (only?) downside for existing installations is that any
secrets stored in sasldb would have to migrated to the new format. This
will require resetting all of the users passwords because they can not
be extracted from the old sasldb (unless you have been
Ken Murchison wrote:
The biggest (only?) downside for existing installations is that any
secrets stored in sasldb would have to migrated to the new format. This
will require resetting all of the users passwords because they can not
be extracted from the old sasldb (unless you have been
Hajimu UMEMOTO wrote:
Hi,
On Mon, 19 Nov 2001 13:54:11 -0500
Ken Murchison [EMAIL PROTECTED] said:
ken We are getting close to releasing Cyrus v2.1 (yeah, I know I've said
ken this a bunch of times already) and we are leaning towards making it
ken dependent on SASL v2. We would
Ken Murchison wrote:
Cyrus users,
We are getting close to releasing Cyrus v2.1 (yeah, I know I've said
this a bunch of times already) and we are leaning towards making it
dependent on SASL v2. We would like to do this for a number of reasons:
1. Take advantage of the benefits of SASL
Ken,
I have no problem resetting SASL Admin passwords however, does this
change to SASL V2 effect PAM authentication (kerberos, LDAP, etc.)?
Regards,
Robert Beazley
OCNS, Inc.
[EMAIL PROTECTED]
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Ken
OCNS Consulting wrote:
Ken,
I have no problem resetting SASL Admin passwords however, does this
change to SASL V2 effect PAM authentication (kerberos, LDAP, etc.)?
All of the plaintext verification mechanisms (PAM, password, shadow,
krb, sasldb, etc) have been moved out of the library
--On Monday, November 19, 2001 01:54:11 PM -0500 Ken Murchison
[EMAIL PROTECTED] wrote:
Cyrus users,
We are getting close to releasing Cyrus v2.1 (yeah, I know I've said
this a bunch of times already) and we are leaning towards making it
dependent on SASL v2. We would like to do this for
On Monday 19 November 2001 01:54 pm, Ken Murchison wrote:
Cyrus users,
We are getting close to releasing Cyrus v2.1 (yeah, I know I've said
this a bunch of times already) and we are leaning towards making it
dependent on SASL v2. We would like to do this for a number of
reasons:
1. Take
Pat Lashley wrote:
--On Monday, November 19, 2001 01:54:11 PM -0500 Ken Murchison
[EMAIL PROTECTED] wrote:
Cyrus users,
We are getting close to releasing Cyrus v2.1 (yeah, I know I've said
this a bunch of times already) and we are leaning towards making it
dependent on SASL v2.
Sorry I was out of the loop for this thread, I'm a little behind on my
mail. I'm currently testing a new version of imapmigrate -- I'll add
this patch and it will be included in the next release. Thanks, Scot!
Scot W. Hetzel wrote:
From: Darrell [EMAIL PROTECTED]
We're testing the
Christopher Wong wrote:
On Monday 19 November 2001 01:54 pm, Ken Murchison wrote:
Cyrus users,
We are getting close to releasing Cyrus v2.1 (yeah, I know I've said
this a bunch of times already) and we are leaning towards making it
dependent on SASL v2. We would like to do this
On Mon, 19 Nov 2001, Ken Murchison wrote:
The biggest (only?) downside for existing installations is that any
secrets stored in sasldb would have to migrated to the new format. This
will require resetting all of the users passwords because they can not
be extracted from the old sasldb
On Mon, 19 Nov 2001, Christopher Wong wrote:
1. Take advantage of the benefits of SASL v2 (improvements in memory
management, support for additional plugin types, simplified database
support, and improved error reporting).
[snip]
You have sketched out benefits largely from a developer's
--On Monday, November 19, 2001 03:49:59 PM -0500 Ken Murchison
[EMAIL PROTECTED] wrote:
The biggest (only?) downside for existing installations is that any
secrets stored in sasldb would have to migrated to the new format.
This will require resetting all of the users passwords because
I would be all for making cyrus-imapd SASLv2 dependant.
Best Regards,
-Jev
On Mon, Nov 19, 2001 at 01:54:11PM -0500, Ken Murchison wrote:
Cyrus users,
Can you use snmpwalk to see your statistics? Something like
snmpwalk mail3.andrew.cmu.edu public cmu
you should see a large number of entries under enterprises.cmuMIB.
If you can't see that, step #1 is to understand what's happening.
You might want to crack up the logging on snmpd and see
From: Esh, Thomas D (Tom) [EMAIL PROTECTED]
Date: Mon, 19 Nov 2001 10:26:22 -0500
We are evaluating the possibility of using cyrus for a
commercial product.
Therefore, I'm looking licensing issues with Cyrus and the Berkeley DB
product must be licensed if the source code of
On Mon, 19 Nov 2001, Lawrence Greenfield wrote:
snmpwalk mail3.andrew.cmu.edu public cmu
you should see a large number of entries under enterprises.cmuMIB.
Where can one get the CMU and cmuCyrus MIB files? I had to nuke away the
cmuMIB and cmuCyrus mib symbols, converting them to their OIDs to
Pat Lashley wrote:
--On Monday, November 19, 2001 03:49:59 PM -0500 Ken Murchison
[EMAIL PROTECTED] wrote:
The biggest (only?) downside for existing installations is that any
secrets stored in sasldb would have to migrated to the new format.
This will require resetting all of the
Date: Mon, 19 Nov 2001 22:20:49 -0200
From: Henrique de Moraes Holschuh [EMAIL PROTECTED]
On Mon, 19 Nov 2001, Lawrence Greenfield wrote:
snmpwalk mail3.andrew.cmu.edu public cmu
you should see a large number of entries under enterprises.cmuMIB.
Where can one get the CMU and
--On Monday, November 19, 2001 07:40:16 PM -0500 Ken Murchison
[EMAIL PROTECTED] wrote:
Right. Which means that they will be duplicated and must be kept
in sync for as long as you have apps using both versions. Changing
your password in either database won't automatically change it in
the
Hi,
I am having a couple of problems with SASL authentication. First of all,
the authentication mechanisms CRAM-MD5 DIGECT-MD5 done't appear as being
supported, even though I have used the the sample programs that come
with SASL those appear to work.
Also, I have set the pwcheck_method to
On Mon, 19 Nov 2001, Ken Murchison wrote:
The v1 sasl library supported an auto-transition for plaintext
logins where the login was authenticated against some external
mechanism (e.g., /etc/passwd) and then used to create the entries
in the sasldb. A similar auto-transition, even
Rob Siemborski wrote:
As far as setpass() specifically, each plugin is still allowed to maintain
its own database of secrets if necessary. There is no requirement that
any mechanism plugin use sasldb for authentication (e.g. KERBEROS_V4).
For the record, saslpasswd makes all appropriate
The previous patch that I submitted made sure that the envelope
recipient address of the message that triggers a vacation response had
the same domain name as the one used by the MTA. Today's patch
ensures that this same address will be used as the originator of the
response message. Taking it
Hi All,
I have a mail server setup with Cyrus Imap 2.0.16
and Postfix snapshot-20010808 with LDAP and I use a php based webmail system.
Everything works fine, but occasionally I experience 2 serious
problem.
1:
Webmail login for certain accounts get blocked.
Once this happened I can use
Hello all,
All the talk about the sasldb migration reminds me
of Nalin Dahyabhai's pam sasldb patch
(http://people.redhat.com/nalin/test/pam_sasldb-20011022.tgz).
Has anyone tried that yet? My thought is this.
Perhaps people who need to migrate could use that
(probably with a little
Additionally, how hard is it to write a pwcheck
method in SASL 2? I had a couple I did in SASL
1.5, but they required patches to the source. Can
you just drop in a plugin, do you have to write a
pwcheck/saslauthd daemon, or is there a simpler
method I'm just overlooking?
You can plug in a
38 matches
Mail list logo
