April 2014 - dovecot - dovecot.org

[Dovecot] Why does it appear that dovecot is deleting messages after migration?
by Bill Eccles 28 Apr '14

28 Apr '14

Hi, y'all, long-time Mac OS X Server user Bill here with a thorny question for the mailing list since nobody at discussions.apple.com can quite put their finger on the answer. While well-aquainted with other aspects of Server, Dovecot is a bit of a mystery still to me. So here it goes: Background I'm struggling to migrate from MacOS X 10.6 to 10.9. I tried twice using the "live server in target disk mode" method, but after things went horribly awry (meaning I was left with no working services on the new server), I gave up on that and have been working to slowly bring services over, one at a time. I've got both Dovecot and PostFix accepting connections from my test machine, and I am able to connect with IMAP to the new server. What I Do... First, I turn both mail servers off. Then I tar up the /var/spool/imap/dovecot/mail directory on the old server, move it to the new server, untar it in /Library/Server/Mail/Data/ (where it belongs), and change ownership to _dovecot:mail, all per many other suggestions found in the Apple forums. (All files appear to be in maildir format, that I can tell.) I then turn the mail service back on on the new server. What Dovecot Does... (or appears to do) If I quickly connect to the new server with my IMAP client (MacOS X Mail.app) and create a "fresh user" in Mail.app, message folders appear correctly. But it's only a matter of time before Dovecot, or something, runs "doveadm index -u (usernames) (mailboxes)" on all of the mailboxes. As it does, it deletes thousands of messages, leaving, for example, the same 17 in INBOX and 3695 in "Deleted Items Archive". And 0 in others, and other seemingly-random numbers of messages in still yet others. I can watch it marching through the mailboxes, one at a time, if I "ps -ax" enough times. What I've Done to Counteract This... Nothing I've done so far has been able to do anything about it. Re-untar the archive, and it just does it all again. Try using dsync, and it just deletes the messages from the un-tar'd archive. In other words, there are thousands of messages in the archive which don't seem to meet Dovecot's requirement for being in that particular folder, so it deletes them. The "cur" directory in a mailbox directory may start out with >21000 messages in it, but when it's done, it'll have deleted the same messages from "cur" every time, leaving me with a fraction of what I started out with. I even used the 65-migrate_mailboxes.pl script (supplied as part of OS X 10.9 Server), and the same thing happens. (The migrate script does a lot more than just what I've noted above, but most of what it does is responsible for settings and configuration migration. Very little of the script is responsible for moving the data, and that part of the script ends up being a bunch of "cp" followed by a "chown"--essentially what I'm doing.) The Questions What is going on? Failing a fix, am I trying to migrate the wrong way? Is there a better way? Random Thoughts and Observations I've changed hostnames. The old one was shr-xs.mydomain.net, and the new one is shr-mini.mydomain.net. Is it unhappy with that for some reason? In one of the directories where messages are deleted, there were a zillion files named like this: 1396718896.M324523P43630.shr-xs.mydomain.net,S=1209,W=1238:2,Sac There were also a bunch of files named like this: 1211416234.cyrus.457,S=893:2,Sac When it's all said and done, and Dovecot has done its thing, care to guess which ones are left? Only these: 1211416234.cyrus.457,S=893:2,Sac Just to see if I could influence which files get deleted, I deleted all of the dovecot* files in the mailbox directory. And Dovecot recreated them faithfully, but still deleted all but the ones which said "cyrus" in the filenames. I changed the hostname to match shr-xs.mydomain.net, and that doesn't seem to have affected things a bit, though I don't have enough data to support that I really succeeded in changing the hostname for all services (specifically for Dovecot). Is Dovecot really filtering out messages that just don't seem to "belong" in the folder? Thanks, y'all. I've puzzled on this one for about eight hours and it now hurts my brain. I hope somebody else has an answer sans brain hurts.

3 3

[Dovecot] dovecot temporary suspension all of pop3 login about 5 minutes
by Jason 28 Apr '14

