- dovecot - dovecot.org

[Dovecot] upgrade from 1.0.5 to 2.1.7
by Andreas Meyer 08 Jun '12

08 Jun '12

Hello! I want to upgrade the docevot-installation from v 1.0.5 to 2.1..7 Now I get the following executing doveconf -n -c /etc/dovecot/dovecot.conf > /home/mail1/dovecot-2.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:217: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:219: passdb passwd-file {} has been replaced by passdb { driver=passwd-file } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:222: userdb passwd-file {} has been replaced by userdb { driver=passwd-file } The section at line 217 looks like this: auth default { mechanisms = plain passdb passwd-file { args = /etc/dovecot/passwd } userdb passwd-file { args = /etc/dovecot/passwd } How do I change it to fullfill the new needs? And how do I handle line 217? add auth_ prefix to all settings inside auth {} and remove the auth {} section completely ? Thanks for help! Andreas

3 14

[Dovecot] Fwd: ntlm_auth in Dovecot
by Алексей Переклад 08 Jun '12

08 Jun '12

Try to delete your server from domain and add it again by "net ads join..." > I'm trying getting NTLM auth working against AD in my Dovecot 2.0.15. > > I'm getting the following error: > > > Jun 08 14:18:11 auth: Info: winbind(?,10.44.3.151): user not > authenticated: NT_STATUS_UNSUCCESSFUL

1 0

[Dovecot] Director pop3 real ips v2.1.1
by Костырев Александр Алексеевич 08 Jun '12

08 Jun '12

good day! I'm experiencing problem with pop3 proxying: on backend servers in logs there's director's ip instead of remote's like this: Jun 8 15:21:23 host-01 dovecot: pop3-login: Login: user=<test1(a)example.com>, method=PLAIN, rip=192.168.5.102, lip=192.168.5.100, mpid=26170, secured Jun 8 15:32:16 host-01 dovecot: pop3-login: Login: user=<test1(a)example.com>, method=PLAIN, rip=192.168.5.102, lip=192.168.5.100, mpid=26426, secured -- С уважением, Костырев Александр системный администратор ЗАО "Сервер-Центр" тел.: (423) 262-02-62 (доб. 2037) факс: (423) 262-02-10 a.kostyrev(a)serverc.ru icq: 404-198-497

3 3

[Dovecot] dovecot ignores entries in virtual_alias_maps when using dovecot lda
by Marko Weber 08 Jun '12

08 Jun '12

hello list, i need help. dovecot dont look into my virtual_alias_maps . i set via postzfixadmin an alias postmaster(a)domain.tld to newmail(a)domainother.tld. when i send mails to postmaster(a)domain.tld mails are rejected. dovecot authworker tells me in log: user unknown. but i can request the data via postmap -v -q postmaster(a)domain.tld mysql:/etc/postfix/mysql_virtual_alias.cf and get result "newmail(a)domainother.tld". any ideas, hwo to get dovecot to look into my alias maps? marko

2 2

[Dovecot] Can we know when a user read our email?
by Beto Moreno 08 Jun '12

08 Jun '12

Hi. I have seen some emails servers that if I send a email to other person I can see if that person have read our emails and with a option to delete the email if the person hasn't read our email. Does dovecot have some like this feature? Thanks!!!

13 32

[Dovecot] Problems since upgrading to 2.1.6 from 2.0.20
by Trever L. Adams 08 Jun '12

08 Jun '12

Hello Everyone, I saw the text about the change and needing to define an inbox namespace. Everything seems to work fine except doveadm. I get the following from a cronjob that has worked well for years now. doveadm(account(a)example.com): Error: Syncing mailbox TRASH failed: Mailbox doesn't exist: TRASH doveadm(account(a)example.com): Error: Syncing mailbox TRASH failed: Mailbox doesn't exist: TRASH doveadm(account(a)example.com): Error: Syncing mailbox TRASH failed: Mailbox doesn't exist: TRASH The cronjob is: 1 4 * * * doveadm expunge -A mailbox TRASH SAVEDBEFORE 30D What is the problem? I have tried to find documentation and do searches for others having the same problem. I do not know if I am just missing something or what. Any help would be greatly appreciated. Thank you, Trever

1 1

[Dovecot] Postfix don't relay to dovecot virtual user
by phil25lsbin 07 Jun '12

07 Jun '12

Hi, I run a mail server on debian squeeze system , i installed the following software postfix dovecot spamassassin postgrey I configured a virtual domain and virtual mailbox but postfix don't pipe mail in dovecot. In log, it's appear that the relay mode is local and the delivery message is delivered to mailbox) Jun 7 15:23:01 ns230370 postfix/smtpd[27501]: 66BBA4D40F0: client=localhost.localdomain[127.0.0.1] Jun 7 15:23:01 ns230370 postfix/cleanup[8017]: 66BBA4D40F0: message-id=< E1Sccg1-00029S-9I(a)ns231581.ovh.net> Jun 7 15:23:01 ns230370 postfix/qmgr[27490]: 66BBA4D40F0: from=< admlb(a)lebest.fr>, size=1807, nrcpt=1 (queue active) Jun 7 15:23:01 ns230370 postfix/local[7907]: 66BBA4D40F0: to=< admlb(a)lebest.fr>, relay=local, delay=0, delays=0/0/0/0, dsn=2.0.0, status=sent (delivered to mailbox) Jun 7 15:23:01 ns230370 postfix/qmgr[27490]: 66BBA4D40F0: removed My dovecot.conf: protocols = imap imaps pop3 pop3s log_timestamp = "%Y-%m-%d %H:%M:%S " log_path = /var/log/dovecot/dovecot.log info_log_path = /var/log/dovecot/dovecot-info.log mail_privileged_group = mail disable_plaintext_auth = no mail_location = maildir:/home/smtp/%d/%n:INDEX=/home/smtp/%d/%n/indexes protocol imap { } protocol pop3 { } protocol managesieve { } protocol lda { postmaster_address = admlb(a)XXX.FR mail_plugin_dir = /usr/lib/dovecot/modules/lda auth_socket_path = /var/run/dovecot/auth-master } auth default { userdb sql { args = /etc/dovecot/dovecot-mysql.conf } passdb sql { args = /etc/dovecot/dovecot-mysql.conf } socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = smtp } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } dict { } plugin { } My main.cf myhostname = smtp.XXX.FR alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases myorigin = XXX.FR mydestination = XXX.FR, smtp.XXX.FR, localhost.XXX.FRr, localhost relayhost = mynetworks = 172.16.0.0/12 127.0.0.0/8 mailbox_size_limit = 0 inet_interfaces = all virtual_uid_maps = static:3000 virtual_gid_maps = static:3000 virtual_mailbox_base = /home/smtp virtual_transport = dovecot virtual_mailbox_domains = mysql:/etc/postfix/ mysql_virtual_mailbox_domains.cf virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf relay_domains = mysql:/etc/postfix/mysql_relay_domains.cf smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_non_fqdn_hostname, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_unauth_destination, reject_unauth_pipelining, check_policy_service inet:127.0.0.1:10023, reject_invalid_hostname smtpd_sasl_auth_enable = yes smtpd_sasl_security_options = noanonymous content_filter = amavis:[127.0.0.1]:10024 receive_override_options = no_address_mappings inet_protocols = ipv4 The end of master.cf file dovecot unix - n n - - pipe flags=DRhu user=smtp:smtp argv=/usr/lib/dovecot/deliver -f ${sender} -d ${user}@${nexthop} amavis unix - - - - 2 smtp -o smtp_data_done_timeout=1200 -o smtp_send_xforward_command=yes 127.0.0.1:10025 inet n - - - - smtpd -o content_filter= -o local_recipient_maps= -o relay_recipient_maps= -o smtpd_restriction_classes= -o smtpd_client_restrictions= -o smtpd_helo_restrictions= -o smtpd_sender_restrictions= -o smtpd_recipient_restrictions=permit_mynetworks,reject -o mynetworks=127.0.0.0/8 -o strict_rfc821_envelopes=yes -o receive_override_options=no_unknown_recipient_checks,no_header_body_checks -o smtpd_bind_address=127.0.0.1 Thanks

3 3

[Dovecot] auth-worker problem here.
by Marko Weber 07 Jun '12

07 Jun '12

hello, in howto for gentoo i found this: To tell Postfix about the maps that you've just set up, add the following (substituting mysql for pgsql if you're on PostgreSQL) to the bottom of /etc/postfix/main.cf: virtual_alias_maps = mysql:/etc/postfix/sql_virtual_alias_maps.cf virtual_mailbox_domains = mysql:/etc/postfix/sql_virtual_domain_maps.cf virtual_mailbox_maps = mysql:/etc/postfix/sql_virtual_mailbox_maps.cf Tip: Because this is using the Dovecot's LDA, all results from virtual_mailbox_maps are ignored beyond checking if they exist. I added in the mysql db an alias postmaster(a)domainn.tld that should be forwarded to name(a)domainn.tld. The tip above tells me when using dovecot lda the virtual_alias_maps is ignored by dovecot. now when i send a mail to postmaster(a)domainn.tld the mail is not transported to name(a)domainn.tld. in logfile i see this: dovecot: auth-worker: sql(postmaster(a)zbfmail.de): Unknown user how can i tell dovecot to also use the virtual_alias_maps? thank you marko

1 0

[Dovecot] Problem with Dovecot and AD LDAP auth
by Алексей Переклад 07 Jun '12

07 Jun '12

Hi. Seems it's a bug in dovecot auth. I have FreeBSD 8.1-RELEASE-p1 and I tried 1.2.17 and 2.1.7 versions of Dovecot, and still no luck. The problem: when I set in dovecot-ldap.conf: base = CN=Users,DC=domain,DC=local everything works fine. But if I set: base = DC=domain,DC=local mail client can't authorize. /var/log/dovecot.log says: =============================================== Jun 07 18:07:17 auth: Debug: auth client connected (pid=14611) Jun 07 18:08:11 auth: Debug: client in: AUTH 1 PLAIN service=imap session=G1//aeLB6wAKAABu lip=10.0.0.3 rip=10.0.0.110 lport=143 rport=55787 resp=AGdhdGV3YXkAVU82eUpuUXQ= Jun 07 18:08:11 auth: Debug: ldap(gateway,10.0.0.110,<G1//aeLB6wAKAABu>): bind search: base=DC=domain,DC=local filter=(&(objectClass=person)(sAMAccountName=gateway)) Jun 07 18:08:11 auth: Debug: ldap(gateway,10.0.0.110,<G1//aeLB6wAKAABu>): result: uid missing Jun 07 18:10:18 imap-login: Info: Disconnected: Inactivity during authentication (disconnected while authenticating, waited 127 secs): user=<>, method=PLAIN, rip=10.0.0.110, lip=10.0.0.3, session=<G1//aeLB6wAKAABu> Jun 07 18:10:18 auth: Debug: client in: CANCEL 1 Jun 07 18:10:18 auth: Debug: auth client connected (pid=14706) Jun 07 18:10:26 auth: Debug: client in: AUTH 1 PLAIN service=imap session=n6IBcuLB7AAKAABu lip=10.0.0.3 rip=10.0.0.110 lport=143 rport=55788 resp=AGdhdGV3YXkAVU82eUpuUXQ= Jun 07 18:10:26 auth: Debug: ldap(gateway,10.0.0.110,<n6IBcuLB7AAKAABu>): bind search: base=DC=domain,DC=local filter=(&(objectClass=person)(sAMAccountName=gateway)) Jun 07 18:10:26 auth: Error: ldap(gateway,10.0.0.110,<n6IBcuLB7AAKAABu>): Connection appears to be hanging, reconnecting Jun 07 18:10:26 auth: Debug: ldap(gateway,10.0.0.110,<n6IBcuLB7AAKAABu>): result: uid missing Jun 07 18:10:26 auth: Error: ldap(gateway,10.0.0.110,<G1//aeLB6wAKAABu>): Request lost Jun 07 18:10:26 auth: Error: ldap(gateway,10.0.0.110,<n6IBcuLB7AAKAABu>): ldap_search(base=DC=domain,DC=local filter=(&(objectClass=person)(sAMAccountName=gateway))) failed: Operations error Jun 07 18:10:26 auth: Error: LDAP: Reply with unknown msgid 2 Jun 07 18:10:26 auth: Error: LDAP: Reply with unknown msgid 2 Jun 07 18:10:26 auth: Error: LDAP: Reply with unknown msgid 2 Jun 07 18:10:26 auth: Error: LDAP: Reply with unknown msgid 2 Jun 07 18:10:28 auth: Debug: client out: FAIL 1 user=gateway temp Jun 07 18:10:28 auth: Debug: client out: FAIL 1 user=gateway temp Jun 07 18:13:18 imap-login: Info: Disconnected: Inactivity (auth failed, 1 attempts in 172 secs): user=<gateway>, method=PLAIN, rip=10.0.0.110, lip=10.0.0.3, session=<n6IBcuLB7AAKAABu> ============================================ My dovecot-ldap.conf: =============================== ldap_version = 3 hosts = ad.domain.local base = DC=hrom,DC=local scope = subtree dn = CN=mailserver,CN=Users,DC=domain,DC=local dnpass = here_is_pass auth_bind = yes pass_attrs = uid=user pass_filter = "(&(objectClass=person)(sAMAccountName=%u))" user_attrs = name=mail=maildir:/var/mail/virtual/hrom.local/%n user_filter = "(&(objectClass=person)(sAMAccountName=%u))" =================================================== I need base = DC=domain,DC=local for searching for user's accounts in different OU of my AD. If I set base = CN=Users,DC=domain,DC=local, Dovecot can't authorize user accounts from OU. P.S.: Postfix with base = DC=domain,DC=local works perfectly, so the problem is not with our domain controller (LDAP server as well) .

