Re: v2.2.22 released

[Gerhard Wiesinger]

On 16.03.2016 09:27, Timo Sirainen wrote:

http://dovecot.org/releases/2.2/dovecot-2.2.22.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.22.tar.gz.sig

  - Expunges were forgotten in some situations, for example when
pipelining multiple IMAP MOVE commands.




Ad Expunge: I'm using Thunderbird latest with Xpunge Addon: 
http://www.theodoretegos.net/mozilla/tb/index.html


Since some time I'm having the problem that when I press "XPUNGE" I get 
the following error message: "Some folders (e.g. foldername) cannot be 
compacted because there is not enough free disk space. Please delete 
some files and try again."


I was hoping it was fixed with 2.2.22.

Diskspace is of course enough available (locally and on imap server), 
using Maildir.


Anyone having the same issues or any ideas?

Thnx.

Ciao,
Gerhard

https://www.wiesinger.com/

Re: v2.2.21 released

[Gerhard Wiesinger]

On 11.12.2015 18:10, Timo Sirainen wrote:

http://dovecot.org/releases/2.2/dovecot-2.2.21.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.21.tar.gz.sig



Hello Timo,

tried to compile it, but tests fail on Fedora 23 with latest gcc 
(gcc-5.3.1-2.fc23.x86_64):

fts_icu_utf8_to_utf16 ascii resize ... : ok
fts_icu_utf8_to_utf16 32bit resize ... : ok
fts_icu_utf16_to_utf8  : ok
fts_icu_utf16_to_utf8 resize . : ok
fts_icu_translate  : ok
fts_icu_translate_resize resize .. : ok
fts_icu_lcase  : ok
fts_icu_lcase resize . : ok
0 / 8 tests failed
==11141== Conditional jump or move depends on uninitialised value(s)
==11141==at 0x512C753: 
icu_54::LocaleUtility::initLocaleFromName(icu_54::UnicodeString const&, 
icu_54::Locale&) (in /usr/lib64/libicuuc.so.54.1)
==11141==by 0x4DB1E70: 
icu_54::TransliteratorSpec::TransliteratorSpec(icu_54::UnicodeString 
const&) (in /usr/lib64/libicui18n.so.54.1)
==11141==by 0x4DB28D4: 
icu_54::TransliteratorRegistry::find(icu_54::UnicodeString&, 
icu_54::UnicodeString&, icu_54::UnicodeString&) (in 
/usr/lib64/libicui18n.so.54.1)
==11141==by 0x4DB2B76: 
icu_54::TransliteratorRegistry::find(icu_54::UnicodeString const&) (in 
/usr/lib64/libicui18n.so.54.1)
==11141==by 0x4DB2BFA: 
icu_54::TransliteratorRegistry::get(icu_54::UnicodeString const&, 
icu_54::TransliteratorAlias*&, UErrorCode&) (in 
/usr/lib64/libicui18n.so.54.1)
==11141==by 0x4D9D58D: 
icu_54::Transliterator::createBasicInstance(icu_54::UnicodeString 
const&, icu_54::UnicodeString const*) (in /usr/lib64/libicui18n.so.54.1)
==11141==by 0x4DA3DEC: 
icu_54::TransliteratorIDParser::SingleID::createInstance() (in 
/usr/lib64/libicui18n.so.54.1)
==11141==by 0x4DA432B: 
icu_54::TransliteratorIDParser::instantiateList(icu_54::UVector&, 
UErrorCode&) (in /usr/lib64/libicui18n.so.54.1)
==11141==by 0x4D9E9DA: 
icu_54::Transliterator::createInstance(icu_54::UnicodeString const&, 
UTransDirection, UParseError&, UErrorCode&) (in 
/usr/lib64/libicui18n.so.54.1)
==11141==by 0x4D9F6E9: utrans_openU_54 (in 
/usr/lib64/libicui18n.so.54.1)

==11141==by 0x10B9F5: get_translit (test-fts-icu.c:90)
==11141==by 0x10BBFC: test_fts_icu_translate (test-fts-icu.c:106)
==11141==
==11141== Conditional jump or move depends on uninitialised value(s)
==11141==at 0x512C753: 
icu_54::LocaleUtility::initLocaleFromName(icu_54::UnicodeString const&, 
icu_54::Locale&) (in /usr/lib64/libicuuc.so.54.1)
==11141==by 0x4DB1E70: 
icu_54::TransliteratorSpec::TransliteratorSpec(icu_54::UnicodeString 
const&) (in /usr/lib64/libicui18n.so.54.1)
==11141==by 0x4DB28DF: 
icu_54::TransliteratorRegistry::find(icu_54::UnicodeString&, 
icu_54::UnicodeString&, icu_54::UnicodeString&) (in 
/usr/lib64/libicui18n.so.54.1)
==11141==by 0x4DB2B76: 
icu_54::TransliteratorRegistry::find(icu_54::UnicodeString const&) (in 
/usr/lib64/libicui18n.so.54.1)
==11141==by 0x4DB2BFA: 
icu_54::TransliteratorRegistry::get(icu_54::UnicodeString const&, 
icu_54::TransliteratorAlias*&, UErrorCode&) (in 
/usr/lib64/libicui18n.so.54.1)
==11141==by 0x4D9D58D: 
icu_54::Transliterator::createBasicInstance(icu_54::UnicodeString 
const&, icu_54::UnicodeString const*) (in /usr/lib64/libicui18n.so.54.1)
==11141==by 0x4DA3DEC: 
icu_54::TransliteratorIDParser::SingleID::createInstance() (in 
/usr/lib64/libicui18n.so.54.1)
==11141==by 0x4DA432B: 
icu_54::TransliteratorIDParser::instantiateList(icu_54::UVector&, 
UErrorCode&) (in /usr/lib64/libicui18n.so.54.1)
==11141==by 0x4D9E9DA: 
icu_54::Transliterator::createInstance(icu_54::UnicodeString const&, 
UTransDirection, UParseError&, UErrorCode&) (in 
/usr/lib64/libicui18n.so.54.1)
==11141==by 0x4D9F6E9: utrans_openU_54 (in 
/usr/lib64/libicui18n.so.54.1)

==11141==by 0x10B9F5: get_translit (test-fts-icu.c:90)
==11141==by 0x10BBFC: test_fts_icu_translate (test-fts-icu.c:106)
==11141==
Failed to run: ./test-fts-icu

Any ideas?

Thank you.

Ciao,
Gerhard

Re: v2.2.21 released

[Gerhard Wiesinger]

On 13.12.2015 20:35, Timo Sirainen wrote:

On 13 Dec 2015, at 15:40, Gerhard Wiesinger <li...@wiesinger.com> wrote:

On 11.12.2015 18:10, Timo Sirainen wrote:

http://dovecot.org/releases/2.2/dovecot-2.2.21.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.21.tar.gz.sig


Hello Timo,

tried to compile it, but tests fail on Fedora 23 with latest gcc 
(gcc-5.3.1-2.fc23.x86_64):

The compiling works, the make check part just fails. You could also set 
NOVALGRIND=1 environment before building and it would succeed.


==11141== Conditional jump or move depends on uninitialised value(s)
==11141==at 0x512C753: 
icu_54::LocaleUtility::initLocaleFromName(icu_54::UnicodeString const&, 
icu_54::Locale&) (in /usr/lib64/libicuuc.so.54.1)
==11141==by 0x4DB1E70: 
icu_54::TransliteratorSpec::TransliteratorSpec(icu_54::UnicodeString const&) 
(in /usr/lib64/libicui18n.so.54.1)

This looks a bit worrysome though. But if it's a bug then I'm pretty sure it's 
on the libicu side. I'm not sure what exactly is wrong in there. You could also 
see if setting LC_ALL=C environment happens to work.

What's the libicu version? 54.1?




libicu-devel-54.1-5.fc23.x86_64
libicu-54.1-5.fc23.x86_64

gcc has been recentyl updated to 5.3.1 (from 5.1.1 as far as I remember).

So all the libs are compiled with the old version. Maybe there is some 
incompatibility.


Will try that.

Ciao,
Gerhard

Re: v2.2.20 released

[Gerhard Wiesinger]

On 07.12.2015 20:13, Timo Sirainen wrote:

http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.20.tar.gz.sig

