- dovecot - dovecot.org

[Dovecot] Enable IMAP only for certain users/IP
by Simone Marx :: Edinet Srl 29 May '13

29 May '13

Hi, I'm trying to config dovecot to enable IMAP protocol only for certain IPs and users. The logical steps I've followed are: 1. If a user is trying to login from an IP that I've authorized ( listed in a file) the request is authorized. 2. If not, if the user is listed in a second file the request is authorized. 3. If also this check fails the request is rejected. I'm using PAM for passdb and a passwd-file for userdb: passdb { driver = pam args = session=yes failure_show_msg=yes max_requests=16 cache_key=%u%r%l dovecot-%s } userdb { driver = passwd-file args = /etc/passwd-dovecot } In /etc/pam.d/ there are two files: dovecot-pop3 dovecot-imap dovecot-pop3: #%PAM-1.0 @include common-auth @include common-account @include common-session (for this protocol everything works fine, I don't want to limit it.) dovecot-imap: #%PAM-1.0 @include common-auth auth sufficient pam_listfile.so item=rhost sense=allow file=/etc/dovecot/imaphosts onerr=fail auth required pam_listfile.so item=user sense=allow file=/etc/dovecot/imapusers onerr=fail @include common-account @include common-session If I'm not wrong, once the user is authenticated, PAM checks if the remote IP address is in imaphosts; if it's true, it returns PAM_SUCCESS and stops the execution of the auth block, else if it's false, PAM executes the next line, verifying the presence of the username in imapusers file; if found, then return PAM_SUCCESS, else fail. If this can work, I've a problem with pam_listfile.so and IP addresses: I want to do something smarter than specifying 2^11 IP addresses instead a /21 or IP/netmask Are there alternatives for doing it better? Thanks. Sincerely, Simone Marx.

2 4

[Dovecot] Corrupt index file zlib
by Paul Lim 29 May '13

29 May '13

Hi, I'm getting this error constantly on a couple of folders. No matter what I do it keeps recurring. -- 2013-05-29 14:15:03 imap(nj(a)***.com.au): Error: Cached message size smaller than expected (2551 < 8192) 2013-05-29 14:15:03 imap(nj(a)***.com.au): Error: Maildir filename has wrong S value, renamed the file from /home/***.com.au/nj/.***.Builders/cur/1369030267.M775209P12595.pygmy,S= /2551:2,S to /home/***.com.au/nj/.***.Builders/cur/1369030267.M775209P12595.pygmy,S= /2551:2,S 2013-05-29 14:15:03 imap(nj(a)***.com.au): Error: Corrupted index cache file /home/archarch.com.au/nj/.***.Builders/dovecot.index.cache: Broken /physical size for mail UID 13 2013-05-29 14:15:03 imap(nj(a)***.com.au): Error: Cached message size smaller than expected (2551 < 8284) 2013-05-29 14:15:03 imap(nj(a)***.com.au): Error: Maildir filename has wrong S value, renamed the file from /home/***.com.au/nj/.***.Builders/cur/1369030267.M775209P12595.pygmy,S= /2551:2,S to /home/***.com.au/nj/.***.Builders/cur/1369030267.M775209P12595.pygmy,S= /2551:2,S 2013-05-29 14:15:03 imap(nj(a)***.com.au): Error: Corrupted index cache file /home/archarch.com.au/nj/.***.Builders/dovecot.index.cache: Broken /physical size for mail UID 13 2013-05-29 14:15:03 imap(nj(a)***.com.au): Error: read(/home/***.com.au/nj/.***.Builders/cur/1369030267.M775209P12595. pygmy,S=2551:2,S) failed: Input/output error (uid=13) --- stuff I've done: - Deleted dovecot* in .Builders/ - run maildir-size-fix.pl -v -r -f- c on .Builders/ - delete and recreate the folder Dovecot 2.1.7 (wheezy) zlib enabled maildir_broken_filename_sizes = yes There are only 6 emails, so it's only building dovecot.index.log, not the cache file --- dovecot-uidlist --- 3 V1317717759 N1 G1b2d4a37936fa551430d0000c0318918 1 :1369030267.M775209P12595.pygmy,S=8284 2 :1369030564.M957106P12595.pygmy,S=13188 3 :1369030568.M223636P12595.pygmy,S=23270 4 :1369030568.M223637P12595.pygmy,S=10813 5 :1369030568.M223638P12595.pygmy,S=58600 6 :1369030615.M783237P12595.pygmy,S=9677 7 :1369030267.M775209P12595.pygmy,S=2551 8 :1369030564.M957106P12595.pygmy,S=3560 ----- --- ls cur --- 1369030267.M775209P12595.pygmy,S=8284:2,S 1369030564.M957106P12595.pygmy,S=13188:2,RS 1369030568.M223636P12595.pygmy,S=23270:2,RS 1369030568.M223637P12595.pygmy,S=10813:2,RS 1369030568.M223638P12595.pygmy,S=58600:2,RS 1369030615.M783237P12595.pygmy,S=9677:2,RS ---- It all seems to match... but it continues to break. If I delete the first email file, it breaks on the next one as well. Any thoughts?? I'm thinking I'll probably disable zlib if I can't find a solution... will this mean I have to decompress all the compressed emails? cheers Paul

