- dovecot - dovecot.org

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

Re: [Dovecot] integration of old mails into new dovecot Maildir
by K. C. Mohan - Personal 25 Apr '14

25 Apr '14

Steffen, Thank you for all your help in helping me resolve my mail integration. I was able to get the old mails integrated into the new server following your suggestion of 1:1 transfer. Thanks again and have a good day. -----Original Message----- From: Steffen Kaiser [mailto:skdovecot@smail.inf.fh-brs.de] Sent: Monday, April 14, 2014 2:18 AM To: K. C. Mohan Cc: dovecot(a)dovecot.org Subject: Re: [Dovecot] integration of old mails into new dovecot Maildir -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 13 Apr 2014, K. C. Mohan wrote: Please, do not top post. > Thank you Steffen, for addressing my problem of migrating old mails > into new mail server. I went through the article you pointed to but > could not succueed. I will appreciate if you could guide me to step by > step process to migrate the mails. My old mail server used 2.x dovecot version. you post very little information: 1) how are the messages storred on the old server, which storage backend do you use, maybe Maildir? 2) the storage backend on the new server? 3) do you care about the message UIDs? 4) How many users do you have (approx.) and can you access the user's mailboxes via IMAP, e.g. using a master user or do you know their password or can you switch to a known password during migration of one particular user? 5) Did you've changed namespaces? - From your first post I figure that the basic mail server functionality of the new server is working, most importantly login, message delivery and retrieval. > -----Original Message----- From: Steffen Kaiser > Sent: Thursday, April 10, 2014 6:14 AM > To: K. C. Mohan - Personal s > Cc: dovecot(a)dovecot.org > Subject: Re: [Dovecot] integration of old mails into new dovecot > Maildir > > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, 8 Apr 2014, K. C. Mohan - Personal wrote: > >> I just installed dovecot 2.2.9 on to a new server and want to >> transfer all the old mails into the email accounts I imported from >> the previous server into MySQL database. I am not able to view the >> subfolders and or old mails that I copied into their respective >> maildir folders. I was very much appreciate if anyone could let me >> know how to import old mails into the new server. All I see, is the >> new mails that have come into the account since I started dovecot service in the new server. > > Check out http://wiki2.dovecot.org/Migration . Read esp. about > "preserving messages' UIDs". > > If the old server uses Maildir, too, and you don't care about the > UIDs, copy the files over and you are done. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBU0t9r3D1/YhP6VMHAQL21wgAx1GgDwQDWwDMPxbMQ+1vR3i7dsyUk5jm PNmRigoV8qylbn2AuZ1YMxGN2wEZfSl2zi/j2CtSEUX+d9LOf+lvI9V8zXkvSHT6 jYEHwuIQACjPUxWmh7x8XelvQvZHB9PEH56z8eJhkgyVxpae8Rbb1EHurvmxckef O0fdmCIglXJdJJ+B9WZ7JZVsB3M6PFFsllizS17+Hus6O2NeVaszLa7o7bk5XInD m+Co4e4sCVphVlssHRCIRa8Lj6nDC+D6g3RjCR+n0rVREXRbvEcSQPerEAqrZhf8 HB46x3V3n6C2fEu7RNWLB0+DzglHLBI5p9ZqAjJRMr3D9Xy9L5SKlQ== =IH25 -----END PGP SIGNATURE----- --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com --- This email is free from viruses and malware because avast! Antivirus protection is active. http://www.avast.com

1 0

[Dovecot] Assert crash with latest HG ddf374a36057
by e-frog 24 Apr '14

24 Apr '14

Hello, Latest HG assert crashes with imap(user): Panic: file mail-storage.c: line 1836 (mailbox_transaction_begin): assertion failed: (box->opened) Full backtrace is attached. Thanks, e-frog

1 0

[Dovecot] Regarding Quota
by Joy 24 Apr '14

24 Apr '14

Dear All, One of my user is using sieve to make a copy of incoming mail in another folder all is working file. I have seen that he is using 15GB out of 20GB space of his mailbox, while calculating the same using du command returns only 9.5 GB. I am not facing this issue with any of other user. Is there something going wrong or misconfiguration causing this.

2 1

[Dovecot] Help implementing username_format in auth PAM driver
by lee＠trager.us 24 Apr '14

24 Apr '14

While configuring my server with dovecot I noticed that the PAM authentication driver does not support the username_format option as does the password file driver. This didn't seem too hard to implement so I through together a patch. As you can see in the attached patch I only modify the username sent to PAM. Despit doing this I run into the domain lost issue(http://wiki2.dovecot.org/DomainLost). This prevents me from using the domain name in my mail_location config string. What I don't understand is why does changing the username string sent to PAM for authentication trigger this issue? Shouldn't dovecot continue to use the client supplied username as I am *not* changing it anywhere in my config? Thanks, Lee

1 0

Re: [Dovecot] Allowing non-SSL connections only for certain Password Databases
by Joseph Tam 24 Apr '14

24 Apr '14

Dan Pollock <pollock(a)theorem.ca> writes: > I would like to move everyone onto more modern mail programs, but at the > moment I have a couple of them that are stuck using very old software > installed for them on work computers. The rest of my clients can connect > on ports 993 and 995 without it being a problem. You know best whether you want to take the risk of compromising passwords on your system (including compromised accounts using for spamming and blowing your mail reputation to smithereens), but I don't know whether your customers do. They may think they are only risking their Email, but it can be leveraged to also gain access to other authentication systems e.g. "Forgot password" feature. You can suggest the installation of a SSL proxy for those holdouts that won't switch mail readers (stunnel even has support down to Win98). https://www.stunnel.org/ports.html These days, cleartext passwords over the network is just begging to be compromised. Joseph Tam <jtam.home(a)gmail.com>

1 0

Re: [Dovecot] ImapTest utility not compiling
by Hein, Brad 23 Apr '14

23 Apr '14

* Found my error. I moved the dovecot source code after compiling it. Didn’t realize there were embedded/absolute URLS within the dovecot source tree. All I needed to do was make clean && make dovecot, then imaptest compiled no problem. [Brad Hein] From: <Hein>, Local Administrator <Brad_Hein(a)cable.comcast.com<mailto:Brad_Hein@cable.comcast.com>> Date: Wednesday, April 23, 2014 at 2:00 PM To: "dovecot(a)dovecot.org<mailto:dovecot@dovecot.org>" <dovecot(a)dovecot.org<mailto:dovecot@dovecot.org>> Subject: ImapTest utility not compiling Following the wiki instructions here: http://www.imapwiki.org/ImapTest/Installation I’ve run into a wall trying to compile the imapTest utility (dovecot compiled without any problems). I think there’s a problem in the imapTest utility? Copy/pasted compile output and attached. The gist of the problem seems to be that imaptest can’t find the dovecot headers and libraries (configure script was executed like this: ./configure --with-dovecot=/usr/src/dovecot-20140420 checkpoint.c:3:17: error: lib.h: No such file or directory checkpoint.c:4:17: error: str.h: No such file or directory <and many more> Based on these errors I believe there’s a compatibility problem between the current imapTest utility and dovecot. The configure script said to report errors to this email address. [Brad Hein]

1 0