[email protected] wrote :

> You ever resolve this? I had to roll back the courier-auth packages to
> the previous versions... that was the only solution I could find.

I did like you : removing courier-authlib-mysql_0.58-4+etch2 and 
re-installating courier-authlib-mysql_0.58-4 package from etch main 
repository by pining this package in /etc/apt/preferences

Package: courier-authlib-mysql
Pin: version 0.58-4
Pin-Priority: 1001


Hopefully, there is no dependancies with courier-authlib-mysql package, 
so it was quite easy.


But someone in Debian Brugtrack gave a trick to use the 0.58-4+etch2 
version when user login have no domain part :


http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=509280

---
From: Gabriele Vivinetto <[email protected]>
To: Debian Bug Tracking System <[email protected]>
Subject: Re: courier-authlib: bug with certain setups
Date: Mon, 22 Dec 2008 18:48:01 +0100

Package: courier-authlib
Version: 0.58-4+etch2
Followup-For: Bug #509280

I confirm that this bug exist in configuration where you authenticate
whith a username that does not contain the domain part.
I solved the problem defining in
  /etc/courier/authmysqlrc
an explicit MYSQL_SELECT_CLAUSE where the username is selected appending
the "@", like this:
  MYSQL_SELECT_CLAUSE             SELECT \
                                         CONCAT(username, '@'), \
                                         "", \
                                         password, \
  .......
---

i think it could work to "fake" the  mysql_real_escape_string()

But i did not test Grabiele's tick yet , i just discover it this 
evening. And tomorrow i'll get few rest days for Christmas and New year, 
so i don't want to broke the imap server again of my University before 
leaving, users would hang me....  :)


--
Arnaud


------------------------------------------------------------------------------
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to