- dovecot - dovecot.org

[Dovecot] Mail deduplication
by Tim Groeneveld 15 May '13

15 May '13

Hi Guys, I am wondering about mail deduplication. I am looking into the possibility of seperating out all of the message bodies with multiple parts inside mail that is recived from `dovecot` and hashing them all. The idea is that by hashing all of the parts inside the email, I will be able to ensure that each part of the email will only be saved once. This means that attachments & common parts of the body will only be saved once inside the storage. How achievable would this be with the current state of dovecot? Would it even be worth doing? Thanks, Tim

7 19

[Dovecot] quota and dict
by Jeff Gustafson 15 May '13

15 May '13

I have a question about using dict and quotas. I want dovecot to send quota queries to a custom dict server over a socket. I'm doing this because I can't do group quotas based on domain since a customer can have each of their users associated with different domains under a single account. I need to lookup the account ID and group based on that. I'm worried putting everything in mysql will cause way too many writes and lower the performance of our mysql cluster. I have having a little trouble connecting all the dots in the config file. In the userdb example, there is an 'args' parameter that allows a file to specify a uri. I don't see how to do that for dict. I only see file, mysql, and postgresql. Shouldn't I be able to use a dictionary proxy to attach any custom program to a quota dict socket? Tell the quota plug to proxy quota which then points to a socket: plugin { quota = dict:User quota::proxy::quota } dict { quota = proxy:/tmp/test-socket } or should it be: plugin { quota = dict:User quota::proxy:/tmp/test-socket } Neither one create a socket in /tmp. It seems like this should be possible, but I don't see an obvious way to do it. ...Jeff

2 1

[Dovecot] Released Pigeonhole v0.4.0 for Dovecot v2.2.1.
by Stephan Bosch 15 May '13

15 May '13

Hello Dovecot users, I finally release the first version of Pigeonhole v0.4 for Dovecot v2.2. The main reason for the delay was that some unexpected (design) problems occurred with the new doveadm-sieve plugin, which allows synchronizing sieve scripts using doveadm sync. One important change is that I incorporated the extprograms plugin into the main Pigeonhole release. With this plugin it is possible to execute administrator-controlled external programs (shell scripts) from the Sieve interpreter, e.g. for special message delivery, filtering and string manipulation. The list of new features is not that impressive. I've been working on IMAP URLAUTH, IMAP CATENATE and HTTP support for Dovecot. Currently, I'm building an SMTP submission proxy server. After all that I plan to spend more time on Sieve development. One of the most important issues on my list is implementing support for using alternative types of storage (e.g. a database) for Sieve scripts, rather than only a filesystem directory as it is now. Changelog v0.4.0: + Added doveadm-sieve plugin that provides the possibility to sync Sieve scripts using doveadm sync along with the user's mailboxes. + Added the Sieve extprograms plugin to the main Pigeonhole package. It is still a plugin, but it is now included so that a separate compile is no longer necessary and distributors are likely to include it. The extprograms plugin provides Sieve language extensions that allows executing (administrator-controlled) external programs for message delivery, message filtering and string manipulation. Refer to doc/plugins/sieve_extprograms.txt for more information. + Added debug message showing Pigeonhole version at initialization. Makes it very clear that the plugin is properly loaded. + Finished implementation of the Sieve include extension. It should now fully conform to RFC 6609. The main addition is the new :optional tag which makes the include command ignore missing included scripts without an error. + Finished implementation of the Sieve environment extension as much as possible. Environment items "location", "phase" and "domain" now also return a usable value. The release is available as follows: http://www.rename-it.nl/dovecot/2.2/dovecot-2.2-pigeonhole-0.4.0.tar.gz http://www.rename-it.nl/dovecot/2.2/dovecot-2.2-pigeonhole-0.4.0.tar.gz.sig Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

10 27

[Dovecot] 2.2.x autobuilds: Debian Stable now Wheezy, which pool for 2.2.x?
by Ron Leach 15 May '13

15 May '13

List, good evening, just installed a new Debian Stable (Wheezy). The Debian Stable repositories now include Dovecot 2.1.7 as standard. I haven't installed that because I wanted to try 2.2.x on this new clean install but unsure which 'pool' to use in the xi.rename-it.nl repository of autobuilds. http://xi.rename-it.nl/debian/pool/ Wheezy became Stable on May 5, just a few days ago. I'm not sure whether to still follow the advice in the wiki for obtaining 2.2.x for Wheezy, which (understandably, because the new Debian Stable release has been so very recent) continues to refer to Wheezy as 'testing'. http://wiki2.dovecot.org/PrebuiltBinaries#Automatically_Built_Packages Presumably, the packages in the 'testing' autobuild system pick up Debian's 'testing' pool libraries (or assume them to exist) and these may no longer be the ones needed for Wheezy because Wheezy is 'Stable', in Debian-speak. Does anyone know, for sure, which autobuild pool to now use for 2.2.x for Wheezy? http://xi.rename-it.nl/debian/pool/stable-auto/ or http://xi.rename-it.nl/debian/pool/testing-auto/ 2.2.x in 'stable-auto' doesn't seem to have changed since before Wheezy was released, whereas 2.2.x has changed in 'testing-auto', and I'm not sure what to make of that. Stephan does suggest that queries be directly written to him, but I posted here because I thought I might not be the only person who was unsure. I'd be grateful for any advice, regards, Ron

