- dovecot - dovecot.org

[Dovecot] Store quota on passwd-file?? Not work
by Sébastien FOURCADE 28 Jul '11

28 Jul '11

Hello all, I have installed Dovecot 1.2.15 and Postfix 2.7.1 on my Debian 6.This install no include MySQL, I prefer to store Password/User in a file... File /etc/dovecot/passwd contains :user2@domain.com:{CRAM-MD5}::::userdb_mail=maildir:~/Maildir userdb_quota_rule=*:bytes=300M File /etc/dovecot/users :user2@domain.com::3000:3000::/home/vmail/domain.com/user2/:/bin/false:: What is the correct syntax for my file to use a different per-user quota ? This example not work on my Dovecot :user2@domain.com:{CRAM-MD5}:3000:3000::/home/vmail/domain.com/user2::userdb_mail=maildir:~/Maildir userdb_quota_rule=*:storage=200Muser2@domain.com:{CRAM-MD5}:3000:3000::/home/vmail/domain.com/user2::userdb_quota_rule=*:bytes=200M Thx.

2 2

[Dovecot] set delay between pop3-logins
by tonjg 28 Jul '11

28 Jul '11

I'm using dovecot 1.1.8 on a raq4 server running centos 4.8 Is it possible to set a time delay between all dovecot pop3-logins? say 20 - 30 seconds for example? My reason is I want to thwart the constant login attempts from hackers hunting for an open relay. It's no good blocking the ip address because every hack attempt comes in from a different address. I'm the only user on the server so no-one else would be affected by such a delay. Thanks for any pointers -- View this message in context: http://old.nabble.com/set-delay-between-pop3-logins-tp32134037p32134037.html Sent from the Dovecot mailing list archive at Nabble.com.

4 4

[Dovecot] lmtp multiple recipients fail
by flylordis flylordis 28 Jul '11

28 Jul '11

