- dovecot - dovecot.org

[Dovecot] Fwd: STARTTLS bug - background story
by Robert Schetterer 07 Mar '11

07 Mar '11

-------- Original-Nachricht -------- Betreff: STARTTLS bug - background story Datum: Mon, 7 Mar 2011 15:08:09 -0500 (EST) Von: Wietse Venema <wietse(a)porcupine.org> An: Postfix users <postfix-users(a)postfix.org> CERT/CC announces a flaw today in multiple STARTTLS implementations. This problem was silently fixed in Postfix 2.8 and 2.9. Updates for Postfix 2.[4-7] are made available via the usual channels. Wietse Plaintext injection in multiple implementations of STARTTLS =========================================================== This is a writeup about a flaw that I found recently, and that existed in multiple implementations of SMTP (Simple Mail Transfer Protocol) over TLS (Transport Layer Security) including my Postfix open source mailserver. I give an overview of the problem and its impact, technical background, how to find out if a server is affected, fixes, and draw lessons about where we can expect similar problems now or in the future. A time line is at the end. On-line information is/will be available at: http://www.kb.cert.org/vuls/id/555316 http://www.postfix.org/CVE-2011-0411.html Problem overview and impact =========================== The TLS protocol encrypts communication and protects it against modification by other parties. This protection exists only if a) software is free of flaws, and b) clients verify the server's TLS certificate, so that there can be no "man in the middle" (servers usually don't verify client certificates). The problem discussed in this writeup is caused by a software flaw. The flaw allows an attacker to inject client commands into an SMTP session during the unprotected plaintext SMTP protocol phase (more on that below), such that the server will execute those commands during the SMTP-over-TLS protocol phase when all communication is supposed to be protected. The injected commands could be used to steal the victim's email or SASL (Simple Authentication and Security Layer) username and password. This is not as big a problem as it may appear to be. The reason is that many SMTP client applications don't verify server TLS certificates. These SMTP clients are always vulnerable to command injection and other attacks. Their TLS sessions are only encrypted but not protected. A similar plaintext injection flaw may exist in the way SMTP clients handle SMTP-over-TLS server responses, but its impact is less interesting than the server-side flaw. SMTP is not the only protocol with a mid-session switch from plaintext to TLS. Other examples are POP3, IMAP, NNTP and FTP. Implementations of these protocols may be affected by the same flaw as discussed here. Technical background: SMTP over TLS =================================== For a precise description of SMTP over TLS, see RFC 3207, on-line at http://www.ietf.org/rfc/rfc3207.txt. SMTP over TLS uses the same TLS protocol that is also used to encrypt traffic between web clients and web servers. But, there is a subtle difference in the way TLS is used, and that makes this flaw possible. SMTP sessions over TLS begin with an SMTP protocol handshake in plaintext. Plaintext means no encryption (thus no privacy), and no protection against modification (no integrity). The plaintext handshake is needed because SMTP has always worked this way. Simply skipping this plaintext phase would seriously break internet email. During the plaintext handshake phase, the SMTP server announces whether it is willing to use TLS. If both SMTP client and server support TLS, the client sends a "STARTTLS" request to turn on TLS. Once TLS is turned on, all further traffic is encrypted and protected from modification. The client and server repeat the entire SMTP protocol handshake, and the client starts sending mail. Demonstration ============= The problem is easy to demonstrate with a one-line change to the OpenSSL s_client command source code (I would prefer scripting, but having to install Perl CPAN modules and all their dependencies is more work than downloading a .tar.gz file from openssl.org, adding eight characters to one line, and doing "./config; make"). (The OpenSSL s_client command can make a connection to servers that support straight TLS, SMTP over TLS, or a handful other protocols over TLS. The demonstration here focuses on SMTP over TLS only.) The demonstration with SMTP over TLS involves a one-line change in the OpenSSL s_client source code (with OpenSSL 1.0.0, at line 1129 of file apps/s_client.c). Old: BIO_printf(sbio,"STARTTLS\r\n"); New: BIO_printf(sbio,"STARTTLS\r\nRSET\r\n"); With this change, the s_client command sends the plaintext STARTTLS command ("let's turn on TLS") immediately followed by an RSET command (a relatively harmless protocol "reset"). Both commands are sent as plaintext in the same TCP/IP packet, and arrive together at the server. The "\r\n" are the carriage-return and newline characters; these are necessary to terminate an SMTP command. When an SMTP server has the plaintext injection flaw, it reads the STARTTLS command first, switches to SMTP-over-TLS mode, and only then the server reads the RSET command. Note, the RSET command was transmitted during the plaintext SMTP phase when there is no protection, but the server reads the command as if it was received over the TLS-protected channel. Thus, when the SMTP server has the flaw, the s_client command output will show two "250" SMTP server responses instead of one. The first "250" response is normal, and is present even when the server is not flawed. The second "250" response is for the RSET command, and indicates that the SMTP server has the plaintext injection flaw. $ apps/openssl s_client -quiet -starttls smtp -connect server:port [some server TLS certificate details omitted] 250 some text here <=== Normal response, also with "good" server. 250 more text here <=== RSET response, only with flawed server. How would an attacker exploit this? It would play man-in-the-middle on the connection between SMTP client and server, perhaps using ARP spoofing at a public WIFI access point. Instead of adding a harmless RSET command, it could steal email or authentication credentials. Anatomy of the flaw =================== The flaw is made possible by two ingredients: I already discussed the switch mid-session from plaintext SMTP to SMTP over TLS. This allows an attacker to piggy-back commands onto the SMTP client's plaintext STARTTLS ("let's turn on TLS") request, such that the server may read those commands after the switch to TLS is completed, as if the commands arrived through the TLS-encrypted session. The second ingredient is a layered software architecture through which those piggy-backed commands bubble up from the network to the application. In the case of SMTP, we have the following major layers before and after the switch to TLS: Before switch to TLS After switch to TLS SMTP protocol engine SMTP protocol engine || || TCP/IP protocol engine TLS protocol engine || || Internet TCP/IP protocol engine || Internet Each layer hides details of what is happening inside. Layering makes it easy to switch from plaintext to TLS, with minimal changes to existing code. To insert the TLS layer between the SMTP engine and the O/S TCP/IP engine, simply adjust the plumbing between the layers, and make all information flow through the TLS layer. It's all about the plumbing =========================== Whether a program may have the plaintext injection flaw depends on how it adjusts the plumbing as it inserts the TLS protocol layer in-between the SMTP protocol layer and the O/S TCP/IP protocol layer. I illustrate this with examples from three open source MTAs: Postfix, Sendmail and Exim. The diagram below zooms in on the plumbing between the SMTP and TLS layers, and shows how different MTAs handle the switch from plaintext to TLS. It is best viewed with a fixed-width font (for example, from the Courier family). Postfix MTA Sendmail MTA Exim MTA before/after before/after before/after switch to TLS switch to TLS switch to TLS SMTP SMTP SMTP SMTP SMTP SMTP <= SMTP layer || || || || || || stream stream stream stream' || || buffers buffers buffers buffers' rw r'w' <= stream layer rw r'w' rw r'w' || || || || || || || || || TLS || TLS || TLS <= TLS layer || || || || || || O/S O/S O/S O/S O/S O/S <= TCP/IP layer As shown in the diagram, both Postfix and Sendmail use an application- level stream abstraction, where each stream has properties such as read/write buffers, read/write functions (indicated with rw), and other properties that are omitted for brevity. When Postfix switches to SMTP over TLS, it replaces the plaintext read/write functions (rw) with the TLS read/write functions (r'w'). Postfix does not modify any of the other stream properties including the read/write buffers. A patch for qmail that introduces TLS support uses the same approach. This approach of replacing only the stream read/write functions, but not the buffers or other stream properties, can introduce the plaintext injection flaw. When Sendmail switches to SMTP over TLS, it replaces the entire stream, along with its read/write buffers and read/write functions. Exim. on the other hand, does not have a stream abstraction like Postfix, Sendmail or qmail. Instead of replacing streams or stream properties, Exim replaces plaintext read/write functions with TLS read/write functions. Because of their program structure, Sendmail and Exim didn't suffer from the plaintext injection flaw. Switching world views ===================== When the switch from plaintext to TLS mode is made, all layers above the TLS layer need to purge all information that they have received through the plaintext session. This "world view switch" needs to be implemented consistently. Otherwise, information that was sent as unprotected plaintext may slip through the cracks. In the case of Postfix and other affected MTAs, this "world view switch" was incomplete. Postfix it did not account for information that lingered in stream buffers at the boundary between two layers. This allowed an attacker to piggy-back commands onto the plaintext "let's turn on TLS" request, such that the commands could be read after the switch to TLS was completed, as if they had arrived through the TLS-encrypted session. Fixing the problem ================== There are two solutions to address the flaw, and both solutions can be used together. - Report an error when unexpected plaintext is received after the STARTTLS command. As documented in RFC 3207, STARTTLS must be the last command in a pipelined group. If plaintext commands are received after STARTTLS, then that is a protocol violation. This measure can also be implemented outside the MTA, for example in a protocol-aware firewall. - If a program uses the same input buffer before and after the switch to TLS, it should discard the contents of the input buffer, just like it discards SMTP protocol information that it received during the plaintext protocol phase. Conclusion ========== This plaintext injection problem is likely to recur when some development moves the plaintext-to-ciphertext switch outside the application: for example, into the kernel, into the local hardware, into a proxy, or into other infrastructure. This encourages applications to use the same application-level streams and buffers and read/write functions before and after the switch to ciphertext. When this migration happens, plaintext injection becomes once more a possibility. Postfix did not reject plaintext commands that were piggy-backed onto the plaintext "let's turn on TLS" request. This reflects what once was the primary mission of Postfix: to deliver mail, not to force other systems to implement all the Internet RFCs correctly. Nowadays, strict protocol compliance is becoming a requirement for senders to get their email delivered. As this episode shows, stricter protocol enforcement by receivers can bring security benefits, besides blocking spambots. Time line ========= Jan 5 2011: While finishing Postfix for its annual release, I found this flaw in the server and client implementations of SMTP over TLS. It had been sitting there for six years ever since TLS support was adopted into Postfix. Not wanting to delay the release schedule, I silently fixed the problem and sent an email to co-developer Victor Duchovni. Jan 6-10 2011: As we investigated the scope of the problem, Victor discovered quickly that many other SMTP over TLS implementations were also affected. Among those affected were email service providers, email anti-spam/virus service providers, anti-spam/virus appliances, as well as other mail server implementations. It was clear that this problem's resolution was going to involve many organizations. Jan 11 2011: Contact CERT/CC to help coordinate with the problem's resolution. Mar 7 2011: Public announcement.

1 0

[Dovecot] POP3 with mdbox
by Patrick Domack 07 Mar '11

07 Mar '11

I converted all my box's over to mdbox, from maildir and ran into this issue, I knew exactly what it was and fixed it, but might want to log a config error or something for others to notice the issue. I was running with pop3_uidl_format = %f, and well, that doesn't work with mdbox very well, and when a user ran a UIDL command, it errored the user out. Simple fix, but would probably be nicer to log a config error when started dovecot instead.

1 0

[Dovecot] dovecot 1.2.3: TB fails to unsubscribe folder after deletion
by Max Dittrich 07 Mar '11

07 Mar '11

Hi, I'm running dovecot 1.2.3 with "imap_client_workarounds = tb-extra-mailbox-sep" and noticed that after deleting a folder (moving to Trash and emptying it on exit) that folder in Trash still keeps subscribed. I think the reason for that behavior is that the call for mailbox_list_set_subscribed() in imap/cmd-subscribe.c (line 84) is fed with the original mailbox name and not the stripped version in verify_name. Assigning verify_name to mailbox in the workaround-conditional fixes this issue for me. I'm not very familiar with C programming but while tracing cmd_subscribe_full() I stumbled upon another thing. In mail_namespace_find_mask() (lib-storage/mail-namespace.c at line 413) mailbox is reassigned with a local string (not t_strduped). I think this might be a problem when mailbox is dereferenced after returning from that function?! .max