3 5

[Dovecot] Idea: POP3 deletion as a flag
by Timo Sirainen 14 May '13

14 May '13

GMail doesn't delete mails when POP3 client issues a DELE command for it. Instead they just become invisible for future POP3 sessions, but they still exist for IMAP/webmail. The same could be implemented pretty easily for Dovecot: - Add a new setting to enable this: pop3_deleted_flag = $POP3Deleted - When DELEting a message, add this flag to the message. - When listing messages, skip all messages that have this flag. - Also hide this flag from IMAP clients(?) Thoughts? Probably 20 lines of new code.

18 44

[Dovecot] ot: mirroring/archiving to a Mac?
by voytek＠sbt.net.au 14 May '13

14 May '13

I have Doveot 2.1.1 on Centos, all's well user mails are kept for 60 days, then, 'aged off' (deleted) a Mac user with two domains and two dozen users asked me: can I set a mail server on my home Mac server, and, 'mirror' the real mail server mailboxes so than I can have an offline mail archive for ever ? I know very little about Macs, can I setup dovceot on Mac? any tips/suggestions/howtos for mirroring/archiving as so?

5 6

[Dovecot] Pigeonhole: Typo in 20-managesieve.conf
by Gedalya 12 May '13

12 May '13

Line 33: #process_count = 1024 Probably you mean process_limit

2 1

[Dovecot] Any way to let dovecot block pop3 attempts?
by Steve Campbell 12 May '13

12 May '13

Is there a way using dovecot facilities to block an IP from attempting POP3 connections (similar to the sendmail access file for smtp connections)? I usually do this at my border firewall, but if there's a quick and dirty way in dovecot to do this, it'd make life a little simpler. Thanks steve campbell

7 10

[Dovecot] Problem with LDA reject message
by Davide 11 May '13

11 May '13

Hi to all, i have a problem with LDA when users are quota-full. My setup is Vpopmail + dovecot + lda; if i send a messagge internally to a user with quota full i receive correctly a messagge but in the header ( i attacch a snip) From - Fri May 10 14:42:27 2013 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 X-Mozilla-Keys: Return-Path: <"<>"@mail.cgilfe.it> i receive this strange Return-Path. I the messagge is sent outside other servers reply with this messagge: Subject: failure notice Hi. This is the qmail-send program at mail.cgilfe.it. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. <Roberta.Luzzi(a)filcams.cgil.it>: Connected to 80.207.169.234 but sender was rejected. Remote host said: 501 Address Syntax Error in <"<>"@mail.cgilfe.it> this is my .qmail-default file: |/var/qmail/bin/preline -f /usr/local/libexec/dovecot/dovecot-lda -d $EXT@$USER | /home/vpopmail/bin/vdelivermail "" bounce-no-mailbox Thanks in advance. -- *Davide Marchi* *T*eorema *F*errara *Srl* Via Spronello, 7 - Ferrara - 44121 Tel. *0532783161* Fax. *0532783368* E-m@il: *davide.marchi(a)mail.cgilfe.it* Skype: *davide.marchi73* Web: *http://www.cgilfe.it* *CONFIDENZIALITA'* *Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute in questo messaggio sono riservate ed a uso esclusivo del destinatario/dei destinatari. Qualora il messaggio in parola Le fosse pervenuto per errore, La invitiamo ad eliminarlo senza copiarlo e a non inoltrarlo a terzi, dandocene gentilmente comunicazione.* *Per favore, pensa all'ambiente. Stampa questa email solo se necessario.*

2 1

Re: [Dovecot] Any way to let dovecot block pop3 attempts?
by Joseph Tam 11 May '13

11 May '13

Steve Campbell writes: > I use Centos and the default dovecot RPM. I seem to recall there was a > way to determine if dovecot was built with "--with-libwrap". Can anyone > shed light on how to determine this, please? Maybe dovecot --build-options Or you can just test it directly by denying a connection to a test host. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] Remove Return-Path in lda rejection message
by Davide 11 May '13

11 May '13

Is it possible to remove return-path in dovecot lda rejection? -- *Davide Marchi* *T*eorema *F*errara *Srl* Via Spronello, 7 - Ferrara - 44121 Tel. *0532783161* Fax. *0532783368* E-m@il: *davide.marchi(a)mail.cgilfe.it* Skype: *davide.marchi73* Web: *http://www.cgilfe.it* *CONFIDENZIALITA'* *Ai sensi del D.Lgs. 196/2003 si precisa che le informazioni contenute in questo messaggio sono riservate ed a uso esclusivo del destinatario/dei destinatari. Qualora il messaggio in parola Le fosse pervenuto per errore, La invitiamo ad eliminarlo senza copiarlo e a non inoltrarlo a terzi, dandocene gentilmente comunicazione.* *Per favore, pensa all'ambiente. Stampa questa email solo se necessario.*