1 0

[Dovecot] Email auto purging applied to all mail folders
by Joe V Aldeguer 07 Jun '12

07 Jun '12

Hello, Is it possible to have this done not only for spam and trash folder but lets say like the user inbox and any user created mail folders too? My ultimate goal is to have a way to automate the email deletion process of emails stored in the user inbox or mail folders when it reaches a specified date. My boss wants to force users to keep emails only a month old anything beyond that will be deleted. Has anyone done this using dovecot and are there any guides available? I am also open to suggestions for commercial solutions but so far searching online for solutions only comes up with email archiving. The dovecot version I have installed is version 2.0.19. Thanks in advance. - Joe

2 1

[Dovecot] dsync backup doubles quota
by Patrick Westenberg 07 Jun '12

07 Jun '12

Hi everyone, I recognized a very strange behavior when doing backups of my mdbox mailboxes. After the backup the quota for each mailbox is twice as much as before the backup and I have to recalculate the quota to get the former/correct information. root@mb01:~# doveadm quota get -u test(a)example.com User quota STORAGE 5 10240 User quota MESSAGE 11 - root@mb01:~# doveadm backup -u test(a)example.com mdbox:/home/example.com/test root@mb01:~# doveadm quota get -u test(a)example.com User quota STORAGE 10 10240 User quota MESSAGE 22 - root@mb01:~# doveadm quota get -u test(a)example.com root@mb01:~# doveadm quota get -u test(a)example.com User quota STORAGE 5 10240 User quota MESSAGE 11 - Is this a bug or normal behavior? Regards Patrick

2 1

[Dovecot] best practises for mail systems
by Костырев Александр Алексеевич 06 Jun '12

06 Jun '12

hello! Can someone point me to some best practices in building high-available scalable mail system or! share your own success stories. I've read article in LJ "Building a Scalable High-Availability E-Mail System with Active Directory and More" but it seemed to be outdated and there's a single point of failure (Master node). What I want to achieve: high-available, horizontaly scalable, with no single point of failure mail solution. Available hardware: intel mfsys25 modular server with 2 storage controllers, 2 switches, 4 power supply blocks with - 2 blade-servers in mfsys with: 2xIntel Xeon E5620 @ 2.40GHz with 8 cores each - promise vtrak e610s (2 storage controllers, 2 power supply blocks) - 6x 2TB SATA Hitachi HDS72302 We decided to go for KVM virtualization and glusterfs for live migration for vm image but that's not what this is all about :) We installed centos on host systems. for now while we could think of two ways to go: The first way (currently at testing stage): On each host system we created one VM and passed through 3x2TB disks into it. In guests vms on top of this disks we made XFS and fired up glusterfs with distributed replicated volumes for our mailstorage. so it looks like this: vm1 replicate vm2 disk1 ------------> disk4 disk2 ------------> disk5 disk3 ------------> disk6 in each vm we mounted glusterfs and pointed dovecot to that dir for mail creation (as ltmp) and imap4 user access. also we use exim as smtp. So, with glusterfs as mailstorage we can go for LVS to load balancing for exim and dovecot. so wherenever one of host systems (hence one of mail vms) goes down, users don't notice that 'cause LVS points them to working smtp and imap4 servers and they get their mail 'cause of glusterfs. Pros: - high-available - horizontaly scalable - with no single point of failure Cons: - not quite sure if glusterfs is production ready solution 'cause I've experienced split-brains during setting it up - IO performance issue. Though we didn't yet run any io tests, but glusterfs uses fuse to mount on clients. And guys on #gluster told me writing to the glusterfs mount will not be strictly local io. The second way: split up the users mail with: two back-end VMs each other on DIFFERENT host system with - fat mailstorage with raid1+linear mode (mdadm)+XFS - dovecot/exim-back-ends and two VMs for nginx-based proxy servers for imap4 and smtp - nginx can redirect user to right back-end through HTTP-php-based logic. Pros: - we split up not only load for exim/dovecot but users mail IOs too - no split-brains Cons: - If one of the host systems (hence one of back-end VMs with storage) goes down, half of our users is unhappy P.S. Sorry if this place is way wrong to ask for such things.

5 5

[Dovecot] No ports listening
by Marco 06 Jun '12

06 Jun '12

Please forgive my newbie post but this has me stumped. I've been a happy Dovecot 0.X and 1.X admin for years but something in my first 2.X configuration is oddly broken. It loads fine, logs no errors, but doesn't listen to any network ports! Thanks in advance for any help. Marco # 2.0.19: /etc/dovecot/dovecot.conf # OS: Linux 2.6.35.14 x86_64 Ubuntu 10.10 ext4 auth_debug = yes auth_mechanisms = plain login first_valid_gid = 111 first_valid_uid = 111 login_greeting = example.com pop/imap ready mail_location = mbox:/var/mail/%u.imap:INBOX=/var/mail/%u passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { mode = 0666 } } service imap-login { inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 993 } process_limit = 50 } service pop3-login { inet_listener pop3 { address = * port = 110 } inet_listener pop3s { address = * port = 995 } process_limit = 50 } ssl_cert = </etc/ssl/mail.example.com.crt ssl_key = </etc/ssl/mail.example.com.key syslog_facility = local0 userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } valid_chroot_dirs = /var/mail verbose_proctitle = yes verbose_ssl = yes protocol lda { postmaster_address = postmaster(a)example.com }

1 0

Re: [Dovecot] dovecot-metadata-9 released
by Dennis Schridde 06 Jun '12

06 Jun '12

Hello Nick! I am sorry - I forgot to mention that you need attached patch for dovecot. Kind regards, Dennis Am Dienstag, 5. Juni 2012, 11:28:27 schrieb Nick Rosier: > Hi Dennis, > > I'm trying to compile the plugin on FreeBSD 9 with Dovecot 2.1.7 and get > the following error: > > libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. > -I/usr/local/include/dovecot -g -O2 -MT mailbox-ext.lo -MD -MP -MF > .deps/mailbox-ext.Tpo -c mailbox-ext.c -fPIC -DPIC -o > .libs/mailbox-ext.o mailbox-ext.c:25:19: error: missing binary operator > before token "(" > mailbox-ext.c: In function 'mailbox_get_guid_string': mailbox-ext.c:32: > error: 'MAIL_GUID_128_SIZE' undeclared (first use in this function) > mailbox-ext.c:32: error: (Each undeclared identifier is reported only > once mailbox-ext.c:32: error: for each function it appears in.) > mailbox-ext.c:33: warning: implicit declaration of function > 'mailbox_get_guid' > *** Error code 1 > Stop in /root/work/dovecot-metadata-plugin-6fe39779d758/src. *** Error > code 1 > > Removing DOVECOT_PREREQ and "forcing" to use the 2.1 definition fixes > that (I couldn't find anywhere where that macro was defined). > > Next I get another error, again caused by the DOVECOT_PREREQ: > > libtool: compile: gcc -std=gnu99 -DHAVE_CONFIG_H -I. -I.. > -I/usr/local/include/dovecot -g -O2 -MT imap-metadata-plugin.lo -MD -MP > -MF .deps/imap-metadata-plugin.Tpo -c imap-metadata-plugin.c -fPIC > -DPIC -o .libs/imap-metadata-plugin.o > imap-metadata-plugin.c: In function 'is_valid_rfc5464_entry_name': > imap-metadata-plugin.c:162: warning: comparison is always false due to > limited range of data type > imap-metadata-plugin.c:513:19: error: missing binary operator before > token "(" > imap-metadata-plugin.c: In function 'cmd_getmetadata': > imap-metadata-plugin.c:516: warning: passing argument 2 of > 'mail_namespace_find' from incompatible pointer type > imap-metadata-plugin.c: In function 'setmetadata_helper': > imap-metadata-plugin.c:596: warning: 'return' with a value, in function > returning void > imap-metadata-plugin.c:672:19: error: missing binary operator before > token "(" > imap-metadata-plugin.c: In function 'cmd_setmetadata': > imap-metadata-plugin.c:675: warning: passing argument 2 of > 'mail_namespace_find' from incompatible pointer type > *** Error code 1 > > Am I missing something on my system? > > Rgds, > N. > > Dennis Schridde wrote: > > Hello everyone! > > > > I just released dovecot-metadata-8, which is an implementation of RFC 5464 > > (IMAP METADATA), allowing to add comments/annotations/metadata to folders > > of an email account. > > > > 2012-06-04: Version 9 > > > > * Added Dovecot 2.1 compatibility > > * Fixed compliance with RFC 5464 Section 3.2 > > * Separated backend code into library > > * Synced code of imap-annotatemore with imap-metadata > > * Improved error messages > > * Several bugfixes (incl. segfaults) > > * Minor cleanups > > > > Please get the code from [1] and send me an email for any problem you > > find. > > > > For more information please refer to my email from Sun, 12 Jun 2011 > > 15:55:57 +0200 titled "dovecot-metadata-8 released". > > > > Kind regards, > > Dennis > > > > [1] http://hg.dovecot.org/dovecot-metadata-plugin

2 1

Re: [Dovecot] auth trouble
by Joseph Tam 06 Jun '12

06 Jun '12

Glenn English wrote: >> Maybe someone is brute forcing your server's Postfix authenticated >> SMTP service since Postfix can be configured to use Dovecot's SASL >> authentication framework. > > and for the suggestion -- I do have Postfix using Dovecot-Auth checking > for SASL. > > I think I'm going to re-install and run Tripwire... Tripwire? If the purpose of your query is to automate blocking of brute forcers, this software is not what you want (which detects tampering of critical system files). I suggest trying to find where Postfix failed login reports go, then use your fail2ban or what-have-you to detect and block hosts that repeatedly fail authentication. (First Google hit I did on this subject) http://scottlinux.com/2011/05/26/prevent-postfix-brute-force/ The log entries might look like {timestamp} {servername} postfix/smtpd[{pid}]: lost connection after AUTH from {remote-hostname}[{remote-ip}] Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] INBOX help needed, dovecot + squirrelmail
by jeep＠rahul.net 05 Jun '12

05 Jun '12

