- dovecot - dovecot.org

[Dovecot] [PATCH] Add SCRAM-SHA-1 password scheme
by Florian Zeitz 03 Oct '12

03 Oct '12

Hello, attached is an hg export on top of the current dovecot-2.2 branch, which adds support for a SCRAM-SHA-1 password scheme. Ideally I'd want doveadm pw's rounds flag to apply to this, but that's currently specific to the crypt password scheme, so I left it out for now. Regards, Florian Zeitz

2 9

[Dovecot] Syntax for doveadm auth cache
by Angel L. Mateo 03 Oct '12

03 Oct '12

Hello, What is the correct syntax of doveadm auth cache command? According to command line help: usage: doveadm [-Dv] [-f <formatter>] <command> [<args>] altmove [-u <user>|-A] [-S <socket_path>] [-r] <search query> auth [-a <auth socket path>] [-x <auth info>] <user> [<password>] auth cache but when I try to run doveadm auth cache, then I'm asked for a password, so I think the command is trying to authenticate cache user. Moreover... according to previous mails (thread http://www.dovecot.org/list/dovecot/2012-June/066691.html) there is a patch to remove a specific user entry from cache. This patch I think is included in dovecot 2.1.9 (which I'm running) and the syntax is (I think): doveadm auth cache flush <user> 4 cache entries flushed So I'm running this command. Whenever I run it, I get the message that 3 (sometimes, is 4) entries are removed, but user information isn't really reloaded and I doubt it is really removed from cache (I have the user in a passwd-file and information used by imap processes is still the old one, no the new one, changed before the flush) -- Angel L. Mateo Martínez Sección de Telemática Área de Tecnologías de la Información y las Comunicaciones Aplicadas (ATICA) http://www.um.es/atica Tfo: 868887590 Fax: 868888337

2 9

Re: [Dovecot] Logging IP address for failed login
by Joseph Tam 03 Oct '12

03 Oct '12

Scott Neville <dovecot-in(a)keystealth.org> writes: > I am trying to use the logs to show the IP that brute force activity > comes from, but Im not succeeding. I have read the archives and seen > the advice others have had. I can see logs for repeated bad logins, > but I need the IP address from the attempts. > > ... > but only for successful logins. The brute force attempts dont log like that: > > Sep 16 00:02:58 olive dovecot: auth: pam(backup): unknown user This was similar to another complaint several months ago. I conjectured that these attempts are SMTP AUTH, not IMAP, brute forcing. Are you using the dovecot's SASL feature to authenticate outgoing Email (i.e. via Postfix?). Maybe you verify this hypothesis by checking the Postfix logs. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] segfault in Debian Squeeze + Dovecot 2.1.10
by Joe Auty 03 Oct '12

03 Oct '12

Hello, I'm seeing a lot of these in my /var/log/messages in Debian Squeeze, I suspect this might be causing performance issues. Any suggestions what I can try to fix this? > [7236671.301179] imap-login[9306]: segfault at 28 ip 00007f9ff83c7e14 > sp 00007fff49d385c0 error 4 in libdovecot.so.0.0.0[7f9ff837c000+8b000] I'm using the 2.1.10 packages obtained with the following in my sources.list: deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.1 main I need to use Dovecot 2.1.x because I need to support handling multiple SSL certs.

7 25

[Dovecot] Spurious " Renaming not supported across conflicting directory permissions"
by tlhackque 02 Oct '12

02 Oct '12