3 10

[Dovecot] mdbox command line access howto request
by David Favor 07 Mar '11

07 Mar '11

Currently using Maildir in my config for 1.2.16 going to 2.0.11 and wondering about accessing files outside of dovecot. Many files require access by external programs. For example walking a list of receipt files from merchant processors verifying transaction amounts. This requires each file being read + parsed. With mdbox a file may contain multiple messages. Let me know the best command line tool to break mdbox files into a string of messages. Thanks. -- Love feeling your best ever, all day, every day? Click http://RadicalHealth.com for the easy way!

2 2

Re: [Dovecot] auth on tcp socket?
by Hajo Locke 07 Mar '11

07 Mar '11

Hello, > there are some warnings in log: > "when SASL type is "dovecot", SASL path "inet:localhost:1434" should be a > socket pathname" > ( Datei src/xsasl/xsasl_dovecot_server.c ) file xsasl_dovecot_server.c is in postfix sources but was written by you, Timo Should there also made an update to support auth on tcp-socket without warnings from postfix side? Thanks, Hajo

3 3

[Dovecot] Dovecot, Postfix and Dovecot LDA (LMTP) delivery
by Remy Zandwijk 07 Mar '11

07 Mar '11

Hi list, I am running a Debian Lenny machine with Postfix 2.5.5 and Dovecot 2.0.8. Up until now I ran Postfix with the Procmail delivery agent succesfully. The machine has only local users; I am not using virtual mailboxes. Due to obvious reasons I want to switch to Dovecot LDA delivery, through LMTP. I spend quite some time finding 'the' configuration for both Postfix and Dovecot, but without success. Find my current configuration below. Postfix receives the e-mail, but delivery through LMTP fails, resulting in Postfix sending an NDR. I just cannot figure out what's wrong and I am not sure whether it's a Postfix or Dovecot problem either. Some log output from Postfix: Mar 5 13:25:15 hostname postfix/smtpd[12442]: connect from otherhost.domain.tld[aa.bb.cc.dd] Mar 5 13:25:16 hostname postfix/smtpd[12442]: CC47979071: client=otherhost.domain.tld[aa.bb.cc.dd] Mar 5 13:25:16 hostname postfix/cleanup[12447]: CC47979071: message-id=<Pine.GSO.4.64.1103051324570.5319(a)otherhost.domain.tld> Mar 5 13:25:16 hostname postfix/qmgr[12372]: CC47979071: from=<remy(a)otherhost.domain.tld>, size=1037, nrcpt=1 (queue active) Mar 5 13:25:16 hostname postfix/smtpd[12442]: disconnect from otherhost.domain.tld[aa.bb.cc.dd] Mar 5 13:25:16 hostname postfix/lmtp[12448]: CC47979071: to=<remy(a)hostname.domain.tld>, relay=hostname.domain.tld[private/dovecot-lmtp], delay=1.2, delays=1.2/0.01/0.01/0.05, dsn=5.1.1, status=bounced (host hostname.domain.tld[private/dovecot-lmtp] said: 550 5.1.1 <remy(a)hostname.domain.tld> User doesn't exist: remy(a)hostname.domain.tld (in reply to RCPT TO command)) The only lines that Dovecot logs are: Mar 05 13:25:16 lmtp(12449): Info: Connect from local Mar 05 13:25:16 lmtp(12449): Info: Disconnect from local: Client quit Although LMTP should log to /tmp/dovecot-lmtp.log, the file remains empty. Anyone amongst you who is running the same kind of setup and can help? Thanks, Remy Postfix config (postfix -n output) alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases append_dot_mydomain = no biff = no config_directory = /etc/postfix default_transport = smtp inet_interfaces = all local_transport = lmtp:unix:private/dovecot-lmtp mailbox_command = mailbox_size_limit = 0 message_size_limit = 31457280 mydestination = hostname.domain.tld, localhost.domain.tld, localhost myhostname = hostname.domain.tld mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 myorigin = /etc/mailname readme_directory = no recipient_delimiter = + relay_transport = error relayhost = smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) smtpd_client_restrictions = check_client_access hash:/etc/postfix/access, permit_sasl_authenticated, reject_rbl_client zen.spamhaus.org, reject_rbl_client dnsbl.sorbs.net,reject_unauth_pipelining smtpd_helo_required = yes smtpd_helo_restrictions = reject_invalid_helo_hostname,reject_non_fqdn_helo_hostname,reject_unknown_helo_hostname smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_non_fqdn_recipient, reject_unauth_destination, reject_unknown_recipient_domain smtpd_sasl_auth_enable = yes smtpd_sasl_path = private/auth smtpd_sasl_type = dovecot smtpd_sender_restrictions = check_sender_access hash:/etc/postfix/access, reject_non_fqdn_sender, reject_unknown_sender_domain smtpd_tls_auth_only = yes smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtpd_use_tls = yes Dovecot config (dovecot -n output) # 2.0.8: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-amd64 x86_64 Debian 5.0.8 auth_master_user_separator = * listen = * log_path = /var/log/dovecot.log mail_location = maildir:~/.maildir maildir_stat_dirs = 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 namespace { hidden = no inbox = yes list = yes location = prefix = separator = / subscriptions = yes type = private } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap lmtp service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } verbose_proctitle = yes protocol lmtp { info_log_path = /tmp/dovecot-lmtp-info.log log_path = /tmp/dovecot-lmtp.log } protocol imap { mail_plugins = }

2 3

[Dovecot] Dovecot 2.0 in Active-Standby configuration
by Yaron & Hani Nahum 07 Mar '11

07 Mar '11

Hi, I am planning to use Dovecot 2.0 as a Mail server for a Voicemail system. There is not much traffic so I am not concerend about scaling. However redudancy is an issue. I need to have two Dovecot servers installed on two different farms and setup HA between the two. I would prefer that the HA would be automatically. I have two different storage machines with SAN, and I can setup Layer 2 between the two farms. I am concerned with split brain scenario where the two farms are disconnected and both machines would become active. What cluster configuration would you recommend for such an enviroment?

1 0

[Dovecot] Problems with shared folders with Dovecot 1.2.12
by Pašek Ladislav 07 Mar '11

07 Mar '11

Hello, I'm trying to run shared folders with Dovecot 1.2.12. I'm managing ACLs from SOGo and it seemd that it successfully create dovecot-acl and dovecot-acl-list in user maildir. But I cannot see any of these shared folders. In Thunderbird I could see shared folder in Subscriptions but without option to subscribe. I was reading almost everything that was possible to google but without success. My config: [root@mail etc]# dovecot -n # 1.2.12: /etc/dovecot.conf # OS: Linux 2.6.18-194.32.1.el5 x86_64 CentOS release 5.5 (Final) xfs base_dir: /var/run/dovecot/ log_path: /var/log/dovecot/dovecot-deliver.log info_log_path: /var/log/dovecot/dovecot-deliver.log log_timestamp: "%b %d %H:%M:%S protocols: imap imaps managesieve listen(default): *:143 listen(imap): *:143 listen(managesieve): *:2000 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(managesieve): ssl_cert_file: /etc/pki/tls/private/mail.valbek.cz.crt ssl_key_file: /etc/pki/tls/private/privkey.key version_ignore: yes login_dir: /var/run/dovecot//login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(managesieve): /usr/libexec/dovecot/managesieve-login login_greeting: Welcome to Dovecot eMail Server. login_log_format: %$: %s %u login_process_size: 128 login_processes_count: 5 login_max_processes_count: 140 mail_max_userip_connections(default): 30 mail_max_userip_connections(imap): 30 mail_max_userip_connections(managesieve): 10 verbose_proctitle: yes first_valid_uid: 306 last_valid_uid: 306 first_valid_gid: 306 last_valid_gid: 306 mail_uid: vmail mail_gid: vmail mail_location: maildir:/mnt/pole/mail/valbek.cz/%u mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(managesieve): /usr/libexec/dovecot/managesieve mail_plugins(default): acl imap_acl mail_plugins(imap): acl imap_acl mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(managesieve): /usr/lib64/dovecot/managesieve imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(managesieve): managesieve_logout_format(default): bytes=%i/%o managesieve_logout_format(imap): bytes=%i/%o managesieve_logout_format(managesieve): bytes ( in=%i : out=%o ) namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: shared separator: / prefix: sdilene/%%u/ location: maildir:/mnt/pole/mail/valbek.cz/%%u:INDEX=/mnt/pole/mail/valbek.cz/%%u/sdilene/%%u list: children lda: postmaster_address: it(a)valbek.cz mail_plugins: sieve acl auth default: mechanisms: plain login passdb: driver: ldap args: /etc/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot-ldap.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: mail plugin: autocreate: Spam autocreate2: NoSpam autocreate3: Archiv sieve: /mnt/pole/mail/valbek.cz/%u/.dovecot.sieve sieve_storage: /mnt/pole/mail/valbek.cz/%u/sieve sieve_global_dir: /var/lib/dovecot/sieve/global/ fts: squat fts_squat: partial=4 full=10 acl: vfile acl_shared_dict: file:/var/lib/dovecot/shared-mailboxes.db >From log: "Mar 05 15:25:16imap-login: Info: Login: user=<pasek(a)valbek.cz>, method=PLAIN, rip=192.168.1.221, lip=192.168.1.254 "Mar 05 15:25:16IMAP(pasek@valbek.cz): Info: Loading modules from directory: /usr/lib64/dovecot/imap "Mar 05 15:25:16IMAP(pasek@valbek.cz): Info: Module loaded: /usr/lib64/dovecot/imap/lib01_acl_plugin.so "Mar 05 15:25:16IMAP(pasek@valbek.cz): Info: Module loaded: /usr/lib64/dovecot/imap/lib02_imap_acl_plugin.so "Mar 05 15:25:16IMAP(pasek@valbek.cz): Info: Effective uid=306, gid=306, home=(none) "Mar 05 15:25:16IMAP(pasek@valbek.cz): Info: Namespace: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes "Mar 05 15:25:16IMAP(pasek@valbek.cz): Info: maildir: data=/mnt/pole/mail/valbek.cz/pasek(a)valbek.cz "Mar 05 15:25:16IMAP(pasek@valbek.cz): Info: maildir++: root=/mnt/pole/mail/valbek.cz/pasek(a)valbek.cz, index=, control=, inbox=/mnt/pole/mail/valbek.cz/pasek(a)valbek.cz "Mar 05 15:25:16IMAP(pasek@valbek.cz): Info: acl: initializing backend with data: vfile "Mar 05 15:25:16IMAP(pasek@valbek.cz): Info: acl: acl username = pasek(a)valbek.cz "Mar 05 15:25:16IMAP(pasek@valbek.cz): Info: acl: owner = 1 "Mar 05 15:25:16IMAP(pasek@valbek.cz): Info: acl vfile: Global ACL directory: (null) "Mar 05 15:25:16IMAP(pasek@valbek.cz): Info: Namespace: type=shared, prefix=sdilene/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=no "Mar 05 15:25:16IMAP(pasek@valbek.cz): Info: shared: root=, index=, control=, inbox= "Mar 05 15:25:16IMAP(pasek@valbek.cz): Info: acl vfile: reading file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/dovecot-acl "Mar 05 15:25:16IMAP(pasek@valbek.cz): Info: Namespace : Using permissions from /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz: mode=0700 gid=-1 "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.Trash/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.Trash.TuX/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.Sent/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.Sent.Archiv/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.Sent.Po&AWE-ta &AWA-vejda/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.Spam/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.NoSpam/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: reading file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.Prodex/dovecot-acl "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.dovecot/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: reading file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.Autodesk/dovecot-acl "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.ebay/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.Hesla/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: reading file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.Intranet/dovecot-acl "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.&AX4-ivotopisy/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.Archiv/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.Archiv.RIB-Service/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.Archiv.Po&AWE-ta &AWA-vejda/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.Archiv.Osobn&AO0- po&AWE-ta/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.spr&AOE-va-IT/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.Blbosti/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.V&AWA-B/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: reading file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.SCST/dovecot-acl "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.PPP-R1/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: reading file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.SOGo/dovecot-acl "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.Nexenta/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.openldap/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.INBOX.Pron&AOE-jmy/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.Drafts/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.Archiv/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.Nevy&AX4A4Q-dan&AOE- po&AWE-ta/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.Odstran&ARs-n&AOE- po&AWE-ta/dovecot-acl not found "Mar 05 15:25:19IMAP(pasek@valbek.cz): Info: acl vfile: file /mnt/pole/mail/valbek.cz/pasek(a)valbek.cz/.Odeslan&AOE- po&AWE-ta/dovecot-acl not found Thanks in Advance Ladislav

2 1

[Dovecot] v2.0.11 released
by Timo Sirainen 07 Mar '11

07 Mar '11

http://dovecot.org/releases/2.0/dovecot-2.0.11.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.11.tar.gz.sig Looks like v2.0.10 was a bit troublesome release. I expect this one to last longer. * dotlock_use_excl setting's default was accidentally "no" in all v2.0.x releases, instead of "yes" as in v1.1 and v1.2. Changed it back to "yes". - v2.0.10: LDAP support was broken - v2.0.10: dsyncing to remote often hanged (timed out in 15 mins)

1 0

[Dovecot] OT auto delete attachments with sieve
by Robert Schetterer 07 Mar '11

07 Mar '11

Hi , off topic , but anyone with an idea how to autodelete attachments from mail with sieve, as far i investigated this , it can only be done indirectly perhaps per size etc, but there is no direct auto way, am i right here ? or someone has magic...? -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

1 0

[Dovecot] 2.0.10 Auth failed while binding ldap
by Stéphane Wartel 06 Mar '11

06 Mar '11

Everything is ok, Thanks Timo ;)