Im trying to figure out how to get dovecot to deliver to my mail_location (example: /opt/imapdata/j/jeff/INBOX/inbox) AND work with squirrelmail. Ive worked on this for hours reading the docs etc with no luck so far. I get dovecot-lda to deliver to: /opt/imapdata/j/jeff/INBOX/inbox but when I use squirrelmail, I see the following in the log: dovecot: imap(jeff): Debug: Effective uid=1006, gid=999, home=/opt/imapdata/j/jeff/INBOX/inbox dovecot: imap(jeff): Error: chdir(/opt/imapdata/j/jeff/INBOX/inbox) failed: Not a directory dovecot: imap(jeff): Debug: Namespace : type=private, prefix=INBOX/, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/opt/imapdata/j/jeff:INBOX=/opt/imapdata/j/jeff/INBOX:LAYOUT=fs:DIRNAME=mmDIR:INDEX=~/indexes It complains that 'inbox' isnt a directory, but I want it to use: /opt/imapdata/j/jeff/INBOX What parameter do I need to tweak to get this to work? Ive tried the 'folder options' in squirrelmail but that doesnt appear to have any effect here (or at least at this point in my testing). It seems that the only parameter to tweak is 'mail_location' which Im having no luck getting to work correctly. Also namespace may play a part but every combination Ive tried does not result in getting it work thus far. On a sidenote when I send more than 1 email, it doesnt seem to honor 'maildir', it seems its doing 'mbox' instead? I get one flat file. Im lost and confused. my variables: mail_location = maildir:/opt/imapdata/%1n/%n:INBOX=/opt/imapdata/%1n/%n:LAYOUT=fs:DIRNAME=mmDIR:INDEX=~/indexes namespace { type = private separator = / prefix = INBOX/ inbox = yes } Your help is appreciated! Thanks, Jeff /mf/home/jeep/shell/.signature

2 5

[Dovecot] Customization of "Rejected" message.
by Malloc Kilobyte 04 Jun '12

04 Jun '12

Helo, I'm using Dovecot 2.1.1 with Postfix 2.3.3. I've enabled the quota plugin, so that Dovecot LDA reject e-mails, when user's mailbox is out of space. By default, when mailbox is near quota, and someone tries to send huge message, a reply is automatically send to the sender. It's being send from postmaster named as Mail Delivery Subsystem. And here is my question: Is there some way to customize that auto-reply, so that it is not only being send to the sender but also to recipient gets some notice about failed attempt ? I've also noticed, that this reply has attachment, which is rejected message, but it appears to be empty. Can I configure Dovecot to send back whole rejected message ? Regards malloc4k

1 0

[Dovecot] dovecot-metadata-9 released
by Dennis Schridde 04 Jun '12

04 Jun '12

Hello everyone! I just released dovecot-metadata-8, which is an implementation of RFC 5464 (IMAP METADATA), allowing to add comments/annotations/metadata to folders of an email account. 2012-06-04: Version 9 * Added Dovecot 2.1 compatibility * Fixed compliance with RFC 5464 Section 3.2 * Separated backend code into library * Synced code of imap-annotatemore with imap-metadata * Improved error messages * Several bugfixes (incl. segfaults) * Minor cleanups Please get the code from [1] and send me an email for any problem you find. For more information please refer to my email from Sun, 12 Jun 2011 15:55:57 +0200 titled "dovecot-metadata-8 released". Kind regards, Dennis [1] http://hg.dovecot.org/dovecot-metadata-plugin

2 1

[Dovecot] Vacation stopped working
by Jacek Osiecki 04 Jun '12

04 Jun '12

