November 2017 - dovecot

Mark message as read when moved to Trash
by Felix Rubio Dalmau 26 Nov '17

26 Nov '17

Hi all, When I send a message to trash, without previously reading it (just with the subject is enough to say I do not want to read it), it remains as "unread". Then, clients (I am using Kmail) report there are unread message, when all of them are in Trash. The question, then is: Is there any way to automatically mark a message as read, when that message is moved to Trash? Thank you! Felix

5 5

Re: Sieve coding question
by Stephan Bosch 25 Nov '17

25 Nov '17

Op 11/25/2017 om 5:33 PM schreef Roger Klorese: > On Sat, Nov 25, 2017 at 4:56 AM Stephan Bosch <stephan(a)rename-it.nl > <mailto:stephan@rename-it.nl>> wrote: > > Op 11/19/2017 om 8:54 AM schreef Roger B.A. Klorese: > > On 11/16/17 11:03 AM, Stephan Bosch wrote: > >> Op 11/16/2017 om 7:42 PM schreef lists.dovecot(a)rogerklorese.com > <mailto:lists.dovecot@rogerklorese.com>: > >>> Is there a more appropriate list on which to ask for assistance in > >>> coding Sieve rules, or may I ask here? > >> I know of no other suitable venue, so go ahead. > >> > >> Regards, > >> > >> Stephan. > > > And I > > > Here is the config. I don't think IMAPsieve is configured... > > Then I don't understand what you mean. Sieve is normally only involved > at initial delivery, not when messages are moved between mailboxes. > > Regards, > > Stephan. > > > Of cpurse, that was my understanding too. Hence the question. Are you sure your mail client doesn't have any rules of its own that may be doing this? Regards, Stephan.

1 0

Sieve coding question
by lists.dovecot＠rogerklorese.com 25 Nov '17

25 Nov '17

Is there a more appropriate list on which to ask for assistance in coding Sieve rules, or may I ask here?

3 5

Re: Upgrade to 2.2.32 from 2.2.15 failed
by Mark Foley 25 Nov '17

25 Nov '17