28 Apr '14

Dear All， When the user login P0P3 more than 10 times in 1 minute that the dovecot temporary suspension all of pop3 login about 5 minutes. How to disable the setting for dovecot. Mail Log: Apr 24 16:11:14 mww dovecot: pop3-login: Login: user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, mpid=8767, session=<5USPZMX3/QDAqBBU> Apr 24 16:11:14 mww dovecot: pop3(scan): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 24 16:11:15 mww dovecot: auth-worker: Error: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory Apr 24 16:11:15 mww dovecot: pop3-login: Login: user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, mpid=8769, session=<GzyeZMX3/wDAqBBU> Apr 24 16:11:15 mww dovecot: pop3(scan): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 24 16:11:16 mww dovecot: auth-worker: Error: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory Apr 24 16:11:16 mww dovecot: pop3-login: Login: user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, mpid=8771, session=<bGSsZMX3AQDAqBBU> Apr 24 16:11:16 mww dovecot: pop3(scan): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 24 16:11:17 mww dovecot: auth-worker: Error: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory Apr 24 16:11:17 mww dovecot: pop3-login: Login: user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, mpid=8773, session=<ASq6ZMX3AwDAqBBU> Apr 24 16:11:17 mww dovecot: pop3(scan): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 24 16:11:18 mww dovecot: auth-worker: Error: no talloc stackframe at ../source3/param/loadparm.c:4864, leaking memory Apr 24 16:11:18 mww dovecot: pop3-login: Login: user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, mpid=8775, session=<Ux3JZMX3BQDAqBBU> Apr 24 16:11:18 mww dovecot: pop3(scan): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Apr 24 16:11:23 mww dovecot: pop3-login: Disconnected (auth failed, 1 attempts in 4 secs): user=<scan>, method=PLAIN, rip=192.168.16.84, lip=192.168.16.159, session=<kP3WZMX3BwDAqBBU> Apr 24 16:12:04 mww dovecot: pop3-login: Disconnected (auth failed, 1 attempts in 4 secs): user=<jason>, method=PLAIN, rip=192.168.16.59, lip=192.168.16.159, session=<WX9NZ8X3pwDAqBA7> Dovecot v2.2.9 # 2.2.9: /etc/dovecot/dovecot.conf doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:99: ssl_disable has been renamed to ssl # OS: Linux 3.13.0-24-generic x86_64 Ubuntu 14.04 LTS disable_plaintext_auth = no mail_location = mbox:~/mail:INBOX=/var/mail/%u namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = " imap pop3" ssl = no ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { driver = passwd } protocol imap { mail_max_userip_connections = 100 } protocol pop3 { mail_max_userip_connections = 100 } Best regards, Jason

2 3

Re: [Dovecot] Fwd: Dovecot cannot connect to PostgreSQL server
by Chris Vaas 28 Apr '14

28 Apr '14

On Mon, Apr 28, 2014 at 9:30 AM, Steffen Kaiser < skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Mon, 28 Apr 2014, Chris Vaas wrote: > > I just looked into my SELinux audit log and found the following denial. >> >> type=AVC msg=audit(1398609990.493:280): avc: denied { name_connect } for >> pid=5964 comm="auth" dest=5432 >> scontext=unconfined_u:system_r:dovecot_auth_t:s0 >> tcontext=system_u:object_r:postgresql_port_t:s0 tclass=tcp_socket >> >> There seems to be a good chance, that this is my problem, doesn't it? But >> how can I allow the connection? >> > > I don't run SELinux, checkout a SELinux HowTo, e.g. > http://wiki.centos.org/HowTos/SELinux, audit2allow looks promising. > > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBU14Dj3z1H7kL/d9rAQKtdwf/d4mIe45sOFRkOc+BGfhD/PSYOKK9Akk9 > xRofzDZszgj/I9w1T5AWrND3Xn3RfXmCA3MuvEG4L3JAIznuPJWAATkV1XMw56v5 > pe4Z6SRB9aH6QZFvmDBfO5pEVrsGoXYeDCY78rZhSERXXgutCDuWHhQUK6pnnXTY > m2lumWt6w1mHpvLZZ5gxd2MjZiDZqYJYhhDbMGxb6lcVN42WJgfD5Lm1J000F6Pq > pbwCR+2lz2W9tBTCChJqTwIMebUhxesUQxcmFrh9/0/tR7b5hKkEY2o9OtDxRGt6 > A6qE/9H82peC64AtV7Cn6rbEJ76HVSCWMP9lLOhmiflpP3cwF+d7VA== > =aI5S > -----END PGP SIGNATURE----- > Bam. Works! Thank you very much, everyone! Cheers Chris

