Scott Kitterman:
> I am looking at some of the two decades of accumulated cruft in the Debian
> bug
> tracking system for the Postfix package. I came across an old bug with a
> patch that appears never to have been incorporated (no sign ups required):
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=400395
>
> I've attached the patch (it's very old, but at a glance it doesn't look like
> the relevant code has changed much).
>
> No one in Debian who works on Postfix uses the mysql bits. Is there anyone
> that is using it that thinks it's worth updating and seeing if it can be
> incorporated?
I think that something along those lines has been implemented.
Wietse
MYSQL_TABLE(5) MYSQL_TABLE(5)
NAME
mysql_table - Postfix MySQL client configuration
...
option_file
Read options from the given file instead of the default my.cnf
location. This reads options from the [client] option group,
optionally followed by options from the group given with
option_group.
This parameter is available with Postfix 2.11 and later.
option_group (default: Postfix >=3.2: client, <= 3.1: empty)
Read options from the given group of the mysql options file,
after reading options from the [client] group.
Postfix 3.2 and later read [client] option group settings by
default. To disable this specify no option_file and specify
"option_group =" (i.e. an empty value).
Postfix 3.1 and earlier don't read [client] option group set-
tings unless a non-empty option_file or option_group value are
specified. To enable this, specify, for example, "option_group =
client".
This parameter is available with Postfix 2.11 and later.