No, is that something that would make a difference between 2.2.15 and 2.2.32? --Mark On Fri, 24 Nov 2017 21:37:47 -0800 Gary <lists(a)lazygranch.com> wrote: > Out of curiosity, do you do a !SSLv3 in the conf file? > > > Original Message >> From: mfoley(a)ohprs.org >> Sent: November 24, 2017 9:04 PM >> To: dovecot(a)dovecot.org >> Subject: Upgrade to 2.2.32 from 2.2.15 failed >> >> I have a problem. I have been running Dovecot 2.2.15 and I'd like to upgrade. My distro >> (Slackware) has dovecot 2.2.32 available. I downloaded and installed that, but it didn't work. >> No one was able to get messages from the dovecot server on their workstations. The following is >> the entire dovecot log file from startup to the last message generated. No more messages went >> into the logfile after line 76, even with clients trying to connect. The 174.233.134.88 IP is >> from an external user connecting from his iPhone. The normal successful message from this user >> are shown at bottom. >> >> I'm suspecting something to do with line 18 where is says "Auth process broken." If anyone has >> any insight I'd deeply appreciate it as I'd love to upgrade. >> >> THX -- Mark >> >> 1 Nov 24 19:22:24 master: Info: Dovecot v2.2.32 (dfbe293d4) starting up for imap (core dumps disabled) >> 2 Nov 24 19:22:24 ssl-params: Info: Generating SSL parameters >> 3 Nov 24 19:22:26 ssl-params: Info: SSL parameters regeneration completed >> 4 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x10, ret=1: before/accept initialization [174.233.134.88] >> 5 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2001, ret=1: before/accept initialization [174.233.134.88] >> 6 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client hello A [174.233.134.88] >> 7 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server hello A [174.233.134.88] >> 8 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write certificate A [174.233.134.88] >> 9 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write key exchange A [174.233.134.88] >> 10 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server done A [174.233.134.88] >> 11 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 flush data [174.233.134.88] >> 12 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client certificate A [174.233.134.88] >> 13 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client key exchange A [174.233.134.88] >> 14 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client key exchange A [174.233.134.88] >> 15 Nov 24 19:23:02 auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth >> 16 Nov 24 19:23:02 auth: Debug: Module loaded: /usr/lib64/dovecot/auth/lib20_auth_var_expand_crypt.so >> 17 Nov 24 19:23:02 auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth >> 18 Nov 24 19:23:02 imap-login: Info: Disconnected: Auth process broken (disconnected before auth was ready, waited 0 secs): user=<>, rip=174.233.134.88, lip=98.102.63.107, TLS handshaking, session=<idAcrMNe8xqu6YZY> >> 19 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x10, ret=1: before/accept initialization [174.233.134.88] >> 20 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2001, ret=1: before/accept initialization [174.233.134.88] >> 21 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client hello A [174.233.134.88] >> 22 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server hello A [174.233.134.88] >> 23 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write certificate A [174.233.134.88] >> 24 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write key exchange A [174.233.134.88] >> 25 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server done A [174.233.134.88] >> 26 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 flush data [174.233.134.88] >> 27 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client certificate A [174.233.134.88] >> 28 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client key exchange A [174.233.134.88] >> 29 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client key exchange A [174.233.134.88] >> 30 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client key exchange A [174.233.134.88] >> 31 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read certificate verify A [174.233.134.88] >> 32 Nov 24 19:23:02 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read finished A [174.233.134.88] >> 33 Nov 24 19:23:03 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read finished A [174.233.134.88] >> 34 Nov 24 19:23:03 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write change cipher spec A [174.233.134.88] >> 35 Nov 24 19:23:03 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write finished A [174.233.134.88] >> 36 Nov 24 19:23:03 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 flush data [174.233.134.88] >> 37 Nov 24 19:23:03 imap-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully [174.233.134.88] >> 38 Nov 24 19:23:03 imap-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully [174.233.134.88] >> 39 Nov 24 19:23:04 auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth >> 40 Nov 24 19:23:04 auth: Debug: Module loaded: /usr/lib64/dovecot/auth/lib20_auth_var_expand_crypt.so >> 41 Nov 24 19:23:04 auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth >> 42 Nov 24 19:23:04 imap-login: Info: Disconnected: Auth process broken (disconnected before auth was ready, waited 2 secs): user=<>, rip=174.233.134.88, lip=98.102.63.107, TLS, session=<YGw7rMNe+Rqu6YZY> >> 43 Nov 24 19:23:04 imap-login: Debug: SSL alert: close notify [174.233.134.88] >> 44 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x10, ret=1: before/accept initialization [174.233.134.88] >> 45 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x2001, ret=1: before/accept initialization [174.233.134.88] >> 46 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client hello A [174.233.134.88] >> 47 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server hello A [174.233.134.88] >> 48 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write certificate A [174.233.134.88] >> 49 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write key exchange A [174.233.134.88] >> 50 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server done A [174.233.134.88] >> 51 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 flush data [174.233.134.88] >> 52 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client certificate A [174.233.134.88] >> 53 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client key exchange A [174.233.134.88] >> 54 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client key exchange A [174.233.134.88] >> 55 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client key exchange A [174.233.134.88] >> 56 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read certificate verify A [174.233.134.88] >> 57 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read finished A [174.233.134.88] >> 58 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read finished A [174.233.134.88] >> 59 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write change cipher spec A [174.233.134.88] >> 60 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write finished A [174.233.134.88] >> 61 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x2001, ret=1: SSLv3 flush data [174.233.134.88] >> 62 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully [174.233.134.88] >> 63 Nov 24 19:23:05 imap-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully [174.233.134.88] >> 64 Nov 24 19:23:08 auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth >> 65 Nov 24 19:23:08 auth: Debug: Module loaded: /usr/lib64/dovecot/auth/lib20_auth_var_expand_crypt.so >> 66 Nov 24 19:23:08 auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth >> 67 Nov 24 19:23:08 imap-login: Info: Disconnected: Auth process broken (disconnected before auth was ready, waited 3 secs): user=<>, rip=174.233.134.88, lip=98.102.63.107, TLS, session=<7ZF4rMNe8hqu6YZY> >> 68 Nov 24 19:23:08 imap-login: Debug: SSL alert: close notify [174.233.134.88] >> 69 Nov 24 19:23:16 auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth >> 70 Nov 24 19:23:16 auth: Debug: Module loaded: /usr/lib64/dovecot/auth/lib20_auth_var_expand_crypt.so >> 71 Nov 24 19:23:16 auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth >> 72 Nov 24 19:23:16 imap-login: Info: Disconnected: Auth process broken (disconnected before auth was ready, waited 0 secs): user=<>, rip=192.168.0.54, lip=192.168.0.2, session=<6bbyrMNeGM/AqAA2> >> 73 Nov 24 19:24:13 auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth >> 74 Nov 24 19:24:13 auth: Debug: Module loaded: /usr/lib64/dovecot/auth/lib20_auth_var_expand_crypt.so >> 75 Nov 24 19:24:13 auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth >> 76 Nov 24 19:24:13 imap-login: Info: Disconnected: Auth process broken (disconnected before auth was ready, waited 0 secs): user=<>, rip=192.168.0.52, lip=192.168.0.2, session=<b75YsMNeb9nAqAA0> >> >> Normal OK messages from dovecot 2.2.15: >> >> Nov 24 23:50:49 imap-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully [174.233.134.88] >> Nov 24 23:50:49 imap-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation finished successfully [174.233.134.88] >> Nov 24 23:50:49 auth: Debug: client in: AUTH 1 PLAIN service=imap secured session=vQnEacde6QCu6YZY lip=98.102.63.107 rip=174.233.134.88 lport=993 rport=6889 resp=AG0udGhlbQAhbXRfMTAxOQ== (previous base64 data may contain sensitive data) >> Nov 24 23:50:49 auth-worker(17650): Debug: shadow(m.them,174.233.134.88): lookup >> Nov 24 23:50:49 auth: Debug: client passdb out: OK 1 user=m.them >> >> Finally, the 2.2.15 doveconf, which I used the same for 2.2.32: >> >> > doveconf -n >> # 2.2.15: /usr/local/etc/dovecot/dovecot.conf >> # OS: Linux 4.4.88 x86_64 Slackware 14.2 >> auth_debug = yes >> auth_debug_passwords = yes >> auth_gssapi_hostname = $ALL >> auth_krb5_keytab = /etc/dovecot/dovecot.keytab >> auth_mechanisms = plain login gssapi >> auth_use_winbind = yes >> auth_username_format = %n >> auth_verbose = yes >> auth_verbose_passwords = plain >> disable_plaintext_auth = no >> info_log_path = /var/log/dovecot_info >> mail_location = maildir:~/Maildir >> passdb { >> driver = shadow >> } >> protocols = imap >> ssl_cert = </etc/ssl/certs/OHPRS/GoDaddy/Apache/2016-08-10/54e789087d419b6e.crt >> ssl_key = </etc/ssl/certs/OHPRS/GoDaddy/mail.ohprs.org.key >> userdb { >> driver = passwd >> } >> verbose_ssl = yes