2 3

[Dovecot] Dovecot 2.1.7-7 only allow localhost access to IMAP and POP3
by Torben Schou Jensen 29 May '13

29 May '13

Recently I have upgraded my server to Debian 7. Debian have now removed uw-imapd and suggest using dovecot instead. Debian include dovecot version 2.1.7-7. On http://www.debian-administration.org/articles/275 and http://www.debian-administration.org/articles/200 I can read how to setup older version of dovecot with SquirrelMail. They recommend to use uncrypted IMAP when SquirrelMail is on same server. What I would like to support is then imap, imaps, pop3 and pop3s. imaps and pop3s for external users. imap and pop3 only open for localhost, that is SquirrelMail on same machine. With dovecot 1 you could restrict access using "imap_listen = localhost" How do I make the same restriction with localhost on dovecot 2 ??? Brgds Torben

3 2

[Dovecot] dsync Panic: Unknown key: send_mail_requests
by Oli Schacher 29 May '13

29 May '13

Hi Timo With the current dovecot hg we're getting dsync replication errors "Panic: Unknown key: send_mail_requests" followed by a crash. This seems to have been introduced somewhere around http://hg.dovecot.org/dovecot-2.2/rev/4883a8e1db13 Log output from latest hg, 2.2.2 (e7c474011934+): May 29 09:30:53 munged03 dovecot: doveadm(luke(a)example.com): Panic: Unknown key: send_mail_requests May 29 09:30:53 munged03 dovecot: doveadm(luke(a)example.com): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x5f7da) [0x7f84f84637da] -> /usr/lib64/dovecot/libdovecot.so.0(+0x5f826) [0x7f84f8463826] -> /usr/lib64/dovecot/libdovecot.so.0(+0x2006a) [0x7f84f842406a] -> dovecot/doveadm-server() [0x42c41b] -> dovecot/doveadm-server() [0x42908b] -> dovecot/doveadm-server(dsync_brain_master_init+0x1c9) [0x4186f9] -> dovecot/doveadm-server() [0x416606] -> dovecot/doveadm-server() [0x40c94f] -> dovecot/doveadm-server() [0x414b7a] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f84f8472b66] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0xa7) [0x7f84f8473c17] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7f84f8472b08] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f84f8428ae3] -> dovecot/doveadm-server(main+0x121) [0x4152c1] -> /lib64/libc.so.6(__libc_start_main+0xfd) [0x34de41ecdd] -> dovecot/doveadm-server() [0x40c1b9] May 29 09:30:53 munged03 dovecot: doveadm(luke(a)example.com): Fatal: master: service(doveadm): child 49077 killed with signal 6 (core dumped) dovecot -n is attached Best regards Oli -- message transmitted on 100% recycled electrons

2 1

[Dovecot] Email migration
by Romer Ventura 29 May '13

29 May '13

Hello, So I am currently running dovecot 1.2.11 on Debian 5 for our production email systems. We just deployed some new Debian 7 servers and we will be upgrading to the latest dovecot version. I've been reading the docs, but I wanted to heard some feedback on the import of all my current email into the new installation. We have 320GB worth of email. Any gotchas I should be prepared for? Any complications I should be aware of when importing all these data? Any thoughts would be appreciated. Thanks. <BR CLEAR="ALL"> <hr style="border: 1px solid #CCC;"> <p style="font-style:italic; font-size:8pt; font-family:verdana; color:gray;">This document and attachments may contain technical data controlled under the U.S. International Traffic in Arms Regulations (ITAR) or the Export Administration Regulations (EAR) and may not be exported to a Foreign Person, either in the U.S. or abroad, without the proper authorization by the U.S. Department of State or Department of Commerce, whichever is applicable. CONFIDENTIALITY NOTE: This electronic transmission, including all attachments, is directed in confidence solely to the person(s) to whom it is addressed, or an authorized recipient, and may not otherwise be distributed, copied or disclosed. The contents of the transmission may also be subject to intellectual property rights and such rights are expressly claimed and are not waived. If you have received this transmission in error, please notify the sender immediately by return electronic transmission and then immediately delete this transmission, including all attachments, without copying, distributing or disclosing same. The recipient should check this e-mail and any attachments for the presence of viruses. Houston Sigma Technologies L.P. accepts no liability for any damage caused by any virus transmitted by this e-mail.</p>

