Hi,
I've been using cyrus imapd for years using saslauthd against unix
passwd/shadow.
This way it's easy to understand the relation between a user and its mailbox.
Now I want to integrate authentication with a sql backend, forgetting about
unix users.
I have a postgres db containing users and pas
On Tue, Jan 25, 2011 at 03:51:51PM +, David Mayo wrote:
> Simon,
>
> On 25/01/11 15:40, Simon Matter wrote:
>
> >> When I try to move a top level mailbox to be a sub mailbox, or vice
> >> versa, the IMAP server returns:
> >>
> >> "NO Operation is not supported on mailbox"
> >>
> >> eg.
> >>
>
Thanks for the explanation. Though, I would prefer something better
than MD5 since it has been broken for years.
As for my "hack", it doesn't work because I mis-read what %p was,
thinking it was the password, not the column to look for... so back to
the drawing board. I will look at using someth
On 25/01/11 12:48 -0500, Raymond T. Sundland wrote:
>So given that it's been at least 6 years since it's been common
>security practice to not store cleartext passwords in a database, why
>does SASL still require it? Can't SASL be modified to accept
>some token from the SQL query t
Maybe this isn't the correct list for this question as it has to do
more with SASL, but I am setting up a new mail server on a new box.
This is my 4th iteration of "starting fresh" using Cyrus Imap with
some sort of 3rd party database backend, using both LDAP and MySQL
Simon,
On 25/01/11 15:40, Simon Matter wrote:
>> When I try to move a top level mailbox to be a sub mailbox, or vice
>> versa, the IMAP server returns:
>>
>> "NO Operation is not supported on mailbox"
>>
>> eg.
>>
>> renm user.toplevel user.aa.toplevel
>> renm user.aa.toplevel user.toplevel
>>
>>
>
> When I try to move a top level mailbox to be a sub mailbox, or vice
> versa, the IMAP server returns:
>
> "NO Operation is not supported on mailbox"
>
> eg.
>
> renm user.toplevel user.aa.toplevel
> renm user.aa.toplevel user.toplevel
>
> Why is this? Can I get around it other than creating a n
When I try to move a top level mailbox to be a sub mailbox, or vice
versa, the IMAP server returns:
"NO Operation is not supported on mailbox"
eg.
renm user.toplevel user.aa.toplevel
renm user.aa.toplevel user.toplevel
Why is this? Can I get around it other than creating a new mailbox and
co