1 0

Dovecot proxy
by Federico Bartolucci 24 Nov '17

24 Nov '17

Hello, has someone already tested the dovecot-proxy with more than 10 nodes? or someone knows anyway if is it officially supported up to a certain number? Thanks.

2 1

set parameter per user
by A. Schulze 24 Nov '17

24 Nov '17

Hello, My dovecot server (2.2.33.2) work with "lmtp_save_to_detail_mailbox = no" Now I would like to enable the feature for /some/ users. Is that an option that could be set from an LDAP entry? I tried the following: modify my ldap schema to allow an optional attribute "lmtp-save-to-detail-mailbox" in /etc/dovecot/ldap.conf user_attrs = ... =lmtp_save_to_detail_mailbox=%{ldap:lmtp-save-to-detail-mailbox:no}, =... Now I set an ldapattribute "lmtp-save-to-detail-mailbox" with value "yes" for some users. Unfortunately messages to user+extension@domain are still delivered to INBOX/ while they should be delivered to INBOX/extension. I also tried to make the attribute accessible vi pass_attr and userdb_foo = ... because I use prefetch driver as userdb. I also disabled prefetching at all but no luck :-/ any Ideas? Andreas

3 5

Exclude disabled accounts
by Evgeniy Korneechev 23 Nov '17

23 Nov '17