Dovecot 2.1.10 Client = Thunderbird. Local disks. mbox format. Attempted to rename a folder, failed with: CANNOT Renaming not supported across conflicting directory permissions I don't understand why this should happen. o I was renaming within a directory - the attempt was to rename "Domain Names &- SSL Certificates" to "Domain Names". No directory was specified o The reason the directory has g=s is for dovecot - so that the 'mail' group (12) will stick to any files created. I was getting more understandable permission failures before I added it. Since 's' doesn't apply to files, I don't see why this should be viewed as a conflict. o If I chmod g-s the directory, the command succeeds. But then I'm back to file ownership problems... drwxrws--- 4 4503 12 4096 Sep 22 06:17 F/N/ -rw-rw---- 1 4503 12 81530 Sep 22 06:17 F/N/Domain Names &- SSL Certificates Sequence from TB's trace (crlfs for clarity): 1140[11ebcf00]: 121e8c00:imap.example.com:A:SendData: 66 rename "F/N/Domain Names &- SSL Certificates" "F/N/Domain Names" 1140[11ebcf00]: ReadNextLine [stream=12135a28 nb=80 needmore=0] 1140[11ebcf00]: 121e8c00:imap.example.com:A:CreateNewLineFromSocket: 66 NO [CANNOT] Renaming not supported across conflicting directory permissions 9592[c7d6840]: ReadNextLine [stream=ab687e8 nb=22 needmore=0] Config: # 2.1.10: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.22.14-72.fc6 i686 Fedora Core release 6 (Zod) first_valid_gid = 4000 first_valid_uid = 4000 hostname = smtp.example.com login_greeting = Dovecot ready. Unauthorized access is prohibited. mail_location = mbox:~/mail:INBOX=/var/mail/%n mail_privileged_group = mail 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 = separator = / } passdb { driver = pam } service imap-login { inet_listener imap { address = imap.v4.example.com imap.v6.example.com port = 143 } inet_listener imaps { address = imap.v4.example.com imap.v6.example.com port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { address = pop.v4.example.com pop.v6.example.com port = 110 } inet_listener pop3s { address = pop.v4.example.com pop.v6.example.com port = 995 ssl = yes } } ssl_ca = </etc/pki/tls/certs/example_com_ca-cert-crl.pem ssl_cert = </etc/pki/tls/certs/servers-example-com.pem ssl_key = </etc/pki/tls/private/servers-example-com.pmk userdb { driver = passwd } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep tb-lsub-flags } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } -- --------------------------------------------------------- This communication may not represent my employer's views, if any, on the matters discussed.

2 1

[Dovecot] noisy auth-worker messages in logs (dovecot 2.1.8 FreeBSD)
by Philippe Chevalier 02 Oct '12

02 Oct '12

Hello, I don't know if it's been addressed before, but anyway : In my dovecot setup, I have local and virtual users. So, I need multiple passdb backends. Namely, passwd for the local users and ldap for the virtual users. passdb { driver = passwd } passdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf driver = ldap } Everything work correctly : when a user logs in (imap/pop3) there's a lookup in passwd and if it fails there's a lookup in ldap (if I understand the process correctly), which eventually succeeds. Except that every time a virtual user logs in, dovecot logs an error, like : dovecot: auth-worker(99126): Error: passwd(xxx(a)domain.org,12.34.254.255): getpwnam() failed: Invalid argument I guess it's because the login is a full email that getpwnam fails. Anyway, the user logs in just fine. But I would like to know if/how I can get rid of the messages filling my logs ? I tried : auth_debug_passwords = no auth_verbose = no But no dice. I used dovecot 1.x before and there was no such messages. Thanks for any advice. K. -- Kyoko Otonashi's shrine / Le temple de Kyoko Otonashi My tribute to Maison Ikkoku / Mon hommage a Maison Ikkoku Visit http://www.kyoko.org/

2 4

[Dovecot] LTMP Proxy fails when backend server connection refused
by Jack Bates 02 Oct '12

02 Oct '12

Version: 2.1.9 Connecting directly to the proxy server on the LMTP port, issue lhlo, mail from, rcpt to, data. After the . closing of data, it just hangs there. The logs on the proxy server show: Sep 27 19:55:12 proxy1 dovecot: lmtp(9398): Connect from 69.8.2.71 Sep 27 19:55:24 proxy1 dovecot: lmtp(9398): Error: lmtp client: connect(lmtp, 7025) failed: Connection refused root 9398 1102 0 19:53 ? 00:00:00 dovecot/lmtp The proxy server is hard coded (not director in this case). I purposefully shut it down to see how the system would handle failures. Unfortunately, it appears that the process just hangs there. For fun, I tried a separate protocol lmtp option in the config to try proxy_timeout. It made no difference. Missing some error handling? protocol lmtp { passdb { driver = static args = proxy=y host=%s nopassword=y proxy_timeout=120 } } Jack