Hi, I'm sure that it WAS working, but I can't guarantee... On a system with dovecot 2.0.16 and dovecot-pigeonhole-2.0_0.2.5. Today a user reported that vacation autoreponse did not work for him. As I have checked the dovecot logs, I see such a message: Jun 04 13:39:51 lmtp(9986, user(a)xxx.com) Info: ZumtCleezE8CJwAAA1GDYg: sieve: msgid=<alpine.LNX.2.00.1206041336520.11397(a)pingwin.sc>: discarding vacation response for implicitly delivered message; no known (envelope) recipient address found in message headers (recipient=<user(a)xxx.com>, and additional `:addresses' are specified) Any idea what actually went wrong? I was browsing for this error message, but found only dovecot sources :( Greetings, -- Jacek Osiecki joshua(a)ceti.pl GG:3828944 I don't want something I need. I want something I want.

1 0

Re: [Dovecot] Can we know when a user read our email?
by Richard 04 Jun '12

04 Jun '12

> Date: Sunday, June 03, 2012 02:54:32 PM -0400 > From: Jerry <jerry(a)seibercom.net> > >> On Sun, 03 Jun 2012 20:19:20 +0200 >> Reindl Harald articulated: >> >> people are mostly to stupid to realize what they >> are trying to accomplish and why it it a bad idea >> >> this is why we professionals exist and if people >> refuse what you are explaining them kiss them >> goodbye - irt will be better for you over the long > > No offense, but considering your business attitude and disdain for > potential clients and your opinion of them, it would be a far > better thing if they steered clear of you all together. There are > many considerate, intelligent, compassionate professionals out > there who would be willing to take on the difficult client. Any > "asshole" can service the routine, run of the mill, client. It > takes a true professional to work with and service a difficult > one. Something that seems to be missing from this discussion are considerations of privacy and (personal) security. There are fairly serious implications of a sender being able to tell that/when someone has downloaded/opened a message -- including discovery of daily patterns and potentially where the recipient is, or isn't. I think it is our responsibility to understand these issues and explain them to managers/clients in order to bring them along if we refuse (as I would) to provide a capability such as this. [I always set the sendmail "noreceipts" PrivacyOptions so it doesn't respond to these disposition requests.] One approach is to point out to managers/clients that if their system is configured to return read receipts, anyone sending mail to them on that system will be able to get these same types of receipts. When they think about that they may not like the implications and may reconsider their request. Just because it is technically possible to do something (and even if other vendors provide the capability) does not mean that it is the ethically or legally responsible thing to do. - Richard

2 1

[Dovecot] Exposing global (default) sieve script through Managesieve
by Matthijs Kooijman 04 Jun '12

04 Jun '12

Hi folks, I'm setting up a dovecot server with managesieve support. I'd like to offer spamfiltering through a Sieve script to my users by default, but still allow them to modify the filtering rules through Managesieve. I found the sieve_global_path configuration option, which seems perfect for what I want. I can configure a default script there, which will work for all users until they set upload their own sieve script using managesieve. However, when configured like this, the user experience isn't quite perfect. When users open the managesieve interface on their client, there is no trace of the default filters, so users might think the spamfiltering is done in some other manner. Now, when they create a filtering rule (e.g., to sort out mail to mailing lists), that rule will overwrite the default spamfiltering rule causing all the spam to spill into the user's mailbox. I'm afraid that most users won't realize they have to manually recreate the spamfiltering rule to fix this. Also, they might not know how to write the rule, even if they do... I've considered a few existing ways to fix this: - Use sieve_before / sieve_after to make sure that the default script is always executed, in addition to any user-supplied scripts. This removes the surprise, but removes the option for users to tweak the spamfiltering rules. - Don't use sieve_global_path, but instead distribute the default script to each user's homedir on user creation. This prevents making changes to the default script for existing users and in my setup, user creation and (mail)homedir creation are nicely separated through an LDAP directory, I'd rather not go this route. - When using the Roundcube webmail application as the IMAP client, I can point Roundcube at the default sieve script. Now, when Roundcube sees there are no scripts through ManageSieve, it shows a (fake) "default" script with the correct contents. As soon as the user changes this script or creates a new script, it is actually uploaded to Dovecot, causing the edited script to be used instead of the global script. This option has the user experience I'm looking for, but having this out-of-band connection from Roundcube to the default script configured with dovecot is ugly (and tricky, since these run on different hosts in my setup). The biggest problem is of course that this only works for Roundcube, not for any other IMAP client my users might use. So, I was wondering: Wouldn't it make sense for the managesieve plugin to do something similar to roundcube: When the user has no sieve script configured, let it fake a single "default" script, showing the contents of the global script? Since the ManageSieve protocol doesn't seem to support any way to flag this situation, it would be fooling the clients a bit, but I'm not sure if that's really a problem. While the user has not script named "default" in his sieve_dir: - include a script called "default" in the LISTSCRIPTS output. - return the contents of the sieve_global_path in the GETSCRIPT "default" command. - remove any sieve symlink after a SETACTIVE "default" command (as if SETACTIVE "" was given). This causes dovecot to fall back to the sieve_global_path script. - the DELETESCRIPT "default" command should fail. This might confuse clients and users, since it is listed in LISTSCRIPTS but cannot be deleted, but I think most users will understand they can't delete the default script. - RENAMESCRIPT "default" "some_name" should copy the sieve_global_path script into the user's sieve_dir. This will effectively copy the script instead of renaming it (since it will still be magically listed in LISTSCRIPTS), so that might be confusing. All other commands work just like they do now (in particular, PUTSCRIPT "default" uploads a script called "default" into the user's sieve_dir, preventing all of the above from applying. As noted above, this change might cause some confusion, but I think that is manageable. On additional thing is that running SETACTIVE "" will not completely disable sieve processing (as would be expected), but will (again) cause the sieve_global_path script to be run. This is already the case currently, though, and should probably be considered a separate problem (whose root cause is the lack of a difference between "no script script configured yet" and "active script disabled", both remove the sieve symlink). Also, this problem might be a feature in some setups, so fixing it might not be so easy... So, any thoughts on this? Any fundamental problems I'm missing? (Not-so) obvious alternatives? Gr. Matthijs

2 3

[Dovecot] postfix+dovecat: virtual domains with imap+lmtp
by el07694 03 Jun '12

03 Jun '12

Hi to all, I have tryed a few days to configure postfix/dovecot to run into a VPS machine (CentOs) -->The machine has 2 domains (but more in the future) -->i want info(a)mail.domain1.com and info(a)mail.domain2.com to be seperated mailboxes -->i want to use lmtp protocol to connect dovecot with postfix -->It will be perfect if i can use the system users for authentication I /etc/postfix/main.cf file looks like this smtpd_soft_error_limit = 10 smtpd_hard_error_limit = 20 masquerade_domains = mail.going-on.com mail.commundi.de masquerade_exceptions = root, papinhio relocated_maps = hash:/etc/postfix/relocated smtpd_client_restrictions = check_client_access hash:/etc/postfix/access virtual_mailbox_domains = mail.going-on.com mail.commundi.de virtual_mailbox_base = /var/spool/virtual_hosts virtual_mailbox_maps = hash:/etc/postfix/virtual virtual_uid_maps = static:0 virtual_gid_maps = static:0 mailbox_command = /usr/libexec/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT" dovecot_destination_recipient_limit = 1 mailbox_transport = lmtp:unix:private/dovecot-lmtp /etc/postfix/relocated file has only comments the same for /etc/postfix/access file i have made /var/spool/virtual_hosts folder with chmod 777 inside this folder i have made mail.going-on.com folder and mail.commundi.de folder cat /etc/postfix/virtual produce this: papinhio(a)mail.going-on.com mail.going-on.com/papinhio papinhio is a system_user!! uid,gid = 0 (the root user) master.cf file # # Postfix master process configuration file. For details on the format # of the file, see the master(5) manual page (command: "man 5 master"). # # ========================================================================== # service type private unpriv chroot wakeup maxproc command + args # (yes) (yes) (yes) (never) (100) # ========================================================================== smtp inet n - n - - smtpd submission inet n - n - - smtpd -o smtpd_enforce_tls=yes -o smtpd_sasl_auth_enable=yes -o smtpd_sasl_type=dovecot -o smtpd_sasl_path=private/auth -o smtpd_sasl_security_options=noanonymous -o smtpd_sasl_local_domain=$myhostname -o smtpd_client_restrictions=permit_sasl_authenticated,reject -o smtpd_sender_login_maps=hash:/etc/postfix/virtual pickup fifo n - - 60 1 pickup cleanup unix n - - - 0 cleanup qmgr fifo n - n 300 1 qmgr #qmgr fifo n - n 300 1 oqmgr tlsmgr unix - - n 1000? 1 tlsmgr rewrite unix - - n - - trivial-rewrite bounce unix - - n - 0 bounce defer unix - - n - 0 bounce trace unix - - n - 0 bounce verify unix - - n - 1 verify flush unix n - n 1000? 0 flush proxymap unix - - n - - proxymap smtp unix - - n - - smtp relay unix - - n - - smtp -o fallback_relay= showq unix n - n - - showq error unix - - n - - error discard unix - - n - - discard local unix - n n - - local virtual unix - n n - - virtual lmtp unix - - n - - lmtp anvil unix - - n - 1 anvil scache unix - - n - 1 scache maildrop unix - n n - - pipe flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient} # # The Cyrus deliver program has changed incompatibly, multiple times. # old-cyrus unix - n n - - pipe flags=R user=cyrus argv=/usr/lib/cyrus-imapd/deliver -e -m ${extension} ${user} # Cyrus 2.1.5 (Amos Gouaux) # Also specify in main.cf: cyrus_destination_recipient_limit=1 cyrus unix - n n - - pipe user=cyrus argv=/usr/lib/cyrus-imapd/deliver -e -r ${sender} -m ${extension} ${user} # # See the Postfix UUCP_README file for configuration details. # uucp unix - n n - - pipe flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient) ifmail unix - n n - - pipe flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient) bsmtp unix - n n - - pipe flags=Fq. user=foo argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient dovecot unix - n n - - pipe flags=DRhu user=root:root argv=/usr/local/libexec/dovecot/dovecot-lda -f ${sender} -d ${recipient} Ok, the /etc/dovecot/dovecot.conf file looks like this: !include conf.d/*.conf !include_try local.conf protocols = imap lmtp service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } protocol lmtp { mail_plugins = quota sieve } mail_location = mbox:/var/spool/virtual_hosts/%d/%n Both of the services can start this no errors/warnings I can send mail from bash with this command : /bin/mail -s "Hello" "el07694(a)mail.ntua.gr" < /etc/dovecot/dovecot.conf Can anyone help me, plz? I don't know what i do wrong Thanks in advance, Chris Pappas

2 1

[Dovecot] sieve with dovecot v1.x
by Andreas Meyer 02 Jun '12

02 Jun '12

Hello! Is there a chance to have sieve working with dovecot version 1.0.5? /usr/lib/dovecot looks like this: -rwxr-xr-x 1 root root 43932 22. Sep 2007 checkpassword-reply -rwxr-xr-x 1 root root 538996 22. Sep 2007 deliver -rwxr-xr-x 1 root root 127728 22. Sep 2007 dict -rwxr-xr-x 1 root root 270248 22. Sep 2007 dovecot-auth -rwxr-xr-x 1 root root 43952 22. Sep 2007 gdbhelper -rwxr-xr-x 1 root root 48080 22. Sep 2007 idxview -rwxr-xr-x 1 root root 596364 22. Sep 2007 imap -rwxr-xr-x 1 root root 135912 22. Sep 2007 imap-login -rwxr-xr-x 1 root root 43952 22. Sep 2007 logview drwxr-xr-x 5 root root 4096 23. Dez 2008 modules -rwxr-xr-x 1 root root 529512 22. Sep 2007 pop3 -rwxr-xr-x 1 root root 127660 22. Sep 2007 pop3-login -rwxr-xr-x 1 root root 69056 22. Sep 2007 rawlog -rwxr-xr-x 1 root root 134748 22. Sep 2007 sievec -rwxr-xr-x 1 root root 68748 22. Sep 2007 sieved -rwxr-xr-x 1 root root 44116 22. Sep 2007 ssl-build-param so there is a sievec and a sieved, but in the dovecot.conf there is no mention about sieve. I would compile the latest version of dovecot if I knew, how the running 1.0.5 was built. I need it for an openSUSE 10.3 Kind regards Andreas

3 5

[Dovecot] Strange Dovecot 2.0.20 auth chokes and cores
by Alan Brown 02 Jun '12

02 Jun '12

> From: "Konrad ."<len7hir(a)gmail.com> > When we upgrade our kernels from 2.6.32.2 to 3.2.16 something strange > has happened. > On high traffic dovecot/auth looks like not responding. > > We found a lot of this lines at the log: [snip] > We compile Dovecot with poll instead of epoll (--with-ioloop=poll) and > this works for us. > > > Is any problem with epoll on 3.2.x kernels? Yes - and it's been discussed here. Some "bright spark" rewrote the kernel epoll code to prevent DoS attacks caused by "excessive forking". That "bright spark" clearly doesn't use imap or webserver software. Redhat backported this change to kernels released after February 2012 and are about to release an emergency kernel release which removes it. A number of $LARGE companies were "not happy" As you've posted, compiling without epoll fixes the problem, but that doesn't help anyone using distro or repo packages.

3 2

[Dovecot] interesting stats pattern
by Cor Bosman 02 Jun '12

02 Jun '12

Hey all, im experimenting with dovecot stats service, and graphing the result. My initial results are kind of interesting. Check out this graph showing connected sessions and users: http://grab.by/dReu At first I thought maybe one of our 35 imap servers was having issues sending data, but all individual servers show this patters. Here is a bunch of individual servers: http://grab.by/dReC Anyone have any idea what could cause such a pattern? Maybe dovecot does some cleaning up of idle sessions at specific intervals? Or maybe our loadbalancers do, or the imapdirectors. regards, Cor

5 7

[Dovecot] auth trouble
by Glenn English 02 Jun '12

02 Jun '12

Debian Lenny, Dovecot v 1.0.15. I'm getting a lot of what I think is a local socket asking dovecot:auth to verify username/passwords: > May 31 09:00:54 server dovecot-auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=admin rhost= Note the empty 'rhost='. That's why I think it's on the server. I see others that look like bots: > May 30 23:08:43 server dovecot-auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=admin rhost=200.119.139.22 And I know how to promote the latter to a firewall. But with no rhost, I'm stumped... I've read books, googled, read docs, and asked for help on other mailing lists, and I've learned a lot. And I no longer think it really has much to do with Dovecot, other than the login attempt going through it to get to PAM. But has anyone here seen this before? Is my current theory correct? What did you do to make it go away? (I suspect that upgrading to Debian Squeeze might get rid of it, but I'm afraid that if I don't figure out what's going on, it might just come back.) -- Glenn English hand-wrapped from my Apple Mail

1 1

[Dovecot] Inconsistent search results and crash on force-resync
by Joe Beaubien 01 Jun '12

01 Jun '12

Hi, I am seeing inconsistencies in search results (finding 2 emails when only 1 exists, finding the email when it has been moved to another folder, etc). I figured I should run force-resync to fix any issues. I ran the following: doveadm -v force-resync -u <user> <mailbox> and I got some worrysome logs. - I should mention that I have been seeing some crashes of fts-lucene in my logs. I sent a traceback of this on the mailing list 1-2 days ago under the subject "[Dovecot] fts_lucene crashing". - I should also mention that all the problems I am having are only in 1 email account. This email account contains folders of over 100k emails. Do I need to tweak dovecot somehow for this? Up until now all I did was change vsz_limit to 1024 MB for "service imap". Here are the logs: Jun 1 11:15:01 XXXXX dovecot: imap(form): Error: Recent flags state corrupted for mailbox INBOX2 Jun 1 11:15:01 XXXXX dovecot: imap(form): Error: /data/emails/form/mailboxes/INBOX2/dbox-Mails/dovecot.index reset, view is now inconsistent Jun 1 11:15:01 XXXXX dovecot: imap(form): Error: /data/emails/form/mailboxes/INBOX2/dbox-Mails/dovecot.index reset, view is now inconsistent Jun 1 11:15:01 XXXXX dovecot: imap(form): Error: Recent flags state corrupted for mailbox contrat Jun 1 11:15:01 XXXXX dovecot: imap(form): Error: /data/emails/form/mailboxes/contrat/dbox-Mails/dovecot.index reset, view is now inconsistent Jun 1 11:15:01 XXXXX dovecot: imap(form): Error: /data/emails/form/mailboxes/rep_Immigation soi-m&AOo-me/dbox-Mails/dovecot.index reset, view is now inconsistent Jun 1 11:15:01 XXXXX dovecot: imap(form): Error: /data/emails/form/mailboxes/Templates/dbox-Mails/dovecot.index reset, view is now inconsistent Jun 1 11:15:02 XXXXX dovecot: imap(form): Error: Recent flags state corrupted for mailbox rep_eval_positive Jun 1 11:15:02 XXXXX dovecot: imap(form): Error: /data/emails/form/mailboxes/rep_eval_positive/dbox-Mails/dovecot.index reset, view is now inconsistent Jun 1 11:15:02 XXXXX dovecot: imap(form): Error: Recent flags state corrupted for mailbox Sent Jun 1 11:15:02 XXXXX dovecot: imap(form): Error: /data/emails/form/mailboxes/Sent/dbox-Mails/dovecot.index reset, view is now inconsistent Jun 1 11:15:02 XXXXX dovecot: imap(form): Error: Recent flags state corrupted for mailbox form_positif Jun 1 11:15:02 XXXXX dovecot: imap(form): Error: /data/emails/form/mailboxes/form_positif/dbox-Mails/dovecot.index reset, view is now inconsistent Jun 1 11:15:02 XXXXX dovecot: imap(form): Error: /data/emails/form/mailboxes/Archives/contrat/dbox-Mails/dovecot.index reset, view is now inconsistent Jun 1 11:15:02 XXXXX dovecot: imap(form): Error: /data/emails/form/mailboxes/form_positif/dbox-Mails/dovecot.index reset, view is now inconsistent Jun 1 11:15:02 XXXXX dovecot: imap(form): Error: /data/emails/form/mailboxes/form_positif/dbox-Mails/dovecot.index reset, view is now inconsistent Jun 1 11:15:03 XXXXX dovecot: imap(form): Error: /data/emails/form/mailboxes/Archives/form_indetermine/dbox-Mails/dovecot.index reset, view is now inconsistent Jun 1 11:15:03 XXXXX dovecot: imap(form): Error: /data/emails/form/mailboxes/Archives/form_indetermine/dbox-Mails/dovecot.index reset, view is now inconsistent Jun 1 11:15:15 XXXXX dovecot: imap(form): Error: Recent flags state corrupted for mailbox form_indetermine Jun 1 11:15:15 XXXXX dovecot: imap(form): Error: /data/emails/form/mailboxes/form_indetermine/dbox-Mails/dovecot.index reset, view is now inconsistent Jun 1 11:15:25 XXXXX dovecot: indexer-worker: Error: indexer-worker: /home/jd/work/clucene-core-2.3.3.4/src/core/CLucene/index/DocumentsWriter.cpp:210: std::string lucene::index::DocumentsWriter::closeDocStore(): Assertion `numDocsInStore*8 == directory->fileLength( (docStoreSegment + "." + IndexFileNames::FIELDS_INDEX_EXTENSION).c_str() )' failed. Jun 1 11:15:25 XXXXX dovecot: indexer: Error: Indexer worker disconnected, discarding 28 requests for form Jun 1 11:15:25 XXXXX dovecot: indexer-worker(form): Fatal: master: service(indexer-worker): child 9909 killed with signal 6 (core not dumped) I have 3 questions: 1) When the log says "/mailboxes/INBOX2/dbox-Mails/dovecot.index reset, view is now inconsistent" should I be worried, or this will fix itself? 2) Should I expect to see "Error: Recent flags state corrupted for mailbox Sent"??? I ran the force-resync 3 times and I still see this message. 3) Any idea why clucene is crashing? Regards, -Joe

1 0

[Dovecot] inet_listener imaps { port = 0 } question
by henrixd 01 Jun '12

01 Jun '12

Hi Why commenting out "inet_listener imaps {}" won't stop dovecot to listen port 993? I think this would be expected behavior. Just curious, finally got it working with port = 0. :) - Henri

2 1

Re: [Dovecot] High level of pop3 popping causing server to become unresponsive
by Root Kev 30 May '12

30 May '12

Missed CCing on last reply. See below.. Also, would having Nagios checking the number of messages in a mailbox cause issues with the popping of messages? And/Or would having a user accessing the mailbox from two different applications cause issues? Ie. from Outlook and mobile device? I am under the impression that a lock file is generated which should deal with the issue of contention, deleting mail, etc. Thanks for any information. Kevin Sorry for the delay in responding, long weekend in Canada... > > When trying to SSH into the server, the server prompts for user name then > password, then just hangs. Same if there is already a console connection > over, when trying to SU to root, it just hangs after entering the password. > > Our passwords are in the shadow file, and because this is a server > dedicated for this task, there is only the default linux users, and maybe 8 > other user accounts in the shadow file. > > There shouldn't be high IO as all this box does is postfix, pop3ad and > dovecot. This box is seeing less then 3000 emails a day, and only has 5 > mailboxes on it. > > Thanks for the continued suggestions... > > Kevin > > > On Sat, May 19, 2012 at 3:33 PM, Timo Sirainen <tss(a)iki.fi> wrote: > >> On Fri, 2012-05-18 at 09:21 -0400, Root Kev wrote: >> > During the last time that the load went up, it became unable to login / >> su >> > to root for the entire period that dovecot was running, we had to kill >> > dovecot and go back to Popa3d until the mailq was cleared up. We are >> > running CentOS 5.6 server. Based on TOP running at the time the CPU >> usage >> > was running under 10%. Once Dovecot was killed, we were then able to >> log >> > in /su again. >> >> Like Kelsey said, a very high disk IO might explain this, although >> normally the login should still eventually succeed. Another thing I'm >> wondering is if some process limit reached. How does the login/su fail, >> does it just hang or immediately fail with some error? >> >> > We were under the impression that checking to shadow directly should be >> the >> > fastest and least amount of overhead, is any of the other ways to >> connect >> > have less load on authentication to PAM? >> >> Your passwords really are in /etc/shadow file, not LDAP/something else? >> I don't think the problem is with authentication. Reading /etc/shadow is >> pretty fast (unless maybe if it's a huge file) and it anyway can't block >> login/su from working. >> >> >> >

