Tickets :: [#3682] multiple sieve backends

Summary	multiple sieve backends
Queue	Ingo
Queue Version	HEAD
Type	Enhancement
State	Rejected
Priority	1. Low
Owners
Requester	adrieder (at) sbox (dot) tugraz (dot) at
Created	03/23/2006 (7108 days ago)
Due
Updated	03/24/2006 (7107 days ago)
Assigned
Resolved	03/23/2006 (7108 days ago)
Milestone
Patch	No

03/24/2006 09:17:22 AM	adrieder (at) sbox (dot) tugraz (dot) at	Comment #3	Reply to this comment
http://wiki.horde.org/IngoMulti Thats not a solution.... :( How should a user know which one of the instances of ingo (ingo, imgo, ipgo and so on) to use for his server. We are providing IMP for serveral IMAP server of several domains. It would be nice to determin the ingo backend depending on the realm used in hordeauth.

03/23/2006 10:33:35 PM	Chuck Hagenbuch	Comment #2 State ⇒ Rejected	Reply to this comment
http://wiki.horde.org/IngoMulti

03/23/2006 09:42:10 PM	adrieder (at) sbox (dot) tugraz (dot) at	Comment #1 State ⇒ New Priority ⇒ 1. Low Type ⇒ Enhancement Summary ⇒ multiple sieve backends Queue ⇒ Ingo	Reply to this comment
Hi, it would be very helpful to be able to use multiple sieve backend servers for multiple imap/pop servers, such that depending on which imap/pop server the user is connected via IMP the right sieve backend server will be choosen.