On Tue, June 19, 2012 3:55 pm, Dan White wrote:
> On 06/19/12 11:17 +0200, Eric Luyten wrote:
>
>> Folks,
>>
>>
>>
>> (hitting the same wall over and over again when upgrading)
>>
>>
>>
>> Cyrus SASL is working/looking in /var/state/saslauthd all
>> right, but Cyrus 2.4 appears to be writing elsewh
On 06/19/12 11:17 +0200, Eric Luyten wrote:
>Folks,
>
>
>(hitting the same wall over and over again when upgrading)
>
>
>Cyrus SASL is working/looking in /var/state/saslauthd all
>right, but Cyrus 2.4 appears to be writing elsewhere, and
>we cannot find out where exactly.
>
>Have tried 'saslauthd_p
On Tue, June 19, 2012 12:05 pm, Adam Tauno Williams wrote:
> On Tue, 2012-06-19 at 11:17 +0200, Eric Luyten wrote:
>
>> (hitting the same wall over and over again when upgrading)
>> Cyrus SASL is working/looking in /var/state/saslauthd all
>> right, but Cyrus 2.4 appears to be writing elsewhere, a
On Tue, 2012-06-19 at 11:17 +0200, Eric Luyten wrote:
> (hitting the same wall over and over again when upgrading)
> Cyrus SASL is working/looking in /var/state/saslauthd all
> right, but Cyrus 2.4 appears to be writing elsewhere, and
> we cannot find out where exactly.
Are you sure it is loading
Folks,
(hitting the same wall over and over again when upgrading)
Cyrus SASL is working/looking in /var/state/saslauthd all
right, but Cyrus 2.4 appears to be writing elsewhere, and
we cannot find out where exactly.
Have tried 'saslauthd_path' option in /etc/imapd.conf to
no avail.
I pretty mu