5 8

Re: [Dovecot] Dovecot 2.1 mbox + maildir
by Alan Brown 30 May '12

30 May '12

> From: Timo Sirainen<tss(a)iki.fi> > On Mon, 2012-05-28 at 14:50 +0100, Alan Brown wrote: >> > What syntax is needed to make this work? >> > >> > The 2.0 wiki recomendations don't work - I can see the inboxes or the >> > folders but not both at once and there are lots of error messages about >> > prefix clashes if I simply use the existing 2.0.20 conf file on 2.1.6 > Are you saying that it works in v2.0 but not in v2.1? yes. > Then something's > wrong. Show your doveconf -n output and what error messages you see. Attached to this email (dovecot 2.0 and 2.1 -n outputs) In both cases, we use the same local config file, included from dovecot.conf (I've included both of these too) The error message is: May 30 17:00:31 msslat dovecot: imap(foobar): Error: user foobar: Initialization failed: namespace configuration error: Duplicate namespace prefix: "" May 30 17:00:31 msslat dovecot: imap(foobar): Error: Invalid user settings. Refer to server log for more information. May 30 17:00:31 msslat dovecot: master: Warning: Killed with signal 15 (by pid=18489 uid=0 code=kill) Attempting to tweak MAIL.conf to fix this error simply resulted in various states of "broken", so any help untangling this will be greatly appreciated.

2 1

[Dovecot] Strange Dovecot 2.0.20 auth chokes and cores
by Konrad . 30 May '12

30 May '12

When we upgrade our kernels from 2.6.32.2 to 3.2.16 something strange has happened. On high traffic dovecot/auth looks like not responding. We found a lot of this lines at the log: dovecot: pop3-login: Error: net_connect_unix(pop3) failed: Resource temporarily unavailable (...) and clients stop authorizing Some other errors follow in the wake of: dovecot: pop3: Error: Raw backtrace: /opt/dovecot2/lib/dovecot/libdovecot.so.0(+0x373ca) [0x7768a3ca] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(+0x3743b) [0x7768a43b] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7766048b] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(+0x4593a) [0x7769893a] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(io_add+0xaf) [0x7769757f] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(master_service_init_finish+0x19a) [0x77683c2a] -> dovecot/pop3(main+0xfc) [0x804a90c] -> /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x774c04d3] -> dovecot/pop3() [0x804aba9] dovecot: pop3: Error: Raw backtrace: /opt/dovecot2/lib/dovecot/libdovecot.so.0(+0x373ca) [0x7768a3ca] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(+0x3743b) [0x7768a43b] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7766048b] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(+0x4593a) [0x7769893a] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(io_add+0xaf) [0x7769757f] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(master_service_init_finish+0x19a) [0x77683c2a] -> dovecot/pop3(main+0xfc) [0x804a90c] -> /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x774c04d3] -> dovecot/pop3() [0x804aba9] dovecot: master: Error: service(pop3): child 18756 killed with signal 6 (core dumped) dovecot: master: Error: service(pop3): child 18756 killed with signal 6 (core dumped) dovecot: master: Error: service(pop3): command startup failed, throttling dovecot: master: Error: service(pop3): command startup failed, throttling dovecot: pop3-login: Error: Raw backtrace: /opt/dovecot2/lib/dovecot/libdovecot.so.0(+0x373ca) [0x776b73ca] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(+0x3743b) [0x776b743b] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7768d48b] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(+0x4593a) [0x776c593a] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(io_add+0xaf) [0x776c457f] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(master_service_init_finish+0x19a) [0x776b0c2a] -> /opt/dovecot2/lib/dovecot/libdovecot-login.so.0(main+0x143) [0x77705383] -> /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x774ed4d3] -> dovecot/pop3-login() [0x8049471] dovecot: pop3-login: Error: Raw backtrace: /opt/dovecot2/lib/dovecot/libdovecot.so.0(+0x373ca) [0x776fd3ca] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(+0x3743b) [0x776fd43b] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x776d348b] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(+0x4593a) [0x7770b93a] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(io_add+0xaf) [0x7770a57f] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(master_service_init_finish+0x19a) [0x776f6c2a] -> /opt/dovecot2/lib/dovecot/libdovecot-login.so.0(main+0x143) [0x7774b383] -> /lib/i386-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x775334d3] -> dovecot/pop3-login() [0x8049471] And example stack trace (from pop3, pop3-login throws almost the same): #0 0x776f6424 in __kernel_vsyscall () No symbol table info available. #1 0x7744d1ef in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 resultvar = <optimized out> resultvar = <optimized out> pid = 2002518004 selftid = 25476 #2 0x77450835 in __GI_abort () at abort.c:91 save_stage = 2 act = {__sigaction_handler = {sa_handler = 0x9bce4a8, sa_sigaction = 0x9bce4a8}, sa_mask = {__val = {163409408, 2002781570, 163374248, 603, 163374280, 604, 163374280, 2001703379, 0, 2002790760, 2140717252, 163374280, 0, 2003786736, 2002596704, 0, 2002618953, 2003087348, 2140717196, 0, 163409408, 2001286473, 163374248, 10, 2000834616, 2002534400, 604, 2003087348, 604, 2002791863, 4294967295, 10}}, sa_flags = 2140717316, sa_restorer = 0x7764bd84 <pid.3786>} sigs = {__val = {32, 0 <repeats 31 times>}} #3 0x77603390 in default_fatal_finish (type=<optimized out>, status=<optimized out>) at failures.c:187 backtrace = 0x9bce098 "/opt/dovecot2/lib/dovecot/libdovecot.so.0(+0x3837a) [0x7760337a] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(+0x383eb) [0x776033eb] -> /opt/dovecot2/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x775d877a"... #4 0x776033eb in i_internal_fatal_handler (ctx=0x7f98c174, format=0x9bd6db0 "(25476) epoll_ctl(%s, %d) failed: %m", args=0x7f98c194 "\\\323bw\006") at failures.c:688 status = 0 #5 0x775d877a in i_panic (format=0x7762d364 "epoll_ctl(%s, %d) failed: %m") at failures.c:263 ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0} args = 0x7f98c194 "\\\323bw\006" f = <optimized out> #6 0x77611d8a in io_loop_handle_add (io=0x9bd6d78) at ioloop-epoll.c:119 ---Type <return> to continue, or q <return> to quit--- ctx = 0x9bd64d8 list = <optimized out> event = {events = 24, data = {ptr = 0x9bd6da0, fd = 163409312, u32 = 163409312, u64 = 163409312}} op = 1 first = true #7 0x776109af in io_add (fd=6, condition=IO_ERROR, callback=0x775fd030 <master_status_error>, context=0x9bd6300) at ioloop.c:54 io = <optimized out> __FUNCTION__ = "io_add" #8 0x775fca9a in master_service_init_finish (service=0x9bd6300) at master-service.c:381 sigint_flags = <optimized out> st = {st_dev = 8, __pad1 = 0, __st_ino = 1286567453, st_mode = 4480, st_nlink = 1, st_uid = 0, st_gid = 0, st_rdev = 0, __pad2 = 0, st_size = 0, st_blksize = 4096, st_blocks = 0, st_atim = {tv_sec = 1338389522, tv_nsec = 269436805}, st_mtim = {tv_sec = 1338389522, tv_nsec = 269436805}, st_ctim = { tv_sec = 1338389522, tv_nsec = 269436805}, st_ino = 1286567453} value = <optimized out> count = 1 __FUNCTION__ = "master_service_init_finish" #9 0x0804a954 in main (argc=1, argv=0x7f98c414) at main.c:232 set_roots = {0x804ee40, 0x0} service_flags = <optimized out> storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT postlogin_socket_path = 0x0 username = 0x0 c = <optimized out> We do some investigation. Restart helped for a moment, but problem was returning. When we back to older kernel - everything back to normal. We compile Dovecot with poll instead of epoll (--with-ioloop=poll) and this works for us. Is any problem with epoll on 3.2.x kernels? Or maybe this is Dovecot problem? Maybe this is not connected with epoll, but epoll is interferes with this. Problem on Dovecot 2.0.11 and 2.0.20. -- Len7hir

2 1

[Dovecot] i can't make DOTS before mailbox names
by John Goodner 30 May '12

30 May '12

hello i have a real stumper of an issue here and need some help! (config posted below) ok, so i'm building out a new mail system with v1.2.15 of dovecot on debian6 this new system is being designed to seamlessly migrate from an older dovecot mail system (v1.1.3). i have everything almost perfect but i've hit a wall which I need help on. so the existing mailboxes on the old server are as such: cur dovecot.index dovecot.index.cache dovecot.index.log dovecot-uidlist dovecot-uidvalidity dovecot-uidvalidity.4fbffa1a .INBOX.Drafts .INBOX.Sent .INBOX.Trash new subscriptions tmp .Trash NOTICE that it puts the . in before INBOX now on the new mailserver I get this: cur dovecot.index.cache dovecot.index.log dovecot-uidlist dovecot-uidvalidity dovecot-uidvalidity.4fc03e57 Drafts INBOX new Sent subscriptions tmp Trash Notice how it's no longer using DOTS before the names. so what i need to do is make the new mail server DUPLICATE EXACTLY the folder layouts of the old server. i've tried fussing with Namespace and the MailDir and especially the PREFIX option which is seems to ignore a '.' to start a filename. i also fussed with the autocreate hoping i could find something there to adjust. but no good. no matter what i do I can't get it to make or read .Trash .Sent .Drafts! please help me! any advice would be appreciated. i'm also willing to hire someone to finish up the config for me. shouldn't take more than a couple hours. thanks! jg here's my config: root@mailserver1:/# dovecot -n # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686 i686 Debian 6.0.5 nfs log_path: /var/log/dovecot.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s 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 mail_location: maildir:/var/vmail/%d/%n@%d:INBOX=/var/vmail/%d/%n@%d:LAYOUT=fs 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 namespace: type: private separator: . prefix: .INBOX. inbox: yes list: yes subscriptions: yes lda: log_path: /var/log/dovecot-deliver.log auth_socket_path: /var/run/dovecot/auth-master postmaster_address: postmaster(a)m.minla.net mail_plugins: sieve global_script_path: /home/vmail/globalsieverc auth default: passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: static args: uid=1010 gid=1010 home=/home/vmail allow_all_users=yes 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: vmail

2 1

[Dovecot] Dovecot-lda - 100% cpu
by For＠ll 30 May '12