1 0

Re: [Dovecot] Fwd: Dovecot cannot connect to PostgreSQL server
by Chris Vaas 28 Apr '14

28 Apr '14

On Mon, Apr 28, 2014 at 9:11 AM, Steffen Kaiser < skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Mon, 28 Apr 2014, Chris Vaas wrote: > > On Mon, Apr 28, 2014 at 8:43 AM, Steffen Kaiser < >> skdovecot(a)smail.inf.fh-brs.de> wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> On Sun, 27 Apr 2014, Chris Vaas wrote: >>> >>> [fixed ugly top posting] >>> >>> On Sat, Apr 26, 2014 at 11:39 PM, Steffen < >>> skdovecot(a)smail.inf.fh-brs.de >>> >>>> wrote: >>>>> >>>> >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> >>>>> Hash: SHA1 >>>>> >>>>> Chris Vaas wrote: >>>>> >>>>> I am currently facing the following log output: >>>>>> >>>>>> Apr 26 16:40:28 h2290750 dovecot: auth: Error: pgsql(localhost): >>>>>> Connect failed to database mail: could not connect to server: >>>>>> Permission denied Apr 26 16:40:28 h2290750 dovecot: auth: Error: >>>>>> #011Is the server running on host "localhost" (::1) and accepting >>>>>> Apr 26 16:40:28 h2290750 dovecot: auth: Error: #011TCP/IP >>>>>> connections on port 5432? >>>>>> >>>>>> I have double checked the database. It is listening correctly and I >>>>>> can connect to it via >>>>>> >>>>>> psql -U mailreader mail >>>>>> >>>>>> I provided all necessary information to dovecot via this >>>>>> configuration snippet: >>>>>> >>>>>> driver = pgsql connect = host=localhost dbname=mail user=mailreader >>>>>> password=secret default_pass_scheme = SHA512 >>>>>> >>>>>> >>>>> does Postgres allow connections on "host ::1" for user mailreader ? >>>>> Actually I wonder, because I thought the Postgres lib defaults to >>>>> "local" (socket) by default on localhost -> does Postgres allow >>>>> connections on "local" for mailreader? Permissions are configured in >>>>> pg_hba.conf, but -> Does Postgres logs something? It should if PG >>>>> denies the connection. >>>>> >>>>> >>>> I set the host to 127.0.0.1 now. And my pg_hba.conf looks like that: >>> >>>> >>>> # TYPE DATABASE USER ADDRESS METHOD >>>> # Mail stuff >>>> host mail mailreader 127.0.0.1/32 md5 >>>> host mail mailreader ::1/128 md5 >>>> local all all md5 >>>> host all all 127.0.0.1/32 ident >>>> host all all ::1/128 ident >>>> >>>> >>> What about the "Does Postgres logs something?" >>> >>> >> The log under /var/logs/pgsql is completely empty. >> > > In addition to Aleksandar's question: Does Postgres runs at all? > > >>> Do you have SELinux or something like that running? >>> What about this question? >>> >> >> I do have a SELinux up and running, yeah. >> > > Did you've checked its logs, e.g. (pretty old): > http://linux.derkeiler.com/Mailing-Lists/Fedora/2006-03/msg05342.html > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBU13/FXz1H7kL/d9rAQLjbQf+IQV/jSAj+fvxCaIgxgzktUuJenONp5Za > LrxYEQ79YelD5ljH1Ms1cYyegp5+8ecHsp0Fc850ZBeEYsplfZjfvAoPP4lO+cdH > GOPt3+zniEdeEVMVFfOokyTGjSPWbRrlb5r/wWYj6pU35pkw1pK3M6hPxF2Y6grm > poLMdHvaktwIr9STtqu1JTOxRffLgW5qh1AcQwJ+BoNs+h0MKs7ddqgnfeV9bKZx > rmyOuAU36QnNcv+LJQJSiJMFw1pejS+OBvI23xYsj/04dAAiTzNHGe3doz/sF1PX > P2zroewTEEb+lkvjUkOmukLuTlLnCAVgdHyWZF37c5vML9HD7Xyqrg== > =e13N > -----END PGP SIGNATURE----- > It is running, yes. I can connect from my local machine to the server without a flaw. About SELinux: I just looked into my SELinux audit log and found the following denial. type=AVC msg=audit(1398609990.493:280): avc: denied { name_connect } for pid=5964 comm="auth" dest=5432 scontext=unconfined_u:system_r:dovecot_auth_t:s0 tcontext=system_u:object_r:postgresql_port_t:s0 tclass=tcp_socket There seems to be a good chance, that this is my problem, doesn't it? But how can I allow the connection? Cheers Chris

