XCEEDED:
>//MY: return "452 4.2.2 Over quota";
>return "552 4.2.2 Over quota";
>
>and it's work for me
>
>Scott Pederick wrote:
>>
>> G'Day,
>>
>> cyrus-imapd-2.0.9
>> postfix-19991231-pl10
>>
>> Jus
G'Day,
cyrus-imapd-2.0.9
postfix-19991231-pl10
Just wondering if anyone has modified Cyrus to return a Permanent Failure
rather than a Temporary Failure when a user has exceeded their quota? On a
temporary failure postfix just leaves it in the queue and I would prefer a
bounce.
I intend to make
Ken,
It works beautifully - truly poetry in motion (or maybe I'm slightly
over-reacting out of relief ;) ).
Thanks again!
Scott
>Sorry this took so long, but I've been out of town the last two days.
>Here is a patch against cyrus-imapd-2.0.9. Consider it beta.
>
>1. Apply this patch in the im
-Original Message-
From: Ken Murchison <[EMAIL PROTECTED]>
To: Scott Pederick <[EMAIL PROTECTED]>
Cc: Cyrus Mailing List <[EMAIL PROTECTED]>
Date: Thursday, 25 January 2001 1:10
Subject: Re: Renaming users
>
>
>Scott Pederick wrote:
>>
>> G'
lbox". It doesn't
seem to be a permissions issue so I'm thinking I'll have to do something
more low-level (ie. move files, rebuild db's, etc).
If anyone has any advice or can point me in the right direction, it would be
greatly appreciated. Thanks in advance.
Regards,
Scott Pederick
Hello all,
I'm having problems using PAM authentication with Cyrus imap.
I'm running : Cyrus Imap 2.0.7, Cyrus SASL 1.5.24, Berkeley DB 3.1.17
What appears to be happening is that Imap isn't paying attention to
/etc/pam.d/imap and always uses sasldb. The username/password specified in
/etc/sasl
