- dovecot - dovecot.org

[Dovecot] sievec fails when last line is a comment without trailing \n
by Peter Marschall 11 Oct '09

11 Oct '09

Hi, when switching from Dovecot 1.1 + cmusieve to Dovecot 1.2 + sieve I stumbled upon the following problem: My sieve files, generated with Dovecot 1.1's managesieve, did not compile anymore with sieve's sievec. The error message was: error: end of file before end of hash comment. Looking a bit closer I found that the last line, which was a comment, did not have a trailing newline. Adding a newline fixed the problem. I do not know if Dovecot 1.2's managesieve behaves differently, but the upgrade from cmusieve to sieve In the spirit of "be generous in what you accept but strict in what you send", is it possible for sievec to not throw an error in this case, but simply compile the file. This might help other updates from cmusieve -> sieve as well. Thanks in advance. Peter -- Peter Marschall peter(a)adpm.de

2 2

[Dovecot] soft quota lda question
by toni＠dingsbums.org 11 Oct '09

11 Oct '09

hi all, i'm using dovecot deliver (lda) and i want to show quota to the users via imap/pop3, but i don't want to enforce it (i.e. don't reject/bounce mails when quota is exceeded). protocol imap { mail_plugins = quota imap_quota } protocol pop3 { mail_plugins = quota } # In case you're using deliver: protocol lda { #mail_plugins = quota } does it work if i just comment out the "mail_plugin = quota" in the protocol lda section and leave the imap/pop3 configuration or is there another better way to do this? thanks in advance, someone2.0

2 1

[Dovecot] status & use-case of fts_solr?
by PGNet Dev 10 Oct '09

10 Oct '09

i've deployed a Solr server, and setup Dovecot for *both* squat & solr FTS. iiuc, reading at, http://wiki.dovecot.org/Plugins/FTS http://wiki.dovecot.org/Plugins/FTS/Solr as of dovecot v1.1.2, squat's required for IMAP compliance; solr search breaks it. is that still the case in v1.2? Is IMAP-compliant Solr search possible? planned? if the goal is fast, indexed FTS of dovecot IMAP stores from within a MUA, is fts_solr even helpful? or is it targeted for web interfaces to search ... ? thanks.

3 7

[Dovecot] mail archiving
by dhottinger＠harrisonburg.k12.va.us 10 Oct '09

10 Oct '09

Im curious if anyone is archiving emails and what they are using. I currently utilize sendmail/procmail/dovecot. thanks, ddh -- Dwayne Hottinger Network Administrator Harrisonburg City Public Schools "Everything should be made as simple as possible, but not simpler." -- Albert Einstein "The hottest places in Hell are reserved for those who, in times of moral crisis, preserved their neutrality." -- Dante

4 5

Re: [Dovecot] What exactly do you mean by archiving?
by dhottinger＠harrisonburg.k12.va.us 10 Oct '09

10 Oct '09

I mean every single email sent and recieved is kept for a period of time (3 -5 years) separate from users mail, and emails cant be deleted. Ideally emails would have compression, mailboxes need to be searchable easily, and some mechanism whereby attachments sent to multiple people only get saved once, and emails sent to multiple people only get saved once. I could do something with procmail that copies every email coming in to another directory easily, but that doesnt solve the sent email. Ive looked at several commercial products, but none seem to work nicely with sendmail. Thanks for the information, I'll look and see if sieve will work better for me than procmail. Im not sure thought that your method will pass the test come litigation time (if that every happens). thanks, ddh -- Dwayne Hottinger Network Administrator Harrisonburg City Public Schools "Everything should be made as simple as possible, but not simpler." -- Albert Einstein "The hottest places in Hell are reserved for those who, in times of moral crisis, preserved their neutrality." -- Dante

2 1

[Dovecot] @2.0, --sysconfdir incorrectly populated with dovecot/*.conf
by PGNet Dev 10 Oct '09

10 Oct '09

to document from #irc, in 1.2.x, specifying ./configure ... --sysconfdir=/path/to/dir ... correctly results in dovecot.conf looked for as "/path/to/dir/dovecot.conf". in 2.0, dovecot incorrectly creates a dovecot dir in the sysconfdir, and looks for, /path/to/dir/dovecot/dovecot.conf 2.0's behavior should be made consistent with the correct implementation in 1.2.x, or clarified as different in --help/docs. thanks.

2 3

[Dovecot] very frequent disconnections
by Dan Christensen 09 Oct '09

09 Oct '09

I've installed dovecot 1:1.1.11-0ubuntu4.1 on my jaunty system. Access from the same host works well, but when I access remotely (from various MUAs and networks) I get *very* frequent disconnects. Authentication is fine, and I can usually open a mail folder, but larger operations such as copying 20 messages into an imap folder always get disconnected. I can reconnect, but I often get disconnected again in a few seconds, especially if I do more than very light access. I've enabled all the logging I'm aware of, but I don't see any explanations. I get things like Oct 7 20:19:38 jdc dovecot: auth(default): new auth connection: pid=390 Oct 7 20:19:39 jdc dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservice=imap^Isecured^Ilip=129.100.75.85^Irip=65.95.132.250^Ilport=143^Irport=62044^Iresp=<hidden> Oct 7 20:19:39 jdc dovecot: auth-worker(default): pam(jdc,65.95.132.250): lookup service=dovecot Oct 7 20:19:39 jdc dovecot: auth-worker(default): pam(jdc,65.95.132.250): #1/1 style=1 msg=Password: Oct 7 20:19:39 jdc dovecot: auth(default): client out: OK^I1^Iuser=jdc Oct 7 20:19:39 jdc dovecot: auth(default): master in: REQUEST^I2^I367^I1 Oct 7 20:19:39 jdc dovecot: auth(default): passwd(jdc,65.95.132.250): lookup Oct 7 20:19:39 jdc dovecot: auth(default): master out: USER^I2^Ijdc^Isystem_user=jdc^Iuid=1000^Igid=1000^Ihome=/home/jdc Oct 7 20:19:39 jdc dovecot: IMAP(jdc): Effective uid=1000, gid=1000, home=/home/jdc Oct 7 20:19:39 jdc dovecot: IMAP(jdc): maildir: data=~/Maildir Oct 7 20:19:39 jdc dovecot: IMAP(jdc): maildir++: root=/home/jdc/Maildir, index=, control=, inbox=/home/jdc/Maildir Oct 7 20:19:40 jdc dovecot: IMAP(jdc): Connection closed bytes=303/1423 and Oct 7 20:43:54 jdc dovecot: auth(default): new auth connection: pid=6620 Oct 7 20:43:55 jdc dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservice=imap^Isecured^Ilip=129.100.75.85^Irip=65.95.132.250^Ilport=143^Irport=62633^Iresp=<hidden> Oct 7 20:43:55 jdc dovecot: auth-worker(default): pam(jdc,65.95.132.250): lookup service=dovecot Oct 7 20:43:55 jdc dovecot: auth-worker(default): pam(jdc,65.95.132.250): #1/1 style=1 msg=Password: Oct 7 20:43:55 jdc dovecot: auth(default): client out: OK^I1^Iuser=jdc Oct 7 20:43:55 jdc dovecot: auth(default): master in: REQUEST^I5^I6594^I1 Oct 7 20:43:55 jdc dovecot: auth(default): passwd(jdc,65.95.132.250): lookup Oct 7 20:43:55 jdc dovecot: auth(default): master out: USER^I5^Ijdc^Isystem_user=jdc^Iuid=1000^Igid=1000^Ihome=/home/jdc Oct 7 20:43:55 jdc dovecot: imap-login: Login: user=<jdc>, method=PLAIN, rip=65.95.132.250, lip=129.100.75.85, TLS Oct 7 20:43:55 jdc dovecot: IMAP(jdc): Effective uid=1000, gid=1000, home=/home/jdc Oct 7 20:43:55 jdc dovecot: IMAP(jdc): maildir: data=~/Maildir Oct 7 20:43:55 jdc dovecot: IMAP(jdc): maildir++: root=/home/jdc/Maildir, index=, control=, inbox=/home/jdc/Maildir Oct 7 20:44:00 jdc dovecot: IMAP(jdc): Disconnected in APPEND bytes=1081/1965 The output of dovecot -n is: # 1.1.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.28-15-generic x86_64 Ubuntu 9.04 log_timestamp: %Y-%m-%d %H:%M:%S ssl_cert_file: /etc/ssl/certs/dovecot.pem ssl_key_file: /etc/ssl/private/dovecot.pem verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_greeting_capability: yes max_mail_processes: 25 mail_max_userip_connections: 20 mail_privileged_group: mail mail_location: maildir:~/Maildir mail_debug: yes maildir_copy_preserve_filename: yes auth default: verbose: yes debug: yes passdb: driver: pam userdb: driver: passwd The clients I have tried are Gnus (with starttls and gnutls-cli) and evolution, on a jaunty system; and k9mail-beta on an HTC Dream cell phone. All four configurations show similar connection issues, and the jaunty client system has a solid DSL connection to the server. The clients don't have informative error messages either. To them it just appears that the connection was closed. Any idea what could be causing this? Or how to debug it? Thanks, Dan -- Dan Christensen jdc(a)uwo.ca

2 4

[Dovecot] Binary locations
by Timo Sirainen 09 Oct '09

09 Oct '09

Where do you think the following binaries should be installed to? The possible locations are: - bin/ - sbin/ - libexec/dovecot/ (or lib/dovecot/ in most Linux distros) So the binaries are: 1) These probably belong to bin/ or sbin/ or both: - authtest - dovecotpw - doveadm 2) Binaries that you might want to call from mail_executable setting: - rawlog - gdbhelper 3) Index file dumping programs, mostly meant for debugging problems: - idxview - listview - logview - mailboxlogview - threadview 4) Some extra tools that might be useful sometimes: - imap-utf7 : Encode/decode IMAP mailbox names (mUTF-7 <-> UTF-8) - maildirlock : Lock a Maildir, primarily intended for compressing files in maildir And perhaps some of the binaries should be renamed? The authtest actually now looks like a bad name. Maybe it should have been "doveauthtest" or "dovecot-authtest" or ..?

9 11

[Dovecot] Using sieve with virtual delivery & maildir
by Jerry 09 Oct '09

09 Oct '09

I am using Postfix virtual users/domains with Dovecot virtual delivery to maildir style mailboxes. Now I want to get sieve working to sort out a few minor delivery problems. I want all mail with a message header "Delivered-To: foo+bar(a)domain.com placed in the /var/mail/vhost/example.com/foo/new directory. Would this work: require "fileinto"; if anyof (header :contains "Delivered-To" "foo+bar(a)domain.com") { fileinto "foo(a)example.com"; stop; } Running 'sieve-test' works OK; however, I do not want to implement it and suddenly start losing mail. -- Jerry gesbbb(a)yahoo.com Outside of a dog, a book is a man's best friend: and inside a dog, it's too dark to read. Groucho Marx

3 2

[Dovecot] how to config dovecot for multiple domains, multiple SSL certs, and conditional IP access -- with passwd-file passdb?
by PGNet Dev 09 Oct '09

09 Oct '09

at them moment, i've configured dovecot for a flat passwd-file, annd static userdb. from dovecot.conf, ... auth default { mechanisms = plain digest-md5 cram-md5 user = mail ... passdb passwd-file { args = /data/mail/users/imap_user_file } userdb static { args = static uid=mail gid=mail home=/data/mail/store/Domains/%d/Accounts/%n quota=maildir:storage=4096 nice=10 } ... i'd like to configure dovecot to, host multiple domains, each on a separate IP setup a separate SSL cert for each domain respond with a different login_greeting for each domain restrict access to, and access type (e.g., TLS req'd vs noTLS, secure auth OK) of, imap login based with conditional rules based on the guest's IP address. all of these things are currently implemented on the non-dovecot imap server i'm migrating _from_, and i'd like to preserve these capabilities. can any/all of these be accomplished with a passwd-file flatfile lookup? i know i can restrict IP access in passwd-file with 'allow_nets=', but atm i'm unclear how i'd do that for multiple domains, etc. i understand that much can be accomplished with custom SQL queries, but for a small install would _prefer_ to stay flat file. i'm finding bits & pieces of capability in docs, etc -- but, so far, nothing comprehensive/all-inclusive. which makes me wonder a bit -- why not? any comments/advice would be much appreciated. thanks!

3 2