Hello list members,
we have delete_mode and expunge_mode set to delayed on our cyrus
2.3.11 backend. When cyr_expire tries to remove deleted mailboxes, it
fails with the following error:
cyr_expire[24222]: can not connect to mupdate server for delete of
Patrick Boutilier wrote:
and I am getting this error:
Mar 31 01:33:41 collab cyrus/imaps[12733]: unable to get certificate
from '/usr/lib/ssl/imap.pem'
Mar 31 01:33:41 collab cyrus/imaps[12733]: TLS server engine: cannot
load cert/key data, may be a cert/key mismatch?
Mar 31 01:33:41 collab
Ernst Jeschek wrote, on 31.03.2008 10:24:
Hello list members,
we have delete_mode and expunge_mode set to delayed on our cyrus
2.3.11 backend. When cyr_expire tries to remove deleted mailboxes, it
fails with the following error:
cyr_expire[24222]: can not connect to mupdate server for
On Mon, Mar 31, 2008 at 12:13:38PM +0200, Wolfgang Breyha wrote:
https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=3034
http://www.invoca.ch/pub/packages/cyrus-imapd/cyrus-imapd-2.3.11-3.src.rpm
and newer versions include the proposed fix.
Thank you! I tried the patch, now it works.
kind
On Mar 29, 2008 12:24 AM, Andrew Morgan [EMAIL PROTECTED] wrote:
On Fri, 28 Mar 2008, Bart Coninckx wrote:
Add /* and /*/* to the reconstruction path and it works. Gabor's
patch might also work for you. (I haven't tested yet)
Tom Bryntesen wrote:
Hi,
What's the conclusion on this problem?
On Mon, Mar 31, 2008 at 5:12 AM, Gary Mills [EMAIL PROTECTED] wrote:
On Sun, Mar 30, 2008 at 02:27:29PM +0100, Alain Spineux wrote:
On Mon, Mar 17, 2008 at 5:39 PM, Gary Mills [EMAIL PROTECTED] wrote:
Once again, we had somebody use the sieve facility to redirect e-mail
back to the
On Mon, Mar 31, 2008 at 10:30 AM, Bernhard D Rohrer [EMAIL PROTECTED] wrote:
Patrick Boutilier wrote:
and I am getting this error:
Mar 31 01:33:41 collab cyrus/imaps[12733]: unable to get certificate
from '/usr/lib/ssl/imap.pem'
Mar 31 01:33:41 collab cyrus/imaps[12733]: TLS server
Jo Rhett [EMAIL PROTECTED] wrote:
I would ask that you spend some time determining how the
program could determine it is a bad rule, and provide a patch to fix this
behavior. (in short -- it's harder than you think)
A mail delivery system that loses mail is buggy. I don't need to look
at
On Mon, Mar 31, 2008 at 02:04:29PM +0200, Alain Spineux wrote:
On Mon, Mar 31, 2008 at 5:12 AM, Gary Mills [EMAIL PROTECTED] wrote:
On Sun, Mar 30, 2008 at 02:27:29PM +0100, Alain Spineux wrote:
On Mon, Mar 17, 2008 at 5:39 PM, Gary Mills [EMAIL PROTECTED] wrote:
Once again, we had
On Mon, Mar 31, 2008 at 2:40 PM, Joseph Brennan [EMAIL PROTECTED] wrote:
Jo Rhett [EMAIL PROTECTED] wrote:
I would ask that you spend some time determining how the
program could determine it is a bad rule, and provide a patch to fix this
behavior. (in short -- it's harder than you
Gary Mills wrote:
Once again, we had somebody use the sieve facility to redirect e-mail
back to the same mailbox and then go on vacation. This sets up a
forwarding loop which cyrus breaks by discarding the e-mail. During
this vacation, all of the person's e-mail disappeared.
Shouldn't we
You can either remove the CRAM-MD5 SASL plugin, or restrict the list of
advertised mechanisms by using the 'sasl_mech_list' option in imapd.conf
Joshua Tew wrote:
I have not been able to authenticate POP3 over SSL from thunderbird
2.0.0.12 to Cyrus POm.3.8 on a OS X Server 10.5.
I have
It was added at some point in the 2.3 tree and is used for the IMAP
URLAUTH extension which isn't widely supported by clients yet.
Shelley Waltz wrote:
I searched, but could not find the relevant infomation regarding
the mboxkey_db database in 2.3.7
My current 2.2.3 install simply has
I'm all for trying fix this if someone can come up with some logic to do
so. IMO, the code is correctly processing the script as written. Here
is the current code logic:
- original message is sent to lmtpd
- message is forwarded and a record is put in deliver.db stating as much
-
Hello !
We are planning an upgrade to Cyrus 2.3.7
Currently, we have some servers, running different versions of Cyrus mail :
- mupdate running Cyrus v2.1.18
- 2 frontends running Cyrus v2.1.18, others frontends running v2.2.12
- All our backends are running Cyrus v 2.2.12
Our goal is to
Joseph Brennan wrote:
I'm all for trying fix this if someone can come up with some logic to do
so. IMO, the code is correctly processing the script as written. Here
is the current code logic:
- original message is sent to lmtpd
- message is forwarded and a record is put in deliver.db
On Fri, 28 Mar 2008, Jo Rhett wrote:
On Mar 28, 2008, at 4:24 PM, Andrew Morgan wrote:
These are the exact steps I follow when I recover email for a user from our
tape backups:
13. Run su cyrus -c '/usr/local/cyrus/bin/reconstruct -x -f
user.username'.
14. Run su cyrus -c
On Mon, 31 Mar 2008, Steeve Gagnon wrote:
Hello !
We are planning an upgrade to Cyrus 2.3.7
Currently, we have some servers, running different versions of Cyrus mail :
- mupdate running Cyrus v2.1.18
- 2 frontends running Cyrus v2.1.18, others frontends running v2.2.12
- All our backends
On 31 Mar 2008, at 11:52, Ken Murchison wrote:
How can
lmtpd be intelligent enough to know that the forwarded address will
cause the message to come back?
There's no way to do that, but one could insert a header, e.g, X-
Sieve-Redirect. Maybe the value would be a random string which was
On Mon, 31 Mar 2008, Bart Coninckx wrote:
Can 't help put thinking that this is a load of work. Hopefully the
developpers will write some tools to simplify the restore procedure.
If you run with expunge_mode:delayed, it's as simple as using the
unexpunge command. :)
After you restore the
On Mon, Mar 31, 2008 at 04:21:20PM +0200, Alain Spineux wrote:
On Mon, Mar 31, 2008 at 2:40 PM, Joseph Brennan [EMAIL PROTECTED] wrote:
Jo Rhett [EMAIL PROTECTED] wrote:
I would ask that you spend some time determining how the
program could determine it is a bad rule, and provide
On Tue, 1 Apr 2008, Bron Gondwana wrote:
On Mon, Mar 31, 2008 at 04:21:20PM +0200, Alain Spineux wrote:
On Mon, Mar 31, 2008 at 2:40 PM, Joseph Brennan [EMAIL PROTECTED] wrote:
Jo Rhett [EMAIL PROTECTED] wrote:
I would ask that you spend some time determining how the
program could
On Mon, 31 Mar 2008 15:51:17 -0700 (PDT), Andrew Morgan [EMAIL PROTECTED]
said:
On Tue, 1 Apr 2008, Bron Gondwana wrote:
On Mon, Mar 31, 2008 at 04:21:20PM +0200, Alain Spineux wrote:
On Mon, Mar 31, 2008 at 2:40 PM, Joseph Brennan [EMAIL PROTECTED] wrote:
Jo Rhett [EMAIL PROTECTED]
On Mar 31, 2008, at 5:40 AM, Joseph Brennan wrote:
A mail delivery system that loses mail is buggy. I don't need to look
at the code to know that.
And knives that cut people are bad. No matter how they are used.
*whatever*
plonk.
--
Jo Rhett
Net Consonance : consonant endings by net
*sigh* No, not in a virtual domain environment they don't. Try
adding
13a. Run su cyrus -c '/usr/local/cyrus/bin/reconstruct -x -f
user.username/*'.
13b. Run su cyrus -c '/usr/local/cyrus/bin/reconstruct -x -f
user.username/*/*'.
13c. Run su cyrus -c
On Mon, Mar 31, 2008 at 11:52:10AM -0400, Ken Murchison wrote:
Gary Mills wrote:
Once again, we had somebody use the sieve facility to redirect e-mail
back to the same mailbox and then go on vacation. This sets up a
forwarding loop which cyrus breaks by discarding the e-mail. During
this
Thanks Ken
restricting the list using
sasl_mech_list
worked.
Joshua
On Mar 31, 2008, at 11:56 PM, Ken Murchison wrote:
You can either remove the CRAM-MD5 SASL plugin, or restrict the list
of advertised mechanisms by using the 'sasl_mech_list' option in
imapd.conf
Joshua Tew
27 matches
Mail list logo