This could be (one of) the last v2.2.x release. We're starting v2.3 development 
soon.




Great!

What's on the featurelist of v2.3?

Ciao,
Gerhard

Re: v2.2.20 release candidate released

[Gerhard Wiesinger]

On 06.12.2015 13:10, Timo Sirainen wrote:

On 05 Dec 2015, at 11:32, Gerhard Wiesinger <li...@wiesinger.com> wrote:

Is it possible to configure the secure session caching mechanism?
e.g. like in nginx: https://bjornjohansen.no/optimizing-https-nginx

I remember hearing about various security vulnerabilities in that earlier.. I 
guess they're fixed now then, unless people find more ways to exploit it. 
Anyway I'm not sure how useful it would actually even be for most IMAP/POP3 
servers, because most clients don't connect all that often. Or I guess it might 
help some clients that create multiple connections immediately.

Then again, we are planning on adding some HTTP(S)-based services to Dovecot 
and there it would likely be more useful. So I guess it gets implemented at 
some point.




Session tickets are broken by DESIGN as they violate PFS (Perfect 
Forward Secrecy). If you can steal one AES key (all session tickets are 
encrypted for server lifetime with only one key) you can decrypt ALL 
sessions ever made with session tickets for the future. This violates 
PFS (Perfect Forward Secrecy) as only server side "parameters" are 
relevant from now on.


Yes, session caching should reduce server load on multiple connections.

See e.g. https://community.qualys.com/thread/15768

Therefore it would be great if you could implement the secure session 
caching mechanism.


As Gedalya mentioned OCSP would be great, too.

Ciao,
Gerhard

Re: v2.2.20 release candidate released

[Gerhard Wiesinger]

On 03.12.2015 14:51, Timo Sirainen wrote:

http://dovecot.org/releases/2.2/rc/dovecot-2.2.20.rc1.tar.gz
http://dovecot.org/releases/2.2/rc/dovecot-2.2.20.rc1.tar.gz.sig

v2.2.20 probably will be released tomorrow or maybe during weekend.

  + ssl_options: Added support for no_ticket



Hello TImo,

great to see that inseucre session tickets (violating PFS) can be disabled.

Is it possible to configure the secure session caching mechanism?
e.g. like in nginx: https://bjornjohansen.no/optimizing-https-nginx

Thnx.

Ciao,
Gerhard

Re: * Re: procmail as a content_filter with dovecot

[Gerhard Wiesinger]

On 10.11.2015 23:38, Vicki Brown wrote:

Thank you. This may be helpful.


On Nov 10, 2015, at 13:01, Benny Pedersen  wrote:


https://www.google.dk/search?q=procmailrc+to+sieve




Find my enhanced version + wrapper script at with custom configuration at:
http://www.wiesinger.com/opensource/procmail2sieve/

Ciao,
Gerhard

Re: Dovecot sieve pigeonhole permission

[Gerhard Wiesinger]

On 05.08.2015 13:06, Steffen Kaiser wrote:

On Tue, 4 Aug 2015, Gerhard Wiesinger wrote:



I'm running dovecot in a classical vmail.vmail setup with pigeonhole 
and LMTP. Permission worked well in the initial setup but currently 
(maybe after Fedora 22 update) I'm having the following permission 
issue:


lmtp(root): Error: 7fPZFOL9wFXePQAABcdabc: sieve: binary open: failed 
to open: open(/etc/dovecot/sieve_after.svbin) failed: Permission 
denied (euid=(vmail) egid=(vmail) missing +r perm: 
/etc/dovecot/sieve_after.svbin, we're not in group 0(root), dir owned 
by 0:0 mode=0755)


Did you honored the error log and added the read permission for the 
vmail user, which most likely means:


chmod a+r /etc/dovecot/sieve_after.svbin



Yes, I read it but I didn't like to give read permissions for all. Isn't 
there a better designed solution available?

Nevertheless it works by setting the read permissions for all ...

lmtp(root): Error: 7fPZFOL9wFXePQAABcdabc: sieve: binary save: failed 
to create temporary file: 
open(/etc/dovecot/sieve_after.svbin.myserver.mydomain.15838.) failed: 
Permission denied (euid=(vmail) egid=(vmail) missing +w perm: 
/etc/dovecot, dir owned by 0:0 mode=0755)
lmtp(root): Error: 7fPZFOL9wFXePQAABcdcbc: sieve: The LDA Sieve 
plugin does not have permission to save global Sieve script binaries; 
global Sieve scripts like `/etc/dovecot/sieve_after.sieve' need to be 
pre-compiled using the sievec tool


Did you compiled the script manually as described in the error log?



Yes, I did, but didn't work because of the missing read permissions for all.

Ciao,
Gerhard

--
http://www.wiesinger.com/

Dovecot sieve pigeonhole permission

[Gerhard Wiesinger]

Hello,

I'm running dovecot in a classical vmail.vmail setup with pigeonhole and 
LMTP. Permission worked well in the initial setup but currently (maybe 
after Fedora 22 update) I'm having the following permission issue:


lmtp(root): Error: 7fPZFOL9wFXePQAABcdabc: sieve: binary open: failed to 
open: open(/etc/dovecot/sieve_after.svbin) failed: Permission denied 
(euid=(vmail) egid=(vmail) missing +r perm: 
/etc/dovecot/sieve_after.svbin, we're not in group 0(root), dir owned by 
0:0 mode=0755)
lmtp(root): Error: 7fPZFOL9wFXePQAABcdabc: sieve: binary save: failed to 
create temporary file: 
open(/etc/dovecot/sieve_after.svbin.myserver.mydomain.15838.) failed: 
Permission denied (euid=(vmail) egid=(vmail) missing +w perm: 
/etc/dovecot, dir owned by 0:0 mode=0755)
lmtp(root): Error: 7fPZFOL9wFXePQAABcdcbc: sieve: The LDA Sieve plugin 
does not have permission to save global Sieve script binaries; global 
Sieve scripts like `/etc/dovecot/sieve_after.sieve' need to be 
pre-compiled using the sievec tool


rpm -V dovecot dovecot-pigeonhole
doesn't report any permission issues

Versions:
dovecot-2.2.18-2.fc22.x86_64
dovecot-pigeonhole-2.2.18-2.fc22.x86_64

Relevant config parts:
mail_gid = vmail
mail_uid = vmail

plugin {
  sieve = ~/.dovecot.sieve
  sieve_after = /etc/dovecot/sieve_after.sieve
  sieve_dir = ~/sieve
}

