- dovecot - dovecot.org

does lda_save_to_detail_mailbox exist?
by A. Schulze 04 Dec '14

04 Dec '14

Hello, there is a nice feature in lmtp to save messages to user+foo@domain in INBOX/foo Looks like that doesn't work as good if lda is used. I have dovecot-2.2.13 mail_location = maildir:%h/ lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes *lmtp*_save_to_detail_mailbox = yes messages to user+foo generate an error and are saved to INBOX not matter if INBOX/foo exist or not: Dec 4 09:40:59 mail dovecot: lda(user(a)example.org): Debug: Effective uid=10020, gid=10020, home=/var/mail/user(a)example.org/ Dec 4 09:40:59 mail dovecot: lda(user(a)example.org): Debug: Destination address: user(a)example.org (source: user@hostname) Dec 4 09:40:59 mail dovecot: lda(user(a)example.org): msgid=<3jtWlm3FCHz52KG@localhost>: save failed to open mailbox foo: Mailbox can't be created Dec 4 09:40:59 mail dovecot: lda(user(a)example.org): msgid=<3jtWlm3FCHz52KG@localhost>: saved mail to INBOX # doveadm user -u user(a)example.org userdb: user(a)example.org home : /var/mail/user(a)example.org/ quota_rule: *:bytes=1000000 master_user: user(a)example.org # doveadm mailbox list -u user(a)example.org INBOX INBOX/bar Possible, that *lda*_save_to_detail_mailbox is simply not implemented? Thanks, Andreas

2 2

"maildir_empty_new = yes" not working
by Nikola Derikonjic 04 Dec '14

04 Dec '14

I need for my dovecot-uidlist to be updated with next id when new email arrives (moved from new/ to cur/). This only happens now when I check for new email with my client. Setting maildir_empty_new = yes is not working. Do I have to uncomment something else as well maybe? I want to do some proemial pipe lets say for 10 emails. All of them will have same UID since dovecot-uidlist is not updated. I am suing 2.2.13 dovecot on Gentoo 64bit. This is my dovecot -n: # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.16.5-gentoo x86_64 Gentoo Base System release 2.2 auth_mechanisms = plain login digest-md5 first_valid_gid = 500 last_valid_gid = 2000 last_valid_uid = 2000 login_greeting = Santa server is ready. mail_gid = vmail mail_location = /var/vmail/%d/%n/:INDEX=/var/vmail/%d/%n/indexes mail_uid = vmail maildir_empty_new = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave duplicate namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } service auth-worker { user = vmail } 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 lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } ssl_ca = </etc/ssl/dovecot/server.in.crt ssl_cert = </etc/ssl/dovecot/server.csr.rapid ssl_key = </etc/ssl/dovecot/server.key.rapid ssl_key_password = notshown userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } -- Nikola Derikonjic Sent with Sparrow (http://www.sparrowmailapp.com/?sig)

2 2

Manual (file system level) message deletion
by absolutely_free＠libero.it 04 Dec '14

04 Dec '14

Hi,I use Dovecot + Postfix on CentOS server. I use maildir. What happen if I manually delete some messages (eg. the ones older than 6 months) for every use?I think that dovecot's indexes will be wrong... is this a potential performance issue?If so, how can I "rebuild" index file for every user? Thank you

2 1

R: Re: R: Re: best file system ?
by absolutely_free＠libero.it 03 Dec '14

03 Dec '14

Thank you very much for your detailed explaination! >----Messaggio originale---- >Da: amateo(a)um.es >Data: 03/12/2014 8.13 >A: <dovecot(a)dovecot.org> >Ogg: Re: R: Re: best file system ? > >El 02/12/14 a las 16:38, absolutely_free(a)libero.it escribió: >> Hi Angel, >> can you please share your dovecot configuration? > > I have attached our doveconf -n output. We have two imap servers (with >the same configuration) and two more acting as proxy (with director) in >front of them. These last direct user request to their corresponding server. > > For storage we are using our SAN (a HP 3PAR 7400) connecting to it with >fibre channel. We have two XFS filesystems. One for mail indexes and the >other for user mailboxes and attachment files. > > In these servers we are running ubuntu 12.04 with kernel 3.4.0. > >> What webmail are you using (if any)? > > We are using horde. > >-- >Angel L. Mateo Martínez >Sección de Telemática >Área de Tecnologías de la Información >y las Comunicaciones Aplicadas (ATICA) >http://www.um.es/atica >Tfo: 868887590 >Fax: 868888337 >

1 0

incorrect column width for multi-byte characters by'doveadm -f table'
by Hardy Flor 03 Dec '14

03 Dec '14

In calculating the column width multi-byte characters (eg umlauts, utf8) not properly analyzed: Username mailbox messages guid sh_berger Spam 0 a7b32818c14e5b54bf5500006ad9a53c sh_berger Entwürfe 0 a4b32818c14e5b54bf5500006ad9a53c sh_berger Papierkorb 0 a6b32818c14e5b54bf5500006ad9a53c

1 0

Exporting plain_pass using passwd driver
by List 03 Dec '14

03 Dec '14