Hello! We have userdb=passwd. userdb { driver = passwd #server was entered domain Active Directory override_fields = home=/var/vmail/glu_vrem/%u } If I disable in AD user's account, he can not sign in. But he can and will receive letters, which of course is not correct. How can I exclude disabled accounts from 'userdb'? dovecot -n: # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.4.39-std-def-alt0.M80P.1 x86_64 ALT 8.1 Server auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login cram-md5 auth_socket_path = /var/run/dovecot/auth-userdb auth_username_chars = auth_verbose = yes auth_verbose_passwords = plain base_dir = /var/run/dovecot/ debug_log_path = /var/log/dovecot disable_plaintext_auth = no first_valid_gid = 502 first_valid_uid = 502 last_valid_gid = 268999999 last_valid_uid = 268999999 log_path = /var/log/dovecot login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c mail_access_groups = vmail mail_debug = yes mail_gid = 502 mail_location = maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/ mail_plugins = " quota autocreate" mail_privileged_group = vmail mail_uid = 502 managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext imapflags notify mbox_write_locks = fcntl namespace { list = children location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u prefix = shared/%%u/ separator = / subscriptions = yes type = shared } namespace inbox { inbox = yes location = prefix = separator = / type = private } passdb { driver = pam } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { quota_rule = *:storage=5G recipient_delimiter = + sieve = /etc/dovecot/sieves/default.sieve sieve_default = /etc/dovecot/sieves/default.sieve sieve_dir = ~/sieve sieve_extensions = +notify +imapflags sieve_max_redirects = 8 } protocols = imap pop3 lmtp sieve service auth-worker { user = root } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0600 user = vmail } } service imap-login { inet_listener imap { port = 143 } } service imap { process_limit = 1024 vsz_limit = 256 M } service lmtp { unix_listener lmtp { mode = 0666 } } service managesieve-login { inet_listener sieve { port = 4190 } vsz_limit = 64 M } service pop3-login { inet_listener pop3 { port = 110 } } service pop3 { process_limit = 1024 } ssl_ca = </usr/share/ca-certificates/ca-bundle.crt ssl_cert = </etc/dovecot/server.crt ssl_key = # hidden, use -P to show it userdb { driver = passwd override_fields = home=/var/vmail/glu_vrem/%u } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { mail_plugins = " quota autocreate sieve" } protocol lda { mail_plugins = " quota autocreate sieve quota" plugin { quota = dict:user::file:/var/vmail/glu_vrem/%n/.quotausage } } protocol imap { mail_plugins = " quota autocreate autocreate imap_quota" plugin { autocreate = INBOX autocreate2 = Sent autocreate3 = Trash autocreate4 = Drafts autocreate5 = Junk autosubscribe = INBOX autosubscribe2 = Sent autosubscribe3 = Trash autosubscribe4 = Drafts autosubscribe5 = Junk quota = dict:user::file:/var/vmail/glu_vrem/%n/.quotausage } } protocol sieve { mail_max_userip_connections = 10 managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 5 managesieve_max_line_length = 65536 } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } -- WBR, Korneechev Evgeniy BaseALT/ALTLinux Team

2 1

Passing information from passdb to userdb
by Qmail 23 Nov '17

23 Nov '17

I'm trying to hack together a new authentication back-end and I wanted to know if it's possible to pass values from passdb to userdb in the auth_request structure at authentication time. I modified struct auth_request in auth-request.h to contain a new variable and it gets set properly in my passdb, however the value is not there when checking for it userdb. I'm very novice when it comes to Dovecot programming so any help is appreciated. Thanks!

2 3

[Dovecot] Configure replication in backup mode
by japerez 22 Nov '17

22 Nov '17

Dovecot 2.2.27 (c0f36b0) I'm trying to configure dovecot to backup all my email to a secondary server using "dsync". I got it working in "sync" mode or two-way synchonization, that means whatever happens in one server gets replicated in the other. However, documentation also says that a one way synchronization is posible, yet, after spending a good amount of hours searching, I failed to find what do I have to modify in my "30-dsync.conf" to do so. My 30-dsync.conf reads as follows: #This sets globally the port needed to connect #to the doveadm service #doveadm_port = 12345 # Set the password globally to use for connecting to # and requiring for the doveadm service doveadm_password = +++++++++++++ # Set the directory for validating certificates # provided when running with SSL enabled # Should be the standard OpenSSL certificate directory by default ssl_client_ca_dir = /etc/ssl/certs # Configure the doveadm service to listen service doveadm { inet_listener { # port to listen on port = 12345 # enable SSL # ssl = yes } } # Configure the aggregator service for notifications service aggregator { fifo_listener replication-notify-fifo { # Your mail user that's managing files generally is used here user = +++++ mode = 0755 } unix_listener replication-notify { user = +++++ mode = 0755 } } # Configure the replicator service service replicator { user = root process_min_avail = 1 unix_listener replicator-doveadm { user = root mode = 0755 } } replication_dsync_parameters = -d -N -l 30 -U -x nobody # Configure target hosts for replication # tcps can be tcp if you don't want to connect with SSL # :port can be omitted if it's the default set globally for doveadm plugin { mail_replica = tcp:*.*.*.*:12345 } Thanks.

1 0

dovecot initscript
by dovecot＠schoepfer.info 22 Nov '17

22 Nov '17

Hi, about https://wiki.dovecot.org/DovecotInit, i wondered about stop) if test $running = yes; then echo "Stopping Dovecot" kill `cat $pidfile` echo "." else echo "Dovecot is already stopped." fi ;; Is "doveadm stop" technically the same, or better/worse/safer? Does "doveadm stop" wait until all child processes are finished, or would "sleep 1" in the restart-function still be necessary in this case? Is "kill -HUP `cat $pidfile`" technically the same as "doveadm reload"? If it'a all fine to use doveadm in an initscript, i there a reason to not add "doveadm start" to doveadm functionality? Surely this is not that important, but maybe a bit more consistent. Thanks, Johannes

1 0