1 0

Re: [Dovecot] Multiple Concurrent IMAP Connections For Same User
by Knute Johnson 06 Mar '11

06 Mar '11

On 03/05/2011 07:45 PM, Stan Hoeppner wrote: > If you're not doing local sync with TB and you have GLODA disabled, > TB is going to show you exactly what's in your Dovecot mailbox. If > the message doesn't disappear from your TB view sometime after > deleting it on your smartphone, then I'd say it's very likely that > Dovecot didn't receive the delete and/or expunge command from the > phone. Check your Dovecot logs and see what the phone is actually > sending, or not sending. > > Both of you mentioned problems specifically WRT smartphones. It's > likely the IMAP implementation in these phones is simply buggy, or > your network coverage is spotty. I don't use a smartphone so I can't > really say. What smartphone are you each using? I've got a Samsung Captivate running K-9 Mail. It could definitely have some bugs. Sometimes if I delete a message on my phone, I'll see it show up in the Trash folder but not disappear from the folder it was deleted from. It's just not consistent. but it is better than it was before. I'll look in the logs and see if I see anything interesting. Thanks again,

1 0

[Dovecot] Dovecot MySQL Schema
by Alokat 06 Mar '11

06 Mar '11

Hi, where can I find the MySQL schema for Dovecot on Debian? Regards, alokat

2 1

[Dovecot] Multiple Concurrent IMAP Connections For Same User
by Nigel Webber 05 Mar '11

05 Mar '11

Hi I've been using courier for some time, but have just built a new box and am using dovecot (V1.2.9), Ubuntu 10.04LTS. I have a question regarding multiple concurrent imap connections and how to get dovecot to behave in the same way that courier does. I have searched the wiki, but find little relevant to my specific issue. Courier-Imap Behaviour If I have thunderbird pointed at the 'Inbox' folder via IMAP, then connect another IMAP client to the same mail account (in this case an iPhone), and then delete an email using the iphone, then after a couple of seconds, the inbox shown by Thunderbird updates, removing the now deleted email. It does this without my having to touch Thunderbird. Dovecot behaviour Performing the same test on a different mailbox, this time hosted via Dovecot, I again see the two views, one in Thunderbird and one on the iPhone, but when I delete the email on the iPhone, the change is not reflected in the view on Thunderbird. If I select the email on Thunderbird, then it has no content. If I restart thunderbird, the deleted email is still shown. I have to delete (the already deleted) the email also in thunderbird before it finally dissapears. How can I get the courier behaviour where the inbox in one email client automagically reflects the changes made to that inbox in another client? If I am better sticking to Courier to get this functionality, thats fine, but if I can configure the behaviour I desire and still retail the benefits of dovecot then thats even better! Kind Regards Nigel

7 12

[Dovecot] 2.0.10 Auth failed while binding ldap
by Stéphane Wartel 05 Mar '11

05 Mar '11

Dear all, Since new release has been installed, auth process crash with io loop : 2011-03-05 11:22:44 auth: Panic: file db-ldap.c: line 1113 (db_ldap_result_change_attr): assertion failed: (ctx->vals == NULL) 2011-03-05 11:22:44 auth: Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0xb76ceab1] -> /usr/lib/dovecot/libdovecot.so.0 [0xb76ceb2f] -> /usr/lib/dovecot/libdovecot.so.0(i_error+0) [0xb76cee04] -> dovecot/auth(db_ldap_result_iterate_next+0x3be) [0x806aa8e] -> dovecot/auth [0x806c857] -> dovecot/auth [0x806cd91] -> dovecot/auth [0x806c314] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x51) [0xb76db781] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xe0) [0xb76dc840] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0xb76db700] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x2a) [0xb76c73da] -> dovecot/auth(main+0x300) [0x805ea50] -> /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7147455] -> dovecot/auth [0x8052a51] 2011-03-05 11:22:44 master: Error: service(auth): child 23136 killed with signal 6 (core dumps disabled) 2011-03-05 11:22:44 master: Error: service(auth): command startup failed, throttling dovecot --version 2.0.10 (d757b13d84ff) # 2.0.10 (d757b13d84ff): /etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-686 i686 Debian 5.0.8 auth_failure_delay = 5 secs auth_mechanisms = plain login debug_log_path = /var/log/dovecot-debug.log dict/acl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext info_log_path = /var/log/dovecot-info.log lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = 127.0.0.1 log_path = /var/log/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " mail_access_groups = mail mail_debug = yes mail_fsync = always mail_gid = mail mail_location = maildir:~/Maildir mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = " quota trash zlib" mail_uid = vmail 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 mmap_disable = yes namespace { inbox = yes location = prefix = separator = . type = private } namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/Shared/%%n prefix = Shared.%%n. separator = . subscriptions = no type = shared } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin/acl = vfile plugin/acl_shared_dict = proxy::acl plugin/autocreate = Junk plugin/autosubscribe = Junk plugin/quota = maildir:User quota plugin/quota_rule2 = Trash:storage=+100M plugin/quota_warning = storage=95%% quota-warning 95 %u plugin/quota_warning2 = storage=80%% quota-warning 80 %u plugin/sieve = ~/.dovecot.sieve plugin/sieve_before = /etc/dovecot/global_script/dovecot.sieve plugin/sieve_dir = ~/sieve plugin/trash = /etc/dovecot/dovecot-trash.conf.ext plugin/zlib_save = bz2 plugin/zlib_save_level = 6 postmaster_address = postmaster protocols = imap pop3 lmtp sieve quota_full_tempfail = yes service auth { unix_listener /var/spool/postfix/private/auth { group = mail mode = 0660 user = postfix } unix_listener auth-master { group = mail mode = 0660 user = vmail } unix_listener auth-userdb { group = mail mode = 0660 user = vmail } } service dict { unix_listener dict { group = mail mode = 0660 user = vmail } } service imap-login { process_min_avail = 10 service_count = 1 } service managesieve-login { process_min_avail = 3 service_count = 1 } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = vmail } user = dovecot } ssl_ca = </etc/ssl/certs/GandiStandardSSLCA.pem ssl_cert = </etc/ssl/certs/imap.zero-spam.fr.pem ssl_key = </etc/ssl/private/imap.zero-spam.fr.key userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap } protocol lda { auth_socket_path = /var/run/dovecot/auth-master mail_plugins = " quota trash zlib sieve autocreate acl" } protocol imap { mail_plugins = " quota trash zlib acl imap_quota imap_acl imap_zlib" } protocol sieve { managesieve_logout_format = bytes=%i/%o 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 } dovecot-ldap.conf.ext hosts = 127.0.0.1 dn = "cn=sup,dc=domain,dc=com" dnpass = "**********" auth_bind = yes ldap_version = 3 base = dc=domain, dc=com user_attrs = mailbox=home,mailuserquota=quota_rule=*:storage user_filter = (&(objectClass=mailAccount)(mail=%u)(mailenable=OK)) pass_attrs = mail=user,userPassword=password pass_filter = (&(objectClass=mailAccount)(mail=%u)(mailenable=OK)) iterate_attrs = mail=user iterate_filter = (&(objectClass=mailAccount)(mailenable=OK)) Hope this could help you ! Many thanks by advance, Stephane

3 3

[Dovecot] deleted messages not going away in Thunderbird?
by Dave McGuire 05 Mar '11

05 Mar '11

Hi folks. This may be a dumb question, but I can't seem to find a clue. I'm running Dovecot v1.2.9 and Thunderbird v3.1.7. If I delete messages using a different IMAP client (I also use an iPhone and occasionally SquirrelMail), I would expect those messages to disappear from Thunderbird the next time I start it or click on "Get Mail". In fact, they do...most of the time. Sometimes, however, they just stick around. If I do a "Repair Folder" on the inbox in Thunderbird, the messages go away. Is this a known issue? My gut tells me there's some Thunderbird option to make it follow inbox contents with more "attention" but I've not been able to find it. Thanks, -Dave -- Dave McGuire Port Charlotte, FL

2 1

[Dovecot] version difference understanding
by upen 05 Mar '11

05 Mar '11

Hello, I am in process of setting up an IMAP server (with postfix SMTP), I installed RHEL 5.5 on my server and found that version of dovecot is 1.x.x while when I checked online RHEL 6 is version is 2.x.x. Can someone please tell me if these two versions are still in development or 1.x.x is very old and must be replaced by 2.x.x version? Also are there any special features in 2.x.x or 1.x.x that makes it better than other? I see similar things for postfix package but I understand this is not the place to ask postfix Qns, Appreciate your help! ~A

2 2

[Dovecot] All mails unread after short while
by francwalter＠gmx.net 05 Mar '11

05 Mar '11

Hello, I have on Ubuntu 8.04 Postfix 2.5.1 and Dovecot 1.0.10. The mails are saved in maildir format. In one account on my server all mails are unread all the time. If i set them as read in my client (IMAP with Mac Mail 4.4 or IMAP with Squirrelmail, it doesn’t matter) they seem to be checked as read for some minutes or less, but very soon they are unread again, so i guess, only my client thinks that they are read, but after the next check, the client reads again that they are unread. Now i don’t know where to look or change the “Has been read”-Flag in the maildir-directory. Is it in some file or where is it, the flag? It is only one account, the other accounts on the same domain and on other domains are working quite well. Maybe it is only after a Squirrelmail update last week, but I am not sure. Thank you, Kind Regards, frank walter

4 7

[Dovecot] Is the trunk version of Pigeonhole still broken or am I missing something?
by interfaSys sàrl 05 Mar '11

05 Mar '11

Things broke a couple of months back and I thought I had caught the repository at a bad time, but trying again today, after having seen that people had been working on it recently, bore the same result. ../../../../libtool: line 2072: cmd-vacation.c: command not found I'm simply syncing with the repository and using autogen, configure and make. Are there any other steps required? Olivier

