The following issue has been RESOLVED. 
====================================================================== 
http://www.dbmail.org/mantis/view.php?id=391 
====================================================================== 
Reported By:                windowsrefund
Assigned To:                aaron
====================================================================== 
Project:                    DBMail
Issue ID:                   391
Category:                   Command-Line programs (dbmail-users, dbmail-util)
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     resolved
target:                      
Resolution:                 fixed
Fixed in Version:           SVN Trunk
====================================================================== 
Date Submitted:             07-Aug-06 20:25 CEST
Last Modified:              14-Aug-06 19:43 CEST
====================================================================== 
Summary:                    dbmail-smtpd can not create new sub folders
Description: 
2188 appears to be the last build that is capable of creating subfolders
like so

dbmail-smtpd -u foo -m "INBOX/foo"

Later builds fail with a "Permissions denied" error. 




====================================================================== 

---------------------------------------------------------------------- 
 aaron - 09-Aug-06 18:54  
---------------------------------------------------------------------- 
Previously no hierarchical permissions checking was done when creating a
new mailbox. Now we check to make sure that we have permission to create a
folder below the parent folder. Your configuration sets all folders to
read-only -- so they are no longer permitted to have sub-folders created
within them...

On the one hand, a read-only folder is read-only -- 2.1.7 closes a bug
where one could create a new folder below a read-only folder... on the
other hand, it breaks your very useful read-only archive system.

Let's think about a permissions-oriented workaround. 

---------------------------------------------------------------------- 
 windowsrefund - 09-Aug-06 22:43  
---------------------------------------------------------------------- 
I noticed the no_inferiors column in the dbmail_mailboxes table and can't
help but wonder if that attribute would make for a better check.

Best,
Adam 

---------------------------------------------------------------------- 
 aaron - 12-Aug-06 16:55  
---------------------------------------------------------------------- 
We do check for no_inferiors, after checking for general writability. I'm
thinking that the semantics of "read only" should apply only to the
message contents of a mailbox, and not to the subfolders. The question is
how the read-only/read-write flag interacts with no_inferiors and
no_select.

I think it's time to write up a wiki page to map out the semantics:
http://www.dbmail.org/dokuwiki/doku.php?id=folder_perms 

---------------------------------------------------------------------- 
 aaron - 14-Aug-06 19:43  
---------------------------------------------------------------------- 
Added a new -M option to dbmail-smtp to bypass permission checks and Sieve
scripts. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-Aug-06 20:25 windowsrefund  New Issue                                    
09-Aug-06 18:54 aaron          Note Added: 0001335                          
09-Aug-06 22:43 windowsrefund  Note Added: 0001336                          
12-Aug-06 16:55 aaron          Note Added: 0001339                          
14-Aug-06 19:43 aaron          Status                   new => resolved     
14-Aug-06 19:43 aaron          Fixed in Version          => SVN Trunk       
14-Aug-06 19:43 aaron          Resolution               open => fixed       
14-Aug-06 19:43 aaron          Assigned To               => aaron           
14-Aug-06 19:43 aaron          Note Added: 0001341                          
======================================================================

Reply via email to