30 May '12

Hello, On my MTA server where I have installed postfix+mysql+dovecot(2.0.19), when server receives e.g 1000 e-mails and postfix start 10 threads dovecot-lda then my load is growing up. Disk for e-mails is connected through with iSCSI protocol. Any idea why this is happening?

1 0

Re: [Dovecot] per-mailbox message limits
by Alan Brown 30 May '12

30 May '12

On 29/05/12 16:56, dovecot-request(a)dovecot.org wrote: >> > This is something Timo hacked up for me a few years ago and I realised >> > should be on the list in case anyone else wants them. >> > > Perhaps you should try mdbox some day? If and when I get permission to implement it. (It was hard enough getting permission to move to Maildir format. My manager is a confirmed VMS-head who regards all Unix formats as unreliable and the newer they are the less he trusts them.)

2 1

[Dovecot] v2.1.7 released
by Timo Sirainen 29 May '12

29 May '12

http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz.sig * Session ID is now included by default in auth and login process log lines. It can be added to mail processes also by adding %{session} to mail_log_prefix. + Added ssl_require_crl setting, which specifies if CRL check must be successful when verifying client certificates. + Added mail_shared_explicit_inbox setting to specify if a shared INBOX should be accessible as "shared/$user" or "shared/$user/INBOX". - v2.1.5: Using "~/" as mail_location or elsewhere failed to actually expand it to home directory. - dbox: Fixed potential assert-crash when reading dbox files. - trash plugin: Fixed behavior when quota is already over limit. - mail_log plugin: Logging "copy" event didn't work. - Proxying to backend server with SSL: Verifying server certificate name always failed, because it was compared to an IP address.

2 3

[Dovecot] Different SSL requirements for connections on different ports?
by William Gallafent 29 May '12

29 May '12

Hi All, I'm running dovecot 2.0.19. I currently have remote users access mail using IMAP over SSL, with their client certificates being both required and verified. I do this using "ssl = required" and "ssl_verify_client_cert = yes". I would now like to add a webmail front-end (squirrelmail) running on the same server. In order to achieve this I would like to have squirrelmail connecting locally using IMAP, but without the certificate requirement. I'm happy to use the standard IMAP port for this, since that port is firewalled so that only localhost has access. Do I need to run two separate dovecot instances in order to achieve this, or can I somehow configure different SSL requirements for the two ports? Is there a way to have the ssl directives I mention above active only for a certain port (or for certain hosts, i.e. non-local?) I've been looking around in the documentation, but I haven't yet worked out how to do this other than by having two separate dovecot instances running, with the different auth configurations. Is that the best approach, or can I get it working with only once instance? Thanks for any help! -- Bill Gallafent.

3 3

[Dovecot] Director and backend on the same server
by James Devine 29 May '12

29 May '12

I have setup director and a backend dovecot service on the same machine using different ports. The backend service is listening on the default 24, 110 and 143 for lmtp, pop3 and imap respectively. Director is listening on 10024, 10110 and 10143 for the same respective services. I can get this setup to work if I have one backend server on a different IP listening on 10024, it seems director tries to use the same port it is listening on when making backend connections. If I point it to the local backend server, it tries to connect to itself which fails. Is there a way to specify the backend ports that director tries to connect to? I see there is a way to specify the port in director_servers but I'm not sure how I would specify the different ports for the different backend services, if this is even possible.

2 3

[Dovecot] I can't logon to the mail server using an NIS user account
by Kayode Odeyemi 29 May '12

29 May '12

Below is my configuration # 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 3.0.0-17-server x86_64 Ubuntu 11.10 auth_mechanisms = plain login mail_location = maildir:/nfs/users/%u/Maildir passdb { args = scheme=CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } protocols = " imap pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } ssl_cert = </etc/ssl/certs/mail.prisaltd.local.crt ssl_key = </etc/ssl/private/prisa.key userdb { args = username_format=%u /etc/dovecot/users driver = passwd-file } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep imap_logout_format = bytes=%i/%o mail_plugins = } /etc/pam.d/common-password -------------------------------------------- # here are the per-package modules (the "Primary" block) password [success=1 default=ignore] pam_unix.so obscure sha512 nis # here's the fallback if no module succeeds password requisite pam_deny.so # prime the stack with a positive return value if there isn't one already; # this avoids us returning an error just because nothing sets a success code # since the modules above will each just jump around password required pam_permit.so # and here are more per-package modules (the "Additional" block) password optional pam_ecryptfs.so # end of pam-auth-update config dovecot logs ------------------ May 26 13:14:39 prisa-appserver ntpdate[574]: Can't find host ntp.ubuntu.com: Name or service not known (-2) May 26 13:14:39 prisa-appserver ntpdate[574]: no servers can be used, exiting May 26 13:14:48 prisa-appserver sudo: pam_ecryptfs: pam_sm_authenticate: /home/prisa is already mounted May 26 13:14:50 prisa-appserver kernel: [ 90.418686] CIFS: Unknown mount option - May 26 13:14:50 prisa-appserver kernel: [ 90.472004] CIFS VFS: default security mechanism requested. The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.1 May 26 13:15:44 prisa-appserver ntpdate[1571]: Can't find host ntp.ubuntu.com: Name or service not known (-2) May 26 13:15:44 prisa-appserver ntpdate[1571]: no servers can be used, exiting May 26 13:17:01 prisa-appserver CRON[1678]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) May 26 13:39:01 prisa-appserver CRON[1775]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find /var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib/php5/maxlifetime) ! -execdir fuser -s {} 2>/dev/null \; -delete) May 26 13:46:08 prisa-appserver dovecot: imap-login: Disconnected (auth failed, 3 attempts): user=<prisa>, method=PLAIN, rip=192.168.128.14, lip=192.168.128.15, TLS May 26 13:46:59 prisa-appserver dovecot: imap-login: Aborted login (no auth attempts): rip=192.168.128.14, lip=192.168.128.15 May 26 13:46:59 prisa-appserver dovecot: imap-login: Aborted login (no auth attempts): rip=192.168.128.14, lip=192.168.128.15 May 26 13:46:59 prisa-appserver dovecot: imap-login: Disconnected (no auth attempts): rip=192.168.128.14, lip=192.168.128.15, TLS handshaking: SSL_accept() failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca: SSL alert number 48 May 26 13:46:59 prisa-appserver dovecot: pop3-login: Aborted login (no auth attempts): rip=192.168.128.14, lip=192.168.128.15 May 26 13:46:59 prisa-appserver dovecot: pop3-login: Aborted login (no auth attempts): rip=192.168.128.14, lip=192.168.128.15 May 26 13:46:59 prisa-appserver dovecot: pop3-login: Disconnected (no auth attempts): rip=192.168.128.14, lip=192.168.128.15, TLS handshaking: SSL_accept() failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca: SSL alert number 48 May 26 13:46:59 prisa-appserver dovecot: imap-login: Aborted login (no auth attempts): rip=192.168.128.14, lip=192.168.128.15, TLS May 26 13:46:59 prisa-appserver dovecot: pop3-login: Disconnected (no auth attempts): rip=192.168.128.14, lip=192.168.128.15, TLS May 26 13:47:04 prisa-appserver postfix/smtpd[1820]: connect from unknown[192.168.128.14] May 26 13:47:04 prisa-appserver postfix/smtpd[1820]: improper command pipelining after EHLO from unknown[192.168.128.14] May 26 13:47:04 prisa-appserver postfix/smtpd[1820]: disconnect from unknown[192.168.128.14] May 26 13:47:04 prisa-appserver postfix/smtpd[1830]: connect from unknown[192.168.128.14] May 26 13:47:04 prisa-appserver postfix/smtpd[1830]: lost connection after CONNECT from unknown[192.168.128.14] May 26 13:47:04 prisa-appserver postfix/smtpd[1830]: disconnect from unknown[192.168.128.14] May 26 13:47:22 prisa-appserver dovecot: imap-login: Disconnected (auth failed, 3 attempts): user=<femmy>, method=PLAIN, rip=192.168.128.14, lip=192.168.128.15, TLS May 26 13:47:48 prisa-appserver dovecot: imap-login: Disconnected (auth failed, 3 attempts): user=<femmy(a)mail.prisaltd.local>, method=PLAIN, rip=192.168.128.14, lip=192.168.128.15, TLS May 26 13:48:15 prisa-appserver dovecot: imap-login: Disconnected (auth failed, 3 attempts): user=<femmy>, method=PLAIN, rip=192.168.128.14, lip=192.168.128.15, TLS May 26 13:48:21 prisa-appserver dovecot: imap-login: Disconnected (auth failed, 3 attempts): user=<femmy(a)mail.prisaltd.local>, method=PLAIN, rip=192.168.128.14, lip=192.168.128.15, TLS Please what am I doing wrong? I've been on this for 2 weeks. -- Odeyemi 'Kayode O. http://ng.linkedin.com/in/kayodeodeyemi. t: @charyorde blog: http://sinati.com/tree/java-cheat-sheet

2 2

[Dovecot] Crash on force-resync if / is given as mailbox name
by Daniel Parthey 29 May '12

29 May '12

Hi, when I specify a slash a mailbox name on the command line of doveadm force-resync, it throws a panic. I'm not sure this is considered a bug. mail01:~# doveadm force-resync -u user1(a)example.org / doveadm(user1(a)example.org): Panic: file mailbox-list-fs.c: line 150 (fs_list_get_path): assertion failed: (mailbox_list_is_valid_pattern(_list, name)) doveadm(user1(a)example.org): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x3a7ca) [0x7f1250b797ca] -> /usr/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x32) [0x7f1250b798b2] -> /usr/lib/dovecot/libdovecot.so.0(+0x13e4a) [0x7f1250b52e4a] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x364a7) [0x7f12512384a7] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_mailbox_alloc+0x13c) [0x7f125124a89c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mdbox_mailbox_alloc+0x9a) [0x7f1251258eaa] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_alloc+0x5d) [0x7f125122c8bd] -> doveadm() [0x40a1fb] -> doveadm() [0x40a2c2] -> doveadm() [0x40a753] -> doveadm(doveadm_mail_single_user+0x61) [0x40a811] -> doveadm() [0x40ac4d] -> doveadm(doveadm_mail_try_run+0x141) [0x40b081] -> doveadm(main+0x3b1) [0x410b11] -> /lib/libc.so.6(__libc_start_main+0xfd) [0x7f12503cec4d] -> doveadm() [0x40a009] Aborted mail01:~# echo $? 134 # 2.0.20: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-40-server x86_64 Ubuntu 10.04.4 LTS Regards Daniel

2 1

[Dovecot] Dovecot 2.1 mbox + maildir
by Alan Brown 29 May '12

29 May '12

What syntax is needed to make this work? The 2.0 wiki recomendations don't work - I can see the inboxes or the folders but not both at once and there are lots of error messages about prefix clashes if I simply use the existing 2.0.20 conf file on 2.1.6 The layout I have is: Inboxes in mbox format - /var/spool/mail/%u Folders in maildir format - /var/spool/imap/%u/Maildir/ Control and index folders are under separate trees (/var/spool/control & /var/spool/indexes) There's also a mbox area mainly for moving oversized inboxes (/var/spool/imap/%u/mbox/ - prefixed as OLD) Presumably I'm not the only one who's had problems of this type? Thanks in advance for any help Alan

2 1

[Dovecot] Bug report - crash on group lookup
by Peter Meier 29 May '12

29 May '12