Hello, I am having a problem with the lmtp delivery of mail addressed to multiple recipients. The first recipient receives the mail correctly but the next recipients do not. ltmp apparently tries to create a link from the subsequent recipients' mail store to the first recipient mail store and fails. This returns 451 smtp codes to the sender which then resends at some later time. Please see below for users jerry, steve, and mary. The message to jerry gets written but not steve or mary: ul 27 11:24:41 testmailserver dovecot: lmtp(12412): Debug: none: root=, index=, control=, inbox= Jul 27 11:24:41 testmailserver dovecot: lmtp(12412): Connect from 143.112.53.4 Jul 27 11:24:41 testmailserver dovecot: lmtp(12412): Debug: auth input: jerry home=/spool/mail/j/jerry system_groups_user=jerry uid=18738 gid=4025 Jul 27 11:24:41 testmailserver dovecot: lmtp(12412): Debug: auth input: steve home=/spool/mail/s/steve system_groups_user=steve uid=9838 gid=3011 Jul 27 11:24:41 testmailserver dovecot: lmtp(12412): Debug: auth input: mary home=/spool/mail/m/mary system_groups_user=mary uid=7007 gid=3011 Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, jerry): Debug: Effective uid=18738, gid=4025, home=/spool/mail/j/jerry Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, jerry): Debug: fs: root=/spool/mail/j/jerry/mail, index=, control=, inbox=/spool/mail/j/jerry/mail/INBOX Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, jerry): Debug: Namespace : Permission lookup failed from /spool/mail/j/jerry/mail/mailboxes/INBOX Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, jerry): Debug: Namespace : Using permissions from /spool/mail/j/jerry/mail: mode=0700 gid=-1 Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, jerry): Debug: Namespace : Permission lookup failed from /spool/mail/j/jerry/mail/mailboxes/INBOX Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, jerry): Debug: Namespace : Using permissions from /spool/mail/j/jerry/mail: mode=0700 gid=-1 Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, jerry): Debug: Namespace : Permission lookup failed from /spool/mail/j/jerry/mail/mailboxes/INBOX Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, jerry): Debug: Namespace : Using permissions from /spool/mail/j/jerry/mail: mode=0700 gid=-1 Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, jerry): Debug: Namespace : Permission lookup failed from /spool/mail/j/jerry/mail/mailboxes/INBOX Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, jerry): Debug: Namespace : Using permissions from /spool/mail/j/jerry/mail: mode=0700 gid=-1 Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, jerry): +1IXBeVXME58MAAARoVNxQ: msgid=<201107271824.p6RIOPa5020900@backup.>: saved mail to INBOX Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, steve): Debug: Effective uid=9838, gid=3011, home=/spool/mail/s/steve Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, steve): Debug: fs: root=/spool/mail/s/steve/mail, index=, control=, inbox=/spool/mail/s/steve/mail/INBOX Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, steve): Debug: Namespace : Permission lookup failed from /spool/mail/s/steve/mail/mailboxes/INBOX Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, steve): Debug: Namespace : Using permissions from /spool/mail/s/steve/mail: mode=0700 gid=-1 Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, steve): Debug: Namespace : Permission lookup failed from /spool/mail/s/steve/mail/mailboxes/INBOX Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, steve): Debug: Namespace : Using permissions from /spool/mail/s/steve/mail: mode=0700 gid=-1 Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, steve): Debug: Namespace : Permission lookup failed from /spool/mail/s/steve/mail/mailboxes/INBOX Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, steve): Debug: Namespace : Using permissions from /spool/mail/s/steve/mail: mode=0700 gid=-1 Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, steve): Debug: Namespace : Permission lookup failed from /spool/mail/s/steve/mail/mailboxes/INBOX Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, steve): Debug: Namespace : Using permissions from /spool/mail/s/steve/mail: mode=0700 gid=-1 Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, steve): Error: link(/spool/mail/j/jerry/mail/INBOX/u.20423, /spool/mail/s/steve/mail/INBOX/.temp.1311791081.P12412Q2M989550.testmailserver.) failed: Permission denied Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, steve): +1IXBeVXME58MAAARoVNxQ: msgid=<201107271824.p6RIOPa5020900@backup.>: save failed to INBOX: Internal error occurred. Refer to server log for more information. [2011-07-27 11:24:41] Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, mary): Debug: Effective uid=7007, gid=3011, home=/spool/mail/m/mary Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, mary): Debug: fs: root=/spool/mail/m/mary/mail, index=, control=, inbox=/spool/mail/m/mary/mail/INBOX Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, mary): Debug: Namespace : Permission lookup failed from /spool/mail/m/mary/mail/mailboxes/INBOX Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, mary): Debug: Namespace : Using permissions from /spool/mail/m/mary/mail: mode=0700 gid=-1 Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, mary): Debug: Namespace : Permission lookup failed from /spool/mail/m/mary/mail/mailboxes/INBOX Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, mary): Debug: Namespace : Using permissions from /spool/mail/m/mary/mail: mode=0700 gid=-1 Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, mary): Debug: Namespace : Permission lookup failed from /spool/mail/m/mary/mail/mailboxes/INBOX Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, mary): Debug: Namespace : Using permissions from /spool/mail/m/mary/mail: mode=0700 gid=-1 Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, mary): Debug: Namespace : Permission lookup failed from /spool/mail/m/mary/mail/mailboxes/INBOX Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, mary): Debug: Namespace : Using permissions from /spool/mail/m/mary/mail: mode=0700 gid=-1 Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, mary): Error: link(/spool/mail/j/jerry/mail/INBOX/u.20423, /spool/mail/m/mary/mail/INBOX/.temp.1311791081.P12412Q3M989550.testmailserver.) failed: Permission denied Jul 27 11:24:42 testmailserver dovecot: lmtp(12412, mary): +1IXBeVXME58MAAARoVNxQ: msgid=<201107271824.p6RIOPa5020900@backup.>: save failed to INBOX: Internal error occurred. Refer to server log for more information. [2011-07-27 11:24:41] Jul 27 11:24:42 testmailserver dovecot: lmtp(12412): Disconnect from 143.112.53.4: Client quit Jul 27 11:24:42 testmailserver dovecot: lmtp(12412): Disconnect from 143.112.53.4: Client quit I am using version 2.0.13. dovecot -n shows this: # 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-71.29.1.el6.i686 i686 CentOS Linux release 6.0 (Final) ext4 auth_debug = yes auth_master_user_separator = * auth_verbose = yes auth_verbose_passwords = plain lda_mailbox_autocreate = yes mail_debug = yes mail_location = sdbox:/spool/mail/%1Ln/%Ln/mail:INBOX=/spool/mail/%1Ln/%Ln/mail/INBOX mbox_write_locks = fcntl passdb { args = /etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = failure_show_msg=yes driver = pam } plugin { autocreate = INBOX autosubscribe = INBOX } service lmtp { inet_listener ltmp { port = 24 } } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = home=/spool/mail/%1Ln/%Ln driver = passwd } protocol lmtp { mail_plugins = " autocreate" } Thanks for any pointers, -Boris Lordis