2 1

Re: [Dovecot] Fwd: Dovecot cannot connect to PostgreSQL server
by Chris Vaas 28 Apr '14

28 Apr '14

On Mon, Apr 28, 2014 at 8:43 AM, Steffen Kaiser < skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Sun, 27 Apr 2014, Chris Vaas wrote: > > [fixed ugly top posting] > > On Sat, Apr 26, 2014 at 11:39 PM, Steffen <skdovecot(a)smail.inf.fh-brs.de >> >wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> Chris Vaas wrote: >>> >>>> I am currently facing the following log output: >>>> >>>> Apr 26 16:40:28 h2290750 dovecot: auth: Error: pgsql(localhost): >>>> Connect failed to database mail: could not connect to server: >>>> Permission denied Apr 26 16:40:28 h2290750 dovecot: auth: Error: >>>> #011Is the server running on host "localhost" (::1) and accepting >>>> Apr 26 16:40:28 h2290750 dovecot: auth: Error: #011TCP/IP >>>> connections on port 5432? >>>> >>>> I have double checked the database. It is listening correctly and I >>>> can connect to it via >>>> >>>> psql -U mailreader mail >>>> >>>> I provided all necessary information to dovecot via this >>>> configuration snippet: >>>> >>>> driver = pgsql connect = host=localhost dbname=mail user=mailreader >>>> password=secret default_pass_scheme = SHA512 >>>> >>> >>> does Postgres allow connections on "host ::1" for user mailreader ? >>> Actually I wonder, because I thought the Postgres lib defaults to >>> "local" (socket) by default on localhost -> does Postgres allow >>> connections on "local" for mailreader? Permissions are configured in >>> pg_hba.conf, but -> Does Postgres logs something? It should if PG >>> denies the connection. >>> >> > I set the host to 127.0.0.1 now. And my pg_hba.conf looks like that: >> >> # TYPE DATABASE USER ADDRESS METHOD >> # Mail stuff >> host mail mailreader 127.0.0.1/32 md5 >> host mail mailreader ::1/128 md5 >> local all all md5 >> host all all 127.0.0.1/32 ident >> host all all ::1/128 ident >> > > What about the "Does Postgres logs something?" > The log under /var/logs/pgsql is completely empty. > > Do you have SELinux or something like that running? >>> >> > What about this question? > I do have a SELinux up and running, yeah. > > > I remember that I had a server that had wrong permissions on: >>> >>> ls -al /var/run/postgresql >>> >>> drwxrwsr-x 2 postgres postgres 4096 Feb 10 07:32 ./ >>> srwxrwxrwx 1 postgres postgres 0 Apr 26 23:15 .s.PGSQL.5432= >>> >>> the .s.PGSQL. socket is the local socket usually used for localhost >>> connections and automatically found by libpg. >>> >> > The folder /var/run/postgresql is not existing on my machine. >> > > - -- Steffen Kaiser - Chris

