postfix 3.1.0-3 fails on mysql table lookup
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postfix |
New
|
Undecided
|
Unassigned | ||
postfix (Debian) |
Fix Released
|
Unknown
|
Bug Description
what I get in the log:
Jul 3 01:21:40 postfix/
Jul 3 01:21:40 postfix/
Jul 3 01:21:40 postfix/
Configuration:
virtual_alias_maps = mysql:/
and the query in that file:
query = CALL get_aliases_
the stored procedure in the database could be as simple as
CREATE PROCEDURE `get_aliases_
BEGIN
SELECT CONCAT(
END
The bare select itself as query does work fine.
The crucial thing is that <email address hidden> already is the alias destination, so the first query worked fine. In fact postalias -q .... returns valid results.
I believe this occurs because of the mysql library returning an second empty result set which is not removed/cleared by postfix.
See this discussion which describes a similar issue:
http://
I'm not familiar with the postfix sources but I think a possible fix could be inserted into the plmysql_query function in dict_mysql.c similar to what is discussed in the link and a dozen similar mysql api issues on the web.
Changed in postfix (Debian): | |
status: | Unknown → Fix Released |