On 12-08-20 03:29 PM, Dan White wrote:
> On 08/19/12 19:39 -0400, brian wrote:
>> I'm having some trouble configuring SASL for a new server. Specifically,
>> it seems, with realms. I'm now at the point where imtest works with the
>> virtual domains but not with the default domain.
>>
>> I'm using s
On 08/19/12 19:39 -0400, brian wrote:
>I'm having some trouble configuring SASL for a new server. Specifically,
>it seems, with realms. I'm now at the point where imtest works with the
>virtual domains but not with the default domain.
>
>I'm using sasldb through auxprop. In the past I've always don
On 12-08-20 09:43 AM, Andrew Morgan wrote:
>
> Does it work if you use:
>
> imtest -v -m plain -a user -r DEFAULT.TLD localhost
No, it does not. Same result, same msg in logs. I had tried that as well as:
imtest -v -m plain -a user -r poseidon.DEFAULT.TLD localhost
imtest -v -m plain -a user -r m
On Sun, 19 Aug 2012, brian wrote:
> I'm having some trouble configuring SASL for a new server. Specifically,
> it seems, with realms. I'm now at the point where imtest works with the
> virtual domains but not with the default domain.
>
> I'm using sasldb through auxprop. In the past I've always do
I'm having some trouble configuring SASL for a new server. Specifically,
it seems, with realms. I'm now at the point where imtest works with the
virtual domains but not with the default domain.
I'm using sasldb through auxprop. In the past I've always done:
saslpasswd2 -c usern...@domain.tld
B
