- dovecot - dovecot.org

[Dovecot] bug formatting results when using doveadm-server
by Angel L. Mateo 04 Oct '12

04 Oct '12

Hello, I have a infrastructure using director in front of backend servers. So I normally run doveadm commands in director servers, not the backends. The problem I have is when I try to concatenate commands like this: doveadm search -S /var/run/dovecot/auth-userdb -u ${user} SAVEDSINCE 5w | while read guid uid; do doveadm fetch -S /var/run/dovecot/auth-userdb -u ${user} size.physical mailbox-guid $guid uid $uid; done The problem is that although when I run doveadm search command in the backend server I correctly get the list of mails, each line with the mailbox-guid and the uid of the message, when I run the same command in the director server, format of the list is corrupted and there are lines that contains just the mailbox-guid and the next the uid (of the previous) and the mailbox-guid of next, and so on. Like: e62e0d3834ed094e5c7900007efb8a67 66 e62e0d3834ed094e5c7900007efb8a67 71 e62e0d3834ed094e5c7900007efb8a67 74 e62e0d3834ed094e5c7900007efb8a67 75 e62e0d3834ed094e5c7900007efb8a67 77 e62e0d3834ed094e5c7900007efb8a67 78 e62e0d3834ed094e5c7900007efb8a67 so I can't postprocess correctly the output. I think it could be a bug in the communication between the doveadm client and server. PS: As the time of writing this email, I have realized that I could use fetch command directly. But, anyway, I want to report the problem/bug so it can be fixed.

2 6

[Dovecot] possible nfs issue
by Cor Bosman 04 Oct '12

04 Oct '12

Hi all, we've started receiving complaints from users that seemingly use more quota than they actually have. We noticed that these users have (in some cases many) .nfs files in their mailspool. Some of our admins checked their own dirs, and noticed them there as well. This could of course be unrelated to dovecot (kernel issue, netapp issue) but maybe somehow has an idea about if dovecot could cause this. This has been going on for at least a year, not really enough to notice before now. root@userimap1# find . -type f|grep -i .nfs ./cur/.nfs00000000003967ad003c0603 ./cur/.nfs000000000757b44b003be609 ./cur/.nfs00000000035e89bd003be60b ./cur/.nfs000000000796251c003be60c ./cur/.nfs000000000796251f003be60e ./cur/.nfs000000000262f9a1003be33a ./cur/.nfs00000000096513f3003be524 ./cur/.nfs0000000007962525003be60f ./cur/.nfs0000000003e7d8ab003be62b ./cur/.nfs00000000026f4fad003be50d ./cur/.nfs0000000000bdaeab003c0611 ./cur/.nfs0000000005da42c7003be525 ./cur/.nfs0000000003d74729003be526 ./cur/.nfs000000000229769e003be535 ./cur/.nfs000000000440969e003be516 With NFS these files are created when a file gets unlinked, but another process still has it open. It disappears as soon as the other process closes it. For some reason they dont disappear. As far as I can tell we've had no server crashes that could explain this. One possible theory is that a rename happens after an unlink. In that case the file remains. This could possibly be a dovecot issue. Anyone else with NFS mailspools seeing this? Cor

5 7

[Dovecot] LDA vs LMTP index files
by list＠airstreamcomm.net 03 Oct '12

03 Oct '12

In the docs it states that LDA " ...takes mail from anMTAand delivers it to a user's mailbox, while keeping Dovecot index files up to date." I am wondering if LMTP also interacts with the Dovecot index files and keeps them up to date?

3 3

[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 02 Oct '12

02 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 02 Oct '12

02 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