[Tickets #6775] Creating a /new/ spam folder results in a setting without the correct namespace prefix

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/6775
-----------------------------------------------------------------------
 Ticket             | 6775
 Created By         | janne.peltonen at helsinki.fi
 Summary            | Creating a /new/ spam folder results in a setting
without the correct
                    | namespace prefix
 Queue              | Ingo
 Version            | 1.2
 Type               | Bug
 State              | Unconfirmed
 Priority           | 2. Medium
 Milestone          |
 Patch              |
 Owners             |
+New Attachment     | ingo_new_spam_folder_creation_append_namespace.patch
-----------------------------------------------------------------------


janne.peltonen at helsinki.fi (2008-05-29 05:37) wrote:

OK, what really appeared to be wrong was that when creating a new folder
for spam, then the spam->folder setting (and the created script) ends up
without the namespace prefix. What happened was that the new folder was
created using Ingo::createFolder()'s result, which doesn't contain the
namespace part in any case. This also explains why, when I created a new
folder and the script got activated OK and the newly created folder ended
up in the drop down menu of spam.php, it wasn't selected in the menu:
spam.php realoads the folder from the server and gets, for instance,
INBOX.newspamfolder, but the default value of the menu ends up as
newspamfolder...

I fixed the problem locally by adding a line that calls
IMP::appendNamespace($result) into spam.php... I don't know whether this is
an optimal solution, maybe it'd be better to give the mail/createFolder
function a new parameter that tells whether to return the result with or
without the namespace prefix?