2 5

[Dovecot] v2.0.10 released
by Timo Sirainen 04 Mar '11

04 Mar '11

http://dovecot.org/releases/2.0/dovecot-2.0.10.tar.gz http://dovecot.org/releases/2.0/dovecot-2.0.10.tar.gz.sig I thought it was finally time to make a new v2.0 release. Or probably it was a while ago already, but I've been a bit lazy this year. Maybe it's because this is the first time in last 5 years when all branches of Dovecot have been quite stable and I haven't been stressing on it. Of course there are some v2.0 features that still have some bugs, but few people are complaining about them. v2.1 development branch also appears to be pretty good shape. I'm hopeful that v2.1.rc1 will be out before summer. * LMTP: For user+detail@domain deliveries, the +detail is again written to Delivered-To: header. * Skip auth penalty checks from IPs in login_trusted_networks. + Added import_environment setting. + Added submission_host setting to send mails via SMTP instead of via sendmail binary. + Added doveadm acl get/set/delete commands for ACL manipulation, similar to how IMAP ACL extension works. + Added doveadm acl debug command to help debug and fix problems with why shared mailboxes aren't working as expected. - IMAP: Fixed hangs with COMPRESS extension - IMAP: Fixed a hang when trying to COPY to a nonexistent mailbox. - IMAP: Fixed hang/crash with SEARCHRES + pipelining $. - IMAP: Fixed assert-crash if IDLE+DONE is sent in same TCP packet. - LMTP: Fixed sending multiple messages in a session. - doveadm: Fixed giving parameters to mail commands. - doveadm import: Settings weren't correctly used for the import storage. - dsync: Fixed somewhat random failures with saving messages to remote dsync. - v2.0.9: Config reload didn't notify running processes with shutdown_clients=no, so they could have kept serving new clients with old settings.

2 2

Re: [Dovecot] Error: FETCH [1] for mailbox badbox UID 1 got too little data: 2 vs 4 (fwd)
by Chris Wilson 04 Mar '11

04 Mar '11

Hi all, Any thoughts about this error? Should I file a bug report somewhere? Cheers, Chris. On Wed, 12 Jan 2011, Chris Wilson wrote: > Hi all, > > I can send myself a test message that causes Dovecot to crash when I open > it in Alpine, with the following error: > > Jan 12 14:52:52 one-mail dovecot: imap(chris): Error: FETCH [1] for > mailbox badbox UID 1 got too little data: 2 vs 4 > Jan 12 14:52:52 one-mail dovecot: imap(chris): Error: Corrupted index > cache file /home/chris/mail/.imap/badbox/dovecot.index.cache: Broken > MIME parts for mail UID 1 > Jan 12 14:52:52 one-mail dovecot: imap(chris): Disconnected: FETCH failed > bytes=485/1394 > > I can do this as follows: > > $ touch ~/mail/badbox > $ echo test | /usr/libexec/dovecot/dovecot-lda -m badbox > $ cat ~/mail/badbox > > From MAILER-DAEMON Wed Jan 12 14:52:29 2011 > test > X-IMAPbase: 1294843949 0000000001 > X-UID: 1 > Status: > X-Keywords: > Content-Length: 1 > > And then when I try to open badbox in Alpine (over IMAP), and then open > this email, I get the error above, and the connection is aborted. > > I expect that the "test" line is not a valid header, but dovecot should > not crash when opening it. > > Cheers, Chris. > -- Aptivate | http://www.aptivate.org | Phone: +44 1223 760887 The Humanitarian Centre, Fenner's, Gresham Road, Cambridge CB1 2ES Aptivate is a not-for-profit company registered in England and Wales with company number 04980791.

2 1

[Dovecot] /etc/pam.d/dovecot missing? during high load
by Douglas Mortensen 04 Mar '11

04 Mar '11

