Hi Nate,
Thanks for the suggestion! Unfortunately, it still failed :(
I got the following error message in proftp log:
2013-08-09 08:32:41,777 mod_sql/4.3[32384]: entering postgres cmd_escapestring
2013-08-09 08:32:41,777 mod_sql/4.3[32384]: entering postgres cmd_open
2013-08-09 08:32:41,777 mod_sql/4.3[32384]: connection 'default' count is now 2
2013-08-09 08:32:41,777 mod_sql/4.3[32384]: exiting postgres cmd_open
2013-08-09 08:32:41,777 mod_sql/4.3[32384]: entering postgres cmd_close
2013-08-09 08:32:41,777 mod_sql/4.3[32384]: connection 'default' count is now 1
2013-08-09 08:32:41,777 mod_sql/4.3[32384]: exiting postgres cmd_close
2013-08-09 08:32:41,777 mod_sql/4.3[32384]: exiting postgres cmd_escapestring
2013-08-09 08:32:41,777 mod_sql/4.3[32384]: cache hit for user '
hailiang.mei1@nbic.nl'
2013-08-09 08:32:41,777 mod_sql/4.3[32384]: >>> cmd_check
2013-08-09 08:32:41,777 mod_sql/4.3[32384]: checking password using SQLAuthType 'sha1'
2013-08-09 08:32:41,781 mod_sql/4.3[32384]: 'sha1' SQLAuthType handler reports failure
2013-08-09 08:32:41,781 mod_sql/4.3[32384]: checking password using SQLAuthType 'sha256'
2013-08-09 08:32:41,781 mod_sql/4.3[32384]: 'sha256' SQLAuthType handler reports failure
2013-08-09 08:32:41,781 mod_sql/4.3[32384]: checking password using SQLAuthType 'pbkdf2'
2013-08-09 08:32:41,841 mod_sql/4.3[32384]: 'pbkdf2' SQLAuthType handler reports failure
2013-08-09 08:32:41,841 mod_sql/4.3[32384]: <<< cmd_check
2013-08-09 08:32:41,841 mod_sql/4.3[32384]: <<< cmd_auth
The old user account generated before our code update still works.