2 5

[Dovecot] Antispam plugin problem (CRM114)
by Davide 02 Oct '12

02 Oct '12

Hi to all, sorry in advance for my poor english, this is the first time that i wrote to a list if i make mistake .... excuseme. My problem is this: i have dovecot 2.1.8 installed and functioning from 2 years one week ago i have installed crm114 for my last spam detection filter "version 20100106-BlameMichelson (TRE 0.8.0 (BSD))" My mail system is qmail that through .qmail default correctly tag with X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-27CA1CFB X-CRM114-CacheID: sfid-20120927_105129_798028_B0035817 X-CRM114-Status: GOOD ( 28.64 ) headers dovecot.conf is as follow: plugin { . . . antispam_signature = X-CRM114-CacheID antispam_verbose_debug = 1 antispam_debug_target = stderr antispam_backend = crm114 antispam_signature_missing = error antispam_trash = Trash antispam_spam = SPAM antispam_unsure = UNSURE antispam_crm_binary = /opt/crm114/mailreaver.crm antispam_crm_args = --fileprefix=/opt/crm114/ . . . } protocol imap { . . . mail_plugin_dir = /usr/local/lib/dovecot mail_plugins = $mail_plugins quota imap_quota mail_log antispam . . . } I have a sieve default compiled script that automatically put mails in SPAM folder or UNSURE folder if respectively in message hedere there is the evaluation of crm114 (UNSURE or SPAM). When i move mails incorrectly tagged by crm (for example from SPAM to my inbox or from UNSURE to SPAM) thunderbird (company official mail client ver 15.01) go in error with the following message: "Operation failed over folder 'UNSURE'. Server for account davide.marchi(a)mail.cgilfe.it said: [CANNOT] Failed to call crm114 binary.." I dont'know where is my mistake if someone can help me is much appreciated Thank you -- */Davide Marchi /Teorema Ferrara Srl /(Tel: /**/+39 0532 783161)/**/ (Fax: +/**/39 0532 783368/**/)/**//**/ /**//**/Davide.Marchi(a)mail.cgilfe.it <mailto:davide.marchi@mail.cgilfe.it?subject=Info> /CONFIDENZIALITA’ *** Questo messaggio, inclusi gli eventuali allegati, è indirizzato solo ai destinatari e può contenere informazioni riservate e confidenziali. Se avete ricevuto il messaggio senza esserne un destinatario, siete pregati di non utilizzare, copiare o distribuire questo messaggio o i suoi allegati. Se avete ricevuto il messaggio per errore, siete pregati di cancellarlo dal vostro sistema, assieme a tutti gli allegati, e di informare immediatamente il mittente,sia ai sensi dell'art. 616 c.p., sia ai sensi del DL n. 196/03. *CONFIDENTIALITY*** This message and any attachments are intended only for the use of the addressee(s) and may contain information that is privileged and/or confidential. If the reader of the message is not the intended recipient(s) or an authorized representative of the intended recipient(s), please do not use, copy, distribute this email or its attachments or take action based on them. If you have received this communication in error, please notify us immediately by email and delete the message and any attachments from your system. *Teorema FerraraSrl - Via Spronello, 7 - 44121 Ferrara Italia - P. IVA 01244490387** P**S**tampa questo messaggio solo se veramente necessario, pensa alla natura! - Please consider whether it is necessary to print this e-mail*

2 17

[Dovecot] BUG to compile dovecot 2.1.10 on Debian 4.0, using gcc 4.1.2
by Fabio Depin 02 Oct '12

02 Oct '12