This morning on our newly built server, the following was logged twice: auth: Error: pam(username,127.0.0.1): pam_authenticate() failed: Authentication failure (/etc/pam.d/dovecot missing?) This also happened to be during a time of 100+ imap-login processes, where we were seeing: master: Warning: service(imap-login): process_limit reached, client connections are being dropped The initial error was correct, in that I had not yet created /etc/pam.d/dovecot. I have since created the file. However, we brought this server into production yesterday & there were no complaints, nor was the error logged besides twice this morning within 3.5 minutes of eachother. In looking at pam documentation, it is my understanding that when a service (dovecot) does not have its own file existing under /etc/pam.d, then pam will instead use the settings from /etc/pam.d/others as defaults. This seems logical to me, and would explain why things have been working fairly well with no errors regarding pam (other than the 2 logged this morning). However, what this does not explain, is why dovecot auth logged about the file missing at all. I can only guess that it was related to logins being dropped due to high load, and was incorrectly logged?? For reference, my current /etc/pam.d/dovecot is: auth required pam_unix.so nullok account required pam_unix.so My current /etc/pam.d/other is: @include common-auth @include common-account @include common-password @include common-session Which results in (confirmed via : grep -v ^# common-auth common-account common-password common-session) auth [success=1 default=ignore] pam_unix.so nullok_secure auth requisite pam_deny.so auth required pam_permit.so account [success=1 new_authtok_reqd=done default=ignore] pam_unix.so account requisite pam_deny.so password [success=1 default=ignore] pam_unix.so obscure sha512 password requisite pam_deny.so password required pam_permit.so session [default=1] pam_permit.so session requisite pam_deny.so session required pam_permit.so session required pam_unix.so So there definitely is quite a difference between the dovecot pam file I created (based on the dovecot2 wiki), and the system default (other). I don't know whether this could have been related, so I figured I'd share. Otherwise, I'm running dovecot 2.0.9 compiled from source. dovecot -n at the time of the pam errors was probably: # 2.0.9: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0 auth_debug = yes auth_mechanisms = plain login disable_plaintext_auth = no log_timestamp = "%Y-%m-%d %H:%M:%S " mail_debug = yes mail_location = maildir:~/ mail_privileged_group = mail passdb { driver = pam } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } ssl_cert = </etc/ssl/certs/jlgray.com.cer ssl_key = </etc/ssl/private/jlgray.com.key userdb { driver = passwd } Thanks, - Doug Mortensen Network Consultant Impala Networks Inc CCNA, MCSA, Security+, A+ Linux+, Network+, Server+ . www.impalanetworks.com P: (505) 327-7300 F: (505) 327-7545

2 2

[Dovecot] logging issues w/ login_max_processes_count on 1.x
by Douglas Mortensen 04 Mar '11

04 Mar '11

Today I found our dovecot 2.x gracefully logged: dovecot: master: Warning: service(imap-login): process_limit reached, client connections are being dropped I am confident that we had the very same problem on our previous dovecot 1.x box. Of course with dovecot 1.x, the same relative setting is login_max_processes_count. I believe that I turned up all dovecot logging & debugging to the max (also checked with the 1.x wiki), but nothing was ever logged relating to this. Does anyone know whether there is a way to get dovecot 1.x to log this type of error? Thanks, - Doug Mortensen Network Consultant Impala Networks Inc CCNA, MCSA, Security+, A+ Linux+, Network+, Server+ . www.impalanetworks.com P: (505) 327-7300 F: (505) 327-7545

2 2

[Dovecot] penalty configuration and proxy servers
by Mark Zealey 04 Mar '11

04 Mar '11

Hi there, I've had a look through the wiki and a quick look through the source for penalty configurations (dovecot 2.0.9) but I've not found anything to do with configuration options for this functionality. I'm basically wanting to disable a particular host/subnet from the penalty setup. In our case we have some webmail servers that do get attacked however most of the traffic is legitimate so I'd rather that the user experience was faster (ie not having a few seconds of delay on login) than that we slowed down attacks from them. On a similar note; is it possible to do the per-ip login limit in the auth level rather than the imap/pop level? I ask this as we've just implemented a proxy setup whereby we have two frontend proxy servers that then dispatch to backend servers specified in the database. So, the backend servers do the actual imap/pop sessions however we now don't see the remote ip addresses so it becomes difficult to limit abusive users. The 'doveadm who'/process listing code also doesn't work on the proxy servers even though dovecot knows who logged in and forwards the connection through to the backend servers. None of these features/suggestions are show-stoppers; dovecot is a great program however they're more suggestions of ways it would be useful for us to improve the software. Thanks, Mark

2 1

[Dovecot] strange problem receiving mails
by deconya 04 Mar '11

04 Mar '11

Hi guys Im viewing how to repair a problem using a postfix platform with openldap and dovecot. This is the problem: -When I create a new user inside openldap with mail account appears correctly inside ldap but when I access first time appears inside /var/spool/dovecot/ the folder of account bad. Not appears the name of uid, appears the name of user mail, for ex: drwx------ 5 exemple Domain Users 4,0K 2011-03-04 13:28 exemple drwx------ 9 exemple Domain Users 4,0K 2011-03-04 13:29 exemple.usermail Log filteered: Mar 4 13:28:21 mailserver deliver(exemple): Loading modules from directory: /usr/lib/dovecot/modules/lda Mar 4 13:28:21 mailserver deliver(exemple): Module loaded: /usr/lib/dovecot/modules/lda/ lib10_quota_plugin.so Mar 4 13:28:21 mailserver dovecot: auth(default): master in: USER^I1^Iunesco^Iservice=deliver Mar 4 13:28:21 mailserver dovecot: auth(default): prefetch( exemple(a)mydomain.com) passdb didn't return userdb entries, trying the next userdb Mar 4 13:28:21 mailserver dovecot: auth(default): passwd( exemple(a)mydomain.com) lookup Mar 4 13:28:21 mailserver dovecot: auth(default): passwd( exemple(a)mydomain.com) unknown user Mar 4 13:28:21 mailserver dovecot: auth(default): ldap(exemple(a)mydomain.com): user search: base=ou=Users, dc=ldap, dc=es scope=subtree filter=(&(objectClass=posixAccount)(|(mail=exemple(a)mydomain.com)(uid= exemple(a)mydomain.com)(uid=exemple))) fields=homeDirectory,uidNumber,gidNumber,mailQuota Mar 4 13:28:21 mailserver deliver(exemple): auth input: home=/home/exemple Mar 4 13:28:21 mailserver deliver(exemple): auth input: uid=10017 Mar 4 13:28:21 mailserver deliver(exemple): auth input: gid=513 Mar 4 13:28:21 mailserver deliver(exemple): Home dir not found: /home/exemple Mar 4 13:28:21 mailserver deliver(exemple): Quota root: name=User quota backend=maildir args= Mar 4 13:28:21 mailserver deliver(exemple): Quota rule: root=User quota mailbox=* bytes=52428800 messages=0 Mar 4 13:28:21 mailserver deliver(exemple): Quota rule: root=User quota mailbox=Trash ignored Mar 4 13:28:21 mailserver deliver(exemple): maildir: data=/var/spool/dovecot/exemple/ Mar 4 13:28:21 mailserver deliver(exemple): maildir++: root=/var/spool/dovecot/exemple, index=, control=, inbox=/var/spool/dovecot/exemple Mar 4 13:28:21 mailserver dovecot: auth(default): ldap(exemple(a)mydomain.com): result: homeDirectory(home)=/home/exemple uidNumber(uid)=10017 gidNumber(gid)=513 Mar 4 13:28:21 mailserver dovecot: auth(default): master out: USER^I1^ Iunesco(a)mydomain.com^Ihome=/home/exemple^Iuid=10017^Igid=513 Mar 4 13:28:21 mailserver deliver(exemple): msgid=<1299241700.26848.1.camel@infolinux>: saved mail to INBOX Mar 4 13:28:21 mailserver postfix/pipe[29996]: 6191E26F95B: to=< exemple(a)mydomain.com>, orig_to=<exemplemail(a)admi.mydomain.com>, relay=dovecot, delay=0.09, delays=0.03/0/0/0.06, dsn=2.0.0, status=sent (delivered via dovecot service) Mar 4 13:28:26 mailserver dovecot: auth-worker(default): pam( exemplemail(a)mydomain.com,10.0.0.4) lookup service=dovecot Mar 4 13:28:26 mailserver dovecot: auth-worker(default): pam( exemplemail(a)mydomain.com,10.0.0.4) #1/1 style=1 msg=Password: Mar 4 13:28:28 mailserver dovecot: auth-worker(default): pam( exemplemail(a)mydomain.com,10.0.0.4) pam_authenticate() failed: Authentication failure (password mismatch?) Mar 4 13:28:28 mailserver dovecot: auth(default): ldap( exemplemail(a)mydomain.com,10.0.0.4) bind search: base=ou=Users, dc=ldap, dc=es filter=(&(objectClass=posixAccount)(|(mail=exemplemail(a)mydomain.com )(uid=exemplemail(a)mydomain.com))) Mar 4 13:28:28 mailserver dovecot: auth(default): auth( exemplemail(a)mydomain.com,10.0.0.4) username changed exemplemail(a)mydomain.com -> exemple Mar 4 13:28:28 mailserver dovecot: auth(default): ldap(exemple,10.0.0.4): result: homeDirectory(userdb_home)=/home/exemple uid(user)=exemple uidNumber(userdb_uid)=10017 gidNumber(userdb_gid)=513 Mar 4 13:28:28 mailserver dovecot: auth(default): client out: OK^I1^Iuser=exemple Mar 4 13:28:28 mailserver dovecot: auth(default): prefetch(exemple,10.0.0.4): success Mar 4 13:28:28 mailserver dovecot: auth(default): master out: USER^I411619^ Iunescochair.lccc(a)mydomain.com^Ihome=/home/exemple^Iuid=10017^Igid=513 Mar 4 13:28:28 mailserver dovecot: imap-login: Login: user=<exemple>, method=PLAIN, rip=10.0.0.4, lip=10.0.0.5 Mar 4 13:28:28 mailserver dovecot: IMAP(exemplemail(a)mydomain.com): Loading modules from directory: /usr/lib/dovecot/modules/imap Mar 4 13:28:28 mailserver dovecot: IMAP(exemplemail(a)mydomain.com): Module loaded: /usr/lib/dovecot/modules/imap/lib10_quota_plugin.so Mar 4 13:28:28 mailserver dovecot: IMAP(exemplemail(a)mydomain.com): Module loaded: /usr/lib/dovecot/modules/imap/lib11_imap_quota_plugin.so Mar 4 13:28:28 mailserver dovecot: IMAP(exemplemail(a)mydomain.com): Effective uid=10017, gid=513, home=/home/exemple Mar 4 13:28:28 mailserver dovecot: IMAP(exemplemail(a)mydomain.com): Quota root: name=User quota backend=maildir args= Mar 4 13:28:28 mailserver dovecot: IMAP(exemplemail(a)mydomain.com): Quota rule: root=User quota mailbox=* bytes=52428800 messages=0 Mar 4 13:28:28 mailserver dovecot: IMAP(exemplemail(a)mydomain.com): Quota rule: root=User quota mailbox=Trash ignored Mar 4 13:28:28 mailserver dovecot: IMAP(exemplemail(a)mydomain.com): maildir: data=/var/spool/dovecot/exemplemail/ Mar 4 13:28:28 mailserver dovecot: IMAP(exemplemail(a)mydomain.com): maildir++: root=/var/spool/dovecot/exemplemail, index=, control=, inbox=/var/spool/dovecot/exemplemail Mar 4 13:28:28 mailserver dovecot: IMAP(exemplemail(a)mydomain.com): Disconnected: Logged out bytes=45/375 Any idea? Thanks and Best Regards

1 0

[Dovecot] unsubscribe
by Rob Coward 04 Mar '11

04 Mar '11

Please consider the environment before printing this email. Game Stores Group Limited, registered number 1937170, registered in England

2 1

[Dovecot] Dovecot and ManageSieve crash trace
by Samuel Hassine 04 Mar '11

04 Mar '11

Hi all, I am trying to deploy Dovecot with Sieve support and I choose the easy way: install ManageSieve. But I have a problem here, and I did not find how to deal with. I tested the communication to the server with the telnet command. Here the result: http://pastebin.com/dgvhEwxJ And I do not understand how to link IMAP authentification and Sieve authentification. I just want to allow creation of Sieve filters for any IMAP user (based on LDAP). Thanks for your answer. Best regards. Samuel Hassine

2 1

[Dovecot] sieve issue
by Informatik.hu 04 Mar '11

04 Mar '11

Hi All! I have got some problem with dovecot sieve. (from Debian Squeeze packages). I have already installed dovecot and postfix with mysql(postfix admin) virtual domains and users, configured dovecot deliver for delivery method in postfix. Dovecot sieve IS working, reads the global script, BUT it DOES NOT reads the user scripts from the users virtual home directory. If i place ".dovecot.sieve" in /home/vmail, and configure sieve for this location, it reads the script. If i put the file under /home/vmail/domain.com (/home/vmail/%d) or /home/vmail/domain.com/user(a)domain.com (/home/vmail/%d/%u) the sieve plugin does not read(compile) the script. Deliver log contains that the incoming mail (which has to be filtered) saved to INBOX, and there is no error in the deliver error log, nor dovecot logs. Can anybody help me out what am i doing wrong? Vuki

2 1

[Dovecot] Problem with sieve and namespace
by Patrick Westenberg 03 Mar '11

03 Mar '11

Hi guys, my default sieve script fails due to an unknown mailspace even I told him to use one. What's wrong? Patrick Feb 26 00:39:25 endeavour dovecot: lmtp(6967, mail(a)jasbafliesen.de) Error: 1WYlBCE1aE03GwAA0CSSVw: sieve: msgid=<4D683DA5.7030505(a)gmx.de>: failed to store into mailbox mail(a)jasbafliesen.de': Unknown namespace Feb 26 00:39:25 endeavour dovecot: lmtp(6967, mail(a)jasbafliesen.de) Error: 1WYlBCE1aE03GwAA0CSSVw: sieve: script /usr/local/etc/dovecot/sieve/default.sieve failed with unsuccessful implicit keep This is what my sieve script looks like: require ["fileinto", "mailbox"]; if header :contains "X-Spam-Flag" "YES" { fileinto :create "INBOX.Spam"; } # 2.0.6: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.26-2-amd64 x86_64 Debian 5.0.8 auth_debug = yes auth_debug_passwords = yes auth_verbose = yes disable_plaintext_auth = no mail_debug = yes mail_gid = vmail mail_location = mdbox:~/mdbox mail_plugins = quota mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = comparator-i;octet comparator-i;ascii-casemap fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date namespace { inbox = yes location = prefix = INBOX. separator = . type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota = dict:User quota::file:%h/mdbox/dovecot-quota quota_warning = storage=90%% quota-warning 90 %u quota_warning2 = storage=75%% quota-warning 75 %u sieve = ~/.dovecot.sieve sieve_global_path = /usr/local/etc/dovecot/sieve/default.sieve } protocols = lmtp service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service quota-warning { executable = script /usr/local/etc/dovecot/quota-warning.sh unix_listener quota-warning { user = vmail } user = vmail } ssl = no userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = quota sieve } protocol lda { mail_plugins = quota sieve } protocol imap { mail_plugins = quota imap_quota }

3 4

[Dovecot] process_min_avail being ignored?
by Douglas Mortensen 03 Mar '11

03 Mar '11

Today I found out we are having users w/ problems because: Mar 3 09:57:33 jlgray dovecot: master: Warning: service(imap-login): process_limit reached, client connections are being dropped Mar 3 09:58:42 jlgray dovecot: master: Warning: service(imap-login): process_limit reached, client connections are being dropped Mar 3 10:02:51 jlgray dovecot: master: Warning: service(imap-login): process_limit reached, client connections are being dropped Mar 3 10:04:29 jlgray dovecot: master: Warning: service(imap-login): process_limit reached, client connections are being dropped Mar 3 10:05:41 jlgray dovecot: master: Warning: service(imap-login): process_limit reached, client connections are being dropped Mar 3 10:06:58 jlgray dovecot: master: Warning: service(imap-login): process_limit reached, client connections are being dropped So, based on the dovecot2 wiki, it would seem that the solution is to follow the recommendations at http://wiki2.dovecot.org/LoginProcess, and use them as a guide for our situation. I have done so. But unless I misunderstand their purpose, I don't think they're working. Maybe I don't have them in the correct place?? I am expecting the imap-login process count to immediately jump up to 200 (based on my config below). But instead, they just slowly gradually increase. But even an hour after changing the config & restarting dovecot, I only have 78 login processes. dovecot -n output is: # 2.0.9: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0 auth_debug = yes auth_mechanisms = plain login disable_plaintext_auth = no log_timestamp = "%Y-%m-%d %H:%M:%S " mail_debug = yes mail_location = maildir:~/ mail_privileged_group = mail passdb { driver = pam } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } ssl_cert = </etc/ssl/certs/jlgray.com.cer ssl_key = </etc/ssl/private/jlgray.com.key userdb { driver = passwd } This configuration was updated from a dovecot 1.x config, by following the instructions at: http://wiki2.dovecot.org/Upgrading/2.0 Namely: doveconf -n -c dovecot-1.conf > dovecot-2.conf Then we renamed dovecot-2.conf to dovecot.conf I'm pretty sure there were no problems with that part. We are running dovecot 2.0.9 compiled from source. OS is 64-bit Debian Squeeze (6.0), as shown by 'cat /proc/version': Linux version 2.6.32-5-amd64 (Debian 2.6.32-30) (ben(a)decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Jan 12 03:40:32 UTC 2011 I really appreciate anyone helping me figure out why Thanks, - Doug Mortensen Network Consultant Impala Networks Inc CCNA, MCSA, Security+, A+ Linux+, Network+, Server+ . www.impalanetworks.com P: (505) 327-7300 F: (505) 327-7545

1 1

[Dovecot] TB, dovecot & trailing slash - again
by Bruno Tréguier 03 Mar '11

03 Mar '11

Hi there, I have been browsing the mailing list archives in search of a solution to my problem, related to the quite infamous "trailing slash" issue with Thunderbird, but I don't seem to have found any closely related discussion. Please forgive me if this problem has already found a solution. Here I go; We use a lot of TB clients (2.x and 3.x), and we are using Dovecot 1.2.4 on our production server (mbox format). As told in many places, including this list, I added the option "tb-extra-mailbox-sep" in my dovecot.conf file. The checkbox regarding the mix of mailbox/submailbox and mailbox/messages is unchecked in the advanced options of our TB standard config. I snooped the connection with "ngrep" when creating a folder meant for containing subfolders. Here is the trace: > 6 create "ABCDE/".. < 6 OK Create completed... > 7 subscribe "ABCDE/".. < 7 OK Subscribe completed... > 8 list "" "ABCDE/".. < * LIST (\Noselect \HasChildren) "/" "ABCDE/"..8 OK List completed... So far, so good. But when you have a look at the .subscriptions file, you can see that the ABCDE folder has no trailing slash: it has been stripped off, apparently due to an "enhancement" made in 2009: http://hg.dovecot.org/dovecot-1.2/rev/339be408f49a It may be intended, but the drawback is that TB then gets a bit confused, as it has no way, during a "LIST" operation, to distinguish between a "folder/subfolder" scheme and a "folder/message" scheme: consequently, you get an error message from TB whenever you click on the containing folder, stating that "the mailbox isn't selectable". The problem is not just cosmetic, though, as the subfolders of such folders are not synchronized when selected for offline reading. I made a test with another version of Dovecot, of the 1.1 branch, and it behaves a little bit differently: the trailing slash is kept in the .subscriptions file, and everything is ok. TB is able to make the distinction between both kinds of folders. For the moment, I simply erased the "tb-extra-mailbox-sep" from my config file, and this is what happens: > 306 create "ABCDE/".. < 306 OK Create completed... > 307 subscribe "ABCDE/".. < 307 NO Invalid mailbox name: ABCDE/.. > 308 list "" "ABCDE/".. < * LIST (\Noselect \HasChildren) "/" "ABCDE/"..308 OK List completed... In that case, the "subscribe" command fails, so the folder does not appear by itself in the .subscriptions file, but as it is not used (only "terminal" mailboxes, containing messages, which are files in the filesystem), this is not a problem. The directory is created on the disk, and you can then create subfolders without any problem... Sorry for this long message, I just wanted to explain precisely what happens. A last word: switching to maildir would be quite a hassle, as we use quite a lot of procmail-based tools. Rewriting everything using Sieve is not planned for the moment. Does anyone out there have a solution for this ? What am I doing wrong ? Is the "tb-extra-mailbox-sep" really necessary when using TB ? As far as I can tell, it rather got us into trouble here, than solved anything... Thanks for any info/pointer/else ! Best regards, Bruno -- - Service Hydrographique et Oceanographique de la Marine - DO/MGS/INF - 13, rue du Chatellier - CS 92803 - 29228 Brest Cedex 2, FRANCE - Phone: +33 2 98 22 17 49 - Email: Bruno.Treguier(a)shom.fr

1 0

[Dovecot] expire plugin and sieve
by cvb＠kruemel.org 03 Mar '11

03 Mar '11

Hi. I am running dovecot 1.2.9 here, allowing users to filter their mails with the sieve plugin, and am using sieve to move mail tagged as probably spam into the spam folder. I'm now looking to get the expire plugin working as well. It does work as described in the wiki: Once I manually move messages into other folders, the mysql database is filled with entries. However, the combination of sieve and expire does not seem to be working: When sieve moves messages into a folder, no entry is created in the database. Don't these plugins work together, or did I misconfigure something? # dovecot -n # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-27-server x86_64 Ubuntu 10.04.1 LTS fuse.glusterfs log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s managesieve ssl_cert_file: /etc/dovecot/imapd.pem ssl_key_file: /etc/dovecot/imapd.pem 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 login_executable(managesieve): /usr/lib/dovecot/managesieve-login login_user: postfix login_process_per_connection: no login_process_size: 128 first_valid_uid: 113 mail_privileged_group: mail mail_location: maildir:/home/vmail/%Ld/%Ln:INDEX=/var/indexes/%u mail_debug: yes mail_nfs_storage: yes 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_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): expire mail_plugins(imap): expire mail_plugins(pop3): expire mail_plugins(managesieve): 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 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): managesieve_logout_format(default): bytes=%i/%o managesieve_logout_format(imap): bytes=%i/%o managesieve_logout_format(pop3): bytes=%i/%o managesieve_logout_format(managesieve): bytes ( in=%i : out=%o ) namespace: type: private separator: . prefix: INBOX. inbox: yes list: yes subscriptions: yes lda: postmaster_address: postmaster(a)example.com mail_plugins: expire mail_plugins: sieve auth default: mechanisms: plain login user: nobody verbose: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: static args: uid=5000 gid=5000 home=/home/vmail/%Ld/%Ln allow_all_users=yes socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: root master: path: /var/run/dovecot/auth-master mode: 438 user: vmail group: vmail plugin: sieve: /home/vmail/%Ld/%Ln/.dovecot.sieve sieve_global_path: /home/vmail/globalsieverc sieve_dir: ~/sieve sieve_global_dir: /var/lib/dovecot/sieve/global/ expire: INBOX.Trash 7 INBOX.Mailing-Lists.* 30 INBOX.Spam 14 expire_dict: proxy::expire dict: expire: mysql:/etc/dovecot/dovecot-dict-expire.conf Thanks, Christian

2 2

[Dovecot] dovecot share
by Eric Broch 03 Mar '11

03 Mar '11

Hello List, I have created a shared folder in dovecot and am trying to use ACL's to limit access to it and give users who do have access the ability to create sub-directories and copy email to them. When I try to create a sub-directory in the share using Outlook I get the following error: "Cannot create the folder. The server responded: 'NOPERM] Permission denied'." And, I get the following info in the dovecot server log: 2011-03-01 15:38:30.250214500 IMAP(test(a)whitehorsetc.com): Info: Loading modules from directory: /usr/local/lib/dovecot/imap 2011-03-01 15:38:30.250399500 IMAP(test(a)whitehorsetc.com): Info: Module loaded: /usr/local/lib/dovecot/imap/lib01_acl_plugin.so 2011-03-01 15:38:30.250402500 IMAP(test(a)whitehorsetc.com): Info: Module loaded: /usr/local/lib/dovecot/imap/lib02_imap_acl_plugin.so 2011-03-01 15:38:30.250404500 IMAP(test(a)whitehorsetc.com): Info: Effective uid=89, gid=89, home=/home/vpopmail/domains/whitehorsetc.com/test 2011-03-01 15:38:30.250407500 IMAP(test(a)whitehorsetc.com): Info: acl: No acl_shared_dict setting - shared mailbox listing is disabled 2011-03-01 15:38:30.250422500 IMAP(test(a)whitehorsetc.com): Info: Namespace: type=private, prefix=INBOX., sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes 2011-03-01 15:38:30.250425500 IMAP(test(a)whitehorsetc.com): Info: maildir: data=~/Maildir 2011-03-01 15:38:30.250427500 IMAP(test(a)whitehorsetc.com): Info: maildir++: root=/home/vpopmail/domains/whitehorsetc.com/test/Maildir, index=, control=, inbox=/home/vpopmail/domains/whitehorsetc.com/test/Maildir 2011-03-01 15:38:30.250441500 IMAP(test(a)whitehorsetc.com): Info: acl: initializing backend with data: vfile 2011-03-01 15:38:30.250443500 IMAP(test(a)whitehorsetc.com): Info: acl: acl username = test(a)whitehorsetc.com 2011-03-01 15:38:30.250445500 IMAP(test(a)whitehorsetc.com): Info: acl: owner = 1 2011-03-01 15:38:30.250447500 IMAP(test(a)whitehorsetc.com): Info: acl vfile: Global ACL directory: (null) 2011-03-01 15:38:30.250515500 IMAP(test(a)whitehorsetc.com): Info: Namespace: type=shared, prefix=projects., sep=., inbox=no, hidden=no, list=yes, subscriptions=yes 2011-03-01 15:38:30.250518500 IMAP(test(a)whitehorsetc.com): Info: maildir: data=/home/vpopmail/domains/whitehorsetc.com/projects 2011-03-01 15:38:30.250520500 IMAP(test(a)whitehorsetc.com): Info: maildir++: root=/home/vpopmail/domains/whitehorsetc.com/projects, index=, control=, inbox= 2011-03-01 15:38:30.250534500 IMAP(test(a)whitehorsetc.com): Info: acl: initializing backend with data: vfile 2011-03-01 15:38:30.250536500 IMAP(test(a)whitehorsetc.com): Info: acl: acl username = test(a)whitehorsetc.com 2011-03-01 15:38:30.250538500 IMAP(test(a)whitehorsetc.com): Info: acl: owner = 0 2011-03-01 15:38:30.250540500 IMAP(test(a)whitehorsetc.com): Info: acl vfile: Global ACL directory: (null) 2011-03-01 15:38:30.250754500 imap-login: Info: Login: user=<test(a)whitehorsetc.com>, method=PLAIN, rip=192.168.9.5, lip=192.168.9.6 2011-03-01 15:38:30.254448500 IMAP(test(a)whitehorsetc.com): Info: acl vfile: file /home/vpopmail/domains/whitehorsetc.com/projects/.xxxxxx/dovecot-acl not found 2011-03-01 15:39:10.998483500 IMAP(test(a)whitehorsetc.com): Info: Disconnected: Logged out bytes=76/431 The second to the last line in the log indicates that there is no 'dovecot-acl' file in the directory I'm trying to create using Outlook. I'm not sure if this is the error and I'm not sure what I need to adjust in order to create a directory using the email account. My dovecot.conf file is as follows: base_dir = /var/run/dovecot/ protocols = imap imaps disable_plaintext_auth = no log_path = /dev/stderr info_log_path = /dev/stderr log_timestamp = "" ssl_cert_file = /var/qmail/control/servercert.pem ssl_key_file = /var/qmail/control/servercert.pem ssl_cipher_list = ALL:!LOW verbose_ssl = yes login_dir = /usr/local/var/run/dovecot/login login_user = dovecot login_process_per_connection = yes login_processes_count = 3 login_max_processes_count = 128 login_greeting = Dovecot ready. login_log_format_elements = user=<%umethod=%m rip=%r lip=%l %c mail_location = maildir:~/Maildir namespace private { separator = . prefix = INBOX. inbox = yes } namespace shared { separator = . prefix = projects. location = maildir:/home/vpopmail/domains/mydomain.com/shared/projects } mail_debug = yes verbose_proctitle = yes first_valid_uid = 89 last_valid_uid = 89 protocol imap { mail_plugins = acl imap_acl } protocol pop3 { } protocol lda { postmaster_address = postmaster(a)whitehorsetc.com } auth default { mechanisms = plain login digest-md5 cram-md5 passdb vpopmail { args = } userdb passwd { } userdb vpopmail { } user = vpopmail count = 1 ssl_require_client_cert = no } dict { } plugin { vfile = acl } In the share directory (/home/vpopmail/domains/whitehorsetc.com.com/shared/projects) I created two files: 'subscriptions' and 'dovecot-acl.' Listing this directory yields the following: drwx------ 2 vpopmail vchkpw 4096 Feb 17 08:57 cur -rwxrwxrwx 1 vpopmail vchkpw 39 Mar 1 15:01 dovecot-acl -rw------- 1 vpopmail vchkpw 0 Mar 1 15:51 dovecot-acl-list drwx------ 2 vpopmail vchkpw 4096 Jan 28 14:48 new -rw------- 1 vpopmail vchkpw 1 Mar 1 14:46 subscriptions drwx------ 2 vpopmail vchkpw 4096 Feb 17 08:57 tmp The file 'dovecot-acl-list' is created automatically when I open Outlook. In the file 'dovecot-acl' I have the following entry: user=test(a)whitehorsetc.com lrwstipekxa I also noticed that the 'projects' folder would not become visible in Outlook until I manually created the 'subscriptions' file, opened it, entered a <CR><LF>, and closed the file. Without ACL support enabled all works as expected. Any help would be appreciated. Eric