I am trying to get a postlogin script running that can see the plain_pass=%w while running the passwd driver. This is running Dovecot 2.0.7 and so far everything I have tried results in the value being empty.

1 0

R: Re: best file system ?
by absolutely_free＠libero.it 03 Dec '14

03 Dec '14

Hi Angel, can you please share your dovecot configuration? What webmail are you using (if any)? Thank you >----Messaggio originale---- >Da: amateo(a)um.es >Data: 02/12/2014 8.24 >A: <dovecot(a)dovecot.org> >Ogg: Re: best file system ? > >El 01/12/14 a las 18:45, Sami Ketola escribió: >> >>> On 01 Dec 2014, at 18:24, absolutely_free(a)libero.it wrote: >>> >>> Hi, >>> I'm going to set up a new storage for our email users (about 10k). >>> It's a network attached storage (Coraid). >>> In your opinion, what is the best file system for mail server (pop3/imap/webmail) purpose? >> >> Depends on what OS you have chosen, or if OS is not the limiter I would go with ZFS. >> > Have you any performance comparison with xfs? > > I'm running two imap servers. One with about 9k accounts and 3.5TB of >storage, and another with 55k accounts and 2TB of storage with XFS, and >I'm thinking about migrating them from XFS to ZFS but I'm concern about >IO performance of ZFS. When we developed these two servers, I remember >reading some zfs performance problems in comparison with xfs (I have >lost the link) and that was the reason to finally use xfs, but now we >are having problems with LVM snapshots and we also like some zfs >features (like replication) so we are thinking about the change. > > >-- >Angel L. Mateo Martínez >Sección de Telemática >Área de Tecnologías de la Información >y las Comunicaciones Aplicadas (ATICA) >http://www.um.es/atica >Tfo: 868887590 >Fax: 868888337 >

2 1

mail_location maildir:~/Maildir Invalid user settings[SOLVED]
by soko.tica 03 Dec '14

03 Dec '14

Hallo list, I was having quite a hard time configuring dovecot on OpenBSD -current. The problem was default Maildir setting in 10-mail.conf, namely: mail_location maildir:~/Maildir was unable to locate user's home directory. As far as I can remember, it was the correct setting on OpenBSD-current a week or two ago. Once I figured out and changed it to mail_location maildir:/path/to/home/%u/Maildir the problem was solved. Attached are dmesg, maillog and doveconf -n output.

2 1

Unknown scheme SSHA256.HEX.b64
by grundy 02 Dec '14

02 Dec '14

I'm getting a very strange error and I'm completely mystified by it. Thank you so much for taking a look! I recently migrated some users from another dovecot server to my own, and the previous admin had the passwords in their database using the SSHA256 scheme in HEX format. All the password hashes are in my database (MySQL) with a {SSHA256.HEX} prefix, and I thought at first that they were working fine, but then I checked my logs and am seeing this: localhost dovecot: auth: Error: password(***(a)***.***): Unknown scheme SSHA256.HEX.b64 (I have replaced the email address with asterisks) I am completely flabbergasted, as I can't imagine how "SSHA256.HEX.b64" is even coming in to existence as a string. I have triple checked the database and that combination appears nowhere in it. Does anybody have any idea how that is happening? Thanks again. -- View this message in context: http://dovecot.2317879.n4.nabble.com/Unknown-scheme-SSHA256-HEX-b64-tp50803… Sent from the Dovecot mailing list archive at Nabble.com.

2 1

disabling certain ciphers
by Will Yardley 02 Dec '14

02 Dec '14

Can you use both ssl_protocols *and* ssl_cipher_list in the same config (in a way that's sane)? ssl_protocols (>= 2.1) and ssl_cipher_list co-exist, or are they mutually exclusive? I have a Dovecot 2.2.13 system, and I tried setting: I also tried things like ssl_cipher_list = HIGH or ssl_cipher_list = HIGH:!MEDIUM:!LOW however, doing this seems to make v3 still work unless I explicitly do !SSLv3 in ssl_cipher_list in addition to disabling it in $ssl_protocols. This is different from Apache, which has similar parameters, but where disabling the protocol takes precedence. If I just do: ssl_protocols = !SSLv2 !SSLv3 I still get some ciphers that show up as "weak", e.g., | SSLv3: | ciphers: | TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA - strong | TLS_DHE_RSA_WITH_AES_128_CBC_SHA - strong | TLS_DHE_RSA_WITH_AES_256_CBC_SHA - strong | TLS_DHE_RSA_WITH_DES_CBC_SHA - weak [....] | TLS_RSA_WITH_DES_CBC_SHA - weak Is there a way to exclude these ciphers, while still keeping my config easy to parse and avoiding duplicative or deprecated configs? The behavior is also pretty strange; if I have something like one of the following, with or without $ssl_protocols set to exclude SSLv2 and SSLv3: ssl_cipher_list = HIGH:!MEDIUM:!LOW:!SSLv3 ssl_cipher_list = ALL:!ADH:!LOW:!SSLv2:!SSLv3:!EXP:!aNULL:+HIGH:!MEDIUM TLS v1.0 and v1.1 get disabled as well. I also can't seem to explicitly enable TLS 1.0 or 1.1 in $ssl_cipher_list. w

3 12