2 2

[Dovecot] Fwd: Dovecot cannot connect to PostgreSQL server
by Chris Vaas 28 Apr '14

28 Apr '14

I set the host to 127.0.0.1 now. And my pg_hba.conf looks like that: # TYPE DATABASE USER ADDRESS METHOD # Mail stuff host mail mailreader 127.0.0.1/32 md5 host mail mailreader ::1/128 md5 local all all md5 host all all 127.0.0.1/32 ident host all all ::1/128 ident The folder /var/run/postgresql is not existing on my machine. The problem is still present. :( On Sat, Apr 26, 2014 at 11:39 PM, Steffen <skdovecot(a)smail.inf.fh-brs.de>wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Chris Vaas wrote: > > I am currently facing the following log output: > > > > Apr 26 16:40:28 h2290750 dovecot: auth: Error: pgsql(localhost): > > Connect failed to database mail: could not connect to server: > > Permission denied Apr 26 16:40:28 h2290750 dovecot: auth: Error: > > #011Is the server running on host "localhost" (::1) and accepting > > Apr 26 16:40:28 h2290750 dovecot: auth: Error: #011TCP/IP > > connections on port 5432? > > > > I have double checked the database. It is listening correctly and I > > can connect to it via > > > > psql -U mailreader mail > > > > I provided all necessary information to dovecot via this > > configuration snippet: > > > > driver = pgsql connect = host=localhost dbname=mail user=mailreader > > password=secret default_pass_scheme = SHA512 > > does Postgres allow connections on "host ::1" for user mailreader ? > Actually I wonder, because I thought the Postgres lib defaults to > "local" (socket) by default on localhost -> does Postgres allow > connections on "local" for mailreader? Permissions are configured in > pg_hba.conf, but -> Does Postgres logs something? It should if PG > denies the connection. > > Do you have SELinux or something like that running? > > I remember that I had a server that had wrong permissions on: > > ls -al /var/run/postgresql > > drwxrwsr-x 2 postgres postgres 4096 Feb 10 07:32 ./ > srwxrwxrwx 1 postgres postgres 0 Apr 26 23:15 .s.PGSQL.5432= > > the .s.PGSQL. socket is the local socket usually used for localhost > connections and automatically found by libpg. > > - -- > Steffen > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (Darwin) > Comment: Using GnuPG with undefined - http://www.enigmail.net/ > > iQEVAwUBU1wnoXD1/YhP6VMHAQJh8gf/fyThDqYhNiMXk6YNtwgiAT8MLyCblXOR > 1/4scQAFQUTbHgOODBfoJkoTdtsmhBu0UmxNe9Y/1Y+j2pAcVU2GrJAGLEED1Is0 > OmPPptnrdGaqjsIaybIDpmuJM7vqmOYhPMvAOGVXdgXdKa5QQZU3hgo/fH1xdIrj > j45LEfLE8Cu9QedOolXz4adFLk2XuRylMJWhQWrsT3yutr38Nv6wqhRDl7Rxwo4p > 2y1b2GiBTZkVHXzUs0a2UKxOsYsgQVgCcN6wCyio0ogCTAKwHWeQ00rUpNmn9COw > xKf5nhFPR8RYlCKukk7Djb2aklIfvko6S9+QoCKZEufjNi/moA4pcg== > =1sd0 > -----END PGP SIGNATURE----- >

3 2

Re: [Dovecot] Dovecot cannot connect to PostgreSQL server
by Joseph Tam 28 Apr '14

28 Apr '14