Hello, Today I needed to compile dovecot 2.1.10 on Debian 4.0, using gcc 4.1.2. When running 'make' getting the following error: -------------------------------------------------- -------- db-checkpassword.c: In function 'sigchld_handler': db-checkpassword.c: 426: error: assignment of read-only member '__in' db-checkpassword.c: 429: error: assignment of read-only member '__in' db-checkpassword.c: 431: error: assignment of read-only member '__in' db-checkpassword.c: 432: error: assignment of read-only member '__in' make [3]: ** [db-checkpassword.o] Error 1 make [3]: ** Waiting for other processes to finish. mv-f .deps / auth-worker-server.Tpo .deps / auth-worker-server.Po make [3]: Leaving directory `/ usr/src/dovecot/dovecot-2.1.7/src/auth ' make [2]: ** [all-recursive] Error 1 make [2]: Leaving directory `/ usr/src/dovecot/dovecot-2.1.7/src ' make [1]: ** [all-recursive] Error 1 make [1]: Leaving directory `/ usr/src/dovecot/dovecot-2.1.7 ' make: ** [all] Error 2 -------------------------------------------------- -------- -To work did the following: -------------------------------------------------- -------- 417a418 + Int stat = status-> status; 426c427 - If (WIFSIGNALED (status-> status)) { --- + If (WIFSIGNALED (stat)) { 429c430 - Dec2str (status-> pid), WTERMSIG (status-> status)); --- + Dec2str (status-> pid), WTERMSIG (stat)); 431.432 c432, 433 -} Else if (WIFEXITED (status-> status)) { - Request-> exit_status WEXITSTATUS = (status-> status); --- +} Else if (WIFEXITED (stat)) { + Request-> exit_status WEXITSTATUS = (stat); -------------------------------------------------- -------- With this change worked perfectly ntanto in debian 4 with gcc 4.1.2, as in debian 6 with gcc 4.4.5. -I wonder if I made the change may affect any function of dovecot, or if it is correct. Thank you for your attention. Fabio Depin

2 1

[Dovecot] Logging IP address for failed login
by Scott Neville 02 Oct '12

02 Oct '12

Hi, I am trying to use the logs to show the IP that brute force activity comes from, but Im not succeeding. I have read the archives and seen the advice others have had. I can see logs for repeated bad logins, but I need the IP address from the attempts. dovecot 2.0.12 / CentOS 5.4 / imaps only (993) I have tried a bunch of different combinations of 10-logging.conf settings. This is what I have currently (that does not work the way I want): auth_verbose = yes #auth_verbose_passwords = no #auth_debug = yes #auth_debug_passwords = no #mail_debug = no I *dont* want to see the passwords, either failed or successful. I just want to see failed logins for whatever reason and the IP they came from. In /var/log/maillog I get lines like this: Oct 1 04:19:12 olive dovecot: auth: pam(marketing): unknown user Oct 1 04:19:17 olive dovecot: auth: pam(marketing): unknown user When i had debugging turned on, I would get lines like this: Sep 9 01:14:59 olive dovecot: auth: Debug: passwd(dbelan,62.128.300.94): lookup but only for successful logins. The brute force attempts dont log like that: Sep 16 00:02:57 olive dovecot: auth: Debug: pam(backup): lookup service=dovecot Sep 16 00:02:57 olive dovecot: auth: Debug: pam(backup): lookup service=dovecot Sep 16 00:02:57 olive dovecot: auth: Debug: pam(backup): #1/1 style=1 msg=Password: Sep 16 00:02:57 olive dovecot: auth: Debug: pam(backup): #1/1 style=1 msg=Password: Sep 16 00:02:57 olive dovecot: auth: Debug: pam(backup): lookup service=dovecot Sep 16 00:02:57 olive dovecot: auth: Debug: pam(backup): #1/1 style=1 msg=Password: Sep 16 00:02:58 olive dovecot: auth: pam(backup): unknown user No IP anywhere in that. fail2ban seems to rely on the pop-login or imap-login lines to pull the IP from. I get an imap-login for my real logins: Oct 1 12:38:56 olive dovecot: imap-login: Login: user=<dbelan>, method=PLAIN, rip=62.128.300.94, lip=204.152.189.165, mpid=20360, TLS but no similar line for the failed logins. So is this a dovecot logging configuration combination I need to find? Is it getting lost in pam? Is it specific to CentOS? Any help appreciated - happy to read up on it myself, but would need a pointer, since the docs so far either assume I get an imap-login line for failed logins which I dont, or they assume I just want to see the repeated attempts/passwords. Scott.

2 1