2 10

Re: [Dovecot] auth on tcp socket?
by Hajo Locke 03 Mar '11

03 Mar '11

Hello, >> is it possible to provide service auth on tcp-socket instead of >> unix-socket? >> I changed my conf and dovecot 2.0.5 is restarting but on telnet test it >> throws: >> dovecot: auth: Fatal: getsockname(12) failed: Socket operation on >> non-socket >> >> Want to separate smtp and imap to different servers but keep using >> dovecot auth for postfix-sasl. >> Whats to do? hmm, is postfix able to use non-unix socket for >> dovecot-sasl? > Well, added support for that: > http://hg.dovecot.org/dovecot-2.0/rev/fe8e82b5bff9 Thanks for that. is it save to use smtpd_sasl_path = inet:localhost:1434 in postfix's main.cf? there are some warnings in log: "when SASL type is "dovecot", SASL path "inet:localhost:1434" should be a socket pathname" ( Datei src/xsasl/xsasl_dovecot_server.c ) Thanks, Hajo

1 0

[Dovecot] Does dovecot proxy support message caching?
by Edward Carraro 03 Mar '11

03 Mar '11

For example, say the connection between the user and the dovecot proxy is fast/cheap, but the connection from the proxy to the dovecot imap backend server is costly. is there a way to set up the proxy to cache messages to allow faster loading? if so, does it have different levels of caching (full message, headers only, etc)? I'm using dovecot 2.0.9 for both the proxy and the imap backend. if not, is there something that can work with dovecot to allow this? Thanks!