2 1

[Dovecot] Some messages appear twice
by Dominik Schulz 28 Jul '11

28 Jul '11

Hi, I'm using Dovecot 1.2.15 on Debian. On some clients, at least KMail, some messages (especially older ones) appear twice in the message list of the client. This is really annoying. Can anyone give me a hint on how to solve this issue? -- Best Regards, Dominik Schulz

1 0

[Dovecot] DIsctionnary flat file format for shared mailboxes ?
by Frank Bonnet 28 Jul '11

28 Jul '11

Hello I would be grateful if someone could send an example of a dictionnary flat file used by the shared mailboxes feature, it has very few here so a flat file will be enough I think. Thank you

1 0

[Dovecot] sieve on debian squeeze
by Andrea Ganduglia 28 Jul '11

28 Jul '11

Hi. I have a quite problem with dovecot and sieve on Debian Squeeze. I'm trying to enable sieve plugin into dovecot, but something is deeply wrong. I hope that this is the right place to give some help. There are no errors or warning messages, simply sieve don't works. For the big picture about my mail server you can follow this link http://www.linux-archive.org/debian-user/555576-postfix-virtual_transport-m… and here there is my specific request on Debian User List http://www.linux-archive.org/debian-user/557551-sieve-dovecot-squeeze-help.… here my dovecot -n output # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.1 ext3 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s lda disable_plaintext_auth: no 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 first_valid_uid: 102 mail_privileged_group: mail mail_location: maildir:/home/vmail/%d/%n 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: log_path: /var/vmail/dovecot-deliver.log postmaster_address: info(a)**********.it auth_socket_path: /var/run/dovecot/auth-master mail_plugins: cmusieve auth default: mechanisms: cram-md5 plain login debug: yes passdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: postfix plugin: sieve_global_path: /var/vmail/globalsieverc sieve_dir: ~/sieve sieve: ~/.dovecot.sieve sieve_global_dir: /var/vmail/sieve sieve_maxscriptsize: 128 Any suggestions? Thanks in advance! -Andrea

3 3

[Dovecot] Problem with client login in 1.2.17
by John O'Brien 27 Jul '11

27 Jul '11

