Tickets :: [#7351] Ingo does not correctly detect the spam_folder setting from imp

6.0.0-beta1

7/7/25

Summary	Ingo does not correctly detect the spam_folder setting from imp
Queue	Ingo
Queue Version	1.2.1
Type	Bug
State	Not A Bug
Priority	1. Low
Owners
Requester	m.gabriel (at) das-netzwerkteam (dot) de
Created	09/17/2008 (6137 days ago)
Due
Updated	12/21/2009 (5677 days ago)
Assigned	11/06/2008 (6087 days ago)
Resolved	12/21/2009 (5677 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

12/21/2009 09:28:05 PM	Jan Schneider	Comment #3 Taken from Chuck Hagenbuch Taken from Jan Schneider Taken from Gunnar Wrobel State ⇒ Not A Bug	Reply to this comment
This feature has been removed altogether with Ingo 1.2.2.

12/29/2008 10:10:59 AM	Jan Schneider	Version ⇒ 1.2.1 Queue ⇒ Ingo

12/29/2008 09:33:49 AM	Gunnar Wrobel	Comment #2 Assigned to Chuck Hagenbuch Assigned to Jan Schneider Taken from Thomas Jarosch Summary ⇒ Ingo does not correctly detect the spam_folder setting from imp	Reply to this comment
I can validate this but this is no Kolab specific bug. The queue should be changed to imp or ingo. The patch cannot be used as it is indeed only a workaround.

11/06/2008 05:26:56 AM	Chuck Hagenbuch	Assigned to Thomas Jarosch Assigned to Gunnar Wrobel State ⇒ Assigned

09/17/2008 06:00:56 PM	Chuck Hagenbuch	Version ⇒ Queue ⇒ Kolab

09/17/2008 05:39:35 PM	m (dot) gabriel (at) das-netzwerkteam (dot) de	Comment #1 State ⇒ Unconfirmed New Attachment: ingo-Storage.php.patch Patch ⇒ No Milestone ⇒ Queue ⇒ Ingo Summary ⇒ with kolab-backend: spam_folder not detected from imp Type ⇒ Bug Priority ⇒ 1. Low	Reply to this comment
when i use horde as a kolab-client, then ingo does not detect the "spam_folder" preference from imp (it retrieves e.g. "Junk-E-Mail" from imp but wants to have "INBOX/Junk-E-Mail". patch/workaround is attached...