- dovecot - dovecot.org

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

[Dovecot] Incompatibility Thunderbirds Auth Mech TLS-Certificate <-> Dovecot
by Christian Felsing 25 Apr '14

25 Apr '14

Hello, it seems there there is an issue regarding "TLS-Certtificate" authentication in Thunderbird and Dovecot. Obviously client certificate is recognized by Dovecot: Apr 25 14:29:01 dovecot dovecot: imap-login: Valid certificate: /emailAddress=christian.felsing(a)example.net/CN=Christian Felsing (Test)/OU=CF Certificates/O=example.net/C=DE AFAIK Dovecot always requires IMAP login, even in "static" passdb config. Static means arbitrary password is ok, but not "no login" I hope, I am wrong, following log entry gave a hint, what Thunderbird does or more precisely - not do: Apr 25 14:29:01 dovecot dovecot: imap-login: Disconnected (no auth attempts in 5 secs): user=<>, rip=192.168.1.99, lip=192.168.42.1, TLS, session=<3+1THN33NQBtWq5D> Dovecot wants an IMAP login, but Thunderbird does not so. I am not sure if that is a bug (or feature) of Dovecot or Thunderbird. Thunderbird does several strange things on client certificates: 1st) If Dovecot is configured to request a client certificate and Thunderbird is configured to use plain text auth, Thunderbird offers a client certificate and login succeeds as configured in Dovecot. Unfortunately Thunderbird uses same certificate for all configured accounts to that host. Very bad if Dovecot reads username from certificate attributes. 2nd) If Dovecot is configured to request a client certificate and Thunderbird is configured to use TLS-Certificate, Thunderbird also offers a client certificate, but Dovecot requests login from Thunderbird. That fails, because Thunderbird assumes TLS-Certificate is enough for successful log. If it is true that Dovecot is not compatible to Thunderbirds way of TLS-Certificate Authentication, I consider to set up a proxy, which supports that way. May be Nginx would be a solution, it supports IMAP and LUA module plus some LUA code will fake the authentication. This is an ugly hack so I would like to avoid that, if anybody has a better solution. Thunderbird is a very widespread IMAP client so it should not be ignored. best regards Christian ---Dovecot config--- # /opt/dovecot/bin/doveconf -n # 2.2.12: /opt/dovecot/etc/dovecot-cert/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4 auth_debug = yes auth_debug_passwords = yes auth_master_user_separator = * auth_ssl_require_client_cert = yes auth_ssl_username_from_cert = yes auth_username_chars = "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@#" auth_username_translation = "@#" base_dir = /var/run/dovecot-cert first_valid_uid = 124 last_valid_uid = 124 listen = 192.168.42.1 log_timestamp = %Y-%m-%d %H:%M:%S login_greeting = example.net imap4/pop3 (cert only) ready. mail_gid = 124 mail_location = maildir:~/Maildir mail_privileged_group = vmail mail_uid = 124 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave imapflags notify namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace inbox { inbox = yes list = 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 = separator = / type = private } passdb { args = password=test driver = static } plugin { acl = vfile:/etc/dovecot/global-acls:cache_secs=300 acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes autocreate = Trash autocreate2 = Drafts autosubscribe = Trash autosubscribe2 = Drafts quota = maildir:User quota quota_rule = *:storage=500M quota_rule2 = Trash:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u recipient_delimiter = + sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags } protocols = imap pop3 lmtp sieve service anvil { client_limit = 4000 } service auth-worker { group = vmail } service auth { client_limit = 8000 unix_listener auth-master { group = vmail mode = 0660 user = vmail } unix_listener auth-userdb { group = vmail mode = 0660 user = dovecot } user = root } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_limit = 1024 } service imap-postlogin { executable = script-login /opt/cfbin/lastlogin.sh } service imap { executable = imap imap-postlogin } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } process_limit = 1024 } service pop3-postlogin { executable = script-login /opt/cfbin/lastlogin.sh } service pop3 { executable = pop3 pop3-postlogin } service quota-warning { executable = script /opt/cfbin/quota-warning.sh user = vmail } ssl_ca = </opt/dovecot/etc/dovecot/client-ca.pem ssl_cert = </opt/dovecot/etc/dovecot/example.net.pem ssl_cipher_list = kEECDH:kEDH:AESGCM:ALL:+3DES:!RC4:!LOW:!EXP:!MD5:!aNULL:!eNULL ssl_dh_parameters_length = 4096 ssl_key = </opt/dovecot/etc/dovecot/example.net.key ssl_prefer_server_ciphers = yes ssl_verify_client_cert = yes verbose_ssl = yes protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 20 mail_plugins = quota imap_quota acl imap_acl } protocol sieve { managesieve_logout_format = bytes ( in=%i : out=%o ) } protocol pop3 { mail_plugins = quota pop3_uidl_format = %08Xu%08Xv }

2 1

[Dovecot] separating logs by port
by Hanno Böck 25 Apr '14

25 Apr '14

Hi, I wanted to ask if there's an easy way to log the port in dovecot. The background is that, as everyone's probably aware, pop3/imap usually listen on two ports (110/995 for pop3, 143/993 for imap). One port is the "classic" port that allows unencrypted and STARTTLS connections, the other is the legacy SSL port that allows TLS only connections. The legacy SSL ports are considered deprecated and I'd like to know if I can deprecate them on my severs. Therefore I'd like to know how many users use them, but at the moment I can't see which port my users use. I haven't found an easy way to detect that. The easiest thing would be if there'd be a way to add the port number to the pop3-login/imap-login lines in the log files. Any way to do that? cu, -- Hanno Böck http://hboeck.de/ mail/jabber: hanno(a)hboeck.de GPG: BBB51E42

2 1

[Dovecot] Multiple Instances Of Dovecot On One Messagebase
by Christian Felsing 25 Apr '14

25 Apr '14

Hello, I would like to run multiple instances of Dovecot with same message base (maildir format) Will this set up work or would that destroy message base? Intention is to offer different authentication methods to users, username/password and client certificates. Those instances should run on different IP addresses which is supported by Dovecot. Unfortunately Dovecot does not allow different auth configs in "local <ip> {}" sections. best regards Christian

1 0