Salaam,
I think that you may have to add proxy to this line
This is your line:
sender_canonical_maps=mysql:/etc/postfix/mysql_canonical_maps.cf
This is what I suggest:
sender_canonical_maps= proxy:mysql:/etc/postfix/mysql_canonical_maps.cf
We use postgres in our organization and we use that proxy keyword too.
Wa Salaam,
Muhammed Sameer
--- On Thu, 1/1/09, Jeff Weinberger <j...@jweinberger.homeip.net> wrote:
> From: Jeff Weinberger <j...@jweinberger.homeip.net>
> Subject: issue connecting to mysql after upgrade
> To: post...@yahoogroups.com, postfix-us...@yahoogroups.com,
> postfix-users@postfix.org, postfix-us...@egroups.com
> Date: Thursday, January 1, 2009, 4:31 PM
> Hello again:
>
> One more issue on which I would appreciate any help anyone
> can offer:
>
> Yesterday I upgraded my postfix installation from 2.5.2 to
> 2.5.5 and my MySQL installation from 5.0.51b to 5.0.75.
> Immediately after restarting everything (the whole
> computer), I started seeing these messages in my mail log:
>
> Jan 1 09:48:35 s postfix/smtpd[13199]: warning:
> connect to mysql server localhost: Can't connect to
> local MySQL server through socket '/tmp' (38)
> Jan 1 09:48:35 s postfix/cleanup[13201]: warning:
> connect to mysql server localhost: Can't connect to
> local MySQL server through socket '/tmp' (38)
> Jan 1 09:48:42 s postfix/trivial-rewrite[13205]:
> warning: connect to mysql server localhost: Can't
> connect to local MySQL server through socket '/tmp'
> (38)
>
> As far as I can tell this has been consistent with smtpd,
> cleanup and trivial-rewrite, but nothing else. (there have
> been pre-existing issues, per my prior conversation with
> mouss, with dspam, but these have not changed at all - they
> existed before the upgrade and still exist)
>
> I use mysql for nearly all my tables in postfix. All of my
> aliases are working and forwarding fine, which means that
> postfix can access my mysql database (and yes, postconf -m
> shows mysql). virtual is finding the maildirs correctly for
> my virtual mailboxes.
>
> However, my sender_canonical_maps are no longer working
> after the upgrade (outbound addresses are not being
> rewritten at all as they were before the upgrade)
>
> As an example, my main.cf contains:
>
> sender_canonical_maps=mysql:/etc/postfix/mysql_canonical_maps.cf
>
> and mysql_canonical_maps.cf contains:
>
> user = postfixuser
> password = postfixpassword
> hosts = localhost, 127.0.0.1
> dbname = postfixdatabase
> query = SELECT result FROM canonical WHERE
> address='%s' AND active='Y'
>
> (obvious information changed). This is unchanged before and
> after the upgrade.
>
> The query works on all the addresses (I tested it at the
> mysql command prompt).
>
> I also tested a local telnet to 127.0.0.1 on port 3306
> which worked as expected and mysql responds perfectly. I
> also tested connection through the localhost socket with
> works as expected. Also several other parts of my mail
> system (e.g. courier_auth) connect through the socket and
> report success. And as noted, postfix is able to connect
> most of the time (aliases, virtual maildirs, etc.). Other
> software on my system, e.g. PHP, is also able to connect to
> mysql successfully.
>
> I tried all the steps in the MySQL documentation on
> dev.mysql.com suggested to diagnose this error, and all
> confirmed that the MySQL server is working correctly.
>
> So I find myself not knowing where to look next, and I hope
> someone here knows what might be happening or at least be
> able to point me in the right direction.
>
> One additional piece of information: I am running on Mac
> OS/X and as part of this upgrade, I installed the 10.5.5 to
> 10.5.6 upgrade (thus needing to restart my computer). This
> upgrade is known to break postfix. So I reinstalled postfix
> and my main.cf and master.cf files after the upgrade and
> stopped and restarted postfix to be sure. (and mysql)
>
> What other information might be helpful in diagnosing this?
>
> Thank you for any help you can offer!
