Well, that makes sense. My mail server is constantly hammered with brute
force attacks that don't include domain names.
On Tue, Nov 7, 2017 at 6:50 AM, Eric Broch wrote:
> Yes, it is odd. But even so it will happen if the domain field is empty,
> for whatever reason.
Yes, it is odd. But even so it will happen if the domain field is empty,
for whatever reason. If the domain field is empty it will look for the
vpopmail.users db which in our case doesn't exist.
On 11/7/2017 7:12 AM, Boheme wrote:
Well, I get why it was establishing a connection, as I had
Well, I get why it was establishing a connection, as I had just restarted
dovecot. Just seemed odd that it was trying to access a table that doesn’t
exist. But if legacy code from before the table-per-domain refactoring if the
vpopmail DB layout?
-Sent from my Pip-Boy 3000
> On Nov 7, 2017,
Chris,
This could happen if dovecot sends an empty domain to the vpopmail/mysql
authentication query, there my be other reasons that I'm not aware of
yet. The function call to vpopmail is 'vauth_getpw(vpop_user,
vpop_domain)'. I'm not sure HOW this would happen.
Can you send me the
Here's the explanation in the code as a result of the 'mysql_query' and
'mysql_error' call:
if (mysql_query(_read,SqlBufRead)) {
fprintf(stderr, "vmysql: sql error[3]: %s\n",
mysql_error(_read));
/* - May 29, 2006 - With newer versions of MySQL, there is
such a thing
That's a good question, Chris. I'll have to delve into the code.
On 11/6/2017 9:57 PM, Chris wrote:
Given that the new DB structure for vpopmail involves having a
separate table for each domain, I thought seeing this in my
dovecot.log was a little weird:
Nov 06 20:53:43 auth-worker: Error:
Given that the new DB structure for vpopmail involves having a separate
table for each domain, I thought seeing this in my dovecot.log was a little
weird:
Nov 06 20:53:43 auth-worker: Error: vmysql: sql error[3]: Table
'vpopmail.users' doesn't exist
Nov 06 20:53:43 auth-worker: Error: Attempting