2 1

[Dovecot] Expunge mailbox from script
by Paul van der Vlis 10 May '13

10 May '13

Hello, I would like to expunge all mail of a mailbox from a script. What's a good tool to do that? With regards, Paul van der Vlis. -- Paul van der Vlis Linux systeembeheer, Groningen http://www.vandervlis.nl/

2 1

Re: [Dovecot] change inbox dotlock name
by Chris Saldanha 10 May '13

10 May '13

Axel Luttgens <AxelLuttgens(a)swing.be> wrote: > But I fear I don't understand your problem description. > Could you elaborate? Hi Axel, The issue is that the procmail port on FreeBSD doesn't acquire a dotlock when it's the default lock file (/var/mail/username.lock). It prints that it's bypassing the dotlock and just does a lockf() lock after. Looking in the code for procmail, it seems that it's being too clever with a bunch of checks and so it doesn't try to get the lock -- it's decided it doesn't want to before doing it. The permissions and runtime environment permit the lock, and the same lock is acquired correctly by dovecot when writing to the inbox. I'm doing dotlock and then lockf() locking in all the mail software. procmail's checks only seem to apply to the default lock file for the inbox. If I specify an alternate name in the .procmailrc for the $ORGMAIL delivery of the message, then it will acquire any other lock I ask, including an alternate name in the /var/mail directory. I'll dig into the procmail sources as needed to resolve it, but I had hoped that I could get dovecot to lock with a different filename, because that would resolve the issue with minimal hackery... Cheers, Chris -- Chris Saldanha Parliant Corporation

2 1

[Dovecot] dovecot not logging after upgrade to 2.1.7 on debian
by Steinar Bang 09 May '13

09 May '13

After upgrading my IMAP server to the new debian stable, and upgrading dovecot from 1.x to 2.1.7 in the process, dovecot no longer logs anything to /var/log/mail.*. The last entries there are from before the upgrade, and no starts or error messages or failed login attempts, since then, have been logged. Does anyone know what might cause this? "doveconf -n" doesn't mention any of the log settings. Maybe the log settings aren't picked up? What could be done to make sure they are picked up? Here's the content of the /etc/dovecot/conf.d/10-logging.conf file: ## ## Log destination. ## # Log file to use for error messages. "syslog" logs to syslog, # /dev/stderr logs to stderr. log_path = syslog # Log file to use for informational messages. Defaults to log_path. #info_log_path = # Log file to use for debug messages. Defaults to info_log_path. #debug_log_path = # Syslog facility to use if you're logging to syslog. Usually if you don't # want to use "mail", you'll use local0..local7. Also other standard # facilities are supported. syslog_facility = mail ## ## Logging verbosity and debugging. ## # Log unsuccessful authentication attempts and the reasons why they failed. #auth_verbose = no # In case of password mismatches, log the attempted password. Valid values are # no, plain and sha1. sha1 can be useful for detecting brute force password # attempts vs. user simply trying the same password over and over again. #auth_verbose_passwords = no # Even more verbose logging for debugging purposes. Shows for example SQL # queries. #auth_debug = no # In case of password mismatches, log the passwords and used scheme so the # problem can be debugged. Enabling this also enables auth_debug. #auth_debug_passwords = no # Enable mail process debugging. This can help you figure out why Dovecot # isn't finding your mails. #mail_debug = no # Show protocol level SSL errors. #verbose_ssl = no # mail_log plugin provides more event logging for mail processes. plugin { # Events to log. Also available: flag_change append #mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename # Available fields: uid, box, msgid, from, subject, size, vsize, flags # size and vsize are available only for expunge and copy events. #mail_log_fields = uid box msgid size } ## ## Log formatting. ## # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " # Space-separated list of elements we want to log. The elements which have # a non-empty variable value are joined together to form a comma-separated # string. #login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c # Login log format. %$ contains login_log_format_elements string, %s contains # the data we want to log. #login_log_format = %$: %s # Log prefix for mail processes. See doc/wiki/Variables.txt for list of # possible variables you can use. #mail_log_prefix = "%s(%u): " # Format to use for logging mail deliveries. You can use variables: # %$ - Delivery status message (e.g. "saved to INBOX") # %m - Message-ID # %s - Subject # %f - From address # %p - Physical size # %w - Virtual size #deliver_log_format = msgid=%m: %$

4 6

[Dovecot] Released Pigeonhole v0.3.5 for Dovecot v2.1.16
by Stephan Bosch 09 May '13

09 May '13

Hello Dovecot users, Before I release the first version of Pigeonhole v0.4, I quickly release a few small but important fixes for Pigeonhole v0.3. Changelog v0.3.5: - Sieve editheader extension: fixed interaction with the Sieve body extension. If used together, the deleteheader action could fail after a body test was performed. - Test suite: fixed a time zone dependency in the Sieve date extension tests. The release is available as follows: http://www.rename-it.nl/dovecot/2.1/dovecot-2.1-pigeonhole-0.3.5.tar.gz http://www.rename-it.nl/dovecot/2.1/dovecot-2.1-pigeonhole-0.3.5.tar.gz.sig Refer to http://pigeonhole.dovecot.org and the Dovecot v2.x wiki for more information. Have fun testing this new release and don't hesitate to notify me when there are any problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl

1 0

[Dovecot] Permission problem with LDA and dovecot 2.2.1
by Tobi 09 May '13

09 May '13

Hello list today I built dovecot 2.2.1 from sources. But I have permission problems with LDA The "normal" imap part works fine, users can login and see their boxes. deliver is called as LDA from postfix master.cf as follows << dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/local/libexec/dovecot/deliver -f ${sender} -d ${user}@${nexthop} >> but when I try to send a testmail then I get the following in the logs << 2013 May 6 18:37:59 nordkap lda: Fatal: Internal error occurred. Refer to server log for more information. May 6 18:37:59 nordkap dovecot: lda: Error: userdb lookup: connect(/var/run/dovecot/auth-userdb) failed: Connection refused May 6 18:37:59 nordkap dovecot: lda: Fatal: Internal error occurred. Refer to server log for more information. >> For me it looks odd because the auth-userdb is defined as << base_dir = /usr/local/var/run/dovecot/ service auth { unix_listener auth-userdb { mode = 0777 user = vmail group = vmail } .... >> The rights on the file should be correct according to the config above << ls -al /usr/local/var/run/dovecot/auth-userdb srwxrwxrwx 1 vmail vmail 0 May 6 20:11 /usr/local/var/run/dovecot/auth-userdb >> I cannot explain why the lda tries to access << Error: userdb lookup: connect(/var/run/dovecot/auth-userdb) >> I grepped through all the configfiles but could not find the "wrong" path from the error message above. Would it might be a "fix" to symlink /usr/local/var/run/dovecot to /var/run/dovecot ? Or would that break something with dovecot? Thanks for any hint or idea tobi

5 12

[Dovecot] SSL problems on dovecot 2.1.7
by Steinar Bang 09 May '13

09 May '13

When I upgraded my debian-based imap server from squeeze to wheezy yesterday, SSL stopped working. I am using a http://cacert.org signed server sertificate, and I am reusing the certificates that were used on the 1.x dovecot of debian squeeze. My three MUAs that worked against the previous 1.x dovecot with the same certificate, now fails in various ways. Any hints and guesses as to how to debug this further will be highly appreciated. Even more appreciated will be a pin point of the issue. :-) Here are the error messages from the MUAs: - Opera 12.15 on Windows 7 just reports: "The connection with the IMAP server was unexpectedly interrupted." - Emacs24(w/linked-in gnutls)/Ma Gnus 0.8 (Gnus git HEAD) on Windows 7 says "imap.mydomain.com certificate could not be verified." - Emacs23/Ma Gnus 0.8 (also Gnus git HEAD) on debian testing (with Emacs23 gnutls-cli is run in a subprocess), says: "Opening connection to imap.mydomain.com via tls... Opening TLS connection to `imap.mydomain.com'... Opening TLS connection with `gnutls-cli --insecure -p 993 imap.mydomain.com'...done Opening TLS connection to `imap.mydomain.com'...done Unable to open server nnimap+privat due to: Process *nnimap* not running" When I try running gnutls-cli from the command line of the debian testing machine (the same gnutls-cli that is used by the emacs23/gnus combo), it seems to connect ok (the transcript of that session is below). The config for the SSL, from /etc/dovecot/conf.d/10-ssl.conf, is: # SSL/TLS support: yes, no, required. <doc/wiki/SSL.txt> ssl = yes # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf ssl_cert = </etc/ssl/certs/imap_mydomain_com.pem ssl_key = </etc/ssl/private/imap_mydomain_com.key The access privileges of the files, are: -rw-r--r-- 1 root root 2077 Mar 27 12:45 /etc/ssl/certs/imap_mydomain_com.pem -rw------- 1 root root 3243 Jul 12 2011 /etc/ssl/private/imap_mydomain_com.key What follows, is the transcript from the gnutls-cli session from a debian testing machine to the server (which seems to be working as far as I can tell...): sb@edwards:~$ gnutls-cli -p 993 rainey.mydomain.com WARNING: gnome-keyring:: couldn't connect to: /home/sb/.cache/keyring-yeEdM3/pkcs11: No such file or directory Resolving 'rainey.mydomain.com'... Connecting to '212.110.185.190:993'... - Ephemeral Diffie-Hellman parameters - Using prime: 1024 bits - Secret key: 1023 bits - Peer's public key: 1023 bits - Certificate type: X.509 - Got a certificate list of 1 certificates. - Certificate[0] info: - subject `CN=imap.mydomain.com', issuer `O=Root CA,OU=http://www.cacert.org,CN=CA Cert Signing Authority,EMAIL=support(a)cacert.org', RSA key 4096 bits, signed using RSA-SHA1, activated `2013-03-27 12:43:30 UTC', expires `2013-09-23 12:43:30 UTC', SHA-1 fingerprint `86f8a501bca1e2b0eadc677bf05b103d298ce247' - The hostname in the certificate does NOT match 'rainey.mydomain.com' sb@edwards:~$ gnutls-cli -p 993 imap.mydomain.com WARNING: gnome-keyring:: couldn't connect to: /home/sb/.cache/keyring-yeEdM3/pkcs11: No such file or directory Resolving 'imap.mydomain.com'... Connecting to '212.110.185.190:993'... - Ephemeral Diffie-Hellman parameters - Using prime: 1024 bits - Secret key: 1022 bits - Peer's public key: 1021 bits - Certificate type: X.509 - Got a certificate list of 1 certificates. - Certificate[0] info: - subject `CN=imap.mydomain.com', issuer `O=Root CA,OU=http://www.cacert.org,CN=CA Cert Signing Authority,EMAIL=support(a)cacert.org', RSA key 4096 bits, signed using RSA-SHA1, activated `2013-03-27 12:43:30 UTC', expires `2013-09-23 12:43:30 UTC', SHA-1 fingerprint `86f8a501bca1e2b0eadc677bf05b103d298ce247' - The hostname in the certificate matches 'imap.mydomain.com'. - Peer's certificate issuer is unknown - Peer's certificate is NOT trusted - Version: TLS1.2 - Key Exchange: DHE-RSA - Cipher: AES-128-CBC - MAC: SHA1 - Compression: NULL - Handshake was completed - Simple Client Mode: * OK Waiting for authentication process to respond.. - Peer has closed the GnuTLS connection

1 0

[Dovecot] dovecot stats
by Jan-Frode Myklebust 09 May '13

09 May '13

I just upgraded one of our servers to dovecot v2.1.16 (ee), and am looking into the stats feature. Am I interpreting the wiki correct in reading that the "doveadm stats dump command" only returns statistics about IMAP commands? Is it possible to collect info about POP3 and LMTP commands also ? Also, is "doveadm stats dump command" telling me the results of all commands that has finished the last stats_command_min_time, or will it maybe contain much more than 1 minute of activity ? -jf

3 5

[Dovecot] AuthenticationFailedException: [IN-USE] Couldn't open INBOX: Permission denied
by Earles, Jill 09 May '13

09 May '13

I've been pouring over the documentation for dovecot, but can't find a solution to this problem. I recently took over administration of the dovecot email service at the University where I work, and things were going smoothly. We've been creating email accounts for use with JIRA, a bug reporting/tracking system, and one day recently, when I tried to add a new account to JIRA, I got this error returned from dovecot: "AuthenticationFailedException: [IN-USE] Couldn't open INBOX: Permission denied" I got help from Atlassian, the creators of JIRA, and they sent me links to some forum posts that said that changing the permissions of that user's /var/mail/ directory to 0600 would solve the problem. I changed that and no longer got the error. Being satisfied that this was a solution, I created a bunch of new email accounts today to replace exchange accounts, and then changed the permissions on all the /var/mail/ directories to 0600. Now I'm getting that error again, even for pre-existing email addresses, including the one that I had previously fixed by changing the permissions the same way. I tried changing some of the older accounts back to 0660, which is what they had before, and I still get the error even after restarting dovecot. JIRA uses POP, port 110, to connect to the dovecot mail server. I've also had the same problem trying to connect from Mac Mail. Our JIRA application is used for tracking issues for the UBC Libraries, and those email addresses are critical for the creation of tickets and adding comments to tickets. I am at a loss for what to do. Can anyone help? Thank you very much for your time. # dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-131.0.15.el6.x86_64 x86_64 Red Hat Enterprise Linux Server release 6.4 (Santiago) auth_debug = yes auth_debug_passwords = yes disable_plaintext_auth = no mail_access_groups = mail mail_location = mbox:~/mail:INBOX=/var/spool/mail/%u mail_privileged_group = mail mbox_write_locks = fcntl passdb { driver = pam } ssl_cert = </etc/pki/dovecot/certs/server.crt ssl_key = </etc/pki/dovecot/private/server.key userdb { driver = passwd } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } Here's an except of the maillog from a recent attempt: May 8 17:46:49 moose dovecot: auth: Debug: pam(lib.sysadmin,{ip removed}): lookup service=dovecot May 8 17:46:49 moose dovecot: auth: Debug: pam(lib.sysadmin,{ip removed}): #1/1 style=1 msg=Password: May 8 17:46:49 moose dovecot: auth: Debug: client out: OK#0111#011user=lib.sysadmin May 8 17:46:49 moose dovecot: auth: Debug: master in: REQUEST#0111028653057#01128298#0111#011a60ed90501af39d7e353a14e027255cd May 8 17:46:49 moose dovecot: auth: Debug: passwd(lib.sysadmin,{ip removed}): lookup May 8 17:46:49 moose dovecot: auth: Debug: master out: USER#0111028653057#011lib.sysadmin#011system_groups_user=lib.sysadmin#011uid=523#011gid=524#011home=/home/lib.sysadmin May 8 17:46:49 moose dovecot: pop3-login: Login: user=<lib.sysadmin>, method=PLAIN, rip={ip removed}, lip={ip removed}, mpid=28302 May 8 17:46:49 moose dovecot: pop3(lib.sysadmin): Error: stat(/var/spool/mail/lib.sysadmin) failed: Permission denied May 8 17:46:49 moose dovecot: pop3(lib.sysadmin): Error: stat(/var/spool/mail/lib.sysadmin) failed: Permission denied May 8 17:46:49 moose dovecot: pop3(lib.sysadmin): Error: Couldn't open INBOX: Permission denied May 8 17:46:49 moose dovecot: pop3(lib.sysadmin): Couldn't open INBOX top=0/0, retr=0/0, del=0/0, size=0 May 8 17:46:50 moose dovecot: auth: Debug: auth client connected (pid=28303) May 8 17:46:50 moose dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=pop3#011lip={ip removed}#011rip={ip removed}#011lport=110#011rport=64420#011resp=AGJ2YXV3LnJlbGFpcwByM2xAaXMuYnZAdXc=

2 8

[Dovecot] change inbox dotlock name
by Chris Saldanha 08 May '13

08 May '13

Hi, Is there a configuration element that would allow me to change the dot-lock name for the user's /var/mail inbox when it is locked? dovecot (correctly) acquires <username>.lock, but I'm having a problem with procmail where some obscure code path is preventing procmail's acquisition of a lock when it's that default name in /var/mail. The issue is not permissions (using a world-writeable and sticky-bit config for /var/mail). I'll dig into the procmail code if needed, but if dovecot could use a different filename for such locks, then that would solve my issue. procmail has such an option, and I only need to do this for inboxes. Thanks, Chris -- Chris Saldanha Parliant Corporation

2 1

[Dovecot] sieve redirect envelope address problem
by Костырев Александр Алексеевич 08 May '13

08 May '13

Good day! I have a problem with mail redirection through sieve rules. I've configured sieve rule that redirects any mail coming to user to gmail mailbox (or whatever external mail system there is). But when sieve redirects any mail it puts vmail@%dovecot_hostname% into envelope address, gives it to my exim for delivery and gmail rejects my mail because user vmail@%dovecot_hostname% do not exist. Please, advice for what can be done about this behavior. my `doveconf -n` http://pastebin.com/0dyL9Jgs Thanks in advance! -- С уважением, Костырев Александр администратор Linux-систем

4 4

[Dovecot] CATENATE mis-reads literal after bad URL
by Mike Abbott 08 May '13

08 May '13

Dovecot-2.2.1 plus Timo's recent CATENATE and URLAUTH fixes mishandles literals after bad URLs. (As before remember that the "foobar" text below is really "foobarCRLF" hence the length of 8. Also, last time some MTA discarded an important single leading space character in the snippet I quoted so this time I'm prefixing all the lines to avoid that. In case it's lost again, there's a space before the word "url" below.) | b append inbox catenate (text {8} | + OK | foobar | url /a-bad-url text {8} | b NO [BADURL /a-bad-url] Invalid messagepart IMAP URL. | c noop | d noop | d OK NOOP completed. | e logout | * BYE Logging out | e OK Logout completed. Note that the command with tag "c" is lost. I think it shouldn't be, because the NO was reported to the client without sending a continuation (+ OK) so the client knows not to send the literal. Plus it appears only one line is discarded regardless of the size of the literal.

2 2

[Dovecot] URLAUTH assertion failures in 2.2.1
by Mike Abbott 07 May '13

07 May '13

Testing URLAUTH in dovecot-2.2.1 plus Timo's recent CATENATE and URLAUTH fixes eventually trips some assertions. No simple sequence of commands always hits these; they appear to be timing-dependent. The first one is: May 02 17:47:17 imap(pid 50490 user submit): Panic: file imap-client.c: line 643 (client_command_free): assertion failed: (client->output_cmd_lock == NULL) The line number doesn't match dovecot-2.2.1 due to Apple's unrelated modifications. 0 libsystem_kernel.dylib 0x00007fff8a9f7d4a __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007fff8f728705 pthread_kill + 92 2 libsystem_c.dylib 0x00007fff8f48b17b abort + 125 3 libdovecot.0.dylib 0x000000010db8d2bb default_fatal_finish + 68 4 libdovecot.0.dylib 0x000000010db8df66 i_internal_error_handler + 0 5 libdovecot.0.dylib 0x000000010db8d53d i_panic + 158 6 imap 0x000000010da468fe client_command_free + 446 7 imap 0x000000010da47a33 client_output_cmd + 37 8 imap 0x000000010da46497 client_output + 143 9 libdovecot.0.dylib 0x000000010dba5610 stream_send_io + 53 10 libdovecot.0.dylib 0x000000010db9bc74 io_loop_call_io + 46 11 libdovecot.0.dylib 0x000000010db9cc85 io_loop_handler_run + 214 12 libdovecot.0.dylib 0x000000010db9be1f io_loop_run + 77 13 libdovecot.0.dylib 0x000000010db5b0c6 master_service_run + 24 14 imap 0x000000010da4fa66 main + 1010 15 libdyld.dylib 0x00007fff8f7887bd start + 1 The second one is: May 02 19:23:29 imap(pid 60229 user mja): Panic: file index-mail.c: line 1274 (index_mail_close_streams_full): assertion failed: (!mail->data.destroying_stream) 0 libsystem_kernel.dylib 0x00007fff8a9f7d4a __pthread_kill + 10 1 libsystem_pthread.dylib 0x00007fff8f728705 pthread_kill + 92 2 libsystem_c.dylib 0x00007fff8f48b17b abort + 125 3 libdovecot.0.dylib 0x00000001054c42bb default_fatal_finish + 68 4 libdovecot.0.dylib 0x00000001054c4f66 i_internal_error_handler + 0 5 libdovecot.0.dylib 0x00000001054c453d i_panic + 158 6 libdovecot-storage.0.dylib 0x00000001053aaebb index_mail_close_streams_full + 199 7 libdovecot-storage.0.dylib 0x00000001053aaf29 index_mail_close + 44 8 libdovecot-storage.0.dylib 0x00000001053ab6bd index_mail_free + 48 9 libdovecot-storage.0.dylib 0x000000010538a19a mail_free + 15 10 libdovecot-storage.0.dylib 0x00000001053dd3b3 imap_msgpart_url_free + 65 11 imap 0x000000010532d563 imap_urlauth_fetch_abort_local + 30 12 imap 0x000000010532cb96 imap_urlauth_fetch_abort + 38 13 imap 0x000000010532cb54 imap_urlauth_fetch_deinit + 24 14 imap 0x00000001053218bd cmd_urlfetch_finish + 45 15 imap 0x0000000105321aa3 cmd_urlfetch_continue + 167 16 imap 0x0000000105323ef8 command_exec + 55 17 imap 0x0000000105323a20 client_output_cmd + 18 18 imap 0x0000000105322497 client_output + 143 19 libdovecot.0.dylib 0x00000001054dc610 stream_send_io + 53 20 libdovecot.0.dylib 0x00000001054d2c74 io_loop_call_io + 46 21 libdovecot.0.dylib 0x00000001054d3c85 io_loop_handler_run + 214 22 libdovecot.0.dylib 0x00000001054d2e1f io_loop_run + 77 23 libdovecot.0.dylib 0x00000001054920c6 master_service_run + 24 24 imap 0x000000010532ba66 main + 1010 25 libdyld.dylib 0x00007fff8f7887bd start + 1

2 2

[Dovecot] Dovecot Postfix Quota Policy Service
by Daniel Luttermann 07 May '13

07 May '13

Hallo zusammen, über den Policy Service von Dovecot zum Abfragen der User Quotas wurde ja schon diskutiert - auch gibt es eine gute Anleitung zum Einrichten, nur leider bekomme ich den Policy Server nicht korrekt konfiguriert. Folgende Fehler werden protokolliert: May 3 22:00:13 mail postfix/smtpd[17463]: warning: access table unix:private/quota-status entry has empty value May 3 22:00:42 mail dovecot: quota-status(daniel(a)dlutt.de): Error: user daniel(a)dlutt.de: Error reading configuration: net_connect_unix(/usr/var/run/dovecot/config) failed: Permission denied Es ist dabei so, dass nach einem Reload der Dienste die erste Mail noch zugestellt wird, die folgende, eingehende Mail dann jedoch abgelehnt wird. Nachfolgend die kompletten Logeinträge: May 3 22:00:12 mail postfix/smtpd[17463]: connect from mail-ie0-x236.google.com[2607:f8b0:4001:c03::236] May 3 22:00:13 mail postfix/smtpd[17463]: warning: access table unix:private/quota-status entry has empty value May 3 22:00:13 mail postfix/smtpd[17463]: 0EB81172391A: client=mail-ie0-x236.google.com[2607:f8b0:4001:c03::236] May 3 22:00:13 mail postfix/cleanup[17475]: 0EB81172391A: message-id=<CAKrzS114MaJGND9BxYUiixMMtORmXJqTA3W13B=QAr0YW_nkUg(a)mail.gmail.com> May 3 22:00:13 mail postfix/qmgr[17429]: 0EB81172391A: from=<sender(a)googlemail.com>, size=5409, nrcpt=1 (queue active) May 3 22:00:13 mail postfix/smtpd[17463]: disconnect from mail-ie0-x236.google.com[2607:f8b0:4001:c03::236] May 3 22:00:13 mail klms-smtp_proxy: Message from sender(a)googlemail.com to daniel(a)dlutt.de passed May 3 22:00:14 mail postfix/smtpd[17482]: connect from localhost[127.0.0.1] May 3 22:00:14 mail postfix/smtpd[17482]: 00776172391C: client=localhost[127.0.0.1], orig_client=mail-ie0-x236.google.com[2607:f8b0:4001:c03::236] May 3 22:00:14 mail postfix/cleanup[17475]: 00776172391C: message-id=<CAKrzS114MaJGND9BxYUiixMMtORmXJqTA3W13B=QAr0YW_nkUg(a)mail.gmail.com> May 3 22:00:14 mail postfix/qmgr[17429]: 00776172391C: from=<sender(a)googlemail.com>, size=6195, nrcpt=1 (queue active) May 3 22:00:14 mail postfix/smtpd[17482]: disconnect from localhost[127.0.0.1] May 3 22:00:14 mail postfix/smtp[17476]: 0EB81172391A: to=<daniel(a)dlutt.de>, relay=127.0.0.1[127.0.0.1]:10025, delay=1.2, delays=0.54/0.02/0/0.65, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 00776172391C) May 3 22:00:14 mail postfix/qmgr[17429]: 0EB81172391A: removed May 3 22:00:14 mail dovecot: lmtp(17484): Connect from local May 3 22:00:14 mail dovecot: lmtp(17484, daniel(a)dlutt.de) dEa8BE4XhFFMRAAAG4AjPw: sieve: msgid=<CAKrzS114MaJGND9BxYUiixMMtORmXJqTA3W13B=QAr0YW_nkUg(a)mail.gmail.com>: stored mail into mailbox 'INBOX' May 3 22:00:14 mail dovecot: lmtp(17484): Disconnect from local: Successful quit May 3 22:00:14 mail postfix/lmtp[17483]: 00776172391C: to=<daniel(a)dlutt.de>, relay=mail.dlutt.de[private/dovecot-lmtp], delay=0.11, delays=0.05/0.02/0.01/0.03, dsn=2.0.0, status=sent (250 2.0.0 <daniel(a)dlutt.de> dEa8BE4XhFFMRAAAG4AjPw Saved) May 3 22:00:14 mail postfix/qmgr[17429]: 00776172391C: removed May 3 22:00:36 mail postfix/postscreen[17433]: CONNECT from [2607:f8b0:4001:c03::230]:43653 to [2a00:1828:2000:206::2]:25 May 3 22:00:42 mail postfix/postscreen[17433]: PASS NEW [2607:f8b0:4001:c03::230]:43653 May 3 22:00:42 mail postfix/smtpd[17463]: connect from mail-ie0-x230.google.com[2607:f8b0:4001:c03::230] May 3 22:00:42 mail dovecot: quota-status(daniel(a)dlutt.de): Error: user daniel(a)dlutt.de: Error reading configuration: net_connect_unix(/usr/var/run/dovecot/config) failed: Permission denied May 3 22:00:42 mail postfix/smtpd[17463]: NOQUEUE: reject: RCPT from mail-ie0-x230.google.com[2607:f8b0:4001:c03::230]: 450 4.7.1 <daniel(a)dlutt.de>: Recipient address rejected: Internal error occurred. Refer to server log for more information.; from=<absender(a)googlemail.com> to=<daniel(a)dlutt.de> proto=ESMTP helo=<mail-ie0-x230.google.com> May 3 22:00:42 mail postfix/smtpd[17463]: disconnect from mail-ie0-x230.google.com[2607:f8b0:4001:c03::230] May 3 22:00:53 mail postfix/postfix-script[17560]: stopping the Postfix mail system May 3 22:00:53 mail postfix/master[17425]: terminating on signal 15 May 3 22:02:51 mail dovecot: master: Warning: Killed with signal 15 (by pid=17681 uid=0 code=kill) Das Problem tritt mit dem unix_listener, aber auch mit dem inet_listener auf - beide Male beschwert sich Dovecot über den Zugriff auf den Service "config". Ich habe auch mal versucht, die Berechtigungen für den Service "config" auf World-Readable zu setzen, leider hat dies auch nicht geklappt, wobei ich nicht weiß, ob dieser unbedingt mit dem Problem etwas zu tun hat. Auch beim Debug-Logging sind leider nicht mehr Infos zum Fehler zu finden. Zum Einsatz kommt aktuell Postfix 2.10.0 und Dovecot 2.2.1. Die Dovecot Quota Konfiguration sieht so aus, wie bei sys4 beschrieben: service quota-status { executable = quota-status -p postfix unix_listener /var/spool/postfix/private/quota-status { group = postfix mode = 0660 user = postfix } client_limit = 1 } Mittlerweile habe ich schon einige Optionen und Berechtigungen ausprobiert, aber der Fehler bleibt leider der gleiche. Hat vielleicht jemand noch einen Tip? Danke schon mal. -- Daniel

6 18

[Dovecot] pop3 login ok then disconnects right away..outlook
by markh 07 May '13

07 May '13

I have dovecot with postfix on ubuntu server 12 I cannot log into outgoing server with outlook. It logs into incoming server ok with outlook. I can telnet pop3 and imap ok. Looking at mail log it looks like dovecot auths: ok then shows pop3-login: Login: user=<user> USER#etc ok ... then next line shows..same second pop3(user): disconnected: Logged out top/0/0 etc. I have tried a lot of combinations with ssl ,tls none Any suggestions...thanks -- View this message in context: http://dovecot.2317879.n4.nabble.com/pop3-login-ok-then-disconnects-right-a… Sent from the Dovecot mailing list archive at Nabble.com.

2 1