2 1

[Dovecot] system account delivery userdb authentication
by Yann Shukor 29 May '13

29 May '13

Hi I have a remaining issue with a mail server setup. Composed of Postfix and Dovecot it is is a 'local' mail server At first I relied upon Mysql to store the various parameters, and then switched to a flat file approach I also initially set the server up to handle virtual users, but then I realized that it was destined to manage local system accounts only. So I reconfigured it accordingly Relying on system accounts for authentication means that the domain name component is absent from the username (as opposed to virtual user identifiers) This caused me some difficulty at first with roundcube, but I was able to get around it through a manual adjustment in Mysql The remaining aspect that isn't working is the delivery of emails. The entry in master.cf for dovecot looks looks this: dovecot unix - n n - - pipe flags=DRhu user=mail:mail argv=/usr/lib/dovecot/deli ver -d ${recipient} The problem is that the recipient equates to the users email address, which can't in fact be used for authentication purposes with system accounts. I then tried replacing recipient with user: dovecot unix - n n - - pipe flags=DRhu user=mail:mail argv=/usr/lib/dovecot/deliver -d ${user} There seems to be a rights issue because I get the following error: dovecot Fatal: setgid(100(users)) failed with euid=8(mail), gid=8(mail), egid=8(mail): Operation not permitted Any ideas ? thanks yann # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686 i686 Debian 6.0.7 ext4 log_timestamp: %d-%m-%Y %H:%M:%S protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/ssl/certs/postfix.pem ssl_key_file: /etc/ssl/private/postfix.key login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_privileged_group: mail mail_location: maildir:/var/mail/%u mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 lda: auth_socket_path: /var/run/dovecot/auth-master postmaster_address: postmaster(a)holinice.com mail_plugins: sieve log_path: syslog_facility: mail auth default: mechanisms: plain login verbose: yes passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: mail group: mail

2 1

[Dovecot] dovecot + virtio (9p2000.L) = errors
by epek＠gmx.net 28 May '13

28 May '13

Hi! I hope someone knows more about the issues I've encountered in: Setup: I am running dovecot 2.1.7 on Debian Wheezy in a virtual machine (kvm-style qemu-kvm: host: ubuntu 13.04/1.4.0-dfsg-1expubuntu). The mail storage is a directory on the host machine mounted via virtfs (9p2000.L) on the guest. Furthermore ISPConfig is involved in that setup, but that should not make any significant difference at that point. Problem resolved: The problem is, that similar to nfs mmap() and dotlocking seem to fail - the mmap issue could be resolved by adding: mmap_disable=yes to dovecot.conf Problem remaining: Still the following errors remain, despite dotlock_use_excl=no May 27 12:54:51 host dovecot: imap(test@mydomain): Error: fstat(/var/vmail/mydomain/test/.quotausage.lock) failed: No such file or directory May 27 12:54:51 host dovecot: imap(test@mydomain): Error: file dict commit: file_dotlock_open(/var/vmail/mydomain/test/.quotausage) failed: No such file or directory May 27 12:54:51 host dovecot: imap(test@mydomain): Error: fstat(/var/vmail/mydomain/test/Maildir/dovecot-uidlist.lock) failed: No such file or directory May 27 12:54:51 host dovecot: imap(test@mydomain): Error: fstat(/var/vmail/mydomain/test/Maildir/dovecot-uidlist.lock) failed: No such file or directory May 27 12:54:51 host dovecot: imap(test@mydomain): Error: fstat(/var/vmail/mydomain/test/Maildir/dovecot-uidlist.lock) failed: No such file or directory May 27 12:54:51 host dovecot: imap(test@mydomain): Error: fstat(/var/vmail/mydomain/test/Maildir/dovecot-uidlist.lock) failed: No such file or directory May 27 12:54:51 host dovecot: imap(test@mydomain): Error: fstat(/var/vmail/mydomain/test/Maildir/dovecot-uidlist.lock) failed: No such file or directory May 27 12:54:51 host dovecot: imap(test@mydomain): Error: fstat(/var/vmail/mydomain/test/Maildir/dovecot-uidlist.lock) failed: No such file or directory May 27 12:54:52 host dovecot: imap(test@mydomain): Error: fstat(/var/vmail/mydomain/test/Maildir/dovecot-uidlist.lock) failed: No such file or directory May 27 12:54:52 host dovecot: imap(test@mydomain): Error: file_dotlock_create(/var/vmail/mydomain/test/Maildir/dovecot-uidlist) failed: No such file or directory May 27 12:54:52 host dovecot: imap(test@mydomain): Error: fstat(/var/vmail/mydomain/test/Maildir/dovecot-uidlist.lock) failed: No such file or directory May 27 12:54:52 host dovecot: imap(test@mydomain): Error: fstat(/var/vmail/mydomain/test/Maildir/dovecot-uidlist.lock) failed: No such file or directory May 27 12:54:52 host dovecot: imap(test@mydomain): Error: file_dotlock_create(/var/vmail/mydomain/test/Maildir/dovecot-uidlist) failed: No such file or directory The "failed" files are existing on that path - permissions for the configured "vmail" user and group exist (0600). I'd be greatful for any hint on how to resolve that issue - Thanks in advance! Regards Erich