Hi I was doing some migration from a 1.2 installation to a 2.1. While testing my new installation dovecot crashed at two test-cases constantly with with a "Panic: Trying to allocate 0 bytes" message. Both times it was because I was using a wrong group (or none) in my config. The output I got by dovecot was not that helpful. I only figured it out, that it has something to do with the group by looking at the code, to figure out where the stacktrace I got could come from. Unfortunately, I don't remember one of the examples anymore that correctly (except that it was also a group configuration related issue). The other example, was that I was testing the quota warning scripts: Normal delivery worked fine, but as soon as dovecot should send a quota warning, after the mail got already delivered, I received said panic. For the MTA the mail delivery failed (-> bounce), although the LDA already delivered the mail, but failed in post processing (sending the quota warning). My fix was to add: unix_listener quota-warning { group = mail mode = 0660 } to the quota warning service. The LDA process has an own user per mailbox and the mail group. It looks to me as it would panic by looking up the user of the lda process, but that's pure guess. Attached is a debug output and the configuration that triggered the problem. I see two problems: 1. Don't panic while "looking" up a group 2. Give a meaningful error messages. If you have any further questions, please let me know. ~pete ==> /var/log/dovecot/debug.log <== May 25 12:19:50 lda: Debug: Loading modules from directory: /usr/lib/dovecot May 25 12:19:50 lda: Debug: Module loaded: /usr/lib/dovecot/lib10_quota_plugin.so May 25 12:19:50 lda: Debug: Module loaded: /usr/lib/dovecot/lib90_sieve_plugin.so May 25 12:19:50 lda: Debug: auth input: dovecot(a)example.com home=/var/mail/dovecot(a)example.com uid=41407 gid=12 quota_rule=*:storage=1M May 25 12:19:50 lda: Debug: Added userdb setting: plugin/quota_rule=*:storage=1M May 25 12:19:50 lda(dovecot(a)example.com): Debug: Effective uid=41407, gid=12, home=/var/mail/dovecot(a)example.com May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota root: name=User quota backend=maildir args= May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota rule: root=User quota mailbox=* bytes=1048576 messages=0 May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota rule: root=User quota mailbox=INBOX.Trash bytes=+104857 (10%) messages=0 May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota warning: bytes=996147 (95%) messages=0 reverse=no command=quota-warning 95 dovecot(a)example.co, May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota warning: bytes=838860 (80%) messages=0 reverse=no command=quota-warning 80 dovecot(a)example.com May 25 12:19:50 lda(dovecot(a)example.com): Debug: Namespace inbox: type=private, prefix=INBOX., sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:/var/mail/dovecot@example.com May 25 12:19:50 lda(dovecot(a)example.com): Debug: maildir++: root=/var/mail/dovecot(a)example.com/mail, index=, control=, inbox=/var/mail/dovecot(a)example.com/mail, alt= May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota root: name=User quota backend=maildir args= May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota rule: root=User quota mailbox=* bytes=0 messages=0 May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota rule: root=User quota mailbox=INBOX.Trash bytes=0 (10%) messages=0 May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota warning: bytes=0 (95%) messages=0 reverse=no command=quota-warning 95 raw mail ur May 25 12:19:50 lda(dovecot(a)example.com): Debug: Quota warning: bytes=0 (80%) messages=0 reverse=no command=quota-warning 80 raw mail ur May 25 12:19:50 lda(dovecot(a)example.com): Debug: none: root=, index=, control=, inbox=, alt= May 25 12:19:50 lda(dovecot(a)example.com): Debug: Destination address: dovecot(a)example.com (source: -a parameter) May 25 12:19:50 lda(dovecot(a)example.com): Debug: sieve: user's script path /var/mail/dovecot(a)example.com/dovecot.sieve doesn't exist (usinglobal script path in stead) May 25 12:19:50 lda(dovecot(a)example.com): Debug: sieve: using sieve path for user's script: /var/lib/dovecot-sieve/default.sieve May 25 12:19:50 lda(dovecot(a)example.com): Debug: sieve: opening script /var/lib/dovecot-sieve/default.sieve May 25 12:19:50 lda(dovecot(a)example.com): Debug: sieve: script binary /var/lib/dovecot-sieve/default.svbin successfully loaded May 25 12:19:50 lda(dovecot(a)example.com): Debug: sieve: binary save: not saving binary /var/lib/dovecot-sieve/default.svbin, because its already stored May 25 12:19:50 lda(dovecot(a)example.com): Debug: sieve: executing script from /var/lib/dovecot-sieve/default.svbin May 25 12:19:51 lda(dovecot(a)example.com): Debug: quota: Executing warning: quota-warning 80 dovecot(a)example.com ==> /var/log/dovecot/deliver-errors.log <== May 25 12:19:51 lda(dovecot(a)example.com): Panic: Trying to allocate 0 bytes May 25 12:19:51 lda(dovecot(a)example.com): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0xbd4e70] -> /usr/lib/dovecot/libdoveco t.so.0(default_fatal_handler+0x43) [0xbd4f63] -> /usr/lib/dovecot/libdovecot.so.0 [0xbd4784] -> /usr/lib/dovecot/libdovecot.so.0 [0xbd 241d] -> /usr/lib/dovecot/libdovecot.so.0(t_malloc0+0x29) [0xbd2619] -> /usr/lib/dovecot/libdovecot.so.0(restrict_get_groups_list+0x43 ) [0xbef183] -> /usr/lib/dovecot/libdovecot.so.0 [0xbd2b39] -> /usr/lib/dovecot/libdovecot.so.0 [0xbd2dd2] -> /usr/lib/dovecot/libdove cot.so.0 [0xbd34c6] -> /usr/lib/dovecot/lib10_quota_plugin.so(quota_transaction_commit+0x5ff) [0xeeeaff] -> /usr/lib/dovecot/lib10_quo ta_plugin.so [0xef3f6c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit_get_changes+0x42) [0xc922d2] -> /usr/li b/dovecot/libdovecot-storage.so.0(mailbox_transaction_commit+0x33) [0xc92323] -> /usr/lib/dovecot/libdovecot-sieve.so.0 [0xd4cfa4] -> /usr/lib/dovecot/libdovecot-sieve.so.0 [0xd44821] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_result_execute+0x2d1) [0xd44b41] -> /usr/lib/dovecot/libdovecot-sieve.so.0(sieve_execute+0x69) [0xd550f9] -> /usr/lib/dovecot/lib90_sieve_plugin.so [0x11211c] -> /usr/lib /dovecot/libdovecot-lda.so.0(mail_deliver+0x4c) [0x843e1c] -> /usr/libexec/dovecot/deliver(main+0x725) [0x804a185] -> /lib/i686/nosegn eg/libc.so.6(__libc_start_main+0xdc) [0x65ce9c] -> /usr/libexec/dovecot/deliver [0x80498c1] == config # dovecot -n # 2.1.6: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-238.el5xen i686 CentOS release 5.8 (Final) xfs debug_log_path = /var/log/dovecot/debug.log dict { expire = sqlite:/etc/dovecot/dovecot-expire.conf.ext } disable_plaintext_auth = no first_valid_gid = 12 first_valid_uid = 40001 info_log_path = /var/log/dovecot/infos.log lda_mailbox_autocreate = yes log_path = /var/log/dovecot/error.log mail_debug = yes mail_location = maildir:/var/mail/%u/mail maildir_very_dirty_syncs = yes 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 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 = INBOX. } passdb { args = /usr/libexec/dovecot/checkpassword-bcrypt/checkpassword-bcrypt.rb driver = checkpassword } plugin { expire = INBOX.Trash 14 INBOX.Trash/* 14 INBOX.Spam 14 INBOX.spam 14 INBOX.Papierkorb 14 INBOX.Papierkorb/* 14 INBOX.Junk 14 expire_dict = proxy::expire quota = maildir:User quota quota_rule = *:storage=0 quota_rule2 = INBOX.Trash:storage=+10%% quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = ~/dovecot.sieve sieve_default = /var/lib/dovecot-sieve/default.sieve sieve_dir = ~/sieve sieve_global_dir = /var/lib/dovecot-sieve/global/ } postmaster_address = postmaster(a)example.com protocols = imap pop3 sieve service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service quota-warning { executable = script /usr/libexec/dovecot/quota-warning.sh } ssl_cert = </etc/certs/server.crt ssl_cipher_list = HIGH:MEDIUM:!aNULL:!SSLv2:@STRENGTH ssl_key = </etc/certs/server.key userdb { driver = prefetch } userdb { args = /usr/libexec/dovecot/checkpassword-bcrypt/checkpassword-bcrypt.rb driver = checkpassword } version_ignore = yes protocol lda { info_log_path = /var/log/dovecot/deliver.log log_path = /var/log/dovecot/deliver-errors.log mail_plugins = sieve quota } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep mail_max_userip_connections = 30 mail_plugins = expire quota imap_quota } protocol pop3 { mail_plugins = expire quota }

2 1

[Dovecot] Time stamp or expire_stamp not updating to DATABASE table expires in mysql
by Steve Wells 29 May '12

29 May '12

Debian OS Dovecot upgraded from 1.2 to 2.0.18 RoundCubeMail Web Client which uses imap to make connection mysql-server-5.1 version = 5.1.61-0+squeeze1 RoundCubeMail = 0.7.2 As users delete mail in Roundcubemail the database timestamp not entered. The database is blank /var/log/dovecot.log shows no error Do you know where I can look to resolve this problem? If you need any further information/test feel free to ask. Below is dovecot -n, dovecot-dict-expire.conf, and mysql describe of table expire Thanks in advance? Steven Wells Advanced Business Networks wells(a)netabn.com nm2:/var/lib/dovecot# dovecot -n # 2.0.18: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686 i686 Debian 6.0.3 auth_mechanisms = PLAIN LOGIN dict { acl = mysql:/etc/dovecot/dovecot-share-folder.conf expire = mysql:/etc/dovecot/dovecot-dict-expire.conf quotadict = mysql:/etc/dovecot/dovecot-used-quota.conf } disable_plaintext_auth = no first_valid_uid = 1001 last_valid_uid = 1001 listen = * log_path = /var/log/dovecot.log mail_gid = 1001 mail_location = maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/ mail_plugins = " expire" mail_uid = 1001 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 namespace { inbox = yes location = prefix = separator = / type = private } namespace { list = children location = maildir:/%%Lh/Maildir/:INDEX=/%%Lh/Maildir/Shared/%%u prefix = Shared/%%u/ separator = / subscriptions = yes type = shared } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } plugin { acl = vfile acl_shared_dict = proxy::acl auth_socket_path = /var/run/dovecot/auth-master autocreate = INBOX autocreate2 = Sent autocreate3 = Trash autocreate4 = Drafts autocreate5 = Junk autosubscribe = INBOX autosubscribe2 = Sent autosubscribe3 = Trash autosubscribe4 = Drafts autosubscribe5 = Junk expire = Trash 7 Trash/* 7 Junk 30 Sent 30 expire_dict = proxy::expire quota = dict:user::proxy::quotadict quota_rule = *:storage=1G quota_warning = storage=85%% quota-warning 85 %u quota_warning2 = storage=90%% quota-warning 90 %u quota_warning3 = storage=95%% quota-warning 95 %u sieve = /%Lh/sieve/dovecot.sieve sieve_dir = /%Lh/sieve sieve_global_dir = /var/vmail/sieve sieve_global_path = /var/vmail/sieve/dovecot.sieve } protocols = pop3 imap sieve service auth { unix_listener /var/spool/postfix/dovecot-auth { group = postfix mode = 0666 user = postfix } unix_listener auth-master { group = vmail mode = 0666 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service quota-warning { executable = script /usr/local/bin/dovecot-quota-warning.sh unix_listener quota-warning { group = vmail mode = 0660 user = vmail } } ssl_ca = </etc/ssl/certs/gd_bundle.pem ssl_cert = </etc/ssl/certs/nm2.abgnetwork.net.pem ssl_key = </etc/ssl/private/nm2.key userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } protocol lda { auth_socket_path = /var/run/dovecot/auth-master lda_mailbox_autocreate = yes log_path = /var/log/sieve.log mail_plugins = quota sieve autocreate expire postmaster_address = root } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_plugins = quota imap_quota autocreate expire } protocol pop3 { mail_plugins = quota expire pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } cat dovecot-dict-expire.conf connect = host=127.0.0.1 dbname=vmail user=vmail password=********************* map { pattern = shared/expire/$user/$mailbox table = expires value_field = expire_stamp fields { username = $user mailbox = $mailbox } } mysql> describe expires; +--------------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +--------------+--------------+------+-----+---------+-------+ | username | varchar(75) | NO | PRI | NULL | | | mailbox | varchar(255) | NO | PRI | NULL | | | expire_stamp | int(11) | NO | | NULL | | +--------------+--------------+------+-----+---------+-------+ 3 rows in set (0.00 sec)