Hi, I have been using CentOS 5.5 with Dovecot 1.0.7. My client apps login with TLS/SSL using an postgres database for username and password authentication. I developed a plugin that added an additional IMAP command. I want to eventually migrate to release 2.0 but have decided to make this a two step process. I have started with 1.2.17 as I hope this would be a smaller step along the way. I have installed 1.2.17 from source an installed. Rebuilt my plugin and installed and set about updating the dovecot.conf file. Installing the SSL certificate etc..... I have tested the 1.0.7 configuration previously using a standard IMAP mail client. When I try with 1.2.17 I can't seem to get logged in. ==> /var/log/maillog <== Jul 27 21:48:26 email dovecot: auth(default): client in: AUTH 1 PLAIN service=imap secured lip=192.168.1.10 rip=202.81.69.135 lport=10143 rport=58641 resp=ADYxNDE0NjI3NDM2AFExcjQwNHVD Jul 27 21:48:26 email dovecot: auth-worker(default): pam(john,202.81.69.135): lookup service=dovecot Jul 27 21:48:26 email dovecot: auth-worker(default): pam(john,202.81.69.135): #1/1 style=1 msg=Password: Jul 27 21:48:28 email dovecot: auth-worker(default): pam(john,202.81.69.135): unknown user Jul 27 21:48:28 email dovecot: auth(default): sql(john,202.81.69.135): query: SELECT password FROM ivms_iphone WHERE username='john' Jul 27 21:48:28 email dovecot: auth(default): client out: OK 1 user=john Jul 27 21:48:28 email dovecot: auth(default): master in: REQUEST 2 28178 1 Jul 27 21:48:28 email dovecot: auth(default): passwd(john,202.81.69.135): lookup Jul 27 21:48:28 email dovecot: auth(default): passwd(john,202.81.69.135): unknown user Jul 27 21:48:28 email dovecot: auth(default): sql(john,202.81.69.135): SELECT home, uid, gid FROM users WHERE username='john' Jul 27 21:48:28 email dovecot: auth(default): master out: USER 2 john home=/var/imap_mail/john uid=50gid=500 Jul 27 21:48:28 email dovecot: IMAP(john): Loading modules from directory: /usr/local/lib/dovecot/imap/ Jul 27 21:48:28 email dovecot: IMAP(john): Module loaded: /usr/local/lib/dovecot/imap//lib20_mail_log_plugin.so Jul 27 21:48:28 email dovecot: IMAP(john): Module loaded: /usr/local/lib/dovecot/imap//change_passwd_plugin.so Jul 27 21:48:28 email dovecot: IMAP(john): Effective uid=500, gid=500, home=/var/imap_mail/john Jul 27 21:48:28 email dovecot: IMAP(john): maildir: data=john Jul 27 21:48:28 email dovecot: IMAP(john): maildir++: root=john, index=, control=, inbox=john Jul 27 21:48:28 email dovecot: imap-login: Login: user=<john>, method=PLAIN, rip=202.81.69.135, lip=192.168.1.10, TLS Jul 27 21:48:28 email dovecot: IMAP(john): Namespace : Using permissions from john: mode=0700 gid=-1 ==> /var/log/secure <== Jul 27 21:48:26 email dovecot-auth: pam_unix(dovecot:auth): check pass; user unknown Jul 27 21:48:26 email dovecot-auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=john rhost=202.81.69.135 Jul 27 21:48:26 email dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user john I have the following in the .conf file auth_verbose=yes auth_debug=yes auth_debug_passwords=yes mail_debug=yes verbose_ssl=yes Also note the following differences in behaviour between Dovecot 1.0.7 and 1.2.17 $ telnet new_system_1.2.17 10143 Trying 192.168.1.10... Connected to new_system.com.au. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE STARTTLS LOGINDISABLED] Dovecot ready. A001 LOGIN john Q1r404uC * BAD [ALERT] Plaintext authentication not allowed without SSL/TLS, but your client did it anyway. If anyone was listening, the password was exposed. A001 NO [CLIENTBUG] Plaintext authentication disallowed on non-secure (SSL/TLS) connections. telnet> quit Connection closed. $ telnet old_system_1.0.7 10143 Trying 192.168.1.4... Connected to new_system.com.au Escape character is '^]'. * OK Dovecot ready. A001 LOGIN john Q1r404uC A001 OK Logged in. Can anyone suggest what else I can enable to assist in determining why I can't appear to login. Its appears related to SSL/TLS but I don't seem to have enough to go on. I'm probably doing something stupid as usual. Regards John

1 0

[Dovecot] sieve, vacation - lda-dupes being ignored?
by Per Jessen 27 Jul '11

27 Jul '11

