atom feed11 messages in net.sourceforge.lists.courier-users[courier-users] Re: MYSQL_SELECT_CLAU...
FromSent OnAttachments
Lindsay HaisleyAug 30, 2004 9:14 am 
Sam VarshavchikAug 30, 2004 4:58 pm 
Lindsay HaisleyAug 31, 2004 12:40 pm 
Ben KennedyAug 31, 2004 1:06 pm 
Lindsay HaisleyAug 31, 2004 1:15 pm 
Keith WillisAug 31, 2004 2:06 pm 
Sam VarshavchikAug 31, 2004 3:37 pm 
Lindsay HaisleyAug 31, 2004 6:26 pm 
Sam VarshavchikSep 1, 2004 4:09 am 
Lindsay HaisleySep 1, 2004 9:24 am 
Sam VarshavchikSep 1, 2004 3:48 pm 
Subject:[courier-users] Re: MYSQL_SELECT_CLAUSE again
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Aug 31, 2004 3:37:47 pm
List:net.sourceforge.lists.courier-users

Lindsay Haisley writes:

Thus spake Sam Varshavchik on Mon, Aug 30, 2004 at 06:58:29PM CDT

Lindsay Haisley writes:

I have MYSQL_SELECT_CLAUSE working nicely with a non-standard query on courier-0.38.2 and authmysql. I'm trying to get courier with authmysql set up and working on a customer's mail system the same way, and it looks as if MYSQL_SELECT_CLAUSE isn't working at all in courier-0.46.

Nothing shows up in the mysql log so apparently no mysql query is being made by the mail server.

This indicates a connectivity problem. Check your login parameters:

MYSQL_SERVER MYSQL_USERNAME MYSQL_PASSWORD

These are OK. If I comment out MYSQL_SELECT_CLAUSE and let authmysql build its own query, then everything is hunky-dory, the query works, and shows up in the mysql log, so it's not connectivity.

That does indicate a bug.

Set DEBUG_LOGIN=2; this generates a few debugging messages in syslog.

Also try replacing $(localpart) with a constant string, 'foo'. Perhaps there's a bug in variable substitution getting triggered.