2 1

[Dovecot] Active Directory : searches in root tree
by nicolasfo 29 May '12

29 May '12

Hello everyone ! I'm trying to make a mail server with dovecot and postfix. Users will authenticate with Active Directory server. I've got an problem with Dovecot. To make the mail server, I'm using IredMail, and I used this tutorial : http://www.iredmail.org/wiki/index.php?title=Integration/Active.Directory.i… here Here's my dovecot-ldap.conf : hosts = dc.domain.lan:389 ldap_version = 3 auth_bind = yes dn = vmail(a)domain.lan dnpass = vmail_passwd base = ou=some_ou,dc=domain,dc=lan scope = subtree deref = never user_filter = (&(userPrincipalName=%u)(objectClass=person)(!(userAccountControl:1.2.840.113556.1.4.803:=2))) pass_filter = (&(userPrincipalName=%u)(objectClass=person)(!(userAccountControl:1.2.840.113556.1.4.803:=2))) user_attrs = =home=/home/mail/%Ld/%Ln/Maildir/,=mail=maildir:/home/mail/%Ld/%Ln/Maildir/ pass_attrs = userPassword=password default_pass_scheme = CRYPT With this configuration file, it works. BUT : To allow Dovecot to find users in my AD database, I must specify an OU in "base". If I only set "dc=domain,dc=lan" the research doesn't work. It seems that Dovecot is not capable to make a research without an OU specified in base. Am I wrong ? The root research works fine with postfix, samba+winbind, and I've an enterprise sized hardware firewall, and it works fine too. I'll be surprised if you tell me that Dovecot can't make a research without OU... That's why I'm posting here.. I've already post about this problem on the Iredmail forum, http://www.iredmail.org/forum/post15184.html#p15184 here , but no solution were found. You're my last hope :) Thanks a lot for replies Nicolas -- View this message in context: http://old.nabble.com/Active-Directory-%3A-searches-in-root-tree-tp33881379… Sent from the Dovecot mailing list archive at Nabble.com.

2 1

[Dovecot] GETQUOTAROOT under roundcube
by Adam Szpakowski 29 May '12

29 May '12

Hi, I'm struggling with the proper quota displaying under roundcube webmail. I've tracked the problem to the different responses on GETQUOTAROOT command. Roundcube aquire quota usage using IMAP command: GETQUOTAROOT INBOX Example dump of the roundcube <-> dovecot communication: > GETQUOTAROOT inbox < QUOTAROOT "inbox" "User quota" < QUOTA "User quota" (STORAGE 1198415 10485760) < OK Getquotaroot completed. The same communication using python imaplib: > GETQUOTAROOT inbox < QUOTAROOT "inbox" "User quota" < QUOTA "User quota" (STORAGE 1431260 10485760) < OK Getquotaroot completed. Quota reported to python client is the same as the one reported to Thunderbird and seems to be the proper one. Python test was performed from the webmail same server, the same user. Can someone point me in the right direction? If there is no explanation on IMAP level i'll move the question to roundcube list. software used: - dovecot: 2.0.15, quota limit set in LDAP, usage tracked in SQL - roundcube: 0.7 - python: 2.6.7 Relevant parts of the dovecot config (taken selectively from different files): quota = dict:User quota::proxy::quota quota_rule2 = Trash:storage=+10%% quota_rule3 = spam:storage=+10%% user_attrs = mailQuota=quota_rule=*:bytes=%$ mail_plugins = quota imap_quota dict { quota = mysql:/etc/dovecot/dovecot-dict-used-quota.conf.ext } #dovecot-dict-used-quota.conf.ext map { pattern = priv/quota/storage table = used_quota username_field = username value_field = bytes } map { pattern = priv/quota/messages table = used_quota username_field = username value_field = messages } -- Adam Szpakowski

2 1

[Dovecot] per-mailbox message limits
by Alan Brown 29 May '12

29 May '12

This is something Timo hacked up for me a few years ago and I realised should be on the list in case anyone else wants them. The following patches will limit maildir folders to 4000 messages on Dovecot 2.0.* and 2.1.* The Specfile patch is against the Cityfan Redhat EL5 SRPM but is likely to work on most build platforms Changing the message limit requires a recompile. It's brutal and ugly but it prevents users overloading FSes that can't cope with huge numbers of files (EG: GFS2)

3 3

[Dovecot] (no subject)
by Phil Petree 29 May '12

29 May '12

Hey All, I'm developing a site on a VPS that comes stock with dovecot 1.2.17 and I'm trying to setup some functionality that is very specific to our business model. My question is this: How do I create (programatically) aliases for a forwarder? I have an address, email(a)domain.com that gets sent to a php script and I want users to be able to send to that script via any number of different names (could ultimately be 1000's). I'm thinking that I append/delete from the etc/aliases file and then run #newaliases So that email(a)domain.com will answer on dummy(a)domain.com or dothis(a)domain.com, once the email comes in, I can check the header, get who it was really sent to, do all my checks, perform the necessary action blah blah blah... and be able to do it all on one piece of code (my fantasy LOL). Am I on the right track here or is this simply not going to work? Thanks, Pete

2 1

[Dovecot] AUTH PLAIN fails while AUTH LOGIN succeeds with Exim -> Dovecot SASL auth
by Sandro Tosi 29 May '12

29 May '12

Hello, we're trying to setup a platform with authenticated SMTP with exim and relying on dovecot as auth agent. We've read http://wiki2.dovecot.org/HowTo/EximAndDovecotSASL and so made the changes mentioned there, also setting auth_mechanisms = plain login in conf.d/10-auth.conf . With this setup, we're able to use AUTH LOGIN method on an SMTP session, but using AUTH PLAIN fails. What we receive in the SMTP session is: auth plain `echo -e -n `\0user\0password' | mimencode` 535 Incorrect authentication data (it's actually the output of that command that we put there), and in the dovecot log we see: 2012-05-24 15:04:20 auth: Debug: client in: AUTH 1 PLAIN service=smtp secured rip=127.0.0.1 lip=127.0.0.1 nologin resp=<hidden> 2012-05-24 15:04:20 auth: Info: plain(?,127.0.0.1): invalid input Do you know where we can look to resolve this problem? If you need any further information/test feel free to ask. Thanks in advance? -- Sandro Tosi Product Engineer Shared Hosting Products R&D | Dada.pro eml sandro.tosi(a)register.it

1 1

[Dovecot] Released Pigeonhole v0.3.1 for Dovecot v2.1.6
by Stephan Bosch 27 May '12

27 May '12

Hello Dovecot users, It's been a few months since the last Pigeonhole release. The main reason is that I've introduced a few big new features. Although the new features themselves probably haven't seen much testing so far, I'm now pretty confident that existing configurations are not broken by these changes. The biggest change is the addition of dict support for Sieve script retrieval. It now possible to fetch Sieve scripts from an SQL database using the Dovecot dict facility. Read the INSTALL file and the referenced additional documentation for more information. Note that this feature currently is not usable with sieve_before/sieve_after and ManageSieve. Additionally, it is now possible to specify multiple sieve_before and sieve_after scripts. This for instance enables administrators to specify both global and user-specific scripts that are to be executed before and after the user's personal script. User-specific scripts configured in sieve_before and sieve_after can not be seen or changed through the ManageSieve protocol. Finally, as promised a while back, I've incorporated the vnd.dovecot.duplicate extension into the main Pigeonhole package. Using this Dovecot-specific extension it is possible to detect duplicate deliveries (such as for example caused by mailing list subscriptions). The detection is based on the message ID and uses the same database file (~/.dovecot.lda-dupes) as the vacation extension. Since the changes introduced in the release are rather large, I strongly advise you to experiment with it a bit before deployment. Changelog v0.3.1: * Added support for retrieving Sieve scripts from dict lookup. This means that Sieve scripts can now be downloaded from a database. Compiled script binaries are still put on disk somewhere if used. The INSTALL documentation is updated with information on this new feature and the (backwards-compatible) changes to the configuration. Note that his feature is currently not supported for sieve_before/sieve_after or script management through ManageSieve. + Incorporated the sieve_duplicate plugin into main Pigeonhole tree as a normal extension (vnd.dovecot.duplicate). This Dovecot-specific extension adds the ability to check for duplicate deliveries based on message ID. Specification can be found in: doc/rfc/spec-bosch-sieve-duplicate.txt + Added support for specifying multiple sieve_before and sieve_after paths. This adds much more flexibility to the multiscript configuration. One application is to have user-specific Sieve scripts outside the user's normal control through ManageSieve. + Added a "session ID" string for managesieve connections, available in %{session} variable (analogous to Dovecot change). - Fixed several small issues, including a few potential segfault bugs, based on static source code analysis. - ManageSieve: changed use of EPROTO error to EIO in ManageSieve string stream implementation because it is apparently not known in BSD. - Gave stamp.h.in (needed for autotools) some content to prevent it from disappearing in patch files. - Fixed bug that caused a SunStudio CC compile failure (reported by Piotr Tarnowski). The release is available as follows: http://www.rename-it.nl/dovecot/2.1/dovecot-2.1-pigeonhole-0.3.1.tar.gz http://www.rename-it.nl/dovecot/2.1/dovecot-2.1-pigeonhole-0.3.1.tar.gz.sig Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

3 5

[Dovecot] Checkpassword Perl LDAP Implementation
by Jeff Hardy 27 May '12

27 May '12

A few years back I hacked up a perl chkpassldap.pl script to authenticate against ldap, and optionally authorize against groups and/or ldap attributes. This works with both qmail and Dovecot, and it also supports a somewhat generic method to alter the environment suitable to use for Dovecot as a prefetch userdb. Anyway, I have been running the script on a qmail-ldap and Dovecot 1.2 proxying cluster using the stock qmail-ldap attributes without any troubles, and figured I would finally release it in the thought someone might find it useful. http://fritz.potsdam.edu/projects/chkpassldap I tried to document the ins and outs of userdb configuration. If anyone finds anything that could use correction or clarification, please let me know. It has been awhile since I was in the middle of it all. Cheers, -Jeff -- Jeffrey Hardy Network / Systems Administrator hardyjm(a)potsdam.edu

1 0

[Dovecot] Dovecot usage values differ from actual disk usage
by Daniel Parthey 26 May '12

26 May '12

Hi, in my dovecot setup the accounting database table shows wrong values which do not correspond with the actual disk space used. The disk usage says 2.6 Gigabytes: mail01:~# du -sh /mail/dovecot/example.org/username 2.6G /mail/dovecot/example.org/username While the doveadm quota get says 7 Gigabytes for the same user: mail01:~# doveadm -f tab quota get -u username(a)example.org Quota name Type Value Limit % User quota STORAGE 7065208 - 0 User quota MESSAGE 282024 - 0 mysql> select * from dovecot.dovecot_usage where username="username(a)example.org"; +----------------------+------------+----------+ | username | storage | messages | +----------------------+------------+----------+ | username(a)example.org | 7234773131 | 282024 | +----------------------+------------+----------+ 1 row in set (0.00 sec) What might be the reason for such huge differences (several gigabytes) between storage value in dovecot_usage table and disk usage value? After a quota recalc everything is correct: mail01:~# doveadm quota recalc -u username(a)example.org mail01:~# doveadm -f tab quota get -u username(a)example.org Quota name Type Value Limit % User quota STORAGE 2630434 - 0 User quota MESSAGE 100714 - 0 mysql> select * from dovecot.dovecot_usage where username="username(a)example.org"; +----------------------+------------+----------+ | username | storage | messages | +----------------------+------------+----------+ | username(a)example.org | 2693565239 | 100714 | +----------------------+------------+----------+ 1 row in set (0.00 sec) How can I keep the accounting data consistent with actual disk usage, without running a recalc cronjob every few hours? There's running a dovecot director and mailbox instance on each of our servers with the mails being stored on NFS and received from postfix via LMTP through the director lmtp port 20024. Configuration of director (dovecot-director.conf) and mailbox (dovecot.conf) is attached. Kind regards Daniel

2 5