Environment: dovecot 2.0.9, postfix 2.6, Pigeonhole 0.2.2 I'm in the process of setting up vacation auto-reply for the first time, (it's that time of the year) and it looks like .dovecot.lda-dupes is being updated, but not read (or just ignored). my vacation script: require ["vacation","variables"]; # get hold of the subject if header :matches "Subject" "*" { set "subj" "${1}"; } vacation # Reply at most once a week to a same sender :days 7 :subject "Re: ${subj} (automatic reply; I am out of the office)" :addresses "pjessen(a)example.com" :mime text: The script works fine, but I get a reply for every msg sent: # grep sieve.*sent /var/log/mail Jul 26 10:17:26 neon dovecot: lmtp(4367, per.acm(a)example.com) Pj0iEbx3Lk4PEQAA0G3O/A: sieve: msgid=<4E2E7807.8000301(a)example.com>: sent vacation response to <SRS0+9c3c5bbcdb70e56f=2N=example.com=per.jessen(a)srs.example.org> Jul 26 10:29:06 neon dovecot: lmtp(10165, per.acm(a)example.com) Hbm3DhJ6Lk61JwAA0G3O/A: sieve: msgid=<4E2E7ABF.3090804(a)example.com>: sent vacation response to <SRS0+9c3c5bbcdb70e56f=2N=example.com=per.jessen(a)srs.example.org> Jul 26 11:09:41 neon dovecot: lmtp(2496, per.acm(a)example.com) WPtRMVWELk7ACQAA0G3O/A: sieve: msgid=<4E2E8447.9070007(a)example.com>: sent vacation response to <SRS0+9c3c5bbcdb70e56f=2N=example.com=per.jessen(a)srs.example.org> Jul 26 11:32:26 neon dovecot: lmtp(15648, per.acm(a)example.com) 7pQrLKqJLk4gPQAA0G3O/A: sieve: msgid=<4E2E8999.8040800(a)example.com>: sent vacation response to <SRS0+9c3c5bbcdb70e56f=2N=example.com=per.jessen(a)srs.example.org> Jul 26 11:39:12 neon dovecot: lmtp(18845, per.acm(a)example.com) ds9CDfeKLk6dSQAA0G3O/A: sieve: msgid=<4E2E8B30.1070804(a)example.com>: sent vacation response to <SRS0+9c3c5bbcdb70e56f=2N=example.com=per.jessen(a)srs.example.org> Jul 26 11:42:40 neon dovecot: lmtp(21484, per.acm(a)example.com) eXZHOw+MLk7sUwAA0G3O/A: sieve: msgid=<4E2E8BF9.7010301(a)example.com>: sent vacation response to <SRS0+9c3c5bbcdb70e56f=2N=example.com=per.jessen(a)srs.example.org> Jul 26 15:26:25 neon dovecot: lmtp(19216, per.acm(a)example.com) Wma/OIDALk4QSwAA0G3O/A: sieve: msgid=<4E2EC06F.5060307(a)example.com>: sent vacation response to <SRS0+9c3c5bbcdb70e56f=2N=example.com=per.jessen(a)srs.example.org> Is there a way to dump the contents of lda-dupes in clear text? thanks Per Jessen, Zürich

1 1

Re: [Dovecot] Converting from qpopper mbox to dovecot maildir
by Joseph Tam 26 Jul '11

26 Jul '11

Dimos Alevizos <dalevizo(a)otenet.gr> wrote: > We recently completed the migration in our company from qpopper/mbox to > dovecot/mbox using only pop3_reuse_xuidl = yes and while everything went much > easier than we feared we came across an interesting problem that you might want > to pay attention to. > > We use dovecot to provide both pop3 and imap (directly and via webmail) access > to our client's mailboxes and we noticed that when a client moves a mail to a > different folder and then back into INBOX (say he deleted it by mistake and > moves it back), dovecot inserts the same X-UIDL into it's cache, thus creating > duplicate entries. > > When a pop3 client sees this (at least outlook in our case) it think's that > there's something wrong with the server's X-UIDL handling and re-downloads the > duplicate messages. EVERY time the user checks his mails. I haven't heard any user complaint about this, but perhaps nobody tried this before. I recreated this situation (copy old qpopper message INBOX -> tmpbox -> INBOX) and produced two messages with identical X-UIDL headers, but according to the Wikipedia entry for POP3: Comparison with IMAP Clients that leave mail on servers generally use the UIDL command to get the current association of message-numbers to message identified by its unique identifier. The unique identifier is arbitrary, and might be repeated if the mailbox contains identical messages. This is echoed in RFC1939 (page 11-12) While it is generally preferable for server implementations to store arbitrarily assigned unique-ids in the maildrop, this specification is intended to permit unique-ids to be calculated as a hash of the message. Clients should be able to handle a situation where two identical copies of a message in a maildrop have the same unique-id. So POP3 UIDLs are not guaranteed to be unique, especially if the messages are the same. Perhaps some mail readers are making unwarranted assumptions about the uniqueness of UIDLs: http://www.eggheadcafe.com/software/aspnet/33485042/duplicate-messageiduidl… https://www.ritlabs.com/bt/view.php?id=3599 Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] phantom new message notification
by Stan Hoeppner 26 Jul '11

26 Jul '11

I've developed a phantom new message notification on a single IMAP folder in Thunderbird. I've deleted the Dovecot index files for this problematic folder, and I've deleted the .msf file in the Tbird profile. Neither of which solved the problem. The only other time I've run into something similar was with CONDSTORE quite a long time ago, but that affected all folders, not just one. Any ideas? -- Stan

1 0