Tickets :: Comment on [#10617] INGO Auth Generation Incorrect

* Your Email Address
* Spam protection	Enter the letters below: _______ _ ________ _______ \|___ / \| \| \| ____\ \ / / __ \ / /\| \| \| \| \|__ \ \ / /\| \|__) \| / / \| \| \| \| __\| \ \/ / \| ___/ / /__\| \|__\| \| \| \ / \| \| /_____\|\____/\|_\| \/ \|_\|
Comment	>> When trying to setup Ingo with my Dovecot Managesieve server I ran >> into an authentication issue. Ingo was always including the Horde >> user credential when generating the base64 encoded plain >> authentication as the first field. I need this field to be blank in >> order for Dovecot to properly authenticate. > > I don't follow. What are you talking about? > >> I tracked the issue down to a line in >> ingo/lib/Transport/Timsievd.php. I went ahead an updated the file so >> it will use the "euser" parameter passed from backends.php or default >> to using the pre-existing call to Ingo::getUser(false). I have >> attached a patch detailing the updates I made. > > That doesn't make sense, how is managesieve supposed to know for > which user to accept the uploaded script, if you hardcode the > effective user to a fixed value?
Attachment
Watch this ticket