ls -lad /etc/dovecot/
drwxr-xr-x. 3 root root 4096 Jul 30 18:13 /etc/dovecot/
ls -la /etc/dovecot/*sieve*
-rwxr-x--- 1 vmail vmail 288 Aug  8  2014 /etc/dovecot/sieve_after.sieve
-rw-r- 1 root  root  355 Jul 30 18:13 /etc/dovecot/sieve_after.svbin

What's are the recommended permissions for the files/directories (also 
for root service startup of dovecot)?

Did something change in permissions management?

Thanx.

Ciao,
Gerhard

--
http://www.wiesinger.com/

Re: Dovecot and remote SASL Client via TLS

[Gerhard Wiesinger]

Hello,

Anyone interested, I solved it the following way:
imap server: dovecot = /bin/saslcheckpassword = local unix domain 
socket for saslauthd = socat client

 ^
 = Remote TLS connection
 v
auth server: socat server = saslauthd = /etc/passwd,/etc/shadow

saslcheckpassword is based on checkpassword.sh and enhanced for SASL, 
modified version attached:

https://bitbucket.org/vizovitin/dovecot-conf-examples/src/tip/checkpassword-shell/checkpassword.sh

Detailed configs below.

imap server:
touch /var/log/dovecot-saslcheckpassword.log
chown dovecot.dovecot /var/log/dovecot-saslcheckpassword.log
chmod 750 /var/log/dovecot-saslcheckpassword.log

Advantage is single authentication entity.

Works well for me for some time now.

If you have some questions feel free to ask.

Ciao,
Gerhard


IMAP server, SASL client:
cat /etc/systemd/system/multi-user.target.wants/saslclient.service
[Unit]
Description=SASL remote client for authentication, provides local unix 
domain socket

After=network.target

[Service]
# Must be running under permissions for the dovecot user!
ExecStart=/usr/bin/socat -4 -ly 
UNIX-LISTEN:/var/run/saslauthd/mux,fork,user=dovecot,group=dovecot 
'OPENSSL:myserver:1234,verify=1,method=TLSv1,cipher=DHE-RSA-AES256-SHA:!aNULL:!eNULL:!EXP:!LOW:!MD5,cafile=/etc/socat/mycert.crt'


[Install]
WantedBy=multi-user.target

Auth server:
cat /etc/systemd/system/multi-user.target.wants/saslserver.service
[Unit]
Description=SASL remote server for authentication
After=network.target

[Service]
ExecStart=/usr/bin/socat -4 -ly 
'OPENSSL-LISTEN:,reuseaddr,fork,verify=0,method=TLSv1,cipher=DHE-RSA-AES256-SHA:!aNULL:!eNULL:!EXP:!LOW:!MD5,cert=/etc/socat/mycert.pem,cafile=/etc/socat/mycert.crt' 
/var/run/saslauthd/mux


[Install]
WantedBy=multi-user.target

Relevant dovecot config:
userdb {
  args = username_format=%n /etc/dovecot/users
  driver = passwd-file
}

passdb {
  args = /bin/saslcheckpassword
  driver = checkpassword
}


--
http://www.wiesinger.com/

On 16.07.2014 15:50, Gerhard Wiesinger wrote:


Any comments?

Thank you.

Ciao,
Gerhard

http://www.wiesinger.com/


#!/bin/bash

# Example Dovecot checkpassword script that may be used as both passdb or 
userdb.
#
# Originally written by Nikolay Vizovitin, 2013.
# Enhanced by Gerhard Wiesinger, 2014.

# Assumes authentication DB is in /etc/dovecot/users, each line has 
'user:password' format.
# Place this script into /etc/dovecot/checkpassword.sh file and make executable.
# Implementation guidelines at 
http://wiki2.dovecot.org/AuthDatabase/CheckPassword

# The first and only argument is path to checkpassword-reply binary.
# It should be executed at the end if authentication succeeds.
CHECKPASSWORD_REPLY_BINARY=$1

# Messages to stderr will end up in mail log (prefixed with dovecot: auth: 
Error:)
#LOG=/dev/stderr
# Will be e.g. /tmp/systemd-dovecot.service-XfZAUy5/tmp/saslcheckpassword.log
#LOG=/tmp/saslcheckpassword.log
# touch /var/log/dovecot-saslcheckpassword.log
# chown dovecot.dovecot /var/log/dovecot-saslcheckpassword.log
# chmod 750 /var/log/dovecot-saslcheckpassword.log
LOG=/var/log/dovecot-saslcheckpassword.log

#export default_userdb_uid=popuser
#export default_userdb_gid=popuser
export default_userdb_uid=vmail
export default_userdb_gid=vmail
export SASL=1

# User and password will be supplied on file descriptor 3.
INPUT_FD=3

# Error return codes.
ERR_PERMFAIL=1
ERR_NOUSER=3
ERR_TEMPFAIL=111

# Make testing this script easy. To check it just run:
#   printf '%s\0%s\0' user password | ./checkpassword.sh test; echo $?
if [ $CHECKPASSWORD_REPLY_BINARY = test ]; then
CHECKPASSWORD_REPLY_BINARY=/bin/true
INPUT_FD=0
fi

# Credentials lookup function. Given a user name it should output 
'user:password' if such
# account exists or nothing if it does not. Return non-zero code in case of 
error.
credentials_lookup()
{
local db=$1
local user=$2

awk -F ':' -v USER=$user '($1 == USER) {print}' $db 2$LOG
}

# Credentials verification function. Given a user name and password it should 
output non-empty
# string (this implementation outputs 'user:password') in case supplied 
credentials are valid
# or nothing if they are not. Return non-zero code in case of error.
credentials_verify()
{
local db=$1
local user=$2
local pass=$3

awk -F

Dovecot, Thunderbird and messages in wrong folder

[Gerhard Wiesinger]

Hello,

Sometimes it happens that messages (e.g. one or two) appear in wrong 
folders in Thunderbird (latest version, also past versions, different 
computers, also Earlybird). When I repair the folder 
(folder/Settings/Repair Folder) in Thunderbird, the folder is correct then.


It happens on my new server with Fedora 20, Dovecot 2.2.13 and Maildir 
but it also happened on my old server with Fedora 1, Dovecot 2.2.13 and 
mbox.


Has anyone the same issue?
Any guess whether it might be a thunderbird or dovecot issue?
Anyone has the same issues with thunderbird and a different IMAP server 
(e.g. cyrus)?


Thank you.

Ciao,
Gerhard

Config (only relevant parts here):
# 2.2.13: /etc/dovecot/dovecot.conf
# OS: Linux 3.15.8-200.fc20.x86_64 x86_64 Fedora release 20 (Heisenbug)
auth_mechanisms = plain login
lda_mailbox_autocreate = yes
listen = *
mail_gid = vmail
mail_home = /home/vmail/%n
mail_location = maildir:~/Maildir
mail_max_userip_connections = 20
mail_plugins =  stats mailbox_alias zlib
mail_uid = vmail
protocols = imap lmtp sieve
service imap-login {
  inet_listener imap {
port = 0
  }
  process_min_avail = 2
  service_count = 0
}
service imap {
  client_limit = 20
  executable = imap postlogin
  process_limit = 20
}
service lmtp {
  inet_listener lmtp {
port = 24
  }
  process_min_avail = 2
}
service managesieve-login {
  process_min_avail = 1
}
service postlogin {
  executable = script-login -d rawlog
}
service stats {
  fifo_listener stats-mail {
mode = 0600
user = vmail
  }
}
ssl_cert = /etc/pki/dovecot/imap.crt
ssl_key = /etc/pki/dovecot/imap.key
submission_host = 127.0.0.1
userdb {
  args = username_format=%n /etc/dovecot/users
  driver = passwd-file
}
protocol imap {
  imap_client_workarounds = tb-extra-mailbox-sep
  mail_plugins =  stats mailbox_alias zlib imap_stats imap_zlib
}
protocol lmtp {
  mail_plugins =  stats mailbox_alias zlib sieve
}

Re: Dovecot and remote SASL Client via TLS

[Gerhard Wiesinger]

On 29.06.2014 07:53, Gerhard Wiesinger wrote:

Hello,

Is it possible to configure Dovecot as SASL client for central 
authentication (also remotely via TCP/TLS)?


Following use case:
IMAP server (host 1) = Windows Domain Controller and /etc/shadow 
authenticator via pam (host2)


Should work as:
IMAP server (host 1) = SASL Client via TLS = Network = SASL 
Server via TLS = Local SASL via pam = Windows Domain Controller 
and /etc/shadow authenticator via pam (host2)




Any comments?

Thank you.

Ciao,
Gerhard

http://www.wiesinger.com/

Re: Mailboxes are in Maildir format. Any good backup tips? Had success with version control?

[Gerhard Wiesinger]

On 01.07.2014 00:28, deoren wrote:
I'm still pretty new to running a mail server, but one thing I've come 
to appreciate over the years is a good backup strategy. Since I have 
always run my own servers for practice and for personal use I don't 
have access to Enterprise backup solutions. Because of that I usually 
just fall back to scripts and tarballs and offload the content on a 
regular basis.


Right now I'm using LVM snapshots + tarballs for daily backups, but 
I'd like to get better coverage for incremental changes that occur 
throughout the day. The size of existing content is low, but (small) 
changes are frequent.


I went with Maildir format because based on my reading it is referred 
to as time tested and corruption resistant. Because individual emails 
are stored as separate files this also leads me to believe that a 
version control system (Git, SVN) would allow for easy point in time 
restores.


I'm also going to research the GNU tar utility's support for 
incremental archives as that sounds promising.


Hello Deoren,

I can recommend dirvish (http://www.dirvish.org/).

Supports incremental backups with aging strategy and hardlinks and very 
efficient storage. Works for years for me. In the background rsync is 
used for syncing the backups but with a high level interface.


Ciao,
Gerhard

Re: Procmail to Sieve translation

[Gerhard Wiesinger]

On 28.06.2014 14:33, Daniel Parthey wrote:

Hi Gerhard,

Am 28.06.2014 07:40, schrieb Gerhard Wiesinger:

I'm trying to move from procmail to dovecot sieve.

How does forwarding to another domain work at the deliver process?

:copy seems not to be supported, right?


http://wiki2.dovecot.org/Pigeonhole/Sieve/Examples#Mail_filtering_by_various_headers 



if header :contains subject [order, buy] {
  redirect recipi...@example.org;
}

Dovecot/Pigeonhole simply uses the sendmail executable or SMTP to 
reinject the redirected/forwarded mail:


See Dovecot Options
* sendmail_path (to send mail via pipe)
* submission_host (to send mail via smtp)


Thank you.

As I'm new to sieve can someone verify the example translations?


* ^From:.*myem...@mydomain.com.*
| formail -IX-Priority: 2 (high) -IX-mydomain-com-seen: yes | 
$SENDMAIL -oi \

  myem...@mydomain2.com  \
  myem...@mydomain3.com

# http://www.emaildiscussions.com/showthread.php?t=57138
# http://tools.ietf.org/html/rfc5293
if header :contains [from] [myem...@mydomain.com] {
  addheader X-Priority 2 (high);
  addheader X-mydomain-com-seen yes;
  redirect :copy myem...@mydomain2.com;
  redirect myem...@mydomain3.com;
}

:0c
* ^From:.*myem...@mydomain.com.*
! +1123456...@mysmsprovider.com

if header :contains [from] [myem...@mydomain.com] {
  redirect +1123456...@mysmsprovider.com;
}

:0c
* ^(To|Cc|Bcc):.*myem...@mydomain.com.*
!   myem...@mydomain2.com myem...@mydomain3.com

if envelope :detail :contains [to, cc, bcc] myem...@mydomain.com {
  redirect :copy myem...@mydomain2.com;
  redirect myem...@mydomain3.com;
}


Thank you.

Ciao,
Gerhard

-- http://www.wiesinger.com/

Dovecot and remote SASL Client via TLS

[Gerhard Wiesinger]

Hello,

Is it possible to configure Dovecot as SASL client for central 
authentication (also remotely via TCP/TLS)?


Following use case:
IMAP server (host 1) = Windows Domain Controller and /etc/shadow 
authenticator via pam (host2)


Should work as:
IMAP server (host 1) = SASL Client via TLS = Network = SASL Server 
via TLS = Local SASL via pam = Windows Domain Controller and 
/etc/shadow authenticator via pam (host2)


Thank you.

Ciao,
Gerhard

-- http://www.wiesinger.com/

Procmail to Sieve translation

[Gerhard Wiesinger]

Hello,

I'm trying to move from procmail to dovecot sieve.

I found the translation script at 
http://www.dovecot.org/tools/procmail2sieve.pl

It works well except the following use cases:

* ^From:.*myem...@mydomain.com.*
| formail -IX-Priority: 2 (high) -IX-mydomain-com-seen: yes | 
$SENDMAIL -oi \

  myem...@mydomain2.com  \
  myem...@mydomain3.com

:0c
* ^From:.*myem...@mydomain.com.*
! +1123456...@mysmsprovider.com

:0c
* ^(To|Cc|Bcc):.*myem...@mydomain.com.*
!   myem...@mydomain2.com myem...@mydomain3.com

Is there a possibility to support these use cases (can be done manually)?

How does forwarding to another domain work at the deliver process?

:copy seems not to be supported, right?

Thank you.

Ciao,
Gerhard

[Dovecot] Dovecot quoting problem?

[Gerhard Wiesinger]

Hello Timo,

I think the following commit makes problems:
http://hg.dovecot.org/dovecot-2.2/rev/68a8b650578e

# Doesn't work
A01 LIST  ~/Mail/Gesendet
# OK with quoted mailbox
A02 LIST  ~/Mail/Gesendet

Details:
imap
* PREAUTH [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID 
ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS 
THREAD=ORDEREDSUBJECT MULTIAPPEND URL-PARTIAL CATENATE UNSELECT CHILDREN 
NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH 
ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS SPECIAL-USE BINARY 
MOVE] Logged in as user

A01 LIST  ~/Mail/Gesendet
A01 BAD Error in IMAP command LIST: literal8 not allowed here
A02 LIST  ~/Mail/Gesendet
* LIST (\NoInferiors \UnMarked) / ~/Mail/Gesendet
A02 OK List completed.
A03 STATUS ~/Mail/Gesendet (MESSAGES UNSEEN RECENT)
A03 BAD Error in IMAP command STATUS: literal8 not allowed here
A04 STATUS ~/Mail/Gesendet (MESSAGES UNSEEN RECENT)
* STATUS ~/Mail/Gesendet (MESSAGES 0 RECENT 0 UNSEEN 0)
A04 OK Status completed.

Is this a bug of dovecot or a bug of the IMAP client (roundcube mail)?

Thank you

Ciao,
Gerhard

[Dovecot] deliver doesn't update cache index with mbox

[Gerhard Wiesinger]

Hello Timo,

I'm having a problem with mbox that opening folder is slow when new 
mails are delivered to a folder. I'm delivering through the deliver 
program. Deliver updates index files but IHMO not completely correct. 
Therefore I compared index files before and after:

1.) Just delivered
2.) After accessing through imap via Thunderbird

diff looks like (stripped down to the relevant things):
INDEX:
-first recent uid . = 25847
+first recent uid . = 25848
-log file tail offset . = 16468
-log file head offset . = 16468
+log file tail offset . = 16828
+log file head offset . = 16828
- - sync_mtime . = 2012-08-30 19:38:05
+ - sync_mtime . = 2012-08-30 20:09:23
- - dirty_flag . = 1
+ - dirty_flag . = 0
- - highest_modseq = 11162
+ - highest_modseq = 11163
- - log_offset ... = 16468
+ - log_offset ... = 16828
CACHE:
-used_file_size ... = 6385696
+used_file_size ... = 6392132
 RECORD: seq=25663, uid=25835, flags=0x00
- - ext 0 keywords  :()
- - ext 1 modseq:  11156 (942b)
+ - ext 0 keywords  :(0100)
+ - ext 1 modseq:  11163 (9b2b)
  - ext 2 mbox  :   42923286 (16f58e02)
- - ext 3 cache :  0 ()
+ - ext 3 cache :6385696 (20706100)
  - ext 4 header-md5:()
+ - cache offset=6385696 size=488, prev_offset = 0
+- hdr.BCC:
+- hdr.CC:
+- hdr.CONTENT-TYPE: 18: Content-Type: text/plain; charset=us-ascii
+- hdr.DATE: 13: Date: Thu, 30 Aug 2012 19:37:24 +0200
some other hdr.x lines removed
+- size.virtual: 1081 (3904)

Same patterns from record: 25664-25675

What does dirty_flag=1 mean?
Why are the cache headers missing and not written by deliver?

Any ideas?

Config is below.

Thank you.

Ciao,
Gerhard

# 2.1.9: /etc/dovecot/dovecot.conf
# OS: Linux
listen = *
mail_full_filesystem_access = yes
mail_location = mbox:~:INBOX=/var/mail/%u
mbox_lazy_writes = no
mbox_write_locks = fcntl
passdb {
  driver = pam
}
postmaster_address = postmaster@domain
protocols = imap
service auth {
  unix_listener auth-userdb {
group = users
mode = 0660
  }
}
service imap-login {
  inet_listener imap {
port = 0
  }
}
service imap {
  executable = imap postlogin
}
service postlogin {
  executable = script-login -d rawlog
}
ssl_cert = /etc/pki/dovecot/dovecot-extern.pem
ssl_key = /etc/pki/dovecot/private/dovecot-extern.pem
userdb {
  driver = passwd
}
protocol imap {
  imap_client_workarounds = tb-extra-mailbox-sep
}
protocol lda {
  lda_mailbox_autocreate = yes
  log_timestamp = %Y.%m.%d %H:%M:%S%t
  mail_debug = yes
  mail_location = mbox:~/Mail:INBOX=/var/mail/%u
}

Re: [Dovecot] v2.1.5 released

[Gerhard Wiesinger]

Hello Timo,

Yes, fixed it. Thnx.

I also had a coredump with 2.1.3 + 
http://hg.dovecot.org/dovecot-2.1/rev/86e6dc46a80e

A02 LIST  *
imap(username: Panic: file mail-storage.c: line 628 (mailbox_alloc): 
assertion failed: (uni_utf8_str_is_valid(vname))


Also fixed with 2.1.5 + http://hg.dovecot.org/dovecot-2.1/rev/249c1c89d9d3

Ciao,
Gerhard

--
http://www.wiesinger.com/

On 25.04.2012 23:16, Timo Sirainen wrote:

On 24.4.2012, at 11.59, Gerhard Wiesinger wrote:


Hello Timo,

Dovecot 2.1.5 seems to be broken. After upgrade from
2.1.3 + patch http://hg.dovecot.org/dovecot-2.1/rev/86e6dc46a80e
I only see Inbox and Trash folder.

Reverting =  OK.

Same config as before and disucssed per private E-mail and on the list. 
Guessing this comes again from:
mail_full_filesystem_access=yes

I guess the problem was this: http://hg.dovecot.org/dovecot-2.1/rev/249c1c89d9d3

Re: [Dovecot] v2.1.5 released

[Gerhard Wiesinger]

Hello Timo,

Dovecot 2.1.5 seems to be broken. After upgrade from
2.1.3 + patch http://hg.dovecot.org/dovecot-2.1/rev/86e6dc46a80e
I only see Inbox and Trash folder.

Reverting = OK.

Same config as before and disucssed per private E-mail and on the list. 
Guessing this comes again from:

mail_full_filesystem_access=yes

Ciao,
Gerhard

--
http://www.wiesinger.com/


On Mon, 23 Apr 2012, Timo Sirainen wrote:


http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz
http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz.sig

A few announcements first:

I'm now going to start being more strict about not answering Dovecot questions 
sent to me privately (especially support requests, but also bug reports, 
feature requests, etc). Often those questions could be answered by other people 
in the mailing list as well, so they just waste my time. Even if you're sure 
that I'm the only person who can possibly answer it, it may be something that 
others are interested of as well and replying privately denies them the 
possibility of reading about it. If you really do not want to send something 
publicly, you still have an option for private communication: just buy one of 
the Dovecot support packages.

This is also the first Dovecot release that has run through automated release 
testing. I've been planning on doing that for last 5 years at least, and 
finally it's done. The testing includes running a lot of tests to verify that 
the IMAP server gives proper responses, stress testing doesn't break it, memory 
isn't leaked and several other things. The tests are run for many different 
kinds of configurations.

Some bugs show up only for some specific combination of settings, but 
unfortunately because there's such a large number of them it's impossible to 
test every combination. So here's another advantage that Dovecot support 
customers have: they can have their specific configuration included in the 
automated tests. This release already fixes one bug I found only after testing 
a customer's config.

Oh, and looks like I got accepted as a speaker to LinuxTag 2012. The plan is to 
talk about some new things in Dovecot and dsync replication (looks like I have 
to hurry up with the dsync rewrite).

And finally, the most important changes since v2.1.4:

* IMAP: When neither the session nor the mailbox has modseq tracking
  enabled, return the mailbox as having NOMODSEQ in SELECT/EXAMINE
  reply. Old versions in this situation always simply returned
  HIGHESTMODSEQ as 1, which could have broken some clients.

+ dict file: Added optional fcntl/flock locking (default is dotlock)
+ fts-solr: doveadm fts rescan now resets indexes, which allows
  reindexing mails. (This isn't a full rescan implementation like
  fts-lucene has.)
+ doveadm expunge: Added -d parameter to delete mailbox if it's
  empty after expunging.
- IMAP: Several fixes related to mailbox listing in some configs
- director: A lot of fixes and performance improvements
- v2.1.4 didn't work without a mail home directory set
- mbox: Deleting a mailbox didn't delete its index files.
- pop3c: TOP command was sent incorrectly
- trash plugin didn't work properly
- LMTP: Don't add a duplicate Return-Path: header when proxying.
- listescape: Don't unescape namespace prefixes.

Re: [Dovecot] v2.1.4 released - broken

[Gerhard Wiesinger]

On 10.04.2012 03:28, Marc Perkel wrote:


I'm seeing this immediately after upgrading from 2.1.3

Apr 09 18:22:43 imap(ch...@powerpage.org): Error: user 
ch...@powerpage.org: Initialization failed: Initializing mail storage 
from mail_location setting failed: Home directory not set for user. 
Can't expand ~/ for mail root dir in: 
/vhome/powerpage.org/home/chris:INDEX=/email/imap-cache/powerpage.org-chris


mail_location = maildir:/vhome/%d/home/%n:INDEX=/email/imap-cache/%d-%n



I'm guessing this occurs from the following bugfix:
http://hg.dovecot.org/dovecot-2.1/rev/86e6dc46a80e

Reverting this patch helps?

What is your config (doveconf -n)?

Ciao,
Gerhard

Re: [Dovecot] Dovecot upgrade from 1.2.x to 2.0.x: roundcube/squirrelmail sent folder doesn't work any more

[Gerhard Wiesinger]

On Wed, 4 Apr 2012, Timo Sirainen wrote:


On 29.3.2012, at 8.25, Gerhard Wiesinger wrote:


2.0.x: with Prefix ~/Mail
A0003 LIST  ~/Mail/sent
A0003 OK List completed.:




mail_full_filesystem_access = yes
mail_location = mbox:~:INBOX=/var/mail/%u


Yes, the problem happens only with mail_full_filesystem_access=yes. It already 
works in v2.1, so I don't think I'll bother looking into why it's not working 
in v2.0.


Hello Timo,

As discussed per private mail you finally fixed it: 
http://hg.dovecot.org/dovecot-2.1/rev/86e6dc46a80e

Thnx for your support.

Ciao,
Gerhard

--
http://www.wiesinger.com/

Re: [Dovecot] Dovecot upgrade from 1.2.x to 2.0.x: roundcube/squirrelmail sent folder doesn't work any more

[Gerhard Wiesinger]

On Thu, 29 Mar 2012, Timo Sirainen wrote:


On 27.3.2012, at 20.28, Gerhard Wiesinger wrote:


After upgrading from 1.2.x to 2.0.x I'm having problems using sent folder in 
Webmail applications like roundcube mail and squirrelmail.


doveconf -n output?


2.0.x: with Prefix ~/Mail
A0003 LIST  ~/Mail/sent
A0003 OK List completed.:


Works with my v2.0.19 config:

x list  ~/Mail/sent
* LIST (\NoInferiors \UnMarked) / ~/Mail/sent
x OK List completed.


# 2.0.19: /etc/dovecot/dovecot.conf
# OS: cutted for security reasons
listen = *
mail_full_filesystem_access = yes
mail_location = mbox:~:INBOX=/var/mail/%u
mbox_lazy_writes = no
mbox_write_locks = fcntl
passdb {
  driver = pam
}
protocols = imap
service auth {
  unix_listener /var/run/dovecot-auth-master {
group = users
mode = 0660
  }
  user = root
}
service imap {
  executable = imap postlogin
}
service postlogin {
  executable = script-login -d rawlog
}
ssl_cert = /etc/pki/dovecot/dovecot-extern.pem
ssl_key = /etc/pki/dovecot/private/dovecot-extern.pem
userdb {
  driver = passwd
}
protocol imap {
  imap_client_workarounds = tb-extra-mailbox-sep
}
protocol lda {
  auth_socket_path = /var/run/dovecot-auth-master
  info_log_path = /path/to/log/deliver.log
  log_path = /path/to/log/deliver.log
  log_timestamp = %Y.%m.%d %H:%M:%S%t
  mail_debug = yes
  mail_location = mbox:~/Mail:INBOX=/var/mail/%u
  postmaster_address = m...@mydomain.com
}

Thnx.

Ciao,
Gerhard

--
http://www.wiesinger.com/

[Dovecot] Dovecot upgrade from 1.2.x to 2.0.x: roundcube/squirrelmail sent folder doesn't work any more

[Gerhard Wiesinger]

Hello,

After upgrading from 1.2.x to 2.0.x I'm having problems using sent 
folder in Webmail applications like roundcube mail and squirrelmail.


Relevant config dovecot.conf:
mail_location = mbox:~:INBOX=/var/mail/%u

Different LIST behaviour from rawlog:
1.2.x: with Prefix ~/Mail
A002 LIST  ~/Mail/sent
* LIST (\NoInferiors \UnMarked) / ~/Mail/sent
A002 OK List completed.

2.0.x: with Prefix ~/Mail
A0003 LIST  ~/Mail/sent
A0003 OK List completed.:

Configured prefix for private spaces in roundcube mail is ~/Mail . 
Roundcube Webmail application checks for existence of the folder but 
dovecot doesn't return anything in 2.x.latest.


Is this by design?
Any ideas to fix it by configuration?
(I tried prefix Mail/ in roundcube mail without success)

Thunderbird works well.

Thnx.

Ciao,
Gerhard

[Dovecot] Dovecot upgrade from 1.2.x to 2.0.x: roundcube/squirrelmail sent folder doesn't work any more

[Gerhard Wiesinger]

Hello,

After upgrading from 1.2.x to 2.0.x I'm having problems using sent 
folder in Webmail applications like roundcube mail and squirrelmail.


Relevant config dovecot.conf:
mail_location = mbox:~:INBOX=/var/mail/%u

Different LIST behaviour from rawlog:
1.2.x: with Prefix ~/Mail
A002 LIST  ~/Mail/sent
* LIST (\NoInferiors \UnMarked) / ~/Mail/sent
A002 OK List completed.

2.0.x: with Prefix ~/Mail
A0003 LIST  ~/Mail/sent
A0003 OK List completed.:

Configured prefix for private spaces in roundcube mail is ~/Mail . 
Roundcube Webmail application checks for existence of the folder but 
dovecot doesn't return anything in 2.x.latest.


Is this by design?
Any ideas to fix it by configuration?
(I tried prefix Mail/ in roundcube mail without success)

Thunderbird works well.

Thnx.

Ciao,
Gerhard

Re: [Dovecot] Update problem from 1.2 = 2.0.19 and recommended imap storage

[Gerhard Wiesinger]

On Fri, 16 Mar 2012, Timo Sirainen wrote:


On 16.3.2012, at 8.02, Gerhard Wiesinger wrote:

Calling imap still fails as non root:
imap
/usr/bin/ld: cannot open output file /usr/local/bin/.libs/2612-lt-imap: 
Permission denied
collect2: ld returned 1 exit statusn


Huh? That looks like imap is running ld to link something. It shouldn't be 
doing that.


After starting it once as root the following files are created and it 
works also as non root:

ls -l /usr/local/bin/.libs/
total 1160
-rwxr-xr-x  1 root root 235848 Aug 25  2010 lt-doveconf
-rwxr-xr-x  1 root root 938454 Mar 16 07:03 lt-imap

Before only one of these files was generated (I think lt-doveconf).

Strange. Any ideas?

Ciao,
Gerhard

--
http://www.wiesinger.com/

[Dovecot] Update problem from 1.2 = 2.0.19 and recommended imap storage

[Gerhard Wiesinger]

Hello,

After fixing configuration and other issues I'm still having one problem 
with imap executable and pine:

less .pinerc
# Changed config:
#rsh-command=/usr/sbin/dovecot --exec-mail imap
rsh-command=/usr/local/bin/imap

Calling imap still fails as non root:
imap
/usr/bin/ld: cannot open output file /usr/local/bin/.libs/2612-lt-imap: 
Permission denied

collect2: ld returned 1 exit statusn

Any ideas to fix it?

BTW: What is the recommended dovecot storage for dovecot 2.x 
(upgradeable from mbox)?


Thnx.

Ciao,
Gerhard

[Dovecot] Problem with local pine after upgrade to 1.2.5

[Gerhard Wiesinger]

Hello,

I upgraded from dovecot 1.1.17 to 1.2.5. Works well so far with e.g. 
Thunderbird and SSL.


One problem left: pine doesn't work any more with rsh:
cat .pinerc (filtered):
rsh-path=
rsh-command=/usr/sbin/dovecot --exec-mail imap

Starting pine:
1.) Opening INBOX
2.) [SECURITY PROBLEM: insecure server advertised AUTH=PLAIN]
3.) Afterwards I'm asked for a password: HOST: localhost (INSECURE)  
ENTER LOGIN NAME [user] :

3.) cancel: [IMAP protocol error: Authentication aborted by client.]

Config: no changes at all.

Any ideas why this is broken?

Thnx.

Ciao,
Gerhard

Re: [Dovecot] Problem with local pine after upgrade to 1.2.5

[Gerhard Wiesinger]

Hello Pascal,

Thanx for the very fast answer, patch works well.

Back again in pine :-)

Thnx.

Ciao,
Gerhard

--
http://www.wiesinger.com/


On Fri, 2 Oct 2009, Pascal Volk wrote:


On 10/02/2009 04:18 PM Gerhard Wiesinger wrote:

Hello,

I upgraded from dovecot 1.1.17 to 1.2.5. Works well so far with e.g.
Thunderbird and SSL.

One problem left: pine doesn't work any more with rsh:
cat .pinerc (filtered):
rsh-path=
rsh-command=/usr/sbin/dovecot --exec-mail imap

Starting pine:
1.) Opening INBOX
2.) [SECURITY PROBLEM: insecure server advertised AUTH=PLAIN]
3.) Afterwards I'm asked for a password: HOST: localhost (INSECURE)
ENTER LOGIN NAME [user] :
3.) cancel: [IMAP protocol error: Authentication aborted by client.]

Config: no changes at all.

Any ideas why this is broken?



Have you applied this patch?
http://hg.dovecot.org/dovecot-1.2/rev/0f04c7da33f1


Regards,
Pascal
--
The trapper recommends today: 5e1f1e55.0927...@localdomain.org

[Dovecot] Sieve Rule for Folders

[Gerhard Wiesinger]

Hello!

Is it possible with sieve to do the following:
When a new message is added to a folder (e.g. dovecot folder and not 
INBOX) then an action like forwarding it per E-Mail should be triggered.


Is this possible? If yes, how does the sieve script look like?

If possible, can a shell script also be triggered as action?

Thanx.

Ciao,
Gerhard

--
http://www.wiesinger.com/

Re: [Dovecot] v1.1.8 released

[Gerhard Wiesinger]

Hello Timo!

Looks like the performance problems on opening/delivering mbox mailboxes 
and index updates/usage have been solved with dovecot 1.1.8 (your inbox 
subject was dovecot 1.1rc7 and cache with deliver). 
http://www.mail-archive.com/dovecot@dovecot.org/msg08274.html


Is this quite logically with the changes you made in 1.1.8?

Ciao,
Gerhard

--
http://www.wiesinger.com/


On Wed, 7 Jan 2009, Timo Sirainen wrote:


http://dovecot.org/releases/1.1/dovecot-1.1.8.tar.gz
http://dovecot.org/releases/1.1/dovecot-1.1.8.tar.gz.sig

Most importantly mbox bugfixes. v1.1 should finally be as stable with
mboxes as it was with v1.0. Hopefully we'll also soon have the first
v1.2 beta release and the final v1.2.0 somewhat soon after that.

- mbox: Several bugfixes. Fixes next message unexpectedly lost
 errors and perhaps some other problems as well.
- deliver: It wasn't possible to override boolean settings in
  lda section by setting them to no.
- Maildir++ quota didn't correctly check if maildirs had changed
  during recalculation.
- kqueue notify: Fixed assert-crash in some situations
- dbox: Several fixes to handling Maildir migrations
- Logging/error message improvements

Re: [Dovecot] Problem with squirrelmail and dovecot 1.1

[Gerhard Wiesinger]

Hello Timo!

dovecot -n
# 1.1.2: /etc/dovecot.conf
listen: [::]
ssl_listen: [::]
ssl_cert_file: /etc/pki/dovecot/dovecot-extern.pem
ssl_key_file: /etc/pki/dovecot/private/dovecot-extern.pem
login_dir: /var/run/dovecot-login
login_executable: /usr/libexec/dovecot/imap-login
mail_location: mbox:~:INBOX=/var/mail/%u
mail_full_filesystem_access: yes
mbox_write_locks: fcntl
mbox_lazy_writes: no
mail_executable: /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap
imap_client_workarounds: tb-extra-mailbox-sep
auth default:
  passdb:
driver: pam
  userdb:
driver: passwd
  socket:
type: listen
master:
  path: /var/run/dovecot-auth-master
  mode: 432
  group: users

So ~/Mail should be ok (and it works with TB and alpine).

Ciao,
Gerhard

--
http://www.wiesinger.com/


On Thu, 28 Aug 2008, Timo Sirainen wrote:


On Fri, 2008-08-22 at 13:01 +0200, Gerhard Wiesinger wrote:

Configuration worked well. I think it has to do with the upgrade from dovecot
1.0 to 1.1 and the LIST command. Thunderbird/alpine work well.

Commands from rawlog are:
A002 LIST  ~/Mail/Drafts
A002 OK List completed.


Is the ~/Mail/ prefix correct?


Has something changed in the folder behaviour of dovecot from 1.0 to 1.1?


Not that I know of.


If you need more information please let me know it.


dovecot -n is always helpful. The most important settings here would be
the namespace configuration and the value of
mail_full_filesystem_access.

Re: [Dovecot] Problem with squirrelmail and dovecot 1.1

[Gerhard Wiesinger]

Hello Timo!

Looks to be fixed.

So the only bug for 100% satisfaction is the mbox/index problem right now.

BTW: You said that mbox is broken in 1.1.x? What's the reason and what are 
the consequences?


Ciao,
Gerhard

--
http://www.wiesinger.com/


On Thu, 28 Aug 2008, Timo Sirainen wrote:


On Thu, 2008-08-28 at 12:53 +0200, Gerhard Wiesinger wrote:

mail_full_filesystem_access: yes

..

So ~/Mail should be ok (and it works with TB and alpine).


Ah, right. I just fixed that:
http://hg.dovecot.org/dovecot-1.1/rev/c1e022104285

[Dovecot] Problem with squirrelmail and dovecot 1.1

[Gerhard Wiesinger]

Hello!

Has noone any idea?

Ciao,
Gerhard

--
http://www.wiesinger.com/



Hello!

I'm running squirrelmail 1.4.8 (I know this is not the latest version) and know 
I'm having troubles with:

1.) Folder list view
2.) Save to sent or Drafts folder.

Configuration worked well. I think it has to do with the upgrade from dovecot 
1.0 to 1.1 and the LIST command. Thunderbird/alpine work well.


Commands from rawlog are:
A002 LIST  ~/Mail/Drafts
A002 OK List completed.

or

A002 LIST  ~/Mail/sent
A003 CREATE ~/Mail/sent
A002 OK List completed.
A003 NO Mailbox exists.

Has something changed in the folder behaviour of dovecot from 1.0 to 1.1?

If you need more information please let me know it.

Any ideas?

Thnx.

Ciao,
Gerhard

--
http://www.wiesinger.com/

[Dovecot] Problem with squirrelmail and dovecot 1.1

[Gerhard Wiesinger]

Hello!

I'm running squirrelmail 1.4.8 (I know this is not the latest version) and 
know I'm having troubles with:

1.) Folder list view
2.) Save to sent or Drafts folder.

Configuration worked well. I think it has to do with the upgrade from 
dovecot 1.0 to 1.1 and the LIST command. Thunderbird/alpine work well.


Commands from rawlog are:
A002 LIST  ~/Mail/Drafts
A002 OK List completed.

or

A002 LIST  ~/Mail/sent
A003 CREATE ~/Mail/sent
A002 OK List completed.
A003 NO Mailbox exists.

Has something changed in the folder behaviour of dovecot from 1.0 to 1.1?

If you need more information please let me know it.

Any ideas?

Thnx.

Ciao,
Gerhard

--
http://www.wiesinger.com/

Re: [Dovecot] Procmail versus Dovecot LDA

[Gerhard Wiesinger]

Hello Timo!

A configuration issue as we had with the config discussed below can be 
definitly barred.


locate only finds somehting in /home/gerhard/Mail/.imap/ which is correct.

Config:
~/.imap 3  ls -l
total 0
lrwxrwxrwx  1 gerhard users 30 Jun 13 22:30 INBOX - 
/home/gerhard/Mail/.imap/INBOX

# Users should have access to the whole home directory
mail_location = mbox:~:INBOX=/var/mail/%u

deliver section:
# Mail folders should be in ~/Mail
mail_location = mbox:~/Mail:INBOX=/var/mail/%u

How can I make a more consistent configuration with namespaces?
To avoid the symlink we might include: INBOX_CACHE_DIR=~/Mail

Do you have the warnings patch (inconsitent sizes/timesptamps between 
index and filesystem) running at your servers, too? Do you get warnings?


Maybe you can include these warnings in the normal release and some other 
people have the same problems.


I think the used filesystem ext3 is rock solid.

Ciao,
Gerhard

--
http://www.wiesinger.com/


On Wed, 13 Aug 2008, Timo Sirainen wrote:


On Aug 13, 2008, at 12:02 AM, Gerhard Wiesinger wrote:

BTW: Timo please fix the bugs regarding deliver and dovecot index bugs as 
already discussed. Scanning large mailbox folders takes a lot of time. If 
you need any help just let me know it.


I was never able to reproduce the problem myself, and the last time we found 
a solution to one problem it was a configuration mistake in your end. So I'm 
a bit afraid if I again spend a lot of time with it we'll only find out that 
it's a configuration issue again.. Or possibly an issue in 
filesystem/something.

Re: [Dovecot] Procmail versus Dovecot LDA

[Gerhard Wiesinger]

Hello!

You can use sendmail/MailScanner/Spamassassin/deliver/procmail.

Maybe you find my procmail patch usefull.
http://markmail.org/message/v4gga3ba75xqemra
http://www.dovecot.org/list/dovecot/2007-March/020787.html

If you need any help just let me know it.

BTW: Timo please fix the bugs regarding deliver and dovecot index bugs as 
already discussed. Scanning large mailbox folders takes a lot of time. If 
you need any help just let me know it.


Ciao,
Gerhard

--
http://www.wiesinger.com/


On Tue, 12 Aug 2008, Jordan Hayes wrote:


I'll note that I'm using procmail because of the ability to filter
and run SpamAssassin from it.


Typically you'd run SpamAssassin first and Dovecot deliver after that.


Is anyone here doing this for virtual users who could describe what they did?

Bonus points for actual configuration files :-)

Thanks,

/jordan 

Re: [Dovecot] v1.1.rc11 released

[Gerhard Wiesinger]

Hello Timo!

Anything changed since 1.1rc9 regarding the mbox issue?
Did you have a look at the file I sent you?

Thnx.

Ciao,
Gerhard

Timo Sirainen wrote:

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc11.tar.gz
http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc11.tar.gz.sig

This is the final v1.1 RC. Tomorrow I'll change only the version number,
update the documentation and call it v1.1.0. But please test this anyway
to make sure I didn't happen to break anything since rc10 :)

- dovecot-uidlist is now recreated if it results in file shrinking
  over 25%.
- Some other minor fixes

  

Re: [Dovecot] v1.1.rc1 released

[Gerhard Wiesinger]

On Tue, 4 Mar 2008, Timo Sirainen wrote:


On Feb 22, 2008, at 9:42 AM, Gerhard Wiesinger wrote:


Hello Timo!
Looks like that mbox index handling still doesn't work with deliver:
1.) 1s mail delivered: Only dovecot.index.log is generated.


This is correct. dovecot.index doesn't need to be created/updated always, 
and dovecot.index.cache isn't created because there's nothing that's known 
wanted to be cached.


Hmmm. But shouldn't this be a feature of 1.1 that deliver updates indexes 
at deliver time? (maybe you can choose the typical indexes the clients 
use).


Updating dovecot.index.log is enough. v1.0 unneededly wastes disk I/O writing 
to dovecot.index way too often.




I don't think this is wasted disk I/O updating indexes as soon as 
possible. When the mailbox (mbox) is read afterwards on large mboxes there 
is much more waste in reading large files.


e.g. When deliver would write e.g. 3 mails with 40 MB:
1.) with indexes
write large mailbox
update small index

reopen:
only read small index

2.) without indexes
write large mailbox

reopen:
read large mailbox
update small index

So case 1 with indexes is IHMO in total more efficient.


1. deliver the first mail
2. open the mailbox
3. deliver lots of large mails
4. open the mailbox again

It should be fast. (and I just tested - it is)


Yes, that's exactly the testcase I use. But here it is slow (opening is 
always done with doevecot 1.0.latest/alpine 1.00 and deliver is done with 
1.1.rc1). I use large files to see a time I see on the first look on 
opening.


Check with v1.1's idxview what the index file contains after steps 2, 3 and 
4. After step 2 it should contain for the first message all the cached fields 
that client needs. Between 3 and 4 steps there should be no changes, and the 
cache fields should be exactly the same with the same decision rules as with 
step 2.




I will check that.

Ciao,
Gerhard

--
http://www.wiesinger.com/

Re: [Dovecot] v1.1.beta13 released

[Gerhard Wiesinger]

Hello Timo!

Looks like that 1.1.beta13 doesn't touch the indexes with mbox at all. 
None are generated/updated.


Ciao,
Gerhard

--
http://www.wiesinger.com/


On Sun, 30 Dec 2007, Timo Sirainen wrote:


http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta13.tar.gz
http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta13.tar.gz.sig

Changes since beta12:

- Half of LDAP code was rewritten to fix reconnect/queuing problems. I
did test that the new code works with and without auth binds, but be
careful.
- \Recent flags should finally work correctly with maildir.
- last_used field wasn't updated for cache fields that were permanently
cached. This caused them to be dropped after a month.

TODO for RC1:

- When pipelining commands, do only one sync after all of them. Besides
improving performance, this fixes some rare problems when multiple
commands are running simultaneously.
- SEARCH/SORT: Replace invalid input with unicode replacement
character instead of just skipping it.
- Squat: Handle expunges. NFS support.
- Fix Lucene support.

Re: [Dovecot] v1.1.beta12 released

[Gerhard Wiesinger]

Hello Timo!

Still got a core on my usual deliver testcase:
#0  0x005b2c32 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
#1  0x0096b989 in raise () from /lib/tls/libc.so.6
#2  0x0096d342 in abort () from /lib/tls/libc.so.6
#3  0x080b1da4 in default_fatal_handler (type=LOG_TYPE_PANIC, status=0,
format=0x80c3960 file %s: line %d (%s): assertion failed: (%s), 
args=0xbfe6d014 \223\226\f\b\022\004) at failures.c:165
#4  0x080b1e57 in i_panic (format=0x80c3960 file %s: line %d (%s): 
assertion failed: (%s)) at failures.c:196

#5  0x080822fa in index_mail_close (_mail=0x941eb38) at index-mail.c:1032
#6  0x080826ce in index_mail_free (_mail=0x941eb38) at index-mail.c:1229
#7  0x080a2e20 in mail_free (mail=0xbfe6d0b8) at mail.c:18
#8  0x0805a928 in main (argc=-1075392304, argv=0x0) at deliver.c:997

Ciao,
Gerhard

--
http://www.wiesinger.com/


On Sat, 22 Dec 2007, Timo Sirainen wrote:


http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta12.tar.gz
http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta12.tar.gz.sig

Still not a release candidate, maybe the next one..

This release fixes a lot of bugs and adds some new sanity checks. Fixes
quite a lot of mbox problems.

v1.1.beta11 (no other versions) had a potential security hole where
memory was free()d multiple times.

\Recent flags should work perfectly now with mbox. Still somewhat broken
with maildir.

Re: [Dovecot] v1.1.beta11 released

[Gerhard Wiesinger]

Hello Timo!

Looks like that dovecot-1.1.beta11 is pretty buggy. deliver cored after 
the first run.


Do you need any further information? (As usual I tried my procmail 
testcase which cored)


Ciao,
Gerhard

--
http://www.wiesinger.com/


On Sun, 9 Dec 2007, Timo Sirainen wrote:


http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta11.tar.gz
http://dovecot.org/releases/1.1/beta/dovecot-1.1.beta11.tar.gz.sig

This one should be the last beta release before the first v1.1 release
candidate.

Re: [Dovecot] v1.1.alpha1 released

[Gerhard Wiesinger]

Hello Timo!

Is the deliver/index update code also included for mbox mailboxes?

Ciao,
Gerhard

--
http://www.wiesinger.com/


On Thu, 19 Jul 2007, Timo Sirainen wrote:


http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz
http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz.sig

This is the first alpha release of Dovecot v1.1. I hope that it
stabilizes into final release within a few months. There are a lot of
new features since v1.0. The most important ones are listed at the end
of this post.

This is the only v1.1.alpha announcement I send to dovecot-news list (or
to www.dovecot.org news). The next one probably will be v1.1.rc1.

I've been stress testing the code a lot and I've also been using it
myself for almost a year, so I think this release should actually be
quite stable and usable. But since I haven't tested everything, there
might be some crashes and misbehaving commands.

So this release should now have all the major features that I intend to
add to v1.1 (except for dbox rewrite, see below). Some smaller features
will still be added. The rest of the major features in my previous v1.1
list will go to v1.2.

While v1.1 is getting stabilized I'm beginning to rewrite dbox code. Its
code is isolated from the rest of Dovecot, so it can't destabilize
anything else. Hopefully it will be ready before v1.1 release, although
maybe still marked as experimental.

Some of the features might not be considered quite ready yet:

- Mailbox list indexes improve STATUS performance a lot (maybe 7x) when
mailboxes haven't changed. Handling updates however is a lot slower than
I'd want (2x with one client, more with multiple), so you may want to
disable them with mailbox_list_index_disable=yes until the update
performance gets better.

- THREAD code is completely rewritten with support for incremental
updates and index files. I tested it last year and it seemed OK, but I
didn't dare try it now so I wouldn't have to delay this alpha if it was
broken :) I'll do some more testing soon, but for now be careful with
using v1.1 with webmails.

- SORT code also uses indexes now, but it's a lot simpler so it
probably works.

- Squat indexes work and I'm using them myself, but they'll be
rewritten for v1.2 with a new faster format.

- Although Dovecot now flushes NFS attribute/data caches when needed,
I'm not sure if it's done in all the necessary places.

- I don't remember if I've tested expire plugin at all.

So, the largest changes I've added to NEWS file (which BTW won't contain
changes between alphas/betas/rcs, those will be only in my mailing list
posts):

* After Dovecot v1.1 has modified index or dovecot-uidlist files,
  they can't be opened anymore with Dovecot versions earlier than
  v1.0.2.
* Empty passwords in passdb doesn't allow user to log in with any
  password anymore. To do that you'll also need to set nopassword
  extra field.

+ IMAP: Added support for UIDPLUS and LIST-EXTENDED extensions.
+ IMAP SORT: Sort keys are indexed, which makes SORT commands faster.
+ IMAP THREAD: Threads are indexed into a dovecot.index.thread file.
  It can usually be updated incrementally, so this makes THREAD fast.
+ Added Dovecot-specific X-REFERENCES2 threading algorithm.
  It's similar to REFERENCES, but it doesn't do base subject merging
  and it sorts the threads by their newest message.
+ When saving messages, update cache file immediately with the data
  that we expect client to fetch later. Maildir-only currently.
+ NFS attribute and data caches are are flushed whenever needed.
  See mail_nfs_storage and mail_nfs_index settings.
+ Mailbox list indexes. Mailbox metadata is stored there, so STATUS
  commands can return synchronized mailboxes' metadata simply by
  reading a single mailbox list index file. Currently works only with
  Maildir++ layout.
+ Out of order command execution (SEARCH, FETCH, LIST), nonstandard
  command cancellation (X-CANCEL tag)
+ Expire plugin can be used to keep track of oldest messages in
  specific mailboxes. A nightly run can then quickly expunge old
  messages from the mailboxes that have them. The tracking is done
  using lib-dict, so you can use either Berkeley DB or SQL database.
+ Namespaces are supported everywhere now.
+ Full text search indexing support with Lucene and Squat backends.
+ OTP and S/KEY authentication mechanisms (by Andrey Panin).
+ mbox and Maildir works with both Maildir++ and FS layouts. You can
  change these by appending :LAYOUT=maildir++ or :LAYOUT=fs to
  mail_location.
+ LDAP: Support templates in pass_attrs and user_attrs
+ Support for listening in multiple IPs/ports.
+ Quota plugin rewrite: Support for multiple quota roots, warnings,
  allow