Chris Vaas writes: >> psql -U mailreader mail >> >> I provided all necessary information to dovecot via this configuration >> snippet: >> >> driver = pgsql >> connect = host=localhost dbname=mail user=mailreader password=secret >> default_pass_scheme = SHA512 ... > I set the host to 127.0.0.1 now. And my pg_hba.conf looks like that: > > # TYPE DATABASE USER ADDRESS METHOD > # Mail stuff > host mail mailreader 127.0.0.1/32 md5 Shouldn't the last column here match your "default_pass_scheme" above? Maybe change "default_pass_scheme" to "md5-crypt" or "md5"? Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] All Mail folder as in Gmail
by Dmitry Podkovyrkin 27 Apr '14

27 Apr '14

Hello How to make a folder "All Mail" so that it got a letter from the Inbox and Sent? Mail client makes a copy of emails sent to the folder Sent. -- Regards Dmitry Podkovyrkin email: dmirty(a)rutelecom.company

2 2

[Dovecot] Dovecot cannot connect to PostgreSQL server
by Chris Vaas 26 Apr '14

26 Apr '14

I am currently facing the following log output: Apr 26 16:40:28 h2290750 dovecot: auth: Error: pgsql(localhost): Connect failed to database mail: could not connect to server: Permission denied Apr 26 16:40:28 h2290750 dovecot: auth: Error: #011Is the server running on host "localhost" (::1) and accepting Apr 26 16:40:28 h2290750 dovecot: auth: Error: #011TCP/IP connections on port 5432? I have double checked the database. It is listening correctly and I can connect to it via psql -U mailreader mail I provided all necessary information to dovecot via this configuration snippet: driver = pgsql connect = host=localhost dbname=mail user=mailreader password=secret default_pass_scheme = SHA512 password_query = SELECT email as user, password, 'maildir:/home/mail'||maildir as userdb_mail FROM users WHERE email = '%u' How can I debug this situation? Cheers Chris

4 4

Re: [Dovecot] Dovecot cannot connect to PostgreSQL server
by Reindl Harald 26 Apr '14

26 Apr '14

first: don't reply off-list and don't top-post Am 26.04.2014 18:26, schrieb Christian Vaas: > How do I determine my postgresql socket location? > > On Apr 26, 2014 6:17 PM, "Reindl Harald" <h.reindl(a)thelounge.net <mailto:h.reindl@thelounge.net>> wrote: > > Am 26.04.2014 18 <tel:26.04.2014%2018>:06, schrieb Chris Vaas: > > I am currently facing the following log output: > > > > Apr 26 16:40:28 h2290750 dovecot: auth: Error: pgsql(localhost): Connect > > failed to database mail: could not connect to server: Permission denied > > Apr 26 16:40:28 h2290750 dovecot: auth: Error: #011Is the server running on > > host "localhost" (::1) and accepting > > Apr 26 16:40:28 h2290750 dovecot: auth: Error: #011TCP/IP connections on > > port 5432? > > > > I have double checked the database. It is listening correctly and I can > > connect to it via > > > > psql -U mailreader mail > > > > I provided all necessary information to dovecot via this configuration > > snippet: > > > > driver = pgsql > > connect = host=localhost dbname=mail user=mailreader password=secret > > default_pass_scheme = SHA512 > > password_query = SELECT email as user, password, > > 'maildir:/home/mail'||maildir as userdb_mail FROM users WHERE email = '%u' > > > > How can I debug this situation? > > try "host=/path/to/your/unix/socket" instead just only "localhost" > or switch to TCP with using 127.0.0.1 instead localhost > > in case of mysqld this would be "host=/var/lib/mysql/mysql.sock" why don't you know that? it's your machine and i don't use PostgreSQL at all "updatedb; locate post | grep socket" may be a good start just read the man page of your distribtion or use google google: "name-of-your-distribution postgresql unix socket" or simply try 127.0.0.1 which is as explained different to localhost localhost is typically unix-socket and 127.0.0.1 TCP/IP, in any case you have to make sure that the user is allowed in case of mysql i can set different permissions for "user1@localhost" and "user1(a)127.0.0.1", most likely PostgeSQL supports that too

1 0