3 4

[Dovecot] Segfault in managesieve with "sieve_extensions = -redirect"
by Sven Hartge 03 Mar '11

03 Mar '11

Hi! I've got a segfault in managesieve while using: sieve_extensions = -vacation -reject -spamtest -virustest -enotify -redirect The problem seems to lie in "-redirect". Reason for excluding "redirect" from sieve is my users should not use sieve to forward or redirect mails but use an external method (web-script to set LDAP attribute) which checks several things like active spam-checker, existing target mailbox, etc. The version ov dovecot ist 1:2.0.9-1~3.gbp785ad1~dvz60+1 on Debian Squeeze which is from the Debian maintainers git repository recompiled on Squeeze (I know, pretty wild.) doveconf -n and backtrace follow: -----------------------8<--------------------------------------------- # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0 auth_username_format = %Ln dict { quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no first_valid_gid = 1000 first_valid_uid = 1000 last_valid_gid = 1000 last_valid_uid = 1000 mail_access_groups = virtmail mail_gid = virtmail mail_location = mdbox:~/mdbox mail_plugins = " quota zlib" mail_uid = virtmail mdbox_rotate_interval = 23 hours mdbox_rotate_size = 25 M namespace { hidden = yes inbox = yes list = yes location = prefix = INBOX. separator = . subscriptions = yes type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { quota = dict:Benutzer-Quota::proxy::quota quota_rule = *:storage=2G sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = -vacation -reject -spamtest -virustest -enotify -redirect zlib_save = gz zlib_save_level = 6 } postmaster_address = postmaster(a)th-mittelhessen.de protocols = imap pop3 sieve service dict { unix_listener dict { group = virtmail mode = 0660 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = /etc/dovecot/dovecot-ldap-userdb.conf.ext driver = ldap } protocol lmtp { mail_plugins = " quota zlib sieve" } protocol lda { mail_plugins = " quota zlib sieve" } protocol imap { mail_plugins = " quota zlib imap_quota imap_zlib" } -----------------------8<--------------------------------------------- (gdb) bt full #0 sieve_extensions_set_string (svinst=<value optimized out>, ext_string=<value optimized out>) at sieve-extensions.c:567 ext = 0x0 op = 0 '\000' name = 0x2375331 "redirect" _data_stack_cur_id = 2 ext_reg = 0x23856c8 ext_names = 0x2375368 i = <value optimized out> ext_count = <value optimized out> relative = true #1 0x00007fb2db4207c2 in sieve_extensions_init (svinst=0x2385680) at sieve-extensions.c:256 extensions = <value optimized out> ext = <value optimized out> #2 0x00007fb2db426914 in sieve_init (env=0x40d700, context=<value optimized out>, debug=false) at sieve.c:83 svinst = 0x2385680 uint_setting = 0 size_setting = 37179544 pool = 0x2385660 #3 0x00000000004085ff in managesieve_capabilities_dump () at managesieve-capabilities.c:125 svinst = <value optimized out> notify_cap = <value optimized out> #4 0x0000000000408af5 in main (argc=4, argv=0x237d370) at main.c:273 set_roots = {0x610040, 0x0} service_flags = <value optimized out> storage_service_flags = 0 postlogin_socket_path = 0x0 username = 0x0 c = <value optimized out> -----------------------8<--------------------------------------------- Grüße, Sven. -- Sig lost. Core dumped.

4 5

[Dovecot] Error purging mdbox (damaged) mailbox
by Javier Miguel Rodríguez 02 Mar '11

02 Mar '11

We are stress testing our preproduction system. One of the "evil" tests we made was putting our mailboxes filesystem in read-only in the middle of smtp(+lda) delivery. When we try to purge one of the affected mailboxes we get error like the followings: / doveadm(lbandera@mysite): Panic: file mdbox-purge.c: line 225 (mdbox_purge_save_msg): assertion failed: (ret == (off_t)msg_size) doveadm(lbandera@mysite): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x3b0943bab0] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x35) [0x3b0943bb95] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3b0943b4c3] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_purge+0xe83) [0x3b0986f0c3] -> /usr/bin/doveadm [0x408d65] -> /usr/bin/doveadm [0x4093c1] -> /usr/bin/doveadm(doveadm_mail_single_user+0x9d) [0x4094ed] -> /usr/bin/doveadm [0x4096fe] -> /usr/bin/doveadm(doveadm_mail_try_run+0xb7) [0x409b37] -> /usr/bin/doveadm(main+0x2fc) [0x40dddc] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3b0881d994] -> /usr/bin/doveadm [0x408c39]/ / doveadm(leonvela@mysite): Panic: file mdbox-purge.c: line 225 (mdbox_purge_save_msg): assertion failed: (ret == (off_t)msg_size) doveadm(leonvela@mysite): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x3b0943bab0] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x35) [0x3b0943bb95] -> /usr/lib64/dovecot/libdovecot.so.0 [0x3b0943b4c3] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mdbox_purge+0xe83) [0x3b0986f0c3] -> /usr/bin/doveadm [0x408d65] -> /usr/bin/doveadm [0x4093c1] -> /usr/bin/doveadm(doveadm_mail_single_user+0x9d) [0x4094ed] -> /usr/bin/doveadm [0x4096fe] -> /usr/bin/doveadm(doveadm_mail_try_run+0xb7) [0x409b37] -> /usr/bin/doveadm(main+0x2fc) [0x40dddc] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3b0881d994] -> /usr/bin/doveadm [0x408c39]/ The mailboxes are damaged, but maybe doveadm should not crash on them, should handle the error more gracefully and exit with a error status. Regards Javier

2 1

Re: [Dovecot] Regenerating mdbox/sis
by Daniel L. Miller 01 Mar '11

01 Mar '11

On 2/21/2011 8:23 AM, Daniel L. Miller wrote: After applying last two patches, I see: root@bubba:/var/mail# dsync -u amiller(a)amfes.com -o mail_plugins="zlib" backup maildir:/var/mail/backup/amiller dsync(amiller(a)amfes.com): Error: Corrupted dbox file /var/mail/amfes.com/amiller/mdbox/storage/m.1 (around offset=237479): Ext refs metadata corrupted: 356039 144422 B72 0a/5a/0a5ae26f12adad628d9e5049e7ec8a756dafe49d-7c35b90f82a1c94ce151000 03bc41c5f dsync(amiller(a)amfes.com): Error: Corrupted dbox file /var/mail/amfes.com/amiller/mdbox/storage/m.1 (around offset=237479): uid=5 points to broken data at offset=237449 dsync(amiller(a)amfes.com): Error: msg-get failed: box=Drafts uid=5 guid=1156208717.P32762Q0M962249.amy dsync(amiller(a)amfes.com): Error: Corrupted dbox file /var/mail/amfes.com/amiller/mdbox/storage/m.2 (around offset=46): Ext refs metadata corrupted: 485733 478770 - f2/12/f212f6dbff17cea018ec1f256cff6f61a873a100-7d35b90f82a1c94ce15100003bc41 c5f dsync(amiller(a)amfes.com): Error: Corrupted dbox file /var/mail/amfes.com/amiller/mdbox/storage/m.2 (around offset=46): uid=9 points to broken data at offset=16 dsync(amiller(a)amfes.com): Error: msg-get failed: box=Drafts uid=9 guid=1157518326.P23171Q0M772523.amy dsync(amiller(a)amfes.com): Warning: mdbox /var/mail/amfes.com/amiller/mdbox/storage: rebuilding indexes -- Daniel

1 0

Re: [Dovecot] Search failure
by Daniel L. Miller 01 Mar '11

01 Mar '11

On 3/1/2011 11:17 AM, Daniel L. Miller wrote: > Applied patches, then performed a search. got all kinds of fun > feedback...here's a small sampling > > root@bubba:/var/mail/amfes.com/dmiller/mdbox# doveadm search -u > dmiller(a)amfes.com TEXT xyzxyz > 392b0c265aa1c94cd45100003bc41c5f 10906 > 392b0c265aa1c94cd45100003bc41c5f 10911 > doveadm(dmiller(a)amfes.com): Error: Corrupted dbox file > /var/mail/amfes.com/dmiller/mdbox/storage/m.2223 (around > offset=36650): Ext refs metadata corrupted: 293271 161935 B76 > 8a/bf/8abf3af65396470c3d39379d922108f9fc46050b-bf22cc2e12ec524dde6c00003bc41c5f > doveadm(dmiller(a)amfes.com): Error: Corrupted dbox file > /var/mail/amfes.com/dmiller/mdbox/storage/m.2223 (around > offset=36650): uid=12937 points to broken data at offset=36620 > doveadm(dmiller(a)amfes.com): Warning: mdbox > /var/mail/amfes.com/dmiller/mdbox/storage: rebuilding indexes > > meanwhile, had a "tail -f /var/log/mail.err" running...had a few of > these pop up > Mar 1 11:12:37 bubba dovecot: imap(dmiller(a)amfes.com): Error: Recent > flags state corrupted for mailbox Lists.Fire-Alarm > Mar 1 11:12:40 bubba dovecot: imap(dmiller(a)amfes.com): Error: > /var/mail/amfes.com/dmiller/mdbox/mailboxes/Lists/Dovecot-Users/dbox-Mails/dovecot.index > reset, view is now inconsistent > 2nd run got similar results. -- Daniel

1 0

[Dovecot] Search failure
by Daniel L. Miller 01 Mar '11

01 Mar '11

doveadm search -u dmiller(a)amfes.com text xyzxyz doveadm(dmiller(a)amfes.com): Panic: file istream-limit.c: line 79 (i_stream_limit_seek): assertion failed: (v_offset <= lstream->v_size) doveadm(dmiller(a)amfes.com): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x3ca8a) [0x7fcf3daaca8a] -> /usr/local/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x32) [0x7fcf3daacb72] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x16dea) [0x7fcf3da86dea] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x45b54) [0x7fcf3dab5b54] -> /usr/local/lib/dovecot/libdovecot.so.0(i_stream_seek+0x6e) [0x7fcf3dab2d8e] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(dbox_attachment_file_get_stream+0x1ca) [0x7fcf3e1e99aa] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(dbox_mail_get_stream+0xea) [0x7fcf3e1eba4a] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x4c1) [0x7fcf3e1bb0a1] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x20) [0x7fcf3e1a2110] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next+0x26) [0x7fcf3e1a2166] -> doveadm() [0x40cdd7] -> doveadm() [0x4092a4] -> doveadm(doveadm_mail_single_user+0x8c) [0x4095bc] -> doveadm() [0x4097c3] -> doveadm(doveadm_mail_try_run+0x141) [0x409bc1] -> doveadm(main+0x3a9) [0x40df59] -> /lib/libc.so.6(__libc_start_main+0xfe) [0x7fcf3d2ffd8e] -> doveadm() [0x408ba9] Aborted -- Daniel

2 5

[Dovecot] Dovecot+Postfix+Mysql+quotas doesn't work
by drum.lucas＠gmail.com 01 Mar '11

01 Mar '11

