Just to follow-up on my previous post, I did some experimenting and if you use a custom query and do not include an '@' in the userId, sqwebmail will not even send the query to the db!
Does anyone know how to: 1. Force sqwebmail to submit a custom query to the db even if the username does not contain a '@'? 2. Use the complete username field as sent by the login screen, instead of just $(local_part) and $(domain)...Maybe $(local_part) would contain it if sqwebmail submitted the query? If this requires code changes to sqwebmail, we would be willing to pay for a patch. The above is using sqwebmail 3.6.0. Thanks, Trevor On Sun, 17 Aug 2003, Trevor Astrope wrote: > Hi, > > I'm using authpgsql with sqwebmail with a custom query. The main reason > I'm using the custom query is because the id field I use doesn't contain > the [EMAIL PROTECTED], but just a unique username. So my custom query returns a > different field I call email instead of the id field. The email field > contains the [EMAIL PROTECTED] This is so I get the virtual domain instead of > the [EMAIL PROTECTED] in the sqwebmail pages. > > I know I can just use [EMAIL PROTECTED] in the id field, but I need it to be > backward compatible with the existing system with courier-imap's pop3d, > which also uses authpgsql, but the built-in query, since all userId's are > unique and I don't need the domain returned. > > Now, what I'd like to do is have the pop3d use the authdaemon from > sqwebmail to reduce the number of db hits. So my questions are: > > 1. Is it possible to make the authdaemon with courier-imap cache like the > sqwebmail authdaemon? > > 2. Is there a variable besides $(local_part) and $(domain) that I can use > with the custom query in sqwebmail, like $(id) that contains the whole > userId field? This way, I could have pop3d use the sqwebmail authdaemon > socket. > > I tried using $(local_part) in my custom query, but it doesn't seem to > work if the username doesn't contain an '@' in it. > > Like I said, all the userId's are unique, so I'd like to be able to > authenticate without having to specify the [EMAIL PROTECTED] in a custom query. > Is this possible? > > Thanks, > > Trevor > > Regards, Trevor Astrope [EMAIL PROTECTED]