1 0

[Dovecot] put users's mailbox in read only mode
by Frank Bonnet 28 May '13

28 May '13

Hello For internal purpose I need to put some users's mailboxes and IMAP folders in read only mode during few days. We use MBOX format and UNIX real users mode ( FreeBSD 9.1 ) thanks for any info

2 1

[Dovecot] UIDLs problem on migration to dovecot
by Oscar A. Jara 27 May '13

27 May '13

Hello list, I'm about to migrate from Courier 4.6 (POP and IMAP) to Dovecot 1.2. I am currently trying to match UIDLs of both servers to avoid redownload of mails but I could not success. I've already configured dovecot POP3 to format UIDLs like this: pop3_uidl_format = UID%u-%v I also executed the script 'courier-dovecot-migrate.pl' to do the migration in a couple of test accounts but the IDs don't match for all mails and the script didn't report any errors. I have production courier pop3 server running on port 110 and the new dovecot server running on another port. Here I paste some of the missmatches in one of the test accounts: 8827 UID9060-1259354075 | 8827 UID9041-1259354075 8828 UID9061-1259354075 | 8828 UID9023-1259354075 8829 UID9062-1259354075 | 8829 UID9067-1259354075 8830 UID9063-1259354075 | 8830 UID9064-1259354075 8831 UID9064-1259354075 | 8831 UID9043-1259354075 8832 UID9065-1259354075 | 8832 UID9061-1259354075 8833 UID9066-1259354075 | 8833 UID9025-1259354075 8834 UID9067-1259354075 | 8834 UID9047-1259354075 One thing that I don't know if is important is that I am using dovecot-lda since long ago, not courier lda. I don't know what I am missing here and I would appreciate some help. Thank you. __________ Information from ESET Mail Security, version of virus signature database 8381 (20130527) __________ The message was checked by ESET Mail Security. http://www.eset.com

1 0

[Dovecot] Problem with dsync replication : mails are not deleted correctly
by Nicolas ROCHE 27 May '13

27 May '13

Hello, I would like to configure a postfix / dovecot cluster based on ssh / dsync replication. I have two linux serveurs (Oracle RHEL 5 86_64) and I install both sides dovecot (V2.2.2+), postfix (2.10.0) and mysql (Ver 14.12 Distrib 5.0.77). I configured these servers in order to make them replicate, and I created some virtual users. I use some java code in order to send mail (with SMTP) and to get mail (with POP3). When the java code get a mail, it deletes it from mailbox (the flag "DELETED" is set to true). When I send a mail on server A, I can see the mail replicated on both servers A and B : a file containing the message data exists in /home/vmail/test03/new/ in both sides. When I get the mail from server A with my java POP3 client, all is OK : the mail is deleted on both servers A and B (no more file in /home/vmail/test03/new/). The problem is when I send a mail on server A and I get it from server B : I can get the mail, but the mail is not deleted from server B, and neither from server A. When I try a second time to get the mail on server B, then all becomes OK : the mail is deleted on both server A and B. I can reproduce the problem every time. Is it a known bug or not ? If yes, is there a patch ? If no, may the problem come from my config ? Regards, Nicolas. [root@int-proxy1 dovecot-2.2.2-p1]# doveconf -n # 2.2.2: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-194.el5xen x86_64 Red Hat Enterprise Linux Server release 5.5 (Tikanga) ext3 disable_plaintext_auth = no hostname = int-proxy1 mail_location = maildir:/home/vmail/%u mail_plugins = acl quota notify replication mail_privileged_group = mail mbox_write_locks = fcntl 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 { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } plugin { mail_replica = remote:vmail@int-proxy2 replication_full_sync_interval = 1 hours } pop3_uidl_format = %g postmaster_address = postmaster(a)mail.fluid-e.int service aggregator { fifo_listener replication-notify-fifo { mode = 0666 user = vmail } unix_listener replication-notify { mode = 0666 user = vmail } } service auth-worker { user = root } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0666 user = vmail } user = root } service config { unix_listener config { user = vmail } } service doveadm { user = vmail } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service replicator { process_min_avail = 1 } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem submission_host = int-proxy1:25 userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf driver = sql } protocol imap { mail_plugins = acl quota imap_acl imap_quota mail_log notify }

3 6