Hi ! I'm using postfix with mysql, dovecot and squirrelmail for WEBMAIL In my dovecot.conf I've: plugin { quota = maildir:User quota quota2 = maildir:Shared quota:ns=Public/ quota_rule = *:storage=400M quota_rule2 = Trash:storage=100M quota_exceeded_message = Quota excedida. Por favor, exclua alguns emails! quota_warning = storage=95%% /usr/local/bin/quota-warning.sh 95 quota_warning2 = storage=80%% /usr/local/bin/quota-warning.sh 80 } In my webmail, he informs me that I'm using the percentage of quota. But I can't make the TRASH folder is ignored. That is, I can't put a higher limit on it than the others. Am I doing something wrong? Another thing. I'm not receiving message of quota exceeded. This is with the MTA or dovecot? ############################################################################################################## ############################################################################################################## ############################################################################################################## ############################################################################################################## My quota-warning.sh: #!/bin/sh PERCENT=$1 FROM="postmaster(a)xxxxxxxx.br" qwf="/tmp/quota.warning.$$" echo "From: $FROM To: $USER To: postmaster(a)xxxxxxx.br Subject: Your email quota is $PERCENT% full Content-Type: text/plain; charset="UTF-8" Sua caixa de e-mail está: $PERCENT% full." >> $qwf cat $qwf | /usr/sbin/sendmail -f $FROM "$USER" rm -f $qwf exit 0 ############################################################################################################## ############################################################################################################## ############################################################################################################## DOVECOT: dovecot.x86_64 1.0.7-7.el5 POSTFIX: postfix.x86_64 2:2.3.3-2.1.centos.mysql_pgsql MYSQL: mysql-server.x86_64 5.0.77-4.el5_5.4 thank's ! -- Atenciosamente; Graciously; *Lucas Possamai * http://psyscrew.posterous.com/ "Sexo? O governo dá camisinha! Engravidou? Bolsa família! Preso? Ele dá dinheiro! Agora vai estudar pra você vê." "Sucesso é a capacidade de enfrentar o fracasso sem perder o entusiasmo" *INFORMAÇÃO DE SEGURANÇA:* Este e-mail é de uso restritamente pessoal. As informações nele contidas podem ser de caráter confidencial e/ou privilegiada. Se você não for o destinatário e recebeu a mensagem por engano, avise imediatamente o remetente e em seguida apague o e-mail, ficando, expressamente vedado o uso, cópia e/ou divulgação das informações contidas, sob pena de responsabilização. *SAFETY INFORMATION:* This e-mail is strictly personal use. The information contained here may be confidential and / or privileged. If you aren't the intended recipient and received the message in error, please notify the sender immediately and delete the email, being expressly forbidden the use, copying and / or disclosure of information, under penalty of accountability. *P* Antes de imprimir, pense em sua responsabilidade e seu compromisso com o meio ambiente. *P* Before printing, think about your responsibility and commitment to the environment.**

4 5

[Dovecot] lazy_expunge, 2 questions
by Hajo Locke 01 Mar '11

01 Mar '11

Hello List, do some tests with lazy_expunge i have 2 short questions. is it possible to set folder for expunged messages to read-only so no user is possible to really delete them? i can use mdbox for expunged-folder. but would'nt it be more functional to use maildir to have possibility to delete separate mails? when using mdbox the clean up by cron would effect always multiple messages with different ages? Thanks, Hajo

2 1

[Dovecot] 1.0.15 -> 2.x upgrade for mass hosting environment
by lists＠truthisfreedom.org.uk 01 Mar '11

01 Mar '11

Hi all, We're looking at upgrading our current mail platform from 1.0.15 to 2.x to take advantage of the new director functionality. Our main concern is the number of mailboxes involved (circa. 300K) and the rebuilding of the index files, especially as it seems that once you've upgraded, rolling back requires the deletion and recreation of all indices. Has anyone worked on an upgrade like this in the past? If so, do you have any war stories you can share either on or off list? Thanks in advance, Matt

3 5

[Dovecot] systemd socket and service
by Vasiliy G Tolstov 01 Mar '11

01 Mar '11

Hello. I'm use systemd and have some questions: 1) Why dovecot.socket contains only imap ListenStream? [Unit] Description=Dovecot IMAP/POP3 email server activation socket [Socket] #dovecot expects separate IPv4 and IPv6 sockets BindIPv6Only=ipv6-only ListenStream=0.0.0.0:143 ListenStream=[::]:143 ListenStream=0.0.0.0:993 ListenStream=[::]:993 KeepAlive=true 2) Does dovecot.service required to use dovecot lmtp, or it may be stoppped (i not often check my mails via client, but have many incoming mails some time) -- Vasiliy G Tolstov <v.tolstov(a)selfip.ru> Selfip.Ru

3 4

[Dovecot] Forward and keep on snow leopard server
by Jbaileypro 01 Mar '11

01 Mar '11

I am wanting to use a service which has to have a copy of the emails but they still need to be delivered to the users inbox. Which script and where does it need to be placed for this to work? I am not sure which version sls runs dovecot but I know that it also uses spamassasin. If anyone can help that would be great. Thanks, Jonathan -- View this message in context: http://old.nabble.com/Forward-and-keep-on-snow-leopard-server-tp31038917p31… Sent from the Dovecot mailing list archive at Nabble.com.

1 0

[Dovecot] Smart IMAP proxying with imapc storage
by Timo Sirainen 28 Feb '11

28 Feb '11

I just committed a very early initial implementation of "imapc" storage backend to v2.1 hg: http://hg.dovecot.org/dovecot-2.1 You can't really do anything except open INBOX and read mails from it, so it's currently only intended for initial testing. It sucks in many ways right now, but I'll be improving it. The idea is that you could set for example: mail_location = imapc:imap.gmail.com And then Dovecot could act as a proxy to gmail. It won't actually work currently with gmail, because there's no SSL support for outgoing connections. Currently index files are forcibly disabled, but it would be easy to enable them, allowing Dovecot to do caching locally to improve performance. In future perhaps it will also support caching message headers/bodies to avoid unnecessary traffic. Besides the mail_location setting, you'll need to also forward the user's password to imap process in "pass" userdb extra field. How to do that depends on what passdb/userdb you're using. While testing you could simply set a static password: plugin { pass = yourpassword }

6 16

Re: [Dovecot] Problem with ldap / quotas
by Nikolaos Milas 28 Feb '11

28 Feb '11

I forgot to cc the list in my subsequent question in this thread, so that question and Timo's reply has not been included in the mailing list. I am submitting for thread completeness, thanking Timo for his invaluable help. Nick On 22/2/2011 6:23 μμ, Timo Sirainen wrote: > On 22.2.2011, at 18.11, Nikolaos Milas wrote: > >> I added dn and dnpass and now everything appears to be running smoothly. I checked, and the maildirsize file gets updated according to the quota value we set in LDAP. >> >> Can you also please clarify: When the default policy is to offer to users some storage space (say 4G) and some additional for Trash (say 100M), and then we define (over LDAP) a different storage space for a particular user (for example 1M), then: >> >> 1. This user will also "inherit" a 100M Trash from the default policy >> or not (in this example 1+100M)? > Yes. > >> Can we change this (also define >> per user Trash size)? > Yes, you can also have ldap return quota_rule2 to override it. Or instead of a hard coded limit, you could set Trash's size to e.g. 10% of the default limit (quota_rule2 = Trash:storage=10%%) so you don't have to return it from ldap. > >> 2. If we define quota_warning (say 75%), the value will apply to the >> total of (MainStorage + Trash (here 101M)) or to MainStorage only >> (1M)? > MainStorage = 1M. > >> I'm asking because I reduced the storage space to only 50K for a test account (for experimenting), and sent various emails (over smtp) to that mailbox, but I saw no warnings or mailbox locking when the mailbox was over-quota or full. > Locking? You mean it allowed user to exceed quota? mail_debug=yes could log something useful about what's going on.

3 9

[Dovecot] Problems setting up shared/public imap folders
by Andre Tann 28 Feb '11

28 Feb '11

Hello everyone, today I have tried to set up shared and public IMAP folders, but it didn't work. # rpm -qa | grep dovecot dovecot12-backend-mysql-1.2.11-3.3.1.x86_64 dovecot12-backend-sqlite-1.2.11-3.3.1.x86_64 dovecot12-1.2.11-3.3.1.x86_64 dovecot12-backend-pgsql-1.2.11-3.3.1.x86_64 Here is my dovecot.conf [1]. Can anyone explain what is wrong with my configuration? It is not possible to access the shared and public mailboxes. Thunderbird and KMail don't show the shared/public namespace at all. Outlook Express shows these namespaces, but trying to access leads to a "mailbox doesn't exist" error message. Dovecot is not logging any errors. What's wrong? Thanks, Andre [1] # cat /etc/dovecot/dovecot.conf protocols = imap imaps protocol imap { mail_plugins = acl imap_acl } listen = * disable_plaintext_auth = no ssl = no login_greeting = alphatest mailservice ready. mail_location = maildir:~/Maildir namespace private { separator = / prefix = inbox = yes } namespace shared { separator = / prefix = shared/ location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u subscriptions = no } namespace public { separator = / prefix = pub/ location = maildir:/srv/mail/pub subscriptions = no } mail_uid = 1002 mail_gid = 1000 protocol imap { mail_plugin_dir = /usr/lib64/dovecot/modules/imap } protocol pop3 { mail_plugin_dir = /usr/lib64/dovecot/modules/pop3 } protocol managesieve { } protocol lda { mail_plugin_dir = /usr/lib64/dovecot/modules/lda mail_plugins = acl } auth default { mechanisms = plain passdb pam { } userdb passwd { } user = root } dict { } plugin { acl = vfile acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes/%u acl_anyone = allow } -- Andre Tann

1 0

[Dovecot] shared folder
by Eric Broch 28 Feb '11

28 Feb '11

Hello list, I have dovecot-1.2.3 installed on my mail server. I created a shared directory which works fine, however, this shared directory has over 16GB of email and when users, 40 to 50 of them, login to their IMAP account and download of the contents of this shared folder begins on their machines it bogs down the server to a crawl. I had to comment out the share it was so bad. Is there a way to implement permissions on the shared folder and add 1 or 2 users at a time so as not to bog down the server. Eric Broch

3 2

[Dovecot] error - dovecot - child (login) killed with signal 16
by Chris Hoogendyk 28 Feb '11

28 Feb '11

We've been happily running Dovecot in Solaris 10 for about 8 months now. Yesterday, Solaris 10's SMF put it in maintenance mode (shut it down) seemingly out of the blue. The only thing going on was that I had updated the ssl certificate. We had previously been using a self signed cert. Now we have a cert from InCommon. We had a problem with a few users who are still on ancient Eudora and didn't have the proper authority chains. We had a problem with a few Thunderbird users who hadn't set up the fully qualified server name in their configuration. The shutdown was coincident (and could be just a coincidence) to the minute with my boss working with a Windows Thunderbird user to change their configuration. I can't figure out how this happened or why. I don't see how to track it any further than what I have here, and it doesn't make sense that a user issue or process could cause this. The IP, by the way, is our NAT. So no way of telling much from that. From /var/adm/dovecot.log: Feb 24 15:52:57 marlin dovecot: [ID 583609 local2.error] dovecot: child 21233 (login) killed with signal 16 (ip=128.119.55.8) Feb 24 15:52:58 marlin dovecot: [ID 583609 local2.warning] dovecot: Killed with signal 15 (by pid=26750 uid=0 code=kill) Note that the first line is logged as an error. These items from the SMF service log for dovecot: [ Feb 24 15:52:58 Stopping because process received fatal signal from outside the service. ] [ Feb 24 15:52:58 Executing stop method ("/etc/mail/svc/method/dovecot.init.d stop") ] Stopping Dovecot are the source of the signal 15 in the second line of the dovecot log above. So, the presumption is that the signal 16 precipitated SMF to put the service in maintenance mode which lead to the signal 15. Any ideas what went wrong here? How to track it down? How to prevent it from happening again? Doing `svcadm clear dovecot` cleared the maintenance mode and started it up again. No problems since. -- --------------- Chris Hoogendyk - O__ ---- Systems Administrator c/ /'_ --- Biology& Geology Departments (*) \(*) -- 140 Morrill Science Center ~~~~~~~~~~ - University of Massachusetts, Amherst <hoogendyk(a)bio.umass.edu> --------------- Erdös 4

2 1