From fumiyas at osstech.jp Mon Sep 1 06:31:22 2014 From: fumiyas at osstech.jp (SATOH Fumiyasu) Date: Mon, 01 Sep 2014 15:31:22 +0900 Subject: Master user and non-plaintext auth does not work Message-ID: <87bnqz3l8l.wl-fumiyas@osstech.jp> Hi, I want to use CRAM-MD5 or DIGEST-MD5 (non-plaintext) authentication for master users, but Dovecot 2.2.13 rejects it with the following log: Sep 1 06:18:08 localhost dovecot: auth: passwd-file(masteruser,10.0.1.20,master,): Master user logging in as u0001 Sep 1 06:18:08 localhost dovecot: auth: cram-md5(u0001 at example.jp,10.0.1.20,): password mismatch Sep 1 06:18:10 localhost dovecot: imap-login: Disconnected (auth failed, 1 attempts in 2 secs): user=, method=CRAM-MD5, rip=10.0.1.20, lip=10.0.103.100, secured, session= PLAIN and LOGIN are OK: Sep 1 06:20:34 localhost dovecot: auth: passwd-file(masteruser,10.0.1.20,master,): Master user logging in as u0001 Sep 1 06:20:34 localhost dovecot: imap-login: Login: user=, method=PLAIN, rip=10.0.1.20, lip=10.0.103.100, mpid=23743, secured, session= Sep 1 06:20:34 localhost dovecot: imap(u0001 at example.jp): SpwmAPsBgwAKAAEU: Connection closed in=13 out=663 I have the following configuration in my dovecot.conf: auth_mechanisms = plain login cram-md5 digest-md5 disable_plaintext_auth = yes auth_master_user_separator = % passdb { driver = passwd-file args = /etc/dovecot/passwd.masterusers master = yes pass = yes } # don't work too #passdb { # driver = checkpassword # args = /opt/osstech/etc/dovecot/checkpassword.masterusers # master = yes # pass = yes #} passdb { driver = ldap args = /etc/dovecot/dovecot-ldap.conf.ext } Is this a bug or a restriction of Dovecot? -- -- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- GitHub Home: https://GitHub.com/fumiyas/ -- PGP Fingerprint: BBE1 A1C9 525A 292E 6729 CDEC ADC2 9DCA 5E1C CBCA From patrick at spamreducer.eu Mon Sep 1 07:33:52 2014 From: patrick at spamreducer.eu (Patrick De Zordo) Date: Mon, 1 Sep 2014 09:33:52 +0200 Subject: AW: Creating a backup of incoming mail In-Reply-To: <7E9AACF8-5101-4462-BD7B-8E86C8716A7A@kreme.com> References: <7E9AACF8-5101-4462-BD7B-8E86C8716A7A@kreme.com> Message-ID: <00ab01cfc5b7$140eb930$3c2c2b90$@spamreducer.eu> To backup all mail (incoming and outgoing), BCC all mails, you could do the following.. Add to your "/etc/postfix/main.cf" the following: ---8<------------------------------------------------------------------------------------- # Auto-Backup all mails transport_maps = hash:/etc/postfix/transport backuplmtp_destination_recipient_limit = 1 lmtp_destination_recipient_limit = 1 recipient_bcc_maps = pcre:/etc/postfix/backup_bcc.pcre sender_bcc_maps = pcre:/etc/postfix/backup_bcc.pcre ---8<------------------------------------------------------------------------------------- Create a domain called "backup.local" in postfixadmin or whatever you use to edit your accounts.. Add every domain for which you like to activate incoming backup to " /etc/postfix/backup_bcc.pcre": ---8<------------------------------------------------------------------------------------- /^(.*)@spamreducer\.eu$/ spamreducer.eu at backup.local ---8<------------------------------------------------------------------------------------- Add to your "/etc/postfix/master.cf" the following: ---8<------------------------------------------------------------------------------------- backuplmtp unix - - n - - lmtp ---8<------------------------------------------------------------------------------------- Add to your "/etc/postfix/transport" the following: ---8<------------------------------------------------------------------------------------- [backup.local] backuplmtp ---8<------------------------------------------------------------------------------------- Don't forget to issue " postmap /etc/postfix/transport".. For making folders based on "year/month" you have to use an appropriate sieve script. Give me a feedback! Bye! --------------------------------------------------------------------- Mit freundlichen Gr??en / Distinti saluti / Kind regards De Zordo Patrick patrick at spamreducer.eu > -----Urspr?ngliche Nachricht----- > Von: dovecot [mailto:dovecot-bounces at dovecot.org] Im Auftrag von > LuKreme > Gesendet: Samstag, 30. August 2014 18:26 > An: dovecot at dovecot.org > Betreff: Creating a backup of incoming mail > > This is my master.cf line for dovecot virtual users: > > dovecot unix - n n - - pipe flags=DRhu user=vpopmail:vchkpw > argv=/usr/local/libexec/dovecot/dovecot-lda -f ${sender} -d > ${user}@${nexthop} -m ${extension} > > I would like to also write every mail, before delivery to the user, to a backup > location like /backup/imap/mm/dd > > Possible? > > -- > 'On whose authority?' demanded Wert. Trymon turned his grey eyes on him. > 'Mine. I need no other.' --The Light Fantastic -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6229 bytes Desc: not available URL: From patrickdk at patrickdk.com Mon Sep 1 09:07:07 2014 From: patrickdk at patrickdk.com (Patrick Domack) Date: Mon, 01 Sep 2014 05:07:07 -0400 Subject: Master user and non-plaintext auth does not work In-Reply-To: <87bnqz3l8l.wl-fumiyas@osstech.jp> Message-ID: <20140901050707.Horde.SX-n2Imou7pLuPUTYHtOzw7@mail.patrickdk.com> Quoting SATOH Fumiyasu : > I want to use CRAM-MD5 or DIGEST-MD5 (non-plaintext) authentication > for master users, but Dovecot 2.2.13 rejects it with the following log: > > auth_mechanisms = plain login cram-md5 digest-md5 > disable_plaintext_auth = yes > auth_master_user_separator = % > > passdb { > driver = passwd-file > args = /etc/dovecot/passwd.masterusers > master = yes > pass = yes > } > > # don't work too > #passdb { > # driver = checkpassword > # args = /opt/osstech/etc/dovecot/checkpassword.masterusers > # master = yes > # pass = yes > #} > > passdb { > driver = ldap > args = /etc/dovecot/dovecot-ldap.conf.ext > } > > Is this a bug or a restriction of Dovecot? This is a restriction of CRAM-MD5 and DIGEST-MD5 They require plaintext passwords, you can't use password hashes on the server if you wish to use them. Or you have to use the special cram/digest-md5 password hash format. There is nothing really to be gained from using these formats, it's just better to require TLS. From arekm at maven.pl Mon Sep 1 09:14:06 2014 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Mon, 1 Sep 2014 11:14:06 +0200 Subject: dovecot 2.2.13: LMTP delivery with multiple recipients incorrectly mixes users Message-ID: <201409011114.06931.arekm@maven.pl> Hi. I'm using exim that delivers email over LMTP to dovecot 2.2.13. I noticed that dovecot LMTP service is sometimes (reare but repeats) mixing users. Example below. There is one mail (msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>) that is going to be delivered to multiple local recipients. Some recipients are delivered properly: Sep 1 05:40:33 host dovecot: lmtp(3176): Connect from local Sep 1 05:40:34 host dovecot: lmtp(3176, gbuser1): TDO+HNDpA1RoDAAA16XVAg: msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: saved mail to INBOX Sep 1 05:40:34 host dovecot: lmtp(3176, jpuser2): TDO+HNDpA1RoDAAA16XVAg: msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: saved mail to INBOX Sep 1 05:40:34 host dovecot: lmtp(3176, rkuser3): TDO+HNDpA1RoDAAA16XVAg: msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: saved mail to INBOX Sep 1 05:40:34 host dovecot: lmtp(3176, gbruser4): TDO+HNDpA1RoDAAA16XVAg: msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: saved mail to INBOX Sep 1 05:40:34 host dovecot: lmtp(3176, pbauser5): TDO+HNDpA1RoDAAA16XVAg: msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: saved mail to INBOX Sep 1 05:40:34 host dovecot: lmtp(3176, mwauser6): TDO+HNDpA1RoDAAA16XVAg: msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: saved mail to INBOX Sep 1 05:40:34 host dovecot: lmtp(3176, mdyuser7): TDO+HNDpA1RoDAAA16XVAg: msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: saved mail to INBOX but some are not: Sep 1 05:40:34 host dovecot: lmtp(3176, lkrzyuser8): Error: lstat(/var/lib/dovecot/control/gbuser1/.INBOX/dovecot-uidlist.lock) failed: Permission denied Sep 1 05:40:34 host dovecot: lmtp(3176, lkrzyuser8): Error: file_dotlock_create(/var/lib/dovecot/control/gbuser1/.INBOX/dovecot-uidlist) failed: Permission denied (euid=28371() egid=17373() missing +x perm: /var/lib/dovecot/control/gbuser1, dir owned by 67593:17373 mode=0700) Notice it was trying to deliver to user "lkrzyuser8" but it tries to access some other user files (dovecot-uidlist). euid=28371 is indeed "lkrzyuser8" but why it tries to access "gbuser1" files? Sep 1 05:40:34 host dovecot: lmtp(3176, lkrzyuser8): Error: lstat(/var/lib/dovecot/control/gbuser1/.INBOX/dovecot-uidlist.lock) failed: Permission denied Sep 1 05:40:34 host dovecot: lmtp(3176, lkrzyuser8): Error: file_dotlock_create(/var/lib/dovecot/control/gbuser1/.INBOX/dovecot-uidlist) failed: Permission denied (euid=28371() egid=17373() missing +x perm: /var/lib/dovecot/control/gbuser1, dir owned by 67593:17373 mode=0700) Sep 1 05:40:34 host dovecot: lmtp(3176, lkrzyuser8): TDO+HNDpA1RoDAAA16XVAg: msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: save failed to INBOX: BUG: Unknown internal error Above is again the same case. Sep 1 05:40:34 host dovecot: lmtp(3176, wm1user9): Error: lstat(/var/lib/dovecot/control/gbuser1/.INBOX/dovecot-uidlist.lock) failed: Permission denied Sep 1 05:40:34 host dovecot: lmtp(3176, wm1user9): Error: file_dotlock_create(/var/lib/dovecot/control/gbuser1/.INBOX/dovecot-uidlist) failed: Permission denied (euid=128065() egid=17373() missing +x perm: /var/lib/dovecot/control/gbuser1, dir owned by 67593:17373 mode=0700) Sep 1 05:40:34 host dovecot: lmtp(3176, wm1user9): Error: lstat(/var/lib/dovecot/control/gbuser1/.INBOX/dovecot-uidlist.lock) failed: Permission denied Sep 1 05:40:34 host dovecot: lmtp(3176, wm1user9): Error: file_dotlock_create(/var/lib/dovecot/control/gbuser1/.INBOX/dovecot-uidlist) failed: Permission denied (euid=128065() egid=17373() missing +x perm: /var/lib/dovecot/control/gbuser1, dir owned by 67593:17373 mode=0700) Sep 1 05:40:34 host dovecot: lmtp(3176, wm1user9): TDO+HNDpA1RoDAAA16XVAg: msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: save failed to INBOX: BUG: Unknown internal error And here again the same problem but with user "wm1user9" Sep 1 05:40:34 host dovecot: lmtp(3176): Disconnect from local: Successful quit # doveadm user gbuser1 field value uid 67593 gid 17373 home /var/mail/gbuser1/ mail maildir:/var/mail/gbuser1/:CONTROL=/var/lib/dovecot/control/gbuser1 # doveadm user lkrzyuser8 field value uid 28371 gid 17373 home /var/mail/lkrzyuser8/ mail maildir:/var/mail/lkrzyuser8/:CONTROL=/var/lib/dovecot/control/lkrzyuser8 # doveadm user wm1user9 field value uid 128065 gid 17373 home /var/mail/wm1user9/ mail maildir:/var/mail/wm1user9/:CONTROL=/var/lib/dovecot/control/wm1user9 Later exim retries delivery and dovecot lmtp succeeds: Sep 1 05:41:34 host dovecot: lmtp(4737): Connect from local Sep 1 05:41:34 host dovecot: lmtp(4737, lkrzyuser8): b9F+OsHqA1SBEgAA16XVAg: msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: saved mail to INBOX Sep 1 05:41:34 host dovecot: lmtp(4737, wm1user9): b9F+OsHqA1SBEgAA16XVAg: msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: saved mail to INBOX Sep 1 05:41:34 host dovecot: lmtp(4737): Disconnect from local: Successful quit The problem is not reasily repeatable. It happens several times a day for different users each time (while thousands users are logging in), so I guess some race condition takes place. # dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf doveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (8000) doveconf: Warning: service anvil { client_limit=1000 } is lower than required under max. load (6003) # OS: Linux 3.14.17-1 x86_64 xfs auth_mechanisms = plain login auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@= auth_username_translation = @= auth_verbose = yes default_process_limit = 2000 default_vsz_limit = 512 M disable_plaintext_auth = no first_valid_gid = 1500 first_valid_uid = 1500 lda_mailbox_autocreate = yes lmtp_save_to_detail_mailbox = yes login_greeting = Mail server ready. mail_location = maildir:/var/mail/%Ln:CONTROL=/var/lib/dovecot/control/%Ln mail_log_prefix = "%s(%u): session=<%{session}>, " mail_plugins = zlib quota namespace { hidden = no inbox = yes location = prefix = INBOX. separator = . type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename quota = fs:User quota:user quota2 = fs:Group quota:group } postmaster_address = postmaster at somwehere.pl service auth { unix_listener auth-userdb { mode = 0666 } } service imap { process_limit = 2048 } service pop3 { process_limit = 1024 } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lmtp { auth_username_format = %Ln auth_username_translation = } protocol imap { imap_logout_format = bytes=%i/%o mail_max_userip_connections = 20 mail_plugins = zlib quota imap_quota mail_log notify } protocol pop3 { mail_max_userip_connections = 20 mail_plugins = mail_log notify pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s, bytes=%i/%o pop3_uidl_format = %Mf } -- Arkadiusz Mi?kiewicz, arekm / maven.pl From fumiyas at osstech.jp Mon Sep 1 10:12:26 2014 From: fumiyas at osstech.jp (SATOH Fumiyasu) Date: Mon, 01 Sep 2014 19:12:26 +0900 Subject: Master user and non-plaintext auth does not work In-Reply-To: <20140901050707.Horde.SX-n2Imou7pLuPUTYHtOzw7@mail.patrickdk.com> References: <87bnqz3l8l.wl-fumiyas@osstech.jp> <20140901050707.Horde.SX-n2Imou7pLuPUTYHtOzw7@mail.patrickdk.com> Message-ID: <87a96j3b05.wl-fumiyas@osstech.jp> Hi, At Mon, 01 Sep 2014 05:07:07 -0400, Patrick Domack wrote: > > I want to use CRAM-MD5 or DIGEST-MD5 (non-plaintext) authentication > > for master users, but Dovecot 2.2.13 rejects it with the following log: > > > > auth_mechanisms = plain login cram-md5 digest-md5 > > disable_plaintext_auth = yes > > auth_master_user_separator = % > > > > passdb { > > driver = passwd-file > > args = /etc/dovecot/passwd.masterusers > > master = yes > > pass = yes > > } > > > > # don't work too > > #passdb { > > # driver = checkpassword > > # args = /opt/osstech/etc/dovecot/checkpassword.masterusers > > # master = yes > > # pass = yes > > #} > > > > passdb { > > driver = ldap > > args = /etc/dovecot/dovecot-ldap.conf.ext > > } > > > > Is this a bug or a restriction of Dovecot? > > This is a restriction of CRAM-MD5 and DIGEST-MD5 > They require plaintext passwords, you can't use password hashes on the server if you wish to use them. Or you have to use the special cram/digest-md5 password hash format. I have plaintext passwords in the master passdb. Dovecot debug log with auth_debug=yes and auth_debug_passwords=yes seems that the master's plaintext password (masterpass) from the master passdb is overrided by user's password (userpass) from the passdb: Sep 01 09:49:26 auth: Debug: client in: AUTH 3 CRAM-MD5 service=imap secured no-penalty session=1hIb6/0BXwAKAAEU lip=10.0.103.100 rip=10.0.1.20 lport=143 rport=40031 Sep 01 09:49:26 auth: Debug: client passdb out: CONT 3 PDk0NDAwNTk4NzgwNzM5MzUuMTQwOTU2NDk2NkBsb2NhbGhvc3QubG9jYWxkb21haW4+ Sep 01 09:49:26 auth: Debug: client in: CONT 3 dTAwMDJAZWR1LnR1dC5hYy5qcCVzaGliYm8gYjk1NWUwODliZDQxMDE2N2NkNGI3ZWRlMjE1ODk2N2U= (previous base64 data may contain sensitive data) Sep 01 09:49:26 auth: Debug: passwd-file(masteruser,10.0.1.20,master,<1hIb6/0BXwAKAAEU>): Master user lookup for login: u0001 at example.jp Sep 01 09:49:26 auth: Debug: passwd-file(masteruser,10.0.1.20,master,<1hIb6/0BXwAKAAEU>): lookup: user=masteruser file=/etc/dovecot/passwd.masterusers Sep 01 09:49:26 auth: Debug: passwd-file(masteruser,10.0.1.20,master,<1hIb6/0BXwAKAAEU>): Generating CRAM-MD5 from user 'masteruser', password 'masterpass' Sep 01 09:49:26 auth: Debug: ldap(u0001 at example.jp,10.0.1.20,<1hIb6/0BXwAKAAEU>): pass search: base=ou=users,dc=edu,dc=tut,dc=ac,dc=jp scope=subtree filter=(uid=u0001) fields=personMailCanonicalAddress,personMailPassword Sep 01 09:49:26 auth: Debug: ldap(u0001 at example.jp,10.0.1.20,<1hIb6/0BXwAKAAEU>): result: personMailCanonicalAddress=u0001 at example.jp personMailPassword=userpass; personMailPassword,personMailCanonicalAddress unused Sep 01 09:49:26 auth: Debug: ldap(u0001 at example.jp,10.0.1.20,<1hIb6/0BXwAKAAEU>): result: personMailCanonicalAddress=u0001 at example.jp personMailPassword=userpass Sep 01 09:49:26 auth: Debug: ldap(u0001 at example.jp,10.0.1.20,<1hIb6/0BXwAKAAEU>): Generating CRAM-MD5 from user 'masteruser', password 'userpass' Sep 01 09:49:26 auth: Debug: ldap(u0001 at example.jp,10.0.1.20,<1hIb6/0BXwAKAAEU>): Credentials: ff5d74b19e3cb9b2b9f4fcb548fe023aeb44f67f231a5a89714d08b5fec22b78 Sep 01 09:49:28 auth: Debug: client passdb out: FAIL 3 user=u0001 at example.jp authz original_user=masteruser auth_user=masteruser > There is nothing really to be gained from using these formats, it's just better to require TLS. I need CRAM-MD5 and DIGEST-MD5 authentication for clients. Thanks. -- -- Name: SATOH Fumiyasu @ OSS Technology Corp. (fumiyas @ osstech co jp) -- Business Home: http://www.OSSTech.co.jp/ -- GitHub Home: https://GitHub.com/fumiyas/ -- PGP Fingerprint: BBE1 A1C9 525A 292E 6729 CDEC ADC2 9DCA 5E1C CBCA From mehmet at atifceylan.com Mon Sep 1 12:41:46 2014 From: mehmet at atifceylan.com (=?UTF-8?B?QXTEsWYgQ0VZTEFO?=) Date: Mon, 01 Sep 2014 15:41:46 +0300 Subject: dsync full sync Message-ID: <5404698A.10605@atifceylan.com> Hi all, I have 2 question. First: I use dovecot (version 2.2.9) with mdbox mail format. When I run dsync tool with "mirror" or "backup" parameters my source and destination directory synchronize correctly but if I delete some messages in user mailbox, deleted messages does not synced to destination. For example : atif at domain.com path is /mail/domain.com/atif/ and its size is 1GB. after first running the "dsync -u atif at domain.com backup mdbox:/backup/domain.com/atif/" command, size of "/backup/domain.com/atif/" is 1GB I deleted 300mb messages in atif mailbox then /mail/domain.com/atif/ is decreased to 700MB and I launched dsync command again. But /backup/domain.com/atif/ is not decreased to 700Mb. My backup directory still 1GB . I tried dsync with "-f , backup, mirror" parameters. Second problem, the first time the backup atif's quota size is increasing to x2. before backup : atif at domain.com quota size 1GB after backup: atif at domain.com quota size 2GB so I must run "doveadm quota recalc" command. Why? What is correct usage of mdbox mail format and dsync tool? -- M.At?f CEYLAN From francesco.fiore at babel.it Mon Sep 1 13:27:44 2014 From: francesco.fiore at babel.it (Francesco Fiore) Date: Mon, 01 Sep 2014 15:27:44 +0200 Subject: Escape comma in the LDAP passdb subquery configuration Message-ID: <54047450.9040702@babel.it> Hi I have to configure the LDAP passdb to execute a subquery defining dinamically the new DN to use. For example: pass_attrs = @mail=mail=%{login_user},dc=%{login_domain},dc=example,dc=com,\ =proxy=y,\ =host=%{ldap:mailHost at mail} In the previous example, the problem is the use of "," for DN representation, which is also the separator for the attribute template in the pass_attr parameter value. I tried to escape it with '\' or '%' but it doesn't work. Dovecot version is 2.2.13. How can I resolve this issue? Thanks in advance From kremels at kreme.com Mon Sep 1 16:20:42 2014 From: kremels at kreme.com (LuKreme) Date: Mon, 1 Sep 2014 10:20:42 -0600 Subject: Creating a backup of incoming mail In-Reply-To: <00ab01cfc5b7$140eb930$3c2c2b90$@spamreducer.eu> References: <7E9AACF8-5101-4462-BD7B-8E86C8716A7A@kreme.com> <00ab01cfc5b7$140eb930$3c2c2b90$@spamreducer.eu> Message-ID: On 01 Sep 2014, at 01:33 , Patrick De Zordo wrote: > To backup all mail (incoming and outgoing), BCC all mails, you could do the following.. > > Add to your "/etc/postfix/main.cf" the following: > ---8<------------------------------------------------------------------------------------- > # Auto-Backup all mails > transport_maps = hash:/etc/postfix/transport > backuplmtp_destination_recipient_limit = 1 > lmtp_destination_recipient_limit = 1 > recipient_bcc_maps = pcre:/etc/postfix/backup_bcc.pcre > sender_bcc_maps = pcre:/etc/postfix/backup_bcc.pcre > ---8<------------------------------------------------------------------------------------- > > Create a domain called "backup.local" in postfixadmin or whatever you use to edit your accounts.. > > Add every domain for which you like to activate incoming backup to " /etc/postfix/backup_bcc.pcre": > ---8<------------------------------------------------------------------------------------- > /^(.*)@spamreducer\.eu$/ spamreducer.eu at backup.local > ---8<------------------------------------------------------------------------------------- > > Add to your "/etc/postfix/master.cf" the following: > ---8<------------------------------------------------------------------------------------- > backuplmtp unix - - n - - lmtp > ---8<------------------------------------------------------------------------------------- > > Add to your "/etc/postfix/transport" the following: > ---8<------------------------------------------------------------------------------------- > [backup.local] backuplmtp > ---8<------------------------------------------------------------------------------------- > > Don't forget to issue " postmap /etc/postfix/transport".. > > For making folders based on "year/month" you have to use an appropriate sieve script. > > Give me a feedback! Wow, that is a whole lot more work that what I did with procmail which was practically one line in the /usr/locale/etc/procmailrc right at the top. YER=`date %Y` MON=`date %m` :0c /backup/mail/$YER/$MON/ I'll start with Sieve (though I still haven't used it) and see what that can do, but this at least I can do, if sieve proves too annoying to get going. -- Granny Weatherwax didn't hold with looking at the future, but now she could feel the future looking at her. She didn't like its expression at all. From kremels at kreme.com Mon Sep 1 16:46:58 2014 From: kremels at kreme.com (LuKreme) Date: Mon, 1 Sep 2014 10:46:58 -0600 Subject: Creating a backup of incoming mail In-Reply-To: <5401FCF2.4000006@mie.utoronto.ca> References: <7E9AACF8-5101-4462-BD7B-8E86C8716A7A@kreme.com> <5401FCF2.4000006@mie.utoronto.ca> Message-ID: On 30 Aug 2014, at 10:33 , Oscar del Rio wrote: > You could use a global "sieve_before" filter. > > http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration And, I get hampered on the very first step: To use Sieve, you will first need to make sure you are using Dovecot LDA or LMTP for delivering incoming mail to users' mailboxes. Then, you need to enable the Pigeonhole Sieve plugin in your configuration: protocol lda { mail_plugins = $mail_plugins sieve } OK, so I am using dovecot-lda via postfix/master.cf, but in my configuration I have a section tagged protocols, not protocol. Don't know if this is the same thing, or a slightly different thing. I don't know where/what $mail_plugins refers to, and there is no "plugins" section of my configuration file. In fact, the string "plug" doesn't appear in dovecot.conf (there are some commented lines for mail_plugins in conf.d/ files). Then, sieve_global_path is deprecated, but despite being tagged as deprecated, the example config uses the sieve_global_path. Shouldn't the example use sieve_default? Looks like further down is the sieve_before, but really, the documentation feels almost like it has set out with the intention of being as obtuse as possible. If I understand it, and I am sure I do not, what I need to add in to dovecot.conf is something like this: protocol lda { mail_plugins = $mail_plugins sieve } (which is separate and unrelated to my "protocols = imap" existing line in dovecot.conf) plugin { sieve = ~/.dovecot.sieve sieve_before = /var/lib/dovecot/sieve/archive.sieve } And then in archive.sieve I find out what the commands are to write a COPY of the mail to a location after getting the date info. require ["variables","date","fileinto","mailbox"]; if currentdate :matches "year" "*" { set "year" "${1}"; } if currentdate :matches "month" "*" { set "month" "${1}"; } And a command like this, but not this, since i wan the backup stores in an absolute path outside the IMAP store and I obviously only want a copy of that message. fileinto :create "INBOX.Lists.${year}.${month}.dovecot"; } -- Did they get you to trade your heroes for ghosts? Hot ashes for trees? Hot air for a cool breeze? Cold comfort for change? From webster.liang at gmail.com Tue Sep 2 02:50:32 2014 From: webster.liang at gmail.com (Webster Liang) Date: Mon, 1 Sep 2014 19:50:32 -0700 (PDT) Subject: How to setup a dovecot lmtp proxy server ? Message-ID: <1409626232085-49553.post@n4.nabble.com> Dear All : I want to setup a dovecot lmtp proxy server , my target as below : Postfix (lmtp) -->dovecot lmtp proxy servers-->dovecot backend servers but i don't know how to setup the dovecot lmtp proxy server , who can help me ? thanks a lot . -- View this message in context: http://dovecot.2317879.n4.nabble.com/How-to-setup-a-dovecot-lmtp-proxy-server-tp49553.html Sent from the Dovecot mailing list archive at Nabble.com. From patrick at spamreducer.eu Tue Sep 2 07:06:47 2014 From: patrick at spamreducer.eu (Patrick De Zordo) Date: Tue, 2 Sep 2014 09:06:47 +0200 Subject: AW: Creating a backup of incoming mail In-Reply-To: References: <7E9AACF8-5101-4462-BD7B-8E86C8716A7A@kreme.com> <5401FCF2.4000006@mie.utoronto.ca> Message-ID: <006801cfc67c$75fe05e0$61fa11a0$@spamreducer.eu> Well, I'll give you some configuration hints.. 1. don't forget to install sieve (eg. "apt-get install dovecot-sieve").. 2. Add to "postfix/main.cf" the following lines: ---8<-------------------------------------------------------------------------------- # Tell postfix to hand off mail to the definition for dovecot in master.cf virtual_transport = dovecot dovecot_destination_recipient_limit = 1 ---8<-------------------------------------------------------------------------------- 3. In "postfix/master.cf": ---8<-------------------------------------------------------------------------------- # Integration with Dovecot - hand mail over to it for local delivery, and # run the process under the vmail user and mail group. dovecot unix - n n - - pipe flags=DRhu user=vmail:mail argv=/usr/lib/dovecot/dovecot-lda -d $(recipient) ---8<-------------------------------------------------------------------------------- 4. add "$mail_plugins sieve" to "dovecot/conf.d/15-lda.conf" That?s all! Then just provide the sieve scripts at location specified in "dovecot/conf.d/90-sieve.conf" and you are done! Good luck! Bye! --------------------------------------------------------------------- Mit freundlichen Gr??en / Distinti saluti / Kind regards De Zordo Patrick patrick at spamreducer.eu > -----Urspr?ngliche Nachricht----- > Von: dovecot [mailto:dovecot-bounces at dovecot.org] Im Auftrag von > LuKreme > Gesendet: Montag, 1. September 2014 18:47 > An: dovecot at dovecot.org > Betreff: Re: Creating a backup of incoming mail > > > On 30 Aug 2014, at 10:33 , Oscar del Rio wrote: > > > You could use a global "sieve_before" filter. > > > > http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration > > And, I get hampered on the very first step: > > To use Sieve, you will first need to make sure you are using Dovecot LDA or > LMTP for delivering incoming mail to users' mailboxes. Then, you need to > enable the Pigeonhole Sieve plugin in your configuration: > > protocol lda { > mail_plugins = $mail_plugins sieve > } > > OK, so I am using dovecot-lda via postfix/master.cf, but in my configuration I > have a section tagged protocols, not protocol. > > Don't know if this is the same thing, or a slightly different thing. I don't know > where/what $mail_plugins refers to, and there is no "plugins" section of my > configuration file. In fact, the string "plug" doesn't appear in dovecot.conf > (there are some commented lines for mail_plugins in conf.d/ files). > > Then, sieve_global_path is deprecated, but despite being tagged as > deprecated, the example config uses the sieve_global_path. Shouldn't the > example use sieve_default? > > Looks like further down is the sieve_before, but really, the documentation > feels almost like it has set out with the intention of being as obtuse as > possible. > > If I understand it, and I am sure I do not, what I need to add in to > dovecot.conf is something like this: > > protocol lda { > mail_plugins = $mail_plugins sieve > } > > (which is separate and unrelated to my "protocols = imap" existing line in > dovecot.conf) > > plugin { > sieve = ~/.dovecot.sieve > sieve_before = /var/lib/dovecot/sieve/archive.sieve > } > > And then in archive.sieve I find out what the commands are to write a COPY > of the mail to a location after getting the date info. > > require ["variables","date","fileinto","mailbox"]; > > if currentdate :matches "year" "*" { set "year" "${1}"; } if currentdate > :matches "month" "*" { set "month" "${1}"; } > > And a command like this, but not this, since i wan the backup stores in an > absolute path outside the IMAP store and I obviously only want a copy of > that message. > > fileinto :create "INBOX.Lists.${year}.${month}.dovecot"; > } > > -- > Did they get you to trade your heroes for ghosts? Hot ashes for trees? > Hot air for a cool breeze? Cold comfort for change? -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6229 bytes Desc: not available URL: From rs at sys4.de Tue Sep 2 07:26:36 2014 From: rs at sys4.de (Robert Schetterer) Date: Tue, 02 Sep 2014 09:26:36 +0200 Subject: Creating a backup of incoming mail In-Reply-To: References: <7E9AACF8-5101-4462-BD7B-8E86C8716A7A@kreme.com> <00ab01cfc5b7$140eb930$3c2c2b90$@spamreducer.eu> Message-ID: <5405712C.5030408@sys4.de> Am 01.09.2014 um 18:20 schrieb LuKreme: > > On 01 Sep 2014, at 01:33 , Patrick De Zordo wrote: > >> To backup all mail (incoming and outgoing), BCC all mails, you could do the following.. >> >> Add to your "/etc/postfix/main.cf" the following: >> ---8<------------------------------------------------------------------------------------- >> # Auto-Backup all mails >> transport_maps = hash:/etc/postfix/transport >> backuplmtp_destination_recipient_limit = 1 >> lmtp_destination_recipient_limit = 1 >> recipient_bcc_maps = pcre:/etc/postfix/backup_bcc.pcre >> sender_bcc_maps = pcre:/etc/postfix/backup_bcc.pcre >> ---8<------------------------------------------------------------------------------------- >> >> Create a domain called "backup.local" in postfixadmin or whatever you use to edit your accounts.. >> >> Add every domain for which you like to activate incoming backup to " /etc/postfix/backup_bcc.pcre": >> ---8<------------------------------------------------------------------------------------- >> /^(.*)@spamreducer\.eu$/ spamreducer.eu at backup.local >> ---8<------------------------------------------------------------------------------------- >> >> Add to your "/etc/postfix/master.cf" the following: >> ---8<------------------------------------------------------------------------------------- >> backuplmtp unix - - n - - lmtp >> ---8<------------------------------------------------------------------------------------- >> >> Add to your "/etc/postfix/transport" the following: >> ---8<------------------------------------------------------------------------------------- >> [backup.local] backuplmtp >> ---8<------------------------------------------------------------------------------------- >> >> Don't forget to issue " postmap /etc/postfix/transport".. >> >> For making folders based on "year/month" you have to use an appropriate sieve script. >> >> Give me a feedback! > > Wow, that is a whole lot more work that what I did with procmail which was practically one line in the /usr/locale/etc/procmailrc right at the top. > > YER=`date %Y` > MON=`date %m` > > :0c > /backup/mail/$YER/$MON/ see https://sys4.de/de/blog/2013/02/07/mailarchiv-mit-dovecot-und-postfix-sortiert-nach-datum-mailadressen-und-ein-ausgehend-unterordnern/ sorry german with listescape plugin enabled something like require ["reject","variables","date","fileinto","mailbox","envelope","subaddress","regex","copy","include"]; # Extract date info if currentdate :matches "year" "*" { set "year" "${1}"; } if currentdate :matches "month" "*" { set "month" "${1}"; } if currentdate :matches "day" "*" { set "day" "${1}"; } if envelope :detail :matches "to" "*" { set :lower "to" "${1}"; } if true { if header :contains "Return-Path" "${to}@domain.de" { fileinto :create "user-backup/${year}/${month}/${day}/${to}/out";} else { fileinto :create "user-backup/${year}/${month}/${day}/${to}/in";} stop; } > > I'll start with Sieve (though I still haven't used it) and see what that can do, but this at least I can do, if sieve proves too annoying to get going. > Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From jogi at mur.at Tue Sep 2 12:26:18 2014 From: jogi at mur.at (=?UTF-8?B?Sm9naSBIb2Ztw7xsbGVy?=) Date: Tue, 02 Sep 2014 14:26:18 +0200 Subject: quota for subfolder with prefix=INBOX. In-Reply-To: <54005640.1060104@mur.at> References: <54005640.1060104@mur.at> Message-ID: <5405B76A.6060201@mur.at> Hi all, Since I did not manage to get quota for individual subfolders working I tried toying with quota_grace, which also does not work for me :( My approach was this: plugin { quota = maildir:User quota quota_grace = 20%% quota_rule = *:storage=5M } I expected normal delivery of email when user is at 103% quota but the new email (even tiny ones with less than 1K) get's rejected with reason 'over quota'. Is this what dovecot is supposed to do or did I do something wrong? Regards, -- j.hofm?ller We are all idiots with deadlines. - Mike West -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: OpenPGP digital signature URL: From bourek at thinline.cz Tue Sep 2 13:26:35 2014 From: bourek at thinline.cz (Jiri Bourek) Date: Tue, 02 Sep 2014 15:26:35 +0200 Subject: quota for subfolder with prefix=INBOX. In-Reply-To: <5405B76A.6060201@mur.at> References: <54005640.1060104@mur.at> <5405B76A.6060201@mur.at> Message-ID: <5405C58B.2020809@thinline.cz> On 2.9.2014 14:26, Jogi Hofm?ller wrote: > Hi all, > > Since I did not manage to get quota for individual subfolders working I > tried toying with quota_grace, which also does not work for me :( My > approach was this: > > plugin { > quota = maildir:User quota > quota_grace = 20%% > quota_rule = *:storage=5M > > } > > I expected normal delivery of email when user is at 103% quota but the > new email (even tiny ones with less than 1K) get's rejected with reason > 'over quota'. Is this what dovecot is supposed to do or did I do > something wrong? > > Regards, > I think your question is answered by first sentence in http://wiki2.dovecot.org/Quota/Configuration#Quota_grace From mine at michi.su Tue Sep 2 13:59:56 2014 From: mine at michi.su (Michael) Date: Tue, 02 Sep 2014 13:59:56 +0000 Subject: Dovecot is looking for .dovecot.lda-dupes in the wrong place Message-ID: <20140902135956.Horde.EVeVlRk68Sn5bkAP8DhZ0w5@webmail.neurohr.at> Hi, I just moved the dovecot maildir location for all virtual users to another location. I moved everything from /var/mail/vhosts/%d/%n to /var/vmail/%d/%n/maildir Everything seem to be fine except of one recurring error: Sep 2 10:16:09 mx0 dovecot: lmtp(13226, sv_bogies at neurohr.at): Error: file_dotlock_open(/var/mail/vhosts/domain.at/michael/.dovecot.lda-dupes) failed: No such file or directory Sep 2 13:31:27 mx0 dovecot: lmtp(16248, sv_bogies at neurohr.at): Error: file_dotlock_open(/var/mail/vhosts/domain.at/michael/.dovecot.lda-dupes) failed: No such file or directory So Dovecot is looking in the old path. How can I fix that? Thanks, Michael doveconf -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-35-generic x86_64 Ubuntu 14.04.1 LTS ext4 auth_mechanisms = plain login mail_location = maildir:/var/vmail/%d/%n/maildir mail_plugins = notify acl quota mail_privileged_group = vmail mail_shared_explicit_inbox = 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 imapflags namespace { list = children location = maildir:/var/vmail/%%d/%%n/maildir:INDEX=/var/vmail/%d/%n/maildir/shared/%%u prefix = shared/%%u/ separator = / subscriptions = no type = shared } 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 Spam { auto = subscribe special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } plugin { acl = vfile acl_shared_dict = file:/var/lib/dovecot/db/shared-mailboxes.db antispam_allow_append_to_spam = yes antispam_backend = pipe antispam_pipe_program = /usr/sbin/sendmail antispam_pipe_program_args = -i;-f;%u antispam_pipe_program_notspam_arg = sh antispam_pipe_program_spam_arg = sm antispam_spam = Spam antispam_trash = trash;Trash;Deleted Items;Deleted Messages fts_autoindex = yes quota = maildir:User quota quota_rule = *:storage=9G quota_rule2 = Trash:storage=+100M sieve = /var/vmail/%d/%n/sieve-scripts/.dovecot.sieve sieve_before = /var/vmail/sieve-scripts/before sieve_dir = /var/vmail/%d/%n/sieve-scripts/sieve sieve_extensions = +imapflags } postmaster_address = postmaster at neurohr.at protocols = " imap lmtp sieve pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { mode = 0666 user = vmail } } service dict { unix_listener dict { user = vmail } } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocol lmtp { mail_plugins = sieve } protocol lda { mail_plugins = sieve } protocol imap { mail_max_userip_connections = 20 mail_plugins = notify acl quota imap_acl imap_quota antispam } From jogi at mur.at Tue Sep 2 15:52:22 2014 From: jogi at mur.at (=?UTF-8?B?Sm9naSBIb2Ztw7xsbGVy?=) Date: Tue, 02 Sep 2014 17:52:22 +0200 Subject: quota for subfolder with prefix=INBOX. In-Reply-To: <5405C58B.2020809@thinline.cz> References: <54005640.1060104@mur.at> <5405B76A.6060201@mur.at> <5405C58B.2020809@thinline.cz> Message-ID: <5405E7B6.7080000@mur.at> Hi, Am 2014-09-02 15:26, schrieb Jiri Bourek: > I think your question is answered by first sentence in > http://wiki2.dovecot.org/Quota/Configuration#Quota_grace I guess I totally misunderstood the quota_grace option then. To be clear: if the last mail brings the user just 1% over quota it doesn't matter that I e.g. set quota_grace = 10 %% because every further email will just be denied. Too bad the extended quota for subfolders don't work in our setup (see my initial email). Cheers, -- J.Hofm?ller Nisiti - Abie Nathan, 1927-2008 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: OpenPGP digital signature URL: From listas at adminlinux.com.br Tue Sep 2 18:03:13 2014 From: listas at adminlinux.com.br (Listas@Adminlinux) Date: Tue, 02 Sep 2014 15:03:13 -0300 Subject: dsync-server couldn't create .dovecot-sync.lock file Message-ID: <54060661.2010000@adminlinux.com.br> My dovecot stores users' emails on /var/spool/imap/ and stores the messages index on /var/lib/imap/. I have many users who do not yet have their userdb_home directories created on the server, because that is created at the time of first login. I'm testing dsync for replication and have seen the following error: dsync-server(): Error: Couldn't create lock /var/lib/imap//.dovecot-sync.lock: No such file or directory The /var/lib/imap/ directory does not exist yet and I think this is the cause. How can I avoid this error message? ================================================================================ root at myserver2:/root# doveconf -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-30-generic x86_64 Ubuntu 14.04.1 LTS auth_master_user_separator = * auth_mechanisms = plain login auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@= auth_worker_max_count = 1 disable_plaintext_auth = no doveadm_password = secret doveadm_port = 12345 listen = myserver2.mydomain.com log_path = /var/log/dovecot.log login_greeting = MAILBOX IMAP/POP3 server mail_fsync = never mail_gid = dovemail mail_plugins = " notify replication quota" mail_uid = dovemail passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = /etc/dovecot/dovecot-sql-master.conf.ext driver = sql master = yes pass = yes } plugin { mail_replica = tcp:myserver1.mydomain.com:12345 quota = dict:User quota::file:/var/lib/imap/%n/dovecot-quota quota_rule = *:storage=1GB } protocols = imap pop3 lmtp service auth-worker { user = $default_internal_user } service auth { client_limit = 1024 process_limit = 1 process_min_avail = 1 } service doveadm { inet_listener { port = 12345 } } service imap { process_limit = 1024 process_min_avail = 1 } service lmtp { inet_listener { address = myserver2.mydomain.com port = 24 } process_limit = 256 process_min_avail = 1 } service pop3-login { inet_listener pop3 { address = myserver2.mydomain.com port = 110 } } service pop3 { process_limit = 256 process_min_avail = 1 } service replicator { process_min_avail = 1 } ssl = no userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep imap_idle_notify_interval = 2 mins imap_max_line_length = 64 k mail_max_userip_connections = 50 mail_plugins = " notify replication quota imap_quota" } protocol lmtp { mail_fsync = optimized mail_plugins = " notify replication sieve quota" } protocol pop3 { mail_plugins = " notify replication quota" } ================================================================================ Thanks! -- Thiago Henrique From peter at tripleseven.us Tue Sep 2 19:12:37 2014 From: peter at tripleseven.us (Peter Cook) Date: Tue, 02 Sep 2014 14:12:37 -0500 Subject: Trouble viewing Inbox via IMAP Client Message-ID: <540616A5.8000704@tripleseven.us> Hello, I have been having trouble with this issue for quite some time now. Here is my environment: CentOS 6.5, Postfix built with PGSQL support, PFA, and dovecot. The problem I am having is that I can send and receive mail fine, but when I try to view my Inbox in an IMAP client like Thunderbird, I can only view sent mail and trash. Here is the result of my dovecot -- version and dovecot -n --version 2.0.9 dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.el6.x86_64 x86_64 CentOS release 6.5 (Final) ext4 auth_debug = yes auth_debug_passwords = yes disable_plaintext_auth = no mail_location = maildir:/var/mail/vmail/%d/%n/ mbox_write_locks = fcntl passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } passdb { driver = pam } protocols = imap pop3 service auth { group = postfix unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = postfix } ssl_cert = References: <54005640.1060104@mur.at> <5405B76A.6060201@mur.at> <5405C58B.2020809@thinline.cz> <5405E7B6.7080000@mur.at> Message-ID: <540622C6.6020005@thinline.cz> On 2.9.2014 17:52, Jogi Hofm?ller wrote: > Hi, > > Am 2014-09-02 15:26, schrieb Jiri Bourek: >> I think your question is answered by first sentence in >> http://wiki2.dovecot.org/Quota/Configuration#Quota_grace > > I guess I totally misunderstood the quota_grace option then. To be > clear: if the last mail brings the user just 1% over quota it doesn't > matter that I e.g. set quota_grace = 10 %% because every further email > will just be denied. > Yes. The grace value only protects the system from receiving huge last message. > Too bad the extended quota for subfolders don't work in our setup (see > my initial email). > > Cheers, > From kremels at kreme.com Tue Sep 2 22:14:54 2014 From: kremels at kreme.com (LuKreme) Date: Tue, 2 Sep 2014 16:14:54 -0600 Subject: Creating a backup of incoming mail In-Reply-To: <5405712C.5030408@sys4.de> References: <7E9AACF8-5101-4462-BD7B-8E86C8716A7A@kreme.com> <00ab01cfc5b7$140eb930$3c2c2b90$@spamreducer.eu> <5405712C.5030408@sys4.de> Message-ID: <6A582824-19A6-4DEE-BA05-3075C1A54994@kreme.com> On 02 Sep 2014, at 01:26 , Robert Schetterer wrote: > with listescape plugin enabled something like > > require > ["reject","variables","date","fileinto","mailbox","envelope","subaddress","regex","copy","include"]; > # Extract date info > if currentdate :matches "year" "*" { set "year" "${1}"; } > if currentdate :matches "month" "*" { set "month" "${1}"; } > if currentdate :matches "day" "*" { set "day" "${1}"; } > if envelope :detail :matches "to" "*" { set :lower "to" "${1}"; } > if true { > if header :contains "Return-Path" "${to}@domain.de" { fileinto :create > "user-backup/${year}/${month}/${day}/${to}/out";} > else { fileinto :create "user-backup/${year}/${month}/${day}/${to}/in";} > stop; > } Oh, thanks for that. I'd made very little progress in finding "fileinto :create" -- 'Pardon me for living, I'm sure.' NO-ONE GETS PARDONED FOR LIVING. From jost+lists at dimejo.at Wed Sep 3 11:17:42 2014 From: jost+lists at dimejo.at (Alex JOST) Date: Wed, 03 Sep 2014 13:17:42 +0200 Subject: Dovecot is looking for .dovecot.lda-dupes in the wrong place In-Reply-To: <20140902135956.Horde.EVeVlRk68Sn5bkAP8DhZ0w5@webmail.neurohr.at> References: <20140902135956.Horde.EVeVlRk68Sn5bkAP8DhZ0w5@webmail.neurohr.at> Message-ID: <5406F8D6.6010106@dimejo.at> Am 02.09.2014 um 15:59 schrieb Michael: > Hi, > I just moved the dovecot maildir location for all virtual users to > another location. > I moved everything from > /var/mail/vhosts/%d/%n > to > /var/vmail/%d/%n/maildir > > Everything seem to be fine except of one recurring error: > > Sep 2 10:16:09 mx0 dovecot: lmtp(13226, sv_bogies at neurohr.at): Error: > file_dotlock_open(/var/mail/vhosts/domain.at/michael/.dovecot.lda-dupes) > failed: No such file or directory > Sep 2 13:31:27 mx0 dovecot: lmtp(16248, sv_bogies at neurohr.at): Error: > file_dotlock_open(/var/mail/vhosts/domain.at/michael/.dovecot.lda-dupes) > failed: No such file or directory > > > So Dovecot is looking in the old path. How can I fix that? > mail_location = maildir:/var/vmail/%d/%n/maildir > passdb { > args = /etc/dovecot/dovecot-sql.conf > driver = sql > } > userdb { > args = /etc/dovecot/dovecot-sql.conf > driver = sql Check the SQL query if it is overwriting your configuration. -- Alex JOST From mine at michi.su Wed Sep 3 11:23:07 2014 From: mine at michi.su (Michael) Date: Wed, 03 Sep 2014 11:23:07 +0000 Subject: Dovecot is looking for .dovecot.lda-dupes in the wrong place In-Reply-To: <5406F8D6.6010106@dimejo.at> References: <20140902135956.Horde.EVeVlRk68Sn5bkAP8DhZ0w5@webmail.neurohr.at> <5406F8D6.6010106@dimejo.at> Message-ID: <20140903112307.Horde.3GxlUHGhQIDMw0MjVSPGZg7@webmail.neurohr.at> Quoting Alex JOST : > Am 02.09.2014 um 15:59 schrieb Michael: >> Hi, >> I just moved the dovecot maildir location for all virtual users to >> another location. >> I moved everything from >> /var/mail/vhosts/%d/%n >> to >> /var/vmail/%d/%n/maildir >> >> Everything seem to be fine except of one recurring error: >> >> Sep 2 10:16:09 mx0 dovecot: lmtp(13226, sv_bogies at neurohr.at): Error: >> file_dotlock_open(/var/mail/vhosts/domain.at/michael/.dovecot.lda-dupes) >> failed: No such file or directory >> Sep 2 13:31:27 mx0 dovecot: lmtp(16248, sv_bogies at neurohr.at): Error: >> file_dotlock_open(/var/mail/vhosts/domain.at/michael/.dovecot.lda-dupes) >> failed: No such file or directory >> >> >> So Dovecot is looking in the old path. How can I fix that? > >> mail_location = maildir:/var/vmail/%d/%n/maildir >> passdb { >> args = /etc/dovecot/dovecot-sql.conf >> driver = sql >> } >> userdb { >> args = /etc/dovecot/dovecot-sql.conf >> driver = sql > > Check the SQL query if it is overwriting your configuration. Exactly that was the case. Thanks for your help. Michael From s.potapov at rambler-co.ru Wed Sep 3 12:41:29 2014 From: s.potapov at rambler-co.ru (Potapov Sergey) Date: Wed, 3 Sep 2014 12:41:29 +0000 Subject: Assertion failed in sql_transaction_commit with pgsql driver Message-ID: <409CEB1649811749B2E36961BEE2DDBC6817650F@srv-mbx5.rambler.ramblermedia.com> Hi! Next code from driver_pgsql_transaction_commit cause assertion failed in do_query function - i_assert(SQL_DB_IS_READY(&db->api)) } else { /* multiple queries, use a transaction */ ctx->refcount++; sql_query(_ctx->db, "BEGIN", transaction_begin_callback, ctx); <- first sql_query changes db state to SQL_DB_STATE_BUSY while (_ctx->head != NULL) { ctx->refcount++; sql_query(_ctx->db, _ctx->head->query, <- second query cause assertion failed due to SQL_DB_IS_READY returns false transaction_update_callback, _ctx->head); _ctx->head = _ctx->head->next; } sql_query(_ctx->db, "COMMIT", transaction_commit_callback, ctx); } Next transaction query should be called after previous is finished and driver state changed to SQL_DB_STATE_IDLE From jogi at mur.at Wed Sep 3 15:05:41 2014 From: jogi at mur.at (=?UTF-8?B?Sm9naSBIb2Ztw7xsbGVy?=) Date: Wed, 03 Sep 2014 17:05:41 +0200 Subject: quota for subfolder with prefix=INBOX. In-Reply-To: <540622C6.6020005@thinline.cz> References: <54005640.1060104@mur.at> <5405B76A.6060201@mur.at> <5405C58B.2020809@thinline.cz> <5405E7B6.7080000@mur.at> <540622C6.6020005@thinline.cz> Message-ID: <54072E45.6090908@mur.at> Hi, Am 2014-09-02 22:04, schrieb Jiri Bourek: > Yes. The grace value only protects the system from receiving huge last > message. Alright then, back to the $subject. Who has a clue on how to get extended quota for subfolders working when using prefix=INBOX.? Cheers, -- J.Hofm?ller Nisiti - Abie Nathan, 1927-2008 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: OpenPGP digital signature URL: From c.vielhauer at me.com Wed Sep 3 16:28:33 2014 From: c.vielhauer at me.com (Christian Vielhauer) Date: Wed, 03 Sep 2014 18:28:33 +0200 Subject: Setup sieve failed Message-ID: <883A6462-2813-4964-BC94-2C0ADD3AAF4C@me.com> Hi, I try to setup sieve but I have some trouble. Using dovecot 2.2.9 on Ubuntu 14.04.1 LTS. I replaced my correct domain with ?domain.tld?. I am able to create sieve scripts using SOGo. The scripts are created in my mailbox. For example in /var/www/kunden/mail/domain.tld/testuser/sieve/sogo.sieve I have the following script and in same ~/sieve folder is a subdirectory available that?s called "tmp?: ~/sieve ~/sieve/tmp require ["vacation"]; if allof ( not exists ["list-help", "list-unsubscribe", "list-subscribe", "list-owner", "list-post", "list-archive", "list-id", "Mailing-List"], not header :comparator "i;ascii-casemap" :is "Precedence" ["list", "bulk", "junk"], not header :comparator "i;ascii-casemap" :matches "To" "Multiple recipients of*" ) {vacation :days 1 :addresses [?testuser at domain.tld"] text: This is a vacation test message. Please ignore. . ; } Now I open /var/log/mail.err and I can see the following: Sep 3 17:50:09 mail dovecot: imap(testuser at domain.tld): Error: stat(/var/www/kunden/mail/domain.tld/testuser/.dovecot.sieve/tmp) failed: Not a directory I try to create ~/.dovecot.sieve folder, but this file exists and is a symlink. 0 lrwxrwxrwx 1 vmail vmail 16 Sep 3 18:14 .dovecot.sieve -> sieve/sogo.sieve I think I have some miss configuration because i don?t receive any vacation reply when I send mail to my testuser. In log files i cannot see any entries according to my sieve script. Here is my dovecot -n # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-35-generic x86_64 Ubuntu 14.04.1 LTS ext4 auth_default_realm = domain.tld auth_mechanisms = plain login default_vsz_limit = 512 M hostname = mail.domain.tld mail_location = maildir:/var/www/kunden/mail/%d/%n mail_plugins = quota zlib fts 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 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 } passdb { args = nopassword=y allow_nets=10.27.1.20/32 driver = static } plugin { quota = maildir:User quota quota_exceeded_message = Quota exceeded, please go to http://www.example.com/over_quota_help for instructions on how to fix this. quota_rule2 = Trash:storage=+100M quota_rule3 = Archive:storage=+100%% quota_rule4 = Archive.2012:storage=+100%% quota_rule5 = Archive.Gesendet:storage=+100%% quota_warning = storage=99%% quota-exceeded 100 %u quota_warning1 = storage=99%% quota-exceeded 99 %u quota_warning10 = storage=80%% quota-warning 90 %u quota_warning11 = storage=80%% quota-warning 80 %u quota_warning12 = storage=50%% quota-warning 50 %u quota_warning2 = storage=95%% quota-warning 98 %u quota_warning3 = storage=95%% quota-warning 97 %u quota_warning4 = storage=95%% quota-warning 96 %u quota_warning5 = storage=95%% quota-warning 95 %u quota_warning6 = storage=80%% quota-warning 94 %u quota_warning7 = storage=80%% quota-warning 93 %u quota_warning8 = storage=80%% quota-warning 92 %u quota_warning9 = storage=80%% quota-warning 91 %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } postmaster_address = postmaster at domain.tld protocols = " imap lmtp sieve pop3" quota_full_tempfail = yes service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0660 user = postfix } } service dns_client { unix_listener dns-client { mode = 0600 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } service_count = 0 } service imap { client_limit = 5 process_limit = 200 service_count = 0 vsz_limit = 2 G } service lmtp { unix_listener lmtp { mode = 0600 } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service pop3 { client_limit = 5 process_limit = 200 service_count = 0 } service quota-exceeded { executable = script /usr/local/bin/quota-exceeded.sh unix_listener quota-exceeded { user = vmail } user = root } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = vmail } user = root } ssl = required ssl_ca = References: <01D1E9EF-BBF4-4035-8BEC-337A5924DF6A@iki.fi> Message-ID: Timo, Is this very difficult? How much extra code do you are talking about? Is it possible to make this change on the next release? 2014-08-29 15:10 GMT-03:00 Timo Sirainen : > On 28 Aug 2014, at 03:48, Bruno Galindro da Costa < > bruno.galindro at gmail.com> wrote: > > > Is it possible to log a message custom header through Mail logger plugin > or > > other method? It seems that there are a fixed number of info that is > > configurable via mail_log_fields ( > http://wiki2.dovecot.org/Plugins/MailLog). > > Not without some extra coding. > > > .. > > > > My custom header is X-VERTICAL-IP-Quarantine-ID and I want a log event > like > > this one: > > > > Aug 27 09:48:13 imap dovecot: imap(user at domain): copy from INBOX: > box=SPAM, > > uid=213, *X-VERTICAL-IP-Quarantine-ID=u7cnUqYDPA9a*, msgid=< > > 0.0.D7.290.1CFC155CE887302.0 at etm2.com>, size=26481, vsize=26949, > > from==?UTF-8?Q?Dafiti=20-=20Parceiros?= , > > subject==?UTF-8?Q?Sapatos=20com=2040%OFF?==?UTF-8?Q?!=20Apro?=? > > =?UTF-8?Q?veite!?= > > > > -- > > Att. > > Bruno Galindro da Costa > > -- Att. Bruno Galindro da Costa From asai at globalchangemusic.org Wed Sep 3 23:26:24 2014 From: asai at globalchangemusic.org (Asai) Date: Wed, 03 Sep 2014 16:26:24 -0700 Subject: Some Dsync Replication Errors Message-ID: <5407A3A0.8040101@globalchangemusic.org> Greetings, Working on setting up replication and ran into some errors I have questions about and wondering if there's something I need to change. This one is fairly common: Sep 3 12:58:25 molecular dovecot: dsync-server(user at domain.org): Warning: Failed to do incremental sync for mailbox INBOX, retry with a full sync (Modseq 100298 no longer in transaction log) These two I ran into yesterday and today: Sep 2 11:13:32 molecular dovecot: dsync-server(user2 at domain2.org): Error: Timeout during state=slave_recv_last_common Sep 3 12:52:08 molecular dovecot: dsync-server(user3 at domain3.org): Error: read(remote.mailserver.net) failed: EOF Configs: mail_plugins = notify replication service doveadm { inet_listener { port = 1234 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } service aggregator { fifo_listener replication-notify-fifo { user = vmail mode = 0600 } unix_listener replication-notify { user = vmail mode = 0600 } } plugin { mail_replica = tcp:sub.domain.org:1234 } And doveconf -n: [root at molecular dovecot]# doveconf -n # 2.2.13.16 (94835dd63163): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.el6.x86_64 x86_64 Scientific Linux release 6.5 (Carbon) ext4 auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain deliver_log_format = msgid=%m: from=%f: %$ doveadm_password = secret doveadm_port = 1234 mail_debug = yes mail_home = /vmail/%d/%n/home mail_location = maildir:/vmail/%d/%n mail_plugins = notify replication 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 = yes location = prefix = separator = / type = private } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } plugin { mail_log_fields = box msgid from flags mail_replica = tcp:sub.domain.org:1234 sieve = /vmail/%d/%n/home/.dovecot.sieve sieve_dir = /vmail/%d/%n/home/sieve } protocols = imap pop3 lmtp sieve service aggregator { fifo_listener replication-notify-fifo { mode = 0600 user = vmail } unix_listener replication-notify { mode = 0600 user = vmail } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { group = vmail mode = 0660 user = vmail } unix_listener auth-userdb { mode = 0660 user = vmail } user = root } service doveadm { inet_listener { port = 1234 } } service imap-login { process_min_avail = 3 service_count = 0 vsz_limit = 0 } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 } } ssl_cert = Hi All, I have a problem with SASL authentification from postfix when more than 10 mails is sent from the same user simultaneously Postfix abort connection ( Connection lost to authentication server ). Dovecot log after the postfix error an error about connection lost also ( read EOF ) I don't seem to find a parameter for a maximum of connection for the auth process ( ther's one for imap, pop, .. ) but none for auth. Do you have an idea of a way to solve this problem or to have better information ? result of Docecot -n # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.15.6-gentoo-xxxx-std-ipv6-64 x86_64 Gentoo Base System release 2.2 auth_default_realm = aprogsys.com auth_mechanisms = plain login auth_username_format = %Ln dict { acl = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u first_valid_uid = 1001 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_access_groups = dovecot mail_location = mdbox:~/mdbox mail_plugins = " acl notify replication" 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 list = 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 = separator = / } passdb { args = * driver = pam } plugin { acl = vfile acl_anyone = allow acl_shared_dict = proxy::acl antispam_backend = DSPAM antispam_debug_target = syslog antispam_dspam_args = --source=error;--signature=%%s;--user;%n antispam_dspam_binary = /usr/bin/dspam antispam_signature = X-DSPAM-Signature antispam_spam = SPAM antispam_trash = Trash antispam_verbose_debug = 1 mail_replica = remote:root at 192.168.1.7 replication_dsync_parameters = -d -U sieve = ~/.dovecot.sieve sieve_before = /var/lib/dovecot/sieve sieve_default = /var/lib/dovecot/sieve/spam.sieve sieve_dir = ~/sieve } protocols = imap pop3 lmtp sieve replication_max_conns = 2 service aggregator { fifo_listener replication-notify-fifo { mode = 0666 } unix_listener replication-notify { mode = 0666 } } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { mode = 0777 } user = root } service dict { unix_listener dict { mode = 0666 } } service imap-login { process_min_avail = 4 service_count = 0 vsz_limit = 256 M } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0666 } } ssl_cert = Hi there, I'm looking into improving IMAP search support for the Gnus Emacs mail client, and trying to add the ability to search non-ascii characters. So far as I know, I start this invocation with something like: . UID SEARCH CHARSET UTF-8 TEXT {NNN} Where NNN is the number of bytes in my search string. Dovecot then responds with: + OK So... what do I do then? I don't actually know what the next statement is, to provide the actual search string itself. Googling has proved unhelpful, as most of the examples online don't actually show this "+ OK" response. Can someone just briefly outline what's meant to happen next? I've tried including the search string immediately after the byte-size, separated by various combinations of \n\r, but that always gives me a "Missing LF after literal size" error. I'm using the Archlinux dovecot package, which reports version 2.2.13-1. Thanks! Eric From giom87 at libero.it Thu Sep 4 10:01:30 2014 From: giom87 at libero.it (Giovanni Mancuso) Date: Thu, 04 Sep 2014 12:01:30 +0200 Subject: Escape comma in the LDAP passdb subquery configuration In-Reply-To: <54047450.9040702@babel.it> References: <54047450.9040702@babel.it> Message-ID: <5408387A.1000304@libero.it> Hi, I need the same. Is there a way to do this? Thanks Il 01/09/2014 15:27, Francesco Fiore ha scritto: Hi > I have to configure the LDAP passdb to execute a subquery defining > dinamically the new DN to use. > > For example: > pass_attrs = > @mail=mail=%{login_user},dc=%{login_domain},dc=example,dc=com,\ > =proxy=y,\ > =host=%{ldap:mailHost at mail} > > In the previous example, the problem is the use of "," for DN > representation, which is also the separator for the attribute template > in the pass_attr parameter value. > I tried to escape it with '\' or '%' but it doesn't work. > Dovecot version is 2.2.13. > How can I resolve this issue? > > Thanks in advance From kremels at kreme.com Thu Sep 4 16:34:18 2014 From: kremels at kreme.com (LuKreme) Date: Thu, 4 Sep 2014 10:34:18 -0600 Subject: SASL LOGIN : connection to server lost with more than 10 simulatneaous postfix smtps In-Reply-To: <753cef64a3a1bcf17f94f3d756d9e7d9@aprogsys.com> References: <753cef64a3a1bcf17f94f3d756d9e7d9@aprogsys.com> Message-ID: On 04 Sep 2014, at 03:12 , Ve (HOME) wrote: > Postfix abort connection That sounds like postfix is rate limiting. -- "If I were willing to change my morals for convenience or financial gain, we wouldn't be arguing, because I'd already *be* a Republican." -- Wil Shipley From slusarz at curecanti.org Thu Sep 4 18:08:46 2014 From: slusarz at curecanti.org (Michael M Slusarz) Date: Thu, 04 Sep 2014 12:08:46 -0600 Subject: charset-specific searches, and continuation lines In-Reply-To: <87ha0nwxjl.fsf@ericabrahamsen.net> Message-ID: <20140904120846.Horde.uun-eIVC9Omg0Gm5HI2rxQ5@bigworm.curecanti.org> Quoting Eric Abrahamsen : > Hi there, > > I'm looking into improving IMAP search support for the Gnus Emacs mail > client, and trying to add the ability to search non-ascii characters. So > far as I know, I start this invocation with something like: > > . UID SEARCH CHARSET UTF-8 TEXT {NNN} > > Where NNN is the number of bytes in my search string. Dovecot then > responds with: > > + OK > > So... what do I do then? I don't actually know what the next statement > is, to provide the actual search string itself. Googling has proved > unhelpful, as most of the examples online don't actually show this "+ > OK" response. Can someone just briefly outline what's meant to happen > next? I've tried including the search string immediately after the > byte-size, separated by various combinations of \n\r, but that always > gives me a "Missing LF after literal size" error. Your example, assuming your search text is "a?b": . UID SEARCH CHARSET UTF-8 TEXT {4} +OK a?b[CRLF] * SEARCH XXX . OK Literal length is the number of octets in the string - not the number of characters - so not sure if that was tripping you up. michael From listas at adminlinux.com.br Thu Sep 4 18:36:05 2014 From: listas at adminlinux.com.br (Listas@Adminlinux) Date: Thu, 04 Sep 2014 15:36:05 -0300 Subject: Trying Dovecot Replication with dsync In-Reply-To: <53ED0DC2.5080202@adminlinux.com.br> References: <53ED0DC2.5080202@adminlinux.com.br> Message-ID: <5408B115.7070108@adminlinux.com.br> I had no luck with distributed filesystems. Then I use DRBD + Ext4 and my cluster is a just failover cluster. But I need to deliver load balancing now. So I want to replace the current design (with Drbd) for a cluster with Dovecot-Dsync (for replication) and Dovecot-Director (for user->backend mapping). But I'm having problems yet. Like this: dsync-server(account=domaintest.com): Error: Couldn't create lock /var/lib/imap/account=domaintest.com/.dovecot-sync.lock: No such file or directory Thanks!! -- Thiago Henrique Em 14-08-2014 16:28, Listas at Adminlinux escreveu: > Hi, > > I have a failover cluster for mail server with: > Ubuntu12.04 + DRBD (for block replication) + Ext4 filesystem > + Dovecot-2.0.19-2 with Mdbox > > It works fine with ~50k accounts. My cluster design: > http://adminlinux.com.br/cluster_design.txt > > I plan to test Dovecot Replication with dsync to build an active/active > cluster with load balancing. Can anyone direct me to some literature? A > tutorial for example. > > I'm installing a cluster (for tests) with Ubuntu 14.04 + Ext4 filesystem > (without Drbd) + Dovecot-2.2.9-1ubuntu2.1. My conf is in: > http://adminlinux.com.br/replication-doveconf.txt > > I'm following this doc http://wiki2.dovecot.org/Replication but I'm > getting some errors: > > 1) > Aug 14 15:39:34 ceph1 dovecot: imap(account=domaintest.com): Error: > open(/var/run/dovecot/replication-notify-fifo) failed: Permission denied > > What is the correct perms for /var/run/dovecot/replication-notify-fifo ? > Currently: > # ll /var/run/dovecot/replication-notify-fifo > prw------- 1 root root 0 Aug 14 15:57 > /var/run/dovecot/replication-notify-fifo| > > 2) > Aug 14 16:02:34 ceph1 dovecot: dsync-server(account=domaintest.com): > Error: Couldn't create lock > /var/lib/imap/account=domaintest.com/.dovecot-sync.lock: No such file or > directory > Aug 14 16:02:34 ceph1 dovecot: dsync-local(account=domaintest.com): > Error: Couldn't create lock > /var/lib/imap/account=domaintest.com/.dovecot-sync.lock: No such file or > directory > > In my production cluster, it is automatically created by dovecot when > the user performs the first login: > /var/lib/imap/ for INDEX > /var/spool/imap/ for Mdbox > > Thanks! > -- > Thiago Henrique From ve at vetienne.net Thu Sep 4 19:30:01 2014 From: ve at vetienne.net (Vincent ETIENNE) Date: Thu, 04 Sep 2014 21:30:01 +0200 Subject: SASL LOGIN : connection to server lost with more than 10 simulatneaous postfix smtps In-Reply-To: References: <753cef64a3a1bcf17f94f3d756d9e7d9@aprogsys.com> Message-ID: <5408BDB9.6040109@vetienne.net> Le 04/09/2014 18:34, LuKreme a ?crit : > On 04 Sep 2014, at 03:12 , Ve (HOME) wrote: >> Postfix abort connection > That sounds like postfix is rate limiting. > Maybe but the message log doesn't look like rate limiting here is an example Sep 2 16:01:05 ns3 postfix/smtpd[32576]: connect from ns206843.ip-94-23-193.eu[94.23.193.183] Sep 2 16:01:06 ns3 postfix/smtpd[32443]: connect from LAubervilliers-656-01-128-94.w80-11.abo.wanadoo.fr[80.11.5.94] Sep 2 16:01:06 ns3 postfix/smtpd[31906]: connect from unknown[123.21.205.191] Sep 2 16:01:09 ns3 postfix/smtpd[32600]: connect from ns206843.ip-94-23-193.eu[94.23.193.183] Sep 2 16:01:15 ns3 postfix/smtpd[32576]: warning: ns206843.ip-94-23-193.eu[94.23.193.183]: SASL LOGIN authentication failed: Connection lost to authentication server Sep 2 16:01:15 ns3 postfix/smtpd[32576]: disconnect from ns206843.ip-94-23-193.eu[94.23.193.183] Sep 2 16:01:15 ns3 postfix/smtpd[32576]: connect from ns206843.ip-94-23-193.eu[94.23.193.183] Sep 2 16:01:15 ns3 dovecot: auth: Warning: auth client 0 disconnected with 1 pending requests: EOF What is strange ( at least for me ) is the 10 second delay between the connect and the warning and that postfix log a connection lost. And i have process_limt configured ( so 100 connection by default i think) But will try to have more information Vincent From morrisonli at 126.com Thu Sep 4 19:53:19 2014 From: morrisonli at 126.com (morrison) Date: Fri, 5 Sep 2014 03:53:19 +0800 (CST) Subject: how to profiling imap process with valgrind Message-ID: <7e212ab1.1ea.148423a6fd6.Coremail.morrisonli@126.com> Hi, I want to profile runtime performance of imap and pop3 processes. There processes are forked by dovecot master process. I am wondering if there is a way I can profile these processes with valgrind. I tried "service = /bin/valgrind /bin/imap" but this did not work. Thanks, From stefan at arentz.ca Fri Sep 5 01:35:22 2014 From: stefan at arentz.ca (Stefan Arentz) Date: Thu, 4 Sep 2014 21:35:22 -0400 Subject: Announce: Plugin for iOS Push Email support Message-ID: <8408BC1C-68B6-40C3-B1B0-679E179C8861@arentz.ca> I?ve been hacking on a personal side project to support native iOS Push Email in Dovecot. This is specifically for people who are migrating their mail away from OS X Server while keeping their existing Push Email functionality. Native Push Email has some great advantages: it speeds up email notifications (usually within seconds of being handled by dovecot-lda) and it improves battery life since the native notifications flow over a single highly optimized connection to Apple?s infrastructure. Although this is at version 0.1, it is working pretty well for me and I am looking for some additional testers that are interested. Please note that it is not possible to use this project without legally running a copy of OS X Server. You can purchase OS X Server on the Mac App Store or download it for free if you are a registered Mac or iOS developer. This feature is enabled by two projects: https://github.com/st3fan/dovecot-xaps-plugin https://github.com/st3fan/dovecot-xaps-daemon Both projects contain a README that describes how to get things going. I have only developed and tested on Ubuntu 12.04.5 so ideally you run the same version if you are interested in playing with this project. You will need to compile some code and not be afraid of a little admin work. I am also interested in a code review. The Dovecot plugin API is barely documented and I had to guess a lot of things by looking at other plugins. An extra pair of eyes specifically on that code would be awesome. Also from a security perspective. Please file bugs! S. From eric at ericabrahamsen.net Fri Sep 5 02:13:17 2014 From: eric at ericabrahamsen.net (Eric Abrahamsen) Date: Fri, 05 Sep 2014 10:13:17 +0800 Subject: charset-specific searches, and continuation lines References: <87ha0nwxjl.fsf@ericabrahamsen.net> <20140904120846.Horde.uun-eIVC9Omg0Gm5HI2rxQ5@bigworm.curecanti.org> Message-ID: <87fvg6olvm.fsf@ericabrahamsen.net> Michael M Slusarz writes: > Quoting Eric Abrahamsen : > >> Hi there, >> >> I'm looking into improving IMAP search support for the Gnus Emacs mail >> client, and trying to add the ability to search non-ascii characters. So >> far as I know, I start this invocation with something like: >> >> . UID SEARCH CHARSET UTF-8 TEXT {NNN} >> >> Where NNN is the number of bytes in my search string. Dovecot then >> responds with: >> >> + OK >> >> So... what do I do then? I don't actually know what the next statement >> is, to provide the actual search string itself. Googling has proved >> unhelpful, as most of the examples online don't actually show this "+ >> OK" response. Can someone just briefly outline what's meant to happen >> next? I've tried including the search string immediately after the >> byte-size, separated by various combinations of \n\r, but that always >> gives me a "Missing LF after literal size" error. > > Your example, assuming your search text is "a?b": > > . UID SEARCH CHARSET UTF-8 TEXT {4} > +OK > a?b[CRLF] > * SEARCH XXX > . OK > > Literal length is the number of octets in the string - not the number > of characters - so not sure if that was tripping you up. Hi Michael, Well that's embarrassing, I could have sworn that was the first thing I tried. I knew about the octets, and had tried inputting a\303\251b as the search string, but was sure I'd also tried the plain old search string. Thanks! While I've got you here, I hope you'll answer one more question: what's the format for searching multiple terms with non-ascii strings? Is it possible in one run to find a utf-8 encoded subject, and a utf-8 encoded body? Thanks again, Eric From slusarz at curecanti.org Fri Sep 5 02:59:37 2014 From: slusarz at curecanti.org (Michael M Slusarz) Date: Thu, 04 Sep 2014 20:59:37 -0600 Subject: charset-specific searches, and continuation lines In-Reply-To: <87fvg6olvm.fsf@ericabrahamsen.net> References: <87ha0nwxjl.fsf@ericabrahamsen.net> <20140904120846.Horde.uun-eIVC9Omg0Gm5HI2rxQ5@bigworm.curecanti.org> <87fvg6olvm.fsf@ericabrahamsen.net> Message-ID: <20140904205937.Horde.2qcxngzCf7IHttpmcW4yGw7@bigworm.curecanti.org> Quoting Eric Abrahamsen : > While I've got you here, I hope you'll answer one more question: what's > the format for searching multiple terms with non-ascii strings? Is it > possible in one run to find a utf-8 encoded subject, and a utf-8 encoded > body? IMAP interaction would look like this: C: . UID SEARCH CHARSET UTF-8 SUBJECT {4} S: +OK C: a?b BODY {4} S: +OK C: a?b S: * SEARCH XXX S: . OK Even better... if the server supports LITERAL+, you don't have to wait for the synchronizing literal which prevents the need to wait for 2 round-trips from the server: C: . UID SEARCH CHARSET UTF-8 SUBJECT {4+} C: a?b BODY {4+} C: a?b[CRLF] S: * SEARCH XXX S: . OK michael From eric at ericabrahamsen.net Fri Sep 5 03:44:09 2014 From: eric at ericabrahamsen.net (Eric Abrahamsen) Date: Fri, 05 Sep 2014 11:44:09 +0800 Subject: charset-specific searches, and continuation lines References: <87ha0nwxjl.fsf@ericabrahamsen.net> <20140904120846.Horde.uun-eIVC9Omg0Gm5HI2rxQ5@bigworm.curecanti.org> <87fvg6olvm.fsf@ericabrahamsen.net> <20140904205937.Horde.2qcxngzCf7IHttpmcW4yGw7@bigworm.curecanti.org> Message-ID: <87zjeen33q.fsf@ericabrahamsen.net> Michael M Slusarz writes: > Quoting Eric Abrahamsen : > >> While I've got you here, I hope you'll answer one more question: what's >> the format for searching multiple terms with non-ascii strings? Is it >> possible in one run to find a utf-8 encoded subject, and a utf-8 encoded >> body? > > IMAP interaction would look like this: > > C: . UID SEARCH CHARSET UTF-8 SUBJECT {4} > S: +OK > C: a?b BODY {4} > S: +OK > C: a?b > S: * SEARCH XXX > S: . OK > > Even better... if the server supports LITERAL+, you don't have to wait > for the synchronizing literal which prevents the need to wait for 2 > round-trips from the server: > > C: . UID SEARCH CHARSET UTF-8 SUBJECT {4+} > C: a?b BODY {4+} > C: a?b[CRLF] > S: * SEARCH XXX > S: . OK Brilliant, thanks a lot! Not something I would have guessed on my own, and surprisingly hard to find online -- I'm learning to read the RFCs... Thanks again, Eric From teemu.huovila at dovecot.fi Fri Sep 5 06:50:28 2014 From: teemu.huovila at dovecot.fi (Teemu Huovila) Date: Fri, 05 Sep 2014 09:50:28 +0300 Subject: how to profiling imap process with valgrind In-Reply-To: <7e212ab1.1ea.148423a6fd6.Coremail.morrisonli@126.com> References: <7e212ab1.1ea.148423a6fd6.Coremail.morrisonli@126.com> Message-ID: <54095D34.2080802@dovecot.fi> Hello On 09/04/2014 10:53 PM, morrison wrote: > I want to profile runtime performance of imap and pop3 processes. There processes are forked by dovecot master process. I am wondering if there is a way I can profile these processes with valgrind. I tried "service = /bin/valgrind /bin/imap" but this did not work. You could try: service imap { executable = /usr/bin/valgrind --num-callers=50 --leak-check=full -q /libexec/dovecot/imap } service pop3 { executable = /usr/bin/valgrind --num-callers=50 --leak-check=full -q /libexec/dovecot/pop3 Fix the paths for valgrind and Dovecot libexec/ to match your system. Depending on your distribution and library versions you may also want to add --suppressions for some external libraries. Valgrind output will be in Dovecot error log. br, Teemu Huovila From admin at awib.it Fri Sep 5 07:55:35 2014 From: admin at awib.it (admin) Date: Fri, 5 Sep 2014 09:55:35 +0200 Subject: Announce: Plugin for iOS Push Email support In-Reply-To: <8408BC1C-68B6-40C3-B1B0-679E179C8861@arentz.ca> References: <8408BC1C-68B6-40C3-B1B0-679E179C8861@arentz.ca> Message-ID: <0E1711D4-E813-4D18-8B8E-962A3567B225@awib.it> This is interesting; I'm not sure if I got that right from scanning the READMEs. Do I really need to have a working OSX-server setup which I then do migrate away from? What makes this certificate that special such that I only can export it from the existing server setup? -M Am 05.09.2014 um 03:35 schrieb Stefan Arentz : > I?ve been hacking on a personal side project to support native iOS Push Email in Dovecot. This is specifically for people who are migrating their mail away from OS X Server while keeping their existing Push Email functionality. > > Native Push Email has some great advantages: it speeds up email notifications (usually within seconds of being handled by dovecot-lda) and it improves battery life since the native notifications flow over a single highly optimized connection to Apple?s infrastructure. > > Although this is at version 0.1, it is working pretty well for me and I am looking for some additional testers that are interested. > > Please note that it is not possible to use this project without legally running a copy > of OS X Server. You can purchase OS X Server on the Mac App Store or download > it for free if you are a registered Mac or iOS developer. > > This feature is enabled by two projects: > > https://github.com/st3fan/dovecot-xaps-plugin > https://github.com/st3fan/dovecot-xaps-daemon > > Both projects contain a README that describes how to get things going. I have only developed and tested on Ubuntu 12.04.5 so ideally you run the same version if you are interested in playing with this project. > > You will need to compile some code and not be afraid of a little admin work. > > I am also interested in a code review. The Dovecot plugin API is barely documented and I had to guess a lot of things by looking at other plugins. An extra pair of eyes specifically on that code would be awesome. Also from a security perspective. > > Please file bugs! > > S. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5820 bytes Desc: not available URL: From lists at wildgooses.com Fri Sep 5 09:46:15 2014 From: lists at wildgooses.com (Ed W) Date: Fri, 05 Sep 2014 10:46:15 +0100 Subject: Panic/backtrace in dovecot 2.2.13 Message-ID: <54098667.4040903@wildgooses.com> Hi I'm running into regular problems with dovecot choking on "corrupted" index files. The main problem is that it doesn't sort itself out and recover. This message below is repeated regularly in the log files (until I delete the index files) I *think* the trigger to get into this situation might be a files being delivered with incorrect S= values in the filename? Which is to say I am using maildrop to deliver messages and occasionally maildrop seems to write files with incorrect S= names (anyone know why or how to fix it?). The error logged regarding incorrect S= values is obviously completely different, but I speculate that it could be the earlier cause that gets the index file out of shape as shown in the problem here Thanks for any help? (note it's not easy to remove maildrop at present) Ed W Sep 1 07:32:51 mail1 dovecot: imap(xxxxxxx at mailasail.com): Panic: file mail-index-transaction-export.c: line 203 (log_append_ext_hdr_update): assertion failed: (u32.offset + u32.size <= ext_hdr_size) Sep 1 07:32:51 mail1 dovecot: imap(xxxxxxx at mailasail.com): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x69a9e) [0xedee5a9e] -> /usr/lib/dovecot/libdovecot.so.0(+0x69b21) [0xedee5b21] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xede97a69] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_transaction_export+0xa36) [0xedfff706] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xa9f50) [0xedffdf50] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_transaction_commit_full+0xc4) [0xedffe454] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_transaction_commit+0x23) [0xedffe513] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_commit+0xef) [0xee0078ef] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x52e05) [0xedfa6e05] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x52040) [0xedfa6040] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0x5251a) [0xedfa651a] -> /usr/lib/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xf4) [0xedfa68d4] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x3b) [0xedfb786b] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync+0x3f) [0xedfb79af] -> dovecot/imap [xxxxxxx at mailasail.com 80.189.197.148 SELECT](cmd_select_full+0x187) [0x80594d7] -> dovecot/imap [xxxxxxx at mailasail.com 80.189.197.148 SELECT](cmd_select+0x17) [0x8059f37] -> dovecot/imap [xxxxxxx at mailasail.com 80.189.197.148 SELECT](command_exec+0x32) [0x805f1a2] -> dovecot/imap [xxxxxxx at mailasail.com 80.189.197.148 SELECT]() [0x805e197] -> dovecot/imap [xxxxxxx at mailasail.com 80.189.197.148 SELECT]() [0x805e2d9] -> dovecot/imap [xxxxxxx at mailasail.com 80.189.197.148 SELECT](client_handle_input+0x115) [0x805e515] -> dovecot/imap [xxxxxxx at mailasail.com 80.189.197.148 SELECT](client_input+0x72) [0x805e8c2] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x59) [0xedef8e89] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xee) [0xedefa05e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x1c) [0xedef8f1c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x48) [0xedef8fa8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x2e) [0xede9d76e] -> dovecot/imap [xxxxxxx at mailasail.com 80.189.197.148 SELECT](main+0x2bd) [0x80520ed] -> /lib/libc.so.6(__libc_start_main+0xf5) [0xedce9f25] Sep 1 07:32:51 mail1 dovecot: imap(xxxxxxx at mailasail.com): Fatal: master: service(imap): child 31315 killed with signal 6 (core dumps disabled) From JEDC at ramboll.com Fri Sep 5 09:54:29 2014 From: JEDC at ramboll.com (Jens Dueholm Christensen) Date: Fri, 5 Sep 2014 09:54:29 +0000 Subject: Migrating from 2.0.x to 2.2 Message-ID: Hi I'm about to migrate a setup with <20 IMAP (but with a few million mails in all) accounts that belong to the same system-user on an older machine running Dovecot 2.0.13 to a new machine running Dovecot 2.2.13 (or possibly newer..). Mails are stored in Maildirs with no special or advanced features (like alternate storage etc etc). Filesystems are prepared for the expected amount of inodes required, and for the time beeing a change to mdbox is seen as an added complexity. One requirement of the migration is that messageID is not changed - mails are referenced by other systems that expect to find individual mails by the ID. Since dsync is incompatible between 2.0<->2.1<->2.2 what is the best way to perform this migration? I was hoping of rsync'ing all Maildirs from the old machine to the new one (including indexes etc etc) and power up Dovecot 2.2.x and see what happens, but is that possible or is there another (and better) way short of installing 2.0.x on the new machine, rsync everything and then upgrade to 2.2.x? Regards, Jens Dueholm Christensen From CMarcus at Media-Brokers.com Fri Sep 5 09:53:51 2014 From: CMarcus at Media-Brokers.com (Charles Marcus) Date: Fri, 05 Sep 2014 05:53:51 -0400 Subject: Announce: Plugin for iOS Push Email support In-Reply-To: <8408BC1C-68B6-40C3-B1B0-679E179C8861@arentz.ca> References: <8408BC1C-68B6-40C3-B1B0-679E179C8861@arentz.ca> Message-ID: <5409882F.5090004@Media-Brokers.com> On 9/4/2014 9:35 PM, Stefan Arentz wrote: > Although this is at version 0.1, it is working pretty well for me and I am looking for some additional testers that are interested. > > Please note that it is not possible to use this project without legally running a copy > of OS X Server. You can purchase OS X Server on the Mac App Store or download > it for free if you are a registered Mac or iOS developer. Well, that is pretty much a deal breaker for just about everyone (that isn't already running an OSX server)... Would you mind explaining *why* the above is required? Is this just a temporary limitation of some kind? From h.reindl at thelounge.net Fri Sep 5 09:58:24 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Fri, 05 Sep 2014 11:58:24 +0200 Subject: Migrating from 2.0.x to 2.2 In-Reply-To: References: Message-ID: <54098940.5@thelounge.net> Am 05.09.2014 um 11:54 schrieb Jens Dueholm Christensen: > Since dsync is incompatible between 2.0<->2.1<->2.2 what is the best way to perform this migration? > > I was hoping of rsync'ing all Maildirs from the old machine to the new one (including indexes etc etc) and power up Dovecot 2.2.x and see what happens, but is that possible or is there another (and better) way short of installing 2.0.x on the new machine, rsync everything and then upgrade to 2.2.x? use rsync! especially because it is fast after the first "hot sync" and you can repeat the sync, look if all is fine and after you are sure config and data are OK * stop services on both machines * rsync a last time * start services on the new machine * change IP or DNS well, and since you don't change data on the old one you have a untouched backup there -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From teemu.huovila at dovecot.fi Fri Sep 5 10:43:49 2014 From: teemu.huovila at dovecot.fi (Teemu Huovila) Date: Fri, 05 Sep 2014 13:43:49 +0300 Subject: Dovecot Enterprize repository access In-Reply-To: References: <53FF15E5.9060504@dovecot.fi> Message-ID: <540993E5.6070900@dovecot.fi> Hello On 08/28/2014 04:57 PM, Alessandro Bono wrote: > I'm using Enterprise repository for centos 6 and works perfectly > but upgrading packages there is not changelog or other info > I don't have idea what's changed on every update > > Can you post somewhere changelog info or include in rpms? A ChangeLog should be found under /usr/share/doc/. The RPMs themselves do not yet have a changelog as such. br, Teemu Huovila From JEDC at ramboll.com Fri Sep 5 11:43:44 2014 From: JEDC at ramboll.com (Jens Dueholm Christensen) Date: Fri, 5 Sep 2014 11:43:44 +0000 Subject: Migrating from 2.0.x to 2.2 In-Reply-To: <54098940.5@thelounge.net> References: <54098940.5@thelounge.net> Message-ID: From: Reindl Harald on Friday, September 05, 2014 11:58 AM >>> I was hoping of rsync'ing all Maildirs from the old machine to the new one (including indexes etc etc) and power up >>> Dovecot 2.2.x and see what happens, but is that possible or is there another (and better) way short of installing 2.0.x >>> on the new machine, rsync everything and then upgrade to 2.2.x? > use rsync! Allright! I just had to make sure where were no obvious incompatibility issues when changing from an older version of Dovecot.. Sometimes (in other systems) there might be a datastructure or something else thats problematic.. > * stop services on both machines > * rsync a last time > * start services on the new machine > * change IP or DNS That is exactly the plan.. > well, and since you don't change data on the old one you have a untouched backup there Regards, Jens Dueholm Christensen? From trashcan at odo.in-berlin.de Fri Sep 5 11:44:32 2014 From: trashcan at odo.in-berlin.de (Michael Grimm) Date: Fri, 05 Sep 2014 13:44:32 +0200 Subject: Migrating from 2.0.x to 2.2 In-Reply-To: References: Message-ID: On 2014-09-05 11:54, Jens Dueholm Christensen wrote: > Filesystems are prepared for the expected amount of inodes required, > and for the time beeing a change to mdbox is seen as an added > complexity. With that amount of mails in mind, a migration to mdbox is a good idea, IMHO. > One requirement of the migration is that messageID is not changed - > mails are referenced by other systems that expect to find individual > mails by the ID. > > Since dsync is incompatible between 2.0<->2.1<->2.2 what is the best > way to perform this migration? IIRC dsync can be run independently from a running dovecot server. If that is correct, then you could install dovecot 2.2 at the old server, and use that dsync 2.2 for migration to the new server by simultaneously changing the mail storage format. Again, IIRC, all your message IDs shouldn't be modified during that approach. Just give it a try ;-) Regards, Michael From trashcan at odo.in-berlin.de Fri Sep 5 12:00:09 2014 From: trashcan at odo.in-berlin.de (Michael Grimm) Date: Fri, 05 Sep 2014 14:00:09 +0200 Subject: Migrating from 2.0.x to 2.2 In-Reply-To: References: Message-ID: On 2014-09-05 13:44, Michael Grimm wrote: > IIRC dsync can be run independently from a running dovecot server. I remembered correctly (http://wiki2.dovecot.org/Tools/Dsync): | dsync can be run completely standalone. It doesn't require any | Dovecot server processes to be running, except when using -u parameter | to do a userdb lookup from auth process. Regards, Michael From bmk at cego.dk Fri Sep 5 13:11:35 2014 From: bmk at cego.dk (Bjarne Mark Kondrup) Date: Fri, 05 Sep 2014 15:11:35 +0200 Subject: trouble syncing public folders Message-ID: <5409B687.9090704@cego.dk> A non-text attachment was scrubbed... Name: cegosig_2008.gif Type: image/gif Size: 2190 bytes Desc: not available URL: From alessandro.bono at gmail.com Fri Sep 5 13:13:21 2014 From: alessandro.bono at gmail.com (Alessandro Bono) Date: Fri, 5 Sep 2014 13:13:21 +0000 (UTC) Subject: Dovecot Enterprize repository access References: <53FF15E5.9060504@dovecot.fi> <540993E5.6070900@dovecot.fi> Message-ID: On Fri, 05 Sep 2014 13:43:49 +0300, Teemu Huovila wrote: > Hello > > On 08/28/2014 04:57 PM, Alessandro Bono wrote: >> I'm using Enterprise repository for centos 6 and works perfectly >> but upgrading packages there is not changelog or other info >> I don't have idea what's changed on every update >> >> Can you post somewhere changelog info or include in rpms? > > A ChangeLog should be found under /usr/share/doc/. The RPMs themselves do not yet have a changelog as such. > Found it, but it's not exactly what I need These information are too low level and missing packaging information for example with 2.2.13.16 you added a new package dovecot-ee-sieve-sendmail, what is the use? anyway thanks for providing these packages > br, > Teemu Huovila From stefan at arentz.ca Fri Sep 5 13:22:05 2014 From: stefan at arentz.ca (Stefan Arentz) Date: Fri, 5 Sep 2014 09:22:05 -0400 Subject: Announce: Plugin for iOS Push Email support In-Reply-To: <5409882F.5090004@Media-Brokers.com> References: <8408BC1C-68B6-40C3-B1B0-679E179C8861@arentz.ca> <5409882F.5090004@Media-Brokers.com> Message-ID: > On Sep 5, 2014, at 5:53 AM, Charles Marcus wrote: > > On 9/4/2014 9:35 PM, Stefan Arentz wrote: >> Although this is at version 0.1, it is working pretty well for me and I am looking for some additional testers that are interested. >> >> Please note that it is not possible to use this project without legally running a copy >> of OS X Server. You can purchase OS X Server on the Mac App Store or download >> it for free if you are a registered Mac or iOS developer. > > Well, that is pretty much a deal breaker for just about everyone (that isn't already running an OSX server)... > > Would you mind explaining *why* the above is required? Is this just a temporary limitation of some kind? Sorry I should have been more clear. Let me explain. To send native push email notifications, you need a certificate that is generated by Apple. When you enable Push Email on OS X Server, that certificate will be generated for you and stored in your Keychain. There is no other way to generate this certificate. This is why you need a legal copy of OS X Server. You don?t actually have to run OS X Server. I migrated away from OS X Server to regular Dovecot on Ubuntu. So I simply took the generated certificate with me. How to export and convert it is described in the README of the daemon project. This is possible because the certificate is not bound to specific hardware or a specific email domain. It is however connected to your Apple ID. I understand that this is not ideal but unfortunately there is no way around this. OS X Server however is just $19.99. When my code is a bit more final, I will try to contact Apple and find out if they are willing to open up the certificate generation. That would sure benefit a larger audience. S. From CMarcus at Media-Brokers.com Fri Sep 5 13:23:54 2014 From: CMarcus at Media-Brokers.com (Charles Marcus) Date: Fri, 05 Sep 2014 09:23:54 -0400 Subject: Announce: Plugin for iOS Push Email support In-Reply-To: References: <8408BC1C-68B6-40C3-B1B0-679E179C8861@arentz.ca> <5409882F.5090004@Media-Brokers.com> Message-ID: <5409B96A.7010805@Media-Brokers.com> On 9/5/2014 9:22 AM, Stefan Arentz wrote: > When you enable Push Email on OS X Server, that certificate will be generated for you and stored in your Keychain. > > There is no other way to generate this certificate. This is why you need a legal copy of OS X Server. > > You don?t actually have to run OS X Server. I migrated away from OS X Server to regular Dovecot on Ubuntu. So I simply took the generated certificate with me. How to export and convert it is described in the README of the daemon project. > > This is possible because the certificate is not bound to specific hardware or a specific email domain. It is however connected to your Apple ID. > > I understand that this is not ideal but unfortunately there is no way around this. OS X Server however is just $19.99. > > When my code is a bit more final, I will try to contact Apple and find out if they are willing to open up the certificate generation. That would sure benefit a larger audience. Ok, thanks for the explanation... Gotta love (hate) closed source software... From daniel.reynolds at providenceday.org Fri Sep 5 13:28:46 2014 From: daniel.reynolds at providenceday.org (Daniel Reynolds) Date: Fri, 5 Sep 2014 09:28:46 -0400 Subject: Announce: Plugin for iOS Push Email support In-Reply-To: References: <8408BC1C-68B6-40C3-B1B0-679E179C8861@arentz.ca> <5409882F.5090004@Media-Brokers.com> Message-ID: "... I will try to contact Apple and find out if they are willing to open up the certificate generation. " I'm willing to bet the answer will be no. Apple != Open On Sep 5, 2014 9:22 AM, "Stefan Arentz" wrote: > > > On Sep 5, 2014, at 5:53 AM, Charles Marcus > wrote: > > > > On 9/4/2014 9:35 PM, Stefan Arentz wrote: > >> Although this is at version 0.1, it is working pretty well for me and I > am looking for some additional testers that are interested. > >> > >> Please note that it is not possible to use this project without > legally running a copy > >> of OS X Server. You can purchase OS X Server on the Mac App Store > or download > >> it for free if you are a registered Mac or iOS developer. > > > > Well, that is pretty much a deal breaker for just about everyone (that > isn't already running an OSX server)... > > > > Would you mind explaining *why* the above is required? Is this just a > temporary limitation of some kind? > > Sorry I should have been more clear. > > Let me explain. > > To send native push email notifications, you need a certificate that is > generated by Apple. > > When you enable Push Email on OS X Server, that certificate will be > generated for you and stored in your Keychain. > > There is no other way to generate this certificate. This is why you need a > legal copy of OS X Server. > > You don?t actually have to run OS X Server. I migrated away from OS X > Server to regular Dovecot on Ubuntu. So I simply took the generated > certificate with me. How to export and convert it is described in the > README of the daemon project. > > This is possible because the certificate is not bound to specific hardware > or a specific email domain. It is however connected to your Apple ID. > > I understand that this is not ideal but unfortunately there is no way > around this. OS X Server however is just $19.99. > > When my code is a bit more final, I will try to contact Apple and find out > if they are willing to open up the certificate generation. That would sure > benefit a larger audience. > > S. > From nerijus.kislauskas at ktu.lt Fri Sep 5 13:30:21 2014 From: nerijus.kislauskas at ktu.lt (Nerijus Kislauskas) Date: Fri, 05 Sep 2014 16:30:21 +0300 Subject: Dovecot + Postfix postmulti SASL Message-ID: <5409BAED.4070300@ktu.lt> Hello, Our Postfix setup uses multi-instance feature. I would like to enable dovecot SASL mechanisms in postfix. Open two unix sockets is not a problem for us: service auth { unix_listener /var/spool/postfix-instance1/private/auth { mode = 0660 user = postfix group = postfix } unix_listener /var/spool/postfix-instance2/private/auth { mode = 0660 user = postfix group = postfix } } Lets assume, that postfix-instance1 uses LDAP1, and postfix-instance2 uses LDAP2. How can I use different userdb and passdb databases for those sockets? -- Sincerely, Nerijus Kislauskas -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3266 bytes Desc: S/MIME Cryptographic Signature URL: From admin at awib.it Fri Sep 5 13:40:56 2014 From: admin at awib.it (admin) Date: Fri, 5 Sep 2014 15:40:56 +0200 Subject: Announce: Plugin for iOS Push Email support In-Reply-To: References: <8408BC1C-68B6-40C3-B1B0-679E179C8861@arentz.ca> <5409882F.5090004@Media-Brokers.com> Message-ID: <64636627-DAA6-4D03-A5F0-3349A02CFA82@awib.it> No matter what the answer's gonna be the "solution" till then still might be the z-push+exchange-approach? Or did I miss anything more sophisticated out there? Am 05.09.2014 um 15:22 schrieb Stefan Arentz : > >> On Sep 5, 2014, at 5:53 AM, Charles Marcus wrote: >> >> On 9/4/2014 9:35 PM, Stefan Arentz wrote: >>> Although this is at version 0.1, it is working pretty well for me and I am looking for some additional testers that are interested. >>> >>> Please note that it is not possible to use this project without legally running a copy >>> of OS X Server. You can purchase OS X Server on the Mac App Store or download >>> it for free if you are a registered Mac or iOS developer. >> >> Well, that is pretty much a deal breaker for just about everyone (that isn't already running an OSX server)... >> >> Would you mind explaining *why* the above is required? Is this just a temporary limitation of some kind? > > Sorry I should have been more clear. > > Let me explain. > > To send native push email notifications, you need a certificate that is generated by Apple. > > When you enable Push Email on OS X Server, that certificate will be generated for you and stored in your Keychain. > > There is no other way to generate this certificate. This is why you need a legal copy of OS X Server. > > You don?t actually have to run OS X Server. I migrated away from OS X Server to regular Dovecot on Ubuntu. So I simply took the generated certificate with me. How to export and convert it is described in the README of the daemon project. > > This is possible because the certificate is not bound to specific hardware or a specific email domain. It is however connected to your Apple ID. > > I understand that this is not ideal but unfortunately there is no way around this. OS X Server however is just $19.99. > > When my code is a bit more final, I will try to contact Apple and find out if they are willing to open up the certificate generation. That would sure benefit a larger audience. > > S. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5820 bytes Desc: not available URL: From akbwiz+dovecot at gmail.com Fri Sep 5 14:14:14 2014 From: akbwiz+dovecot at gmail.com (Akash) Date: Fri, 5 Sep 2014 19:44:14 +0530 Subject: stemmer or no-stemmer.. Message-ID: Hi, In the documentation of FTS lucene, I need little more clarification about this section: -------------------------------------------------- --with-lucene --with-stemmer The second switch is only required if you have compiled libstemmer yourself or if it's included in the CLucene you are using. -------------------------------------------------- I am totally unsure but as I understand, on Debian testing, the stemmer support for libclucene comes as part of libclucene-contribs1 package (which isn't a required dependency and doesn't get installed if I install dovecot from repos). Please correct me if I am wrong. When I install dovecot-lucene from repos, libclucene-core1 and libstemmer install with it (but no libclucene-contribs1). Does that mean dovecot search has stemmer support? Now I am compiling dovecot and libclucene for Debian stable (which doesn't have latest libs in repos). If I don't compile the contribs part in clucene package but compile dovecot with --with-stemmer, do I get the stemmer support? If I totally opt of this stemmer thing, do I lose anything on search performance? And when you have a no_snowball option, what is the need of libstemmer altogether? Please help me through these confusions.. -Regards, Akash From arekm at maven.pl Fri Sep 5 14:35:29 2014 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Fri, 5 Sep 2014 16:35:29 +0200 Subject: lmtp memory usage problem - Fatal: pool_system_realloc(268435456): Out of memory Message-ID: <201409051635.29944.arekm@maven.pl> Hi. In my setup exim delivers mails to dovecot using LMTP. In one LMTP session exim can deliver up to 200 recipients (batch_max set to that value). Now the problem is that sometimes 256MB is not enoug for dovecot lmtp to handle incoming emails. My questions: - how big memory limit should be for lmtp? I was thinking that lmtp (more or less) simply reads from one descriptor and writes to file, then does rename() (maildir used here) and that's all. That shouldn't require big number of memory. So how to determine correct memory limit and what affects this limit? - is number of recipients in one LMTP session important here? Not sure, maybe dovecot stores email in memory first and then writes to the user maildirs? Setting (batch) limit to 1 could reduce memory usage then (since no need to store anything in memory) ? Thanks, Log: Sep 4 16:10:30 mail dovecot: lmtp(21383, user): Fatal: pool_system_realloc(268435456): Out of memory Sep 4 16:10:30 mail dovecot: lmtp(21383, user): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x682a0) [0x7fe327e632a0] -> /usr/lib64/dovecot/libd ovecot.so.0(+0x6837e) [0x7fe327e6337e] -> /usr/lib64/dovecot/libdovecot.so.0(i_error+0) [0x7fe327e1dbf8] -> /usr/lib64/dovecot/libdovecot.so.0(+0x7d6a3) [0x7fe327e786a3] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_grow_buffer+0x8f) [0x7fe327e6c4cf] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_try_alloc+0x82) [0x7fe327e6c592] -> /usr/lib6 4/dovecot/libdovecot.so.0(+0x73b9b) [0x7fe327e6eb9b] -> /usr/lib64/dovecot/libdovecot.so.0(+0x73c36) [0x7fe327e6ec36] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read+0x 53) [0x7fe327e6bad3] -> /usr/lib64/dovecot/libdovecot.so.0(+0x77391) [0x7fe327e72391] -> /usr/lib64/dovecot/libdovecot.so.0(i_stream_read+0x53) [0x7fe327e6bad3] -> /usr/lib 64/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7fe327e6c2fd] -> /usr/lib64/dovecot/libdovecot.so.0(io_stream_copy+0x7f) [0x7fe327e7cacf] -> /usr/lib64/dovecot/libdo vecot.so.0(+0x83310) [0x7fe327e7e310] -> /usr/lib64/dovecot/libdovecot.so.0(o_stream_send_istream+0x4d) [0x7fe327e7c92d] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maild ir_save_continue+0x5a) [0x7fe32811b14a] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_storage_copy+0x88) [0x7fe328145328] -> /usr/lib64/dovecot/libdovecot-storage.so.0 (maildir_copy+0x42) [0x7fe3281179c2] -> /usr/lib64/dovecot/plugins/lib10_quota_plugin.so(+0xb52b) [0x7fe32764352b] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_cop y+0x6d) [0x7fe32814d29d] -> /usr/lib64/dovecot/libdovecot-lda.so.0(mail_deliver_save+0x185) [0x7fe3283f1765] -> /usr/lib64/dovecot/libdovecot-lda.so.0(mail_deliver+0xeb) [0 x7fe3283f1b6b] -> dovecot/lmtp() [0x405d80] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x3f) [0x7fe327e7398f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handl er_run_internal+0xd7) [0x7fe327e74897] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) [0x7fe327e739f9] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x3 8) [0x7fe327e73a78] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7fe327e22ca3] Sep 4 16:10:30 mail dovecot: lmtp(21383, user): Fatal: master: service(lmtp): child 21383 returned error 83 (Out of memory (service lmtp { vsz_limit=256 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) -- Arkadiusz Mi?kiewicz, arekm / maven.pl From dan at langille.org Sat Sep 6 20:38:46 2014 From: dan at langille.org (Dan Langille) Date: Sat, 6 Sep 2014 16:38:46 -0400 Subject: vsz_limit is 18,447 PB Message-ID: <68B274DC-F65B-43FF-A68E-859A1163E902@langille.org> I encountered this error on FreeBSD 9.3 with dovecot2-2.2.13_3 Short version; vsz_limit is 18,447 PB and it ran out of RAM. Suggestions for change? Sep 6 03:39:32 mailjail dovecot: imap(dan): Panic: file imap-fetch.c: line 556 (imap_fetch_more): assertion failed: (ctx->client->output_cmd_lock == NULL || ctx->client->output_cmd_lock == cmd) Sep 6 03:39:32 mailjail dovecot: imap(dan): Fatal: master: service(imap): child 71153 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) Sep 6 03:59:41 mailjail dovecot: imap(dan): Fatal: pool_system_realloc(2097152): Out of memory Sep 6 03:59:41 mailjail dovecot: imap(dan): Fatal: master: service(imap): child 67732 returned error 83 (Out of memory (service imap { vsz_limit=256 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) Background: I?m in the only user on this system, but this server is accessed by my phone, my laptop, my tablet, and perhaps a web interface. Here are the non-default values: $ doveconf -n # 2.2.13: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 9.3-RELEASE amd64 auth_mechanisms = plain login first_valid_gid = 1001 first_valid_uid = 1001 mail_location = maildir:~/Maildir mail_max_userip_connections = 80 mail_privileged_group = mail passdb { args = scheme=SHA512-CRYPT /var/db/dovecot.users driver = passwd-file } protocols = imap service imap-login { inet_listener imap { address = 10.0.0.1 } inet_listener imaps { port = 0 } } ssl = required ssl_ca = From dovecot.org at veggiechinese.net Sun Sep 7 00:00:22 2014 From: dovecot.org at veggiechinese.net (Will Yardley) Date: Sat, 6 Sep 2014 17:00:22 -0700 Subject: Panic/backtrace in dovecot 2.2.13 In-Reply-To: <54098667.4040903@wildgooses.com> References: <54098667.4040903@wildgooses.com> Message-ID: <20140907000022.GA68413@aura.veggiechinese.net> I'm seeing some similar problems, sometimes, but not always, resulting in a backtrace -- recently migrated (where we had POP3 access via an old version of Courier, and IMAP via an older version of Dovecot; rebuilt the indices for POP3 users using the script). A few cases, where it looks like Dovecot doesn't like the size in the dovecot-uidlist written by the conversion script. Even though I could imagine that process not working properly We also had a problem with the auth process on the atrpms 2.2.10 RPM dying / respawning if a user didn't exist in LDAP (quickly built 2.2.13). Clearing the cache only doesn't seem to fix the problem; I can fix by removing dovecot-uidlist entirely and letting it rebuild, but all of the users with problems use both IMAP and POP3, so having the UIDLs reset is not ideal. Sep 6 16:29:30 hostname dovecot: imap(XXXXXXXX): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0() [0x3dd1a69b9a] -> /usr/lib64/dovecot/libdovecot.so.0() [0x3dd1a69c06] -> /usr/lib64/dovecot/libdovecot.so.0() [0x3dd1a22a8a] -> dovecot-main/imap [XXXXXXXX XX.XX.XX.XX UID FETCH UID FETCH UID FETCH UID FETCH]() [0x418d69] -> dovecot-main/imap [XXXXXXXX XX.XX.XX.XX UID FETCH UID FETCH UID FETCH UID FETCH](cmd_fetch+0x4a3) [0x40d863] -> dovecot-main/imap [XXXXXXXX XX.XX.XX.XX UID FETCH UID FETCH UID FETCH UID FETCH](command_exec+0x3d) [0x41709d] -> dovecot-main/imap [XXXXXXXX XX.XX.XX.XX UID FETCH UID FETCH UID FETCH UID FETCH]() [0x416150] -> dovecot-main/imap [XXXXXXXX XX.XX.XX.XX UID FETCH UID FETCH UID FETCH UID FETCH]() [0x41624a] -> dovecot-main/imap [XXXXXXXX XX.XX.XX.XX UID FETCH UID FETCH UID FETCH UID FETCH](client_handle_input+0x11d) [0x4164bd] -> dovecot-main/imap [XXXXXXXX XX.XX.XX.XX UID FETCH UID FETCH UID FETCH UID FETCH](client_input+0x6f) [0x41682f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x4e) [0x3dd1a7a2ee] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xa7) [0x3dd1a7b497] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) [0x3dd1a7a379] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x3dd1a7a3f8] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x3dd1a275d3] -> dovecot-main/imap [XXXXXXXX XX.XX.XX.XX UID FETCH UID FETCH UID FETCH UID FETCH](main+0x2a8) [0x420088] -> /lib64/libc.so.6(__libc_start_main+0xfd) [0x33b8a1ed5d] -> dovecot-main/imap [XXXXXXXX XX.XX.XX.XX UID FETCH UID FETCH UID FETCH UID FETCH]() [0x40ac69] Sep 6 16:31:28 hostname dovecot: imap(XXXXXXXX): Error: read(/var/spool/maildir/l/XXXXXXXX/cur/1409757870.31894_0.hostname.example.com:2,S): FETCH BODY[] for mailbox INBOX UID 778 got too little data: 763 vs 764 Sep 6 16:31:28 hostname dovecot: imap(XXXXXXXX): Error: Corrupted index cache file /mnt/post/cache/l/XXXXXXXX/.INBOX/dovecot.index.cache: Broken virtual size for mail UID 778 Sep 6 16:44:57 hostname dovecot: imap(XXXXXXXX): Error: read(/var/spool/maildir/l/XXXXXXXX/cur/1407825903.29027_0.hostname.example.com:2,aeS): FETCH BODY[] for mailbox INBOX UID 770 got too little data: 1253 vs 1274 Sep 6 16:44:57 hostname dovecot: imap(XXXXXXXX): Error: Corrupted index cache file /mnt/post/cache/l/XXXXXXXX/.INBOX/dovecot.index.cache: Broken virtual size for mail UID 770 From dovecot.org at veggiechinese.net Sun Sep 7 00:20:08 2014 From: dovecot.org at veggiechinese.net (Will Yardley) Date: Sat, 6 Sep 2014 17:20:08 -0700 Subject: Creating a backup of incoming mail In-Reply-To: <00ab01cfc5b7$140eb930$3c2c2b90$@spamreducer.eu> References: <7E9AACF8-5101-4462-BD7B-8E86C8716A7A@kreme.com> <00ab01cfc5b7$140eb930$3c2c2b90$@spamreducer.eu> Message-ID: <20140907002008.GB68413@aura.veggiechinese.net> On Mon, Sep 01, 2014 at 09:33:52AM +0200, Patrick De Zordo wrote: > To backup all mail (incoming and outgoing), BCC all mails, you could > do the following.. > Add to your "/etc/postfix/main.cf" the following: > ---8<------------------------------------------------------------------------------------- > # Auto-Backup all mails > transport_maps = hash:/etc/postfix/transport > backuplmtp_destination_recipient_limit = 1 > lmtp_destination_recipient_limit = 1 > recipient_bcc_maps = pcre:/etc/postfix/backup_bcc.pcre > sender_bcc_maps = pcre:/etc/postfix/backup_bcc.pcre Why not just use $always_bcc? w From bourek at thinline.cz Sun Sep 7 08:39:39 2014 From: bourek at thinline.cz (Jiri Bourek) Date: Sun, 07 Sep 2014 10:39:39 +0200 Subject: vsz_limit is 18,447 PB In-Reply-To: <68B274DC-F65B-43FF-A68E-859A1163E902@langille.org> References: <68B274DC-F65B-43FF-A68E-859A1163E902@langille.org> Message-ID: <540C19CB.7090501@thinline.cz> On 6.9.2014 22:38, Dan Langille wrote: > I encountered this error on FreeBSD 9.3 with dovecot2-2.2.13_3 > > Short version; vsz_limit is 18,447 PB and it ran out of RAM. Suggestions for change? > > Sep 6 03:39:32 mailjail dovecot: imap(dan): Panic: file imap-fetch.c: line 556 (imap_fetch_more): assertion failed: (ctx->client->output_cmd_lock == NULL || ctx->client->output_cmd_lock == cmd) > Sep 6 03:39:32 mailjail dovecot: imap(dan): Fatal: master: service(imap): child 71153 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) > Sep 6 03:59:41 mailjail dovecot: imap(dan): Fatal: pool_system_realloc(2097152): Out of memory > Sep 6 03:59:41 mailjail dovecot: imap(dan): Fatal: master: service(imap): child 67732 returned error 83 (Out of memory (service imap { vsz_limit=256 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) > Check the message again - it says vsz_limit=256MB > Background: I?m in the only user on this system, but this server is accessed by my phone, my laptop, my tablet, and perhaps a web interface. > > > But there are some interesting values when I look at the output of doveconf. Specifically, vsz_limit is 18,447 PB? yeah, that?s pretty big. > > service imap-login { > vsz_limit = 18446744073709551615 B > } > According to your log it was process "imap" what ran out of memory. You are showing configuration for imap-login - they are not the same thing, see http://wiki2.dovecot.org/Design/Processes Not sure if this behaviour is a bug or something that is to be expected when you run out of VSZ limit in imap process - that needs to be answered by someone more knowledgeable From clovis at agr.unicamp.br Mon Sep 8 15:48:20 2014 From: clovis at agr.unicamp.br (Clovis Tristao) Date: Mon, 08 Sep 2014 12:48:20 -0300 Subject: Configure Dovecot Master User Message-ID: <540DCFC4.8060803@agr.unicamp.br> Hi, Does anyone have any idea or hint how to configure dovecot master user? I'm already on it for almost fifteen days and can not find a solution. I appreciate any help, Clovis -- Clovis Tristao - UNICAMP/Faculdade de Engenharia Agricola Administrador de Redes - Secao de Informatica (SINFO) E-mail: clovis at feagri.unicamp.br http://www.feagri.unicamp.br MSN: clovis_tristao33 at hotmail.com Fone: 55(19) 35211031-35211038-35211047-91173116 From listas at adminlinux.com.br Mon Sep 8 17:00:01 2014 From: listas at adminlinux.com.br (Listas@Adminlinux) Date: Mon, 08 Sep 2014 14:00:01 -0300 Subject: Configure Dovecot Master User In-Reply-To: <540DCFC4.8060803@agr.unicamp.br> References: <540DCFC4.8060803@agr.unicamp.br> Message-ID: <540DE091.9040204@adminlinux.com.br> Hi Clovis, try something like this: **In this example you should have your users in a MySQL database. On /etc/dovecot/conf.d/10-auth.conf file add this: # Master login *master-user auth_master_user_separator = * # Use for master login passdb { args = /etc/dovecot/dovecot-sql-master.conf.ext driver = sql master = yes pass = yes } Create /etc/dovecot/dovecot-sql-master.conf.ext file with this content: driver = mysql connect = host= dbname= user= password= default_pass_scheme = MD5-CRYPT password_query = \ SELECT Password AS password \ FROM Users \ WHERE User = 'master-user' user_query = \ SELECT Password AS password \ FROM Users \ WHERE User = 'master-user' To do tests: telnet your-dovecot-server.com 143 AUTH LOGIN *master-user Good Luck -- Thiago Henrique Em 08-09-2014 12:48, Clovis Tristao escreveu: > Hi, > > Does anyone have any idea or hint how to configure dovecot master user? > I'm already on it for almost fifteen days and can not find a solution. > I appreciate any help, > > Clovis > From d.iskandarov at gmail.com Mon Sep 8 09:01:04 2014 From: d.iskandarov at gmail.com (d.iskandarov) Date: Sun, 8 Sep 2014 09:01:04 +0000 Subject: d.iskandarov Message-ID: <4B002335F687AC78482AC58C908C9E55@skennie.com> http://shop2.vashare.sg/zhbyes/oevhtkx.aknikio From dan at langille.org Mon Sep 8 20:58:23 2014 From: dan at langille.org (Dan Langille) Date: Mon, 8 Sep 2014 16:58:23 -0400 Subject: vsz_limit is 18,447 PB In-Reply-To: <540C19CB.7090501@thinline.cz> References: <68B274DC-F65B-43FF-A68E-859A1163E902@langille.org> <540C19CB.7090501@thinline.cz> Message-ID: <7DB084F3-F021-470D-9A9C-FC9590673BC6@langille.org> On Sep 7, 2014, at 4:39 AM, Jiri Bourek wrote: > On 6.9.2014 22:38, Dan Langille wrote: >> I encountered this error on FreeBSD 9.3 with dovecot2-2.2.13_3 >> >> Short version; vsz_limit is 18,447 PB and it ran out of RAM. Suggestions for change? >> >> Sep 6 03:39:32 mailjail dovecot: imap(dan): Panic: file imap-fetch.c: line 556 (imap_fetch_more): assertion failed: (ctx->client->output_cmd_lock == NULL || ctx->client->output_cmd_lock == cmd) >> Sep 6 03:39:32 mailjail dovecot: imap(dan): Fatal: master: service(imap): child 71153 killed with signal 6 (core not dumped - set service imap { drop_priv_before_exec=yes }) >> Sep 6 03:59:41 mailjail dovecot: imap(dan): Fatal: pool_system_realloc(2097152): Out of memory >> Sep 6 03:59:41 mailjail dovecot: imap(dan): Fatal: master: service(imap): child 67732 returned error 83 (Out of memory (service imap { vsz_limit=256 MB }, you may need to increase it) - set CORE_OUTOFMEM=1 environment to get core dump) >> > > Check the message again - it says vsz_limit=256MB Yes, I saw that?. I can?t explain why I didn?t question the rest of the output. > >> Background: I?m in the only user on this system, but this server is accessed by my phone, my laptop, my tablet, and perhaps a web interface. >> > >> >> But there are some interesting values when I look at the output of doveconf. Specifically, vsz_limit is 18,447 PB? yeah, that?s pretty big. >> >> service imap-login { >> vsz_limit = 18446744073709551615 B >> } >> > > According to your log it was process ?im ap" what ran out of memory. You are showing configuration for imap-login - they are not the same thing, see http://wiki2.dovecot.org/Design/Processes My errror, sorry. OK, here?s imap: service imap { chroot = client_limit = 1 drop_priv_before_exec = no executable = imap extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1024 process_min_avail = 0 protocol = imap service_count = 1 type = unix_listener login/imap { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } Still the same value? why not 265MB? > Not sure if this behaviour is a bug or something that is to be expected when you run out of VSZ limit in imap process - that needs to be answered by someone more knowledgeable It seems quite common: $ doveconf | grep vsz_limit default_vsz_limit = 256 M vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B vsz_limit = 18446744073709551615 B [dan at mailjail:~] $ Thank you. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 333 bytes Desc: Message signed with OpenPGP using GPGMail URL: From bourek at thinline.cz Mon Sep 8 22:38:08 2014 From: bourek at thinline.cz (Jiri Bourek) Date: Tue, 09 Sep 2014 00:38:08 +0200 Subject: vsz_limit is 18,447 PB In-Reply-To: <7DB084F3-F021-470D-9A9C-FC9590673BC6@langille.org> References: <68B274DC-F65B-43FF-A68E-859A1163E902@langille.org> <540C19CB.7090501@thinline.cz> <7DB084F3-F021-470D-9A9C-FC9590673BC6@langille.org> Message-ID: <540E2FD0.9030900@thinline.cz> >> >>> Background: I?m in the only user on this system, but this server is accessed by my phone, my laptop, my tablet, and perhaps a web interface. >>> >> >>> >>> But there are some interesting values when I look at the output of doveconf. Specifically, vsz_limit is 18,447 PB? yeah, that?s pretty big. >>> >>> service imap-login { >>> vsz_limit = 18446744073709551615 B >>> } >>> >> >> According to your log it was process ?im ap" what ran out of memory. You are showing configuration for imap-login - they are not the same thing, see http://wiki2.dovecot.org/Design/Processes > > My errror, sorry. OK, here?s imap: > > service imap { > chroot = > client_limit = 1 > drop_priv_before_exec = no > executable = imap > extra_groups = > group = > idle_kill = 0 > privileged_group = > process_limit = 1024 > process_min_avail = 0 > protocol = imap > service_count = 1 > type = > unix_listener login/imap { > group = > mode = 0666 > user = > } > user = > vsz_limit = 18446744073709551615 B > } > > Still the same value? why not 265MB? Hm, I can only guess (someone with more knowledge of dovecot source code probably knows better), but it seems like that value is magic number for "not set". My doveconf outputs the same thing on services which don't have vsz_limit set explicitly, but when I list /proc/[pid]/limits on such a service, the row called "Max address space" (which is - AFAIK - limit on vsz) shows 2GB, a value of default_vsz_limit setting. I'd say don't overthink it, just put explicit vsz_limit = 512M into service imap section (if your machine's RAM allows) and be done with it. From lists at tigertech.com Mon Sep 8 23:41:18 2014 From: lists at tigertech.com (Robert L Mathews) Date: Mon, 08 Sep 2014 16:41:18 -0700 Subject: vsz_limit is 18,447 PB In-Reply-To: <540E2FD0.9030900@thinline.cz> References: <68B274DC-F65B-43FF-A68E-859A1163E902@langille.org> <540C19CB.7090501@thinline.cz> <7DB084F3-F021-470D-9A9C-FC9590673BC6@langille.org> <540E2FD0.9030900@thinline.cz> Message-ID: <540E3E9E.6000903@tigertech.com> On 9/8/14 3:38 PM, Jiri Bourek wrote:> Hm, I can only guess (someone with more knowledge of dovecot source code > probably knows better), but it seems like that value is magic number for > "not set". My doveconf outputs the same thing on services which don't > have vsz_limit set explicitly, but when I list /proc/[pid]/limits on > such a service, the row called "Max address space" (which is - AFAIK - > limit on vsz) shows 2GB, a value of default_vsz_limit setting. > > I'd say don't overthink it, just put explicit vsz_limit = 512M into > service imap section (if your machine's RAM allows) and be done with it. Right. According to my notes from when I upgraded to 2.x, "18446744073709551615" means it's not set and that the default_vsz_limit will apply, which is 256 MB. To avoid the problem the original poster had, I used: default_vsz_limit = 1 G -- Robert L Mathews, Tiger Technologies, http://www.tigertech.net/ From eric at ericabrahamsen.net Tue Sep 9 02:14:53 2014 From: eric at ericabrahamsen.net (Eric Abrahamsen) Date: Tue, 09 Sep 2014 10:14:53 +0800 Subject: minimal configuration for lucene fts Message-ID: <878ultwndu.fsf@ericabrahamsen.net> Hi, I'm using dovecot (version 2.2.13 on archlinux) in the simplest, no-brainer way possible. It sits between mbsync, which I use to fetch mail from servers, and Gnus, my MUA. Both mbsync and Gnus connect to dovecot with an invocation like this: /usr/lib/dovecot/imap -o mail_location=maildir:$HOME/.mail/ea/ I have three different mail accounts, all that changes is the final directory on the mail_location path above. I haven't touched anything else: there's no running daemon, no configuration, no user database, no PAM, no nothing. Now I'm trying to set up text searching via lucene, but all the examples I've seen online assume a full running daemon and user accounts. I tried to fake it by running: doveadm index -u eric at localhost -q INBOX -o mail_location-maildir:/home/eric/.mail/ea but it was clearly expecting a user database. Is there any way to create text indexes for my three different accounts, in their respective directories, without fully setting up a running dovecot? I'll do that if I have to, but my current setup works great, and is very simple, and I'd like to keep it simple if I can. Thanks! Eric From nerijus.kislauskas at ktu.lt Tue Sep 9 06:57:05 2014 From: nerijus.kislauskas at ktu.lt (Nerijus Kislauskas) Date: Tue, 09 Sep 2014 09:57:05 +0300 Subject: Dovecot + Postfix postmulti SASL In-Reply-To: <5409BAED.4070300@ktu.lt> References: <5409BAED.4070300@ktu.lt> Message-ID: <540EA4C1.4030101@ktu.lt> On 09/05/2014 04:30 PM, Nerijus Kislauskas wrote: > Hello, > > Our Postfix setup uses multi-instance feature. I would like to enable > dovecot SASL mechanisms in postfix. Open two unix sockets is not a > problem for us: > > service auth { > unix_listener /var/spool/postfix-instance1/private/auth { > mode = 0660 > user = postfix > group = postfix > } > unix_listener /var/spool/postfix-instance2/private/auth { > mode = 0660 > user = postfix > group = postfix > } > } > > Lets assume, that postfix-instance1 uses LDAP1, and postfix-instance2 > uses LDAP2. How can I use different userdb and passdb databases for > those sockets? > Hi again, After long googling we have found this link: http://dovecot.2317879.n4.nabble.com/multiple-passdbs-and-auth-sockets-td43780.html Ajusted my configs, and now I'm facing this problem: 2014-09-09T08:57:19.954477+03:00 mail-gw1 dovecot: ktu: Error: doveconf: Fatal: execvp(/run/dovecot/dovecot/auth) failed: No such file or directory That is strange, because our dovecot is 2.2.9 from debian wheezy-backports and auth executable is in /usr/lib/dovecot/auth. Source lines responsible for this error is in doveconf.c: $ grep -n execvp src/config/doveconf.c 850: execvp(exec_args[0], exec_args); 851: i_fatal("execvp(%s) failed: %m", exec_args[0]); $ Somehow exec_args[0] comes not as /usr/lib/dovecot/auth, but /run/dovecot/dovecot/auth. Not sure how is that possible. As author states, Dovecot v1.x is better working with multiple auth {} sections. I'm working with postfix multiple instances and SASL. I would be glad to see such capability in dovecot v2.x. Maybe my case is 1 out of the million? -- Sincerely, Nerijus Kislauskas -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 3266 bytes Desc: S/MIME Cryptographic Signature URL: From kremels at kreme.com Tue Sep 9 07:05:54 2014 From: kremels at kreme.com (LuKreme) Date: Tue, 9 Sep 2014 01:05:54 -0600 Subject: Creating a backup of incoming mail In-Reply-To: <20140907002008.GB68413@aura.veggiechinese.net> References: <7E9AACF8-5101-4462-BD7B-8E86C8716A7A@kreme.com> <00ab01cfc5b7$140eb930$3c2c2b90$@spamreducer.eu> <20140907002008.GB68413@aura.veggiechinese.net> Message-ID: <09132729-048A-4A9C-AB74-38EBCF11CCF8@kreme.com> > On 06 Sep 2014, at 18:20 , Will Yardley wrote: > > On Mon, Sep 01, 2014 at 09:33:52AM +0200, Patrick De Zordo wrote: >> To backup all mail (incoming and outgoing), BCC all mails, you could >> do the following.. > >> Add to your "/etc/postfix/main.cf" the following: >> ---8<------------------------------------------------------------------------------------- >> # Auto-Backup all mails >> transport_maps = hash:/etc/postfix/transport >> backuplmtp_destination_recipient_limit = 1 >> lmtp_destination_recipient_limit = 1 >> recipient_bcc_maps = pcre:/etc/postfix/backup_bcc.pcre >> sender_bcc_maps = pcre:/etc/postfix/backup_bcc.pcre > > Why not just use $always_bcc? Does that apply to INCOMING mail? (that's what I am trying to backup) -- 'I warn you, dragon, the human spirit is-' They never found out what it was, or at least what he thought it was, although possibly in the dark hours of a sleepless night some of them might have remembered the subsequent events and formed a pretty good and gut-churning insight, to whit, that one of the things sometimes forgotten about the human spirit is that while it is, in the right conditions, noble and brave and wonderful, it is also, when you get right down to it, only human. From rs at sys4.de Tue Sep 9 08:06:58 2014 From: rs at sys4.de (Robert Schetterer) Date: Tue, 09 Sep 2014 10:06:58 +0200 Subject: Creating a backup of incoming mail In-Reply-To: <09132729-048A-4A9C-AB74-38EBCF11CCF8@kreme.com> References: <7E9AACF8-5101-4462-BD7B-8E86C8716A7A@kreme.com> <00ab01cfc5b7$140eb930$3c2c2b90$@spamreducer.eu> <20140907002008.GB68413@aura.veggiechinese.net> <09132729-048A-4A9C-AB74-38EBCF11CCF8@kreme.com> Message-ID: <540EB522.1090400@sys4.de> Am 09.09.2014 um 09:05 schrieb LuKreme: > >> On 06 Sep 2014, at 18:20 , Will Yardley wrote: >> >> On Mon, Sep 01, 2014 at 09:33:52AM +0200, Patrick De Zordo wrote: >>> To backup all mail (incoming and outgoing), BCC all mails, you could >>> do the following.. >> >>> Add to your "/etc/postfix/main.cf" the following: >>> ---8<------------------------------------------------------------------------------------- >>> # Auto-Backup all mails >>> transport_maps = hash:/etc/postfix/transport >>> backuplmtp_destination_recipient_limit = 1 >>> lmtp_destination_recipient_limit = 1 >>> recipient_bcc_maps = pcre:/etc/postfix/backup_bcc.pcre >>> sender_bcc_maps = pcre:/etc/postfix/backup_bcc.pcre >> >> Why not just use $always_bcc? > > Does that apply to INCOMING mail? (that's what I am trying to backup) > > optional to recipient_bcc_maps sender_bcc_maps you may use http://www.postfix.org/postconf.5.html ... always_bcc (default: empty) Optional address that receives a "blind carbon copy" of each message that is received by the Postfix mail system. Note: with Postfix 2.3 and later the BCC address is added as if it was specified with NOTIFY=NONE. The sender will not be notified when the BCC address is undeliverable, as long as all down-stream software implements RFC 3461. Note: with Postfix 2.2 and earlier the sender will be notified when the BCC address is undeliverable. Note: automatic BCC recipients are produced only for new mail. To avoid mailer loops, automatic BCC recipients are not generated after Postfix forwards mail internally, or after Postfix generates mail itself. ... Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From mailinglist at darac.org.uk Tue Sep 9 12:59:58 2014 From: mailinglist at darac.org.uk (Darac Marjal) Date: Tue, 9 Sep 2014 13:59:58 +0100 Subject: vsz_limit is 18,447 PB In-Reply-To: <540E3E9E.6000903@tigertech.com> References: <68B274DC-F65B-43FF-A68E-859A1163E902@langille.org> <540C19CB.7090501@thinline.cz> <7DB084F3-F021-470D-9A9C-FC9590673BC6@langille.org> <540E2FD0.9030900@thinline.cz> <540E3E9E.6000903@tigertech.com> Message-ID: <20140909125958.GA23729@darac.org.uk> On Mon, Sep 08, 2014 at 04:41:18PM -0700, Robert L Mathews wrote: > On 9/8/14 3:38 PM, Jiri Bourek wrote:> Hm, I can only guess (someone > with more knowledge of dovecot source code > > probably knows better), but it seems like that value is magic number for > > "not set". My doveconf outputs the same thing on services which don't > > have vsz_limit set explicitly, but when I list /proc/[pid]/limits on > > such a service, the row called "Max address space" (which is - AFAIK - > > limit on vsz) shows 2GB, a value of default_vsz_limit setting. > > > > I'd say don't overthink it, just put explicit vsz_limit = 512M into > > service imap section (if your machine's RAM allows) and be done with it. > > Right. According to my notes from when I upgraded to 2.x, > "18446744073709551615" means it's not set and that the default_vsz_limit > will apply, which is 256 MB. That seems sensible to me. 2^64 bytes is 18446744073709551616 (18.45EB), so the number shown is (2^64 - 1). As a *limit* for a 64-bit program, that seems about as close to "no limit" as you're going to get :) > > To avoid the problem the original poster had, I used: > > default_vsz_limit = 1 G > > -- > Robert L Mathews, Tiger Technologies, http://www.tigertech.net/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: From listas at adminlinux.com.br Tue Sep 9 18:56:06 2014 From: listas at adminlinux.com.br (Listas@Adminlinux) Date: Tue, 09 Sep 2014 15:56:06 -0300 Subject: My Dsync isn't replicating 'EXPUNGE' IMAP command Message-ID: <540F4D46.1000004@adminlinux.com.br> Hi! I have two Dovecot-2.2.13 servers with Dsync Replication: server1 and server2. When I execute 'EXPUNGE' on server1 side, the messages with FLAG \Deleted are expunged only on server1. The message is still present in Server2. Could someone give me a hint reason for this ? Thanks in advance! -- Thiago Henrique ====================================================================== How I reproduce: == ON SERVER1 == Client: $ telnet 143 Trying ... Connected to . Escape character is '^]'. Server: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] MAILBOX1 IMAP/POP3 server Client: AUTH LOGIN Server: AUTH OK [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 QUOTA] Logged in Client: A002 SELECT "INBOX" Server: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft nonjunk) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft nonjunk \*)] Flags permitted. * 2 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1410284221] UIDs valid * OK [UIDNEXT 16] Predicted next UID * OK [HIGHESTMODSEQ 56] Highest A002 OK [READ-WRITE] Select completed (0.000 secs). Client: A003 FETCH 1:* (UID FLAGS) Server: * 1 FETCH (UID 13 FLAGS (nonjunk)) * 2 FETCH (UID 15 FLAGS (nonjunk)) A003 OK Fetch completed. Client: A005 STORE 1 +FLAGS \Deleted Server: * 1 FETCH (FLAGS (\Deleted nonjunk)) A005 OK Store completed. Client: A003 FETCH 1:* (UID FLAGS) Server: * 1 FETCH (UID 13 FLAGS (\Deleted nonjunk)) * 2 FETCH (UID 15 FLAGS (nonjunk)) A003 OK Fetch completed. Client: A006 EXPUNGE Server: * 1 EXPUNGE A006 OK Expunge completed. Client: A007 FETCH 1:* (UID FLAGS) Server: * 1 FETCH (UID 15 FLAGS (nonjunk)) A007 OK Fetch completed. Client: A008 LOGOUT Server: * BYE Logging out A008 OK Logout completed. Connection closed by foreign host. == ON SERVER2 == Client: $ telnet 143 Trying ... Connected to . Escape character is '^]'. Server: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] MAILBOX2 IMAP/POP3 server Client: AUTH LOGIN Server: AUTH OK [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 QUOTA] Logged in Client: A002 SELECT "INBOX" Server: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft nonjunk) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft nonjunk \*)] Flags permitted. * 2 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1410284221] UIDs valid * OK [UIDNEXT 17] Predicted next UID * OK [HIGHESTMODSEQ 61] Highest A002 OK [READ-WRITE] Select completed (0.000 secs). Client: A003 FETCH 1:* (UID FLAGS) Server: * 1 FETCH (UID 13 FLAGS (\Deleted nonjunk)) * 2 FETCH (UID 15 FLAGS (nonjunk)) A003 OK Fetch completed. Client: A008 LOGOUT Server: * BYE Logging out A008 OK Logout completed. Connection closed by foreign host. = My settings = * My settins age identical on both server1 and server2, except by 'listen', 'address' and 'mail_replica' directives. # doveconf -n # 2.2.13 (6bb26098a45c): /etc/dovecot/dovecot.conf # OS: Linux 3.13.0-30-generic x86_64 Ubuntu 14.04.1 LTS auth_master_user_separator = * auth_mechanisms = plain login auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@= auth_worker_max_count = 1 disable_plaintext_auth = no doveadm_password = secret doveadm_port = 12345 listen = server1 log_path = /var/log/dovecot.log login_greeting = MAILBOX1 IMAP/POP3 server mail_fsync = never mail_gid = dovemail mail_plugins = " notify replication quota" mail_uid = dovemail passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } passdb { args = /etc/dovecot/dovecot-sql-master.conf.ext driver = sql master = yes pass = yes } plugin { mail_replica = tcp:server2:12345 quota = dict:User quota::file:/var/lib/imap/%n/dovecot-quota quota_rule = *:storage=1GB } protocols = imap pop3 lmtp service aggregator { fifo_listener replication-notify-fifo { user = dovemail } unix_listener replication-notify { user = dovemail } } service auth-worker { user = $default_internal_user } service auth { client_limit = 1024 process_limit = 1 process_min_avail = 1 } service doveadm { inet_listener { port = 12345 } } service imap { process_limit = 1024 process_min_avail = 1 } service lmtp { inet_listener { address = server1 port = 24 } process_limit = 256 process_min_avail = 1 } service pop3-login { inet_listener pop3 { address = server1 port = 110 } } service pop3 { process_limit = 256 process_min_avail = 1 } service replicator { process_min_avail = 1 } ssl = no userdb { driver = prefetch } userdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } verbose_proctitle = yes protocol imap { imap_client_workarounds = tb-extra-mailbox-sep imap_idle_notify_interval = 2 mins imap_max_line_length = 64 k mail_max_userip_connections = 50 mail_plugins = " notify replication quota imap_quota" } protocol lmtp { mail_fsync = optimized mail_plugins = " notify replication sieve quota" } protocol pop3 { mail_plugins = " notify replication quota" } From bob at computerisms.ca Tue Sep 9 21:09:56 2014 From: bob at computerisms.ca (Bob Miller) Date: Tue, 09 Sep 2014 14:09:56 -0700 Subject: outlook 2013 Message-ID: <1410296996.20035.51.camel@worklian> I am trying really hard to wrap my head around why people insist on using this program... Where I have outlook 2013 users, I have had nothing but problems getting their mail to work with imap. my solution has been to set them up with pop, which works just like it always has. Or move them to a different program. recently, I have a customer who requires multiple machines, all using outlook 2013, to access the same email address, so pretty much have to use imap. if I set up just one of the machines with imap, it works more less as expected, with hiccups such as mail taking an hour or two or more to show up. But shortly after I connect a 2nd machine to the same account, one or both machines start to go wonky. Symptoms include deleted items returning, read messages becoming unread again, and duplicates being constantly created and deleted. The last I can confirm by watching in webmail and refreshing the inbox every few seconds; as mail shows up and deletes in outlook, so it does in webmail too. On my test machine connected to the same server, I have evolution, outlook and thunderbird all connecting to one account with no problems. Well, outlook hiccups, but it's not unusable. And I have other users on the system that share email accounts across a variety of other clients and platforms, including older versions of outlook. I have tried checking message rules, there are none; removing all folder subscriptions; running scanpst, which finds errors even before the account finishes syncing and ever time I run it after that; I have looked for viruses/malware; I have confirmed there is no forwarding or some trickery happening on the server; chkdsk and similar hardware checks all come up clean, the computers are only a couple of months old; I have got certs set up with SANs and the CA installed such that outlook does not error on the certificate; and I have tried just about every combination of settings that seem relevant. The one thing that does seem to work, at least for a few minutes or an hour or two, is deleting and recreating the accounts on one of the computers. But the problem inevitably returns in short order. Surely people have outlook 2013 connecting via imap to dovecot without problems; is there some special trick that google is hiding from me? -- Computerisms Bob Miller 867-334-7117 / 867-633-3760 http://computerisms.ca From bruno.galindro at gmail.com Tue Sep 9 21:41:54 2014 From: bruno.galindro at gmail.com (Bruno Galindro da Costa) Date: Tue, 9 Sep 2014 18:41:54 -0300 Subject: ACL with Public Namespace Message-ID: I've configured a namespace like this: namespace avisos { type = public list = yes location = maildir:/var/mail.avisos:INDEXPVT=~/Maildir/avisos subscriptions = yes prefix = "AVISOS." mailbox DIVULGA { auto = subscribe } } This is the namespace representation in filesystem: root at imap:~# ls -lha /var/mail.avisos/ total 44K drwxr-xr-x 7 vmail mail 4,0K Set 9 18:21 . drwxr-xr-x 16 root root 4,0K Set 9 17:08 .. drwxr-xr-x 5 vmail mail 4,0K Set 9 16:49 .DIVULGA -rw-r--r-- 1 root root 17 Set 9 18:21 dovecot-acl -rw-r--r-- 1 vmail mail 0 Set 9 18:11 dovecot-acl-list -rw-r--r-- 1 vmail mail 360 Set 9 18:11 dovecot.mailbox.log -rw-r--r-- 1 vmail mail 8 Set 9 18:02 dovecot-uidvalidity -r--r--r-- 1 vmail mail 0 Set 9 14:57 dovecot-uidvalidity.540f3f88 -rw-r--r-- 1 vmail mail 249 Set 9 18:11 subscriptions This is the content of dovecot-acl file located at namespace's root level: root at imap:~# cat /var/mail.avisos/dovecot-acl authenticated rs After reload dovecot service, it trows this error message in log: Sep 9 18:14:13 imap dovecot: imap(user at mydomain): Error: Failed to autocreate mailbox AVISOS.DIVULGA: Permission denied So, I've changed the dovecot-acl file to this one and the problem was solved. root at imap:~# cat /var/mail.avisos/dovecot-acl authenticated rsk But that change created another problem: dovecot-acl file is copied into AVISOS.DIVULGA. So, the user can create a maildir inside it. This behaviour is bad because "invalid" maildirs are created under the filesystem. My intention is to don't permit the user to create any maildir inside any location of that namespace. But, I want to make possible to the administrator to edit the dovecot.conf, insert a new mailbox into namespace avisos and reload dovecot service to create new maildirs automatically. How can I solve this problem? -- Att. Bruno Galindro da Costa From jtam.home at gmail.com Tue Sep 9 22:37:49 2014 From: jtam.home at gmail.com (Joseph Tam) Date: Tue, 9 Sep 2014 15:37:49 -0700 (PDT) Subject: vsz_limit is 18,447 PB In-Reply-To: References: Message-ID: On Tue, 9 Sep 2014, dovecot-request at dovecot.org wrote: > vsz_limit = 18446744073709551615 B > } > > Still the same value? why not 265MB? I guess this is Dovecot's approximation of infinity. It's the largest value that fits into a 64-bit signed integer (2^64-1). Joseph Tam From ve at vetienne.net Tue Sep 9 23:04:25 2014 From: ve at vetienne.net (Vincent ETIENNE) Date: Wed, 10 Sep 2014 01:04:25 +0200 Subject: Replication problem In-Reply-To: <4f6c77594a5d5dcfa55799379d9921c1@aprogsys.com> References: <4f6c77594a5d5dcfa55799379d9921c1@aprogsys.com> Message-ID: <540F8779.7090505@vetienne.net> Le 19/08/2014 10:34, Ve (HOME) a ?crit : > Hi, > > I'm using mdbox and replication. Due to configuration error > synchronization was not able to be done last week. Since then > the problem has been corrected but synchronisation for some mailbox > always failed in I/O stalled timeout for 600 seconds. > > The link between the two servers is quite slow and multiple sync are > done in parallel leading to congested link. > > I can't replicate with rsync as change in the mdbox has been done on > the two servers to get back to a working state. > > What do you think could be done to resynchronized the two dovecot > server. Another question is what is this timeout ? Timeout of > communication i.e no data received during 600 seconds ( to me that > looks unlikely ) or 600 seconds for doing the full sync or 600 seconds > for one mail sync. > > Thanks for any help. > > Regards, > > Vincent > Hi After some digging, the problem is this 600 seconds timeout that in my case is unsuffisant to transfer one big mail. So retry and ..; same result.. and again and again I have verify with strace that data is exchange continuously during the sync between the two host but i can't succed in uploading the file during that time. Is there a way to configure this timeout ? Eventually a manual sync with a larger timeout to restore replication before limiting maximum size in postfix ? Possibly a feature would be to have a shorter timeout but applied to the transmission ( ie. nothing receive during 30 sec = timeout ) or a timeout compuited base on size ( ie. 300 sec for 10 mo for example) Any help appreciated Vincent From kremels at kreme.com Wed Sep 10 00:25:32 2014 From: kremels at kreme.com (LuKreme) Date: Tue, 9 Sep 2014 18:25:32 -0600 Subject: Creating a backup of incoming mail In-Reply-To: <540EB522.1090400@sys4.de> References: <7E9AACF8-5101-4462-BD7B-8E86C8716A7A@kreme.com> <00ab01cfc5b7$140eb930$3c2c2b90$@spamreducer.eu> <20140907002008.GB68413@aura.veggiechinese.net> <09132729-048A-4A9C-AB74-38EBCF11CCF8@kreme.com> <540EB522.1090400@sys4.de> Message-ID: <05B3CF71-3A66-43DA-806B-C62BC122CF4B@kreme.com> > On 09 Sep 2014, at 02:06 , Robert Schetterer wrote: > > Am 09.09.2014 um 09:05 schrieb LuKreme: >> >>> On 06 Sep 2014, at 18:20 , Will Yardley wrote: >>> >>> On Mon, Sep 01, 2014 at 09:33:52AM +0200, Patrick De Zordo wrote: >>>> To backup all mail (incoming and outgoing), BCC all mails, you could >>>> do the following.. >>> >>>> Add to your "/etc/postfix/main.cf" the following: >>>> ---8<------------------------------------------------------------------------------------- >>>> # Auto-Backup all mails >>>> transport_maps = hash:/etc/postfix/transport >>>> backuplmtp_destination_recipient_limit = 1 >>>> lmtp_destination_recipient_limit = 1 >>>> recipient_bcc_maps = pcre:/etc/postfix/backup_bcc.pcre >>>> sender_bcc_maps = pcre:/etc/postfix/backup_bcc.pcre >>> >>> Why not just use $always_bcc? >> >> Does that apply to INCOMING mail? (that's what I am trying to backup) >> >> > > optional to > > recipient_bcc_maps > sender_bcc_maps Well, heck. I feel twice as dumb as I did before I read your message. Thanks for that, I think. :) -- I DID NOT SEE ELVIS Bart chalkboard Ep. 7G07 From patrickdk at patrickdk.com Wed Sep 10 00:35:11 2014 From: patrickdk at patrickdk.com (Patrick Domack) Date: Tue, 09 Sep 2014 20:35:11 -0400 Subject: outlook 2013 In-Reply-To: <1410296996.20035.51.camel@worklian> Message-ID: <20140909203511.Horde.rINh4s8NjgyG0YrUQ-bqMA2@mail.patrickdk.com> Quoting Bob Miller : > I am trying really hard to wrap my head around why people insist on > using this program... > > Where I have outlook 2013 users, I have had nothing but problems getting > their mail to work with imap. my solution has been to set them up with > pop, which works just like it always has. Or move them to a different > program. > I have no idea what your doing to cause this issue :( I have a normal install of dovecot running, and I have 3 webmail pages open, 2 phones using imap, and a thunderbird connected to it. I started with outlook 2007, then 2010, and now 2013 for the last 2 years or 3years (I upgraded to it in beta at first). I haven't had any issues at all, I can delete emails, move emails, ..., and they instantly change in the other programs. I just use the normal outlook2013 config options for the account, besides making sure the ssl settings are right. I think I have only used it on the 2.2 branch though, what dovecot version are you using? From bob at computerisms.ca Wed Sep 10 00:51:09 2014 From: bob at computerisms.ca (Bob Miller) Date: Tue, 09 Sep 2014 17:51:09 -0700 Subject: outlook 2013 In-Reply-To: <20140909203511.Horde.rINh4s8NjgyG0YrUQ-bqMA2@mail.patrickdk.com> References: <20140909203511.Horde.rINh4s8NjgyG0YrUQ-bqMA2@mail.patrickdk.com> Message-ID: <1410310269.20035.83.camel@worklian> Hi Patrick, Thanks for your reply. > I have no idea what your doing to cause this issue :( > > I have a normal install of dovecot running, and I have 3 webmail pages > open, 2 phones using imap, and a thunderbird connected to it. I > started with outlook 2007, then 2010, and now 2013 for the last 2 > years or 3years (I upgraded to it in beta at first). I haven't had any > issues at all, I can delete emails, move emails, ..., and they > instantly change in the other programs. I have several accounts that are used by a variety of different programs and devices, as well, but the only program that gives me any problem is outlook 2013. And not quite consistently, on some few machines I have seen it work the same as any other client. This one particular case has me quite baffled though. > I just use the normal outlook2013 config options for the account, > besides making sure the ssl settings are right. > > I think I have only used it on the 2.2 branch though, what dovecot > version are you using? # dovecot --version 2.2.13 sigh. At least now I know it should be working, so I will keep searching fior a solution... From kremels at kreme.com Wed Sep 10 03:27:35 2014 From: kremels at kreme.com (LuKreme) Date: Tue, 9 Sep 2014 21:27:35 -0600 Subject: outlook 2013 In-Reply-To: <1410296996.20035.51.camel@worklian> References: <1410296996.20035.51.camel@worklian> Message-ID: <8B59D382-56E6-4848-BF1F-C72A78EBFCA0@kreme.com> On 09 Sep 2014, at 15:09 , Bob Miller wrote: > I am trying really hard to wrap my head around why people insist on > using this program? Which program? > Where I have outlook 2013 users, I have had nothing but problems getting > their mail to work with imap. my solution has been to set them up with > pop, which works just like it always has. Or move them to a different > program. That?s odd. The one and only thing that Lookout does pretty well is IMAP. > Surely people have outlook 2013 connecting via imap to dovecot without > problems; Yep. > is there some special trick that google is hiding from me? Not really. -- "He loves Nature in spite of what it did to him." - Forrest Tucker From trentl at webinabox.net.au Wed Sep 10 04:15:09 2014 From: trentl at webinabox.net.au (Trent Lloyd) Date: Wed, 10 Sep 2014 12:15:09 +0800 Subject: outlook 2013 In-Reply-To: <1410310269.20035.83.camel@worklian> References: <20140909203511.Horde.rINh4s8NjgyG0YrUQ-bqMA2@mail.patrickdk.com> <1410310269.20035.83.camel@worklian> Message-ID: <70997954-4E49-4EEF-8648-6DAE3B648C5D@webinabox.net.au> I have had this problem a lot on my old Dovecot 0.9 system.. it seems to be OK on 2.2 however. It?s really noticeable when interacting with another Apple map system. One key thing is the Outlook by default doesn?t immediately purge your deleted items. It lags on that a bit. There are settings to change that. Trent On 10 Sep 2014, at 8:51 am, Bob Miller wrote: > Hi Patrick, > > Thanks for your reply. > >> I have no idea what your doing to cause this issue :( >> >> I have a normal install of dovecot running, and I have 3 webmail pages >> open, 2 phones using imap, and a thunderbird connected to it. I >> started with outlook 2007, then 2010, and now 2013 for the last 2 >> years or 3years (I upgraded to it in beta at first). I haven't had any >> issues at all, I can delete emails, move emails, ..., and they >> instantly change in the other programs. > > I have several accounts that are used by a variety of different programs > and devices, as well, but the only program that gives me any problem is > outlook 2013. And not quite consistently, on some few machines I have > seen it work the same as any other client. This one particular case has > me quite baffled though. > >> I just use the normal outlook2013 config options for the account, >> besides making sure the ssl settings are right. >> >> I think I have only used it on the 2.2 branch though, what dovecot >> version are you using? > > # dovecot --version > 2.2.13 > > sigh. At least now I know it should be working, so I will keep > searching fior a solution... From trentl at webinabox.net.au Wed Sep 10 04:22:31 2014 From: trentl at webinabox.net.au (Trent Lloyd) Date: Wed, 10 Sep 2014 12:22:31 +0800 Subject: outlook 2013 In-Reply-To: <70997954-4E49-4EEF-8648-6DAE3B648C5D@webinabox.net.au> References: <20140909203511.Horde.rINh4s8NjgyG0YrUQ-bqMA2@mail.patrickdk.com> <1410310269.20035.83.camel@worklian> <70997954-4E49-4EEF-8648-6DAE3B648C5D@webinabox.net.au> Message-ID: <50A548F3-4501-44E4-ABA4-9762D961D256@webinabox.net.au> I had a much more exciting experience with Outlook for Mac (which is much worse?) Changed from Dovecot 0.9 to 2.2 but changed the folder separator from . to \, so that I could have shared folders with dots in the username. When you do this, it starts creating a new mailbox every time it connects every minute, called like Trash 1, Trash 1 1, Trash 1 1 1, Trash 1 1 1.. I got up to about 40+ appended folder names. It also does this with INBOX, Sent, etc. It won?t ever stop doing this, and even if you change the folder separator back it still keeps doing it. Only way to fix is to change the server name which causes it to purge the entire local cache and start over (basically a quick delete/re-add). My other favourite issue with Outlook for Mac was it eating messages, they?d come in, and disappear. Spam filtering was off, no rules setup, they just disappeared, and got deleted from the server. Eish. Trent On 10 Sep 2014, at 12:15 pm, Trent Lloyd wrote: > I have had this problem a lot on my old Dovecot 0.9 system.. it seems to be OK on 2.2 however. > It?s really noticeable when interacting with another Apple map system. > > > One key thing is the Outlook by default doesn?t immediately purge your deleted items. It lags on that a bit. There are settings to change that. > > Trent > > > On 10 Sep 2014, at 8:51 am, Bob Miller wrote: > >> Hi Patrick, >> >> Thanks for your reply. >> >>> I have no idea what your doing to cause this issue :( >>> >>> I have a normal install of dovecot running, and I have 3 webmail pages >>> open, 2 phones using imap, and a thunderbird connected to it. I >>> started with outlook 2007, then 2010, and now 2013 for the last 2 >>> years or 3years (I upgraded to it in beta at first). I haven't had any >>> issues at all, I can delete emails, move emails, ..., and they >>> instantly change in the other programs. >> >> I have several accounts that are used by a variety of different programs >> and devices, as well, but the only program that gives me any problem is >> outlook 2013. And not quite consistently, on some few machines I have >> seen it work the same as any other client. This one particular case has >> me quite baffled though. >> >>> I just use the normal outlook2013 config options for the account, >>> besides making sure the ssl settings are right. >>> >>> I think I have only used it on the 2.2 branch though, what dovecot >>> version are you using? >> >> # dovecot --version >> 2.2.13 >> >> sigh. At least now I know it should be working, so I will keep >> searching fior a solution... From ph at inwx.de Wed Sep 10 05:41:27 2014 From: ph at inwx.de (InterNetworX | Pascal Heverhagen) Date: Wed, 10 Sep 2014 07:41:27 +0200 Subject: =?UTF-8?B?IsKnIi1zaWduIGluIHBhc3N3b3Jkcw==?= Message-ID: <540FE487.8010008@inwx.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hey users, I've got a constellation with dovecot, postfix, froxlor and roundcube. My problem is, when a user has got a paragraph sign in his password, every mail client tells him, that he entered a wrong password. The log says as usually "password mismatch". did anyone else fixed this problem already? Hope you can help me :) Pascal -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUD+SHAAoJEA3oZzzqW4iVobwH/0r/g9eP2inhqCNLqBBN3Ret gU9L9dXM8iqOBl3ylgTK1Fvf/7rhnPHhM43oS+KAoaOcrG4u9PI83hfKYqMGuZPB +1/PhMcEmydUl98mjT76tC/SuGAgRnWlnc6eA+LB1Zp8EgN0h4l8zLXvw2mv6nA5 dyEHUq6cW9oIg38jMe0rXAb5mqNROAGtKTaM7182Xxk5dnJAfb5ZdNPZ8Vbn0A3d ENE9hzdndNeQPkDIVmdD6Fv1kWVwCf7shAPgQ3yJoJxOUaEq9sl4BQRI/GcLU6RF lpQFsMQTjwDa9RWPYvOT33SHDiwYLAr9l65C5A1ReLNROSaTW5rE+lL9NiUWcD8= =jP+Y -----END PGP SIGNATURE----- From slusarz at curecanti.org Wed Sep 10 05:46:29 2014 From: slusarz at curecanti.org (Michael M Slusarz) Date: Tue, 09 Sep 2014 23:46:29 -0600 Subject: =?utf-8?b?IsKnIi1zaWdu?= in passwords In-Reply-To: <540FE487.8010008@inwx.de> Message-ID: <20140909234629.Horde.c8YzQsXrAhSzNcJ64TgtVg4@bigworm.curecanti.org> Quoting InterNetworX | Pascal Heverhagen : > Hey users, > > I've got a constellation with dovecot, postfix, froxlor and roundcube. > > My problem is, when a user has got a paragraph sign in his password, > every mail client tells him, that he entered a wrong password. The log > says as usually "password mismatch". did anyone else fixed this > problem already? non-ASCII characters are only supported in the AUTHENTICATE command. My guess is that your MUA is trying to send those characters via the LOGIN command. michael From jogi at mur.at Wed Sep 10 06:07:05 2014 From: jogi at mur.at (=?UTF-8?B?Sm9naSBIb2Ztw7xsbGVy?=) Date: Wed, 10 Sep 2014 08:07:05 +0200 Subject: Escape comma in the LDAP passdb subquery configuration In-Reply-To: <54047450.9040702@babel.it> References: <54047450.9040702@babel.it> Message-ID: <540FEA89.1070507@mur.at> Hi, Am 2014-09-01 15:27, schrieb Francesco Fiore: > pass_attrs = > @mail=mail=%{login_user},dc=%{login_domain},dc=example,dc=com,\ > =proxy=y,\ > =host=%{ldap:mailHost at mail} > > In the previous example, the problem is the use of "," for DN > representation, which is also the separator for the attribute template I see. Have you tried using a different filter instead of dynamic arguments in pass_attrs? Cheers, -- j.hofm?ller Optimism doesn't alter the laws of physics. - Subcommander T'Pol -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: OpenPGP digital signature URL: From alec at alec.pl Wed Sep 10 06:15:48 2014 From: alec at alec.pl (A.L.E.C) Date: Wed, 10 Sep 2014 08:15:48 +0200 Subject: =?UTF-8?B?IsKnIi1zaWduIGluIHBhc3N3b3Jkcw==?= In-Reply-To: <20140909234629.Horde.c8YzQsXrAhSzNcJ64TgtVg4@bigworm.curecanti.org> References: <20140909234629.Horde.c8YzQsXrAhSzNcJ64TgtVg4@bigworm.curecanti.org> Message-ID: <540FEC94.9080502@alec.pl> On 09/10/2014 07:46 AM, Michael M Slusarz wrote: >> My problem is, when a user has got a paragraph sign in his password, >> every mail client tells him, that he entered a wrong password. The log >> says as usually "password mismatch". did anyone else fixed this >> problem already? > > non-ASCII characters are only supported in the AUTHENTICATE command. My > guess is that your MUA is trying to send those characters via the LOGIN > command. Some clients including Roundcube have password charset setting. So, for Roundcube it should be set to UTF-8. I remember something similiar in Thunderbird. -- Aleksander 'A.L.E.C' Machniak LAN Management System Developer [http://lms.org.pl] Roundcube Webmail Developer [http://roundcube.net] --------------------------------------------------- PGP: 19359DC1 @@ GG: 2275252 @@ WWW: http://alec.pl From francesco.fiore at babel.it Wed Sep 10 08:37:06 2014 From: francesco.fiore at babel.it (Francesco Fiore) Date: Wed, 10 Sep 2014 10:37:06 +0200 Subject: Escape comma in the LDAP passdb subquery configuration In-Reply-To: <540FEA89.1070507@mur.at> References: <54047450.9040702@babel.it> <540FEA89.1070507@mur.at> Message-ID: <54100DB2.6090402@babel.it> Hi, On 10/09/2014 08:07, Jogi Hofm?ller wrote: > Hi, > > Am 2014-09-01 15:27, schrieb Francesco Fiore: > >> pass_attrs = >> @mail=mail=%{login_user},dc=%{login_domain},dc=example,dc=com,\ >> =proxy=y,\ >> =host=%{ldap:mailHost at mail} >> >> In the previous example, the problem is the use of "," for DN >> representation, which is also the separator for the attribute template > I see. Have you tried using a different filter instead of dynamic > arguments in pass_attrs? I tried but in this case the passdb is configured to use master authentication and in this infrastructure there is an N*M association between users and mailboxes. This association is implemented in the back-end instances using the user entries to do authentication, and the mailbox entries to get the attributes in the userdb. In the user entries there is a custom attribute. For example: dn: uid=myuser,ou=People,dc=example,dc=com ... uid: myuser associatedMailbox: mymbox at example.com userPassword: ********** dn: mail=mymbox at example.com,ou=Mailboxes,dc=example,dc=com ... mail: mymbox at example.com mailHost: 192.168.0.1 homeDirectory: /path/to/homedir In the configuration of the back-end instance I use different filters to get different LDAP entries in the passdb (user entries) and userdb (mailbox entries). The problem is in the proxy configuration because Dovecot must execute a LDAP bind with the user entry but it needs to get also the mailHost attribute in the mailbox entry to connect to the correct back-end server. The complete passdb configuration is: pass_attrs =@mail=mail=%{login_user},dc=%{login_domain},dc=example,dc=com,\ =proxy=y,\ =host=%{ldap:mailHost at mail} pass_filter = (&(uid=%{user})(associatedMailbox=%{login_user})) I'm thinking to implement this authentication using an external auth daemon and configure Dovecot tu use an auth-dict, but I would avoid to execute an independent daemon. Can I configure Dovecot to spawn an external process? Is this a valid solution for your experience? > > Cheers, Regars From teemu.huovila at dovecot.fi Wed Sep 10 09:56:49 2014 From: teemu.huovila at dovecot.fi (Teemu Huovila) Date: Wed, 10 Sep 2014 12:56:49 +0300 Subject: Replication problem In-Reply-To: <540F8779.7090505@vetienne.net> References: <4f6c77594a5d5dcfa55799379d9921c1@aprogsys.com> <540F8779.7090505@vetienne.net> Message-ID: <54102061.2000105@dovecot.fi> On 09/10/2014 02:04 AM, Vincent ETIENNE wrote: > After some digging, the problem is this 600 seconds timeout that in my > case is unsuffisant to transfer one big mail. So retry and ..; same > result.. and again and again > > I have verify with strace that data is exchange continuously during the > sync between the two host but i can't succed in uploading the file > during that time. > > Is there a way to configure this timeout ? > > Eventually a manual sync with a larger timeout to restore replication > before limiting maximum size in postfix ? > > Possibly a feature would be to have a shorter timeout but applied to the > transmission ( ie. nothing receive during 30 sec = timeout ) > or a timeout compuited base on size ( ie. 300 sec for 10 mo for example) > > Any help appreciated Currently there is no way to change it at run time. As a quick fix, if you compile your own Dovecot, you could try modifying DSYNC_IBC_STREAM_TIMEOUT_MSECS in src/doveadm/dsync/dsync-ibc-stream.c . I think that is the timeout you are bumping up against. br, Teemu Huovila From mailinglists at easy-mail.it Wed Sep 10 10:41:39 2014 From: mailinglists at easy-mail.it (Francesco) Date: Wed, 10 Sep 2014 12:41:39 +0200 Subject: master user in ldap? Message-ID: <1410345699.3844.29.camel@secoges-laptop> Hello everyone, i was wondering if it was possible to add master user criteria in ldap backends. the idea is that the users, members of a specific group, should be able to login with their own credentials on behalf of other users. i've tried setting it up like this: hosts = localhost dn = CN=ldapuser,OU=someldapou,DC=domain,DC=tld dnpass = auth_bind = yes ldap_version = 3 base = DC=domain,DC=tld user_attrs = sAMAccountName=home=/var/vmail/% $,skip=found,maxStorage=quota_rule=*:storage=% $M,quota_rule2=Trash:storage=+100M user_filter = (&(ObjectClass=person)(sAMAccountName=% u)(memberOf=CN=Domain Admins,CN=Users,DC=domain,DC=tld)) then i added a passdb as follows passdb { driver = ldap master = yes args = /etc/dovecot/dovecot-ldap-masteruser.conf.ext } and of course the separator. but when i try to login with realuser*userinadministratorsgroup passwordofuserinadministratorsgroup i get authentication failed. am i missing something? is it even possible to accomplish such thing? because i didn't see any example in the wiki, only plain passdb and sql. thanks in advance Francesco From ve at vetienne.net Wed Sep 10 10:49:27 2014 From: ve at vetienne.net (Vincent ETIENNE) Date: Wed, 10 Sep 2014 12:49:27 +0200 Subject: Replication problem In-Reply-To: <54102061.2000105@dovecot.fi> References: <4f6c77594a5d5dcfa55799379d9921c1@aprogsys.com> <540F8779.7090505@vetienne.net> <54102061.2000105@dovecot.fi> Message-ID: <54102CB7.5030204@vetienne.net> Le 10/09/2014 11:56, Teemu Huovila a ?crit : > On 09/10/2014 02:04 AM, Vincent ETIENNE wrote: >> After some digging, the problem is this 600 seconds timeout that in my >> case is unsuffisant to transfer one big mail. So retry and ..; same >> result.. and again and again >> >> I have verify with strace that data is exchange continuously during the >> sync between the two host but i can't succed in uploading the file >> during that time. >> >> Is there a way to configure this timeout ? >> >> Eventually a manual sync with a larger timeout to restore replication >> before limiting maximum size in postfix ? >> >> Possibly a feature would be to have a shorter timeout but applied to the >> transmission ( ie. nothing receive during 30 sec = timeout ) >> or a timeout compuited base on size ( ie. 300 sec for 10 mo for example) >> >> Any help appreciated > Currently there is no way to change it at run time. As a quick fix, if you compile your own Dovecot, you could try modifying > DSYNC_IBC_STREAM_TIMEOUT_MSECS in src/doveadm/dsync/dsync-ibc-stream.c . I think that is the timeout you are bumping up against. > > br, > Teemu Huovila > Thanks will try and keep you inform of the result. May take some time ( i am not compiling dovecot now ) Really thanks because for now my replication is broken and so mail are not receive for some user depending on the instance of dovecot they connect.... Vincent ETIENNE From teemu.huovila at dovecot.fi Wed Sep 10 11:02:42 2014 From: teemu.huovila at dovecot.fi (Teemu Huovila) Date: Wed, 10 Sep 2014 14:02:42 +0300 Subject: Replication problem In-Reply-To: <54102CB7.5030204@vetienne.net> References: <4f6c77594a5d5dcfa55799379d9921c1@aprogsys.com> <540F8779.7090505@vetienne.net> <54102061.2000105@dovecot.fi> <54102CB7.5030204@vetienne.net> Message-ID: <54102FD2.3040406@dovecot.fi> On 09/10/2014 01:49 PM, Vincent ETIENNE wrote: > Le 10/09/2014 11:56, Teemu Huovila a ?crit : >>Currently there is no way to change it at run time. As a quick fix, if you compile your own Dovecot, you could try modifying >> DSYNC_IBC_STREAM_TIMEOUT_MSECS in src/doveadm/dsync/dsync-ibc-stream.c . I think that is the timeout you are bumping up against. > Thanks will try and keep you inform of the result. May take some time ( > i am not compiling dovecot now ) > Really thanks because for now my replication is broken and so mail are > not receive for some user depending on > the instance of dovecot they connect.... Cancel that advice. Timo did a change that should make changing the timeout by hand unnecessary. If you can, try running Dovecot with this patch http://hg.dovecot.org/dovecot-2.2/rev/647162da8423. There should be no time outs, even for large mails. Do you get any error messages, when there is a timeout? br, Teemu Huovila From jogi at mur.at Wed Sep 10 11:20:36 2014 From: jogi at mur.at (=?UTF-8?B?Sm9naSBIb2Ztw7xsbGVy?=) Date: Wed, 10 Sep 2014 13:20:36 +0200 Subject: preserving flags for shared mailbox when migrating from cyrus to dovecot In-Reply-To: <594B2611-57AD-4464-9BF5-29ED31F545DB@iki.fi> References: <53F4890F.5000008@mur.at> <594B2611-57AD-4464-9BF5-29ED31F545DB@iki.fi> Message-ID: <54103404.1090507@mur.at> Hi Timo, all, Am 2014-08-20 14:16, schrieb Timo Sirainen: > I think you can first migrate the shared mailbox's mails as whatever > user. Then use doveadm sync -1 (and maybe -m shared/foo to sync only > the one mailbox) to migrate the message flags. Well, I tried that in several different ways, all without any success. Let's assume the user is called jane and she has a subscription for the shared mailbox doe I tried the following: doveadm sync -1 -R -u jane -m shared.doe imapc: I also tried using the namespace switch: doveadm sync -1 -R -u jane -n shared imapc: again no success. The shared mailbox stays available and working but the flags will not be synced to the state they had on the original server. I also tried it without -R but that didn't get me anywhere either and should be wrong anyways AFAICT. Any further ideas anyone or should I prepare our shared mailbox users that all their email will be unread after migration? Cheers, -- j.hofm?ller We are all idiots with deadlines. - Mike West -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: OpenPGP digital signature URL: From teemu.huovila at dovecot.fi Wed Sep 10 11:49:25 2014 From: teemu.huovila at dovecot.fi (Teemu Huovila) Date: Wed, 10 Sep 2014 14:49:25 +0300 Subject: preserving flags for shared mailbox when migrating from cyrus to dovecot In-Reply-To: <54103404.1090507@mur.at> References: <53F4890F.5000008@mur.at> <594B2611-57AD-4464-9BF5-29ED31F545DB@iki.fi> <54103404.1090507@mur.at> Message-ID: <54103AC5.9060207@dovecot.fi> Hello On 09/10/2014 02:20 PM, Jogi Hofm?ller wrote: > again no success. The shared mailbox stays available and working but > the flags will not be synced to the state they had on the original > server. I also tried it without -R but that didn't get me anywhere > either and should be wrong anyways AFAICT. > > Any further ideas anyone or should I prepare our shared mailbox users > that all their email will be unread after migration? I looked at the dovecot -n output attached to your previous mail and I think I spotted some issues. namespace { hidden = no inbox = no list = children location = maildir:/srv/vmail/%%u/Maildir:INDEX=/srv/vmail/%u/shared/%%u:CONTROL=/srv/vmail/%u/shared/%%u:INDEXPVT=/srv/vmail/%u/shared/%%u prefix = shared.%%u. separator = . subscriptions = yes type = shared } The INDEX and INDEXPVT are identical, which means there is no private index. Having the CONTROL defined is also questionable. I suggest you try defining location like this: location = maildir:/srv/vmail/%%u/Maildir:INDEXPVT=/srv/vmail/%u/shared/%%u Also, to make subscriptions work sensibly, set the shared namespace subscriptions = no and then add a placeholder namespace with an empty prefix to contain just the private subscriptions: namespace { prefix = hidden = yes list = no subscriptions=yes } Please read http://wiki2.dovecot.org/SharedMailboxes/Public?highlight=%28INDEXPVT%29#Maildir:_Per-user_.2BAFw-Seen_flag for further details. br, Teemu Huovila From jogi at mur.at Wed Sep 10 13:08:49 2014 From: jogi at mur.at (=?UTF-8?B?Sm9naSBIb2Ztw7xsbGVy?=) Date: Wed, 10 Sep 2014 15:08:49 +0200 Subject: preserving flags for shared mailbox when migrating from cyrus to dovecot In-Reply-To: <54103AC5.9060207@dovecot.fi> References: <53F4890F.5000008@mur.at> <594B2611-57AD-4464-9BF5-29ED31F545DB@iki.fi> <54103404.1090507@mur.at> <54103AC5.9060207@dovecot.fi> Message-ID: <54104D61.3060203@mur.at> Hi Teemu, all, Am 2014-09-10 13:49, schrieb Teemu Huovila: > I looked at the dovecot -n output attached to your previous mail and > I think I spotted some issues. > (...) > The INDEX and INDEXPVT are identical, which means there is no private > index. Having the CONTROL defined is also questionable. I suggest you > try defining location like this: > > location = > maildir:/srv/vmail/%%u/Maildir:INDEXPVT=/srv/vmail/%u/shared/%%u Did that, and didn't change anything. I still have now way to sync flags for shared mailboxes from the old mail server. > Also, to make subscriptions work sensibly, set the shared namespace > subscriptions = no and then add a placeholder namespace with an empty > prefix to contain just the private subscriptions: > > namespace { > prefix = > hidden = yes > list = no > subscriptions=yes >} Alright, thanks for the hint. Cheers, -- J.Hofm?ller Im ?brigen bin ich der Meinung, das Joanneum muss zerschlagen werden! - Barbara Fischer -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: OpenPGP digital signature URL: From ve at vetienne.net Wed Sep 10 13:28:01 2014 From: ve at vetienne.net (Ve (HOME)) Date: Wed, 10 Sep 2014 15:28:01 +0200 Subject: Replication problem In-Reply-To: <54102FD2.3040406@dovecot.fi> References: "\" <4f6c77594a5d5dcfa55799379d9921c1@aprogsys.com>" "\"<540F8779.7090505@vetienne.net>\\\" <54102061.2000105@dovecot.fi>" <54102CB7.5030204@vetienne.net>" <54102FD2.3040406@dovecot.fi> Message-ID: Le 2014-09-10 13:02, Teemu Huovila a ?crit?: > On 09/10/2014 01:49 PM, Vincent ETIENNE wrote: >> Le 10/09/2014 11:56, Teemu Huovila a ?crit : > Cancel that advice. Timo did a change that should make changing the > timeout by hand unnecessary. If you can, try running Dovecot > with this patch http://hg.dovecot.org/dovecot-2.2/rev/647162da8423. > There should be no time outs, even for large mails. > > Do you get any error messages, when there is a timeout? > > br, > Teemu Huovila Have tested with the patch from Timo ( applied to 2.2.13 version ) and have successfully synchronized with a mail double the size of the mail that causes trouble before. So the changes looks correct. But i have not tested that the timeout occured if the link is down or broken. Thanks a lot for the quick response. Very helpful. Vincent ETIENNE From arekm at maven.pl Wed Sep 10 14:00:43 2014 From: arekm at maven.pl (Arkadiusz =?utf-8?q?Mi=C5=9Bkiewicz?=) Date: Wed, 10 Sep 2014 16:00:43 +0200 Subject: dovecot 2.2.13: LMTP delivery with multiple recipients incorrectly mixes users In-Reply-To: <201409011114.06931.arekm@maven.pl> References: <201409011114.06931.arekm@maven.pl> Message-ID: <201409101600.43467.arekm@maven.pl> On Monday 01 of September 2014, Arkadiusz Mi?kiewicz wrote: > Hi. > > I'm using exim that delivers email over LMTP to dovecot 2.2.13. > > I noticed that dovecot LMTP service is sometimes (reare but repeats) mixing > users. Example below. There is one mail > (msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>) that is going > to be delivered to multiple local recipients. What is worse is that dovecot lmtp can sometimes (if permissions allow that) create mail file, in maildir tree, of user B using user A uid/gid! All that because it mixes users. That leads to more problems (like when using filesystem quota. Since user A has his files (by uid/gid) stored in directory of user B. A cannot access them, delete them but they still eat user A quota). Looks to be some major brokeness in dovecot lmtp. (batch_max = 1 should workaround the problem I think but that's not a solution) > Some recipients are delivered properly: > > Sep 1 05:40:33 host dovecot: lmtp(3176): Connect from local > Sep 1 05:40:34 host dovecot: lmtp(3176, gbuser1): TDO+HNDpA1RoDAAA16XVAg: > msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: saved mail to > INBOX Sep 1 05:40:34 host dovecot: lmtp(3176, jpuser2): > TDO+HNDpA1RoDAAA16XVAg: > msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: saved mail to > INBOX Sep 1 05:40:34 host dovecot: lmtp(3176, rkuser3): > TDO+HNDpA1RoDAAA16XVAg: > msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: saved mail to > INBOX Sep 1 05:40:34 host dovecot: lmtp(3176, gbruser4): > TDO+HNDpA1RoDAAA16XVAg: > msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: saved mail to > INBOX Sep 1 05:40:34 host dovecot: lmtp(3176, pbauser5): > TDO+HNDpA1RoDAAA16XVAg: > msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: saved mail to > INBOX Sep 1 05:40:34 host dovecot: lmtp(3176, mwauser6): > TDO+HNDpA1RoDAAA16XVAg: > msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: saved mail to > INBOX Sep 1 05:40:34 host dovecot: lmtp(3176, mdyuser7): > TDO+HNDpA1RoDAAA16XVAg: > msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: saved mail to > INBOX > > but some are not: > > Sep 1 05:40:34 host dovecot: lmtp(3176, lkrzyuser8): Error: > lstat(/var/lib/dovecot/control/gbuser1/.INBOX/dovecot-uidlist.lock) > failed: Permission denied Sep 1 05:40:34 host dovecot: lmtp(3176, > lkrzyuser8): Error: > file_dotlock_create(/var/lib/dovecot/control/gbuser1/.INBOX/dovecot-uidlis > t) failed: Permission denied (euid=28371() egid=17373() > missing +x perm: /var/lib/dovecot/control/gbuser1, dir owned by > 67593:17373 mode=0700) > > Notice it was trying to deliver to user "lkrzyuser8" but it tries to access > some other user files (dovecot-uidlist). euid=28371 is indeed "lkrzyuser8" > but why it tries to access "gbuser1" files? > > Sep 1 05:40:34 host dovecot: lmtp(3176, lkrzyuser8): Error: > lstat(/var/lib/dovecot/control/gbuser1/.INBOX/dovecot-uidlist.lock) > failed: Permission denied Sep 1 05:40:34 host dovecot: lmtp(3176, > lkrzyuser8): Error: > file_dotlock_create(/var/lib/dovecot/control/gbuser1/.INBOX/dovecot-uidlis > t) failed: Permission denied (euid=28371() egid=17373() > missing +x perm: /var/lib/dovecot/control/gbuser1, dir owned by > 67593:17373 mode=0700) Sep 1 05:40:34 host dovecot: lmtp(3176, > lkrzyuser8): TDO+HNDpA1RoDAAA16XVAg: > msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: save failed to > INBOX: BUG: Unknown internal error > > Above is again the same case. > > Sep 1 05:40:34 host dovecot: lmtp(3176, wm1user9): Error: > lstat(/var/lib/dovecot/control/gbuser1/.INBOX/dovecot-uidlist.lock) > failed: Permission denied Sep 1 05:40:34 host dovecot: lmtp(3176, > wm1user9): Error: > file_dotlock_create(/var/lib/dovecot/control/gbuser1/.INBOX/dovecot-uidlis > t) failed: Permission denied (euid=128065() egid=17373() > missing +x perm: /var/lib/dovecot/control/gbuser1, dir owned by > 67593:17373 mode=0700) Sep 1 05:40:34 host dovecot: lmtp(3176, wm1user9): > Error: lstat(/var/lib/dovecot/control/gbuser1/.INBOX/dovecot-uidlist.lock) > failed: Permission denied Sep 1 05:40:34 host dovecot: lmtp(3176, > wm1user9): Error: > file_dotlock_create(/var/lib/dovecot/control/gbuser1/.INBOX/dovecot-uidlis > t) failed: Permission denied (euid=128065() egid=17373() > missing +x perm: /var/lib/dovecot/control/gbuser1, dir owned by > 67593:17373 mode=0700) Sep 1 05:40:34 host dovecot: lmtp(3176, wm1user9): > TDO+HNDpA1RoDAAA16XVAg: > msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: save failed to > INBOX: BUG: Unknown internal error > > And here again the same problem but with user "wm1user9" > > Sep 1 05:40:34 host dovecot: lmtp(3176): Disconnect from local: Successful > quit > > > # doveadm user gbuser1 > field value > uid 67593 > gid 17373 > home /var/mail/gbuser1/ > mail maildir:/var/mail/gbuser1/:CONTROL=/var/lib/dovecot/control/gbuser1 > > > # doveadm user lkrzyuser8 > field value > uid 28371 > gid 17373 > home /var/mail/lkrzyuser8/ > mail > maildir:/var/mail/lkrzyuser8/:CONTROL=/var/lib/dovecot/control/lkrzyuser8 > > > # doveadm user wm1user9 > field value > uid 128065 > gid 17373 > home /var/mail/wm1user9/ > mail > maildir:/var/mail/wm1user9/:CONTROL=/var/lib/dovecot/control/wm1user9 > > > Later exim retries delivery and dovecot lmtp succeeds: > > Sep 1 05:41:34 host dovecot: lmtp(4737): Connect from local > Sep 1 05:41:34 host dovecot: lmtp(4737, lkrzyuser8): > b9F+OsHqA1SBEgAA16XVAg: > msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: saved mail to > INBOX Sep 1 05:41:34 host dovecot: lmtp(4737, wm1user9): > b9F+OsHqA1SBEgAA16XVAg: > msgid=<1ACE53B70631CA45B62348E4EE8757493731A59E at KRMXA41>: saved mail to > INBOX Sep 1 05:41:34 host dovecot: lmtp(4737): Disconnect from local: > Successful quit > > The problem is not reasily repeatable. It happens several times a day for > different users each time (while thousands users are logging in), so I > guess some race condition takes place. > > # dovecot -n > # 2.2.13: /etc/dovecot/dovecot.conf > doveconf: Warning: service auth { client_limit=1000 } is lower than > required under max. load (8000) doveconf: Warning: service anvil { > client_limit=1000 } is lower than required under max. load (6003) # OS: > Linux 3.14.17-1 x86_64 xfs > auth_mechanisms = plain login > auth_username_chars = > abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@= > auth_username_translation = @= > auth_verbose = yes > default_process_limit = 2000 > default_vsz_limit = 512 M > disable_plaintext_auth = no > first_valid_gid = 1500 > first_valid_uid = 1500 > lda_mailbox_autocreate = yes > lmtp_save_to_detail_mailbox = yes > login_greeting = Mail server ready. > mail_location = maildir:/var/mail/%Ln:CONTROL=/var/lib/dovecot/control/%Ln > mail_log_prefix = "%s(%u): session=<%{session}>, " > mail_plugins = zlib quota > namespace { > hidden = no > inbox = yes > location = > prefix = INBOX. > separator = . > type = private > } > passdb { > args = /etc/dovecot/dovecot-sql.conf.ext > driver = sql > } > plugin { > mail_log_events = delete undelete expunge copy mailbox_delete > mailbox_rename quota = fs:User quota:user > quota2 = fs:Group quota:group > } > postmaster_address = postmaster at somwehere.pl > service auth { > unix_listener auth-userdb { > mode = 0666 > } > } > service imap { > process_limit = 2048 > } > service pop3 { > process_limit = 1024 > } > > userdb { > args = /etc/dovecot/dovecot-sql.conf.ext > driver = sql > } > protocol lmtp { > auth_username_format = %Ln > auth_username_translation = > } > protocol imap { > imap_logout_format = bytes=%i/%o > mail_max_userip_connections = 20 > mail_plugins = zlib quota imap_quota mail_log notify > } > protocol pop3 { > mail_max_userip_connections = 20 > mail_plugins = mail_log notify > pop3_client_workarounds = outlook-no-nuls oe-ns-eoh > pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s, > bytes=%i/%o pop3_uidl_format = %Mf > } -- Arkadiusz Mi?kiewicz, arekm / maven.pl From admin at awib.it Wed Sep 10 16:37:28 2014 From: admin at awib.it (admin) Date: Wed, 10 Sep 2014 18:37:28 +0200 Subject: outlook 2013 In-Reply-To: <50A548F3-4501-44E4-ABA4-9762D961D256@webinabox.net.au> References: <20140909203511.Horde.rINh4s8NjgyG0YrUQ-bqMA2@mail.patrickdk.com> <1410310269.20035.83.camel@worklian> <70997954-4E49-4EEF-8648-6DAE3B648C5D@webinabox.net.au> <50A548F3-4501-44E4-ABA4-9762D961D256@webinabox.net.au> Message-ID: <867B438D-E887-457F-94E3-CC5B68CBC6BC@awib.it> Am 10.09.2014 um 06:22 schrieb Trent Lloyd : > I had a much more exciting experience with Outlook for Mac (which is much worse?) > > Changed from Dovecot 0.9 to 2.2 but changed the folder separator from . to \, so that I could have shared folders with dots in the username. > When you do this, it starts creating a new mailbox every time it connects every minute, called like Trash 1, Trash 1 1, Trash 1 1 1, Trash 1 1 1.. I got up to about 40+ appended folder names. It also does this with INBOX, Sent, etc. > > It won?t ever stop doing this, and even if you change the folder separator back it still keeps doing it. Only way to fix is to change the server name which causes it to purge the entire local cache and start over (basically a quick delete/re-add). > > > My other favourite issue with Outlook for Mac was it eating messages, they?d come in, and disappear. Spam filtering was off, no rules setup, they just disappeared, and got deleted from the server. Eish. I am observing something similar; If I use my router (fritz.box) to send incoming fax by mail to a given account on my server, the mail appears and instantly vanishes. I then used a different mail account (completely different server/domain etc.) and the mail stays; and then again, forwarding it a mail address of the domain where this weird behavior was seen, the mail also arrives and disappears. This issue roughly dates back to the beginning of this year; had no time to investigate yet... > > Trent > > On 10 Sep 2014, at 12:15 pm, Trent Lloyd wrote: > >> I have had this problem a lot on my old Dovecot 0.9 system.. it seems to be OK on 2.2 however. >> It?s really noticeable when interacting with another Apple map system. >> >> >> One key thing is the Outlook by default doesn?t immediately purge your deleted items. It lags on that a bit. There are settings to change that. >> >> Trent >> >> >> On 10 Sep 2014, at 8:51 am, Bob Miller wrote: >> >>> Hi Patrick, >>> >>> Thanks for your reply. >>> >>>> I have no idea what your doing to cause this issue :( >>>> >>>> I have a normal install of dovecot running, and I have 3 webmail pages >>>> open, 2 phones using imap, and a thunderbird connected to it. I >>>> started with outlook 2007, then 2010, and now 2013 for the last 2 >>>> years or 3years (I upgraded to it in beta at first). I haven't had any >>>> issues at all, I can delete emails, move emails, ..., and they >>>> instantly change in the other programs. >>> >>> I have several accounts that are used by a variety of different programs >>> and devices, as well, but the only program that gives me any problem is >>> outlook 2013. And not quite consistently, on some few machines I have >>> seen it work the same as any other client. This one particular case has >>> me quite baffled though. >>> >>>> I just use the normal outlook2013 config options for the account, >>>> besides making sure the ssl settings are right. >>>> >>>> I think I have only used it on the 2.2 branch though, what dovecot >>>> version are you using? >>> >>> # dovecot --version >>> 2.2.13 >>> >>> sigh. At least now I know it should be working, so I will keep >>> searching fior a solution... -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5820 bytes Desc: not available URL: From admin at awib.it Wed Sep 10 16:39:54 2014 From: admin at awib.it (admin) Date: Wed, 10 Sep 2014 18:39:54 +0200 Subject: outlook 2013 In-Reply-To: <8B59D382-56E6-4848-BF1F-C72A78EBFCA0@kreme.com> References: <1410296996.20035.51.camel@worklian> <8B59D382-56E6-4848-BF1F-C72A78EBFCA0@kreme.com> Message-ID: Am 10.09.2014 um 05:27 schrieb LuKreme : > On 09 Sep 2014, at 15:09 , Bob Miller wrote: >> I am trying really hard to wrap my head around why people insist on >> using this program? > > Which program? > >> Where I have outlook 2013 users, I have had nothing but problems getting >> their mail to work with imap. my solution has been to set them up with >> pop, which works just like it always has. Or move them to a different >> program. > > That?s odd. The one and only thing that Lookout does pretty well is IMAP. My only issue with Outlook2013 was that they discontinued supporting md5-crypt password method, so it took me a while to find out, what the problem was after updating outlook. > >> Surely people have outlook 2013 connecting via imap to dovecot without >> problems; > > Yep. > >> is there some special trick that google is hiding from me? > > Not really. > > -- > "He loves Nature in spite of what it did to him." - Forrest Tucker -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5820 bytes Desc: not available URL: From listas at adminlinux.com.br Wed Sep 10 17:19:28 2014 From: listas at adminlinux.com.br (Listas@Adminlinux) Date: Wed, 10 Sep 2014 14:19:28 -0300 Subject: My Dsync isn't replicating 'EXPUNGE' IMAP command In-Reply-To: <540F4D46.1000004@adminlinux.com.br> References: <540F4D46.1000004@adminlinux.com.br> Message-ID: <54108820.7040909@adminlinux.com.br> Dsync really is not working for EXPUNGE Imap command. This seems to be a bug in version 2.2.13. Someone else was touched by it? Thanks! Thiago Em 09-09-2014 15:56, Listas at Adminlinux escreveu: > Hi! > > I have two Dovecot-2.2.13 servers with Dsync Replication: server1 and > server2. > > When I execute 'EXPUNGE' on server1 side, the messages with FLAG > \Deleted are expunged only on server1. The message is still present in > Server2. > > Could someone give me a hint reason for this ? > Thanks in advance! > -- > Thiago Henrique > > ====================================================================== > How I reproduce: > > == ON SERVER1 == > > Client: $ telnet 143 > Trying ... > Connected to . > Escape character is '^]'. > Server: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR > LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] MAILBOX1 IMAP/POP3 > server > > Client: AUTH LOGIN > Server: AUTH OK [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 QUOTA] Logged in > > Client: A002 SELECT "INBOX" > Server: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft nonjunk) > * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft > nonjunk \*)] Flags permitted. > * 2 EXISTS > * 0 RECENT > * OK [UNSEEN 1] First unseen. > * OK [UIDVALIDITY 1410284221] UIDs valid > * OK [UIDNEXT 16] Predicted next UID > * OK [HIGHESTMODSEQ 56] Highest > A002 OK [READ-WRITE] Select completed (0.000 secs). > > Client: A003 FETCH 1:* (UID FLAGS) > Server: * 1 FETCH (UID 13 FLAGS (nonjunk)) > * 2 FETCH (UID 15 FLAGS (nonjunk)) > A003 OK Fetch completed. > > Client: A005 STORE 1 +FLAGS \Deleted > Server: * 1 FETCH (FLAGS (\Deleted nonjunk)) > A005 OK Store completed. > > Client: A003 FETCH 1:* (UID FLAGS) > Server: * 1 FETCH (UID 13 FLAGS (\Deleted nonjunk)) > * 2 FETCH (UID 15 FLAGS (nonjunk)) > A003 OK Fetch completed. > > Client: A006 EXPUNGE > Server: * 1 EXPUNGE > A006 OK Expunge completed. > > Client: A007 FETCH 1:* (UID FLAGS) > Server: * 1 FETCH (UID 15 FLAGS (nonjunk)) > A007 OK Fetch completed. > > Client: A008 LOGOUT > Server: * BYE Logging out > A008 OK Logout completed. > Connection closed by foreign host. > > == ON SERVER2 == > > Client: $ telnet 143 > Trying ... > Connected to . > Escape character is '^]'. > Server: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR > LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] MAILBOX2 IMAP/POP3 > server > > Client: AUTH LOGIN > Server: AUTH OK [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 QUOTA] Logged in > > Client: A002 SELECT "INBOX" > Server: * FLAGS (\Answered \Flagged \Deleted \Seen \Draft nonjunk) > * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft > nonjunk \*)] Flags permitted. > * 2 EXISTS > * 0 RECENT > * OK [UNSEEN 1] First unseen. > * OK [UIDVALIDITY 1410284221] UIDs valid > * OK [UIDNEXT 17] Predicted next UID > * OK [HIGHESTMODSEQ 61] Highest > A002 OK [READ-WRITE] Select completed (0.000 secs). > > Client: A003 FETCH 1:* (UID FLAGS) > Server: * 1 FETCH (UID 13 FLAGS (\Deleted nonjunk)) > * 2 FETCH (UID 15 FLAGS (nonjunk)) > A003 OK Fetch completed. > > Client: A008 LOGOUT > Server: * BYE Logging out > A008 OK Logout completed. > Connection closed by foreign host. > > > = My settings = > > * My settins age identical on both server1 and server2, except by > 'listen', 'address' and 'mail_replica' directives. > > # doveconf -n > # 2.2.13 (6bb26098a45c): /etc/dovecot/dovecot.conf > # OS: Linux 3.13.0-30-generic x86_64 Ubuntu 14.04.1 LTS > auth_master_user_separator = * > auth_mechanisms = plain login > auth_username_chars = > abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@= > auth_worker_max_count = 1 > disable_plaintext_auth = no > doveadm_password = secret > doveadm_port = 12345 > listen = server1 > log_path = /var/log/dovecot.log > login_greeting = MAILBOX1 IMAP/POP3 server > mail_fsync = never > mail_gid = dovemail > mail_plugins = " notify replication quota" > mail_uid = dovemail > passdb { > args = /etc/dovecot/dovecot-sql.conf.ext > driver = sql > } > passdb { > args = /etc/dovecot/dovecot-sql-master.conf.ext > driver = sql > master = yes > pass = yes > } > plugin { > mail_replica = tcp:server2:12345 > quota = dict:User quota::file:/var/lib/imap/%n/dovecot-quota > quota_rule = *:storage=1GB > } > protocols = imap pop3 lmtp > service aggregator { > fifo_listener replication-notify-fifo { > user = dovemail > } > unix_listener replication-notify { > user = dovemail > } > } > service auth-worker { > user = $default_internal_user > } > service auth { > client_limit = 1024 > process_limit = 1 > process_min_avail = 1 > } > service doveadm { > inet_listener { > port = 12345 > } > } > service imap { > process_limit = 1024 > process_min_avail = 1 > } > service lmtp { > inet_listener { > address = server1 > port = 24 > } > process_limit = 256 > process_min_avail = 1 > } > service pop3-login { > inet_listener pop3 { > address = server1 > port = 110 > } > } > service pop3 { > process_limit = 256 > process_min_avail = 1 > } > service replicator { > process_min_avail = 1 > } > ssl = no > userdb { > driver = prefetch > } > userdb { > args = /etc/dovecot/dovecot-sql.conf.ext > driver = sql > } > verbose_proctitle = yes > protocol imap { > imap_client_workarounds = tb-extra-mailbox-sep > imap_idle_notify_interval = 2 mins > imap_max_line_length = 64 k > mail_max_userip_connections = 50 > mail_plugins = " notify replication quota imap_quota" > } > protocol lmtp { > mail_fsync = optimized > mail_plugins = " notify replication sieve quota" > } > protocol pop3 { > mail_plugins = " notify replication quota" > } From joliver at john-oliver.net Wed Sep 10 18:31:48 2014 From: joliver at john-oliver.net (John Oliver) Date: Wed, 10 Sep 2014 11:31:48 -0700 Subject: LDAP authentication Message-ID: <20140910183148.GA16679@ns2.sdsitehosting.net> CentOS 6.5, dovecot 2.0.9-7 I was using http://www.linuxmail.info/postfix-dovecot-ldap-centos-5/ to get LDAP auth working. And what's really annoying is, it worked... until I screwed something up and had to pull my work back from a backup. Now it doesn't work :-( [joliver at localhost ~]$ telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN] Dovecot ready. a1 LOGIN testuser1 password a1 NO [AUTHENTICATIONFAILED] Authentication failed. Turn on debugging and see: Sep 10 11:26:58 localhost dovecot: auth: Debug: pam(testuser1,127.0.0.1): lookup service=dovecot Sep 10 11:26:58 localhost dovecot: auth: Debug: pam(testuser1,127.0.0.1): #1/1 style=1 msg=Password: Sep 10 11:27:00 localhost dovecot: auth: pam(testuser1,127.0.0.1): pam_authenticate() failed: Permission denied Sep 10 11:27:00 localhost dovecot: auth: ldap(testuser1,127.0.0.1): invalid credentials Sep 10 11:27:02 localhost dovecot: auth: Debug: client out: FAIL#0111#011user=testuser1 So, I don't know what permission is being denied by PAM, or if that was there or not when this did work. I can access my LDAP server just fine. What else can I check? -- *********************************************************************** * John Oliver http://www.john-oliver.net/ * * * *********************************************************************** From clovis at agr.unicamp.br Wed Sep 10 19:11:37 2014 From: clovis at agr.unicamp.br (Clovis Tristao) Date: Wed, 10 Sep 2014 16:11:37 -0300 Subject: Configure Dovecot Master User In-Reply-To: <540DE091.9040204@adminlinux.com.br> References: <540DCFC4.8060803@agr.unicamp.br> <540DE091.9040204@adminlinux.com.br> Message-ID: <5410A269.20805@agr.unicamp.br> I'm using this setting in dovecot: # dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.29.2.el6.x86_64 x86_64 CentOS release 6.5 (Final) auth_debug = yes auth_debug_passwords = yes auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain disable_plaintext_auth = no mail_location = mbox:~/mail:INBOX=/var/mail/%u mbox_write_locks = fcntl passdb { args = /etc/dovecot/passwd.masterusers driver = passwd-file master = yes pass = yes } passdb { driver = shadow } ssl = no ssl_cert = Hi Clovis, > > try something like this: > > **In this example you should have your users in a MySQL database. > > On /etc/dovecot/conf.d/10-auth.conf file add this: > > # Master login *master-user > auth_master_user_separator = * > # Use for master login > passdb { > args = /etc/dovecot/dovecot-sql-master.conf.ext > driver = sql > master = yes > pass = yes > } > > Create /etc/dovecot/dovecot-sql-master.conf.ext file with this content: > > driver = mysql > connect = host= dbname= > user= password= > default_pass_scheme = MD5-CRYPT > password_query = \ > SELECT Password AS password \ > FROM Users \ > WHERE User = 'master-user' > > user_query = \ > SELECT Password AS password \ > FROM Users \ > WHERE User = 'master-user' > > To do tests: > telnet your-dovecot-server.com 143 > AUTH LOGIN *master-user > > Good Luck > -- > Thiago Henrique > > Em 08-09-2014 12:48, Clovis Tristao escreveu: >> Hi, >> >> Does anyone have any idea or hint how to configure dovecot master user? >> I'm already on it for almost fifteen days and can not find a solution. >> I appreciate any help, >> >> Clovis >> > -- Clovis Tristao - UNICAMP/Faculdade de Engenharia Agricola Administrador de Redes - Secao de Informatica (SINFO) E-mail: clovis at feagri.unicamp.br http://www.feagri.unicamp.br MSN: clovis_tristao33 at hotmail.com Fone: 55(19) 35211031-35211038-35211047-91173116 From pada at posteo.de Wed Sep 10 19:24:13 2014 From: pada at posteo.de (Daniel Parthey) Date: Wed, 10 Sep 2014 21:24:13 +0200 Subject: Configure Dovecot Master User In-Reply-To: <5410A269.20805@agr.unicamp.br> References: <540DCFC4.8060803@agr.unicamp.br> <540DE091.9040204@adminlinux.com.br> <5410A269.20805@agr.unicamp.br> Message-ID: <5410A55D.5060500@posteo.de> Hi Clovis, What do you get in your dovecot debug log when you try to log in? Kind regards Daniel -- https://emailselfdefense.fsf.org https://pgp.mit.edu/pks/lookup?op=get&search=0xB4DD34660B6F0F1B -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From clovis at agr.unicamp.br Wed Sep 10 19:40:01 2014 From: clovis at agr.unicamp.br (Clovis Tristao) Date: Wed, 10 Sep 2014 16:40:01 -0300 Subject: Configure Dovecot Master User In-Reply-To: <5410A55D.5060500@posteo.de> References: <540DCFC4.8060803@agr.unicamp.br> <540DE091.9040204@adminlinux.com.br> <5410A269.20805@agr.unicamp.br> <5410A55D.5060500@posteo.de> Message-ID: <5410A911.9000006@agr.unicamp.br> Hi Daniel, Em 10-09-2014 16:24, Daniel Parthey escreveu: > Hi Clovis, > > What do you get in your dovecot debug log when you try to log in? Sep 10 16:38:18 centosVM dovecot: master: Dovecot v2.0.9 starting up (core dumps disabled) Sep 10 16:38:18 centosVM dovecot: ssl-params: Generating SSL parameters Sep 10 16:38:19 centosVM dovecot: ssl-params: SSL parameters regeneration completed Sep 10 16:38:26 centosVM dovecot: auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth Sep 10 16:38:26 centosVM dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libauthdb_ldap.so Sep 10 16:38:26 centosVM dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_sqlite.so Sep 10 16:38:26 centosVM dovecot: auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libmech_gssapi.so Sep 10 16:38:26 centosVM dovecot: auth: Debug: passwd-file /etc/dovecot/passwd.masterusers: Read 1 users Sep 10 16:38:26 centosVM dovecot: auth: Debug: auth client connected (pid=1492) Sep 10 16:38:42 centosVM dovecot: auth: Debug: client in: AUTH#0111#011PLAIN#011service=imap#011lip=10.0.2.15#011rip=10.0.2.2#011lport=143#011rport=59979#011resp=AG1haWxhZG0qbWFzdGVyAHNpYm5mbyoyODE0 Sep 10 16:38:42 centosVM dovecot: auth: Debug: auth(master,10.0.2.2,master): Master user lookup for login: mailadm Sep 10 16:38:42 centosVM dovecot: auth: Debug: passwd-file(master,10.0.2.2,master): lookup: user=master file=/etc/dovecot/passwd.masterusers Sep 10 16:38:42 centosVM dovecot: auth: passwd-file(master,10.0.2.2,master): unknown user Sep 10 16:38:44 centosVM dovecot: auth: Debug: client out: FAIL#0111#011user=master > > Kind regards > Daniel > Tkx a lot, Clovis -- Clovis Tristao - UNICAMP/Faculdade de Engenharia Agricola Administrador de Redes - Secao de Informatica (SINFO) E-mail: clovis at feagri.unicamp.br http://www.feagri.unicamp.br MSN: clovis_tristao33 at hotmail.com Fone: 55(19) 35211031-35211038-35211047-91173116 From bob at computerisms.ca Wed Sep 10 19:41:16 2014 From: bob at computerisms.ca (Bob Miller) Date: Wed, 10 Sep 2014 12:41:16 -0700 Subject: LDAP authentication In-Reply-To: <20140910183148.GA16679@ns2.sdsitehosting.net> References: <20140910183148.GA16679@ns2.sdsitehosting.net> Message-ID: <1410378076.20035.110.camel@worklian> Hi, > Sep 10 11:27:00 localhost dovecot: auth: pam(testuser1,127.0.0.1): > pam_authenticate() failed: Permission denied > Sep 10 11:27:00 localhost dovecot: auth: ldap(testuser1,127.0.0.1): > invalid credentials I am not clear from this if you are using pam auth first and ldap auth 2nd, or if you are trying to use pam to do your ldap authentication for you. Assuming the former, I would guess that you are either failing the auth_bind, or the attributes you are using for user_filter/pass_filter aren't matching the username format. I would start by checking the settings in your dovecot-ldap.conf file... > Sep 10 11:27:02 localhost dovecot: auth: Debug: client out: > FAIL#0111#011user=testuser1 > > > So, I don't know what permission is being denied by PAM, or if that was > there or not when this did work. I can access my LDAP server just fine. > > What else can I check? > From joliver at john-oliver.net Wed Sep 10 19:45:02 2014 From: joliver at john-oliver.net (John Oliver) Date: Wed, 10 Sep 2014 12:45:02 -0700 Subject: LDAP authentication In-Reply-To: <1410378076.20035.110.camel@worklian> References: <20140910183148.GA16679@ns2.sdsitehosting.net> <1410378076.20035.110.camel@worklian> Message-ID: <20140910194502.GA16910@ns2.sdsitehosting.net> On Wed, Sep 10, 2014 at 12:41:16PM -0700, Bob Miller wrote: > Hi, > > Sep 10 11:27:00 localhost dovecot: auth: pam(testuser1,127.0.0.1): > > pam_authenticate() failed: Permission denied > > Sep 10 11:27:00 localhost dovecot: auth: ldap(testuser1,127.0.0.1): > > invalid credentials > > I am not clear from this if you are using pam auth first and ldap auth > 2nd, or if you are trying to use pam to do your ldap authentication for > you. Assuming the former, I would guess that you are either failing the > auth_bind, or the attributes you are using for user_filter/pass_filter > aren't matching the username format. I would start by checking the > settings in your dovecot-ldap.conf file... [joliver at localhost ~]$ dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.el6.x86_64 x86_64 CentOS release 6.5 (Final) auth_debug = yes auth_username_format = %Lu auth_verbose = yes mail_access_groups = mail mail_location = mbox:~/mail/:INBOX=/var/mail/%u mail_privileged_group = mail mbox_write_locks = fcntl passdb { driver = pam } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocols = imap ssl_cert = References: <1410296996.20035.51.camel@worklian> <8B59D382-56E6-4848-BF1F-C72A78EBFCA0@kreme.com> Message-ID: <1410379215.20035.118.camel@worklian> > That?s odd. The one and only thing that Lookout does pretty well is IMAP. After several hours scouring the net last night, I am surprised to hear that. Certainly has never been my experience with outlook, especially 2013... > > is there some special trick that google is hiding from me? > > Not really. > I went in armed with a list of possible fixes and did battle with the two machines today. started by installing thunderbird and shutting off outlook, which absolutely proved outlook was the problem; as soon as I started up outlook again, thunderbird showed mails being created and deleted every few seconds. Went through my list, everything from A-W (account settings to windows updates). So far so good, it's too early to say it is fixed, but I am past the two hour mark now with no problems... From bob at computerisms.ca Wed Sep 10 20:09:11 2014 From: bob at computerisms.ca (Bob Miller) Date: Wed, 10 Sep 2014 13:09:11 -0700 Subject: LDAP authentication In-Reply-To: <20140910194502.GA16910@ns2.sdsitehosting.net> References: <20140910183148.GA16679@ns2.sdsitehosting.net> <1410378076.20035.110.camel@worklian> <20140910194502.GA16910@ns2.sdsitehosting.net> Message-ID: <1410379751.20035.124.camel@worklian> Hi, > [joliver at localhost ~]$ cat /etc/dovecot/dovecot-ldap.conf.ext > hosts = localhost > base = ou=Users,dc=my,dc=domain > ldap_version = 3 > auth_bind = yes > auth_bind_userdn = uid=%u,ou=Users,dc=my,dc=domain > this looks different than mine. here is my example config file, maybe it helps: hosts = 192.168.26.10:389 debug_level = 0 auth_bind = yes auth_bind_userdn = %Ln at computerisms.com base = dn=computerisms,dn=com scope = subtree user_filter = (&(sAMAccountName=%Ln)) pass_filter = (&(sAMAccountName=%Ln)) From pada at posteo.de Wed Sep 10 20:14:41 2014 From: pada at posteo.de (Daniel Parthey) Date: Wed, 10 Sep 2014 22:14:41 +0200 Subject: Configure Dovecot Master User In-Reply-To: <5410A911.9000006@agr.unicamp.br> References: <540DCFC4.8060803@agr.unicamp.br> <540DE091.9040204@adminlinux.com.br> <5410A269.20805@agr.unicamp.br> <5410A55D.5060500@posteo.de> <5410A911.9000006@agr.unicamp.br> Message-ID: <5410B131.6090800@posteo.de> Am 10.09.2014 um 21:40 schrieb Clovis Tristao: > Sep 10 16:38:26 centosVM dovecot: auth: Debug: passwd-file /etc/dovecot/passwd.masterusers: Read 1 users > Sep 10 16:38:42 centosVM dovecot: auth: Debug: auth(master,10.0.2.2,master): Master user lookup for login: mailadm > Sep 10 16:38:42 centosVM dovecot: auth: Debug: passwd-file(master,10.0.2.2,master): lookup: user=master file=/etc/dovecot/passwd.masterusers > Sep 10 16:38:42 centosVM dovecot: auth: passwd-file(master,10.0.2.2,master): unknown user > Sep 10 16:38:44 centosVM dovecot: auth: Debug: client out: FAIL#0111#011user=master The passdb lookup fails to find user "master" in file /etc/dovecot/passwd.masterusers. This file needs to contain the master usernames and passwords: http://wiki2.dovecot.org/Authentication/MasterUsers Kind regards Daniel -- https://emailselfdefense.fsf.org https://pgp.mit.edu/pks/lookup?op=get&search=0xB4DD34660B6F0F1B -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From joliver at john-oliver.net Wed Sep 10 20:20:56 2014 From: joliver at john-oliver.net (John Oliver) Date: Wed, 10 Sep 2014 13:20:56 -0700 Subject: LDAP authentication In-Reply-To: <1410379751.20035.124.camel@worklian> References: <20140910183148.GA16679@ns2.sdsitehosting.net> <1410378076.20035.110.camel@worklian> <20140910194502.GA16910@ns2.sdsitehosting.net> <1410379751.20035.124.camel@worklian> Message-ID: <20140910202056.GA17027@ns2.sdsitehosting.net> On Wed, Sep 10, 2014 at 01:09:11PM -0700, Bob Miller wrote: > Hi, > > > [joliver at localhost ~]$ cat /etc/dovecot/dovecot-ldap.conf.ext > > hosts = localhost > > base = ou=Users,dc=my,dc=domain > > ldap_version = 3 > > auth_bind = yes > > auth_bind_userdn = uid=%u,ou=Users,dc=my,dc=domain > > > > this looks different than mine. here is my example config file, maybe > it helps: > > hosts = 192.168.26.10:389 > debug_level = 0 > auth_bind = yes > auth_bind_userdn = %Ln at computerisms.com > base = dn=computerisms,dn=com > scope = subtree > user_filter = (&(sAMAccountName=%Ln)) > pass_filter = (&(sAMAccountName=%Ln)) I wish it was possible to kiss someone over the Internet :-) The debug_level helped me immensely... I realized it was literally looking for 'uid' on my LDAP. Changed to 'cn' and all is well! THANK YOU!!! -- *********************************************************************** * John Oliver http://www.john-oliver.net/ * * * *********************************************************************** From fuckspam at wheres5.com Wed Sep 10 20:43:14 2014 From: fuckspam at wheres5.com (Hoggins!) Date: Wed, 10 Sep 2014 22:43:14 +0200 Subject: Dovecot replication Message-ID: <5410B7E2.6060406@wheres5.com> Hello list, I'm trying to achieve very simple replication, but I'm not sure if I'm starting the good way. I have two Dovecot servers that use the same GlusterFS storage. Of course, the indexes get corrupted eventually, even if I apply an "NFS-like" configuration. So I'd like to synchronize my two servers with each other. I'm trying to follow this page : http://wiki2.dovecot.org/Replication, but I have to admit that it's not really self-explanatory. I got several errors, so I decided to start fresh, and that is why I'm not giving you any configuration, but I prefer asking if I have the prerequisites. The page states that my userdb should have "user listing", and that you can check it by issuing `doveadm user '*'`. But I don't know what it's supposed to produce, apart from my userlist (my userdb is the system passwd file). As my servers are located on the same private LAN, I decided I would not go with the SSH replication solution, but with the simple mutual TCP connection... Maybe this is a wrong start. Any help will be appreciated. Thanks in advance ! -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From jerry at seibercom.net Wed Sep 10 20:48:14 2014 From: jerry at seibercom.net (Jerry) Date: Wed, 10 Sep 2014 16:48:14 -0400 Subject: outlook 2013 In-Reply-To: <1410379215.20035.118.camel@worklian> References: <1410296996.20035.51.camel@worklian> <8B59D382-56E6-4848-BF1F-C72A78EBFCA0@kreme.com> <1410379215.20035.118.camel@worklian> Message-ID: <20140910164814.45a8a0c9@scorpio> On Wed, 10 Sep 2014 13:00:15 -0700, Bob Miller stated: >> That?s odd. The one and only thing that Lookout does pretty well is IMAP. > >After several hours scouring the net last night, I am surprised to hear >that. Certainly has never been my experience with outlook, especially >2013... > >> > is there some special trick that google is hiding from me? >> >> Not really. > >I went in armed with a list of possible fixes and did battle with the >two machines today. started by installing thunderbird and shutting off >outlook, which absolutely proved outlook was the problem; as soon as I >started up outlook again, thunderbird showed mails being created and >deleted every few seconds. Went through my list, everything from A-W >(account settings to windows updates). So far so good, it's too early to >say it is fixed, but I am past the two hour mark now with no problems... I have absolutely no problem with MS Outlook 2013 and Dovecot and I have it on four machines. I did have to tweak the root folder path though once. I am not sure exactly why, but that took care of everything. -- Jerry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: not available URL: From joliver at john-oliver.net Wed Sep 10 22:37:51 2014 From: joliver at john-oliver.net (John Oliver) Date: Wed, 10 Sep 2014 15:37:51 -0700 Subject: Dovecot can't read mail, creates duplicate directories Message-ID: <20140910223751.GA17417@ns2.sdsitehosting.net> CentOS 6.5, dovecot 2.0.9-7 I used http://www.linuxmail.info/postfix-dovecot-ldap-centos-5/ to configure LDAP authentication for postfix and dovecot. I can log in to dovecot via IMAP, but it cannot read messages. It does wind up creating alternate directories though: [joliver at localhost ~]$ sudo ls -l /var/vmail/ total 8 drwx------. 3 vmail vmail 4096 Sep 10 15:00 testuser1 drwx------. 3 vmail vmail 4096 Sep 10 14:59 testUser1 [joliver at localhost ~]$ sudo ls -l /var/vmail/testuser1/ total 4 drwx------. 3 vmail vmail 4096 Sep 10 15:00 mail [joliver at localhost ~]$ sudo ls -l /var/vmail/testuser1/mail/ total 0 [joliver at localhost ~]$ sudo ls -l /var/vmail/testUser1/ total 4 drwx------. 5 vmail vmail 4096 Sep 10 14:59 Maildir [joliver at localhost ~]$ sudo ls -l /var/vmail/testUser1/Maildir/ total 12 drwx------. 2 vmail vmail 4096 Sep 10 14:59 cur drwx------. 2 vmail vmail 4096 Sep 10 15:01 new drwx------. 2 vmail vmail 4096 Sep 10 15:01 tmp [joliver at localhost ~]$ sudo ls -l /var/vmail/testUser1/Maildir/new/ total 8 -rw-------. 1 vmail vmail 444 Sep 10 15:25 1410387938.Vfd02I1e89M2893.localhost.localdomain -rw-------. 1 vmail vmail 453 Sep 10 15:26 1410387970.Vfd02I1e8cM685475.localhost.localdomain [joliver at localhost ~]$ telnet localhost 143 Trying ::1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN] Dovecot ready. a1 LOGIN testuser1 password a1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS] Logged in a2 EXAMINE INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS ()] Read-only mailbox. * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1410388142] UIDs valid * OK [UIDNEXT 1] Predicted next UID * OK [HIGHESTMODSEQ 1] Highest a2 OK [READ-ONLY] Select completed. [joliver at localhost ~]$ cat /etc/dovecot/conf.d/auth-ldap.conf.ext auth_username_format = %Lu passdb { driver = ldap args = /etc/dovecot/dovecot-ldap.conf.ext } userdb { driver = static args = uid=504 gid=505 home=/var/vmail/%u } [joliver at localhost ~]$ grep vmail /etc/passwd vmail:x:504:505:Vmail:/var/vmail:/sbin/nologon -- *********************************************************************** * John Oliver http://www.john-oliver.net/ * * * *********************************************************************** From nobody73 at riseup.net Wed Sep 10 22:39:20 2014 From: nobody73 at riseup.net (nobody73) Date: Thu, 11 Sep 2014 00:39:20 +0200 Subject: dovecot imap auth method issue Message-ID: <5410D318.4080203@riseup.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi List , I run Debian GNU/Linux 7 and i have followed the guide on workaround dot org and at the end of it i have authentications issues with thunderbird .On workaround there is a local test for authentication and it was successfull .Thunderbird says: "the IMAP server doesn't support the selected authentication method ,please change the authetntication method .... " I have tried all of clear, starttls and ssl/tls . dovecot 10-auth.conf is set: > disable_plaintext_auth = yes auth_mechanisms = plain login !include > auth-sql.conf.ext auth-sql.conf.ex has: > passdb { driver = sql > > # Path for SQL configuration file, see > example-config/dovecot-sql.conf.ext args = > /etc/dovecot/dovecot-sql.conf.ext } > userdb { driver = static args = uid=vmail gid=vmail > home=/var/vmail/%d/%n } My dovecot-sql.conf.ext content is: > driver = mysql connect = host=127.0.0.1 dbname=maildb user=userdb > password=123456789 default_pass_scheme = PLAIN-MD5 password_query > = SELECT email as user, password FROM virtual_users WHERE > email='%u'; and dovecot -n says: > # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-686-pae i686 > Debian 7.6 ext3 auth_mechanisms = plain login mail_location = > maildir:/var/vmail/%d/%n/Maildir 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 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 = separator = } passdb { args = > /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = > ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = " imap sieve > pop3" service auth { unix_listener /var/spool/postfix/private/auth > { group = postfix mode = 0660 user = postfix } } service imap-login > { inet_listener imap { port = 143 } inet_listener imaps { port = > 993 ssl = yes } } service pop3-login { inet_listener pop3 { port = > 110 } inet_listener pop3s { port = 995 ssl = yes } } ssl_cert = > userdb { args = uid=vmail gid=vmail home=/var/vmail/%d/%n driver = > static } protocol lda { mail_plugins = " sieve" } All help will be appreciated Regards Gab - -- Key fingerprint = D8E8 7374 49EA 8017 EC52 AD73 0294 F341 FF66 9495 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iF4EAREKAAYFAlQQ0xgACgkQApTzQf9mlJV/9AD9GI4J7CJ3bBgpDutdK9Zert/z 9PsbpN/BJQ0fB8APuBIA/RFD5s5D5aCR4QUnXLzG/e25Jb/4HwxJ+X4QZdm5Yr/Y =NPMR -----END PGP SIGNATURE----- From jtam.home at gmail.com Wed Sep 10 22:43:15 2014 From: jtam.home at gmail.com (Joseph Tam) Date: Wed, 10 Sep 2014 15:43:15 -0700 (PDT) Subject: Configure Dovecot Master User In-Reply-To: References: Message-ID: On Wed, 10 Sep 2014, Clovis Tristao writes: > userdb { > args = allow_all_users=yes master_user=%u > driver = static > } > ... > > I still can not authenticate with the master user, any suggestions or tips? Just a wild-ass guess, but shouldn't "master_user=%u" be something like "master_user=muser" where "muser" is the master user as defined in your master password file? Joseph Tam From peter at tripleseven.us Thu Sep 11 04:34:46 2014 From: peter at tripleseven.us (Peter Cook) Date: Wed, 10 Sep 2014 23:34:46 -0500 Subject: Dovecot can't read mail, creates duplicate directories In-Reply-To: <20140910223751.GA17417@ns2.sdsitehosting.net> References: <20140910223751.GA17417@ns2.sdsitehosting.net> Message-ID: <54112666.9000409@tripleseven.us> On 9/10/2014 5:37 PM, John Oliver wrote: > CentOS 6.5, dovecot 2.0.9-7 > > I used http://www.linuxmail.info/postfix-dovecot-ldap-centos-5/ to > configure LDAP authentication for postfix and dovecot. > > I can log in to dovecot via IMAP, but it cannot read messages. It does > wind up creating alternate directories though: > > [joliver at localhost ~]$ sudo ls -l /var/vmail/ > total 8 > drwx------. 3 vmail vmail 4096 Sep 10 15:00 testuser1 > drwx------. 3 vmail vmail 4096 Sep 10 14:59 testUser1 > [joliver at localhost ~]$ sudo ls -l /var/vmail/testuser1/ > total 4 > drwx------. 3 vmail vmail 4096 Sep 10 15:00 mail > [joliver at localhost ~]$ sudo ls -l /var/vmail/testuser1/mail/ > total 0 > [joliver at localhost ~]$ sudo ls -l /var/vmail/testUser1/ > total 4 > drwx------. 5 vmail vmail 4096 Sep 10 14:59 Maildir > [joliver at localhost ~]$ sudo ls -l /var/vmail/testUser1/Maildir/ > total 12 > drwx------. 2 vmail vmail 4096 Sep 10 14:59 cur > drwx------. 2 vmail vmail 4096 Sep 10 15:01 new > drwx------. 2 vmail vmail 4096 Sep 10 15:01 tmp > [joliver at localhost ~]$ sudo ls -l /var/vmail/testUser1/Maildir/new/ > total 8 > -rw-------. 1 vmail vmail 444 Sep 10 15:25 > 1410387938.Vfd02I1e89M2893.localhost.localdomain > -rw-------. 1 vmail vmail 453 Sep 10 15:26 > 1410387970.Vfd02I1e8cM685475.localhost.localdomain > > [joliver at localhost ~]$ telnet localhost 143 > Trying ::1... > Connected to localhost. > Escape character is '^]'. > * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE > IDLE STARTTLS AUTH=PLAIN] Dovecot ready. > a1 LOGIN testuser1 password > a1 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE > IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND > UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE > QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS] > Logged in > a2 EXAMINE INBOX > * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) > * OK [PERMANENTFLAGS ()] Read-only mailbox. > * 0 EXISTS > * 0 RECENT > * OK [UIDVALIDITY 1410388142] UIDs valid > * OK [UIDNEXT 1] Predicted next UID > * OK [HIGHESTMODSEQ 1] Highest > a2 OK [READ-ONLY] Select completed. > > [joliver at localhost ~]$ cat /etc/dovecot/conf.d/auth-ldap.conf.ext > auth_username_format = %Lu > > passdb { > driver = ldap > args = /etc/dovecot/dovecot-ldap.conf.ext > } > > userdb { > driver = static > args = uid=504 gid=505 home=/var/vmail/%u > } > > [joliver at localhost ~]$ grep vmail /etc/passwd > vmail:x:504:505:Vmail:/var/vmail:/sbin/nologon > Bump, been having the same troubles configuring this in dovecot. From eric at ericabrahamsen.net Thu Sep 11 08:30:52 2014 From: eric at ericabrahamsen.net (Eric Abrahamsen) Date: Thu, 11 Sep 2014 16:30:52 +0800 Subject: minimal configuration for lucene fts References: <878ultwndu.fsf@ericabrahamsen.net> Message-ID: <87ppf2zhhf.fsf@ericabrahamsen.net> Eric Abrahamsen writes: > Hi, > > I'm using dovecot (version 2.2.13 on archlinux) in the simplest, > no-brainer way possible. It sits between mbsync, which I use to fetch > mail from servers, and Gnus, my MUA. Both mbsync and Gnus connect to > dovecot with an invocation like this: > > /usr/lib/dovecot/imap -o mail_location=maildir:$HOME/.mail/ea/ > > I have three different mail accounts, all that changes is the final > directory on the mail_location path above. > > I haven't touched anything else: there's no running daemon, no > configuration, no user database, no PAM, no nothing. > > Now I'm trying to set up text searching via lucene, but all the examples > I've seen online assume a full running daemon and user accounts. I tried > to fake it by running: > > doveadm index -u eric at localhost -q INBOX > -o mail_location-maildir:/home/eric/.mail/ea > > but it was clearly expecting a user database. > > Is there any way to create text indexes for my three different accounts, > in their respective directories, without fully setting up a running > dovecot? I'll do that if I have to, but my current setup works great, > and is very simple, and I'd like to keep it simple if I can. > > Thanks! > Eric I figured there probably wasn't any way to do this, and just set up dovecot properly, running as a daemon. E From eric at ericabrahamsen.net Thu Sep 11 08:37:12 2014 From: eric at ericabrahamsen.net (Eric Abrahamsen) Date: Thu, 11 Sep 2014 16:37:12 +0800 Subject: charset-specific searches, and continuation lines References: <87ha0nwxjl.fsf@ericabrahamsen.net> <20140904120846.Horde.uun-eIVC9Omg0Gm5HI2rxQ5@bigworm.curecanti.org> <87fvg6olvm.fsf@ericabrahamsen.net> <20140904205937.Horde.2qcxngzCf7IHttpmcW4yGw7@bigworm.curecanti.org> Message-ID: <87lhpqzh6v.fsf@ericabrahamsen.net> Michael M Slusarz writes: > Quoting Eric Abrahamsen : > >> While I've got you here, I hope you'll answer one more question: what's >> the format for searching multiple terms with non-ascii strings? Is it >> possible in one run to find a utf-8 encoded subject, and a utf-8 encoded >> body? > > IMAP interaction would look like this: > > C: . UID SEARCH CHARSET UTF-8 SUBJECT {4} > S: +OK > C: a?b BODY {4} > S: +OK > C: a?b > S: * SEARCH XXX > S: . OK > > Even better... if the server supports LITERAL+, you don't have to wait > for the synchronizing literal which prevents the need to wait for 2 > round-trips from the server: > > C: . UID SEARCH CHARSET UTF-8 SUBJECT {4+} > C: a?b BODY {4+} > C: a?b[CRLF] > S: * SEARCH XXX > S: . OK > > michael One other question: I've set up full text search indexing via Lucene, and it works great. But how is this index encoded? Specifically, if I use the above method to search for non-ascii strings, am I still benefiting from the speedups of the search index? I know that some people who are indexing non-ascii, non-UTF-8 messages are running them through some sort of decoder to force them into UTF-8, so that Lucene can index them properly. Is this still necessary if I'm using the method above? Thanks! Eric From fuckspam at wheres5.com Thu Sep 11 09:00:00 2014 From: fuckspam at wheres5.com (Hoggins!) Date: Thu, 11 Sep 2014 11:00:00 +0200 Subject: Dovecot HA Message-ID: <54116490.1010603@wheres5.com> Hello everyone, Following my previous message about replication (I'm still stuck), I was wondering in a more general way how to achieve high availability with Dovecot, and how to store the mail data. Do you have some thoughts about this ? Maybe one or two links leading to people who already have ideas or experience ? I don't host a big e-mail service, nor have a lot of clients connecting. I just need to ensure that data is always available, from the storage to the actual service. Thanks in advance. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From philippbruell at posteo.de Tue Sep 9 15:15:06 2014 From: philippbruell at posteo.de (Philipp Bruell) Date: Tue, 09 Sep 2014 17:15:06 +0200 Subject: Dict protocol RFC Message-ID: <540F197A.9020301@posteo.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, does someone know if there is a RFC protocol description of the dict protocol that dovecot is using for auth/quota/... requests? Haven't found anything on google yet. Best regards, Philipp -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUDxl6AAoJEDL/SWo0Ta8F8nUH/1HvEwZQf7pd9/VMFdiThre2 T7M72ciqn/40uImdaxth3t1oWXnIcPMOR8dO2LVOX4nRUErDYPoVeL3T7mgyvoG5 oCNDxwJepIXFeW+pEKfXLM0GUGhi5xeUvwcahcv36yyMmC+YVR2+e14daZlp6FNf 4m5ZlLJnFzCiH29qJ4v9WATeybdasWtpQQzjTTmevtK/+9lPqDToIDoqo309F/Wc QQJqZCnPhUu0p8Nvg5qTMA6mwOz2NxtE/uQSuEg8clS30O56tqWKWBPvAeGsvtDM Y6BMqNK1oAo9AEZbYtf82mIG1wn5ny1ZYVocf8kVIaXDJWyMGM1PqDYae/5CjrE= =XI9B -----END PGP SIGNATURE----- From rs at sys4.de Thu Sep 11 10:30:21 2014 From: rs at sys4.de (Robert Schetterer) Date: Thu, 11 Sep 2014 12:30:21 +0200 Subject: Dovecot HA In-Reply-To: <54116490.1010603@wheres5.com> References: <54116490.1010603@wheres5.com> Message-ID: <541179BD.9060707@sys4.de> Am 11.09.2014 um 11:00 schrieb Hoggins!: > Hello everyone, > > Following my previous message about replication (I'm still stuck), I was > wondering in a more general way how to achieve high availability with > Dovecot, and how to store the mail data. > > Do you have some thoughts about this ? Maybe one or two links leading to > people who already have ideas or experience ? > > I don't host a big e-mail service, nor have a lot of clients connecting. > I just need to ensure that data is always available, from the storage to > the actual service. > > Thanks in advance. > please search list archive Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From wdgarc88 at gmail.com Thu Sep 11 11:21:16 2014 From: wdgarc88 at gmail.com (Edwardo Garcia) Date: Thu, 11 Sep 2014 21:21:16 +1000 Subject: usenet/imap Message-ID: Halo, Has anyones had experiences with feeding usenet into imap folders, we like to have some group for all user, any problem with message limit? We only want the text newsgroups? From e1c1bac6253dc54a1e89ddc046585792 at posteo.net Thu Sep 11 13:36:36 2014 From: e1c1bac6253dc54a1e89ddc046585792 at posteo.net (Philipp) Date: Thu, 11 Sep 2014 15:36:36 +0200 Subject: replicating (manage)sieve - no symlink on =?UTF-8?Q?replica=3F?= Message-ID: <5aac7554cee68f3b811b38ad3b2b232e@posteo.de> 2.2.13/0.4.2, both from source-tarball, no fancy options. tcp-replication between two nodes and following plugin parameters (same on both sides, except the ip-addr) plugin { sieve_before = /home/ssfn/etc/dovecot/sieve.default sieve_global_dir = /home/ssfn/etc/dovecot sieve = ~/.dovecot.sieve sieve_dir = ~/.sieve sieve_extensions = +vnd.dovecot.duplicate sieve_duplicate_period = 6h mail_replica = tcp:10.66.50.15:9993 } mail_location = sdbox:/home/ssfn/var/mail/boxes/%n mail_home = /home/ssfn/var/mail/boxes/%n Testbed: user getting first email delivered, the subdir %n/.sieve/tmp is automatically created as expected. User logs into managesieve on node1 and uploads a script. The %n/.sieve/managesieve.sieve and the symlink .dovecot.sieve -> .sieve/managesieve.sieve is created as expected. One node2 (via replica) happens: automatically create %n/.sieve/tmp automatically create/sync %n/.sieve/managesieve.sieve just NOT the symlink .dovecot.sieve -> .sieve/managesieve.sieve Logfiles for lmtp,doveadm,dsync-local dont indicate an error why it could not create the link or such, to me it looks like it wouldnt even try. mail-syncing works flawlessly (for delivery, just read about the expunge .. hum.) I tried to force a full-resync via doveadm replicator afterwards, to no change on the matter. Any input? Log from node2 after the moment managesieve saves everything correctly on node1: Sep 11 15:20:12 doveadm(10.66.30.15,ssfntest): Debug: auth input: user=ssfntest Sep 11 15:20:12 doveadm(10.66.30.15,ssfntest): Debug: auth input: ssfntest Sep 11 15:20:12 doveadm(10.66.30.15,ssfntest): Debug: Added userdb setting: plugin/=yes Sep 11 15:20:12 doveadm(10.66.30.15,ssfntest): Debug: Effective uid=993, gid=993, home=/home/ssfn/var/mail/boxes/ssfntest Sep 11 15:20:12 doveadm(10.66.30.15,ssfntest): Debug: Namespace inbox: type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=sdbox:/home/ssfn/var/mail/boxes/ssfntest:INDEX=/home/ssfn/var/mail/index/ssfntest:ALT=/home/ssfn/var/mail/alternate/ssfntest Sep 11 15:20:12 doveadm(10.66.30.15,ssfntest): Debug: fs: root=/home/ssfn/var/mail/boxes/ssfntest, index=/home/ssfn/var/mail/index/ssfntest, indexpvt=, control=, inbox=, alt=/home/ssfn/var/mail/alternate/ssfntest Sep 11 15:20:12 dsync-server(ssfntest): Debug: Namespace : Using permissions from /home/ssfn/var/mail/boxes/ssfntest: mode=0700 gid=default Sep 11 15:20:12 dsync-server(ssfntest): Debug: doveadm-sieve: Iterating Sieve mailbox attributes Sep 11 15:20:12 dsync-server(ssfntest): Debug: sieve: Pigeonhole version 0.4.2 initializing Sep 11 15:20:12 dsync-server(ssfntest): Debug: sieve-storage: using active sieve script path: /home/ssfn/var/mail/boxes/ssfntest/.dovecot.sieve Sep 11 15:20:12 dsync-server(ssfntest): Debug: sieve-storage: using sieve script storage directory: /home/ssfn/var/mail/boxes/ssfntest/.sieve Sep 11 15:20:12 dsync-server(ssfntest): Debug: sieve-storage: permission lookup failed from /home/ssfn/var/mail/boxes/ssfntest/.sieve Sep 11 15:20:12 dsync-server(ssfntest): Debug: sieve-storage: created storage directory /home/ssfn/var/mail/boxes/ssfntest/.sieve/tmp Sep 11 15:20:12 dsync-server(ssfntest): Debug: sieve-storage: relative path to sieve storage in active link: .sieve/ Sep 11 15:20:12 dsync-server(ssfntest): Debug: sieve: script file /home/ssfn/var/mail/boxes/ssfntest/.sieve/managesieve.sieve not found Sep 11 15:20:12 dsync-server(ssfntest): Debug: doveadm-sieve: Value missing for key `vendor/vendor.dovecot/pvt/server/sieve/files/managesieve' (last change: 1970-01-01 01:00:00) Sep 11 15:20:13 dsync-server(ssfntest): Debug: doveadm-sieve: Assigned value for key `vendor/vendor.dovecot/pvt/server/sieve/files/managesieve' FS tree node2 after that: [..boxes]# find ssfntest -ls|grep -v mailb 24442 4 drwx------ 4 ssfnimp dlagimp 4096 Sep 11 15:20 ssfntest 21048 4 drwx------ 3 ssfnimp dlagimp 4096 Sep 11 15:20 ssfntest/.sieve 21052 4 drwx------ 2 ssfnimp dlagimp 4096 Sep 11 15:20 ssfntest/.sieve/tmp 21056 4 -rw------- 1 ssfnimp dlagimp 69 Sep 11 15:20 ssfntest/.sieve/managesieve.sieve 21016 0 lrwxrwxrwx 1 ssfnimp dlagimp 38 Sep 11 15:05 ssfntest/dbox-alt-root -> /home/dlag/var/mail/alternate/ssfntest FS tree node1 "before": [..boxes]# find ssfntest -ls|grep -v mailb 1835841 4 drwx------ 4 ssfnimp ssfnimp 4096 Sep 11 15:20 ssfntest 1835861 0 lrwxrwxrwx 1 ssfnimp ssfnimp 24 Sep 11 15:05 ssfntest/.dovecot.sieve -> .sieve/managesieve.sieve 1835854 4 -rw------- 1 ssfnimp ssfnimp 8 Sep 11 15:05 ssfntest/dovecot-uidvalidity 1835856 4 drwx------ 3 ssfnimp ssfnimp 4096 Sep 11 15:20 ssfntest/.sieve 1835857 4 drwx------ 2 ssfnimp ssfnimp 4096 Sep 11 15:20 ssfntest/.sieve/tmp 1835860 4 -rw------- 1 ssfnimp ssfnimp 69 Sep 11 15:20 ssfntest/.sieve/managesieve.sieve 1835846 0 lrwxrwxrwx 1 ssfnimp ssfnimp 38 Sep 11 15:05 ssfntest/dbox-alt-root -> /home/ssfn/var/mail/alternate/ssfntest From e1c1bac6253dc54a1e89ddc046585792 at posteo.net Thu Sep 11 13:44:43 2014 From: e1c1bac6253dc54a1e89ddc046585792 at posteo.net (Philipp) Date: Thu, 11 Sep 2014 15:44:43 +0200 Subject: My Dsync isn't replicating 'EXPUNGE' IMAP command In-Reply-To: <54108820.7040909@adminlinux.com.br> References: <540F4D46.1000004@adminlinux.com.br> <54108820.7040909@adminlinux.com.br> Message-ID: <8dad1690d4d014a181b05db5bf96bd75@posteo.de> Am 10.09.2014 19:19 schrieb Listas at Adminlinux: > Dsync really is not working for EXPUNGE Imap command. This seems to > be a bug in version 2.2.13. Someone else was touched by it? Just tried that with roundcube and 'doveadm expunge ...' on a fresh 2.2.13 with mail_replica:tcp; works as expected. Didnt try the manual dance from 'listas'. From clovis at agr.unicamp.br Thu Sep 11 14:37:04 2014 From: clovis at agr.unicamp.br (Clovis Tristao) Date: Thu, 11 Sep 2014 11:37:04 -0300 Subject: Configure Dovecot Master User In-Reply-To: <5410B131.6090800@posteo.de> References: <540DCFC4.8060803@agr.unicamp.br> <540DE091.9040204@adminlinux.com.br> <5410A269.20805@agr.unicamp.br> <5410A55D.5060500@posteo.de> <5410A911.9000006@agr.unicamp.br> <5410B131.6090800@posteo.de> Message-ID: <5411B390.1080308@agr.unicamp.br> Hi, Daniel, My testing, # telnet My_IP My_Port-143 Trying 143.106.74.228... Connected to My_IP. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready. a login mailadm*master master_password a NO [AUTHENTICATIONFAILED] Authentication failed. a login clovis pass_user a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS] Logged in This sequence of commands is correct? When I use a normal user without privileges passwd based authentication it does. Oh my good, I'm going crazy with this. :-) Clovis Em 10-09-2014 17:14, Daniel Parthey escreveu: > Am 10.09.2014 um 21:40 schrieb Clovis Tristao: >> Sep 10 16:38:26 centosVM dovecot: auth: Debug: passwd-file /etc/dovecot/passwd.masterusers: Read 1 users >> Sep 10 16:38:42 centosVM dovecot: auth: Debug: auth(master,10.0.2.2,master): Master user lookup for login: mailadm >> Sep 10 16:38:42 centosVM dovecot: auth: Debug: passwd-file(master,10.0.2.2,master): lookup: user=master file=/etc/dovecot/passwd.masterusers >> Sep 10 16:38:42 centosVM dovecot: auth: passwd-file(master,10.0.2.2,master): unknown user >> Sep 10 16:38:44 centosVM dovecot: auth: Debug: client out: FAIL#0111#011user=master > The passdb lookup fails to find user "master" in file > /etc/dovecot/passwd.masterusers. This file needs to contain the master > usernames and passwords: > > http://wiki2.dovecot.org/Authentication/MasterUsers > > Kind regards > Daniel -- Clovis Tristao - UNICAMP/Faculdade de Engenharia Agricola Administrador de Redes - Secao de Informatica (SINFO) E-mail: clovis at feagri.unicamp.br http://www.feagri.unicamp.br MSN: clovis_tristao33 at hotmail.com Fone: 55(19) 35211031-35211038-35211047-91173116 From mcguire at neurotica.com Thu Sep 11 14:39:59 2014 From: mcguire at neurotica.com (Dave McGuire) Date: Thu, 11 Sep 2014 10:39:59 -0400 Subject: usenet/imap In-Reply-To: References: Message-ID: <5411B43F.5070606@neurotica.com> On 09/11/2014 07:21 AM, Edwardo Garcia wrote: > Has anyones had experiences with feeding usenet into imap folders, we > like to have some group for all user, any problem with message limit? > We only want the text newsgroups? I haven't, but I'm intrigued by the concept. Please summarize back here if you make any progress on this. -Dave -- Dave McGuire, AK4HZ/3 New Kensington, PA From bind at enas.net Thu Sep 11 15:48:13 2014 From: bind at enas.net (Urban Loesch) Date: Thu, 11 Sep 2014 17:48:13 +0200 Subject: Problem with virtual folders Message-ID: <5411C43D.5060201@enas.net> Hi, I'm trying to activate some virtual folders on a new installed dovecot server. My plan is to have two virtual folders like "All" and perhaps "Unseen", like Gmail style for the first step. - All: lists me all messages in the users mailbox - Unseen: all unseen messages in the users mailbox I'm using dovecot EE Release: ii dovecot-ee-core 1:2.2.13.8-1 amd64 secure mail server that supports mbox, maildir, dbox and mdbox mailboxes ii dovecot-ee-imapd 1:2.2.13.8-1 amd64 secure IMAP server that supports mbox, maildir, dbox and mdbox mailboxes ii dovecot-ee-lmtpd 1:2.2.13.8-1 amd64 secure LMTP server for Dovecot ii dovecot-ee-managesieved 0.4.3-1 amd64 secure ManageSieve server for Dovecot ii dovecot-ee-mysql 1:2.2.13.8-1 amd64 MySQL support for Dovecot ii dovecot-ee-sieve 0.4.3-1 amd64 sieve filters support for Dovecot But I can't get it to work. I can see the virtual folders in my Thunderbird, but the folders are empty and can't find any errors in mail log. I also tried it with "mail_debug = yes". Below is my doveconf -n: ... # 2.2.13.8 (71cc347a687c+): /etc/dovecot/dovecot.conf # OS: Linux 3.4.67-vs2.3.3.9-rol-em64t-efigpt x86_64 Debian 7.6 ext4 auth_cache_negative_ttl = 0 auth_cache_ttl = 0 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes deliver_log_format = msgid=%m: %$ %p %w disable_plaintext_auth = no login_trusted_networks = $INTERNAL mail_debug = yes mail_gid = mailstore mail_location = mdbox:/home/vmail/%d/%n:INDEX=/home/dovecotindex/%d/%n mail_log_prefix = "%s(%u pid:%p session:<%{session}>): " mail_plugins = " quota mail_log notify acl zlib stats virtual" mail_shared_explicit_inbox = yes mail_uid = mailstore 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 mdbox_rotate_size = 15 M namespace { list = children location = mdbox:/home/vmail/%%d/%%n:INDEX=/home/dovecotindex/%%d/%%n prefix = [shared]/%%u/ separator = / subscriptions = yes type = shared } namespace { hidden = no inbox = no list = children location = virtual:/home/virtual:INDEX=MEMORY prefix = [virtual]/ separator = / subscriptions = yes type = private } namespace inbox { inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Sent { auto = subscribe special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / subscriptions = yes type = private } passdb { args = /etc/dovecot/dovecot-sql-account.conf driver = sql } plugin { acl = vfile acl_shared_dict = file:/home/vmail/%d/shared-mailboxes mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change save mailbox_create append mail_log_fields = uid box msgid size from mail_log_group_events = no quota = dict:Storage used::file:%h/dovecot-quota quota_rule2 = INBOX/Trash:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_max_redirects = 15 stats_command_min_time = 1 mins stats_domain_min_time = 12 hours stats_ip_min_time = 12 hours stats_memory_limit = 32 M stats_refresh = 30 secs stats_session_min_time = 15 mins stats_track_cmds = yes stats_user_min_time = 1 hours zlib_save = gz zlib_save_level = 9 } protocols = imap lmtp sieve service auth { unix_listener auth-userdb { group = mailstore mode = 0660 user = root } } service imap-login { inet_listener imap { port = 143 } process_limit = 256 process_min_avail = 25 service_count = 1 } service imap { process_limit = 256 process_min_avail = 25 service_count = 1 } service lmtp { inet_listener lmtp { address = * port = 24 } unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0666 user = postfix } } service pop3-login { inet_listener pop3 { port = 110 } process_limit = 256 process_min_avail = 25 service_count = 1 } service pop3 { process_limit = 256 process_min_avail = 25 service_count = 1 } service quota-warning { executable = script /usr/local/rol/dovecot/quota-warning.sh unix_listener quota-warning { user = mailstore } user = mailstore } service stats { fifo_listener stats-mail { mode = 0600 user = mailstore } } ssl = no submission_host = localhost:25 userdb { args = /etc/dovecot/dovecot-sql-account.conf driver = sql } protocol lmtp { mail_fsync = optimized mail_plugins = " quota mail_log notify acl zlib stats virtual sieve zlib" } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep imap_id_log = * imap_logout_format = bytes=%i/%o session=<%{session}> mail_max_userip_connections = 40 mail_plugins = " quota mail_log notify acl zlib stats virtual imap_quota imap_acl imap_zlib imap_stats" } protocol pop3 { mail_plugins = " quota mail_log notify acl zlib stats virtual" pop3_logout_format = bytes_sent=%o top=%t/%p, retr=%r/%b, del=%d/%m, size=%s uidl_hash=%u session=<%{session}> } ... The virtual folders are stored in "/home/virtual/XXX" and are containg only the file "dovecot-virtual". Like: "/home/virtual/All/dovecot-virtual": <--------------------- * all ---------------------> Note: I just have active virtual folders on a different dovecot server version "2:2.2.13-1~auto+74". I copied the configuration from this server. The only three differences between the two servers are: - Server version is different. - The prefix of the default namespace on the new server is "prefix = INBOX/" and not "prefix =" - Mail storage and index files are seperated in different folders on the new server. Here are the relveant namespace configuraiton from the server where it ist working fine: ... namespace { list = children location = mdbox:/home/vmail/%%d/%%n prefix = shared/%%u/ separator = / subscriptions = no type = shared } namespace { hidden = no inbox = no list = children location = virtual:/home/virtual:INDEX=~/virtual prefix = [rolmail]/ separator = / subscriptions = yes type = private } namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Items" { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = separator = / type = private } ... Have you any hint for me how I can fix my problem. Thanks and regards Urban Loesch From joliver at john-oliver.net Thu Sep 11 17:42:11 2014 From: joliver at john-oliver.net (John Oliver) Date: Thu, 11 Sep 2014 10:42:11 -0700 Subject: Case sensitivity Message-ID: <20140911174211.GA22965@ns2.sdsitehosting.net> I think I've answered my last question by changing mail_location But I'm still getting duplicate mailboxes: [joliver at localhost ~]$ sudo ls -l /var/vmail/ total 8 drwx------. 3 vmail vmail 4096 Sep 11 10:30 testuser1 drwx------. 3 vmail vmail 4096 Sep 11 10:36 testUser1 The cn for my user is 'testUser1', and that's where postfix writes mail. But dovecot wants to use 'testuser1', even if I log in as 'testUser1' I suppose one answer may be to try to get postfix to always use lower-case, but in case that can't happen, how can I get dovecot to ignore case when looking for mailboxes? -- *********************************************************************** * John Oliver http://www.john-oliver.net/ * * * *********************************************************************** From nick.z.edwards at gmail.com Thu Sep 11 23:21:14 2014 From: nick.z.edwards at gmail.com (Nick Edwards) Date: Fri, 12 Sep 2014 09:21:14 +1000 Subject: usenet/imap In-Reply-To: References: Message-ID: On 9/11/14, Edwardo Garcia wrote: > Halo, > > Has anyones had experiences with feeding usenet into imap folders, we > like to have some group for all user, any problem with message limit? > We only want the text newsgroups? > Thats crazy! Depending on your news feed that will get huge over time, and if you try get a back feed of existing posts, thats even crazier, my upstream feeds me over FORTY THOUSAND text newsgroups. thats unrealistic to feed into imap, just advertise your news server, or if you dont have one, set up inn on a spare machine, hell for a couple thousand users, a junk box (ie: even a 10yo 32bit desktop PC with half a gig of ram will run nicely) starting out you wont need terabytes of disk space, but heck, a 1TB sata drive is cheap enough so if it fails its no bother, a 1TB scsi, might be a different story LOL (but of course is much much more reliable than sata). There are a few places around who will give you a free feed if you dont have one, and if you get stuck ask me off list, I get one off someone who used to be on this list, though he's likely forgotten that I do as it was a couple years ago he connected us up :-) From nobody73 at riseup.net Thu Sep 11 23:43:46 2014 From: nobody73 at riseup.net (nobody73) Date: Fri, 12 Sep 2014 01:43:46 +0200 Subject: dovecot imap auth method issue Message-ID: <541233B2.8060904@riseup.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi List , I run Debian GNU/Linux 7 and i have followed the guide on workaround dot org and at the end of it i have authentications issues with thunderbird .On workaround there is a local test for authentication and it was successfull .Thunderbird says: "the IMAP server doesn't support the selected authentication method ,please change the authetntication method .... " I have tried all of clear, starttls and ssl/tls . dovecot 10-auth.conf is set: disable_plaintext_auth = yes auth_mechanisms = plain login !include auth-sql.conf.ext auth-sql.conf.ex has: passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf.ext } userdb { driver = static args = uid=vmail gid=vmail home=/var/vmail/%d/%n } My dovecot-sql.conf.ext content is: driver = mysql connect = host=127.0.0.1 dbname=maildb user=userdb password=123456789 default_pass_scheme = PLAIN-MD5 password_query = SELECT email as user, password FROM virtual_users WHERE email='%u'; and dovecot -n is: # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-686-pae i686 Debian 7.6 ext3 auth_mechanisms = plain login mail_location = maildir:/var/vmail/%d/%n/Maildir 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 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 = separator = } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = " imap sieve pop3" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } ssl_cert = References: <541233B2.8060904@riseup.net> Message-ID: <541295D0.7050500@ADwin.de> Gab, On 12.09.2014 01:43, nobody73 wrote: > I run Debian GNU/Linux 7 and i have followed the guide on workaround > dot org and at the end of it i have authentications issues with > thunderbird .On workaround there is a > local test for authentication and it was successfull .Thunderbird says: > "the IMAP server doesn't support the selected authentication method > ,please change the authetntication method .... " I have tried all of > clear, starttls and ssl/tls . I have a very similar setup to yours, and I also see the same error message every once in a while (maybe once per day with heavy use). Do you also get the error message occasionally or are you completely unable to login using thunderbird? Regards, Thomas -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 4246 bytes Desc: S/MIME Cryptographic Signature URL: From slusarz at curecanti.org Fri Sep 12 07:24:55 2014 From: slusarz at curecanti.org (Michael M Slusarz) Date: Fri, 12 Sep 2014 01:24:55 -0600 Subject: charset-specific searches, and continuation lines In-Reply-To: <87lhpqzh6v.fsf@ericabrahamsen.net> References: <87ha0nwxjl.fsf@ericabrahamsen.net> <20140904120846.Horde.uun-eIVC9Omg0Gm5HI2rxQ5@bigworm.curecanti.org> <87fvg6olvm.fsf@ericabrahamsen.net> <20140904205937.Horde.2qcxngzCf7IHttpmcW4yGw7@bigworm.curecanti.org> <87lhpqzh6v.fsf@ericabrahamsen.net> Message-ID: <20140912012455.Horde.1KyP1MOb-35n0Kar9pAoag1@bigworm.curecanti.org> Quoting Eric Abrahamsen : > Michael M Slusarz writes: > >> Quoting Eric Abrahamsen : >> >>> While I've got you here, I hope you'll answer one more question: what's >>> the format for searching multiple terms with non-ascii strings? Is it >>> possible in one run to find a utf-8 encoded subject, and a utf-8 encoded >>> body? >> >> IMAP interaction would look like this: >> >> C: . UID SEARCH CHARSET UTF-8 SUBJECT {4} >> S: +OK >> C: a?b BODY {4} >> S: +OK >> C: a?b >> S: * SEARCH XXX >> S: . OK >> >> Even better... if the server supports LITERAL+, you don't have to wait >> for the synchronizing literal which prevents the need to wait for 2 >> round-trips from the server: >> >> C: . UID SEARCH CHARSET UTF-8 SUBJECT {4+} >> C: a?b BODY {4+} >> C: a?b[CRLF] >> S: * SEARCH XXX >> S: . OK >> >> michael > > One other question: > > I've set up full text search indexing via Lucene, and it works great. > But how is this index encoded? Specifically, if I use the above method > to search for non-ascii strings, am I still benefiting from the speedups > of the search index? > > I know that some people who are indexing non-ascii, non-UTF-8 messages > are running them through some sort of decoder to force them into UTF-8, > so that Lucene can index them properly. Is this still necessary if I'm > using the method above? I have no insight on Lucene internals. michael From alessio at skye.it Fri Sep 12 10:14:20 2014 From: alessio at skye.it (Alessio Cecchi) Date: Fri, 12 Sep 2014 12:14:20 +0200 Subject: Announce: Plugin for iOS Push Email support In-Reply-To: <8408BC1C-68B6-40C3-B1B0-679E179C8861@arentz.ca> References: <8408BC1C-68B6-40C3-B1B0-679E179C8861@arentz.ca> Message-ID: <5412C77C.8050808@skye.it> Il 05/09/2014 03:35, Stefan Arentz ha scritto: > I?ve been hacking on a personal side project to support native iOS Push Email in Dovecot. This is specifically for people who are migrating their mail away from OS X Server while keeping their existing Push Email functionality. > > Native Push Email has some great advantages: it speeds up email notifications (usually within seconds of being handled by dovecot-lda) and it improves battery life since the native notifications flow over a single highly optimized connection to Apple?s infrastructure. > > Although this is at version 0.1, it is working pretty well for me and I am looking for some additional testers that are interested. Hi Stefan, I have installed your code on my personal email server (Dovecot 2.2.13 and Debian 7.6) and works fine! The only note is to copy the plugins file (imap_xaps_plugin.so and xaps_plugin.so) manually in /usr/lib/dovecot/. I hope you will release a version with the ability to run in background the daemon. Thanks From wdgarc88 at gmail.com Fri Sep 12 10:33:25 2014 From: wdgarc88 at gmail.com (Edwardo Garcia) Date: Fri, 12 Sep 2014 20:33:25 +1000 Subject: usenet/imap In-Reply-To: References: Message-ID: On 9/12/14, Nick Edwards wrote: > On 9/11/14, Edwardo Garcia wrote: >> Halo, >> >> Has anyones had experiences with feeding usenet into imap folders, we >> like to have some group for all user, any problem with message limit? >> We only want the text newsgroups? >> > > Thats crazy! > > Depending on your news feed that will get huge over time, and if you > try get a back feed of existing posts, thats even crazier, my upstream > feeds me over FORTY THOUSAND text newsgroups. thats unrealistic to How much of these group are active? Or how many post a day on average you get? > feed into imap, just advertise your news server, or if you dont have > one, set up inn on a spare machine, hell for a couple thousand users, > We looked at inn, it is, to be blunt, a diabolical mess , the access file is nightmare, it no limit user concurrency or daily limit by default without write external code, if inn is typical, is no wonder usenet is not as popular this days. > a junk box (ie: even a 10yo 32bit desktop PC with half a gig of ram > will run nicely) starting out you wont need terabytes of disk space, We have plenty them lying around, so maybe this be better if we find better news server software. > but heck, a 1TB sata drive is cheap enough so if it fails its no > bother, a 1TB scsi, might be a different story LOL (but of course is > much much more reliable than sata). > > There are a few places around who will give you a free feed if you > dont have one, and if you get stuck ask me off list, I get one off > someone who used to be on this list, though he's likely forgotten that > I do as it was a couple years ago he connected us up :-) We have a feeder when we ready, they go to feed our imap, so should feed our own news server, thank you anyway From mh+dovecot at zugschlus.de Fri Sep 12 10:48:32 2014 From: mh+dovecot at zugschlus.de (Marc Haber) Date: Fri, 12 Sep 2014 12:48:32 +0200 Subject: usenet/imap In-Reply-To: References: Message-ID: <20140912104832.GE4747@torres.zugschlus.de> On Thu, Sep 11, 2014 at 09:21:16PM +1000, Edwardo Garcia wrote: > Has anyones had experiences with feeding usenet into imap folders, we > like to have some group for all user, any problem with message limit? > We only want the text newsgroups? I won't do that. While Usenet and e-mail _do_ look reasonably similiar, they aren't. In 20 years of usenet, I have not seen a single gateway between e-mail and Usenet that worked acceptably. Challenges like the per-user "read" status, unique message-IDs and crosspostings are excruciatingly hard to solve. Running INN is much easier. Greetings Marc -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600420 From listas at adminlinux.com.br Fri Sep 12 11:58:36 2014 From: listas at adminlinux.com.br (Listas@Adminlinux) Date: Fri, 12 Sep 2014 08:58:36 -0300 Subject: Configure Dovecot Master User In-Reply-To: <5411B390.1080308@agr.unicamp.br> References: <540DCFC4.8060803@agr.unicamp.br> <540DE091.9040204@adminlinux.com.br> <5410A269.20805@agr.unicamp.br> <5410A55D.5060500@posteo.de> <5410A911.9000006@agr.unicamp.br> <5410B131.6090800@posteo.de> <5411B390.1080308@agr.unicamp.br> Message-ID: <5412DFEC.2010504@adminlinux.com.br> Replace "a login mailadm*master master_password" for "a login master*clovis master_password" -- Thiago Em 11-09-2014 11:37, Clovis Tristao escreveu: > a login mailadm*master master_password From delrio at mie.utoronto.ca Fri Sep 12 13:45:41 2014 From: delrio at mie.utoronto.ca (Oscar del Rio) Date: Fri, 12 Sep 2014 09:45:41 -0400 Subject: Configure Dovecot Master User In-Reply-To: <5412DFEC.2010504@adminlinux.com.br> References: <540DCFC4.8060803@agr.unicamp.br> <540DE091.9040204@adminlinux.com.br> <5410A269.20805@agr.unicamp.br> <5410A55D.5060500@posteo.de> <5410A911.9000006@agr.unicamp.br> <5410B131.6090800@posteo.de> <5411B390.1080308@agr.unicamp.br> <5412DFEC.2010504@adminlinux.com.br> Message-ID: <5412F905.6020803@mie.utoronto.ca> On 12/09/2014 7:58 AM, Listas at Adminlinux wrote: > Replace > "a login mailadm*master master_password" > for > "a login master*clovis master_password" It should be the opposite: a login username*masteruser master_password where username is the regular user (e.g. "clovis") and masteruser is the master defined in /etc/dovecot/passwd.masterusers Dovecot would log: auth: passdb(*masteruser*,IPADDRESS,master,): Master user logging in as *username* The OP should also check that the master password file has the correct entries (it is a standard htpasswd file format) and it is readable by the dovecot process. From alanm at sics.se Fri Sep 12 14:32:58 2014 From: alanm at sics.se (Alan McGinlay) Date: Fri, 12 Sep 2014 16:32:58 +0200 Subject: Configure Dovecot Master User In-Reply-To: <540DCFC4.8060803@agr.unicamp.br> References: <540DCFC4.8060803@agr.unicamp.br> Message-ID: On 2014-09-08 17:48, Clovis Tristao wrote: > Hi, > > Does anyone have any idea or hint how to configure dovecot master > user? > I'm already on it for almost fifteen days and can not find a solution. > I appreciate any help, > > Clovis It's quite simple: # Authentication for master users. Included from 10-auth.conf. # By adding master=yes setting inside a passdb you make the passdb a list # of "master users", who can log in as anyone else. # # Example master user passdb using passwd-file. You can use any passdb though. passdb { driver = passwd-file master = yes args = /etc/dovecot/passwd.masterusers # Unless you're using PAM, you probably still want the destination user to # be looked up from passdb that it really exists. pass=yes does that. pass = yes } then use htpasswd from Apache to generate the file "/etc/dovecot/passwd.masterusers" The documentation explains it quite well: http://wiki2.dovecot.org/Authentication/MasterUsers From mcguire at neurotica.com Fri Sep 12 17:11:05 2014 From: mcguire at neurotica.com (Dave McGuire) Date: Fri, 12 Sep 2014 13:11:05 -0400 Subject: usenet/imap In-Reply-To: References: Message-ID: <54132929.2080005@neurotica.com> On 09/12/2014 06:33 AM, Edwardo Garcia wrote: >> Depending on your news feed that will get huge over time, and if you >> try get a back feed of existing posts, thats even crazier, my upstream >> feeds me over FORTY THOUSAND text newsgroups. thats unrealistic to > > How much of these group are active? Or how many post a day on average you get? I realize you weren't asking me, but just to give you another data point, my server receives about 23,000 articles per day. This is nearly all groups minus the binaries. >> feed into imap, just advertise your news server, or if you dont have >> one, set up inn on a spare machine, hell for a couple thousand users, >> > We looked at inn, it is, to be blunt, a diabolical mess , the access > file is nightmare, it no limit user concurrency or daily limit by > default without write external code, if inn is typical, is no wonder > usenet is not as popular this days. With respect, this a load of crap. I was a commercial INN admin for many years, and I run it on my own network to this day. It's a fine piece of software, does its job very well, is easy to manage, and generally gives no guff. (Of course this is coming from the perspective of someone who ran C-news, and before that, B-news. B was mostly shell scripts!) Just try not to look at it as a mail server, because it isn't, and you'll be fine with INN. And for the record, Usenet is "not as popular these days" because most of the current inhabitants of the Internet are drooling morons who think the Internet and the WWW are the same thing, and that it's all one big TV. They'd never understand the concepts of Usenet in the first place. -Dave -- Dave McGuire, AK4HZ/3 New Kensington, PA From lev at serebryakov.spb.ru Fri Sep 12 18:25:19 2014 From: lev at serebryakov.spb.ru (Lev Serebryakov) Date: Fri, 12 Sep 2014 22:25:19 +0400 Subject: sieve: is it possible to filter ALL mailing lists (with header List-Id) to their folders with ONE rule? Message-ID: <1241574678.20140912222519@serebryakov.spb.ru> Hello, Dovecot. Is it possible to write one rule in sieve, which will: (1) Trigger on any message with "List-Id" header AND (2) Put this message to folder with name build from content of "List-Id" header, in such way, that message with List-Id List-Id: This is decription of list will be put into folder "org.host.list-name" where "." is namespace separator (so, such folders will be shown as hierarchy in mail client)? I don't want to write ~50 rules by hands and add new ones from time to time. I'm speaking about dovecot/pigeonhole sieve implementation, of course. All examples on net shows only manual one-rule-per-list approach :( -- // Black Lion AKA Lev Serebryakov From sca at andreasschulze.de Fri Sep 12 18:37:51 2014 From: sca at andreasschulze.de (A. Schulze) Date: Fri, 12 Sep 2014 20:37:51 +0200 Subject: sieve: is it possible to filter ALL mailing lists (with header List-Id) to their folders with ONE rule? In-Reply-To: <1241574678.20140912222519@serebryakov.spb.ru> Message-ID: <20140912203751.Horde.WFiEBfYVjMW_CVgT9y1ClQ1@horde.andreasschulze.de> Lev Serebryakov: > List-Id: This is decription of list > > will be put into folder "org.host.list-name" where "." is namespace > separator (so, such folders will be shown as hierarchy in mail client)? :-) had the same idea while writing my sieve file ... Another idea would be a key -> value map key : list-id value: foldername Andreas From dominik at dominikbreu.de Fri Sep 12 19:40:25 2014 From: dominik at dominikbreu.de (Dominik Breu) Date: Fri, 12 Sep 2014 21:40:25 +0200 Subject: sieve: is it possible to filter ALL mailing lists (with header List-Id) to their folders with ONE rule? In-Reply-To: <20140912203751.Horde.WFiEBfYVjMW_CVgT9y1ClQ1@horde.andreasschulze.de> References: <20140912203751.Horde.WFiEBfYVjMW_CVgT9y1ClQ1@horde.andreasschulze.de> Message-ID: <1410550825.798.2.camel@Dominik-THINK> Hello list, just a quick guess from my side: if header :matches "List-ID" "<*.*.*>" { fileinto "INBOX.${3}.${2}.${1}"; stop; } this should do the trick -dominik Am Freitag, den 12.09.2014, 20:37 +0200 schrieb A. Schulze: > Lev Serebryakov: > > > List-Id: This is decription of list > > > > will be put into folder "org.host.list-name" where "." is namespace > > separator (so, such folders will be shown as hierarchy in mail client)? > > :-) > had the same idea while writing my sieve file ... > > Another idea would be a key -> value map > key : list-id > value: foldername > > Andreas From lev at serebryakov.spb.ru Fri Sep 12 19:48:48 2014 From: lev at serebryakov.spb.ru (Lev Serebryakov) Date: Fri, 12 Sep 2014 23:48:48 +0400 Subject: sieve: is it possible to filter ALL mailing lists (with header List-Id) to their folders with ONE rule? In-Reply-To: <1410550825.798.2.camel@Dominik-THINK> References: <20140912203751.Horde.WFiEBfYVjMW_CVgT9y1ClQ1@horde.andreasschulze.de> <1410550825.798.2.camel@Dominik-THINK> Message-ID: <54134E20.7010300@serebryakov.spb.ru> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 09/12/2014 23:40, Dominik Breu wrote: Looks like it should work, only should be tinkered for different number of parts in ID. But it is better than full-manual :) Thank you. > just a quick guess from my side: > > if header :matches "List-ID" "<*.*.*>" { fileinto > "INBOX.${3}.${2}.${1}"; stop; } > > this should do the trick > > -dominik > > Am Freitag, den 12.09.2014, 20:37 +0200 schrieb A. Schulze: >> Lev Serebryakov: >> >>> List-Id: This is decription of list >>> >>> will be put into folder "org.host.list-name" where "." is >>> namespace separator (so, such folders will be shown as >>> hierarchy in mail client)? >> >> :-) had the same idea while writing my sieve file ... >> >> Another idea would be a key -> value map key : list-id value: >> foldername >> >> Andreas -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUE04fXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePoHkP/2Q+YYlrBDOlsRcmc4HaeWOV NvbIuWx390deikxaXmD7YiHaE58m1sOzjLzUiySgfV1zA4BoXlD8AyzcSMeNMJz4 hH6XUlRG9iLUt8PikHBNyzoqWR/xEsQK7ELxdKhX7pAk66TG1h+pUj9L11Bmy4wb lkZ2em7HtDudQSg+GYAVEvb3UW79FzEAaWlyyy3qOmDpahGGOIJgQfqN9+m3TNU0 BTHvhI6NQNoodyq4G6VqsrAnO2bOjkbbdKG2lYg/TnfcoW9gy6AinEzVaE9QepO5 qebrRBj1RGfkqvBRm9dAfTtG1qrL7LfCKZFuQBAnwmG6/Wgot/bIWM2S8YGApY9X WfukwzAOmX16YQAmAZB+WGuKw3RFCwvT7NXi5/2xzf+Njzpj1UmVBjPIBCZ6fk85 k3ljYXbmF0deHBkpMpTc7hBFYJcU+nJhPArNQE3jpcVtmk28+k/PZkbLBL1AK9Lu rwBCNYRXVa/k7YtE6g2H9s21tP7lrepVj1YeD8ZyPlfgDZ2cPmFLZJ73hEdoPBCZ YBU7ViQ/zzV/PTtW1T66uz9N+Ex1LfwDI079T0b4kCZuABjq4bCuXKxVqAu52bWW eL4MytN5jjbrJ9jRGrCimhQwZTENBS5JdornOIOH82I/lhEN/Y9TJWRWMYWyR01p LitgYGm4t45cYf1SvA+j =Q7U7 -----END PGP SIGNATURE----- From patrickdk at patrickdk.com Fri Sep 12 21:12:51 2014 From: patrickdk at patrickdk.com (Patrick Domack) Date: Fri, 12 Sep 2014 17:12:51 -0400 Subject: Dovecot HA In-Reply-To: <54116490.1010603@wheres5.com> Message-ID: <20140912171251.Horde.B1v2qRHnRsTU3nH2qsmGyw1@mail.patrickdk.com> Maybe to help alittle. This is two problems, so figure out what one to solve, or if you need to solve both. First is the datastore of the emails, second is the availability of the service to clients. Each has their own issues and requirements. Quoting Hoggins! : > Hello everyone, > > Following my previous message about replication (I'm still stuck), I was > wondering in a more general way how to achieve high availability with > Dovecot, and how to store the mail data. > > Do you have some thoughts about this ? Maybe one or two links leading to > people who already have ideas or experience ? > > I don't host a big e-mail service, nor have a lot of clients connecting. > I just need to ensure that data is always available, from the storage to > the actual service. > > Thanks in advance. From nick.z.edwards at gmail.com Sat Sep 13 00:27:19 2014 From: nick.z.edwards at gmail.com (Nick Edwards) Date: Sat, 13 Sep 2014 10:27:19 +1000 Subject: usenet/imap In-Reply-To: References: Message-ID: On 9/12/14, Edwardo Garcia wrote: > On 9/12/14, Nick Edwards wrote: >> On 9/11/14, Edwardo Garcia wrote: >>> Halo, >>> >>> Has anyones had experiences with feeding usenet into imap folders, we >>> like to have some group for all user, any problem with message limit? >>> We only want the text newsgroups? >>> >> >> Thats crazy! >> >> Depending on your news feed that will get huge over time, and if you >> try get a back feed of existing posts, thats even crazier, my upstream >> feeds me over FORTY THOUSAND text newsgroups. thats unrealistic to > > How much of these group are active? Or how many post a day on average you > get? > >> feed into imap, just advertise your news server, or if you dont have >> one, set up inn on a spare machine, hell for a couple thousand users, >> > We looked at inn, it is, to be blunt, a diabolical mess , the access > file is nightmare, it no limit user concurrency or daily limit by > default without write external code, if inn is typical, is no wonder > usenet is not as popular this days. > DNews I've heard since its unsupported now, they are. or have, given away free keys to some who've asked. We use it, its really powerful, awesome of system resource niceness, and so easy to configure even a child could do it (helolo Benny LOL), try download an have a go, yo can try-before-you-buy with anyway, and I think it still runs forever, not crippled if you dont get a key, it just puts messages into posts about it after a while. DNews even has a mail gateway which would be a sinch to add to imap, but again, thats crazy, dont do it, unless you only want a handful of groups. Oh benefit of DNews is, in "pull mode" it only gets what groups are read, so you dont need to get the full 40K groups if you dont want them, if you want a full feed, I suggest setting it up as ihave, and use suck2 to populate your news server with all articles of all groups your upstream has, but be careful of bandwith requirements for that, and I suggest you suspend your ihave until that is completed. This really off topic now, so if you need to talk more about it, contact me offlist so we dont upset the crybabies. From nick.z.edwards at gmail.com Sat Sep 13 00:40:07 2014 From: nick.z.edwards at gmail.com (Nick Edwards) Date: Sat, 13 Sep 2014 10:40:07 +1000 Subject: usenet/imap In-Reply-To: <54132929.2080005@neurotica.com> References: <54132929.2080005@neurotica.com> Message-ID: On 9/13/14, Dave McGuire wrote: > On 09/12/2014 06:33 AM, Edwardo Garcia wrote: >>> >> We looked at inn, it is, to be blunt, a diabolical mess , the access >> file is nightmare, it no limit user concurrency or daily limit by >> default without write external code, if inn is typical, is no wonder >> usenet is not as popular this days. > > With respect, this a load of crap. I was a commercial INN admin for > many years, and I run it on my own network to this day. It's a fine > piece of software, does its job very well, is easy to manage, and > generally gives no guff. > it does what it does well, yes, but it doesnt do much without writing a bunch of perl extras, like posting filters to anonymize users by stripping out header stuff. Also, inn will not limit user concurrency unless you use an external auth hook you have to write such as in perl, it can not do it out of the box, and it has no way of limiting each host to X amount of transferred data per day. > > And for the record, Usenet is "not as popular these days" because most > of the current inhabitants of the Internet are drooling morons who think > the Internet and the WWW are the same thing, and that it's all one big > TV. They'd never understand the concepts of Usenet in the first place. > heh, most kids of today would be shocked to learn their precious P2P, mailing lists, and forums etc grew out from Usenet. only the die hards use it for binaries these days strange though, since the downloaders are truly anonymous, buit do risk higher chance of missed bits, dont have to share whilst d/loading, and only the senders may leave a trail and at slight risk of being found out. From rs at sys4.de Sat Sep 13 05:58:19 2014 From: rs at sys4.de (Robert Schetterer) Date: Sat, 13 Sep 2014 07:58:19 +0200 Subject: sieve: is it possible to filter ALL mailing lists (with header List-Id) to their folders with ONE rule? In-Reply-To: <1410550825.798.2.camel@Dominik-THINK> References: <20140912203751.Horde.WFiEBfYVjMW_CVgT9y1ClQ1@horde.andreasschulze.de> <1410550825.798.2.camel@Dominik-THINK> Message-ID: <5413DCFB.3020702@sys4.de> Am 12.09.2014 um 21:40 schrieb Dominik Breu: > Hello list, > > just a quick guess from my side: > > if header :matches "List-ID" "<*.*.*>" { > fileinto "INBOX.${3}.${2}.${1}"; stop; > } > > this should do the trick > > -dominik nice i think ,you might need listescape plugin for folders with dots, depend to your namespace setup > > Am Freitag, den 12.09.2014, 20:37 +0200 schrieb A. Schulze: >> Lev Serebryakov: >> >>> List-Id: This is decription of list >>> >>> will be put into folder "org.host.list-name" where "." is namespace >>> separator (so, such folders will be shown as hierarchy in mail client)? >> >> :-) >> had the same idea while writing my sieve file ... >> >> Another idea would be a key -> value map >> key : list-id >> value: foldername >> >> Andreas Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From lev at serebryakov.spb.ru Sat Sep 13 12:08:05 2014 From: lev at serebryakov.spb.ru (Lev Serebryakov) Date: Sat, 13 Sep 2014 16:08:05 +0400 Subject: Does pigeonhole regex extension support PCRE? Message-ID: <541433A5.40509@serebryakov.spb.ru> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I've tried to use negative look-ahead in :regex match like this: if header :regex "List-Id" "" { ... } and manage-sieve server complains on save about such regex with diagnostic "repetition operator operand invalid" :( - -- Black Lion AKA Lev Serebryakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUFDOlXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePzeMP/20iuXilZwM7aZYbMy66J/xK xLldS1PDRSKbeMQKB+Qedw0nyO65/89Uk9UVjoIga+2xh7nURoeCkvFgEu5kss2q Nxeo9rURPrP8pYrNvhv6yi00NaJiQ5qEJ29V8a3vOnHcvB/lOoOTUDWRkNbA48Tm zFC1svaiy5dUPnfZ9YdMvSdFLRVU20ej34R+avodT1Rv+E2TpFOIiNRc69v1lUFD cv05PYfLpE1/k5boZTrGFs0g1Cy/PmC12KxOtvODnQ7S9iGkfbii2bOpI9vTsxky B4diYBms38vxBKMCG8ItkQn2r1TH3VOw1H2hqLt71IhI0Ix78+yTYu3F6zD3nkys KG2VRvbO9AZLvFRHkb3P6xn70OYUvQYoU3UUVZPmbe4eL2tEu7Hg0sxwdKPxi0am i6sf1nMdk/SPd/FNGZapS+hgC+Ik3rQSq+1x38SX4V0IeJ522apTxtJoewRyt4fM D5s+Rsha/oXNHkto55qNlbE2Dn/e/QXrL2Yc+cx9aWpHIz6Iv2iijnqrdgajHpvB E1Iq9+EPnKrkJKtzy/g26Kxlllaahefz/EV5rF27aWrBZGGNwnokIox5Ucrj6Ta1 Huic//Fz6pixSc9jx4WzvO+4b5mECPj8AgEKmfZ/4C04EXbn+v56vjHxx1fwn1gU SU0wiNU2/zfRUeToaUPc =x/yT -----END PGP SIGNATURE----- From stephan at rename-it.nl Sat Sep 13 13:11:47 2014 From: stephan at rename-it.nl (Stephan Bosch) Date: Sat, 13 Sep 2014 15:11:47 +0200 Subject: Does pigeonhole regex extension support PCRE? In-Reply-To: <541433A5.40509@serebryakov.spb.ru> References: <541433A5.40509@serebryakov.spb.ru> Message-ID: <54144293.2000906@rename-it.nl> On 9/13/2014 2:08 PM, Lev Serebryakov wrote: > > I've tried to use negative look-ahead in :regex match like this: > > if header :regex "List-Id" "" > { ... } > > and manage-sieve server complains on save about such regex with > diagnostic "repetition operator operand invalid" :( > https://tools.ietf.org/html/draft-murchison-sieve-regex-08#section-3 Regards, Stephan. From wdgarc88 at gmail.com Sun Sep 14 02:37:50 2014 From: wdgarc88 at gmail.com (Edwardo Garcia) Date: Sun, 14 Sep 2014 12:37:50 +1000 Subject: usenet/imap In-Reply-To: <54132929.2080005@neurotica.com> References: <54132929.2080005@neurotica.com> Message-ID: On 9/13/14, Dave McGuire wrote: > On 09/12/2014 06:33 AM, Edwardo Garcia wrote: >>> Depending on your news feed that will get huge over time, and if you >>> try get a back feed of existing posts, thats even crazier, my upstream >>> feeds me over FORTY THOUSAND text newsgroups. thats unrealistic to >> >> How much of these group are active? Or how many post a day on average you >> get? > > I realize you weren't asking me, but just to give you another data > point, my server receives about 23,000 articles per day. This is nearly > all groups minus the binaries. > >>> feed into imap, just advertise your news server, or if you dont have >>> one, set up inn on a spare machine, hell for a couple thousand users, >>> >> We looked at inn, it is, to be blunt, a diabolical mess , the access >> file is nightmare, it no limit user concurrency or daily limit by >> default without write external code, if inn is typical, is no wonder >> usenet is not as popular this days. > > With respect, this a load of crap. I was a commercial INN admin for > many years, and I run it on my own network to this day. It's a fine > piece of software, does its job very well, is easy to manage, and > generally gives no guff. > Sorry, but Nick was right, it is severe pain to get to do what we would need, I installed dnews, and oh my god, it is so much cleaner and configurable out the box that it took 10 minutes to configure to be anonymous for users but still logs so we know who does what, and it access file is as simple as postfix! unlike inn, wow so much what they say, chalk and cheese, dnews is a dream, I do like its pull feature for only group we want, running now since yesterday, some staff use, we notify select users who want usenet to use, if everybody happy in one week we ask for license, even if need pay, much cleaner, better, and no stress set up > (Of course this is coming from the perspective of someone who ran > C-news, and before that, B-news. B was mostly shell scripts!) > > Just try not to look at it as a mail server, because it isn't, and > you'll be fine with INN. > I think this might be true if you want allow world access and not care who posts where or how or how many. > And for the record, Usenet is "not as popular these days" because most > of the current inhabitants of the Internet are drooling morons who think > the Internet and the WWW are the same thing, and that it's all one big > TV. They'd never understand the concepts of Usenet in the first place. > Binaries still very popular, maybe for reason nick say From wdgarc88 at gmail.com Sun Sep 14 02:41:46 2014 From: wdgarc88 at gmail.com (Edwardo Garcia) Date: Sun, 14 Sep 2014 12:41:46 +1000 Subject: usenet/imap In-Reply-To: References: Message-ID: On 9/13/14, Nick Edwards wrote: > On 9/12/14, Edwardo Garcia wrote: >> On 9/12/14, Nick Edwards wrote: >>> On 9/11/14, Edwardo Garcia wrote: >>>> Halo, >>>> >>>> Has anyones had experiences with feeding usenet into imap folders, we >>>> like to have some group for all user, any problem with message limit? >>>> We only want the text newsgroups? >>>> >>> >>> Thats crazy! >>> >>> Depending on your news feed that will get huge over time, and if you >>> try get a back feed of existing posts, thats even crazier, my upstream >>> feeds me over FORTY THOUSAND text newsgroups. thats unrealistic to >> >> How much of these group are active? Or how many post a day on average you >> get? >> >>> feed into imap, just advertise your news server, or if you dont have >>> one, set up inn on a spare machine, hell for a couple thousand users, >>> >> We looked at inn, it is, to be blunt, a diabolical mess , the access >> file is nightmare, it no limit user concurrency or daily limit by >> default without write external code, if inn is typical, is no wonder >> usenet is not as popular this days. >> > > DNews I've heard since its unsupported now, they are. or have, given > away free keys to some who've asked. We use it, its really powerful, > awesome of system resource niceness, and so easy to configure even a > child could do it (helolo Benny LOL), try download an have a go, yo > can try-before-you-buy with anyway, and I think it still runs forever, > not crippled if you dont get a key, it just puts messages into posts > about it after a while. oh wow, as I say to Dave, yes you are right, total worlds apart, very happy now, will use dnews and forget imap intergration, even though FAQ say it easy to do, no point now, upstream is happy for us to pull a feed from rather than direct feed our imap. > DNews even has a mail gateway which would be a sinch to add to imap, > but again, thats crazy, dont do it, unless you only want a handful of > groups. > > Oh benefit of DNews is, in "pull mode" it only gets what groups are > read, so you dont need to get the full 40K groups if you dont want > them, if you want a full feed, I suggest setting it up as ihave, and > use suck2 to populate your news server with all articles of all groups > your upstream has, but be careful of bandwith requirements for that, > and I suggest you suspend your ihave until that is completed. > > This really off topic now, so if you need to talk more about it, > contact me offlist so we dont upset the crybabies. > From kremels at kreme.com Sun Sep 14 02:53:26 2014 From: kremels at kreme.com (LuKreme) Date: Sat, 13 Sep 2014 20:53:26 -0600 Subject: usenet/imap In-Reply-To: References: <54132929.2080005@neurotica.com> Message-ID: <8E440A45-4FB9-43CE-ADF7-05F23FA10F50@kreme.com> On 13 Sep 2014, at 20:37 , Edwardo Garcia wrote: > Sorry, but Nick was right, it is severe pain to get to do what we > would need, I installed dnews, and oh my god, it is so much cleaner > and configurable out the box that it took 10 minutes to configure to > be anonymous for users but still logs so we know who does what, and it > access file is as simple as postfix! unlike inn, wow so much what they > say, chalk and cheese, dnews is a dream, I do like its pull feature > for only group we want, running now since yesterday, some staff use, > we notify select users who want usenet to use, if everybody happy in > one week we ask for license, even if need pay, much cleaner, better, > and no stress set up Interesting. Where do you get your newsfeed from? I?ve often though about setting up USENET (sans binaries, natch) but just assumed that getting a feed was pretty much impossible. -- 'Yes, but humans are more important than animals,' said Brutha. 'This is a point of view often expressed by humans,' said Om. (Small Gods) From lev at serebryakov.spb.ru Sun Sep 14 20:41:37 2014 From: lev at serebryakov.spb.ru (Lev Serebryakov) Date: Mon, 15 Sep 2014 00:41:37 +0400 Subject: =?UTF-8?B?UGVyLWZvbGRlciAocGVyLW1haWxib3gpIG1lc3NhZ2UgZXhwaXJhdGk=?= =?UTF-8?B?b24gd2l0aCBjb250cm9sIGZyb20gY2xpZW50IHNpZGUg4oCUIGlzIGl0IHBvc3M=?= =?UTF-8?B?aWJsZT8=?= Message-ID: <5415FD81.40900@serebryakov.spb.ru> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 I'm migrating from ?old skool? solution with one mail client (MUA) on one computer, which retrieves mail via POP3, sorts it and manages it locally to installation when there are several MUAs on different devices, accessing mail via IMAP4, and all sorting and management should be server-side. Sorting is ?easy?: sieve. Here are some nuisance (like, if I want to rename folder/mailbox I need to edit script manually. BTW, it looks like that such thing could be done automagically, as language is very simple and find all references to mailboxes is not too hard task), but it works. But is here good solution for expiration? I have abut 50 folders (mailboxes) and rules are very different for them. They are mostly time-based (like "last 30 days"), but some folders are count-limited ("last 2000 messages") and some folders should have time limit but non-read messages could not be deleted at all. Ok, Thunderbird almost could do it (it doesn't have ?don't remove unread messages? option), but I don't want to have any meaningful configuration in MUAs, as each of it could be non-active for long time. Only thing I could find about expiration in dovecot documentation is "doveadm expunge" and helper "Expire" plugin, but it looks like very low-level solution for admins, it could not be managed from client side without direct ssh access to server and it is, in general, very inconvenient. Is here any better solution, maybe, 3rd party one? - -- // Black Lion AKA Lev Serebryakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUFf2BXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePphIQAJUlYIFgXWBcWcrejcbOFgYf op+g35YF4wfwboPkgb/mKk46V3lcjmQImcHir2fci0SCsSSfARcU1a8y4iaeSkPU l949PaMYD8stfukfCbXjoY5pD5FIpj1Os7dDtgdoygp0tfsA4mDg1O0exZoduR9s q4NNPlsnlKOjX2KMOdcWI2AR8/xiFi4zvDTB/vibQPMy8kXVB8ld4Mk0BF1TUyOv 80KKOKzFDxQeLzvoEiNm6FDAqYGEYmpECUaFGXyKG1a7wslhEmEeShJUH5lsj3Oz niMxoO/KTEW0U9QucHQogFJzrcsKkJiOByjqQovWKgZziJll38lCN0O1murMmRBC bDLmN9t53JC7Ef88AbKsaFeULy/AxriohdGU6ePb8j/4W9KlERSJyvgxFkcMxHTg 9mSPiYAHaPr+Ycrzs9SOqhki5b6tI8Q39W/etRorb2us9FS1JE7ib4XLk5ufiUje XOLc4TACUh1qnd/5UUgcIuUrg/akSJgJLZoXg36LqUF/1OeMJHec4RMJresvewAZ RwseWHH/KpD7KxOWlO2Zw1ceHlVFDLWOO/4KWoy/XwZ66fQxEAkLO8ZVyeKMh5Nh dYL+yLQKZdgNWAjalK4lFmwz3u/9jNITwtP5GYLbYnP28EcbDfiN/w9oKGOI8fsD ulD+ca3vx29qdmGGYcKt =9+bG -----END PGP SIGNATURE----- From fbsd at dannysplace.net Mon Sep 15 00:05:27 2014 From: fbsd at dannysplace.net (Dan Carroll) Date: Mon, 15 Sep 2014 10:05:27 +1000 Subject: Migration - Getting it right the first time. Message-ID: <0551CAE3-10F5-4AC0-9707-750CB0C46806@dannysplace.net> Hello All, I?m currently in the process of migrating a very old imap installation to a new server. I think I have everything in place now but I?ve not yet written the procedure on how to do it. The outline will be as follows: put MTA-OLD into store mode where it holds the incoming emails for an indefinite period. Copy all IMAP data across to the new server. Process the IMAP data, converting it from courier to dovecot. put MTA-OLD into forward mode, sending all mail to MTA-NEW Adjust MX records accordingly so MTA-OLD is no longer used. The ?process? part is where I need to take some care. I am aware of the migration tool available for moving the data, but I?m not confidant that my courier databases are in a healthy state. Does anyone have any idea how I can verify that this is the case? I?m happy to do it either before, or after the migration to dovecot, but I?d probably prefer to do it beforehand on the old server. The biggest thing I am concerned about is losing the order of mail messages. It?s not always enough to trust the ?received date? for sorting mail, I?d rather my imap clients trust the imap server to send them the correct order. A second question. Is there a possibility to make the MTA switch, and migrate the messages across in an orderly fashion at a later date? Again, I?d like to ensure that older migrated messages appear further down the ?order? than new messages coming into the MTA. Lastly, thanks for an awesome piece of software. My limited experience so far has been refreshing! -Dan From nick.z.edwards at gmail.com Mon Sep 15 01:20:30 2014 From: nick.z.edwards at gmail.com (Nick Edwards) Date: Mon, 15 Sep 2014 11:20:30 +1000 Subject: usenet/imap In-Reply-To: <8E440A45-4FB9-43CE-ADF7-05F23FA10F50@kreme.com> References: <54132929.2080005@neurotica.com> <8E440A45-4FB9-43CE-ADF7-05F23FA10F50@kreme.com> Message-ID: See Private On 9/14/14, LuKreme wrote: > On 13 Sep 2014, at 20:37 , Edwardo Garcia wrote: >> Sorry, but Nick was right, it is severe pain to get to do what we >> would need, I installed dnews, and oh my god, it is so much cleaner >> and configurable out the box that it took 10 minutes to configure to >> be anonymous for users but still logs so we know who does what, and it >> access file is as simple as postfix! unlike inn, wow so much what they >> say, chalk and cheese, dnews is a dream, I do like its pull feature >> for only group we want, running now since yesterday, some staff use, >> we notify select users who want usenet to use, if everybody happy in >> one week we ask for license, even if need pay, much cleaner, better, >> and no stress set up > > Interesting. Where do you get your newsfeed from? > > I've often though about setting up USENET (sans binaries, natch) but just > assumed that getting a feed was pretty much impossible. > > > -- > 'Yes, but humans are more important than animals,' said Brutha. 'This > is a point of view often expressed by humans,' said Om. (Small Gods) > From mtrainer at westnet.com.au Mon Sep 15 04:21:46 2014 From: mtrainer at westnet.com.au (Murray Trainer) Date: Mon, 15 Sep 2014 12:21:46 +0800 Subject: Clear a single user mapping in Director setup Message-ID: <0c1d53a4e60103e04397740d3d2b4e5bac537930@webmail.westnet.com.au> Hi All, We are using Dovecot director setup.? Is there a command to clear a single user's mapping to a backend mailstore?? This would be useful on occasions.? I couldn't find any command to do it. Thanks Murray From dmiller at amfes.com Mon Sep 15 05:00:13 2014 From: dmiller at amfes.com (Daniel Miller) Date: Sun, 14 Sep 2014 22:00:13 -0700 Subject: Empty mailboxes Message-ID: This is driving me nuts. I need to rebuild a server - got a notification the main drive is failing, and it's been a year or two, so it's time. Got a new drive, fresh install of Ubuntu Tantric, started installing everything needed. Data stored on a RAID array - nicely available separate from the boot/operation drive. Did a fresh compile of Dovecot, copied over the configs from the old drive, mounted the RAID...and... Dovecot starts, authenticates users - and shows empty mailboxes. Nothing shown. Full panic - reboot on old drive. All mails present. Change back - no mail. Executing "doveadm user -u username" seems to give valid results. Mailbox location appears correct (using mdbox). I setup uid/gid the same - I thought it was a rights issue but everything looks correct. What can I do to try to find the stupid mistake I'm making? -- Daniel From odhiambo at gmail.com Mon Sep 15 05:06:47 2014 From: odhiambo at gmail.com (Odhiambo Washington) Date: Mon, 15 Sep 2014 08:06:47 +0300 Subject: Empty mailboxes In-Reply-To: References: Message-ID: Increase the logging level and see where the problem is. On 15 September 2014 08:00, Daniel Miller wrote: > This is driving me nuts. > > I need to rebuild a server - got a notification the main drive is failing, > and it's been a year or two, so it's time. Got a new drive, fresh install > of Ubuntu Tantric, started installing everything needed. Data stored on a > RAID array - nicely available separate from the boot/operation drive. > > Did a fresh compile of Dovecot, copied over the configs from the old > drive, mounted the RAID...and... > > Dovecot starts, authenticates users - and shows empty mailboxes. Nothing > shown. Full panic - reboot on old drive. All mails present. Change back > - no mail. > > Executing "doveadm user -u username" seems to give valid results. Mailbox > location appears correct (using mdbox). > > I setup uid/gid the same - I thought it was a rights issue but everything > looks correct. > > What can I do to try to find the stupid mistake I'm making? > > -- > Daniel > -- Best regards, Odhiambo WASHINGTON, Nairobi,KE +254733744121/+254722743223 "I can't hear you -- I'm using the scrambler." From rs at sys4.de Mon Sep 15 07:26:40 2014 From: rs at sys4.de (Robert Schetterer) Date: Mon, 15 Sep 2014 09:26:40 +0200 Subject: =?UTF-8?B?UmU6IFBlci1mb2xkZXIgKHBlci1tYWlsYm94KSBtZXNzYWdlIGV4cGk=?= =?UTF-8?B?cmF0aW9uIHdpdGggY29udHJvbCBmcm9tIGNsaWVudCBzaWRlIOKAlCBpcyBpdCA=?= =?UTF-8?B?cG9zc2libGU/?= In-Reply-To: <5415FD81.40900@serebryakov.spb.ru> References: <5415FD81.40900@serebryakov.spb.ru> Message-ID: <541694B0.5080703@sys4.de> Am 14.09.2014 um 22:41 schrieb Lev Serebryakov: > > I'm migrating from ?old skool? solution with one mail client (MUA) on > one computer, which retrieves mail via POP3, sorts it and manages it > locally to installation when there are several MUAs on different > devices, accessing mail via IMAP4, and all sorting and management > should be server-side. > > Sorting is ?easy?: sieve. Here are some nuisance (like, if I want to > rename folder/mailbox I need to edit script manually. BTW, it looks > like that such thing could be done automagically, as language is very > simple and find all references to mailboxes is not too hard task), but > it works. > > But is here good solution for expiration? I have abut 50 folders > (mailboxes) and rules are very different for them. They are mostly > time-based (like "last 30 days"), but some folders are count-limited > ("last 2000 messages") and some folders should have time limit but > non-read messages could not be deleted at all. > > Ok, Thunderbird almost could do it (it doesn't have ?don't remove > unread messages? option), but I don't want to have any meaningful > configuration in MUAs, as each of it could be non-active for long time. > > Only thing I could find about expiration in dovecot documentation is > "doveadm expunge" and helper "Expire" plugin, but it looks like very > low-level solution for admins, it could not be managed from client > side without direct ssh access to server and it is, in general, very > inconvenient. > > Is here any better solution, maybe, 3rd party one? i am not sure what exact you searching for if youre on linux try look here http://www.athensfbc.com/imap_tools/details.html http://imapsync.lamiral.info/ thunderbird also has plugins like https://addons.mozilla.org/de/thunderbird/addon/awesome-auto-archive/ however i would prefer doveadm expunge via ssh or cron etc you might also try external sieve plugin to execute doveadm expunge etc via some parameter perhaps as global rule > > Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From mailinglist at darac.org.uk Mon Sep 15 09:12:11 2014 From: mailinglist at darac.org.uk (Darac Marjal) Date: Mon, 15 Sep 2014 10:12:11 +0100 Subject: sieve: is it possible to filter ALL mailing lists (with header List-Id) to their folders with ONE rule? In-Reply-To: <1241574678.20140912222519@serebryakov.spb.ru> References: <1241574678.20140912222519@serebryakov.spb.ru> Message-ID: <20140915091209.GB26680@darac.org.uk> On Fri, Sep 12, 2014 at 10:25:19PM +0400, Lev Serebryakov wrote: > Hello, Dovecot. > > > Is it possible to write one rule in sieve, which will: > > (1) Trigger on any message with "List-Id" header > > AND > > (2) Put this message to folder with name build from content of "List-Id" > header, in such way, that message with List-Id > > List-Id: This is decription of list > > will be put into folder "org.host.list-name" where "." is namespace > separator (so, such folders will be shown as hierarchy in mail client)? > > I don't want to write ~50 rules by hands and add new ones from time to > time. > > I'm speaking about dovecot/pigeonhole sieve implementation, of course. All > examples on net shows only manual one-rule-per-list approach :( Not one rule, but I use the following script to filter mailing lists into folders. It handles most mailing list types and, for consistency, the folder name is case-folded to title case. ## require [ "regex", "variables", "fileinto", "envelope", "mailbox", "imap4flags" ]; # Mailinglist Killfile if anyof (header :contains "from" "unwanted at example.com", header :contains "from" "spammer at example.net", header :contains "from" "troll at example.org"){ discard; stop; } if anyof (header :contains "x-spam-flag" "yes", allof (header :regex "X-DSPAM-Result" "^(Spam|Virus|Bl[ao]cklisted)$", not header :contains "X-DSPAM-Reclassified" "Innocent")){ # Spam goes into the spam folder setflag "\\Seen"; fileinto :create "spam"; stop; } # split out the various list forms # Mailman & other lists using list-id if exists "list-id" { if header :regex "list-id" "<([a-z_0-9-]+)[.@]" { set :lower "listname" "${1}"; fileinto :create "${listname}"; } else { if header :regex "list-id" "^\\s* From lev at serebryakov.spb.ru Mon Sep 15 09:50:25 2014 From: lev at serebryakov.spb.ru (Lev Serebryakov) Date: Mon, 15 Sep 2014 13:50:25 +0400 Subject: =?UTF-8?B?UmU6IFBlci1mb2xkZXIgKHBlci1tYWlsYm94KSBtZXNzYWdlIGV4cGk=?= =?UTF-8?B?cmF0aW9uIHdpdGggY29udHJvbCBmcm9tIGNsaWVudCBzaWRlIOKAlCBpcyBpdCA=?= =?UTF-8?B?cG9zc2libGU/?= In-Reply-To: <541694B0.5080703@sys4.de> References: <5415FD81.40900@serebryakov.spb.ru> <541694B0.5080703@sys4.de> Message-ID: <5416B661.8070002@serebryakov.spb.ru> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 15/09/2014 11:26, Robert Schetterer wrote: > i am not sure what exact you searching for if youre on linux try > look here > > http://www.athensfbc.com/imap_tools/details.html It looks like good toolset, but not solution, > http://imapsync.lamiral.info/ > > thunderbird also has plugins like > > https://addons.mozilla.org/de/thunderbird/addon/awesome-auto-archive/ > I'm searching for solution like this, but running on server (from cron, by example) but I want configure it from client, like I configure sieve from Thunderbird. Best solution will be to translate Thunderbird native settings to some server solution, as typing long folder (mailbox) names by hands (and I have hierarchy with depth of 5!) is error-prone, so it is better to have GUI for configuration which shows real folders (mailboxes). It is place where I prefer clicking to typing. > however i would prefer doveadm expunge via ssh or cron etc It is solution too, but see part about configuration. - -- Black Lion AKA Lev Serebryakov -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQJ8BAEBCgBmBQJUFrZhXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXRGOTZEMUNBMEI1RjQzMThCNjc0QjMzMEFF QUIwM0M1OEJGREM0NzhGAAoJEOqwPFi/3EePIPcQANySDvl2Z/lEr0wnqllSyR22 BbLly7G3fs6anT9eNxsJ9UJokYu+yD2sEOVekX24/AnM5wfpSH5VqB6AJbFOBmgr ZUVhIL7Z2txGJ/0jfuGm97nkMl3O6yYGYuJyET+ZtPk1jEh70Idv1XPpPvG+h4r+ Bex0WLMRhE89PuCIAalRzfvOhTsEQ+TKu2Z0VhEccT56FQcPnIeaWo/Gg9eozOwq SrVSd/NJp5npKJYcL19BxQ4XGPQiJdUBIU9+2N20FWKlHS+p3GGGhILxlWasSu4k dJLR5UZXhD7tMYTIwY36batcow/Iv+/NLbSIusnsC98LuYrPBXQys5/9OeiVcYCs N4iCxWsGBQz7vtMlgVQ0+pBpXeLv/ox3vqtR86cXRqXzmRISIuGuMJvlQD1oIK33 gOL9R7+3PyqHa0khv0BiYuxdtkdGvcPQMOvtfWK21hULRspmk0faIFj/oVigzuif k7l8gMYi9GUhnNnn7ikZMEifiY4V9FW2RnWTjJ4x1YuWJ4Caa0METJfUqkUJwlR1 XIv0ni3kr7GJyWwsJ+0NzGhVuapf6iyGAzsdvukVVwW3ExWz0IFn3kd6l4DVkhIh IU9z/FyZ/ec9NzCAZaLpmErIWKgU6JxpC/vuAeDxSqNnkRB2rX5sURA5OKsa8aRH QVPpHiX5QR+vCBkhzOhA =9/4X -----END PGP SIGNATURE----- From rs at sys4.de Mon Sep 15 10:08:25 2014 From: rs at sys4.de (Robert Schetterer) Date: Mon, 15 Sep 2014 12:08:25 +0200 Subject: =?UTF-8?B?UmU6IFBlci1mb2xkZXIgKHBlci1tYWlsYm94KSBtZXNzYWdlIGV4cGk=?= =?UTF-8?B?cmF0aW9uIHdpdGggY29udHJvbCBmcm9tIGNsaWVudCBzaWRlIOKAlCBpcyBpdCA=?= =?UTF-8?B?cG9zc2libGU/?= In-Reply-To: <5416B661.8070002@serebryakov.spb.ru> References: <5415FD81.40900@serebryakov.spb.ru> <541694B0.5080703@sys4.de> <5416B661.8070002@serebryakov.spb.ru> Message-ID: <5416BA99.9040807@sys4.de> Am 15.09.2014 um 11:50 schrieb Lev Serebryakov: > On 15/09/2014 11:26, Robert Schetterer wrote: > >> i am not sure what exact you searching for if youre on linux try >> look here > >> http://www.athensfbc.com/imap_tools/details.html > It looks like good toolset, but not solution, > >> http://imapsync.lamiral.info/ > >> thunderbird also has plugins like > >> https://addons.mozilla.org/de/thunderbird/addon/awesome-auto-archive/ > > I'm searching for solution like this, but running on server (from > cron, by example) but I want configure it from client, like I > configure sieve from Thunderbird. like this https://github.com/thsmi/sieve/blob/master/nightly/README.md https://addons.mozilla.org/de/thunderbird/addon/sieve ? Best solution will be to translate > Thunderbird native settings to some server solution, you mean some auto translation from thunderbird "local" filter rules to server sieve rules ? some other TB filter stuff is here https://addons.mozilla.org/de/thunderbird/search/?q=filter&appver=&platform= as typing long > folder (mailbox) names by hands (and I have hierarchy with depth of > 5!) is error-prone, so it is better to have GUI for configuration > which shows real folders (mailboxes). It is place where I prefer > clicking to typing. roundcube , horde-ingo has online gui sieve editors > >> however i would prefer doveadm expunge via ssh or cron etc > It is solution too, but see part about configuration. you may look too at http://linux.die.net/man/5/imapfilter_config > > i am not sure that an "exact" solution exists to what you ask for, guess you have to to find a workaround practice or code something by your own Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From tss at iki.fi Mon Sep 15 12:58:44 2014 From: tss at iki.fi (Timo Sirainen) Date: Mon, 15 Sep 2014 15:58:44 +0300 Subject: Announce: Plugin for iOS Push Email support In-Reply-To: <8408BC1C-68B6-40C3-B1B0-679E179C8861@arentz.ca> References: <8408BC1C-68B6-40C3-B1B0-679E179C8861@arentz.ca> Message-ID: On 05 Sep 2014, at 04:35, Stefan Arentz wrote: > I?ve been hacking on a personal side project to support native iOS Push Email in Dovecot. This is specifically for people who are migrating their mail away from OS X Server while keeping their existing Push Email functionality. Nice. I had been planning to look into this as well, but never had much time. Some comments from a quick look: - xaps_str_append_quoted() doesn't quote CR/LF/TABs. Of course those shouldn't normally exist in any of the fields, but older Dovecot versions would have allowed creating folder names with them. Using the str_append_tabescaped() would escape them as well, although then you'd have to implement the unescaping also with Python. - ideally the communication between Dovecot and xaps-daemon would be done asynchronously, but as a quick change you could also use i_stream_create_fd() + i_stream_read_next_line() instead of the strtok_r call. Oh and in internal Dovecot protocols it has always used LF, not CRLF, which would also make it a bit easier to handle. - in xaps_notify() especially async IO would be much better to avoid latency. It's also easier to do than in init, since it wouldn't really even need to wait for the response. Even without async IO does it really even need to read the answer from the server? - also to avoid bursts of notifications in some situations, you could use timeout_add(NOTIFY_DELAY_MSECS, ...) and have the timeout function send the notification. The delay being for example 0,5 seconds or maybe configurable. BTW. We could have some other Dovecot plugins that need to be developed if you want more (paid) work. :) We need to hire more developers to reduce my work load.. From alessandro.bono at gmail.com Mon Sep 15 14:07:42 2014 From: alessandro.bono at gmail.com (Alessandro Bono) Date: Mon, 15 Sep 2014 16:07:42 +0200 Subject: migration from cyrus with dsync sieve problem Message-ID: <5416F2AE.10009@gmail.com> Hi all i'm migrating a cyrus imapd server to dovecot with dsync everyting seems working but sieve rules are not copied to dovecot server I searched for documentation but without any luck I use the configuration below with doveadm -v -o mail_fsync=never backup -R -u emailaddr imapc: Is sieve supported with dsync? How I can specify sieve server address and port? # 2.2.13.21 (606efd4a4f35): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-431.29.2.el6.x86_64 x86_64 CentOS release 6.5 (Final) ext4 auth_default_realm = mydomain.com auth_mechanisms = plain login auth_realms = mydomain.com auth_socket_path = /var/run/dovecot/auth-userdb first_valid_gid = 492 first_valid_uid = 492 hostname = mydomain.com imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags imap_id_log = * imap_idle_notify_interval = 29 mins imapc_features = rfc822.size fetch-headers imapc_host = oldserver.mydomain.com imapc_master_user = cyrus imapc_password = xxxxxxx imapc_user = %u last_valid_gid = 492 last_valid_uid = 492 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c %k mail_attachment_dir = /var/vmail/%d/attachments/ mail_location = maildir:/var/vmail/%d/%n/Maildir:LAYOUT=fs mail_plugins = zlib listescape acl mail_prefetch_count = 20 mailbox_list_index = 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 mbox_write_locks = fcntl namespace inbox { inbox = yes list = 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 = separator = / subscriptions = yes type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile sieve = file:~/sieve;active=~/.dovecot.sieve } protocols = imap lmtp sieve service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service lmtp { user = vmail } ssl = required ssl_cert = References: <68B274DC-F65B-43FF-A68E-859A1163E902@langille.org> <540C19CB.7090501@thinline.cz> <7DB084F3-F021-470D-9A9C-FC9590673BC6@langille.org> <540E2FD0.9030900@thinline.cz> Message-ID: On Sep 8, 2014, at 6:38 PM, Jiri Bourek wrote: >>> >>>> Background: I?m in the only user on this system, but this server is accessed by my phone, my laptop, my tablet, and perhaps a web interface. >>>> >>> >>>> >>>> But there are some interesting values when I look at the output of doveconf. Specifically, vsz_limit is 18,447 PB? yeah, that?s pretty big. >>>> >>>> service imap-login { >>>> vsz_limit = 18446744073709551615 B >>>> } >>>> >>> >>> According to your log it was process ?im ap" what ran out of memory. You are showing configuration for imap-login - they are not the same thing, see http://wiki2.dovecot.org/Design/Processes >> >> My errror, sorry. OK, here?s imap: >> >> service imap { >> chroot = >> client_limit = 1 >> drop_priv_before_exec = no >> executable = imap >> extra_groups = >> group = >> idle_kill = 0 >> privileged_group = >> process_limit = 1024 >> process_min_avail = 0 >> protocol = imap >> service_count = 1 >> type = >> unix_listener login/imap { >> group = >> mode = 0666 >> user = >> } >> user = >> vsz_limit = 18446744073709551615 B >> } >> >> Still the same value? why not 265MB? > > Hm, I can only guess (someone with more knowledge of dovecot source code probably knows better), but it seems like that value is magic number for "not set". My doveconf outputs the same thing on services which don't have vsz_limit set explicitly, but when I list /proc/[pid]/limits on such a service, the row called "Max address space" (which is - AFAIK - limit on vsz) shows 2GB, a value of default_vsz_limit setting. > > I'd say don't overthink it, just put explicit vsz_limit = 512M into service imap section (if your machine's RAM allows) and be done with it. For the record, the error has recurred a few times, so after today?s incident, I added this to dovecot.conf, and restarted dovecot: service imap { vsz_limit = 512MB } FWIW, the server contains 8192 MB of RAM. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 333 bytes Desc: Message signed with OpenPGP using GPGMail URL: From dave.mehler at gmail.com Mon Sep 15 14:41:44 2014 From: dave.mehler at gmail.com (David Mehler) Date: Mon, 15 Sep 2014 10:41:44 -0400 Subject: dovecot and gmail backup Message-ID: Hello, I'm trying to use my server running dovecot to receive via imap a backup of my gmail account, messages. I'm getting an error from imap.gmail.com that it does support plain authentication but that it failed to download messages. If anyone has this working please let me know what you had to do. Thanks. Dave. From clovis at agr.unicamp.br Mon Sep 15 15:26:38 2014 From: clovis at agr.unicamp.br (Clovis Tristao) Date: Mon, 15 Sep 2014 12:26:38 -0300 Subject: Configure Dovecot Master User In-Reply-To: <5412F905.6020803@mie.utoronto.ca> References: <540DCFC4.8060803@agr.unicamp.br> <540DE091.9040204@adminlinux.com.br> <5410A269.20805@agr.unicamp.br> <5410A55D.5060500@posteo.de> <5410A911.9000006@agr.unicamp.br> <5410B131.6090800@posteo.de> <5411B390.1080308@agr.unicamp.br> <5412DFEC.2010504@adminlinux.com.br> <5412F905.6020803@mie.utoronto.ca> Message-ID: <5417052E.3040203@agr.unicamp.br> Hi, Oscar, Thank you all, worked with these tips. Very nice. "a login username*masteruser master_password " Clovis Em 12-09-2014 10:45, Oscar del Rio escreveu: > On 12/09/2014 7:58 AM, Listas at Adminlinux wrote: >> Replace >> "a login mailadm*master master_password" >> for >> "a login master*clovis master_password" > > It should be the opposite: > > a login username*masteruser master_password > > where username is the regular user (e.g. "clovis") and masteruser is > the master defined in /etc/dovecot/passwd.masterusers > > Dovecot would log: > auth: passdb(*masteruser*,IPADDRESS,master,): Master user > logging in as *username* > > The OP should also check that the master password file has the correct > entries (it is a standard htpasswd file format) and it is readable by > the dovecot process. > -- Clovis Tristao - UNICAMP/Faculdade de Engenharia Agricola Administrador de Redes - Secao de Informatica (SINFO) E-mail: clovis at feagri.unicamp.br http://www.feagri.unicamp.br MSN: clovis_tristao33 at hotmail.com Fone: 55(19) 35211031-35211038-35211047-91173116 From jost+lists at dimejo.at Mon Sep 15 15:50:32 2014 From: jost+lists at dimejo.at (Alex JOST) Date: Mon, 15 Sep 2014 17:50:32 +0200 Subject: Case sensitivity In-Reply-To: <20140911174211.GA22965@ns2.sdsitehosting.net> References: <20140911174211.GA22965@ns2.sdsitehosting.net> Message-ID: <54170AC8.3010300@dimejo.at> Am 11.09.2014 um 19:42 schrieb John Oliver: > I think I've answered my last question by changing mail_location But > I'm still getting duplicate mailboxes: > > [joliver at localhost ~]$ sudo ls -l /var/vmail/ > total 8 > drwx------. 3 vmail vmail 4096 Sep 11 10:30 testuser1 > drwx------. 3 vmail vmail 4096 Sep 11 10:36 testUser1 > > The cn for my user is 'testUser1', and that's where postfix writes mail. > But dovecot wants to use 'testuser1', even if I log in as 'testUser1' I > suppose one answer may be to try to get postfix to always use > lower-case, but in case that can't happen, how can I get dovecot to > ignore case when looking for mailboxes? > Is the username modified by your user query? Something like "%Ln"? http://wiki2.dovecot.org/Variables -- Alex JOST From pada at posteo.de Mon Sep 15 19:04:56 2014 From: pada at posteo.de (Daniel Parthey) Date: Mon, 15 Sep 2014 21:04:56 +0200 Subject: Clear a single user mapping in Director setup In-Reply-To: <0c1d53a4e60103e04397740d3d2b4e5bac537930@webmail.westnet.com.au> References: <0c1d53a4e60103e04397740d3d2b4e5bac537930@webmail.westnet.com.au> Message-ID: <647bf7a5-3119-471d-91db-349047eb053f@email.android.com> Hi there, Please see "doveadm director move". This forces a specific backend for one user, for the duration of TTL. Kind regards Daniel From joliver at john-oliver.net Mon Sep 15 22:14:20 2014 From: joliver at john-oliver.net (John Oliver) Date: Mon, 15 Sep 2014 15:14:20 -0700 Subject: Issue creating mailboxes Message-ID: <20140915221420.GA23874@ns2.sdsitehosting.net> CentOS 6.5, cyrus-imapd 2.3.16-6 So, I gather you're supposed to create mailboxes called user. But I wind up with user^, and mailbox can't be found. [joliver at localhost ~]$ cyradm -u testuser1 localhost Password: localhost> cm user.testuser2 localhost> cm user.testuser3 localhost> cm user.textuser4 [joliver at localhost ~]$ sudo ls -l /var/vmail/u/ total 12 drwx------. 2 cyrus mail 4096 Sep 15 15:07 user^testuser2 drwx------. 2 cyrus mail 4096 Sep 15 14:51 user^testuser3 drwx------. 2 cyrus mail 4096 Sep 15 15:07 user^textuser4 Sep 15 15:05:18 localhost lmtpunix[15704]: verify_user(user.testuser2) failed: Mailbox does not exist Sep 15 15:05:18 localhost master[15929]: about to exec /usr/lib/cyrus-imapd/lmtpd Sep 15 15:05:18 localhost lmtpunix[15929]: executed Sep 15 15:05:18 localhost postfix/lmtp[15928]: 4B2E61ED5: to=, relay=localhost.localdomain[/var/lib/imap/socket/lmtp], delay=32, delays=32/0.01/0/0.02, dsn=5.1.1, status=bounced (host localhost.localdomain[/var/lib/imap/socket/lmtp] said: 550-Mailbox unknown. Either there is no mailbox associated with this 550-name or you do not have authorization to see it. 550 5.1.1 User unknown (in reply to RCPT TO command)) What did I do wrong? -- *********************************************************************** * John Oliver http://www.john-oliver.net/ * * * *********************************************************************** From stephan at rename-it.nl Mon Sep 15 22:49:59 2014 From: stephan at rename-it.nl (Stephan Bosch) Date: Tue, 16 Sep 2014 00:49:59 +0200 Subject: replicating (manage)sieve - no symlink on replica? In-Reply-To: <5aac7554cee68f3b811b38ad3b2b232e@posteo.de> References: <5aac7554cee68f3b811b38ad3b2b232e@posteo.de> Message-ID: <54176D17.7070408@rename-it.nl> On 9/11/2014 3:36 PM, Philipp wrote: > 2.2.13/0.4.2, both from source-tarball, no fancy options. > > tcp-replication between two nodes and following plugin parameters > (same on both sides, except the ip-addr) > plugin { > sieve_before = /home/ssfn/etc/dovecot/sieve.default > sieve_global_dir = /home/ssfn/etc/dovecot > sieve = ~/.dovecot.sieve > sieve_dir = ~/.sieve > sieve_extensions = +vnd.dovecot.duplicate > sieve_duplicate_period = 6h > mail_replica = tcp:10.66.50.15:9993 > } > > mail_location = sdbox:/home/ssfn/var/mail/boxes/%n > mail_home = /home/ssfn/var/mail/boxes/%n > > Testbed: user getting first email delivered, the subdir %n/.sieve/tmp > is automatically created as expected. > User logs into managesieve on node1 and uploads a script. > The %n/.sieve/managesieve.sieve and the symlink .dovecot.sieve -> > .sieve/managesieve.sieve > is created as expected. > > One node2 (via replica) happens: > automatically create %n/.sieve/tmp > automatically create/sync %n/.sieve/managesieve.sieve > just NOT the symlink .dovecot.sieve -> .sieve/managesieve.sieve > > Logfiles for lmtp,doveadm,dsync-local dont indicate an error why it > could not create the link or such, > to me it looks like it wouldnt even try. > > mail-syncing works flawlessly (for delivery, just read about the > expunge .. hum.) > > I tried to force a full-resync via doveadm replicator afterwards, to > no change on the matter. > > Any input? Sorry, I haven't had time to look at this one. I believe a similar issue was reported earlier. It is on my list, but testing this is a bit cumbersome for me at the moment. Regards, Stephan. From listas at adminlinux.com.br Tue Sep 16 14:41:04 2014 From: listas at adminlinux.com.br (listas at adminlinux.com.br) Date: Tue, 16 Sep 2014 11:41:04 -0300 Subject: My Dsync isn't replicating 'EXPUNGE' IMAP command In-Reply-To: <8dad1690d4d014a181b05db5bf96bd75@posteo.de> References: <540F4D46.1000004@adminlinux.com.br> <54108820.7040909@adminlinux.com.br> <8dad1690d4d014a181b05db5bf96bd75@posteo.de> Message-ID: <54184C00.6020305@adminlinux.com.br> I made a change in 'mail_plugins' directive, enabling 'notify' and 'replication' globally in dovecot.conf. Now, in my tests, the second server sees the replication of the EXPUNGE command only after running a SELECT command (or an click in the folder on MUA). Is this the expected behavior? * I tested with IMAP talk (telnet) and Thunderbird. Thanks! -- Thiago Henrique From david.myers.24j74 at gmail.com Wed Sep 17 09:55:01 2014 From: david.myers.24j74 at gmail.com (Dave Myers) Date: Wed, 17 Sep 2014 11:55:01 +0200 Subject: unable to see mail when using telnet / open ssl Message-ID: <54195A75.40407@gmail.com> Dear dovecot list. I'm setting up my own VPS and working through getting mail to work. Here is my dovecot -n $dovecot -n maildir:%h/%d/%n/mail : layout=fs # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-xen-amd64 x86_64 Debian 6.0.3 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login cram-md5 auth_verbose = yes auth_verbose_passwords = plain lda_mailbox_autocreate = yes log_path = /var/log/dovecot.log mail_debug = yes mail_gid = 1002 mail_home = /var/mail/virtual/%d/%n mail_location = maildir:~/mail: layout=fs mail_uid = 1002 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 = scheme=SHA512-CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } protocols = imap service auth { unix_listener auth-client { mode = 0660 user = mail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } ssl_cert = References: <20140915221420.GA23874@ns2.sdsitehosting.net> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 15 Sep 2014, John Oliver wrote: > CentOS 6.5, cyrus-imapd 2.3.16-6 this list deals with the Dovecot server, not Cyrus. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBVBlsQnz1H7kL/d9rAQIXRgf/QuU7ueDbSW73RtMYijf+BGP1vunalpfD xz25BPnCBBgwx8kWF/A8mtZPMEamYgfm6XpDTVgbwN52vyXOuxD+x7Qzo3vJoBTC 8q8koXPuIOPCP3n0CjdkWgKa3OU0qUYxj/f0SoEKElOa45ntk5VsdB92i0oV0U6E Cbpn+kinbHwKjJuQ8visjAquiBQ5uNBYde4vrO2JXtt4oqovsTB3+Llt61VZRaSr bW8vsVAx5K9atkApIwgSCNpgXJiytwbl/V0ORqxYA09V6zgw0aTc3O/ln1+9RyR7 C1V7x060DK9BKLtNMLRnJ8RC3zp+YI3BeuZf+Uxv7hSNiPkgBHlS6w== =i/pi -----END PGP SIGNATURE----- From alanm at sics.se Wed Sep 17 12:33:51 2014 From: alanm at sics.se (Alan McGinlay) Date: Wed, 17 Sep 2014 14:33:51 +0200 Subject: replicator only starts for users who log in at least once In-Reply-To: References: Message-ID: <2a5daec59a2d7a53cc281a6c6480a9ec@sics.se> On 2014-08-05 14:49, Alan McGinlay wrote: > Hi! > > I recently setup a second with replication to the other. Both > machines run ubuntu 12.04 with dovecot 2.2.13 (6bb26098a45c). > > All users mail accounts are currently synced manually to the first > (mb1) using a dsync script, they are synchronised from a cyrus imap > server. Users are still logging into the cyrus server. > > It appears that the only accounts that are replicated are ones who > have logged into either of the dovecot servers at least once, is this > how it is supposed to work? I was hoping to get full replication of > all mail accounts before starting to move users into the new system. > > Thanks, > > Alan To answer my own question: doveadm replicator replicate 'user at domain' In my migration script i now include this command for each user. From ben at indietorrent.org Wed Sep 17 16:04:27 2014 From: ben at indietorrent.org (ben at indietorrent.org) Date: Wed, 17 Sep 2014 12:04:27 -0400 Subject: Backtrace =?UTF-8?Q?io=5Fadd=28=30x=31=29=20called=20twice=20?= =?UTF-8?Q?fd=3D=37=20=28was=20Exit=20status=20code=20=31=33=34=3B=20what?= =?UTF-8?Q?=20is=20it=2C=20in=20the=20context=20of=20Dovecot=20Antispam=20?= =?UTF-8?Q?plug-in=3F=29?= In-Reply-To: <53E39E11.90602@indietorrent.org> References: <53D6EC93.8000503@indietorrent.org> <53D7BBD5.7080106@indietorrent.org> <53E39576.3000705@indietorrent.org> <53E39E11.90602@indietorrent.org> Message-ID: <0745b65754c787003ebfdb7e34906425@indietorrent.org> On 2014-08-07 11:41, Ben Johnson wrote: > On 8/7/2014 11:14 AM, Steffen Kaiser wrote: >> one idea: http://www.tldp.org/LDP/abs/html/exitcodes.html >> >> exit code 134 would be in bash's meaning (if this website is >> correct all) some program died off signal 6. This would be Abort in >> Linux. >> >> prepend your script with >> >> exec >> /tmp/trace 2>&1 set -vx >> >> that will dump anything visible into /tmp/trace >> >> - -- Steffen Kaiser > > Thank you for your continued assistance, Steffen. > > You seem to be exactly correct with the Abort signal. > > I prepended the values you suggested to the pipe script and here's the > relevant output: > > + /usr/lib/dovecot/deliver -d sa-training at example.com -m Training.SPAM > ^A^H5584 prefix=lda: > ^A^F5584 io_add(0x1) called twice fd=7, callback=0x7f23489fb6f0 -> > 0x7f23489aa530 > ^A^D5584 Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x5e271) > [0x7f23489e9271] -> /usr/lib/dovecot/libdovecot.so.0(+0x5e34e) > [0x7f23489e934e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) > [0x7f23489a4a9e] -> > /usr/lib/dovecot/libdovecot.so.0(ioloop_iolist_add+0x83) > [0x7f23489f9533] -> > /usr/lib/dovecot/libdovecot.so.0(io_loop_handle_add+0x3b) > [0x7f23489f9cbb] -> /usr/lib/dovecot/libdovecot.so.0(io_add+0x9b) > [0x7f23489f89fb] -> > /usr/lib/dovecot/libdovecot.so.0(master_service_io_listeners_add+0x69) > [0x7f23489a9e49] -> > /usr/lib/dovecot/libdovecot.so.0(master_service_init_finish+0xb0) > [0x7f23489a9f90] -> /usr/lib/dovecot/deliver(main+0x1cb) > [0x7f234939269b] -> > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) > [0x7f23485e6ec5] -> /usr/lib/dovecot/deliver(+0x31de) [0x7f23493931de] > /usr/local/bin/sa-learn-pipe.sh: line 52: 5584 Aborted > (core dumped) /usr/lib/dovecot/deliver -d "sa-training at example.com" > -m "Training.$mode" > + echo 'Exit status was 134' > > Does this tell us anything more? > > I don't see any indication that apparmor is at play, as there is no > profile that should apply in this context (and there is nothing in the > relevant log file): > > # service apparmor status > apparmor module is loaded. > 8 profiles are loaded. > 8 profiles are in enforce mode. > /sbin/dhclient > /usr/bin/freshclam > /usr/lib/NetworkManager/nm-dhcp-client.action > /usr/lib/connman/scripts/dhclient-script > /usr/sbin/clamd > /usr/sbin/mysqld > /usr/sbin/ntpd > /usr/sbin/tcpdump > 0 profiles are in complain mode. > 4 processes have profiles defined. > 4 processes are in enforce mode. > /usr/bin/freshclam (2015) > /usr/sbin/clamd (1897) > /usr/sbin/mysqld (1239) > /usr/sbin/ntpd (2472) > 0 processes are in complain mode. > 0 processes are unconfined but have a profile defined. > > I'll try to reproduce this on an identically-configured server. I > wonder if it would be worth changing the version of Dovecot. But I > hate to play whack-a-mole if a more systematic approach is to be had. > > Thanks again, > > -Ben Hello, I am still struggling with this problem, and am wondering what the best course of action might be with regard to finding a solution. This behavior is the same on two identically-configured Ubuntu 14.04 LTS servers. At least whatever the problem might be, it's consistent. I realize that this version of Dovecot is a bit stale (2.2.9), but ultimately I am forced to work within official the Ubuntu repositories. That said, for the sake of academia, I tried upgrading Dovecot to the latest "ee" version, to see if the problem still exists, but I receive an "ABI version mismatch" when I try to build the Antispam plugin from source. I posted to the mailing list about that and never did receive a response. If it would be more appropriate to file a bug report on the Ubuntu Launchpad system, I am happy to do so. Thank you for any further guidance, -Ben From jogi at mur.at Thu Sep 18 12:08:33 2014 From: jogi at mur.at (=?UTF-8?B?Sm9naSBIb2Ztw7xsbGVy?=) Date: Thu, 18 Sep 2014 14:08:33 +0200 Subject: migration from cyrus with dsync sieve problem In-Reply-To: <5416F2AE.10009@gmail.com> References: <5416F2AE.10009@gmail.com> Message-ID: <541ACB41.10402@mur.at> Hi Alessandro, Am 2014-09-15 um 16:07 schrieb Alessandro Bono: > i'm migrating a cyrus imapd server to dovecot with dsync > everyting seems working but sieve rules are not copied to dovecot server > I searched for documentation but without any luck > I use the configuration below with We are in the process of doing the same here. After first trials with dsync we went to migrating with cyrus2dovecot. For migrating sieve scripts we wrote a simple shell script. The main reason why we abandoned dsync is that it was just painfully slow. I don't remember if it did (attempt) to syn sieve scripts. One thing that we still could not solve is that when migrating shared folders, all flags for all mail are set to unread. Would be interesting if you use shared mailboxes and how you tackle this topic. Cheers, -- J.Hofm?ller Im ?brigen bin ich der Meinung, das Joanneum muss zerschlagen werden! - Barbara Fischer -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: OpenPGP digital signature URL: From alessandro.bono at gmail.com Thu Sep 18 17:17:18 2014 From: alessandro.bono at gmail.com (Alessandro Bono) Date: Thu, 18 Sep 2014 19:17:18 +0200 Subject: migration from cyrus with dsync sieve problem In-Reply-To: <541ACB41.10402@mur.at> References: <5416F2AE.10009@gmail.com> <541ACB41.10402@mur.at> Message-ID: <541B139E.6040304@gmail.com> Hi Jogi Il 18/09/14 14:08, Jogi Hofm?ller ha scritto: > Hi Alessandro, > > Am 2014-09-15 um 16:07 schrieb Alessandro Bono: > >> i'm migrating a cyrus imapd server to dovecot with dsync >> everyting seems working but sieve rules are not copied to dovecot server >> I searched for documentation but without any luck >> I use the configuration below with > We are in the process of doing the same here. After first trials with > dsync we went to migrating with cyrus2dovecot. For migrating sieve > scripts we wrote a simple shell script. > > The main reason why we abandoned dsync is that it was just painfully > slow. I don't remember if it did (attempt) to syn sieve scripts. > > One thing that we still could not solve is that when migrating shared > folders, all flags for all mail are set to unread. Would be interesting > if you use shared mailboxes and how you tackle this topic. I can confirm that dsync not sync sieve script, I finished migration and recreate sieve rules by hand (and yes dsync it's really slow) but a new problem appears, dovecot not support duplication suppression, I partially solved with postfix parameter "enable_original_recipient = no" but it's not a complete solution I have to migrate another system with shared mailboxes but I still have to configure the new server > Cheers, -- Cordiali saluti Alessandro Bono From dovecot at outputservices.com Thu Sep 18 20:06:35 2014 From: dovecot at outputservices.com (dovecot at outputservices.com) Date: Thu, 18 Sep 2014 14:06:35 -0600 (MDT) Subject: LDAP and dovecot Message-ID: <201409182006.s8IK6Zj20017@outputservices.com> At my company I have users who are now becoming remote and using their mobile devices for email. I use Solaris 10 10/09 s10x_u8wos_08a X86 as an operating system and I now need a more secure email solution than the generic sendmail / imap solution. I want to use dovecot and postfix because I have read good reports on these products for ease of setup and use. I need to use both with SSL certificates and username / passwords for both receiving and sending emails. I am having difficulty getting dovecot to work with my ldap password solution. I have read all the documentation, there is a lot of it, and find it confusing. But I have tried very hard to get the solution to work. I have not compiled postfix because I want to use the dovecot authentication solution it mentions. Therefore I need to get dovecot to work first. I have dovecot 2.2.10 & postfix 2.11.1 with openldap 2.4.33. I have tested dovecot with /etc/passwd /etc/shadow password authentication and password flat files. Those work, but not what I need. I need to use ldap so the users only have to set one password. Below is the information I have. I have created self signed SSL certificates for testing purposes. We will get real SSL certificates once everything is operational. ********* I compiled dovecot with the following command: ./configure --prefix=/usr/local/tools/dovecot --with-ssl=openssl --with-solr --with-zlib --with-bzlib --with-ldap=yes ------------------------------------------- dovecot -n # 2.2.10: /usr/local/tools/dovecot/etc/dovecot/dovecot.conf # OS: SunOS 5.10 i86pc base_dir = /dovecot/var/run/dovecot log_path = /dovecot/log/log log_timestamp = "%Y-%m-%d %H:%M:%S " mail_debug = yes mail_location = mbox:~/posta:INBOX=/var/mail/%u:LAYOUT=maildir++:INDEX=~/posta/index:CONTROL=~/posta/control passdb { args = /dovecot/etc/dovecot/tests/ldap.settings driver = ldap } protocols = imap service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 } } ssl_cert = , rip=137.106.101.127, lip=137.106.76.215, TLS handshaking, session= 2014-09-18 09:44:48 master: Warning: Killed with signal 15 (by pid=18992 uid=0 code=kill) ------------------------------------------- If I use a flat file for passwords: 2014-09-18 09:42:23 master: Info: Dovecot v2.2.10 starting up for imap 2014-09-18 09:43:05 imap-login: Info: Login: user=, method=PLAIN, rip=137.106.101.127, lip=137.106.76.215, mpid=16769, TLS, se ssion= 2014-09-18 09:43:05 imap(dave): Debug: Effective uid=6010, gid=131, home=/export/home/sun/dave 2014-09-18 09:43:05 imap(dave): Debug: maildir++: root=/export/home/sun/dave/posta, index=/export/home/sun/dave/posta/index, indexpv t=, control=/export/home/sun/dave/posta/control, inbox=/var/mail/dave, alt= 2014-09-18 09:43:10 imap(dave): Info: Disconnected: Logged out in=223 out=1122 2014-09-18 09:43:22 master: Warning: Killed with signal 15 (by pid=17115 uid=0 code=kill) ------------------------------------------- If I use /etc/passwd /etc/shadow for passwords: 2014-09-18 09:39:56 master: Info: Dovecot v2.2.10 starting up for imap 2014-09-18 09:40:14 imap-login: Info: Login: user=, method=PLAIN, rip=137.106.101.127, lip=137.106.76.215, mpid=13053, TLS, se ssion= 2014-09-18 09:40:14 imap(dave): Debug: Effective uid=6010, gid=131, home=/export/home/sun/dave 2014-09-18 09:40:14 imap(dave): Debug: maildir++: root=/export/home/sun/dave/posta, index=/export/home/sun/dave/posta/index, indexpv t=, control=/export/home/sun/dave/posta/control, inbox=/var/mail/dave, alt= 2014-09-18 09:41:01 imap(dave): Info: Disconnected: Logged out in=219 out=1118 2014-09-18 09:41:33 master: Warning: Killed with signal 15 (by pid=14765 uid=0 code=kill) ------------------------------------------- I am using openldap 2.4.33. I compiled it using the following command: ./configure --enable-crypt --enable-ldap --enable-perl --prefix=/usr/local/openldap In the slapd.conf file I have placed the following: access to attrs=userPassword by dn="cn=dovecot,dc=ldap,dc=outputservices,dc=com" read by anonymous auth by self write by * none ------------------------------------------- In the ldap database I have the following dovecot user information: dn: uid=dovecot,ou=People,dc=ldap,dc=outputservices,dc=com uid: dovecot cn: Dovecot Email User objectClass: account objectClass: posixAccount objectClass: top objectClass: shadowAccount uidNumber: 505 gidNumber: 505 homeDirectory: /tmp structuralObjectClass: account entryUUID: f85d1e02-13e3-1033-9c4a-b7d2075f7ecd creatorsName: cn=admin,dc=ldap,dc=outputservices,dc=com createTimestamp: 20140117165553Z loginShell: /bin/tcsh entryCSN: 20140725160856.481921Z#000000#000#000000 modifiersName: cn=admin,dc=ldap,dc=outputservices,dc=com modifyTimestamp: 20140725160856Z ------------------------------------------- In the /etc/passwd file I have the following information: dovecot:x:505:505:Dovecot IMAP Server:/tmp:/bin/false dovenull:x:506:506:Dovecot IMAP Server:/tmp:/bin/false ------------------------------------------- I need assistance on this and also once I get dovecot running with ldap, I could use proper assistance with the postfix solution also. I want to stop solaris versions of sendmail and use dovecot & postfix. I am also a little confused on the mail_location setting. We use thunderbird as an email client and it sets the "local folders" just fine. But with imap it puts the Sent, Trash, Draft folders in the users "home" directory. With dovecot I have to put them in a different folder, I called it posta for now. It then makes them . Files. (.Sent, .Trash ?) From helge at kraak.info Thu Sep 18 22:57:36 2014 From: helge at kraak.info (Helge Kraak) Date: Fri, 19 Sep 2014 00:57:36 +0200 Subject: dsync error: Error: Can't delete mailbox INBOX: INBOX can't be deleted. Message-ID: <653A24C3-AA9C-4E1D-9B07-87F0E3985526@kraak.info> Hello, I'm aware of these two threads http://www.dovecot.org/pipermail/dovecot/2012-March/thread.html#134311 http://dovecot.org/pipermail/dovecot/2012-June/thread.html#136488 but unfortunately I wasn't successful with my dsync mailbox migration attempt despite the information I could find there. I'm using iRedMail setup for the dovecot server. I made sure that the dovecot mailbox for the mail import had been freshly created and untouched before I tried to run the following command. Running this command: sudo doveadm -vvv -o imapc_host=s04.srv-net.de -o imapc_user=username -o imapc_password=password -o mail_fsync=never -o mail_prefetch_count=20 -o imapc_features=rfc822.size -o imapc_features=fetch-headers -o imapc_port=993 -o imapc_ssl=imaps -o imapc_ssl_ca_dir=/etc/ssl -o imapc_ssl_verify=no -o imapc_features=rfc822.size -o mailbox_list_index=no -D backup -R -u michael at domain.com imapc: I get the following output (I took out some lines obviously not relevant): doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm doveadm(root): Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_deinit (this is usually intentional, so just ignore this message) doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so doveadm(root): Debug: Skipping module doveadm_zlib_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_zlib_plugin.so: undefined symbol: i_stream_create_deflate (this is usually intentional, so just ignore this message) doveadm(root): Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_rescan (this is usually intentional, so just ignore this message) doveadm(michael at domain.com): Debug: Added userdb setting: plugin/master_user=michael at domain.com doveadm(michael at domain.com): Debug: Added userdb setting: plugin/quota_rule=*:bytes=41943040000 doveadm(michael at domain.com): Debug: Effective uid=2000, gid=2000, home=/var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59/ doveadm(michael at domain.com): Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir://var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir/:INDEX=//var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir/ doveadm(michael at domain.com): Debug: maildir++: root=//var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir, index=, control=, inbox=//var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir, alt= doveadm(michael at domain.com): Debug: Namespace : type=shared, prefix=Shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/Shared/%u doveadm(michael at domain.com): Debug: shared: root=/var/run/dovecot, index=, control=, inbox=, alt= dsync(michael at domain.com): Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=imapc: dsync(michael at domain.com): Debug: imapc: root=, index=, control=, inbox=, alt= dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Looking up IP address dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Connecting to 78.138.89.136:993 dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Starting SSL handshake dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Server capabilities: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Authenticating as username dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Server capabilities: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS QUOTA dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Authenticated successfully dsync(michael at domain.com): Debug: Namespace : type=shared, prefix=Shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/Shared/%u dsync(michael at domain.com): Debug: shared: root=/var/run/dovecot, index=, control=, inbox=, alt= dsync(michael at domain.com): Debug: Namespace : Using permissions from //var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir: mode=0700 gid=-1 dsync(michael at domain.com): Error: Can't delete mailbox INBOX: INBOX can't be deleted. dsync(michael at domain.com): Info: Amazon: uidnext changed: 1056 != 1 dsync(michael at domain.com): Info: INBOX: only in dest (guid=3c68c835800a07547d45000029cbe4c2)= 1 dsync(michael at domain.com): Info: Deleted Messages: uidnext changed: 109 != 1 dsync(michael at domain.com): Info: MBA Mails: uidnext changed: 444 != 1 dsync(michael at domain.com): Info: Archive: highest_modseq changed: 0 != 1 dsync(michael at domain.com): Info: Spam: uidnext changed: 3 != 1 dsync(michael at domain.com): Info: Apple Mail To Do: highest_modseq changed: 0 != 1 dsync(michael at domain.com): Info: Jobsuche: uidnext changed: 22436 != 1 dsync(michael at domain.com): Info: Trash (Messages): uidnext changed: 697 != 1 dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Looking up IP address dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Connecting to IP-Adress:993 dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Starting SSL handshake dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Server capabilities: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Authenticating as username dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Server capabilities: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS QUOTA dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Authenticated successfully dsync(michael at domain.com): Error: Trying to open a non-listed mailbox with guid=3c68c835800a07547d45000029cbe4c2 dsync(michael at domain.com): Error: msg iteration failed: Couldn't open mailbox 3c68c835800a07547d45000029cbe4c2 dsync(michael at domain.com): Error: Trying to open a non-listed mailbox with guid=3c68c835800a07547d45000029cbe4c2 dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Disconnected sudo dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.6 auth_master_user_separator = * auth_mechanisms = PLAIN LOGIN dict { acl = mysql:/etc/dovecot/dovecot-share-folder.conf quotadict = mysql:/etc/dovecot/dovecot-used-quota.conf } first_valid_uid = 2000 last_valid_uid = 2000 listen = * log_path = /var/log/dovecot.log mail_gid = 2000 mail_location = maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/ mail_plugins = quota mail_uid = 2000 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 namespace { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = no special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } namespace { list = children location = maildir:/%%Lh/Maildir/:INDEX=/%%Lh/Maildir/Shared/%%u prefix = Shared/%%u/ separator = / subscriptions = yes type = shared } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } passdb { args = /etc/dovecot/dovecot-master-users-password driver = passwd-file master = yes } plugin { acl = vfile acl_shared_dict = proxy::acl auth_socket_path = /var/run/dovecot/auth-master quota = dict:user::proxy::quotadict quota_rule = *:storage=1G quota_warning = storage=85%% quota-warning 85 %u quota_warning2 = storage=90%% quota-warning 90 %u quota_warning3 = storage=95%% quota-warning 95 %u sieve = /%Lh/sieve/dovecot.sieve sieve_default = /var/vmail/sieve/dovecot.sieve sieve_dir = /%Lh/sieve sieve_global_dir = /var/vmail/sieve } protocols = pop3 imap sieve lmtp service auth { unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0666 user = postfix } unix_listener auth-master { group = vmail mode = 0666 user = vmail } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } } service dict { unix_listener dict { group = vmail mode = 0660 user = vmail } } service imap-login { process_limit = 500 service_count = 1 } service lmtp { executable = lmtp -L inet_listener lmtp { port = 24 } process_min_avail = 5 unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } user = vmail } service pop3-login { service_count = 1 } service quota-warning { executable = script /usr/local/bin/dovecot-quota-warning.sh unix_listener quota-warning { group = vmail mode = 0660 user = vmail } } ssl = required ssl_cert = Couple questions about running doveadm with multiple instances... I have Dovecot 2.2.13 on RHEL6 running across 3 boxes, each with a director and main instance running. When I try to lookup something on the main instance (which is handling user auth) via its auth-userdb socket directly, I get an error: # doveadm auth lookup -a /var/run/dovecot-main/auth-userdb myuser doveadm(root): Error: passdb lookup failed for myuser: Configured passdbs don't support crentials lookups When I use the default lookup map, I just get the proxy settings that are configured in the director instance's authdb. # doveadm auth lookup myuser passdb: myuser user : myuser proxy : y nopassword: y In addition, "doveadm director map" can't map the username -I get the error: doveadm(root): Error: User listing returned failure doveadm(root): Error: user listing failed [then I get the whole list, but with for each user] The director itself doesn't have the LDAP passdb that the main dovecot instance talks to, but I have, in the director config: service doveadm { inet_listener { port = 8889 } } director_doveadm_port = 8889 local 192.168.x.x/24 { doveadm_password = XXXXXX } doveadm_proxy_port = 8888 And in the main config: service doveadm { inet_listener { port = 8888 } } local 192.168.x.x/24 { doveadm_password = XXXXXXX ## same password as above } From dovecot.org at veggiechinese.net Fri Sep 19 00:09:38 2014 From: dovecot.org at veggiechinese.net (Will Yardley) Date: Thu, 18 Sep 2014 17:09:38 -0700 Subject: negative auth cache? Message-ID: <20140919000938.GJ18052@aura.veggiechinese.net> I am using Dovecot 2.2.13, which doesn't yet seem to have the $auth_cache_negative parameter. Should the negative cache value honor $auth_cache_ttl then? I had a problem where some of our ldap systems were reinitialized. Some users, presumably those who tried to login while their records were returning a failure, became unable to login after the records were once again returning normally. I currently have: auth_cache_size = 5 M auth_cache_ttl = 5 mins # Not yet implemented #auth_cache_negative = 2 mins yet the problem seemed to persist for more than an hour. Also, how can I flush the cache for a non-default instance's cache using doveadm -- "doveadm auth cache flush" doesn't seem to have an '-a' option AFAICT. # doveadm auth usage: doveadm [-Dv] [-f ] auth [] cache flush w From h.reindl at thelounge.net Fri Sep 19 00:34:34 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Fri, 19 Sep 2014 02:34:34 +0200 Subject: negative auth cache? In-Reply-To: <20140919000938.GJ18052@aura.veggiechinese.net> References: <20140919000938.GJ18052@aura.veggiechinese.net> Message-ID: <541B7A1A.5040608@thelounge.net> Am 19.09.2014 um 02:09 schrieb Will Yardley: > I am using Dovecot 2.2.13, which doesn't yet seem to have the > $auth_cache_negative parameter. Should the negative cache value honor > $auth_cache_ttl then? > > I had a problem where some of our ldap systems were reinitialized. Some > users, presumably those who tried to login while their records were > returning a failure, became unable to login after the records were once > again returning normally. > > I currently have: > auth_cache_size = 5 M > auth_cache_ttl = 5 mins > # Not yet implemented > #auth_cache_negative = 2 mins > > yet the problem seemed to persist for more than an hour. > > Also, how can I flush the cache for a non-default instance's cache using > doveadm -- "doveadm auth cache flush" doesn't seem to have an '-a' > option AFAICT. > > # doveadm auth > usage: doveadm [-Dv] [-f ] auth [] > cache flush just hard restart dovecot the auth cache is not persistent -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From jtam.home at gmail.com Fri Sep 19 01:20:13 2014 From: jtam.home at gmail.com (Joseph Tam) Date: Thu, 18 Sep 2014 18:20:13 -0700 (PDT) Subject: negative auth cache? In-Reply-To: References: Message-ID: Will Yardley writes: > yet the problem seemed to persist for more than an hour. > > Also, how can I flush the cache for a non-default instance's cache using > doveadm -- "doveadm auth cache flush" doesn't seem to have an '-a' > option AFAICT. If you only want to dump a few auth cache entries, you can just authenticate with a bad password. When a different (and possibly correct password) is supplied, there will be a cache miss and the new credentials will be cached. echo "1 login someuser badpassword\n2 logout" | netcat --ssl your-imap-server:993 Joseph Tam From dovecot.org at veggiechinese.net Fri Sep 19 02:54:57 2014 From: dovecot.org at veggiechinese.net (Will Yardley) Date: Thu, 18 Sep 2014 19:54:57 -0700 Subject: negative auth cache? In-Reply-To: <541B7A1A.5040608@thelounge.net> References: <20140919000938.GJ18052@aura.veggiechinese.net> <541B7A1A.5040608@thelounge.net> Message-ID: <20140919025457.GL18052@aura.veggiechinese.net> On Fri, Sep 19, 2014 at 02:34:34AM +0200, Reindl Harald wrote: > Am 19.09.2014 um 02:09 schrieb Will Yardley: > > > > Also, how can I flush the cache for a non-default instance's cache using > > doveadm -- "doveadm auth cache flush" doesn't seem to have an '-a' > > option AFAICT. > > > > # doveadm auth > > usage: doveadm [-Dv] [-f ] auth [] > > cache flush > > just hard restart dovecot > > the auth cache is not persistent Yes, that's how I've solved the problem so far. But since the problem doesn't affect all users, I'd obviously prefer not to do a hard restart of Dovecot just to fix it if there's a command that will clear the auth cache only. w From toni at solu.fi Fri Sep 19 03:49:16 2014 From: toni at solu.fi (Toni Mattila) Date: Fri, 19 Sep 2014 06:49:16 +0300 Subject: Panic: file index-status.c: line 131 (index_storage_get_open_status): assertion failed: (status_r->recent <= status_r->messages) Message-ID: <541BA7BC.4020102@solu.fi> Hi, Got a new one on 2.2.13: Sep 19 04:11:39 moxi dovecot: imap(cen at cor.ed): Error: Log synchronization error at seq=3,offset=144 for /Maildir/.Spam/dovecot.index: Extension record update for invalid uid=494 Sep 19 04:11:39 moxi dovecot: imap(cen at cor.ed): Warning: fscking index file /Maildir/.Spam/dovecot.index Sep 19 04:11:39 moxi dovecot: imap(cen at cor.ed): Panic: file index-status.c: line 131 (index_storage_get_open_status): assertion failed: (status_r->recent <= status_r->messages) Sep 19 04:11:39 moxi dovecot: imap(cen at cor.ed): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0 [0x1f2c1f] -> /usr/lib/dovecot/libdovecot.so.0 [0x1f2c9d] -> /usr/lib/dovecot/libdovecot.so.0 [0x1f2514] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_open_status+0x4d1) [0xcee761] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x42) [0xcee7f2] -> /usr/lib/dovecot/libdovecot-storage.so.0 [0xcd7b3a] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_get_open_status+0x4c) [0xcbe7ac] -> dovecot/imap [0x806485a] -> dovecot/imap(imap_sync_more+0x5cd) [0x8064edd] -> dovecot/imap [0x8065192] -> dovecot/imap(cmd_sync_delayed+0x1de) [0x80655de] -> dovecot/imap(client_handle_input+0x1c8) [0x805baa8] -> dovecot/imap(client_input+0x71) [0x805bd71] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x48) [0x204d88] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xff) [0x20675f] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x1e) [0x204 Sep 19 04:11:39 moxi dovecot: imap(cen at cor.ed): Fatal: master: service(imap): child 17680 killed with signal 6 (core dumped) (gdb) bt full #0 0x00b8f402 in __kernel_vsyscall () No symbol table info available. #1 0x0070af30 in raise () from /lib/i686/nosegneg/libc.so.6 No symbol table info available. #2 0x0070c911 in abort () from /lib/i686/nosegneg/libc.so.6 No symbol table info available. #3 0x001f2c14 in default_fatal_finish (type=, status=0) at failures.c:193 backtrace = 0x8760180 "/usr/lib/dovecot/libdovecot.so.0 [0x1f2c1f] -> /usr/lib/dovecot/libdovecot.so.0 [0x1f2c9d] -> /usr/lib/dovecot/libdovecot.so.0 [0x1f2514] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_get_"... #4 0x001f2c9d in i_internal_fatal_handler (ctx=0xbf827d74, format=0xd219b0 "file %s: line %d (%s): assertion failed: (%s)", args=0xbf827d94 "\225??") at failures.c:657 status = 0 #5 0x001f2514 in i_panic (format=0xd219b0 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:267 ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0} args = 0xbf827d94 "\225??" #6 0x00cee761 in index_storage_get_open_status (box=0x877c968, items=, status_r=0x87adaa8) at index-status.c:131 hdr = (const struct mail_index_header *) 0x87aabd0 __FUNCTION__ = "index_storage_get_open_status" #7 0x00cee7f2 in index_storage_get_status (box=0x877c968, items=139, status_r=0x87adaa8) at index-status.c:48 No locals. #8 0x00cd7b3a in index_list_get_status (box=0x877c968, items=139, status_r=0x87adaa8) at mailbox-list-index-status.c:165 No locals. #9 0x00cbe7ac in mailbox_get_open_status (box=0x877c968, items=139, status_r=0x87adaa8) at mail-storage.c:1539 __FUNCTION__ = "mailbox_get_open_status" #10 0x0806485a in imap_sync_finish (ctx=0x87ada90, aborting=false) at imap-sync.c:321 client = (struct client *) 0x877d9d0 ret = 0 #11 0x08064edd in imap_sync_more (ctx=0x87ada90) at imap-sync.c:621 str = (string_t *) 0x8760030 ret = 1 __FUNCTION__ = "imap_sync_more" #12 0x08065192 in cmd_sync_continue (sync_cmd=0x877e438) at imap-sync.c:659 cmd = prev = client = (struct client *) 0x877d9d0 ctx = (struct imap_sync_context *) 0x87ada90 ret = __FUNCTION__ = "cmd_sync_continue" #13 0x080655de in cmd_sync_delayed (client=0x877d9d0) at imap-sync.c:749 _data_stack_cur_id = 3 #14 0x0805baa8 in client_handle_input (client=0x877d9d0) at imap-client.c:904 remove_io = false handled_commands = true __FUNCTION__ = "client_handle_input" #15 0x0805bd71 in client_input (client=0x877d9d0) at imap-client.c:931 cmd = output = (struct ostream *) 0x877e320 bytes = 216 __FUNCTION__ = "client_input" #16 0x00204d88 in io_loop_call_io (io=0x877e3b8) at ioloop.c:441 ioloop = (struct ioloop *) 0x8768498 t_id = 2 __FUNCTION__ = "io_loop_call_io" #17 0x0020675f in io_loop_handler_run_internal (ioloop=0x8768498) at ioloop-epoll.c:220 ctx = event = (const struct epoll_event *) 0x8769650 list = (struct io_list *) 0x8769f48 io = (struct io_file *) 0x6 tv = {tv_sec = 1787, tv_usec = 891154} msecs = ret = 1 i = 0 j = 0 call = false __FUNCTION__ = "io_loop_handler_run_internal" #18 0x00204e2e in io_loop_handler_run (ioloop=0x8768498) at ioloop.c:488 No locals. #19 0x00204eb8 in io_loop_run (ioloop=0x8768498) at ioloop.c:465 __FUNCTION__ = "io_loop_run" #20 0x001ab42d in master_service_run (service=0x87683c0, callback=0x8066000 ) at master-service.c:566 No locals. #21 0x08065e9f in main (argc=Cannot access memory at address 0x0 ) at main.c:400 login_set = {auth_socket_path = 0x8760038 "P", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x80660c0 , failure_callback = 0x8066060 , request_auth_token = 1} service_flags = storage_service_flags = MAIL_STORAGE_SERVICE_FLAG_DISALLOW_ROOT username = 0x0 c = set_roots = {0x806daa0, 0x0} From e1c1bac6253dc54a1e89ddc046585792 at posteo.net Fri Sep 19 05:01:26 2014 From: e1c1bac6253dc54a1e89ddc046585792 at posteo.net (Philipp) Date: Fri, 19 Sep 2014 07:01:26 +0200 Subject: LDAP and dovecot In-Reply-To: <201409182006.s8IK6Zj20017@outputservices.com> References: <201409182006.s8IK6Zj20017@outputservices.com> Message-ID: <725ff70d8f853ce6b1eeb2e53822b7cd@posteo.de> Am 18.09.2014 22:06 schrieb dovecot at outputservices.com: > /dovecot/etc/dovecot/tests/ldap.settings > hosts = ldap.outputservices.com > tls = no > ldap_version = 3 > base = dc=ldap,dc=outputservices,dc=com > ------------------------------------------- This will likely also need later on: scope = subtree #since ou=People subtree used user_filter = (uid=%Ln) > 2014-09-18 09:44:33 auth: Fatal: LDAP: Buggy LDAP library returned > wrong fd: 1 That's the current problem, might happen that dovecot dynamically doesnt load the installed openldap libraries - or from a wrong ELFCLASS (32/64). Check with file(1) and ldd(1) on the dovecot binary, linked libraries and adjust library loadpaths with crle(1) (note differences for 32/64bit). HTH, Philipp From skdovecot at smail.inf.fh-brs.de Fri Sep 19 06:21:51 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Fri, 19 Sep 2014 08:21:51 +0200 (CEST) Subject: negative auth cache? In-Reply-To: <20140919000938.GJ18052@aura.veggiechinese.net> References: <20140919000938.GJ18052@aura.veggiechinese.net> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 18 Sep 2014, Will Yardley wrote: > Also, how can I flush the cache for a non-default instance's cache using > doveadm -- "doveadm auth cache flush" doesn't seem to have an '-a' > option AFAICT. > > # doveadm auth > usage: doveadm [-Dv] [-f ] auth [] > cache flush mhm: -a does not have no relationship to (Dovecot) "instance". doveadm auth cache flush flushes all the auth cache, no selection of an user possible, no need for - -a. doveadm -i instance_name auth cache flush should flush all the auth cache of the specified instance. Note the "-i" preceeds the command. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBVBvLf3z1H7kL/d9rAQKNiggAiNDAsp6rsiaG/UYT3hsQi8zwjTNUtfcy 3e2Joe6nRo+7ie9Uuy3P3qqY63q113cEaPEjhu+bGPyNHkMeLOAw7/l3RB+YomJo DMqke+Yyb5I3GlZOHmWtZlFDSN9qW/B7YFu8YhXSRy4+g4hWzJl/zTbcmx4uBZnM Ii0Cy5qN1BLqXKhmsYeY4YQibVHvRslxRxLKXU/aLokARin9M4eUocZ79gvG9MIu BM2PmvArvNtCE9+lafkDgr8rqVxfdh5nt2pWVdswtNra/5OWrUH0U3ks2+/WZ2lw U+0iLsL4gnadYY7cBGo0XexGUX7ZlU1+Nb1+I9Oj+HJPx2C9IF1h0Q== =Wmo2 -----END PGP SIGNATURE----- From dovecot.org at veggiechinese.net Fri Sep 19 06:41:14 2014 From: dovecot.org at veggiechinese.net (Will Yardley) Date: Thu, 18 Sep 2014 23:41:14 -0700 Subject: negative auth cache? In-Reply-To: References: <20140919000938.GJ18052@aura.veggiechinese.net> Message-ID: <20140919064114.GA72635@aura.veggiechinese.net> On Fri, Sep 19, 2014 at 08:21:51AM +0200, Steffen Kaiser wrote: > On Thu, 18 Sep 2014, Will Yardley wrote: > > > Also, how can I flush the cache for a non-default instance's cache using > > doveadm -- "doveadm auth cache flush" doesn't seem to have an '-a' > > option AFAICT. > > mhm: -a does not have no relationship to (Dovecot) "instance". > > doveadm auth cache flush > > flushes all the auth cache, no selection of an user possible, no need for > - -a. > > doveadm -i instance_name auth cache flush > > should flush all the auth cache of the specified instance. Note the "-i" > preceeds the command. That doesn't give an error, but strace shows this: [...] connect(8, {sa_family=AF_FILE, path="/var/run/dovecot-director/auth-master"}, 110) = 0 (is it connecting to the wrong instance's auth socket? the path to the 'main' instance's auth socket is /var/run/dovecot-main/auth-master) and then I see # doveadm -i main auth cache flush 0 cache entries flushed (strace shows this, which is the same thing I see from the director instance). write(1, "0 cache entries flushed\n", 240 cache entries flushed ) = 24 The 'main' instance should definitely have plenty of auth cache entries these are fairly busy systems, and the cache TTL is 5 minutes. Also, while I'd seen the use of the '-i flag, I didn't realize it was supported in this version, as '-i' doesn't seem to be listed in doveadm(1) or in the usage for doveadm. w From dovecot.org at veggiechinese.net Fri Sep 19 06:51:55 2014 From: dovecot.org at veggiechinese.net (Will Yardley) Date: Thu, 18 Sep 2014 23:51:55 -0700 Subject: negative auth cache? In-Reply-To: <20140919064114.GA72635@aura.veggiechinese.net> References: <20140919000938.GJ18052@aura.veggiechinese.net> <20140919064114.GA72635@aura.veggiechinese.net> Message-ID: <20140919065155.GB72635@aura.veggiechinese.net> On Thu, Sep 18, 2014 at 11:41:14PM -0700, Will Yardley wrote: > (is it connecting to the wrong instance's auth socket? the path to the > 'main' instance's auth socket is /var/run/dovecot-main/auth-master) > > and then I see > # doveadm -i main auth cache flush > 0 cache entries flushed Seems that the problem was that I had a symlink (for convenience) of /var/run/dovecot to /var/run/dovecot-director (so that I don't have to specify the instance name for common operations, which mostly involve the director). If I remove that symlink, and run the command with '-i main' # doveadm -i main auth cache flush 904 cache entries flushed The relevant code is something like: if (auth_socket_path == NULL) { auth_socket_path = t_strconcat(doveadm_settings->base_dir, "/auth-master", NULL); I'm guessing that auth_socket_path isn't null for some reason, and thus the auth_socket_path isn't constructed correctly in this case, even though the instance is being specified? # doveadm instance list path name last used running /var/run/dovecot-director director 2014-09-18 20:01:12 yes /var/run/dovecot-main main 2014-09-18 20:01:12 yes # doveconf -i main base_dir base_dir = /var/run/dovecot-main w From teemu.huovila at dovecot.fi Fri Sep 19 06:55:51 2014 From: teemu.huovila at dovecot.fi (Teemu Huovila) Date: Fri, 19 Sep 2014 09:55:51 +0300 Subject: doveadm with multiple instances on same machine(s) In-Reply-To: <20140919000413.GI18052@aura.veggiechinese.net> References: <20140919000413.GI18052@aura.veggiechinese.net> Message-ID: <541BD377.2080405@dovecot.fi> On 09/19/2014 03:04 AM, Will Yardley wrote: > Couple questions about running doveadm with multiple instances... I have > Dovecot 2.2.13 on RHEL6 running across 3 boxes, each with a director and > main instance running. When I try to lookup something on the main > instance (which is handling user auth) via its auth-userdb socket > directly, I get an error: > > # doveadm auth lookup -a /var/run/dovecot-main/auth-userdb myuser > doveadm(root): Error: passdb lookup failed for myuser: Configured passdbs don't support crentials lookups > > When I use the default lookup map, I just get the proxy settings that > are configured in the director instance's authdb. > # doveadm auth lookup myuser > passdb: myuser > user : myuser > proxy : y > nopassword: y > > In addition, > "doveadm director map" > > can't map the username -I get the error: > doveadm(root): Error: User listing returned failure > doveadm(root): Error: user listing failed > [then I get the whole list, but with for each user] Assuming your configuration is otherwise ok, I think this was fixed in http://hg.dovecot.org/dovecot-2.2/rev/8b5664bce4a0 and http://hg.dovecot.org/dovecot-2.2/rev/ccc5701dae72 so it will be included in Dovecot 2.2.14 > > The director itself doesn't have the LDAP passdb that the main dovecot > instance talks to, but I have, in the director config: > > service doveadm { > inet_listener { > port = 8889 > } > } > director_doveadm_port = 8889 > > local 192.168.x.x/24 { > doveadm_password = XXXXXX > } > > doveadm_proxy_port = 8888 In the 2.2 series you can write this as "doveadm_port", I think. br, Teemu Huovila From skdovecot at smail.inf.fh-brs.de Fri Sep 19 07:37:56 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Fri, 19 Sep 2014 09:37:56 +0200 (CEST) Subject: unable to see mail when using telnet / open ssl In-Reply-To: <54195A75.40407@gmail.com> References: <54195A75.40407@gmail.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, 17 Sep 2014, Dave Myers wrote: > I'm setting up my own VPS and working through getting mail to work. would you post the commands you use via telnet and the logs you get. > Here is my dovecot -n > > $dovecot -n > maildir:%h/%d/%n/mail : layout=fs ^^ were does this string come from? > # 2.1.7: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.32-5-xen-amd64 x86_64 Debian 6.0.3 > auth_debug = yes > auth_debug_passwords = yes > auth_mechanisms = plain login cram-md5 > auth_verbose = yes > auth_verbose_passwords = plain > lda_mailbox_autocreate = yes > log_path = /var/log/dovecot.log > mail_debug = yes > mail_gid = 1002 > mail_home = /var/mail/virtual/%d/%n > mail_location = maildir:~/mail: layout=fs > mail_uid = 1002 > 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 = scheme=SHA512-CRYPT username_format=%u /etc/dovecot/users > driver = passwd-file > } > protocols = imap > service auth { > unix_listener auth-client { > mode = 0660 > user = mail > } > } > service imap-login { > inet_listener imap { > port = 143 > } > inet_listener imaps { > port = 993 > ssl = yes > } > } > ssl_cert = ssl_key = userdb { > args = username_format=%u /etc/dovecot/users > driver = passwd-file > } > userdb { > driver = passwd > } > verbose_ssl = yes > > > I can successfully log into dovecot using telnet and open ssl from a remote > terminal, so authentication and everything is working fine. > > From the above dovecot -n I asume that mails should be going to > /var/mail/virtual/domain/user/mail > > However when I view this directory I can see a number of test mails that I > have sent using > > echo "Hello me" | mail -s "Dovecot test" $USER > > (see http://wiki2.dovecot.org/FindMailLocation) > > Why am I not seeing them when I use telnet / openSSL to log in? > > All help is greately appreciated. > > - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBVBvdVHz1H7kL/d9rAQK6swgAnMXg6A0z8xzKp8rxU9i2UOalEPPJ70EF vWxgQSb4RJ0aRieazfkWSHnZXZD79T28VXMaPLEG6/B6bQ3eGu3YfCz1pAqiuMkU 2jA9cNIyyJY/suA7JBk9eHI3RBiPfW0Ts7ujDqmKdc1MhYUtco4Y7g06di93i7RI oPcbwMIPVw2FbOto4Zic12hW1pDDlKBaBAIic7Y86HpJiK1GybRXfEDX73/zQJQA e3UBOmDoaK2IYGvQV3+E7c0M2PzxiQ50qJR8Rzkbh0GhaToypA+f6awiC1ZazEdK nks9o+qQCzOxU5OjfCZEXQC2SO8ng7iKxMyD3/XQ9PUZPVIcF4yMhQ== =kSlh -----END PGP SIGNATURE----- From david.myers.24j74 at gmail.com Fri Sep 19 07:54:36 2014 From: david.myers.24j74 at gmail.com (Dave Myers) Date: Fri, 19 Sep 2014 09:54:36 +0200 Subject: dovecot doesn't see my mails ? Message-ID: <541BE13C.6080004@gmail.com> Dear dovecot users. I have an odd issue in that when I connect to my dovecot server from either a local or remote system I can't see my test emails (I have the impression that is is looking at the wrong location on disk). here are some details.... # dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-xen-amd64 x86_64 Debian 6.0.3 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login cram-md5 auth_verbose = yes auth_verbose_passwords = plain lda_mailbox_autocreate = yes log_path = /var/log/dovecot.log mail_debug = yes mail_gid = 1002 mail_home = /var/mail/virtual/%d/%n mail_location = maildir:~/mail/: mail_uid = 1002 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 = scheme=SHA512-CRYPT username_format=%u /etc/dovecot/users driver = passwd-file } protocols = imap service auth { unix_listener auth-client { mode = 0660 user = mail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } ssl_cert = , method=PLAIN, rip=85.170.90.200, lip=92.39.247.92, mpid=26570, TLS, session= Sep 19 07:37:59 imap(websales at exsportee.biz): Debug: Effective uid=1002, gid=1002, home=/var/mail/virtual/exsportee.biz/websales Sep 19 07:37:59 imap(websales at exsportee.biz): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/mail/: Sep 19 07:37:59 imap(websales at exsportee.biz): Debug: maildir++: root=/var/mail/virtual/exsportee.biz/websales/mail, index=, control=, inbox=/var/mail/virtual/exsportee.biz/websales/mail, alt= So I can see that the directories that Dovecot is looking at are: home=/var/mail/virtual/exsportee.biz/websales location=maildir:~/mail/ So if I understand, dovecot is looking at [ /var/mail/virtual/exsportee.biz/websales/mail/ ] for my mail. When I run a listing of the directory I get the following.... # ls -al /var/mail/virtual/exsportee.biz/websales/mail/ total 44 drwx--S--- 5 vmail vmail 4096 Sep 18 12:46 . drwxr-sr-x 3 vmail vmail 4096 Sep 18 12:00 .. drwx--S--- 2 vmail vmail 4096 Sep 18 12:17 cur -rw------- 1 vmail vmail 248 Sep 18 12:23 dovecot.index.log -rw------- 1 vmail vmail 51 Sep 18 12:23 dovecot-uidlist -rw------- 1 vmail vmail 8 Sep 18 12:17 dovecot-uidvalidity -r--r--r-- 1 vmail vmail 0 Sep 18 12:17 dovecot-uidvalidity.541acd49 drwx--S--- 2 vmail vmail 4096 Sep 18 12:17 new -rw------- 1 vmail vmail 561 Sep 18 12:22 q1XUaj8-5382575 -rw------- 1 vmail vmail 517 Sep 18 12:00 q1XUaOD-5382570 -rw------- 1 vmail vmail 513 Sep 18 12:46 q1XUb60-5382584 drwx--S--- 2 vmail vmail 4096 Sep 18 12:17 tmp the 3 files q1xu[....] are test mails that I sent to myself, either internally from the localhost CLI, mutt or from my google mail account. I should note the following: ~ SWAKS can send mails out to external addresses also. ~ I cannot connect to my mail from any external clients (thunderbird) ~ I cannot connect to my mail localy using MUTT ~ I use exim4 (v4.7.2) as my MTA (if you want to see a config just ask). please help me resolve these issues. thanks in advance. David -- Tel: + 33 6 50 14 39 34 email: david.myers.24j74 at gmail.com Addres: 22 Rue de L'Eglise 77700 Coupvray. 77700 France From fvl at mail.ru Fri Sep 19 08:01:04 2014 From: fvl at mail.ru (=?UTF-8?B?0KTQsNC00LXQtdCyINCS0LjRgtCw0LvQuNC5INCb0YzQstC+0LLQuNGH?=) Date: Fri, 19 Sep 2014 12:01:04 +0400 Subject: =?UTF-8?B?U3lzbG9nIFBJRA==?= Message-ID: <1411113664.927426178@f25.i.mail.ru> Hi! How to write PIDs to syslog? Example: Sep 19 00:57:00 hostname dovecot: pop3-login: Login: user=< username at domainname.com >, method=PLAIN, rip=XXX.XXX.XXX.XXX, lip=XXX.XXX.XXX.XXX, mpid=14407, TLS, session=<6LYlcmYDAQC4reGs> Sep 19 00:57:00 hostname dovecot: pop3( username at domainname.com ): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0 Sep 19 00:57:09 hostname exim[14423]: 2014-09-19 00:57:09 dovecot_login authenticator failed for s16010629.onlinehome-server.info (User) [82.165.16.9]: 535 Incorrect authentication data (set_id=front) Sep 19 00:57:09 hostname exim[14424]: 2014-09-19 00:57:09 dovecot_login authenticator failed for s16010629.onlinehome-server.info (User) [82.165.16.9]: 535 Incorrect authentication data (set_id=front I need it because i write all logs to postgresql and analyze them with Adiscon LogAnalyzer. Perhaps, per-process logs entry with PID would be better. From skdovecot at smail.inf.fh-brs.de Fri Sep 19 08:16:18 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Fri, 19 Sep 2014 10:16:18 +0200 (CEST) Subject: dovecot doesn't see my mails ? In-Reply-To: <541BE13C.6080004@gmail.com> References: <541BE13C.6080004@gmail.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 19 Sep 2014, Dave Myers wrote: > a select INBOX > * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) > * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags > permitted. > * 0 EXISTS > * 0 RECENT that's correct for your case > So I seem to have no mails in the inbox... so I check the dovecot log for the > where it thinks it should be looking for the mail > > Sep 19 07:37:59 imap-login: Info: Login: user=, > method=PLAIN, rip=85.170.90.200, lip=92.39.247.92, mpid=26570, TLS, > session= > Sep 19 07:37:59 imap(websales at exsportee.biz): Debug: Effective uid=1002, > gid=1002, home=/var/mail/virtual/exsportee.biz/websales > Sep 19 07:37:59 imap(websales at exsportee.biz): Debug: Namespace inbox: > type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, > subscriptions=yes location=maildir:~/mail/: > Sep 19 07:37:59 imap(websales at exsportee.biz): Debug: maildir++: > root=/var/mail/virtual/exsportee.biz/websales/mail, index=, control=, > inbox=/var/mail/virtual/exsportee.biz/websales/mail, alt= > > So I can see that the directories that Dovecot is looking at are: > home=/var/mail/virtual/exsportee.biz/websales > location=maildir:~/mail/ > > So if I understand, dovecot is looking at [ > /var/mail/virtual/exsportee.biz/websales/mail/ ] for my mail. When I run a > listing of the directory I get the following.... > > # ls -al /var/mail/virtual/exsportee.biz/websales/mail/ > total 44 > drwx--S--- 5 vmail vmail 4096 Sep 18 12:46 . > drwxr-sr-x 3 vmail vmail 4096 Sep 18 12:00 .. > drwx--S--- 2 vmail vmail 4096 Sep 18 12:17 cur > -rw------- 1 vmail vmail 248 Sep 18 12:23 dovecot.index.log > -rw------- 1 vmail vmail 51 Sep 18 12:23 dovecot-uidlist > -rw------- 1 vmail vmail 8 Sep 18 12:17 dovecot-uidvalidity > -r--r--r-- 1 vmail vmail 0 Sep 18 12:17 dovecot-uidvalidity.541acd49 > drwx--S--- 2 vmail vmail 4096 Sep 18 12:17 new > -rw------- 1 vmail vmail 561 Sep 18 12:22 q1XUaj8-5382575 > -rw------- 1 vmail vmail 517 Sep 18 12:00 q1XUaOD-5382570 > -rw------- 1 vmail vmail 513 Sep 18 12:46 q1XUb60-5382584 > drwx--S--- 2 vmail vmail 4096 Sep 18 12:17 tmp > > the 3 files q1xu[....] are test mails that I sent to myself, either > internally from the localhost CLI, mutt or from my google mail account. > I should note the following: > ~ SWAKS can send mails out to external addresses also. > ~ I cannot connect to my mail from any external clients (thunderbird) > ~ I cannot connect to my mail localy using MUTT > ~ I use exim4 (v4.7.2) as my MTA (if you want to see a config just ask). The files q1.. belong to ~/mail/new/ . Exim does not spool them as Maildir. I would recommend to use Dovecot LDA or LMTP. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBVBvmUnz1H7kL/d9rAQLkhwf9ESRHs6R4nJmkbCUzcT0X1ddK13itnZLT jOHe2S7fK13CTyWK9sg4mQZOaU5fadJ6i/POfrg9UL8farKnbH8+UoHSKI1Qm+M+ j14aAwChKAneDviIFW0TIZ6dtjsuBW878Mzal4sy+4GiUIebVB4uff3QdqFi2uFS A0zch3Cu0rINdzXqfKPo3kTRjHpVk+V0dlawl1EhJKFSeNvXqa7apQFQctDa7F47 JcywvC6oMBxbwdJQhq7o8IsA9AqjhiXVvGa852yEUc2cO5knfmWcLLcCtAlSXHIq QwE7U0U3nYnfLv2RksXx+X5+Jrpai3KAIo4awvnzfGrsxdZ43mywfA== =ZLQP -----END PGP SIGNATURE----- From skdovecot at smail.inf.fh-brs.de Fri Sep 19 08:19:04 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Fri, 19 Sep 2014 10:19:04 +0200 (CEST) Subject: Syslog PID In-Reply-To: <1411113664.927426178@f25.i.mail.ru> References: <1411113664.927426178@f25.i.mail.ru> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 19 Sep 2014, ?????? ??????? ??????? wrote: > How to write PIDs to syslog? use %p, see http://wiki2.dovecot.org/Variables and log_format - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBVBvm+Hz1H7kL/d9rAQKHgQf+PU39QjKiEfwBTyl33H9j3ouG/veb+c+5 dqEU60AnVO+5NRceuQMfbf0leHQRazGQfeAVJYLDZa61w7hBme7vhCa0IGpUObq7 qlgcU/zIwO/JPuPsDEMfiQp/5VjLRSaCK/U11PQ+KYCuvjppozh9/vGsuQA4Kquo 8qKIkA+hR9aFD7GMXLGiVZ/qeRF7hF48jEUY9aBivGgnwPh1nBFEOyxQGIf6rvSB IoIi0HLzVRQcF7l0XA7+//fPaPw/jERgGDbrp7xlLGzJpLtKdnXIxhm2Mbtp7Di9 zCdfF7N6Ow9f+hOl+xkMPkdO3qRi9YaKwWlWhoY/bI7av1xjuDf97g== =uxVt -----END PGP SIGNATURE----- From dawid.stawiarski at netart.pl Fri Sep 19 09:05:22 2014 From: dawid.stawiarski at netart.pl (Dawid Stawiarski - nazwa.pl) Date: Fri, 19 Sep 2014 11:05:22 +0200 Subject: quota recalc problem for big maildirs Message-ID: <541BF1D2.9010807@netart.pl> hi, we use dovecot 2.2.13, and we've lately started using maildir quota (previously fs quota was used, right now it's "quota = maildir:User quota" changed from "quota = fs:User quota:user:inode_per_mail"). When the change was applied we didn't manually forced generating maildirsize files. So, when the first deliver happens (or the file grows larger then 5KB) it starts quota recalc. However for users with big maildirs, receiving email every couple of seconds, there are tens of delivery processes each doing its own recalc (as they open file for APPEND and there's no locking). What's even worse, after all the stats and getdents (it takes a lot of IO for 60GB account with 2M emails), deliver makes stat on 'new' dir and detects changes after which it unlinks freshly created maildirsize. So possibly this will never be finished as every process drops its own work. The same thing happened when we checked the native dovecot LMTP server (every connection has its own forked process - each running independently of the others). Is it a known unwanted "feature" of maildir quota (and we should use dict quota instead) or a bug that will be fixed? cheers, Dawid Stawiarski From david.myers.24j74 at gmail.com Fri Sep 19 09:30:41 2014 From: david.myers.24j74 at gmail.com (Dave Myers) Date: Fri, 19 Sep 2014 11:30:41 +0200 Subject: dovecot doesn't see my mails ? In-Reply-To: References: <541BE13C.6080004@gmail.com> Message-ID: <541BF7C1.6040703@gmail.com> @Steffen, Thanks for your input, and please excuse my clearly stupid questions.. ;) > The files q1.. belong to ~/mail/new/ . Exim does not spool them as > Maildir. I would recommend to use Dovecot LDA or LMTP. where / how do I get that to work ? I've added the required stuff to the dovecot and exim configs, but clearly I need to install dovecot-lmtpd (error message about not finding the executable) However I needed to install dovecot from source (as I couldn't get the server to accept backports ?). Any advice on upgrading / changing the install ? Can I simply make a copy of the whole of my config (which otherwise works), then do the same install from a /deb source file for lmtpd, then copy my config back to this location? Or do you advise some other path for the upgrade ? thanks. David -- Tel: + 33 6 50 14 39 34 email: david.myers.24j74 at gmail.com Addres: 22 Rue de L'Eglise 77700 Coupvray. 77700 France From skdovecot at smail.inf.fh-brs.de Fri Sep 19 09:42:24 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Fri, 19 Sep 2014 11:42:24 +0200 (CEST) Subject: dovecot doesn't see my mails ? In-Reply-To: <541BF7C1.6040703@gmail.com> References: <541BE13C.6080004@gmail.com> <541BF7C1.6040703@gmail.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 19 Sep 2014, Dave Myers wrote: > Thanks for your input, and please excuse my clearly stupid questions.. ;) >> The files q1.. belong to ~/mail/new/ . Exim does not spool them as Maildir. >> I would recommend to use Dovecot LDA or LMTP. > > where / how do I get that to work ? http://wiki2.dovecot.org/Variables?action=fullsearch&context=180&value=Exim&titlesearch=Titles See LDA or LMTP > I've added the required stuff to the dovecot and exim configs, but clearly I > need to install > dovecot-lmtpd (error message about not finding the executable) Maybe, you should begin with the LDA then. > However I needed to install dovecot from source (as I couldn't get the server > to accept backports ?). Any advice on upgrading / changing the install ? > > Can I simply make a copy of the whole of my config (which otherwise works), > then do the same install from a /deb source file for lmtpd, then copy my > config back to this location? > > Or do you advise some other path for the upgrade ? Usually, you see how Debian compiles the source - the ./configure options . But I wonder if you want to overwrite the system places. That's you decision. I would: use the LDA now, in order to get the server to work. Then use a test system for the LMTP stuff. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBVBv6gHz1H7kL/d9rAQIkKQgAnwoUc1dkScpy2ieOUehint1kGmBDE55N DiPScj6mrZ0H00vANsQzv9Gg29MskvuPeryXuJtlUGYDvof+YEDnvlJBOT12zNE0 dogIihys00CEzeKqWfI9nk4IPJMB0W7mPznY5Lb+lqrovHLzEzwyNE8XMe8dOefS kW8P1Etwmr/tGub5S7Xz4sgAWfqybjH+DrUVJIEKYuMVtqz3VvHNP1E9i9Cbppr8 0aXTLFheBJ/azoz+1CsF99NRV2MrhHvehneTIVPECOVQSTk2YXipP1+3+i2VK/+Q aPS/wqH0sujU5HphuwUee8saAD/aycklBk4lzhBPQuNoeAEI+ZEs7Q== =Sx8+ -----END PGP SIGNATURE----- From me at junc.eu Fri Sep 19 09:49:44 2014 From: me at junc.eu (Benny Pedersen) Date: Fri, 19 Sep 2014 11:49:44 +0200 Subject: dovecot doesn't see my mails =?UTF-8?Q?=3F?= In-Reply-To: <541BF7C1.6040703@gmail.com> References: <541BE13C.6080004@gmail.com> <541BF7C1.6040703@gmail.com> Message-ID: Dave Myers skrev den 2014-09-19 11:30: > where / how do I get that to work ? http://wiki2.dovecot.org/LDA/Exim From david.myers.24j74 at gmail.com Fri Sep 19 09:52:15 2014 From: david.myers.24j74 at gmail.com (Dave Myers) Date: Fri, 19 Sep 2014 11:52:15 +0200 Subject: dovecot doesn't see my mails ? In-Reply-To: References: <541BE13C.6080004@gmail.com> <541BF7C1.6040703@gmail.com> Message-ID: <541BFCCF.60202@gmail.com> On 19/09/14 11:42, Steffen Kaiser wrote: > Usually, you see how Debian compiles the source - the ./configure > options . But I wonder if you want to overwrite the system places. > That's you decision. I would: use the LDA now, in order to get the > server to work. Then use a test system for the LMTP stuff. Ok thanks for the advice.... David -- Tel: + 33 6 50 14 39 34 email: david.myers.24j74 at gmail.com Addres: 22 Rue de L'Eglise 77700 Coupvray. 77700 France From alex.yegorov at gmail.com Fri Sep 19 10:35:42 2014 From: alex.yegorov at gmail.com (=?KOI8-R?B?4czFy9PBzsTSIOXHz9LP1w==?=) Date: Fri, 19 Sep 2014 13:35:42 +0300 Subject: Support of unicode in then recipient names Message-ID: Hi Dovecot Community, We are using ltmp to deliver messages through postfix to dovecot. During testing we have found that dovecot does not understand recipient email address if it is composed from national symbols : e.g. ???????@???????.??????? Question is are there any plans to either add native support for such email addresses or to translate it to punycode and then try to find such a recipient? -- ????????? ?????? (Alexander Yegorov) From david.myers.24j74 at gmail.com Fri Sep 19 13:17:07 2014 From: david.myers.24j74 at gmail.com (Dave Myers) Date: Fri, 19 Sep 2014 15:17:07 +0200 Subject: how to config dovecot from source with lmtp In-Reply-To: References: <541BE13C.6080004@gmail.com> <541BF7C1.6040703@gmail.com> Message-ID: <541C2CD3.4000700@gmail.com> Hi dovecot users, I've decided to re-install my dovecot-imapd server with lmtp functionality I've been looking at my dovecot source, it certainly contains an lmtp sub folder. I've looked at the details for the config of lda, and I wonder why (particularly as I installed from source) dovecot does not install with lmtp by default ? this is particularly in respect to the details on the wiki2 page: http://wiki2.dovecot.org/LDA Nowadays you should probably use the LMTP server instead, because it's somewhat easier to configure (especially related to permissions) and gives better performance. I've looked through to see how to build dovecot with ldmp support, and I don't find anything in the install doc page http://wiki2.dovecot.org/CompilingSource that explains what switch I need to use to add compatibility for lmtp. I will admit I've not looked very far outside of the official dovecot site, but then most of the google hits return me straight to the above mentioned pages. I should also note that when I downloaded the 'newest version' of dovecot using : wget http://www.dovecot.org/releases/2.2/dovecot-2.2.13.tar.gz Everything goes fine, after doing the stuff a dovecot -n returns # 2.2.13: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-xen-amd64 x86_64 Debian 6.0.3 Which is pleasing, as previously it return 2.1.7 I haven't changed any of my config files, looking at the upgradeing page on the wiki it would seem I haven't set any configs that require it. I now restart the process. $ sudo /etc/init.d/dovecot restart Restarting IMAP/POP3 mail server: dovecotFatal: service(lmtp) access(/usr/lib/dovecot/lmtp) failed: No such file or directory failed! I can confirm that the file it is looking for doesn't exist, but how do I configure the install of dovecot to include it? thanks in advance for your advice David ___________ I include below a part of the original converstion that has led me to decide to add lmtp support to my install. On 19/09/14 11:42, Steffen Kaiser wrote: > >> >>> The files q1.. belong to ~/mail/new/ . Exim does not spool them as >>> Maildir. I would recommend to use Dovecot LDA or LMTP. > > http://wiki2.dovecot.org/Variables?action=fullsearch&context=180&value=Exim&titlesearch=Titles > > See LDA or LMTP > >> I've added the required stuff to the dovecot and exim configs, but >> clearly I need to install >> dovecot-lmtpd (error message about not finding the executable) > > Maybe, you should begin with the LDA then. > >> However I needed to install dovecot from source (as I couldn't get >> the server to accept backports ?). Any advice on upgrading / changing >> the install ? >> >> Can I simply make a copy of the whole of my config (which otherwise >> works), then do the same install from a /deb source file for lmtpd, >> then copy my config back to this location? >> >> Or do you advise some other path for the upgrade ? > > Usually, you see how Debian compiles the source - the ./configure > options . But I wonder if you want to overwrite the system places. > That's you decision. I would: use the LDA now, in order to get the > server to work. Then use a test system for the LMTP stuff. I've been looking at my dovecot source, it certainly contains an lmtp sub folder. I've looked at the details for the config of lda, and I wonder why (particularly as I installed from source) dovecot does not install with lmtp by default ? this is particularly in respect to the details on the wiki2 page: http://wiki2.dovecot.org/LDA Nowadays you should probably use the LMTP server instead, because it's somewhat easier to configure (especially related to permissions) and gives better performance. I've looked through to see how to build dovecot with ldmp support, and I don't find anything in the install doc page -- Tel: + 33 6 50 14 39 34 email: david.myers.24j74 at gmail.com Addres: 22 Rue de L'Eglise 77700 Coupvray. 77700 France From skdovecot at smail.inf.fh-brs.de Fri Sep 19 13:34:14 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Fri, 19 Sep 2014 15:34:14 +0200 (CEST) Subject: how to config dovecot from source with lmtp In-Reply-To: <541C2CD3.4000700@gmail.com> References: <541BE13C.6080004@gmail.com> <541BF7C1.6040703@gmail.com> <541C2CD3.4000700@gmail.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 19 Sep 2014, Dave Myers wrote: > # 2.2.13: /usr/local/etc/dovecot/dovecot.conf ^^^^^^^^ > # OS: Linux 2.6.32-5-xen-amd64 x86_64 Debian 6.0.3 > > Which is pleasing, as previously it return 2.1.7 > I haven't changed any of my config files, looking at the upgradeing page on > the wiki it would seem I haven't set any configs that require it. > > I now restart the process. > > $ sudo /etc/init.d/dovecot restart > Restarting IMAP/POP3 mail server: dovecotFatal: service(lmtp) > access(/usr/lib/dovecot/lmtp) failed: No such file or directory ^^^^^^^ > failed! > > I can confirm that the file it is looking for doesn't exist, but how do I > configure the install of dovecot to include it? I'd say that the application is wrong: did you've updated the /etc/init.d script? Maybe it points to Debian's build still. Maybe you have some setting in your config you copied from Debian's build? Otherwise: does your config.log indicates that you have set a prefix or "dir"? I use ./configure --prefix=/usr/local/.... and everything is down there. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBVBww1nz1H7kL/d9rAQIiCQf/UO+QUHnXY8lGpHawP16CcrzztytCIcLW Ul47bRwA2rnkmdnrCicaYTy7Ia3khqBDEu2861yNLe0JjaH3UWyRzOcQNzHuO8+Q FAmZnEMKRyj2gHVUUtBA2ouI3NuC9R3Rbb7Cb+4Cr7CTBzEf88Er9ycUcLykxc8L 8S2Xoe5EPWljORw9SV5z/ZgTmL9YUKZNTJeFJQu3Num7j8pOhnbS1u/yqtI7Is6B WGct1rT99UBN2DDJPKR5VI2lQVhMslWjEvw+MI+grtLWssKzaGY9vNZUNO07Ln4n axxWACDHz/G/hAeCoXVYb4uDCKYPL44tVHTeIQuw6l8YrqGKDEHUew== =jwql -----END PGP SIGNATURE----- From david.myers.24j74 at gmail.com Fri Sep 19 13:58:28 2014 From: david.myers.24j74 at gmail.com (Dave Myers) Date: Fri, 19 Sep 2014 15:58:28 +0200 Subject: how to config dovecot from source with lmtp In-Reply-To: References: <541BE13C.6080004@gmail.com> <541BF7C1.6040703@gmail.com> <541C2CD3.4000700@gmail.com> Message-ID: <541C3684.8060507@gmail.com> Thanks for the quick reply, Finaly I retried with ./configure --with-lmtp=yes and suddenly I have lmtp in the /usr/local/libexec/dovecot/ directory. On 19/09/14 15:34, Steffen Kaiser wrote: > > I'd say that the application is wrong: > > did you've updated the /etc/init.d script? Maybe it points to Debian's > build still. Maybe you have some setting in your config you copied > from Debian's build? I have built from source, I did apt-get purge dovecot (or whatever it is) before this, just to be sure I then removed any other dovecot directories that I found. And then of course there is a distinct lack of an init.d script for lmtp ? I'm not sure where I need to set the details for the location of the lmtp file. I guess I should be setting it in the service lmtp{....} section. alternatively what should the contents of the lmtp init.d script be? > > Otherwise: does your config.log indicates that you have set a prefix > or "dir"? > > I use ./configure --prefix=/usr/local/.... > > and everything is down there. > > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBVBww1nz1H7kL/d9rAQIiCQf/UO+QUHnXY8lGpHawP16CcrzztytCIcLW > Ul47bRwA2rnkmdnrCicaYTy7Ia3khqBDEu2861yNLe0JjaH3UWyRzOcQNzHuO8+Q > FAmZnEMKRyj2gHVUUtBA2ouI3NuC9R3Rbb7Cb+4Cr7CTBzEf88Er9ycUcLykxc8L > 8S2Xoe5EPWljORw9SV5z/ZgTmL9YUKZNTJeFJQu3Num7j8pOhnbS1u/yqtI7Is6B > WGct1rT99UBN2DDJPKR5VI2lQVhMslWjEvw+MI+grtLWssKzaGY9vNZUNO07Ln4n > axxWACDHz/G/hAeCoXVYb4uDCKYPL44tVHTeIQuw6l8YrqGKDEHUew== > =jwql > -----END PGP SIGNATURE----- -- Tel: + 33 6 50 14 39 34 email: david.myers.24j74 at gmail.com Addres: 22 Rue de L'Eglise 77700 Coupvray. 77700 France From jost+lists at dimejo.at Fri Sep 19 15:32:21 2014 From: jost+lists at dimejo.at (Alex JOST) Date: Fri, 19 Sep 2014 17:32:21 +0200 Subject: how to config dovecot from source with lmtp In-Reply-To: <541C2CD3.4000700@gmail.com> References: <541BE13C.6080004@gmail.com> <541BF7C1.6040703@gmail.com> <541C2CD3.4000700@gmail.com> Message-ID: <541C4C85.1040305@dimejo.at> Am 19.09.2014 um 15:17 schrieb Dave Myers: > Everything goes fine, after doing the stuff a dovecot -n returns > > # 2.2.13: /usr/local/etc/dovecot/dovecot.conf > # OS: Linux 2.6.32-5-xen-amd64 x86_64 Debian 6.0.3 > > Which is pleasing, as previously it return 2.1.7 Dovecot 2.1.7 comes via the squeeze-backports repository. My guess is that you added configuration for LMTP but didn't install the dovecot-lmtpd package. -- Alex JOST From dovecot at outputservices.com Fri Sep 19 21:11:37 2014 From: dovecot at outputservices.com (dovecot at outputservices.com) Date: Fri, 19 Sep 2014 15:11:37 -0600 (MDT) Subject: LDAP and dovecot Message-ID: <201409192111.s8JLBapr026726@sunfire.outputservices.com> I was able to decipher the error after looking at some other web pages. I found I have to compile using the openldap libraries instead of the default Solaris ldap libraries. I compiled using the following: > LDFLAGS='-L/usr/local/openldap/lib -R/usr/local/openldap/lib' \ > ./configure --prefix=/tmp/tocevod --with-ssl=openssl --with-solr --with-zlib --with-bzlib --with-ldap=yes ldd on the ....libexec/dovecot/auth files shows the proper openldap libraries. libdovecot.so.0 => /usr/local/tools/dovecot/lib/dovecot/libdovecot.so.0 libpam.so.1 => /usr/lib/libpam.so.1 libldap-2.4.so.2 => /usr/local/openldap/lib/libldap-2.4.so.2 libsasl.so.1 => /usr/lib/libsasl.so.1 libssl.so.0.9.7 => /usr/sfw/lib/libssl.so.0.9.7 libcrypto.so.0.9.7 => /usr/sfw/lib/libcrypto.so.0.9.7 liblber-2.4.so.2 => /usr/local/openldap/lib/liblber-2.4.so.2 libresolv.so.2 => /usr/lib/libresolv.so.2 libgen.so.1 => /usr/lib/libgen.so.1 librt.so.1 => /usr/lib/librt.so.1 libnsl.so.1 => /usr/lib/libnsl.so.1 libsocket.so.1 => /usr/lib/libsocket.so.1 libsendfile.so.1 => /usr/lib/libsendfile.so.1 libc.so.1 => /usr/lib/libc.so.1 libgcc_s.so.1 => /usr/sfw/lib/libgcc_s.so.1 libcmd.so.1 => /usr/lib/libcmd.so.1 libmd.so.1 => /usr/lib/libmd.so.1 libaio.so.1 => /usr/lib/libaio.so.1 libmp.so.2 => /usr/lib/libmp.so.2 libscf.so.1 => /usr/lib/libscf.so.1 libdoor.so.1 => /usr/lib/libdoor.so.1 libuutil.so.1 => /usr/lib/libuutil.so.1 libssl_extra.so.0.9.7 => /usr/sfw/lib/libssl_extra.so.0.9.7 libcrypto_extra.so.0.9.7 => /usr/sfw/lib/libcrypto_extra.so.0.9.7 libm.so.2 => /usr/lib/libm.so.2 I am not able to authenticate to my ldap server. Thank you all. From dovecot at outputservices.com Fri Sep 19 21:31:06 2014 From: dovecot at outputservices.com (dovecot at outputservices.com) Date: Fri, 19 Sep 2014 15:31:06 -0600 (MDT) Subject: LDAP and dovecot Message-ID: <201409192131.s8JLV6WV029042@sunfire.outputservices.com> I am sorry. I am NOW able to authenticate to my ldap server. Thank you all. From remko at FreeBSD.org Sat Sep 20 21:00:54 2014 From: remko at FreeBSD.org (Remko Lodder) Date: Sat, 20 Sep 2014 23:00:54 +0200 Subject: LDAP and dovecot In-Reply-To: <201409192131.s8JLV6WV029042@sunfire.outputservices.com> References: <201409192131.s8JLV6WV029042@sunfire.outputservices.com> Message-ID: <83DE5F13-FD19-40B8-96D6-1A7479C7B003@FreeBSD.org> On 19 Sep 2014, at 23:31, dovecot at outputservices.com wrote: > I am sorry. > > I am NOW able to authenticate to my ldap server. > > Thank you all. So what changed, for the records :) Remko -- /"\ Best regards, | remko at FreeBSD.org \ / Remko Lodder | remko at EFnet X http://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From robert at gillecaluim.com Mon Sep 22 05:59:35 2014 From: robert at gillecaluim.com (Robert Watson) Date: Sun, 21 Sep 2014 22:59:35 -0700 Subject: don't understand error message Message-ID: new installation of Dovecot 2.0.9 on Centos # telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN] Dovecot ready. LOGIN JohnDoe JohnDoe LOGIN BAD First parameter in line is IMAP's command tag, not the command name. Add that before the command, like: a login user pass ^] telnet> quit Connection closed. What's generating this error? Using samba4 ad for passdb/userdb. Robert From mihai at badici.ro Mon Sep 22 06:01:48 2014 From: mihai at badici.ro (Mihai Badici) Date: Mon, 22 Sep 2014 09:01:48 +0300 Subject: don't understand error message In-Reply-To: References: Message-ID: <1812813.ADG4MnGGSc@arhivio> Try: 01 login JohnDoe JohnDoe On Sunday 21 September 2014 22:59:35 Robert Watson wrote: > new installation of Dovecot 2.0.9 on Centos > # telnet localhost 143 > Trying 127.0.0.1... > Connected to localhost. > Escape character is '^]'. > * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE > STARTTLS AUTH=PLAIN] Dovecot ready. > LOGIN JohnDoe JohnDoe > LOGIN BAD First parameter in line is IMAP's command tag, not the command > name. Add that before the command, like: a login user pass > ^] > telnet> quit > Connection closed. > > What's generating this error? Using samba4 ad for passdb/userdb. > Robert -- Mihai B?dici http://mihai.badici.ro From nicolas at franceoxygene.fr Mon Sep 22 07:19:24 2014 From: nicolas at franceoxygene.fr (Nicolas Cauchie) Date: Mon, 22 Sep 2014 09:19:24 +0200 Subject: Authentication using AD : bug ? Message-ID: <541FCD7C.3050900@franceoxygene.fr> Hello, I've setup a mail server (still in test) with Postfix and Dovecot, authentication made using Active Directory. I authenticate my test user in AD well in Dovecot. However, if I change this user's password in AD, the old password still works for authentication in Dovecot and the new is working too. Is there a time to make Dovecot don't "remember" the old password or is it a bug ? Restarting Dovecot don't solve the problem. Do you already heard about this ? Please tell me what conf files you maybe need. Thanks in advance Nicolas signature ----- From jernej.porenta at arnes.si Mon Sep 22 07:42:54 2014 From: jernej.porenta at arnes.si (Jernej Porenta) Date: Mon, 22 Sep 2014 09:42:54 +0200 Subject: numeric username Message-ID: <541FD2FE.2070202@arnes.si> Heya, does dovecot support "numeric only" usernames (in format "^0-9+$")? We are unable to deliver emails to such usernames via LMTP: Sep 22 08:41:05 razor4 postfix/lmtp[2120]: D4FD91CDC11F: to=<231588 at example.org>, relay=example.org[private/dovecot-lmtp], delay=217653, delays=217653/0.01/0.02/0, dsn=4.2.0, status=deferred (host example.org[private/dovecot-lmtp] said: 451 4.2.0 <231588 at example.org> Permission denied (in reply to end of DATA command)) On normal username format (^[a-z][-a-z0-9]+$) everything is working fine. Permissions are the same as on other accounts: # ls -la .mailbox -rw-------+ 1 231588 users 0 Sep 19 20:13 .mailbox Using dovecot 2.2.13 with local accounts on RHEL and (relevant) configs: auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_username_format = %Ln auth_username_translation = ... lmtp_address_translate = ... passdb { args = cache_key=%u%s dovecot default_fields = deny = no driver = pam master = no name = override_fields = pass = no result_failure = continue result_internalfail = continue result_success = return-ok skip = never } ... service lmtp { chroot = client_limit = 1 drop_priv_before_exec = no executable = lmtp extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 5 protocol = lmtp service_count = 0 type = unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } unix_listener lmtp { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } .... userdb { args = default_fields = driver = passwd name = override_fields = result_failure = continue result_internalfail = continue result_success = return-ok skip = never } Thank you in advance, cheers, Jernej From andreas at cymail.eu Mon Sep 22 09:32:40 2014 From: andreas at cymail.eu (Andreas Kasenides) Date: Mon, 22 Sep 2014 12:32:40 +0300 Subject: =?UTF-8?Q?dovecot=C2=B4s=20multiple=20quota=20roots?= Message-ID: I am trying to find out how Dovecot behaves when there are multiple quota roots. I could not find something authoritative on this. For example, on a nicely running server that used fs quota I now have in 90-quota.conf > plugin { > quota = fs:Mail Quota:user:mount=/Mail > quota2 = maildir:Mail User Quota > } When I do > > doveadm quota get -u atrige01 > Quota name Type Value Limit > % > Mail Quota STORAGE 80036 204800 > 39 > Mail User Quota STORAGE 79306 - > 0 > Mail User Quota MESSAGE 304 - > 0 Apparently both STORAGE quotas values are the same. The question is which of the two is being used by Dovecot. If I insert a limit on the maildir quota which of the two will be used? I am using Dovecot 2.2.12. thank you From david.myers.24j74 at gmail.com Mon Sep 22 10:32:51 2014 From: david.myers.24j74 at gmail.com (Dave Myers) Date: Mon, 22 Sep 2014 12:32:51 +0200 Subject: how to solve : Dovecot version mismatch: Master is v2.1.7, lmtp is v2.2.13 Message-ID: <541FFAD3.9050303@gmail.com> Hello again dovecot list ;) I've recently upgraded my dovecot version from 2.1.7 to 2.2.13. both versions where installed from source. I upgraded why attempting to get lmtp working. I ultimately just coped the executable lmtp to the location that dovecot was expecting it to be in. but then the above error appeared. However when I get the info from dovecot I get the following... $ dovecot -n # 2.2.13: /usr/local/etc/dovecot/dovecot.conf so there seems to be an issue somewhere. I should note that I had copied my previous /conf.d/ files and then copied them back after the update. I guess that I have missed a switch during the build, or need to modify a line in the config somewhere that tells what the version is, but that doesn't explain why the dovecot -n returns the correct info, but the error reports something different. I am considering inserting the version_ignore=yes config option, but where should I insert it ? Thanks in advance. David -- Tel: + 33 6 50 14 39 34 email: david.myers.24j74 at gmail.com Addres: 22 Rue de L'Eglise 77700 Coupvray. 77700 France From h.reindl at thelounge.net Mon Sep 22 10:37:41 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Mon, 22 Sep 2014 12:37:41 +0200 Subject: how to solve : Dovecot version mismatch: Master is v2.1.7, lmtp is v2.2.13 In-Reply-To: <541FFAD3.9050303@gmail.com> References: <541FFAD3.9050303@gmail.com> Message-ID: <541FFBF5.4050105@thelounge.net> Am 22.09.2014 um 12:32 schrieb Dave Myers: > Hello again dovecot list ;) > > I've recently upgraded my dovecot version from 2.1.7 to 2.2.13. > both versions where installed from source. > > I upgraded why attempting to get lmtp working. I ultimately just coped the executable lmtp to the location that > dovecot was expecting it to be in. but then the above error appeared. why do you copy files around? if you update a software then make it complete and not copy random files around - installing from source would in general be better done by build packages because they care about obsoleted files and so on > However when I get the info from dovecot I get the following... > > $ dovecot -n > # 2.2.13: /usr/local/etc/dovecot/dovecot.conf > > so there seems to be an issue somewhere. > > I should note that I had copied my previous /conf.d/ files and then copied them back after the update. > > I guess that I have missed a switch during the build, or need to modify a line in the config somewhere that tells > what the version is, but that doesn't explain why the dovecot -n returns the correct info, but the error reports > something different. > > I am considering inserting the > version_ignore=yes > config option, but where should I insert it? no, you should make sure that you have only one version installed on your system and no old craft staying around -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From helge at kraak.info Mon Sep 22 11:01:23 2014 From: helge at kraak.info (Helge Kraak) Date: Mon, 22 Sep 2014 13:01:23 +0200 Subject: dsync error: Error: Can't delete mailbox INBOX: INBOX can't be deleted. In-Reply-To: <653A24C3-AA9C-4E1D-9B07-87F0E3985526@kraak.info> References: <653A24C3-AA9C-4E1D-9B07-87F0E3985526@kraak.info> Message-ID: <4BF1BAA9-26F5-4A37-A35D-B998F8B2D4B1@kraak.info> No one? Am 19.09.2014 um 00:57 schrieb Helge Kraak: > Hello, > > I'm aware of these two threads > > http://www.dovecot.org/pipermail/dovecot/2012-March/thread.html#134311 > http://dovecot.org/pipermail/dovecot/2012-June/thread.html#136488 > > but unfortunately I wasn't successful with my dsync mailbox migration attempt despite the information I could find there. I'm using iRedMail setup for the dovecot server. I made sure that the dovecot mailbox for the mail import had been freshly created and untouched before I tried to run the following command. > > Running this command: > > sudo doveadm -vvv -o imapc_host=xxx.de -o imapc_user=username -o imapc_password=password -o mail_fsync=never -o mail_prefetch_count=20 -o imapc_features=rfc822.size -o imapc_features=fetch-headers -o imapc_port=993 -o imapc_ssl=imaps -o imapc_ssl_ca_dir=/etc/ssl -o imapc_ssl_verify=no -o imapc_features=rfc822.size -o mailbox_list_index=no -D backup -R -u michael at domain.com imapc: > > I get the following output (I took out some lines obviously not relevant): > > doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules > doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so > doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm > doveadm(root): Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) > doveadm(root): Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_deinit (this is usually intentional, so just ignore this message) > doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so > doveadm(root): Debug: Skipping module doveadm_zlib_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_zlib_plugin.so: undefined symbol: i_stream_create_deflate (this is usually intentional, so just ignore this message) > doveadm(root): Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_rescan (this is usually intentional, so just ignore this message) > doveadm(michael at domain.com): Debug: Added userdb setting: plugin/master_user=michael at domain.com > doveadm(michael at domain.com): Debug: Added userdb setting: plugin/quota_rule=*:bytes=41943040000 > doveadm(michael at domain.com): Debug: Effective uid=2000, gid=2000, home=/var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59/ > doveadm(michael at domain.com): Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir://var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir/:INDEX=//var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir/ > doveadm(michael at domain.com): Debug: maildir++: root=//var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir, index=, control=, inbox=//var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir, alt= > doveadm(michael at domain.com): Debug: Namespace : type=shared, prefix=Shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/Shared/%u > doveadm(michael at domain.com): Debug: shared: root=/var/run/dovecot, index=, control=, inbox=, alt= > dsync(michael at domain.com): Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=imapc: > dsync(michael at domain.com): Debug: imapc: root=, index=, control=, inbox=, alt= > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Looking up IP address > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Connecting to 78.138.89.136:993 > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Starting SSL handshake > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Server capabilities: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Authenticating as username > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Server capabilities: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS QUOTA > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Authenticated successfully > dsync(michael at domain.com): Debug: Namespace : type=shared, prefix=Shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/Shared/%u > dsync(michael at domain.com): Debug: shared: root=/var/run/dovecot, index=, control=, inbox=, alt= > dsync(michael at domain.com): Debug: Namespace : Using permissions from //var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir: mode=0700 gid=-1 > dsync(michael at domain.com): Error: Can't delete mailbox INBOX: INBOX can't be deleted. > dsync(michael at domain.com): Info: Amazon: uidnext changed: 1056 != 1 > dsync(michael at domain.com): Info: INBOX: only in dest (guid=3c68c835800a07547d45000029cbe4c2)= 1 > dsync(michael at domain.com): Info: Deleted Messages: uidnext changed: 109 != 1 > dsync(michael at domain.com): Info: MBA Mails: uidnext changed: 444 != 1 > dsync(michael at domain.com): Info: Archive: highest_modseq changed: 0 != 1 > dsync(michael at domain.com): Info: Spam: uidnext changed: 3 != 1 > dsync(michael at domain.com): Info: Apple Mail To Do: highest_modseq changed: 0 != 1 > dsync(michael at domain.com): Info: Jobsuche: uidnext changed: 22436 != 1 > dsync(michael at domain.com): Info: Trash (Messages): uidnext changed: 697 != 1 > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Looking up IP address > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Connecting to IP-Adress:993 > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Starting SSL handshake > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Server capabilities: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Authenticating as username > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Server capabilities: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS QUOTA > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Authenticated successfully > dsync(michael at domain.com): Error: Trying to open a non-listed mailbox with guid=3c68c835800a07547d45000029cbe4c2 > dsync(michael at domain.com): Error: msg iteration failed: Couldn't open mailbox 3c68c835800a07547d45000029cbe4c2 > dsync(michael at domain.com): Error: Trying to open a non-listed mailbox with guid=3c68c835800a07547d45000029cbe4c2 > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Disconnected > > > > sudo dovecot -n > > # 2.1.7: /etc/dovecot/dovecot.conf > # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.6 > auth_master_user_separator = * > auth_mechanisms = PLAIN LOGIN > dict { > acl = mysql:/etc/dovecot/dovecot-share-folder.conf > quotadict = mysql:/etc/dovecot/dovecot-used-quota.conf > } > first_valid_uid = 2000 > last_valid_uid = 2000 > listen = * > log_path = /var/log/dovecot.log > mail_gid = 2000 > mail_location = maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/ > mail_plugins = quota > mail_uid = 2000 > 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 > namespace { > inbox = yes > location = > mailbox Drafts { > auto = subscribe > special_use = \Drafts > } > mailbox Junk { > auto = subscribe > special_use = \Junk > } > mailbox Sent { > auto = subscribe > special_use = \Sent > } > mailbox "Sent Messages" { > auto = no > special_use = \Sent > } > mailbox Spam { > auto = no > special_use = \Junk > } > mailbox Trash { > auto = subscribe > special_use = \Trash > } > prefix = > separator = / > type = private > } > namespace { > list = children > location = maildir:/%%Lh/Maildir/:INDEX=/%%Lh/Maildir/Shared/%%u > prefix = Shared/%%u/ > separator = / > subscriptions = yes > type = shared > } > passdb { > args = /etc/dovecot/dovecot-mysql.conf > driver = sql > } > passdb { > args = /etc/dovecot/dovecot-master-users-password > driver = passwd-file > master = yes > } > plugin { > acl = vfile > acl_shared_dict = proxy::acl > auth_socket_path = /var/run/dovecot/auth-master > quota = dict:user::proxy::quotadict > quota_rule = *:storage=1G > quota_warning = storage=85%% quota-warning 85 %u > quota_warning2 = storage=90%% quota-warning 90 %u > quota_warning3 = storage=95%% quota-warning 95 %u > sieve = /%Lh/sieve/dovecot.sieve > sieve_default = /var/vmail/sieve/dovecot.sieve > sieve_dir = /%Lh/sieve > sieve_global_dir = /var/vmail/sieve > } > protocols = pop3 imap sieve lmtp > service auth { > unix_listener /var/spool/postfix/private/dovecot-auth { > group = postfix > mode = 0666 > user = postfix > } > unix_listener auth-master { > group = vmail > mode = 0666 > user = vmail > } > unix_listener auth-userdb { > group = vmail > mode = 0660 > user = vmail > } > } > service dict { > unix_listener dict { > group = vmail > mode = 0660 > user = vmail > } > } > service imap-login { > process_limit = 500 > service_count = 1 > } > service lmtp { > executable = lmtp -L > inet_listener lmtp { > port = 24 > } > process_min_avail = 5 > unix_listener /var/spool/postfix/private/dovecot-lmtp { > group = postfix > mode = 0600 > user = postfix > } > user = vmail > } > service pop3-login { > service_count = 1 > } > service quota-warning { > executable = script /usr/local/bin/dovecot-quota-warning.sh > unix_listener quota-warning { > group = vmail > mode = 0660 > user = vmail > } > } > ssl = required > ssl_cert = ssl_key = userdb { > args = /etc/dovecot/dovecot-mysql.conf > driver = sql > } > protocol lda { > auth_socket_path = /var/run/dovecot/auth-master > lda_mailbox_autocreate = yes > log_path = /var/log/dovecot-sieve.log > mail_plugins = quota sieve > postmaster_address = root > } > protocol lmtp { > info_log_path = /var/log/dovecot-lmtp.log > lmtp_save_to_detail_mailbox = yes > mail_plugins = quota sieve > postmaster_address = postmaster > recipient_delimiter = + > } > protocol imap { > imap_client_workarounds = tb-extra-mailbox-sep > mail_plugins = quota imap_quota > } > protocol pop3 { > mail_plugins = quota > pop3_client_workarounds = outlook-no-nuls oe-ns-eoh > pop3_uidl_format = %08Xu%08Xv > } > > > Any assistance is highly appreciated. Thank you. > > Helge From david.myers.24j74 at gmail.com Mon Sep 22 11:44:29 2014 From: david.myers.24j74 at gmail.com (David Myers) Date: Mon, 22 Sep 2014 13:44:29 +0200 Subject: how to solve : Dovecot version mismatch: Master is v2.1.7, lmtp is v2.2.13 In-Reply-To: <541FFBF5.4050105@thelounge.net> References: <541FFAD3.9050303@gmail.com> <541FFBF5.4050105@thelounge.net> Message-ID: @Reindl. I copied my conf.d folder as I deleted all the dovecot files in etc/dovecot use/etc/dovecot etc ... ... When I installed the new 2.2.13 version it didn't seem to want to put the lmtp executable into the location that dovecot was expecting ? So I found the file and copied it to where it was expected to be. I then copied my old (backed up) conf.d bact to etc/dovecot/conf.d/ Performed a restart of dovecot, and got the above error. Quite simple really. But where else does dovecot store files, so as I can get all the errant files. David. On 22 Sep 2014 12:37, "Reindl Harald" wrote: > > Am 22.09.2014 um 12:32 schrieb Dave Myers: > > Hello again dovecot list ;) > > > > I've recently upgraded my dovecot version from 2.1.7 to 2.2.13. > > both versions where installed from source. > > > > I upgraded why attempting to get lmtp working. I ultimately just coped > the executable lmtp to the location that > > dovecot was expecting it to be in. but then the above error appeared. > > why do you copy files around? > > if you update a software then make it complete and not > copy random files around - installing from source would > in general be better done by build packages because > they care about obsoleted files and so on > > > However when I get the info from dovecot I get the following... > > > > $ dovecot -n > > # 2.2.13: /usr/local/etc/dovecot/dovecot.conf > > > > so there seems to be an issue somewhere. > > > > I should note that I had copied my previous /conf.d/ files and then > copied them back after the update. > > > > I guess that I have missed a switch during the build, or need to modify > a line in the config somewhere that tells > > what the version is, but that doesn't explain why the dovecot -n returns > the correct info, but the error reports > > something different. > > > > I am considering inserting the > > version_ignore=yes > > config option, but where should I insert it? > > no, you should make sure that you have only one version installed > on your system and no old craft staying around > > From h.reindl at thelounge.net Mon Sep 22 11:53:07 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Mon, 22 Sep 2014 13:53:07 +0200 Subject: how to solve : Dovecot version mismatch: Master is v2.1.7, lmtp is v2.2.13 In-Reply-To: References: <541FFAD3.9050303@gmail.com> <541FFBF5.4050105@thelounge.net> Message-ID: <54200DA3.6040103@thelounge.net> Am 22.09.2014 um 13:44 schrieb David Myers: > @Reindl. > > I copied my conf.d folder as I deleted all the dovecot files in etc/dovecot > use/etc/dovecot etc ... ... > > When I installed the new 2.2.13 version it didn't seem to want to put the > lmtp executable into the location that dovecot was expecting ? So I found > the file and copied it to where it was expected to be. and there started your mistake just test builds somewhere and realize if it comes to "so i found the file and copied it" something went terrible wrong - that's why you build usually *packages* - rpmbuild complains as long you have not listed all files in the %files section or if there are listed ones no longer built for a clean upgrade you need to replace *every* file and in doubt get rid of orphans - just build packages or use a virtual machine with a snapshot to try as long you know what lives where > I then copied my old (backed up) conf.d bact to etc/dovecot/conf.d/ > Performed a restart of dovecot, and got the above error. > > Quite simple really. But where else does dovecot store files, so as I can > get all the errant files. /usr/bin/ /usr/lib64/dovecot /usr/libexec/ /var/lib/dovecot > David. > On 22 Sep 2014 12:37, "Reindl Harald" wrote: > >> >> Am 22.09.2014 um 12:32 schrieb Dave Myers: >>> Hello again dovecot list ;) >>> >>> I've recently upgraded my dovecot version from 2.1.7 to 2.2.13. >>> both versions where installed from source. >>> >>> I upgraded why attempting to get lmtp working. I ultimately just coped >> the executable lmtp to the location that >>> dovecot was expecting it to be in. but then the above error appeared. >> >> why do you copy files around? >> >> if you update a software then make it complete and not >> copy random files around - installing from source would >> in general be better done by build packages because >> they care about obsoleted files and so on >> >>> However when I get the info from dovecot I get the following... >>> >>> $ dovecot -n >>> # 2.2.13: /usr/local/etc/dovecot/dovecot.conf >>> >>> so there seems to be an issue somewhere. >>> >>> I should note that I had copied my previous /conf.d/ files and then >> copied them back after the update. >>> >>> I guess that I have missed a switch during the build, or need to modify >> a line in the config somewhere that tells >>> what the version is, but that doesn't explain why the dovecot -n returns >> the correct info, but the error reports >>> something different. >>> >>> I am considering inserting the >>> version_ignore=yes >>> config option, but where should I insert it? >> >> no, you should make sure that you have only one version installed >> on your system and no old craft staying around -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From alanm at sics.se Mon Sep 22 13:21:20 2014 From: alanm at sics.se (Alan McGinlay) Date: Mon, 22 Sep 2014 15:21:20 +0200 Subject: dsync error: Error: Can't delete mailbox INBOX: INBOX can't be deleted. In-Reply-To: <4BF1BAA9-26F5-4A37-A35D-B998F8B2D4B1@kraak.info> References: <653A24C3-AA9C-4E1D-9B07-87F0E3985526@kraak.info> <4BF1BAA9-26F5-4A37-A35D-B998F8B2D4B1@kraak.info> Message-ID: On 2014-09-22 13:01, Helge Kraak wrote: > No one? > > > Am 19.09.2014 um 00:57 schrieb Helge Kraak: > > Hello, > > I'm aware of these two threads > > http://www.dovecot.org/pipermail/dovecot/2012-March/thread.html#134311 > http://dovecot.org/pipermail/dovecot/2012-June/thread.html#136488 > > but unfortunately I wasn't successful with my dsync mailbox migration > attempt despite the information I could find there. I'm using iRedMail > setup for the dovecot server. I made sure that the dovecot mailbox for > the mail import had been freshly created and untouched before I tried > to run the following command. > > Running this command: > > sudo doveadm -vvv -o imapc_host=xxx.de -o imapc_user=username -o > imapc_password=password -o mail_fsync=never -o mail_prefetch_count=20 > -o imapc_features=rfc822.size -o imapc_features=fetch-headers -o > imapc_port=993 -o imapc_ssl=imaps -o imapc_ssl_ca_dir=/etc/ssl -o > imapc_ssl_verify=no -o imapc_features=rfc822.size -o > mailbox_list_index=no -D backup -R -u michael at domain.com imapc: > > I get the following output (I took out some lines obviously not > relevant): > > doveadm(root): Debug: Loading modules from directory: > /usr/lib/dovecot/modules > doveadm(root): Debug: Module loaded: > /usr/lib/dovecot/modules/lib10_quota_plugin.so > doveadm(root): Debug: Loading modules from directory: > /usr/lib/dovecot/modules/doveadm > doveadm(root): Debug: Skipping module doveadm_acl_plugin, because > dlopen() failed: > /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined > symbol: acl_user_module (this is usually intentional, so just ignore > this message) > doveadm(root): Debug: Skipping module doveadm_expire_plugin, because > dlopen() failed: > /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: > undefined symbol: expire_set_deinit (this is usually intentional, so > just ignore this message) > doveadm(root): Debug: Module loaded: > /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so > doveadm(root): Debug: Skipping module doveadm_zlib_plugin, because > dlopen() failed: > /usr/lib/dovecot/modules/doveadm/lib10_doveadm_zlib_plugin.so: > undefined symbol: i_stream_create_deflate (this is usually intentional, > so just ignore this message) > doveadm(root): Debug: Skipping module doveadm_fts_plugin, because > dlopen() failed: > /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined > symbol: fts_backend_rescan (this is usually intentional, so just ignore > this message) > doveadm(michael at domain.com): Debug: Added userdb setting: > plugin/master_user=michael at domain.com > doveadm(michael at domain.com): Debug: Added userdb setting: > plugin/quota_rule=*:bytes=41943040000 > doveadm(michael at domain.com): Debug: Effective uid=2000, gid=2000, > home=/var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59/ > doveadm(michael at domain.com): Debug: Namespace : type=private, prefix=, > sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes > location=maildir://var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir/:INDEX=//var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir/ > doveadm(michael at domain.com): Debug: maildir++: > root=//var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir, > index=, control=, > inbox=//var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir, > alt= > doveadm(michael at domain.com): Debug: Namespace : type=shared, > prefix=Shared/%u/, sep=/, inbox=no, hidden=no, list=children, > subscriptions=yes > location=maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/Shared/%u > doveadm(michael at domain.com): Debug: shared: root=/var/run/dovecot, > index=, control=, inbox=, alt= > dsync(michael at domain.com): Debug: Namespace : type=private, prefix=, > sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes > location=imapc: > dsync(michael at domain.com): Debug: imapc: root=, index=, control=, > inbox=, alt= > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Looking up IP > address > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Connecting to > 78.138.89.136:993 > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Starting SSL > handshake > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Server > capabilities: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE > AUTH=PLAIN AUTH=LOGIN > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): > Authenticating as username > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Server > capabilities: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT > SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE > CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC > ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS QUOTA > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Authenticated > successfully > dsync(michael at domain.com): Debug: Namespace : type=shared, > prefix=Shared/%u/, sep=/, inbox=no, hidden=no, list=children, > subscriptions=yes > location=maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/Shared/%u > dsync(michael at domain.com): Debug: shared: root=/var/run/dovecot, > index=, control=, inbox=, alt= > dsync(michael at domain.com): Debug: Namespace : Using permissions from > //var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir: > mode=0700 gid=-1 > dsync(michael at domain.com): Error: Can't delete mailbox INBOX: INBOX > can't be deleted. > dsync(michael at domain.com): Info: Amazon: uidnext changed: 1056 != 1 > dsync(michael at domain.com): Info: INBOX: only in dest > (guid=3c68c835800a07547d45000029cbe4c2)= 1 > dsync(michael at domain.com): Info: Deleted Messages: uidnext changed: > 109 != 1 > dsync(michael at domain.com): Info: MBA Mails: uidnext changed: 444 != 1 > dsync(michael at domain.com): Info: Archive: highest_modseq changed: 0 != > 1 > dsync(michael at domain.com): Info: Spam: uidnext changed: 3 != 1 > dsync(michael at domain.com): Info: Apple Mail To Do: highest_modseq > changed: 0 != 1 > dsync(michael at domain.com): Info: Jobsuche: uidnext changed: 22436 != 1 > dsync(michael at domain.com): Info: Trash (Messages): uidnext changed: > 697 != 1 > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Looking up IP > address > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Connecting to > IP-Adress:993 > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Starting SSL > handshake > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Server > capabilities: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE > AUTH=PLAIN AUTH=LOGIN > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): > Authenticating as username > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Server > capabilities: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT > SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE > CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC > ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS QUOTA > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Authenticated > successfully > dsync(michael at domain.com): Error: Trying to open a non-listed mailbox > with guid=3c68c835800a07547d45000029cbe4c2 > dsync(michael at domain.com): Error: msg iteration failed: Couldn't open > mailbox 3c68c835800a07547d45000029cbe4c2 > dsync(michael at domain.com): Error: Trying to open a non-listed mailbox > with guid=3c68c835800a07547d45000029cbe4c2 > dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Disconnected > > > > sudo dovecot -n > > # 2.1.7: /etc/dovecot/dovecot.conf > # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.6 > auth_master_user_separator = * > auth_mechanisms = PLAIN LOGIN > dict { > acl = mysql:/etc/dovecot/dovecot-share-folder.conf > quotadict = mysql:/etc/dovecot/dovecot-used-quota.conf > } > first_valid_uid = 2000 > last_valid_uid = 2000 > listen = * > log_path = /var/log/dovecot.log > mail_gid = 2000 > mail_location = maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/ > mail_plugins = quota > mail_uid = 2000 > 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 > namespace { > inbox = yes > location = > mailbox Drafts { > auto = subscribe > special_use = \Drafts > } > mailbox Junk { > auto = subscribe > special_use = \Junk > } > mailbox Sent { > auto = subscribe > special_use = \Sent > } > mailbox "Sent Messages" { > auto = no > special_use = \Sent > } > mailbox Spam { > auto = no > special_use = \Junk > } > mailbox Trash { > auto = subscribe > special_use = \Trash > } > prefix = > separator = / > type = private > } > namespace { > list = children > location = maildir:/%%Lh/Maildir/:INDEX=/%%Lh/Maildir/Shared/%%u > prefix = Shared/%%u/ > separator = / > subscriptions = yes > type = shared > } > passdb { > args = /etc/dovecot/dovecot-mysql.conf > driver = sql > } > passdb { > args = /etc/dovecot/dovecot-master-users-password > driver = passwd-file > master = yes > } > plugin { > acl = vfile > acl_shared_dict = proxy::acl > auth_socket_path = /var/run/dovecot/auth-master > quota = dict:user::proxy::quotadict > quota_rule = *:storage=1G > quota_warning = storage=85%% quota-warning 85 %u > quota_warning2 = storage=90%% quota-warning 90 %u > quota_warning3 = storage=95%% quota-warning 95 %u > sieve = /%Lh/sieve/dovecot.sieve > sieve_default = /var/vmail/sieve/dovecot.sieve > sieve_dir = /%Lh/sieve > sieve_global_dir = /var/vmail/sieve > } > protocols = pop3 imap sieve lmtp > service auth { > unix_listener /var/spool/postfix/private/dovecot-auth { > group = postfix > mode = 0666 > user = postfix > } > unix_listener auth-master { > group = vmail > mode = 0666 > user = vmail > } > unix_listener auth-userdb { > group = vmail > mode = 0660 > user = vmail > } > } > service dict { > unix_listener dict { > group = vmail > mode = 0660 > user = vmail > } > } > service imap-login { > process_limit = 500 > service_count = 1 > } > service lmtp { > executable = lmtp -L > inet_listener lmtp { > port = 24 > } > process_min_avail = 5 > unix_listener /var/spool/postfix/private/dovecot-lmtp { > group = postfix > mode = 0600 > user = postfix > } > user = vmail > } > service pop3-login { > service_count = 1 > } > service quota-warning { > executable = script /usr/local/bin/dovecot-quota-warning.sh > unix_listener quota-warning { > group = vmail > mode = 0660 > user = vmail > } > } > ssl = required > ssl_cert = ssl_key = userdb { > args = /etc/dovecot/dovecot-mysql.conf > driver = sql > } > protocol lda { > auth_socket_path = /var/run/dovecot/auth-master > lda_mailbox_autocreate = yes > log_path = /var/log/dovecot-sieve.log > mail_plugins = quota sieve > postmaster_address = root > } > protocol lmtp { > info_log_path = /var/log/dovecot-lmtp.log > lmtp_save_to_detail_mailbox = yes > mail_plugins = quota sieve > postmaster_address = postmaster > recipient_delimiter = + > } > protocol imap { > imap_client_workarounds = tb-extra-mailbox-sep > mail_plugins = quota imap_quota > } > protocol pop3 { > mail_plugins = quota > pop3_client_workarounds = outlook-no-nuls oe-ns-eoh > pop3_uidl_format = %08Xu%08Xv > } > > > Any assistance is highly appreciated. Thank you. > > Helge I seem to remember having similar issues with dsync on that dovecot version. I am not 100% sure as it was a while ago now. Currently using very similar settings to migrate from a cyrus box on solaris 10 and dsync works well. I use Dovecot 2.2.13 from the following ubuntu ppa: https://launchpad.net/~bigmichi1/+archive/ubuntu/dovecot (the ppa owner is on this list I think) There have been a lot of fixes to dsync since 2.2.7 so it might be worth upgrading. /A From tss at iki.fi Mon Sep 22 13:33:54 2014 From: tss at iki.fi (Timo Sirainen) Date: Mon, 22 Sep 2014 16:33:54 +0300 Subject: X-DOVECOT capabilities Message-ID: Dovecot has a few hidden features currenly, which I know some webmails have been hardcoded to use. Maybe it would be nice to have these available in a bit more globally usable way and advertise some kind of X-DOVECOT capability? I don't really like the idea of having a ton of separate X-DOVECOT-* capabilities. Maybe instead just have X-DOVECOT-1 for the current functionality and when more is added X-DOVECOT-2 etc? Then describe in Dovecot wiki page what they actually contain. Thoughts? The current list of features are at least: - STATUS (X-SIZE): Sum of all RFC822.SIZEs in a mailbox. (More efficient than FETCHing them.) - STATUS (X-GUID): Show mailbox's GUID. - SEARCH X-SAVEDBEFORE, X-SAVEDON, X-SAVEDSINCE: Search with message's saved-timestamp. - FETCH X-SAVEDATE: Fetch message's saved-timestamp. - SEARCH & FETCH X-GUID: Search/fetch message GUID - SEARCH X-MAILBOX, FETCH X-MAILBOX, FETCH X-REAL-UID: With virtual mailboxes search/fetch the mail's physical mailbox name and message UID. - X-CANCEL : Stop a (long-running) command, which once in a while goes back to the main loop. For example SEARCH or FETCH. From thomas at koch.ro Mon Sep 22 14:01:13 2014 From: thomas at koch.ro (Thomas Koch) Date: Mon, 22 Sep 2014 16:01:13 +0200 Subject: [wishlist] testsuite for sieve scripts, libsievetest Message-ID: <201409221601.14051.thomas@koch.ro> Hi, I'm writing a test suite with Haskell for my sieve script. - Just to learn Haskell. But it might become something usable. The test suite calls sieve-test and parses the output. So it would of course be much simpler for me if the output of sieve-test would be easier to parse and if I'd know what output to expect. And it would be nice, if there would be an easy way to embed libsievetest as a C library. I looked into the source and the sieve-test binary does quite a bit of setup. This might be a nice hacking project for a beginner... BTW: It would be nice, if I could just 'git clone' dovecot. Thank you for dovecot! From dovecot at outputservices.com Mon Sep 22 14:57:32 2014 From: dovecot at outputservices.com (dovecot at outputservices.com) Date: Mon, 22 Sep 2014 08:57:32 -0600 (MDT) Subject: LDAP and dovecot Message-ID: <201409221457.s8MEvWEY002121@bluemoon.outputservices.com> For the record. I compiled dovecot to use the openldap libraries my openldap server uses. My email server and ldap server are on two different machines. So I just copied over my ldap libraries and placed them in the correct place and then compiled dovecot. I saw this clue in a different web page. Something about Solaris ldap libraries being bad. CPPFLAGS=-I/usr/local/openldap/include \ > LDFLAGS='-L/usr/local/openldap/lib -R/usr/local/openldap/lib' \ ./configure --prefix=/usr/local/tools/dovecot --with-ssl=openssl --with-solr --with-zlib --with-bzlib --with-ldap=yes This now allows me to authenticate with my openldap server. I am NOW able to authenticate to my ldap server. So my final configuration is: dovecot -n # 2.2.10: /usr/local/tools/dovecot/etc/dovecot/dovecot.conf # OS: SunOS 5.10 i86pc base_dir = /dovecot/var/run/dovecot log_path = /dovecot/log/log mail_location = mbox:~/posta:INBOX=/var/mail/%u:LAYOUT=maildir++:INDEX=~/posta/index:CONTROL=~/posta/control passdb { args = /dovecot/etc/dovecot/conf.d/ldap.settings driver = ldap } protocols = imap service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 } } ssl_cert = References: <541FCD7C.3050900@franceoxygene.fr> Message-ID: <1411401260.23027.132.camel@worklian> Hi, > I authenticate my test user in AD well in Dovecot. However, if I change > this user's password in AD, the old password still works for > authentication in Dovecot and the new is working too. > > Is there a time to make Dovecot don't "remember" the old password or is > it a bug ? Are you sure you aren't authenticating against something else as well, like a local unix account with the same password, for example? > > Restarting Dovecot don't solve the problem. > > Do you already heard about this ? > > Please tell me what conf files you maybe need. > > Thanks in advance > > Nicolas > > signature ----- > > > From dovecot at zp1.net Mon Sep 22 20:19:36 2014 From: dovecot at zp1.net (Henry Stack) Date: Mon, 22 Sep 2014 22:19:36 +0200 Subject: sieve redirect to foreign email gets =?UTF-8?B?4oCcUmVsYXkgYWNjZQ==?= =?UTF-8?B?c3MgZGVuaWVk4oCd?= Message-ID: <54208458.7020402@zp1.net> I have a postfix mail server with sql authentication and I want to implement sieve on it. Sieve is working relative good, rules who contain 'fileinto' are executed perfectly. The problem is the redirect to other servers. I configured a rule in Sieve to redirect any email containing "redirect" in subject to a specified foreign destination. # So practically a email coming from sender at live.de for the local user testuser at server.net should be redirected to destination at gmail.com when the subject contains "redirect" if header :contains ["subject"] ["redirect"] {redirect "destination at gmail.com"; stop;} when I test it I get the following log entry /postfix/smtpd[32114]: NOQUEUE: reject: RCPT from mail.server.net[xx.xx.xx.xx]: 554 5.7.1 : Relay access denied; from= to= proto=ESMTP helo=/ How can I tell postfix to let dovecot/sieve relay the email? can somebody give a hint? postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases append_dot_mydomain = no biff = no broken_sasl_auth_clients = yes config_directory = /etc/postfix content_filter = smtp-amavis:[127.0.0.1]:10024 default_process_limit = 15 disable_vrfy_command = yes dovecot_destination_recipient_limit = 1 home_mailbox = mail/ inet_interfaces = all mailbox_size_limit = 0 mydestination = mail.server.net, localhost myhostname = mail.server.net mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 myorigin = /etc/mailname readme_directory = no recipient_delimiter = + smtp_tls_note_starttls_offer = yes smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtp_use_tls = yes smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) smtpd_data_restrictions = reject_unauth_pipelining smtpd_helo_restrictions = reject_unknown_helo_hostname smtpd_recipient_restrictions = permit_sasl_authenticated, reject_unknown_sender_domain, reject_unknown_reverse_client_hostname, reject_unknown_recipient_domain, reject_unverified_recipient, reject_unauth_destination, reject_rbl_client zen.spamhaus.org, reject_rhsbl_helo dbl.spamhaus.org, reject_rhsbl_sender dbl.spamhaus.org, check_policy_service inet:127.0.0.1:10023 smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_authenticated_sender_login_mismatch, reject_unknown_sender_domain smtpd_tls_auth_only = no smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key smtpd_tls_loglevel = 2 smtpd_tls_received_header = yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtpd_use_tls = yes soft_bounce = no virtual_alias_domains = mysql:/etc/postfix/mysql_virtual_alias_domains.cf virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf virtual_mailbox_base = /var/vmail virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains_maps.cf virtual_mailbox_limit = 512000000 virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf virtual_transport = dovecot dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.6 auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain debug_log_path = /var/log/dovecot/dovecot.debug.log disable_plaintext_auth = no first_valid_gid = 99 first_valid_uid = 99 hostname = maxi.zp1.net info_log_path = /var/log/mail.info lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = xxx.xxx.xxx.xxx log_path = /var/log/dovecot/dovecot.log login_greeting = Dovecot ready, Sir. mail_debug = yes mail_gid = 99 mail_location = maildir:~/mail:LAYOUT=fs:INBOX=/var/vmail/%u/mail/ mail_plugins = acl mail_uid = 99 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 namespace { location = maildir:/var/mail/public prefix = Public/ separator = / subscriptions = no type = public } 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 = type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_anyone = allow acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box from subject msgid size sieve = ~/.dovecot.sieve sieve_default = /var/lib/dovecot/sieve/default.sieve sieve_dir = ~/sieve sieve_global_dir = /var/lib/dovecot/sieve/global/ sieve_max_actions = 64 sieve_user_log = ~/.dovecot.sieve.log } postmaster_address = root at server.net protocols = " imap sieve pop3" service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = postfix mode = 0666 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 } ssl_cert = References: <54208458.7020402@zp1.net> Message-ID: <54208578.3050104@thelounge.net> Am 22.09.2014 um 22:19 schrieb Henry Stack: > I have a postfix mail server with sql authentication and I want to implement sieve on it. > > Sieve is working relative good, rules who contain 'fileinto' are executed perfectly. > The problem is the redirect to other servers. > I configured a rule in Sieve to redirect any email containing "redirect" in subject to a specified foreign > destination. # > So practically a email coming from sender at live.de for the local user testuser at server.net should be redirected to > destination at gmail.com when the subject contains "redirect" > > if header :contains ["subject"] ["redirect"] {redirect > "destination at gmail.com"; stop;} > > when I test it I get the following log entry > > /postfix/smtpd[32114]: NOQUEUE: reject: RCPT from > mail.server.net[xx.xx.xx.xx]: 554 5.7.1 : > Relay access denied; from= > to= proto=ESMTP helo= * you have "mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128" * you masked the IP so likely it's not 127.0.0.1 * just use your local MTA or add the machine to "mynetworks" -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From dovecot at zp1.net Mon Sep 22 20:36:32 2014 From: dovecot at zp1.net (Henry Stack) Date: Mon, 22 Sep 2014 22:36:32 +0200 Subject: sieve redirect to foreign email gets =?UTF-8?B?4oCcUmVsYXkgYWNjZQ==?= =?UTF-8?B?c3MgZGVuaWVk4oCd?= Message-ID: <54208850.6050007@zp1.net> I have a postfix mail server with sql authentication and I want to implement sieve on it. Sieve is working relative good, rules who contain 'fileinto' are executed perfectly. The problem is the redirect to other servers. I configured a rule in Sieve to redirect any email containing "redirect" in subject to a specified foreign destination. # So practically a email coming from sender at live.de for the local user testuser at server.net should be redirected to destination at gmail.com when the subject contains "redirect" if header :contains ["subject"] ["redirect"] {redirect "destination at gmail.com"; stop;} when I test it I get the following log entry /postfix/smtpd[32114]: NOQUEUE: reject: RCPT from mail.server.net[xx.xx.xx.xx]: 554 5.7.1 : Relay access denied; from= to= proto=ESMTP helo=/ How can I tell postfix to let dovecot/sieve relay the email? can somebody give a hint? postconf -n alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases append_dot_mydomain = no biff = no broken_sasl_auth_clients = yes config_directory = /etc/postfix content_filter = smtp-amavis:[127.0.0.1]:10024 default_process_limit = 15 disable_vrfy_command = yes dovecot_destination_recipient_limit = 1 home_mailbox = mail/ inet_interfaces = all mailbox_size_limit = 0 mydestination = mail.server.net, localhost myhostname = mail.server.net mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 myorigin = /etc/mailname readme_directory = no recipient_delimiter = + smtp_tls_note_starttls_offer = yes smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache smtp_use_tls = yes smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) smtpd_data_restrictions = reject_unauth_pipelining smtpd_helo_restrictions = reject_unknown_helo_hostname smtpd_recipient_restrictions = permit_sasl_authenticated, reject_unknown_sender_domain, reject_unknown_reverse_client_hostname, reject_unknown_recipient_domain, reject_unverified_recipient, reject_unauth_destination, reject_rbl_client zen.spamhaus.org, reject_rhsbl_helo dbl.spamhaus.org, reject_rhsbl_sender dbl.spamhaus.org, check_policy_service inet:127.0.0.1:10023 smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_sender_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_authenticated_sender_login_mismatch, reject_unknown_sender_domain smtpd_tls_auth_only = no smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key smtpd_tls_loglevel = 2 smtpd_tls_received_header = yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtpd_use_tls = yes soft_bounce = no virtual_alias_domains = mysql:/etc/postfix/mysql_virtual_alias_domains.cf virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf virtual_mailbox_base = /var/vmail virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains_maps.cf virtual_mailbox_limit = 512000000 virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf virtual_transport = dovecot dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.6 auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain debug_log_path = /var/log/dovecot/dovecot.debug.log disable_plaintext_auth = no first_valid_gid = 99 first_valid_uid = 99 hostname = maxi.zp1.net info_log_path = /var/log/mail.info lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = xxx.xxx.xxx.xxx log_path = /var/log/dovecot/dovecot.log login_greeting = Dovecot ready, Sir. mail_debug = yes mail_gid = 99 mail_location = maildir:~/mail:LAYOUT=fs:INBOX=/var/vmail/%u/mail/ mail_plugins = acl mail_uid = 99 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 namespace { location = maildir:/var/mail/public prefix = Public/ separator = / subscriptions = no type = public } 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 = type = private } passdb { args = /etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_anyone = allow acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box from subject msgid size sieve = ~/.dovecot.sieve sieve_default = /var/lib/dovecot/sieve/default.sieve sieve_dir = ~/sieve sieve_global_dir = /var/lib/dovecot/sieve/global/ sieve_max_actions = 64 sieve_user_log = ~/.dovecot.sieve.log } postmaster_address = root at server.net protocols = " imap sieve pop3" service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } unix_listener auth-userdb { group = postfix mode = 0666 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 1 } ssl_cert = References: <20140919000413.GI18052@aura.veggiechinese.net> <541BD377.2080405@dovecot.fi> Message-ID: <20140922205048.GC8353@aura.veggiechinese.net> On Fri, Sep 19, 2014 at 09:55:51AM +0300, Teemu Huovila wrote: > On 09/19/2014 03:04 AM, Will Yardley wrote: > > director_doveadm_port = 8889 [....] > > doveadm_proxy_port = 8888 > In the 2.2 series you can write this as "doveadm_port", I think. Thanks for the heads up. FWIW, the system I have seems to make the translation, since I have doveadm_proxy_port configured but doveconf returns: # doveconf -i director doveadm_port doveadm_port = 8888 # doveconf -i director doveadm_proxy_port # From dovecot at zp1.net Mon Sep 22 21:38:31 2014 From: dovecot at zp1.net (Henry Stack) Date: Mon, 22 Sep 2014 23:38:31 +0200 Subject: sieve redirect to foreign email gets =?UTF-8?B?4oCcUmVsYXkgYQ==?= =?UTF-8?B?Y2Nlc3MgZGVuaWVk4oCd?= In-Reply-To: <54208850.6050007@zp1.net> References: <54208850.6050007@zp1.net> Message-ID: <542096D7.4030105@zp1.net> Am 22.09.2014 um 22:19 schrieb Henry Stack: >/ I have a postfix mail server with sql authentication and I want to implement sieve on it. />/ />/ Sieve is working relative good, rules who contain 'fileinto' are executed perfectly. />/ The problem is the redirect to other servers. />/ I configured a rule in Sieve to redirect any email containing "redirect" in subject to a specified foreign />/ destination. # />/ So practically a email coming fromsender at live.de for the local usertestuser at server.net should be redirected to />/ destination at gmail.com when the subject contains "redirect" />/ />/ if header :contains ["subject"] ["redirect"] {redirect />/ "destination at gmail.com "; stop;} />/ />/ when I test it I get the following log entry />/ />/ /postfix/smtpd[32114]: NOQUEUE: reject: RCPT from />/ mail.server.net[xx.xx.xx.xx]: 554 5.7.1 >: />/ Relay access denied; from=> />/ to=> proto=ESMTP helo= / * you have "mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128" * you masked the IP so likely it's not 127.0.0.1 * just use your local MTA or add the machine to "mynetworks" Thanks for the hint. I tried it, I added the IP to mynetworks and it is still not working, still*Relay access denied;* Henry From h.reindl at thelounge.net Mon Sep 22 21:50:21 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Mon, 22 Sep 2014 23:50:21 +0200 Subject: sieve redirect to foreign email gets =?UTF-8?B?4oCcUmVsYXkgYQ==?= =?UTF-8?B?Y2Nlc3MgZGVuaWVk4oCd?= In-Reply-To: <542096D7.4030105@zp1.net> References: <54208850.6050007@zp1.net> <542096D7.4030105@zp1.net> Message-ID: <5420999D.7020303@thelounge.net> Am 22.09.2014 um 23:38 schrieb Henry Stack: > Am 22.09.2014 um 22:19 schrieb Henry Stack: >>/ I have a postfix mail server with sql authentication and I want to implement sieve on it. > />/ > />/ Sieve is working relative good, rules who contain 'fileinto' are executed perfectly. > />/ The problem is the redirect to other servers. > />/ I configured a rule in Sieve to redirect any email containing "redirect" in subject to a specified foreign > />/ destination. # > />/ So practically a email coming from sender at live.de for the local user testuser at server.net should be redirected to > />/ destination at gmail.com when the subject contains "redirect" > />/ > />/ if header :contains ["subject"] ["redirect"] {redirect > />/ "destination at gmail.com "; stop;} > />/ > />/ when I test it I get the following log entry > />/ > />/ /postfix/smtpd[32114]: NOQUEUE: reject: RCPT from > />/ mail.server.net[xx.xx.xx.xx]: 554 5.7.1 >: > />/ Relay access denied; from=> > />/ to=> proto=ESMTP helo= > / > * you have "mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128" > * you masked the IP so likely it's not 127.0.0.1 > * just use your local MTA or add the machine to "mynetworks" > > > Thanks for the hint. > > I tried it, I added the IP to mynetworks and it is still not working, still *Relay access denied;* you need to provide more informations about your setup and if possible avoid mask IP addresses - where does the smtpd live, where is dovecot and how did you configure the relay at all what postfix version? in case of a recent version -> smtpd_relay_restrictions is configured? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From robert at gillecaluim.com Mon Sep 22 21:50:26 2014 From: robert at gillecaluim.com (Robert Watson) Date: Mon, 22 Sep 2014 14:50:26 -0700 Subject: help with samba4 settings Message-ID: I'm having a great deal of difficulty with integrating dovecot 2.0.9 with a new installation of samba4 4.1.11 and would appreciate anyones help who has this working. *Problem 1:* if dn= cn=Administrator,dc=ourhome,dc=net with dnpass = ***** ---------------I get NT_STATUS_LOGON_FAILURE but dn = "Administrator at ourhome.net" with dnpass = **** works I guess I shouldn't complain but why doesn't the first one work? *Problem 2:* can't seem to get a working set of usr_attrs/user_filter,pass_attrs/pass_filter to authenticate *dovecot-ldap.conf :* uris = ldap://localhost:389 dn = "Administrator at ourhome.net" dnpass = **** tls = no ldap_version = 3 base = cn=Users,dc=ourhome,dc=net scope = subtree user_filter = (&(objectClass=user)(sAMAccountName=%u)) user_attrs = sAMAccountName=user,userPassword=password,=mail=maildir:/var/vmail/%Ld/%n, =home=/var$ pass_filter = (&(objectClass=user)(sAMAccountName=%u)) pass_attrs = sAMAccountName=user,userPassword=password *dovecont.message log output:* *2014-09-22 14:44:50 auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth* *2014-09-22 14:44:50 auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libauthdb_ldap.so* *2014-09-22 14:44:50 auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_mysql.so* *2014-09-22 14:44:50 auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_pgsql.so* *2014-09-22 14:44:50 auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_sqlite.so* *2014-09-22 14:44:50 auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libmech_gssapi.so* *2014-09-22 14:44:50 auth: Debug: auth client connected (pid=5316)* *2014-09-22 14:45:00 auth: Debug: client in: AUTH 1 PLAIN service=imap secured lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=35148 resp=AEpvaG5Eb2UASm9obkRvZQ==* *2014-09-22 14:45:00 auth: Debug: ldap(JohnDoe,127.0.0.1): pass search: base=cn=Users,dc=ourhome,dc=net scope=subtree filter=(&(objectClass=user)(sAMAccountName=JohnDoe)) fields=sAMAccountName,userPassword* *2014-09-22 14:45:00 auth: Debug: ldap(JohnDoe,127.0.0.1): result: sAMAccountName(user)=JohnDoe* *2014-09-22 14:45:00 auth: Info: ldap(JohnDoe,127.0.0.1): No password returned (and no nopassword)* *2014-09-22 14:45:00 auth: Debug: Loading modules from directory: /usr/lib64/dovecot/auth* *2014-09-22 14:45:00 auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libauthdb_ldap.so* *2014-09-22 14:45:00 auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_mysql.so* *2014-09-22 14:45:00 auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_pgsql.so* *2014-09-22 14:45:00 auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libdriver_sqlite.so* *2014-09-22 14:45:00 auth: Debug: Module loaded: /usr/lib64/dovecot/auth/libmech_gssapi.so* *2014-09-22 14:45:00 auth: Debug: pam(JohnDoe,127.0.0.1): lookup service=dovecot* *2014-09-22 14:45:00 auth: Debug: pam(JohnDoe,127.0.0.1): #1/1 style=1 msg=Password: * *2014-09-22 14:45:02 auth: Info: pam(JohnDoe,127.0.0.1): unknown user* *2014-09-22 14:45:04 auth: Debug: client out: FAIL 1 user=JohnDoe* From stephan at rename-it.nl Mon Sep 22 22:47:23 2014 From: stephan at rename-it.nl (Stephan Bosch) Date: Tue, 23 Sep 2014 00:47:23 +0200 Subject: [wishlist] testsuite for sieve scripts, libsievetest In-Reply-To: <201409221601.14051.thomas@koch.ro> References: <201409221601.14051.thomas@koch.ro> Message-ID: <5420A6FB.2040904@rename-it.nl> On 9/22/2014 4:01 PM, Thomas Koch wrote: > Hi, > > I'm writing a test suite with Haskell for my sieve script. - Just to learn > Haskell. But it might become something usable. > > The test suite calls sieve-test and parses the output. So it would of course > be much simpler for me if the output of sieve-test would be easier to parse > and if I'd know what output to expect. Do you know there is a testsuite written in Sieve itself? Well, anyway, it is always good when the code is tested more. :) > And it would be nice, if there would be an easy way to embed libsievetest as a > C library. I looked into the source and the sieve-test binary does quite a bit > of setup. There is a libsieve-tools, but that is not installed as a shared library. I probably won't do anything like this until Dovecot itself provides proper shared libraries for the core framework. I don't see that happening any time soon. > This might be a nice hacking project for a beginner... BTW: It would be nice, > if I could just 'git clone' dovecot. You can do 'hg clone', but yes, some people prefer git. Regards, Stephan. From dmiller at amfes.com Tue Sep 23 03:28:48 2014 From: dmiller at amfes.com (Daniel Miller) Date: Mon, 22 Sep 2014 20:28:48 -0700 Subject: Empty mailboxes In-Reply-To: References: <5416725D.60209@amfes.com> Message-ID: I set auth_debug=yes and mail_debug=yes. Comparing the log output - other than the fact that the working server has additional lines for the mailboxes found they look identical. No errors. Yet there's no mail when booting the other drive. I can see the mailboxes in the file path, everything appears mounted, I don't see any rights issues. There's no errors. Yet I have no mail. What's my next step? I can post log sections - they're kind of lengthy and I don't see anything wrong in them anyway. -- Daniel On 9/14/2014 10:06 PM, Odhiambo Washington wrote: > Increase the logging level and see where the problem is. > > On 15 September 2014 08:00, Daniel Miller wrote: > >> This is driving me nuts. >> >> I need to rebuild a server - got a notification the main drive is failing, >> and it's been a year or two, so it's time. Got a new drive, fresh install >> of Ubuntu Tantric, started installing everything needed. Data stored on a >> RAID array - nicely available separate from the boot/operation drive. >> >> Did a fresh compile of Dovecot, copied over the configs from the old >> drive, mounted the RAID...and... >> >> Dovecot starts, authenticates users - and shows empty mailboxes. Nothing >> shown. Full panic - reboot on old drive. All mails present. Change back >> - no mail. >> >> Executing "doveadm user -u username" seems to give valid results. Mailbox >> location appears correct (using mdbox). >> >> I setup uid/gid the same - I thought it was a rights issue but everything >> looks correct. >> >> What can I do to try to find the stupid mistake I'm making? >> >> -- >> Daniel >> > > From skdovecot at smail.inf.fh-brs.de Tue Sep 23 06:38:55 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Tue, 23 Sep 2014 08:38:55 +0200 (CEST) Subject: Empty mailboxes In-Reply-To: References: <5416725D.60209@amfes.com> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 22 Sep 2014, Daniel Miller wrote: > I set auth_debug=yes and mail_debug=yes. Comparing the log output - other > than the fact that the working server has additional lines for the mailboxes > found they look identical. No errors. Yet there's no mail when booting the > other drive. > > I can see the mailboxes in the file path, everything appears mounted, I don't > see any rights issues. There's no errors. Yet I have no mail. post the log lines you get, when you manually login via telnet, e.g.: telnet server 143 1 login user "password" 2 select INBOX 3 logout and the output of the SELECT command, doveconf -n and the output of: cd "to user's mailbox" pwd ls -al - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBVCEVgHz1H7kL/d9rAQIrnQgAtISTfUmMkJ3aQ+c17kyf1M/9FPFiKZA8 Y6Pio/eSN9XGQglPGykbHwOCKqsUiQgRKoM0rV2sKvifZ/Z3zx7C2kGG6vRwGa3H 7Id0eGKBwSOXaGPV6zaPN7K0Dx3n5WXc6fq6S1+vJrXGEMLmbY7icr8COfowNCn9 dX/vhn/GDC8RiWisu+uQb3IYTQ+WowWUwylIwVlwvaMOZk7eIrcztXuU9BCtO/E3 bjEITwe1utySfUNB0gcg8HM75yw/AxfcLLmzLm9lvECjJGTm5lqY/h7KkeBNH8iS Yv/ROmIL8fnRKNSshuefsmihO+dhK3sEn4iuSo5QyOW8QPJwxSOMTg== =RXeb -----END PGP SIGNATURE----- From alanm at sics.se Tue Sep 23 07:31:16 2014 From: alanm at sics.se (Alan McGinlay) Date: Tue, 23 Sep 2014 09:31:16 +0200 Subject: dsync annoyances Message-ID: <719de21464f0aa9eac11d75714fd4b58@sics.se> Hi! Every time I run dsync for a user against an old Cyrus server, the users mailbox in Dovecot increases by several hundred MB, these are not new emails. So the first dsync run gets the whole mailbox and subsequent runs get a bunch of duplicates or what? doveadm purge clears them all out but why is dsync behaving like this? I didn't happen in previous versions (2.2.13) From dovecot at zp1.net Tue Sep 23 08:22:35 2014 From: dovecot at zp1.net (Henry Stack) Date: Tue, 23 Sep 2014 10:22:35 +0200 Subject: sieve redirect to foreign email gets =?UTF-8?B?4oCcUmVsYXkgYQ==?= =?UTF-8?B?Y2Nlc3MgZGVuaWVk4oCd?= In-Reply-To: <5420999D.7020303@thelounge.net> References: <54208850.6050007@zp1.net> <542096D7.4030105@zp1.net> <5420999D.7020303@thelounge.net> Message-ID: <54212DCB.6060405@zp1.net> On 22-09-2014 23:50, Reindl Harald wrote: > [...] you need to provide more informations about your setup and if > possible avoid mask IP addresses - where does the smtpd live, where > is dovecot and how did you configure the relay at all what postfix > version? in case of a recent version -> smtpd_relay_restrictions is > configured? ok here comes the data the sieve rule is simple if header :contains ["subject"] ["redirect"] {redirect "henry at gmail.com"; stop;} first of all the main issue is the sieve "redirect" to a email address on a foreign server. In our case gmail. (sieve is a part of dovecot, and I found no possibility to make sieve more verbose.) I can make postfix verbose but it just say that relay is not permitted. to test sieve and the rule I send a email from henry at live.de (Hotmail) to my account on the server. henry at example.net and expect it to be redirected to henry at gmail.com The only interesting line in the log-file is still NOQUEUE: reject: RCPT from mail.example.net[62.78.xxx.xxx]: 554 5.7.1 : Relay access denied; from= to= proto=ESMTP helo= it say that sieve is trying to make a email FROM henry at live.de TO henry at gmail.com and send it via mail.example.net. *this is crazzy.* I think that this is the reason why I get the relay not permitted. afaik it should envelope the email using henry at example.net Even I transform my own server in a open relay and send the email like sieve want it to be redirected it will be rejected by the destination server because my server is no authority for gmail. Does somebody know how I can teach sieve to send as envelope ? From alanm at sics.se Tue Sep 23 09:49:51 2014 From: alanm at sics.se (Alan McGinlay) Date: Tue, 23 Sep 2014 11:49:51 +0200 Subject: sieve redirect to foreign email gets =?UTF-8?Q?=E2=80=9CRelay?= =?UTF-8?Q?=20access=20denied=E2=80=9D?= In-Reply-To: <54212DCB.6060405@zp1.net> References: <54208850.6050007@zp1.net> <542096D7.4030105@zp1.net> <5420999D.7020303@thelounge.net> <54212DCB.6060405@zp1.net> Message-ID: On 2014-09-23 10:22, Henry Stack wrote: > On 22-09-2014 23:50, Reindl Harald wrote: > [...] you need to provide more informations about your setup and if > possible avoid mask IP addresses - where does the smtpd live, where > is dovecot and how did you configure the relay at all what postfix > version? in case of a recent version -> smtpd_relay_restrictions is > configured? > > ok here comes the data > the sieve rule is simple > > if header :contains ["subject"] ["redirect"] {redirect > "henry at gmail.com"; stop;} > > first of all the main issue is the sieve "redirect" to a email > address on a foreign server. In our case gmail. > (sieve is a part of dovecot, and I found no possibility to make sieve > more verbose.) > I can make postfix verbose but it just say that relay is not > permitted. > > to test sieve and the rule I send a email from henry at live.de > (Hotmail) to my account on the server. henry at example.net and expect it > to be redirected to henry at gmail.com > > The only interesting line in the log-file is still > NOQUEUE: reject: RCPT from mail.example.net[62.78.xxx.xxx]: 554 5.7.1 > : Relay access denied; from= > to= proto=ESMTP helo= > > it say that sieve is trying to make a email FROM henry at live.de TO > henry at gmail.com and send it via mail.example.net. > *this is crazzy.* > I think that this is the reason why I get the relay not permitted. > afaik it should envelope the email using henry at example.net > > Even I transform my own server in a open relay and send the email > like sieve want it to be redirected it will be rejected by the > destination server because my server is no authority for gmail. > > Does somebody know how I can teach sieve to send as envelope ? This looks like a postfix configuration issue, nothing to do with dovecot or sieve. You should really ask on a postfix list but what does your postfix main.cf look like? From bind at enas.net Tue Sep 23 10:08:42 2014 From: bind at enas.net (Urban Loesch) Date: Tue, 23 Sep 2014 12:08:42 +0200 Subject: sieve redirect to foreign email gets =?UTF-8?B?4oCcUmVsYXkgYQ==?= =?UTF-8?B?Y2Nlc3MgZGVuaWVk4oCd?= In-Reply-To: <54208850.6050007@zp1.net> References: <54208850.6050007@zp1.net> Message-ID: <542146AA.2040905@enas.net> Hi, I'm not shure, but could it be that you are missing "permit_mynetworks" in "smtpd_recipient_restrictions"? Regards Urban Am 22.09.2014 22:36, schrieb Henry Stack: > I have a postfix mail server with sql authentication and I want to implement sieve on it. > > Sieve is working relative good, rules who contain 'fileinto' are executed perfectly. > The problem is the redirect to other servers. > I configured a rule in Sieve to redirect any email containing "redirect" in subject to a specified foreign destination. # > So practically a email coming from sender at live.de for the local user testuser at server.net should be redirected to destination at gmail.com when the > subject contains "redirect" > > if header :contains ["subject"] ["redirect"] {redirect > "destination at gmail.com"; stop;} > > when I test it I get the following log entry > > /postfix/smtpd[32114]: NOQUEUE: reject: RCPT from > mail.server.net[xx.xx.xx.xx]: 554 5.7.1 : > Relay access denied; from= > to= proto=ESMTP helo=/ > > How can I tell postfix to let dovecot/sieve relay the email? > > can somebody give a hint? > > postconf -n > > alias_database = hash:/etc/aliases > alias_maps = hash:/etc/aliases > append_dot_mydomain = no > biff = no > broken_sasl_auth_clients = yes > config_directory = /etc/postfix > content_filter = smtp-amavis:[127.0.0.1]:10024 > default_process_limit = 15 > disable_vrfy_command = yes > dovecot_destination_recipient_limit = 1 > home_mailbox = mail/ > inet_interfaces = all > mailbox_size_limit = 0 > mydestination = mail.server.net, localhost > myhostname = mail.server.net > mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 > myorigin = /etc/mailname > readme_directory = no > recipient_delimiter = + > smtp_tls_note_starttls_offer = yes > smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache > smtp_use_tls = yes > smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU) > smtpd_data_restrictions = reject_unauth_pipelining > smtpd_helo_restrictions = reject_unknown_helo_hostname > smtpd_recipient_restrictions = permit_sasl_authenticated, > reject_unknown_sender_domain, > reject_unknown_reverse_client_hostname, > reject_unknown_recipient_domain, reject_unverified_recipient, > reject_unauth_destination, reject_rbl_client zen.spamhaus.org, > reject_rhsbl_helo dbl.spamhaus.org, reject_rhsbl_sender > dbl.spamhaus.org, check_policy_service inet:127.0.0.1:10023 > smtpd_sasl_auth_enable = yes > smtpd_sasl_authenticated_header = yes > smtpd_sasl_local_domain = $myhostname > smtpd_sasl_path = private/auth > smtpd_sasl_security_options = noanonymous > smtpd_sasl_type = dovecot > smtpd_sender_restrictions = permit_sasl_authenticated, > permit_mynetworks, reject_authenticated_sender_login_mismatch, > reject_unknown_sender_domain > smtpd_tls_auth_only = no > smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem > smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key > smtpd_tls_loglevel = 2 > smtpd_tls_received_header = yes > smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache > smtpd_use_tls = yes > soft_bounce = no > virtual_alias_domains = > mysql:/etc/postfix/mysql_virtual_alias_domains.cf > virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf > virtual_mailbox_base = /var/vmail > virtual_mailbox_domains = > mysql:/etc/postfix/mysql_virtual_domains_maps.cf > virtual_mailbox_limit = 512000000 > virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf > virtual_transport = dovecot > > dovecot -n > > # 2.1.7: /etc/dovecot/dovecot.conf > # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.6 > auth_debug_passwords = yes > auth_mechanisms = plain login > auth_verbose = yes > auth_verbose_passwords = plain > debug_log_path = /var/log/dovecot/dovecot.debug.log > disable_plaintext_auth = no > first_valid_gid = 99 > first_valid_uid = 99 > hostname = maxi.zp1.net > info_log_path = /var/log/mail.info > lda_mailbox_autocreate = yes > lda_mailbox_autosubscribe = yes > listen = xxx.xxx.xxx.xxx > log_path = /var/log/dovecot/dovecot.log > login_greeting = Dovecot ready, Sir. > mail_debug = yes > mail_gid = 99 > mail_location = maildir:~/mail:LAYOUT=fs:INBOX=/var/vmail/%u/mail/ > mail_plugins = acl > mail_uid = 99 > 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 > namespace { > location = maildir:/var/mail/public > prefix = Public/ > separator = / > subscriptions = no > type = public > } > 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 = > type = private > } > passdb { > args = /etc/dovecot/dovecot-sql.conf.ext > driver = sql > } > plugin { > acl = vfile > acl_anyone = allow > acl_shared_dict = file:/var/lib/dovecot/shared-mailboxes > mail_log_events = delete undelete expunge copy mailbox_delete > mailbox_rename > mail_log_fields = uid box from subject msgid size > sieve = ~/.dovecot.sieve > sieve_default = /var/lib/dovecot/sieve/default.sieve > sieve_dir = ~/sieve > sieve_global_dir = /var/lib/dovecot/sieve/global/ > sieve_max_actions = 64 > sieve_user_log = ~/.dovecot.sieve.log > } > postmaster_address = root at server.net > protocols = " imap sieve pop3" > service auth { > unix_listener /var/spool/postfix/private/auth { > mode = 0666 > } > unix_listener auth-userdb { > group = postfix > mode = 0666 > user = postfix > } > } > service managesieve-login { > inet_listener sieve { > port = 4190 > } > service_count = 1 > } > ssl_cert = ssl_key = submission_host = smtp.server.net > userdb { > args = uid=vmail gid=vmail home=/var/vmail/%u > driver = static > } > verbose_proctitle = yes > protocol lda { > mail_plugins = acl sieve > } > protocol imap { > mail_plugins = acl autocreate acl imap_acl > } > protocol sieve { > mail_max_userip_connections = 10 > } > From h.reindl at thelounge.net Tue Sep 23 10:31:46 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Tue, 23 Sep 2014 12:31:46 +0200 Subject: sieve redirect to foreign email gets =?UTF-8?B?4oCcUmVsYXkgYQ==?= =?UTF-8?B?Y2Nlc3MgZGVuaWVk4oCd?= In-Reply-To: <542146AA.2040905@enas.net> References: <54208850.6050007@zp1.net> <542146AA.2040905@enas.net> Message-ID: <54214C12.3040701@thelounge.net> Am 23.09.2014 um 12:08 schrieb Urban Loesch: > I'm not shure, but could it be that you are missing "permit_mynetworks" in "smtpd_recipient_restrictions"? likely * smtpd_sender_restrictions * smtpd_data_restrictions * smtpd_helo_restrictions * smtpd_recipient_restrictions it is in general a bad idea to use all 4 of them how do you know the exact order http://www.postfix.org/postconf.5.html#smtpd_delay_reject default on, so you can put anything in "smtpd_recipient_restrictions" and avoid unpredictable results - below an example how all of them live in "smtpd_recipient_restrictions" the point is postfix is working from top to bottom you only need to take care to skip restrictions applied to inbound mail but not in the local network and for authenticated users while some rules are on top and are explicitly for submission users no reason for that: smtpd_data_restrictions = reject_unauth_pipelining smtpd_recipient_restrictions = permit_mynetworks reject_non_fqdn_recipient reject_non_fqdn_sender reject_unlisted_sender reject_authenticated_sender_login_mismatch permit_sasl_authenticated reject_non_fqdn_helo_hostname reject_invalid_helo_hostname reject_unauth_destination reject_unauth_pipelining reject_unknown_sender_domain reject_unknown_recipient_domain check_recipient_access proxy:hash:/etc/postfix/blacklist_rcpt.cf check_recipient_access proxy:hash:/etc/postfix/whitelist_rcpt.cf check_sender_access proxy:hash:/etc/postfix/whitelist_sender.cf check_sender_access proxy:hash:/etc/postfix/blacklist_sender.cf check_sender_access proxy:hash:/etc/postfix/spoofing_protection.cf check_helo_access proxy:regexp:/etc/postfix/blacklist_helo.cf check_reverse_client_hostname_access proxy:regexp:/etc/postfix/blacklist_generic_ptr.cf check_policy_service unix:private/spf-policy check_recipient_access proxy:hash:/etc/postfix/skip_rcpt_verification.cf reject_unverified_recipient -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From ve at vetienne.net Tue Sep 23 11:37:17 2014 From: ve at vetienne.net (Vincent ETIENNE) Date: Tue, 23 Sep 2014 13:37:17 +0200 Subject: help with samba4 settings In-Reply-To: References: Message-ID: <54215B6D.80301@vetienne.net> Hi robert, Have done something a little different to integrate AD users into dovecot. Here i use sssd to integrate AD users into pam and use standard dovecot pam identification. Maybe not the solution you want ( i.e it provide full user access ... if you want only mail ) But sssd is simple to setup and easy to integrate into nsswitch / pam Moreover sssd provided you with failover ( in case your ad server is not the same as your mail server ) Maybe it could be an idea .. Vincent ETIENNE Le 22/09/2014 23:50, Robert Watson a ?crit : > I'm having a great deal of difficulty with integrating dovecot 2.0.9 with a > new installation of samba4 4.1.11 and would appreciate anyones help who has > this working. > > *Problem 1:* > if dn= cn=Administrator,dc=ourhome,dc=net with dnpass = ***** > ---------------I get NT_STATUS_LOGON_FAILURE > but dn = "Administrator at ourhome.net" with dnpass = **** works > I guess I shouldn't complain but why doesn't the first one work? > > *Problem 2:* > can't seem to get a working set of > usr_attrs/user_filter,pass_attrs/pass_filter to authenticate > > *dovecot-ldap.conf :* > uris = ldap://localhost:389 > dn = "Administrator at ourhome.net" > dnpass = **** > tls = no > ldap_version = 3 > base = cn=Users,dc=ourhome,dc=net > scope = subtree > user_filter = (&(objectClass=user)(sAMAccountName=%u)) > user_attrs = > sAMAccountName=user,userPassword=password,=mail=maildir:/var/vmail/%Ld/%n, > =home=/var$ > pass_filter = (&(objectClass=user)(sAMAccountName=%u)) > pass_attrs = sAMAccountName=user,userPassword=password > > *dovecont.message log output:* > *2014-09-22 14:44:50 auth: Debug: Loading modules from directory: > /usr/lib64/dovecot/auth* > *2014-09-22 14:44:50 auth: Debug: Module loaded: > /usr/lib64/dovecot/auth/libauthdb_ldap.so* > *2014-09-22 14:44:50 auth: Debug: Module loaded: > /usr/lib64/dovecot/auth/libdriver_mysql.so* > *2014-09-22 14:44:50 auth: Debug: Module loaded: > /usr/lib64/dovecot/auth/libdriver_pgsql.so* > *2014-09-22 14:44:50 auth: Debug: Module loaded: > /usr/lib64/dovecot/auth/libdriver_sqlite.so* > *2014-09-22 14:44:50 auth: Debug: Module loaded: > /usr/lib64/dovecot/auth/libmech_gssapi.so* > *2014-09-22 14:44:50 auth: Debug: auth client connected (pid=5316)* > *2014-09-22 14:45:00 auth: Debug: client in: AUTH 1 PLAIN service=imap > secured lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=35148 > resp=AEpvaG5Eb2UASm9obkRvZQ==* > *2014-09-22 14:45:00 auth: Debug: ldap(JohnDoe,127.0.0.1): pass search: > base=cn=Users,dc=ourhome,dc=net scope=subtree > filter=(&(objectClass=user)(sAMAccountName=JohnDoe)) > fields=sAMAccountName,userPassword* > *2014-09-22 14:45:00 auth: Debug: ldap(JohnDoe,127.0.0.1): result: > sAMAccountName(user)=JohnDoe* > *2014-09-22 14:45:00 auth: Info: ldap(JohnDoe,127.0.0.1): No password > returned (and no nopassword)* > *2014-09-22 14:45:00 auth: Debug: Loading modules from directory: > /usr/lib64/dovecot/auth* > *2014-09-22 14:45:00 auth: Debug: Module loaded: > /usr/lib64/dovecot/auth/libauthdb_ldap.so* > *2014-09-22 14:45:00 auth: Debug: Module loaded: > /usr/lib64/dovecot/auth/libdriver_mysql.so* > *2014-09-22 14:45:00 auth: Debug: Module loaded: > /usr/lib64/dovecot/auth/libdriver_pgsql.so* > *2014-09-22 14:45:00 auth: Debug: Module loaded: > /usr/lib64/dovecot/auth/libdriver_sqlite.so* > *2014-09-22 14:45:00 auth: Debug: Module loaded: > /usr/lib64/dovecot/auth/libmech_gssapi.so* > *2014-09-22 14:45:00 auth: Debug: pam(JohnDoe,127.0.0.1): lookup > service=dovecot* > *2014-09-22 14:45:00 auth: Debug: pam(JohnDoe,127.0.0.1): #1/1 style=1 > msg=Password: * > *2014-09-22 14:45:02 auth: Info: pam(JohnDoe,127.0.0.1): unknown user* > *2014-09-22 14:45:04 auth: Debug: client out: FAIL 1 user=JohnDoe* > From skdovecot at smail.inf.fh-brs.de Tue Sep 23 12:07:39 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Tue, 23 Sep 2014 14:07:39 +0200 (CEST) Subject: =?UTF-8?Q?Re=3A_sieve_redirect_to_foreign_email_gets_=E2=80=9CRelay_access_denied=E2=80=9D?= In-Reply-To: <54212DCB.6060405@zp1.net> References: <54208850.6050007@zp1.net> <542096D7.4030105@zp1.net> <5420999D.7020303@thelounge.net> <54212DCB.6060405@zp1.net> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 23 Sep 2014, Henry Stack wrote: > On 22-09-2014 23:50, Reindl Harald wrote: >> [...] you need to provide more informations about your setup and if >> possible avoid mask IP addresses - where does the smtpd live, where >> is dovecot and how did you configure the relay at all what postfix >> version? in case of a recent version -> smtpd_relay_restrictions is >> configured? > > ok here comes the data > the sieve rule is simple > > if header :contains ["subject"] ["redirect"] {redirect "henry at gmail.com"; > stop;} > > first of all the main issue is the sieve "redirect" to a email address on a > foreign server. In our case gmail. > (sieve is a part of dovecot, and I found no possibility to make sieve more > verbose.) > I can make postfix verbose but it just say that relay is not permitted. > > to test sieve and the rule I send a email from henry at live.de (Hotmail) to my > account on the server. henry at example.net and expect it to be redirected to > henry at gmail.com > > The only interesting line in the log-file is still > NOQUEUE: reject: RCPT from mail.example.net[62.78.xxx.xxx]: 554 5.7.1 > : Relay access denied; from= > to= proto=ESMTP helo= > > it say that sieve is trying to make a email FROM henry at live.de TO > henry at gmail.com and send it via mail.example.net. > *this is crazzy.* > I think that this is the reason why I get the relay not permitted. > afaik it should envelope the email using henry at example.net > > Even I transform my own server in a open relay and send the email like sieve > want it to be redirected it will be rejected by the destination server > because my server is no authority for gmail. 1) There is a difference between "resent" and "redirect" (which is also known as "forward" or sometimes "bounce"). You want a redirect, Sieve forwards. Both ways have pros and cons. 2) You do not change your server into an open relay, if you permit just this host to drop messages there, depending what other services the Sieve host hosts. I don't know for certain, if Pigeonhole implements client SMTP AUTH - that would certainly help, but I found no setting for it. On the other hand, you can use a sendmail script instead of SMTP to circumvent that limitation. See: # Binary to use for sending mails. #sendmail_path = /usr/sbin/sendmail # If non-empty, send mails via this SMTP host[:port] instead of sendmail. submission_host = localhost > Does somebody know how I can teach sieve to send as envelope ? If you resent messages, bounces and other notifications (vacation) return to the resender not the original sender. What this means in your situation, I don't know. Stuff like: https://en.wikipedia.org/wiki/Sender_Rewriting_Scheme shall overcome this problem, but then each envelope sender is unique because of the timestamp. What this means for your recipients, I don't know as well. You can teach Sieve doing so by patching the source code and submit a patch Stephan might consider to include into the source. - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBVCFijHz1H7kL/d9rAQJvUQf+L1iIZj/VuKtfPVB3MiAeQn0s+P5yHFnq eq+m4c393KNLeCyHiYYEjnZ/tadm6dU22LPuaZD+2ClzorMC4AJq3zLBN7MDLQZ1 aUBOYcyvwMsA4500zMRBldx2++P2QoZevH/MbIS3MCBEq5YbSOYbIbIz/8U36l6O cwhNhC6XLb9329Slw4ru9MUn1j6VWcpXvq2E6OeEUiNM/crvZ5a12reQ3ksIskA9 YoAsy8rCYhXHVse0p5rlt1MVg4YrcgP9WH8zziqSd4iB50vSjdku7OMFTxT+J0uJ tnNMF8vFX+DznE5vToz5dPd5NbXBMm4QR1e9ILRgV371YtokPWQQOA== =tKmq -----END PGP SIGNATURE----- From p.heinlein at heinlein-support.de Tue Sep 23 12:31:05 2014 From: p.heinlein at heinlein-support.de (Peer Heinlein) Date: Tue, 23 Sep 2014 14:31:05 +0200 Subject: doveadm penalty: who is 0.0.0.0? Message-ID: <54216809.8060709@heinlein-support.de> Using doveadm penalty I just noticed a penalty for 0.0.0.0. Is this Postfix querying the auth-socket for his SASL-requests? I tried adding 0.0.0.0 to login_trusted_networks, but that doesn't help. Peer -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. ?35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Gesch?ftsf?hrer: Peer Heinlein -- Sitz: Berlin -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 490 bytes Desc: OpenPGP digital signature URL: From phil at dovecot.fi Tue Sep 23 13:25:04 2014 From: phil at dovecot.fi (Phil Carmody) Date: Tue, 23 Sep 2014 16:25:04 +0300 Subject: [wishlist] testsuite for sieve scripts, libsievetest Message-ID: <20140923132504.GA29928@phil.dovecot.net> > BTW: It would be nice, if I could just 'git clone' dovecot. Hi, Thomas, I happily use Felipe Contreras' excellent git-hg bridge, as I am far happier in a GIT environment than an Hg one: https://github.com/felipec/git/wiki/git-remote-hg The workflow couldn't be much easier, in particular if you set up a few aliases for the common sequences of tasks. $ hg clone http://hg.dovecot.org/dovecot-2.2 $ git clone "hg::/home/phil/dovecot-2.2" dovecot-2.2-git $ cd dovecot-2.2-git $ git checkout -b hacking $ # work... $ cd ../dovecot-2.2 $ hg pull -u $ cd ../dovecot-2.2-git $ git checkout master $ git rebase master hacking $ # more work... (OK, my workflow includes pushing too ;-) ) Hope that helps. Cheers, Phil From stefan at arentz.ca Tue Sep 23 13:48:57 2014 From: stefan at arentz.ca (Stefan Arentz) Date: Tue, 23 Sep 2014 09:48:57 -0400 Subject: Announce: Plugin for iOS Push Email support In-Reply-To: References: <8408BC1C-68B6-40C3-B1B0-679E179C8861@arentz.ca> Message-ID: <42FE5D04-0804-41B1-97D1-FC917C4F4A38@arentz.ca> > On Sep 15, 2014, at 8:58 AM, Timo Sirainen wrote: > > On 05 Sep 2014, at 04:35, Stefan Arentz wrote: > >> I?ve been hacking on a personal side project to support native iOS Push Email in Dovecot. This is specifically for people who are migrating their mail away from OS X Server while keeping their existing Push Email functionality. > > Nice. I had been planning to look into this as well, but never had much time. Some comments from a quick look: > > - xaps_str_append_quoted() doesn't quote CR/LF/TABs. Of course those shouldn't normally exist in any of the fields, but older Dovecot versions would have allowed creating folder names with them. Using the str_append_tabescaped() would escape them as well, although then you'd have to implement the unescaping also with Python. > > - ideally the communication between Dovecot and xaps-daemon would be done asynchronously, but as a quick change you could also use i_stream_create_fd() + i_stream_read_next_line() instead of the strtok_r call. Oh and in internal Dovecot protocols it has always used LF, not CRLF, which would also make it a bit easier to handle. > > - in xaps_notify() especially async IO would be much better to avoid latency. It's also easier to do than in init, since it wouldn't really even need to wait for the response. Even without async IO does it really even need to read the answer from the server? > > - also to avoid bursts of notifications in some situations, you could use timeout_add(NOTIFY_DELAY_MSECS, ...) and have the timeout function send the notification. The delay being for example 0,5 seconds or maybe configurable. Hi Timo, Thank you for these hints. I appreciate your input. This all sounds pretty good and I will try to make these changes soon and push out a new release. For people who are interested in trying our this project, I have made considerable improvements to the daemon side of things. It is now a proper Twisted application that you can start using twistd, so that it goes in the background, writes a pid file, etc. See https://github.com/st3fan/dovecot-xaps-daemon/blob/master/README.md#installing-and-running-the-daemon S. From patrickdk at patrickdk.com Tue Sep 23 14:47:34 2014 From: patrickdk at patrickdk.com (Patrick Domack) Date: Tue, 23 Sep 2014 10:47:34 -0400 Subject: Announce: Plugin for iOS Push Email support In-Reply-To: <42FE5D04-0804-41B1-97D1-FC917C4F4A38@arentz.ca> References: <8408BC1C-68B6-40C3-B1B0-679E179C8861@arentz.ca> <42FE5D04-0804-41B1-97D1-FC917C4F4A38@arentz.ca> Message-ID: <20140923104734.Horde.XC_JyWbG-FR0RXWeTOxtlA3@mail.patrickdk.com> What would happen if say, the dovegot xaps plugin is installed and the daemon crashed? Would peoples iphones just wait for the push notification? get email every like 30/60min? or would it just use imap idle instead? Just wondering about sideeffects :) Quoting Stefan Arentz : >> On Sep 15, 2014, at 8:58 AM, Timo Sirainen wrote: >> >> On 05 Sep 2014, at 04:35, Stefan Arentz wrote: >> >>> I?ve been hacking on a personal side project to support native iOS >>> Push Email in Dovecot. This is specifically for people who are >>> migrating their mail away from OS X Server while keeping their >>> existing Push Email functionality. >> >> Nice. I had been planning to look into this as well, but never had >> much time. Some comments from a quick look: >> >> - xaps_str_append_quoted() doesn't quote CR/LF/TABs. Of course >> those shouldn't normally exist in any of the fields, but older >> Dovecot versions would have allowed creating folder names with >> them. Using the str_append_tabescaped() would escape them as well, >> although then you'd have to implement the unescaping also with >> Python. >> >> - ideally the communication between Dovecot and xaps-daemon would >> be done asynchronously, but as a quick change you could also use >> i_stream_create_fd() + i_stream_read_next_line() instead of the >> strtok_r call. Oh and in internal Dovecot protocols it has always >> used LF, not CRLF, which would also make it a bit easier to handle. >> >> - in xaps_notify() especially async IO would be much better to >> avoid latency. It's also easier to do than in init, since it >> wouldn't really even need to wait for the response. Even without >> async IO does it really even need to read the answer from the server? >> >> - also to avoid bursts of notifications in some situations, you >> could use timeout_add(NOTIFY_DELAY_MSECS, ...) and have the timeout >> function send the notification. The delay being for example 0,5 >> seconds or maybe configurable. > > Hi Timo, > > Thank you for these hints. I appreciate your input. This all sounds > pretty good and I will try to make these changes soon and push out a > new release. > > For people who are interested in trying our this project, I have > made considerable improvements to the daemon side of things. It is > now a proper Twisted application that you can start using twistd, so > that it goes in the background, writes a pid file, etc. > > See > https://github.com/st3fan/dovecot-xaps-daemon/blob/master/README.md#installing-and-running-the-daemon > > S. From tss at iki.fi Tue Sep 23 15:25:42 2014 From: tss at iki.fi (Timo Sirainen) Date: Tue, 23 Sep 2014 18:25:42 +0300 Subject: quota recalc problem for big maildirs In-Reply-To: <541BF1D2.9010807@netart.pl> References: <541BF1D2.9010807@netart.pl> Message-ID: On 19 Sep 2014, at 12:05, Dawid Stawiarski - nazwa.pl wrote: > we use dovecot 2.2.13, and we've lately started using maildir quota (previously fs quota was used, right now it's "quota = maildir:User quota" changed from "quota = fs:User quota:user:inode_per_mail"). > > When the change was applied we didn't manually forced generating maildirsize files. So, when the first deliver happens (or the file grows larger then 5KB) it starts quota recalc. However for users with big maildirs, receiving email every couple of seconds, there are tens of delivery processes each doing its own recalc (as they open file for APPEND and there's no locking). What's even worse, after all the stats and getdents (it takes a lot of IO for 60GB account with 2M emails), deliver makes stat on 'new' dir and detects changes after which it unlinks freshly created maildirsize. So possibly this will never be finished as every process drops its own work. > > The same thing happened when we checked the native dovecot LMTP server (every connection has its own forked process - each running independently of the others). > > Is it a known unwanted "feature" of maildir quota (and we should use dict quota instead) or a bug that will be fixed? It's a feature that won't be changed. The stat()s are especially bad if you see them - they wouldn't happen if your Maildir filenames contain the ,S=size part. Switch to dict file, which won't be recalculated unless you manually do it. From tss at iki.fi Tue Sep 23 15:50:38 2014 From: tss at iki.fi (Timo Sirainen) Date: Tue, 23 Sep 2014 18:50:38 +0300 Subject: Dict protocol RFC In-Reply-To: <540F197A.9020301@posteo.de> References: <540F197A.9020301@posteo.de> Message-ID: On 09 Sep 2014, at 18:15, Philipp Bruell wrote: > does someone know if there is a RFC protocol description of the dict > protocol that dovecot is using for auth/quota/... requests? Haven't > found anything on google yet. Not really, other than the source code. http://wiki2.dovecot.org/AuthDatabase/Dict has also an example server script. From philippbruell at posteo.de Tue Sep 23 15:55:20 2014 From: philippbruell at posteo.de (Philipp Bruell) Date: Tue, 23 Sep 2014 17:55:20 +0200 Subject: Dict protocol RFC In-Reply-To: References: <540F197A.9020301@posteo.de> Message-ID: <542197E8.8000705@posteo.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Thanks for the feedback, Meanwhile, I've used the script to write a simple dict-server. Best regards, Philipp Am 23.09.2014 um 17:50 schrieb Timo Sirainen: > On 09 Sep 2014, at 18:15, Philipp Bruell > wrote: > >> does someone know if there is a RFC protocol description of the >> dict protocol that dovecot is using for auth/quota/... requests? >> Haven't found anything on google yet. > > Not really, other than the source code. > http://wiki2.dovecot.org/AuthDatabase/Dict has also an example > server script. > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJUIZfoAAoJEDL/SWo0Ta8F7HgH/0C+eSmW5U0nhsDoZB6A/hxh uN1HMPeB+/vjuV9eqzsANu9lxbOFk2QAPtnGuo9ae+EUE6yAcOqr9rEgvFSaEECI g0gv2rt49z2sW9n9eTkj5+uBTUGLMljYsraLTUtOXYHOcuVAOzeMm4hzyHXwdEXi kSi7p7bEIQgM6RHi2dK11+UPUXI7TgRrEye+ufa00eoHbyaJ5r6Sep8ZX6trLjph 5ec9ytajnQi97Z5Z/eLDu+4kxWMkQAtDi7U7pyBlJzTiIe0/fl74245kakT5URVy zbG3iM/aWG+Rz7uxS0rdCp7cpANWaYXRLyBeSuDJNdEus4zpgrNroN+rREvFz/g= =icBT -----END PGP SIGNATURE----- From dovecot at zp1.net Tue Sep 23 18:09:26 2014 From: dovecot at zp1.net (Henry Stack) Date: Tue, 23 Sep 2014 20:09:26 +0200 Subject: sieve redirect to foreign email gets =?UTF-8?B?4oCcUmVsYXkgYQ==?= =?UTF-8?B?Y2Nlc3MgZGVuaWVk4oCd?= In-Reply-To: <54214C12.3040701@thelounge.net> References: <54208850.6050007@zp1.net> <542146AA.2040905@enas.net> <54214C12.3040701@thelounge.net> Message-ID: <5421B756.8080103@zp1.net> On 23-09-2014 12:31, Reindl Harald wrote: > [...] > no reason for that: smtpd_data_restrictions = reject_unauth_pipelining its goood, the reason is to block clients who speak to early like spammers for example. http://www.postfix.org/postconf.5.html#reject_unauth_pipelining "This stops mail from bulk mail software that improperly uses ESMTP command pipelining in order to speed up deliveries." From h.reindl at thelounge.net Tue Sep 23 18:15:14 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Tue, 23 Sep 2014 20:15:14 +0200 Subject: sieve redirect to foreign email gets =?UTF-8?B?4oCcUmVsYXkgYQ==?= =?UTF-8?B?Y2Nlc3MgZGVuaWVk4oCd?= In-Reply-To: <5421B756.8080103@zp1.net> References: <54208850.6050007@zp1.net> <542146AA.2040905@enas.net> <54214C12.3040701@thelounge.net> <5421B756.8080103@zp1.net> Message-ID: <5421B8B2.2050607@thelounge.net> Am 23.09.2014 um 20:09 schrieb Henry Stack: > On 23-09-2014 12:31, Reindl Harald wrote: >> [...] >> no reason for that: smtpd_data_restrictions = reject_unauth_pipelining > > its goood, the reason is to block clients who speak to early like spammers for example. > http://www.postfix.org/postconf.5.html#reject_unauth_pipelining > "This stops mail from bulk mail software that improperly uses ESMTP command pipelining > in order to speed up deliveries." but nobody needs "smtpd_data_restrictions" for that just add it to "smtpd_recipient_restrictions" if you want to block spammers it's anyways the wrong tool * use port 587 for submission * setup http://www.postfix.org/POSTSCREEN_README.html on port 25 * postscreen_greet_action = enforce * postscreen_greet_wait = ${stress?2}${stress:10} with the above configuration on port 25 a sane client has to wait 10 seconds before he is allowed to talk the first time and only after passed that it has a chance to talk to smtpd at all well, and then you can configure "postscreen_dnsbl_sites" and "postscreen_dnsbl_action = enforce" with a sensible scoring and you are rid of 90% spam at all -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From jjhoffart at icloud.com Tue Sep 23 18:57:03 2014 From: jjhoffart at icloud.com (jjhoffart) Date: Tue, 23 Sep 2014 12:57:03 -0600 Subject: director Message-ID: Hello, I am currently trying to setup a cluster of mail servers. I currently have two servers I am trying to cluster together. These servers will also have a shared NFS backend. I have read on the site that I will need to configure director since I am using NFS. I have read through all of the documentation on director but still need a little guidance to get things up and running. One of the questions I have is about the base_dir on the Multiple Invocations section of the wiki. It states that I will need to change the bas_dir to the new run directory, not sure what needs to happen here, can anyone help me out? From helge at kraak.info Tue Sep 23 19:37:51 2014 From: helge at kraak.info (Helge Kraak) Date: Tue, 23 Sep 2014 21:37:51 +0200 Subject: dsync error: Error: Can't delete mailbox INBOX: INBOX can't be deleted. In-Reply-To: References: <653A24C3-AA9C-4E1D-9B07-87F0E3985526@kraak.info> <4BF1BAA9-26F5-4A37-A35D-B998F8B2D4B1@kraak.info> Message-ID: Hello Alan, thank you very much for your help. You were right about the version issue. I hadn't realized that I wasn't running the latest version of dovecot. Now the dsync migration of my mails was successful. Thanks again for your assistance. Helge Am 22.09.2014 um 15:21 schrieb Alan McGinlay: > On 2014-09-22 13:01, Helge Kraak wrote: >> No one? >> Am 19.09.2014 um 00:57 schrieb Helge Kraak: >> Hello, >> I'm aware of these two threads >> http://www.dovecot.org/pipermail/dovecot/2012-March/thread.html#134311 >> http://dovecot.org/pipermail/dovecot/2012-June/thread.html#136488 >> but unfortunately I wasn't successful with my dsync mailbox migration attempt despite the information I could find there. I'm using iRedMail setup for the dovecot server. I made sure that the dovecot mailbox for the mail import had been freshly created and untouched before I tried to run the following command. >> Running this command: >> sudo doveadm -vvv -o imapc_host=xxx.de -o imapc_user=username -o imapc_password=password -o mail_fsync=never -o mail_prefetch_count=20 -o imapc_features=rfc822.size -o imapc_features=fetch-headers -o imapc_port=993 -o imapc_ssl=imaps -o imapc_ssl_ca_dir=/etc/ssl -o imapc_ssl_verify=no -o imapc_features=rfc822.size -o mailbox_list_index=no -D backup -R -u michael at domain.com imapc: >> I get the following output (I took out some lines obviously not relevant): >> doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules >> doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/lib10_quota_plugin.so >> doveadm(root): Debug: Loading modules from directory: /usr/lib/dovecot/modules/doveadm >> doveadm(root): Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_acl_plugin.so: undefined symbol: acl_user_module (this is usually intentional, so just ignore this message) >> doveadm(root): Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_expire_plugin.so: undefined symbol: expire_set_deinit (this is usually intentional, so just ignore this message) >> doveadm(root): Debug: Module loaded: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_quota_plugin.so >> doveadm(root): Debug: Skipping module doveadm_zlib_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib10_doveadm_zlib_plugin.so: undefined symbol: i_stream_create_deflate (this is usually intentional, so just ignore this message) >> doveadm(root): Debug: Skipping module doveadm_fts_plugin, because dlopen() failed: /usr/lib/dovecot/modules/doveadm/lib20_doveadm_fts_plugin.so: undefined symbol: fts_backend_rescan (this is usually intentional, so just ignore this message) >> doveadm(michael at domain.com): Debug: Added userdb setting: plugin/master_user=michael at domain.com >> doveadm(michael at domain.com): Debug: Added userdb setting: plugin/quota_rule=*:bytes=41943040000 >> doveadm(michael at domain.com): Debug: Effective uid=2000, gid=2000, home=/var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59/ >> doveadm(michael at domain.com): Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir://var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir/:INDEX=//var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir/ >> doveadm(michael at domain.com): Debug: maildir++: root=//var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir, index=, control=, inbox=//var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir, alt= >> doveadm(michael at domain.com): Debug: Namespace : type=shared, prefix=Shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/Shared/%u >> doveadm(michael at domain.com): Debug: shared: root=/var/run/dovecot, index=, control=, inbox=, alt= >> dsync(michael at domain.com): Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=imapc: >> dsync(michael at domain.com): Debug: imapc: root=, index=, control=, inbox=, alt= >> dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Looking up IP address >> dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Connecting to 78.138.89.136:993 >> dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Starting SSL handshake >> dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Server capabilities: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN >> dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Authenticating as username >> dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Server capabilities: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS QUOTA >> dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Authenticated successfully >> dsync(michael at domain.com): Debug: Namespace : type=shared, prefix=Shared/%u/, sep=/, inbox=no, hidden=no, list=children, subscriptions=yes location=maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/Shared/%u >> dsync(michael at domain.com): Debug: shared: root=/var/run/dovecot, index=, control=, inbox=, alt= >> dsync(michael at domain.com): Debug: Namespace : Using permissions from //var/vmail/vmail1/domain.com/m/i/c/michael-2014.09.03.14.32.59//Maildir: mode=0700 gid=-1 >> dsync(michael at domain.com): Error: Can't delete mailbox INBOX: INBOX can't be deleted. >> dsync(michael at domain.com): Info: Amazon: uidnext changed: 1056 != 1 >> dsync(michael at domain.com): Info: INBOX: only in dest (guid=3c68c835800a07547d45000029cbe4c2)= 1 >> dsync(michael at domain.com): Info: Deleted Messages: uidnext changed: 109 != 1 >> dsync(michael at domain.com): Info: MBA Mails: uidnext changed: 444 != 1 >> dsync(michael at domain.com): Info: Archive: highest_modseq changed: 0 != 1 >> dsync(michael at domain.com): Info: Spam: uidnext changed: 3 != 1 >> dsync(michael at domain.com): Info: Apple Mail To Do: highest_modseq changed: 0 != 1 >> dsync(michael at domain.com): Info: Jobsuche: uidnext changed: 22436 != 1 >> dsync(michael at domain.com): Info: Trash (Messages): uidnext changed: 697 != 1 >> dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Looking up IP address >> dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Connecting to IP-Adress:993 >> dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Starting SSL handshake >> dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Server capabilities: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN >> dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Authenticating as username >> dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Server capabilities: IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS QUOTA >> dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Authenticated successfully >> dsync(michael at domain.com): Error: Trying to open a non-listed mailbox with guid=3c68c835800a07547d45000029cbe4c2 >> dsync(michael at domain.com): Error: msg iteration failed: Couldn't open mailbox 3c68c835800a07547d45000029cbe4c2 >> dsync(michael at domain.com): Error: Trying to open a non-listed mailbox with guid=3c68c835800a07547d45000029cbe4c2 >> dsync(michael at domain.com): Debug: imapc(s04.xxx.de:993): Disconnected >> sudo dovecot -n >> # 2.1.7: /etc/dovecot/dovecot.conf >> # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.6 >> auth_master_user_separator = * >> auth_mechanisms = PLAIN LOGIN >> dict { >> acl = mysql:/etc/dovecot/dovecot-share-folder.conf >> quotadict = mysql:/etc/dovecot/dovecot-used-quota.conf >> } >> first_valid_uid = 2000 >> last_valid_uid = 2000 >> listen = * >> log_path = /var/log/dovecot.log >> mail_gid = 2000 >> mail_location = maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/ >> mail_plugins = quota >> mail_uid = 2000 >> 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 >> namespace { >> inbox = yes >> location = >> mailbox Drafts { >> auto = subscribe >> special_use = \Drafts >> } >> mailbox Junk { >> auto = subscribe >> special_use = \Junk >> } >> mailbox Sent { >> auto = subscribe >> special_use = \Sent >> } >> mailbox "Sent Messages" { >> auto = no >> special_use = \Sent >> } >> mailbox Spam { >> auto = no >> special_use = \Junk >> } >> mailbox Trash { >> auto = subscribe >> special_use = \Trash >> } >> prefix = >> separator = / >> type = private >> } >> namespace { >> list = children >> location = maildir:/%%Lh/Maildir/:INDEX=/%%Lh/Maildir/Shared/%%u >> prefix = Shared/%%u/ >> separator = / >> subscriptions = yes >> type = shared >> } >> passdb { >> args = /etc/dovecot/dovecot-mysql.conf >> driver = sql >> } >> passdb { >> args = /etc/dovecot/dovecot-master-users-password >> driver = passwd-file >> master = yes >> } >> plugin { >> acl = vfile >> acl_shared_dict = proxy::acl >> auth_socket_path = /var/run/dovecot/auth-master >> quota = dict:user::proxy::quotadict >> quota_rule = *:storage=1G >> quota_warning = storage=85%% quota-warning 85 %u >> quota_warning2 = storage=90%% quota-warning 90 %u >> quota_warning3 = storage=95%% quota-warning 95 %u >> sieve = /%Lh/sieve/dovecot.sieve >> sieve_default = /var/vmail/sieve/dovecot.sieve >> sieve_dir = /%Lh/sieve >> sieve_global_dir = /var/vmail/sieve >> } >> protocols = pop3 imap sieve lmtp >> service auth { >> unix_listener /var/spool/postfix/private/dovecot-auth { >> group = postfix >> mode = 0666 >> user = postfix >> } >> unix_listener auth-master { >> group = vmail >> mode = 0666 >> user = vmail >> } >> unix_listener auth-userdb { >> group = vmail >> mode = 0660 >> user = vmail >> } >> } >> service dict { >> unix_listener dict { >> group = vmail >> mode = 0660 >> user = vmail >> } >> } >> service imap-login { >> process_limit = 500 >> service_count = 1 >> } >> service lmtp { >> executable = lmtp -L >> inet_listener lmtp { >> port = 24 >> } >> process_min_avail = 5 >> unix_listener /var/spool/postfix/private/dovecot-lmtp { >> group = postfix >> mode = 0600 >> user = postfix >> } >> user = vmail >> } >> service pop3-login { >> service_count = 1 >> } >> service quota-warning { >> executable = script /usr/local/bin/dovecot-quota-warning.sh >> unix_listener quota-warning { >> group = vmail >> mode = 0660 >> user = vmail >> } >> } >> ssl = required >> ssl_cert = > ssl_key = > userdb { >> args = /etc/dovecot/dovecot-mysql.conf >> driver = sql >> } >> protocol lda { >> auth_socket_path = /var/run/dovecot/auth-master >> lda_mailbox_autocreate = yes >> log_path = /var/log/dovecot-sieve.log >> mail_plugins = quota sieve >> postmaster_address = root >> } >> protocol lmtp { >> info_log_path = /var/log/dovecot-lmtp.log >> lmtp_save_to_detail_mailbox = yes >> mail_plugins = quota sieve >> postmaster_address = postmaster >> recipient_delimiter = + >> } >> protocol imap { >> imap_client_workarounds = tb-extra-mailbox-sep >> mail_plugins = quota imap_quota >> } >> protocol pop3 { >> mail_plugins = quota >> pop3_client_workarounds = outlook-no-nuls oe-ns-eoh >> pop3_uidl_format = %08Xu%08Xv >> } >> Any assistance is highly appreciated. Thank you. >> Helge > > I seem to remember having similar issues with dsync on that dovecot version. I am not 100% sure as it was a while ago now. > > Currently using very similar settings to migrate from a cyrus box on solaris 10 and dsync works well. I use Dovecot 2.2.13 from the following ubuntu ppa: > > https://launchpad.net/~bigmichi1/+archive/ubuntu/dovecot > > (the ppa owner is on this list I think) > > There have been a lot of fixes to dsync since 2.2.7 so it might be worth upgrading. > > /A From vorgusa at gmail.com Tue Sep 23 20:24:03 2014 From: vorgusa at gmail.com (Chris Lasater) Date: Tue, 23 Sep 2014 16:24:03 -0400 Subject: director In-Reply-To: References: Message-ID: <5421D6E3.7020704@gmail.com> Basically the director is just another instance of Dovecot, and the base_dir is where the dovecot instance stores its information, so if you want 2 instances on 1 server you will need to separate them. You will need to set up 2 configuration files, one for Director and one for dovecot. When I initially did this, I had some issues with the doveadm command, where it would look at the default location instead of the one in base_dir, I am not sure if this is still the case, but I fixed it by deleting the default and setting neither instance to the default base_dir. To control 1 instance you can run doveadm with the -i flag using the instance_name. doveadm -i Director stop and look into the status of both instances using doveadm instance list. I start the 2nd instance using dovecot -c /path/to/director.conf Hopefully this helps, Chris instance_name = Director base_dir = /home/user/dovecot/var/run/director instance_name = Dovecot base_dir = /home/user/dovecot/var/run/mail On 09/23/2014 02:57 PM, jjhoffart wrote: > Hello, > I am currently trying to setup a cluster of mail servers. I currently have two servers I am trying to cluster together. These servers will also have a shared NFS backend. I have read on the site that I will need to configure director since I am using NFS. I have read through all of the documentation on director but still need a little guidance to get things up and running. One of the questions I have is about the base_dir on the Multiple Invocations section of the wiki. It states that I will need to change the bas_dir to the new run directory, not sure what needs to happen here, can anyone help me out? From eduardo at freedominterface.org Tue Sep 23 20:26:37 2014 From: eduardo at freedominterface.org (Eduardo Ramos) Date: Tue, 23 Sep 2014 17:26:37 -0300 Subject: director In-Reply-To: References: Message-ID: <5421D77D.3080705@freedominterface.org> Hi, In fact you don't NEED a director. You can use two dovecot servers sharing a NFS storage with a normal (backend) implementation. It's good to see that page: http://wiki2.dovecot.org/NFS for some good recomendations. You must have a base_dir for each instance of dovecot you want to run, and a dovecot.conf as well. One could be director and other backend. I suggest you have two separated configuration directories, /etc/dovecot-director and /etc/dovecot-backend. Each with the respective configuration. Start dovecot with "dovecot -c /etc/dovecot-director/dovecot.conf". Backend is the same. In order to help more, provide us more details about your environment and doulbts. On 09/23/2014 03:57 PM, jjhoffart wrote: > Hello, > I am currently trying to setup a cluster of mail servers. I currently have two servers I am trying to cluster together. These servers will also have a shared NFS backend. I have read on the site that I will need to configure director since I am using NFS. I have read through all of the documentation on director but still need a little guidance to get things up and running. One of the questions I have is about the base_dir on the Multiple Invocations section of the wiki. It states that I will need to change the bas_dir to the new run directory, not sure what needs to happen here, can anyone help me out? From eduardo at freedominterface.org Tue Sep 23 20:53:44 2014 From: eduardo at freedominterface.org (Eduardo Ramos) Date: Tue, 23 Sep 2014 17:53:44 -0300 Subject: director In-Reply-To: <797A8820-0AA4-48EF-879D-4E3A81948E49@icloud.com> References: <5421D77D.3080705@freedominterface.org> <797A8820-0AA4-48EF-879D-4E3A81948E49@icloud.com> Message-ID: <5421DDD8.40004@freedominterface.org> The configuration use to be in /etc/dovecot, and the working dir is /var/run/dovecot. You should store your configuration file in the /etc/dovecot. The dovecot.conf file can be copied to dovecot-backend.conf and dovecot-director, for example, and you will use '-c' argument of dovecot binary to load on or another. If you do this, you will need create two separated working dir, that will be defined in base_dir on each configuration file. On 09/23/2014 05:39 PM, jjhoffart wrote: > Thanks for the replies, > I am still fairly new to dovecot and still learning. This is a quick run down of my setup: 3 servers running iRedMail (this is a package that installs dovecot 2.1.7, postfix, and LDAP). All three servers share an NFS backend. The same 3 servers are also sitting behind a load balancer. What I want to do is use these three servers as directors and mail servers. So from the replies I have gotten I understand that I need to create 2 config files 1 for director and 1 for dovecot. Now my next question is do these config files need to be stored in /etc/dovecot or /var/run/dovecot? Also is creating the second config file as simple as copying and renaming the dovecot.conf file? > > On Sep 23, 2014, at 2:26 PM, Eduardo Ramos wrote: > >> Hi, >> >> In fact you don't NEED a director. You can use two dovecot servers sharing a NFS storage with a normal (backend) implementation. It's good to see that page: http://wiki2.dovecot.org/NFS for some good recomendations. >> >> You must have a base_dir for each instance of dovecot you want to run, and a dovecot.conf as well. One could be director and other backend. I suggest you have two separated configuration directories, /etc/dovecot-director and /etc/dovecot-backend. Each with the respective configuration. Start dovecot with "dovecot -c /etc/dovecot-director/dovecot.conf". Backend is the same. >> >> In order to help more, provide us more details about your environment and doulbts. >> >> On 09/23/2014 03:57 PM, jjhoffart wrote: >>> Hello, >>> I am currently trying to setup a cluster of mail servers. I currently have two servers I am trying to cluster together. These servers will also have a shared NFS backend. I have read on the site that I will need to configure director since I am using NFS. I have read through all of the documentation on director but still need a little guidance to get things up and running. One of the questions I have is about the base_dir on the Multiple Invocations section of the wiki. It states that I will need to change the bas_dir to the new run directory, not sure what needs to happen here, can anyone help me out? From vorgusa at gmail.com Tue Sep 23 21:07:17 2014 From: vorgusa at gmail.com (Chris Lasater) Date: Tue, 23 Sep 2014 17:07:17 -0400 Subject: director In-Reply-To: References: <797A8820-0AA4-48EF-879D-4E3A81948E49@icloud.com> Message-ID: <5421E105.6020203@gmail.com> The configuration and run/base_dir directories can be where ever you like. The locations Eduardo stated are the most appropriate for dovecot installed with an RPM. Mine were compiled and set in the home directory, so they are in a slightly different location. As long as you use the -c to point to the correct configuration file you should be good. For mine I kept my dovecot config file in the default location and put the director one elsewhere and created an alias, so that I can start the director by just typing director. This might make things easier for you to manage, then you can just stop it by running "doveadm -i stop" alias director="sudo -E PATH=${PATH} LD_LIBRARY_PATH=${LD_LIBRARY_PATH} /home/user/dovecot/sbin/dovecot -c /home/user/dovecot/etc/dovecot/director.conf" On 09/23/2014 05:00 PM, jjhoffart wrote: >> Thanks for the replies, >> I am still fairly new to dovecot and still learning. This is a quick run down of my setup: 3 servers running iRedMail (this is a package that installs dovecot 2.1.7, postfix, and LDAP). All three servers share an NFS backend. The same 3 servers are also sitting behind a load balancer. What I want to do is use these three servers as directors and mail servers. So from the replies I have gotten I understand that I need to create 2 config files 1 for director and 1 for dovecot. Now my next question is do these config files need to be stored in /etc/dovecot or /var/run/dovecot? Also is creating the second config file as simple as copying and renaming the dovecot.conf file? >> >> On Sep 23, 2014, at 2:26 PM, Eduardo Ramos wrote: >> >>> Hi, >>> >>> In fact you don't NEED a director. You can use two dovecot servers sharing a NFS storage with a normal (backend) implementation. It's good to see that page: http://wiki2.dovecot.org/NFS for some good recomendations. >>> >>> You must have a base_dir for each instance of dovecot you want to run, and a dovecot.conf as well. One could be director and other backend. I suggest you have two separated configuration directories, /etc/dovecot-director and /etc/dovecot-backend. Each with the respective configuration. Start dovecot with "dovecot -c /etc/dovecot-director/dovecot.conf". Backend is the same. >>> >>> In order to help more, provide us more details about your environment and doulbts. >>> >>> On 09/23/2014 03:57 PM, jjhoffart wrote: >>>> Hello, >>>> I am currently trying to setup a cluster of mail servers. I currently have two servers I am trying to cluster together. These servers will also have a shared NFS backend. I have read on the site that I will need to configure director since I am using NFS. I have read through all of the documentation on director but still need a little guidance to get things up and running. One of the questions I have is about the base_dir on the Multiple Invocations section of the wiki. It states that I will need to change the bas_dir to the new run directory, not sure what needs to happen here, can anyone help me out? From dawid.stawiarski at netart.pl Wed Sep 24 05:43:15 2014 From: dawid.stawiarski at netart.pl (Dawid Stawiarski - nazwa.pl) Date: Wed, 24 Sep 2014 07:43:15 +0200 Subject: quota recalc problem for big maildirs In-Reply-To: References: <541BF1D2.9010807@netart.pl> Message-ID: <542259F3.8020705@netart.pl> W dniu 23.09.2014 o 17:25, Timo Sirainen pisze: > On 19 Sep 2014, at 12:05, Dawid Stawiarski - nazwa.pl wrote: > >> we use dovecot 2.2.13, and we've lately started using maildir quota (previously fs quota was used, right now it's "quota = maildir:User quota" changed from "quota = fs:User quota:user:inode_per_mail"). >> >> When the change was applied we didn't manually forced generating maildirsize files. So, when the first deliver happens (or the file grows larger then 5KB) it starts quota recalc. However for users with big maildirs, receiving email every couple of seconds, there are tens of delivery processes each doing its own recalc (as they open file for APPEND and there's no locking). What's even worse, after all the stats and getdents (it takes a lot of IO for 60GB account with 2M emails), deliver makes stat on 'new' dir and detects changes after which it unlinks freshly created maildirsize. So possibly this will never be finished as every process drops its own work. >> >> The same thing happened when we checked the native dovecot LMTP server (every connection has its own forked process - each running independently of the others). >> >> Is it a known unwanted "feature" of maildir quota (and we should use dict quota instead) or a bug that will be fixed? > > It's a feature that won't be changed. The stat()s are especially bad if you see them - they wouldn't happen if your Maildir filenames contain the ,S=size part. Switch to dict file, which won't be recalculated unless you manually do it. > > Ok, thank you kindly for clarification. ps. Our email filenames contain the size part. The stats/getents are for each folder in Maildir (there are folders with 100-200K emails, so even listing it takes a long time - especially if there are tens of processes doing it in parallel) From dmiller at amfes.com Wed Sep 24 06:11:03 2014 From: dmiller at amfes.com (Daniel Miller) Date: Tue, 23 Sep 2014 23:11:03 -0700 Subject: Empty mailboxes In-Reply-To: References: <5416725D.60209@amfes.com> <5420E8F0.4080300@amfes.com> Message-ID: Thank you! Preparing these found the problem. And as I originally felt...it wasn't Dovecot or the Dovecot config. Right around the "cd" and "pwd" commands I realized...I store the mailboxes on my raid - and then have a link to the raid under /var/mail. I didn't re-create that link in the new setup. I KNEW it was going to be something simple, stupid, and totally my fault... Daniel On 9/22/2014 11:38 PM, Steffen Kaiser wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Mon, 22 Sep 2014, Daniel Miller wrote: > >> I set auth_debug=yes and mail_debug=yes. Comparing the log output - >> other than the fact that the working server has additional lines for >> the mailboxes found they look identical. No errors. Yet there's no >> mail when booting the other drive. >> >> I can see the mailboxes in the file path, everything appears mounted, >> I don't see any rights issues. There's no errors. Yet I have no mail. > > post the log lines you get, when you manually login via telnet, e.g.: > > telnet server 143 > 1 login user "password" > 2 select INBOX > 3 logout > > and the output of the SELECT command, doveconf -n and the output of: > > cd "to user's mailbox" > pwd > ls -al > > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBVCEVgHz1H7kL/d9rAQIrnQgAtISTfUmMkJ3aQ+c17kyf1M/9FPFiKZA8 > Y6Pio/eSN9XGQglPGykbHwOCKqsUiQgRKoM0rV2sKvifZ/Z3zx7C2kGG6vRwGa3H > 7Id0eGKBwSOXaGPV6zaPN7K0Dx3n5WXc6fq6S1+vJrXGEMLmbY7icr8COfowNCn9 > dX/vhn/GDC8RiWisu+uQb3IYTQ+WowWUwylIwVlwvaMOZk7eIrcztXuU9BCtO/E3 > bjEITwe1utySfUNB0gcg8HM75yw/AxfcLLmzLm9lvECjJGTm5lqY/h7KkeBNH8iS > Yv/ROmIL8fnRKNSshuefsmihO+dhK3sEn4iuSo5QyOW8QPJwxSOMTg== > =RXeb > -----END PGP SIGNATURE----- From alanm at sics.se Wed Sep 24 09:51:09 2014 From: alanm at sics.se (Alan McGinlay) Date: Wed, 24 Sep 2014 11:51:09 +0200 Subject: Confusing wording on the wiki Message-ID: <09acbdc85bf14083d6f14e2db64e4044@sics.se> Hi, I am confused by the wording of this Wiki entry: sieve = ~/.dovecot.sieve The path to the user's main active Sieve script. When ManageSieve is used, this is a symbolic link pointing to the active script in the sieve_dir directory. Avoid placing the active Sieve script inside the sieve_dir directory. So this should be a link *to* the active script in the sieve_dir directory however the active script shouldn't actually be in that directory???? http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration Confused :S /A From r at sys4.de Wed Sep 24 11:35:36 2014 From: r at sys4.de (Ralf Hildebrandt) Date: Wed, 24 Sep 2014 13:35:36 +0200 Subject: LMTP proxying Message-ID: <20140924113535.GG15207@sys4.de> How exactly is LMTP proxying supposed to work? According to the example on http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy I'm only seeing "proxy" in the password_query statements. But LMTP never sends a password. IMAP Proxying is working OK: Sep 24 12:51:09 imap-login: Info: proxy(ralf.hildebrandt at charite.de): started proxying to dovecot.charite.de:993: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Sep 24 12:51:13 imap-login: Info: proxy(ralf.hildebrandt at charite.de): disconnecting 127.0.0.1 (Disconnected by server): user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured But LMTP is logging this: Sep 24 13:13:25 lmtp(17727): Info: Connect from 127.0.0.1 Sep 24 13:13:51 auth-worker(19603): Info: mysql(sql.posteo.local): Connected to database mailservice Sep 24 13:14:11 lmtp(17727, ralf.hildebrandt at charite.de): Info: save: box=INBOX, uid=1, msgid=, size=304 Sep 24 13:14:11 lmtp(17727, ralf.hildebrandt at charite.de): Info: pH2yN1WnIlQ/RQAAoQzodQ: msgid=unspecified: saved mail to INBOX Sep 24 13:14:11 dict: Info: mysql(sql.charite.de): Connected to database mailservice Sep 24 13:14:13 lmtp(17727): Info: Disconnect from 127.0.0.1: Client quit (in reset) Sep 24 13:15:29 master: Warning: Killed with signal 15 (by pid=25892 uid=0 code=kill) I read that there's no "default port for LMTP", but how can I adapt the query in such a way that the default port 24 is being used ONLY FOR LMTP? I'm using (snippet): ... NULL AS password, \ 'Y' AS nopassword, \ 'Y' AS proxy, 'dovecot.charite.de' AS host, 'any-cert' AS 'ssl', \ ... -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From r at sys4.de Wed Sep 24 11:52:59 2014 From: r at sys4.de (Ralf Hildebrandt) Date: Wed, 24 Sep 2014 13:52:59 +0200 Subject: LMTP proxying In-Reply-To: <20140924113535.GG15207@sys4.de> References: <20140924113535.GG15207@sys4.de> Message-ID: <20140924115259.GH15207@sys4.de> * Ralf Hildebrandt : > How exactly is LMTP proxying supposed to work? > > According to the example on > http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy > > I'm only seeing "proxy" in the password_query statements. Found that one, LMTP needs to use "lmtp_proxy = yes" in order to issue passdb lookups. Wonderful. But my next issue is that there's no "default port for LMTP", but how can I adapt the query in such a way that the default port 24 is being used ONLY FOR LMTP? i.e. use the default port for POP/IMAP/POP3S/IMAPS, but use Port 24 for LMTP. -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From rs at sys4.de Wed Sep 24 12:00:22 2014 From: rs at sys4.de (Robert Schetterer) Date: Wed, 24 Sep 2014 14:00:22 +0200 Subject: LMTP proxying In-Reply-To: <20140924113535.GG15207@sys4.de> References: <20140924113535.GG15207@sys4.de> Message-ID: <5422B256.4080103@sys4.de> Am 24.09.2014 um 13:35 schrieb Ralf Hildebrandt: > How exactly is LMTP proxying supposed to work? > > According to the example on > http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy > > I'm only seeing "proxy" in the password_query statements. > > But LMTP never sends a password. > > > IMAP Proxying is working OK: > > Sep 24 12:51:09 imap-login: Info: proxy(ralf.hildebrandt at charite.de): started proxying to dovecot.charite.de:993: user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured > Sep 24 12:51:13 imap-login: Info: proxy(ralf.hildebrandt at charite.de): disconnecting 127.0.0.1 (Disconnected by server): user=, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured > > But LMTP is logging this: > > Sep 24 13:13:25 lmtp(17727): Info: Connect from 127.0.0.1 > Sep 24 13:13:51 auth-worker(19603): Info: mysql(sql.posteo.local): Connected to database mailservice > Sep 24 13:14:11 lmtp(17727, ralf.hildebrandt at charite.de): Info: save: box=INBOX, uid=1, msgid=, size=304 > Sep 24 13:14:11 lmtp(17727, ralf.hildebrandt at charite.de): Info: pH2yN1WnIlQ/RQAAoQzodQ: msgid=unspecified: saved mail to INBOX > Sep 24 13:14:11 dict: Info: mysql(sql.charite.de): Connected to database mailservice > Sep 24 13:14:13 lmtp(17727): Info: Disconnect from 127.0.0.1: Client quit (in reset) > Sep 24 13:15:29 master: Warning: Killed with signal 15 (by pid=25892 uid=0 code=kill) > > I read that there's no "default port for LMTP", but how can I adapt > the query in such a way that the default port 24 is being used ONLY > FOR LMTP? > > I'm using (snippet): > > ... > NULL AS password, \ > 'Y' AS nopassword, \ > 'Y' AS proxy, 'dovecot.charite.de' AS host, 'any-cert' AS 'ssl', \ > ... > > hm...perhaps and '%s' = 'lmtp' http://wiki2.dovecot.org/Variables i have i.e FROM mailbox WHERE username = '%u' AND active = '1' AND (imap_allowed = '1' or '%Ls' = 'pop3') Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From jogi at mur.at Wed Sep 24 12:38:18 2014 From: jogi at mur.at (=?UTF-8?B?Sm9naSBIb2Ztw7xsbGVy?=) Date: Wed, 24 Sep 2014 14:38:18 +0200 Subject: LMTP proxying In-Reply-To: <20140924115259.GH15207@sys4.de> References: <20140924113535.GG15207@sys4.de> <20140924115259.GH15207@sys4.de> Message-ID: <5422BB3A.3070100@mur.at> Hi Ralf, Am 2014-09-24 um 13:52 schrieb Ralf Hildebrandt: > But my next issue is that there's no "default port for LMTP", but how > can I adapt the query in such a way that the default port 24 is being > used ONLY FOR LMTP? We solved that by setting up a second LDAP passdb for lmtp that supplies the following values (all in one line): pass_attrs = uid=user,=nopassword,proxy=proxy,proxyhost=host,=port=24\ =starttls=any-cert This way our LMTP proxy works fine. Regards, -- j.hofm?ller mur.sat -- a space art project http://sat.mur.at/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 213 bytes Desc: OpenPGP digital signature URL: From pada at posteo.de Wed Sep 24 17:26:52 2014 From: pada at posteo.de (Daniel Parthey) Date: Wed, 24 Sep 2014 19:26:52 +0200 Subject: Confusing wording on the wiki In-Reply-To: <09acbdc85bf14083d6f14e2db64e4044@sics.se> References: <09acbdc85bf14083d6f14e2db64e4044@sics.se> Message-ID: <1761d2e4-4426-47c5-a16e-854a4de45d1b@email.android.com> On 24. September 2014 11:51:09 MESZ, Alan McGinlay wrote: >I am confused by the wording of this Wiki entry: > > sieve = ~/.dovecot.sieve This is the file/link which dovecot does load for SIEVE rule processing. Dovecot does not need to know whether this is a symlink or not. > The path to the user's main active Sieve script. When ManageSieve is >used, this is a symbolic link pointing to the active script in the >sieve_dir directory. Avoid placing the active Sieve script inside the >sieve_dir directory. The sieve_dir is usually in directory "sieve" which is in the same directory as the .dovecot.sieve symlink. The actual files are inside of the sieve directory. Mail_home / .dovecot.sieve -> sieve/one Mail_home / sieve / one Mail_home / sieve / two >So this should be a link *to* the active script in the sieve_dir >directory however the active script shouldn't actually be in that >directory? Yes, the link should not be located in the sieve directory. And the sieve configuration directive should point to the link (or any other file to use for SIEVE). Regards Daniel From andy at xecu.net Wed Sep 24 21:11:28 2014 From: andy at xecu.net (Andy Dills) Date: Wed, 24 Sep 2014 17:11:28 -0400 (EDT) Subject: LDA randomly failing to write email to disk Message-ID: <20140924162424.L6814@shell.xecu.net> We're using 2.2.13 with pigeonhole 0.4.3, in a clustered environment (maildir on netapp, dual dovecot instances where each server is both a proxy and a backend). Every now and then (once a month per user, maybe?), users will see a blank email in their inbox. Investigating further, and we will see that the only information recorded in the maildir file for the message is the Return-Path, the Delivered-To, and the first Received line (the one generated by the local LDA via LMTP). For example, here is what I found in one such email today: Return-Path: Delivered-To: Received: from mail5.xecu.net ([10.0.1.85]) by mail2.xecu.net (Dovecot) with LMTP idX86eBjgaI1RdyQAA3SxDBg for ; Wed, 24 Sep 2014 15:24:20 -0400 Everything past that is lost, as if the either the LDA on mail2 exited early or was never sent the information from the dovecot instance on mail5. Here is a little more detail from the header of the same email, different recipient (all other recipients received the email properly, only one failed to receive properly): Return-Path: Delivered-To: Received: from mail5.xecu.net ([10.0.1.85]) by mail1.xecu.net (Dovecot) with LMTP id KPh8ItMXI1StBAAA/c3zFg for ; Wed, 24 Sep 2014 15:24:20 -0400 Received: from mail5.xecu.net by mail5.xecu.net (Dovecot) with LMTP id QsUBFoQZI1RjhgAAXyr1JQ ; Wed, 24 Sep 2014 15:24:20 -0400 Received: from mail5.xecu.net (localhost [127.0.0.1]) by mail5.xecu.net (Postfix) with ESMTP id 30AAE323BB18; Wed, 24 Sep 2014 15:24:20 -0400 (EDT) ... This is what I see in the logs of mail2, which is where the failure happened: Sep 24 15:24:20 mail2 dovecot: lmtp(51549, yyy at xecu.net): X86eBjgaI1RdyQAA3SxDBg: sieve: msgid=unspecified: stored mail into mailbox 'INBOX' When I look at the logs of mail1, which is where the successful delivery happened: Sep 24 15:24:20 mail1 dovecot: lmtp(1197, yyz at xecu.net): KPh8ItMXI1StBAAA/c3zFg: sieve: msgid=<20140924192412.1435.qmail at xxx.xecu.net>: stored mail into mailbox 'INBOX' Nothing of note seems to be logged on mail5 (only a message from postfix, nothing from the proxy side of the lmtp). I do notice, when I check for the PID of 51549 in the logs, all of its other transactions seem to register with proper msgids and were delivered fine. Also, I notice plenty of other messages that have the msgid=unspecified error, but which were delivered with no problems and not truncated, so I'm suspecting what may be happening is that somehow the backend instance is not receiving the actual data portion, and only getting the envelope from proxy instance. How do I approach debugging this? It's very infrequent, but yet quite annoying. Seems to have started since we upgraded to 2.2.13 (from an older 2.1 build) earlier this year. Thanks, Andy --- Andy Dills Xecunet, Inc. www.xecu.net 301-682-9972 --- From dan at langille.org Thu Sep 25 02:04:58 2014 From: dan at langille.org (Dan Langille) Date: Wed, 24 Sep 2014 22:04:58 -0400 Subject: vsz_limit is 18,447 PB In-Reply-To: References: <68B274DC-F65B-43FF-A68E-859A1163E902@langille.org> <540C19CB.7090501@thinline.cz> <7DB084F3-F021-470D-9A9C-FC9590673BC6@langille.org> <540E2FD0.9030900@thinline.cz> Message-ID: On Sep 15, 2014, at 10:20 AM, Dan Langille wrote: > > On Sep 8, 2014, at 6:38 PM, Jiri Bourek wrote: > >>>> >>>>> Background: I?m in the only user on this system, but this server is accessed by my phone, my laptop, my tablet, and perhaps a web interface. >>>>> >>>> >>>>> >>>>> But there are some interesting values when I look at the output of doveconf. Specifically, vsz_limit is 18,447 PB? yeah, that?s pretty big. >>>>> >>>>> service imap-login { >>>>> vsz_limit = 18446744073709551615 B >>>>> } >>>>> >>>> >>>> According to your log it was process ?im ap" what ran out of memory. You are showing configuration for imap-login - they are not the same thing, see http://wiki2.dovecot.org/Design/Processes >>> >>> My errror, sorry. OK, here?s imap: >>> >>> service imap { >>> chroot = >>> client_limit = 1 >>> drop_priv_before_exec = no >>> executable = imap >>> extra_groups = >>> group = >>> idle_kill = 0 >>> privileged_group = >>> process_limit = 1024 >>> process_min_avail = 0 >>> protocol = imap >>> service_count = 1 >>> type = >>> unix_listener login/imap { >>> group = >>> mode = 0666 >>> user = >>> } >>> user = >>> vsz_limit = 18446744073709551615 B >>> } >>> >>> Still the same value? why not 265MB? >> >> Hm, I can only guess (someone with more knowledge of dovecot source code probably knows better), but it seems like that value is magic number for "not set". My doveconf outputs the same thing on services which don't have vsz_limit set explicitly, but when I list /proc/[pid]/limits on such a service, the row called "Max address space" (which is - AFAIK - limit on vsz) shows 2GB, a value of default_vsz_limit setting. >> >> I'd say don't overthink it, just put explicit vsz_limit = 512M into service imap section (if your machine's RAM allows) and be done with it. > > For the record, the error has recurred a few times, so after today?s incident, I added this to dovecot.conf, and restarted dovecot: > > service imap { > vsz_limit = 512MB > } > > FWIW, the server contains 8192 MB of RAM. For the record, the problem has not recurred. ? Dan Langille -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 333 bytes Desc: Message signed with OpenPGP using GPGMail URL: From thomas at koch.ro Thu Sep 25 06:37:37 2014 From: thomas at koch.ro (Thomas Koch) Date: Thu, 25 Sep 2014 08:37:37 +0200 Subject: sieve folder separator Message-ID: <201409250837.38256.thomas@koch.ro> Hi, I'm moving from one email provider (me) to another (mailbox.org) and observed that the new provider uses "/" instead of "." as a folder separator. Now I need to adapt my sieve script. It's not too much work and I can even just define a variable at the beginning of my script: set "SEP" "/" But it would be great, if SIEVE would come with a predefined constant for the folder separator. Or does this already exists and I didn't find it? Thank you, Thomas Koch From dovecot at luftivennad.com Thu Sep 25 10:39:18 2014 From: dovecot at luftivennad.com (Ain) Date: Thu, 25 Sep 2014 13:39:18 +0300 Subject: Namespace configuration over SQL Message-ID: <09216e6a38304bff56c4d4e71f0adddc.squirrel@webmail.equix.ee> Hello! I had working setup, where namespace settings (including prefix) was queried over SQL. Now, after installing new Dovecot to new server (using same configuration), this is not working anymore. Log shows following error: """ Initialization failed: namespace configuration error: list=yes requires prefix=yes to end with separator """ relevant part from dovecot-sql.conf.ext: """ user_query = \ SELECT \ 1002 AS uid \ , 1003 AS gid \ , CONCAT('/www/home/vmail/domains/', SUBSTRING(d.name, 1, 1), '/', d.name, '/', u.username) AS home \ , namespace_prefix AS 'namespace/default/prefix' \ , 'yes' AS 'namespace/default/inbox' \ , '%s' AS 'mail_service' \ FROM vm_domain d \ INNER JOIN vm_user u ON u.vm_domain_id = d.id \ WHERE d.name = '%d' AND u.username = '%n' AND u.active = 1 AND d.active = 1 """ namespace_prefix can be empty or INBOX. doveconf -n output: """ # 2.2.13: /usr/local/etc/dovecot/dovecot.conf # OS: FreeBSD 9.3-RELEASE amd64 auth_debug = yes auth_verbose = yes disable_plaintext_auth = no listen = * mail_debug = yes mail_location = maildir:~/Maildir mmap_disable = yes namespace default { inbox = yes list = yes location = prefix = separator = . type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change append mail_log_fields = uid box msgid size mail_log_group_events = no } service imap { process_limit = 1480 } ssl_cert = References: <54216809.8060709@heinlein-support.de> Message-ID: <20140925111223.GC23735@sys4.de> * Peer Heinlein : > > Using doveadm penalty I just noticed a penalty for 0.0.0.0. > > Is this Postfix querying the auth-socket for his SASL-requests? Maybe a portscan? Sometimes they turn up as 0.0.0.0 -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From r at sys4.de Thu Sep 25 12:22:30 2014 From: r at sys4.de (Ralf Hildebrandt) Date: Thu, 25 Sep 2014 14:22:30 +0200 Subject: SSL issues when proxying Message-ID: <20140925122229.GD23735@sys4.de> I'm getting this in the log when proxying IMAP (three "valid certificate" messages, two "Invalid certificate" messages) Why is dovecot (acting as a proxy to another dovecot instance here) not recognizing the StartCom Extended Validation Server CA? . LOGIN ralf.hildebrandt at charite.de mypassword Sep 25 14:13:04 auth-worker(30859): Info: mysql(sql.charite.de): Connected to database mailservice Sep 25 14:13:04 imap-login: Debug: SSL: where=0x10, ret=1: before/connect initialization [127.0.0.1] Sep 25 14:13:04 imap-login: Debug: SSL: where=0x1001, ret=1: before/connect initialization [127.0.0.1] Sep 25 14:13:04 imap-login: Debug: SSL: where=0x1001, ret=1: unknown state [127.0.0.1] Sep 25 14:13:04 imap-login: Debug: SSL: where=0x1002, ret=-1: unknown state [127.0.0.1] Sep 25 14:13:04 imap-login: Debug: SSL: where=0x1001, ret=1: SSLv3 read server hello A [127.0.0.1] Sep 25 14:13:04 imap-login: Info: Invalid certificate: unable to get local issuer certificate: /C=IL/O=StartCom Ltd./OU=StartCom Certification Authority/CN=StartCom Extended Validation Server CA Sep 25 14:13:04 imap-login: Info: Invalid certificate: certificate not trusted: /C=IL/O=StartCom Ltd./OU=StartCom Certification Authority/CN=StartCom Extended Validation Server CA Sep 25 14:13:04 imap-login: Info: Valid certificate: /C=DE/ST=Berlin/L=Berlin/postalCode=12205/street=Charitestrasse 1/O=Charite Universitaetsmedizin/CN=imap.charite.de/emailAddress=postmaster at charite.de/serialNumber=HRAxxxx/businessCategory=Private Organization/1.3.6.1.4.1.311.60.2.1.1=Mitte/1.3.6.1.4.1.311.60.2.1.2=Berlin/1.3.6.1.4.1.311.60.2.1.3=DE Sep 25 14:13:04 imap-login: Info: Valid certificate: /C=IL/O=StartCom Ltd./OU=StartCom Certification Authority/CN=StartCom Extended Validation Server CA Sep 25 14:13:04 imap-login: Info: Valid certificate: /C=DE/ST=Berlin/L=Berlin/postalCode=12205/street=Charitestrasse 1/O=Charite Universitaetsmedizin/CN=imap.charite.de/emailAddress=postmaster at charite.de/serialNumber=HRAxxxx/businessCategory=Private Organization/1.3.6.1.4.1.311.60.2.1.1=Mitte/1.3.6.1.4.1.311.60.2.1.2=Berlin/1.3.6.1.4.1.311.60.2.1.3=DE Sep 25 14:13:04 imap-login: Debug: SSL: where=0x1001, ret=1: SSLv3 read server certificate A [127.0.0.1] Sep 25 14:13:04 imap-login: Debug: SSL: where=0x1001, ret=1: SSLv3 read server key exchange A [127.0.0.1] Sep 25 14:13:04 imap-login: Debug: SSL: where=0x1001, ret=1: SSLv3 read server done A [127.0.0.1] Sep 25 14:13:04 imap-login: Debug: SSL: where=0x1001, ret=1: SSLv3 write client key exchange A [127.0.0.1] Sep 25 14:13:04 imap-login: Debug: SSL: where=0x1001, ret=1: SSLv3 write change cipher spec A [127.0.0.1] Sep 25 14:13:04 imap-login: Debug: SSL: where=0x1001, ret=1: SSLv3 write finished A [127.0.0.1] Sep 25 14:13:04 imap-login: Debug: SSL: where=0x1001, ret=1: SSLv3 flush data [127.0.0.1] Sep 25 14:13:04 imap-login: Debug: SSL: where=0x1002, ret=-1: SSLv3 read server session ticket A [127.0.0.1] Sep 25 14:13:04 imap-login: Debug: SSL: where=0x1002, ret=-1: SSLv3 read server session ticket A [127.0.0.1] Sep 25 14:13:04 imap-login: Debug: SSL: where=0x1001, ret=1: SSLv3 read server session ticket A [127.0.0.1] Sep 25 14:13:04 imap-login: Debug: SSL: where=0x1001, ret=1: SSLv3 read finished A [127.0.0.1] Sep 25 14:13:04 imap-login: Debug: SSL: where=0x20, ret=1: SSL negotiation finished successfully [127.0.0.1] Sep 25 14:13:04 imap-login: Debug: SSL: where=0x1002, ret=1: SSL negotiation finished successfully [127.0.0.1] . OK [CAPABILITY ... -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From skdovecot at smail.inf.fh-brs.de Thu Sep 25 12:33:37 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Thu, 25 Sep 2014 14:33:37 +0200 (CEST) Subject: SSL issues when proxying In-Reply-To: <20140925122229.GD23735@sys4.de> References: <20140925122229.GD23735@sys4.de> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 25 Sep 2014, Ralf Hildebrandt wrote: > Date: Thu, 25 Sep 2014 14:22:30 +0200 > From: Ralf Hildebrandt > To: dovecot at dovecot.org > Subject: SSL issues when proxying > > I'm getting this in the log when proxying IMAP (three "valid > certificate" messages, two "Invalid certificate" messages) does one of your proxies or servers is missing a root CA? Or do your hosts query a cert database or something like that? Can you validate the cert on all hosts via openssl manually? - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBVCQLoXz1H7kL/d9rAQItWwf/QGaCcxwIvAE2DJgd4rjvL/3/blnPZIQL 16TjRbSpg2c/GCPWMkMlIlavhoooGyqxEyyHNV0hvBGqg9Im/6uzUwJMD4899f9g rB3nN6jMrLPP99LyIPgzpJe+Xnp/5HGMRMS8YKsri6zP7Ltx2mP6rzKDxWr9wd1L aaEozOR+wwVb2N4Fz6wYBX5kKLA28tVdjxLA+mX9xjDw3LzSPXFtgK2Bg3zC+6ln baX2FIlhsiWid7uzl5UblRcAn/oocaXyn/lr3s0jZ6sX2Uh/Ppvx48eJqlEcowiH BrvRfDRiyyLS10VmgGG+WxSDYjD5J5sfeQ6LxkwaBkNg3P5VcREyNA== =4JwM -----END PGP SIGNATURE----- From lst_hoe02 at kwsoft.de Thu Sep 25 12:32:37 2014 From: lst_hoe02 at kwsoft.de (lst_hoe02 at kwsoft.de) Date: Thu, 25 Sep 2014 14:32:37 +0200 Subject: SSL issues when proxying In-Reply-To: <20140925122229.GD23735@sys4.de> Message-ID: <20140925143237.Horde.1A4MA02PFfeEB5v9XauAyQ1@webmail.kwsoft.de> Zitat von Ralf Hildebrandt : > I'm getting this in the log when proxying IMAP (three "valid > certificate" messages, two "Invalid certificate" messages) > > Why is dovecot (acting as a proxy to another dovecot instance here) not > recognizing the StartCom Extended Validation Server CA? > Forgot to include the matching intermediate CA maybe? Regards Andi -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5958 bytes Desc: S/MIME Cryptographic Signature URL: From r at sys4.de Thu Sep 25 12:37:12 2014 From: r at sys4.de (Ralf Hildebrandt) Date: Thu, 25 Sep 2014 14:37:12 +0200 Subject: SSL issues when proxying In-Reply-To: <20140925143237.Horde.1A4MA02PFfeEB5v9XauAyQ1@webmail.kwsoft.de> References: <20140925122229.GD23735@sys4.de> <20140925143237.Horde.1A4MA02PFfeEB5v9XauAyQ1@webmail.kwsoft.de> Message-ID: <20140925123712.GE23735@sys4.de> * lst_hoe02 at kwsoft.de : > > Zitat von Ralf Hildebrandt : > > >I'm getting this in the log when proxying IMAP (three "valid > >certificate" messages, two "Invalid certificate" messages) > > > >Why is dovecot (acting as a proxy to another dovecot instance here) not > >recognizing the StartCom Extended Validation Server CA? > > > > Forgot to include the matching intermediate CA maybe? Certificate chain 0 s:/C=DE/ST=Berlin/L=Berlin/postalCode=... i:/C=IL/O=StartCom Ltd./OU=StartCom Certification Authority/CN=StartCom Extended Validation Server CA 1 s:/C=IL/O=StartCom Ltd./OU=StartCom Certification Authority/CN=StartCom Extended Validation Server CA i:/C=IL/O=StartCom Ltd./OU=Secure Digital Certificate Signing/CN=StartCom Certification Authority Oh bloody hell. I do have "StartCom Extended Validation Server CA" but not "StartCom Certification Authority". MEH! -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From slitt at troubleshooters.com Thu Sep 25 16:14:40 2014 From: slitt at troubleshooters.com (Steve Litt) Date: Thu, 25 Sep 2014 12:14:40 -0400 Subject: Does dovecot work OK on *BSD? Message-ID: <20140925121440.18d15686@mydesq2.domain.cxm> Hi all, I have a dovecot server on my Debian Wheezy desktop computer. My days with Debian are limited, and I'm investigating several 'BSD's: OpenBSD FreeBSD PCBSD NetBSD DragonflyBSD etc Is there any reason Dovecot wouldn't work on any of those? Does anyone know if those OS's have packages for Dovecot, or do I need to compile it myself? Thanks, SteveT Steve Litt * http://www.troubleshooters.com/ Troubleshooting Training * Human Performance From astephens at ptera.com Thu Sep 25 16:17:24 2014 From: astephens at ptera.com (Art Stephens) Date: Thu, 25 Sep 2014 09:17:24 -0700 Subject: Quota Woes Message-ID: Trying to get quota to show up in IMP - Horde 5.x Seems it is not working with dovecot Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready. root at mail:~# dovecot --version 2.0.19 root at mail:~# dovecot -n # 2.0.19: /etc/dovecot/dovecot.conf # OS: Linux 3.11.0-26-generic x86_64 Ubuntu 12.04.4 LTS auth_mechanisms = plain login disable_plaintext_auth = no mail_location = mbox:~/mail/:INBOX=/var/mail/%u mail_plugins = " quota" passdb { driver = pam } plugin { quota = fs:User quota quota_rule = *:storage=300M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u } protocols = " imap pop3" service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } ssl_cert = References: <20140925121440.18d15686@mydesq2.domain.cxm> Message-ID: <54244237.6040908@netocean.de> Hi Steve, Go for FreeBSD ;) it offers Dovecot(2) via ports or via package. I always recommend ports though, due to the fact of being able to enable/disable options - but that's your choise. Ports: cd /usr/ports/mail/dovecot2 make install clean or via pkg(8): pkg install dovecot2 I can allway recommend to ask your friend Google: "FreeBSD + Dovecot + Tutorial" or "FreeBSD + Dovecot + How to". According to my knowledge, it works quite the same with the other BSDs in your list. It's been a while since I worked with one of them. I sticked to FreeBSD * For updating / maintenance of ports and packages, I recommend portmaster. * For System binary related updates there is freebsd-update(8). Best Regards, Leander S. Am 25.09.14 18:14, schrieb Steve Litt: > Hi all, > > I have a dovecot server on my Debian Wheezy desktop computer. My days > with Debian are limited, and I'm investigating several 'BSD's: > > OpenBSD > FreeBSD > PCBSD > NetBSD > DragonflyBSD > etc > > Is there any reason Dovecot wouldn't work on any of those? Does anyone > know if those OS's have packages for Dovecot, or do I need to compile > it myself? > > Thanks, > > SteveT > > Steve Litt * http://www.troubleshooters.com/ > Troubleshooting Training * Human Performance From ef at math.uni-bonn.de Thu Sep 25 16:50:42 2014 From: ef at math.uni-bonn.de (Edgar =?iso-8859-1?B?RnXf?=) Date: Thu, 25 Sep 2014 18:50:42 +0200 Subject: Does dovecot work OK on *BSD? In-Reply-To: <20140925121440.18d15686@mydesq2.domain.cxm> References: <20140925121440.18d15686@mydesq2.domain.cxm> Message-ID: <20140925165041.GP39340@trav.math.uni-bonn.de> I can confirm that Dovecot 1.2 (I started with 0.9 back in the day and just didn't yet upgrade to 2.x) works fine under NetBSD. From larryrtx at gmail.com Thu Sep 25 17:01:01 2014 From: larryrtx at gmail.com (Larry Rosenman) Date: Thu, 25 Sep 2014 12:01:01 -0500 Subject: Does dovecot work OK on *BSD? In-Reply-To: <20140925121440.18d15686@mydesq2.domain.cxm> References: <20140925121440.18d15686@mydesq2.domain.cxm> Message-ID: I run dovecot on FreeBSD and its in ports.. no issues at all and the maintainer keeps it current. On Sep 25, 2014 11:17 AM, "Steve Litt" wrote: > Hi all, > > I have a dovecot server on my Debian Wheezy desktop computer. My days > with Debian are limited, and I'm investigating several 'BSD's: > > OpenBSD > FreeBSD > PCBSD > NetBSD > DragonflyBSD > etc > > Is there any reason Dovecot wouldn't work on any of those? Does anyone > know if those OS's have packages for Dovecot, or do I need to compile > it myself? > > Thanks, > > SteveT > > Steve Litt * http://www.troubleshooters.com/ > Troubleshooting Training * Human Performance > From dovecot.org at veggiechinese.net Thu Sep 25 17:28:44 2014 From: dovecot.org at veggiechinese.net (Will Yardley) Date: Thu, 25 Sep 2014 10:28:44 -0700 Subject: Does dovecot work OK on *BSD? In-Reply-To: References: <20140925121440.18d15686@mydesq2.domain.cxm> Message-ID: <20140925172844.GS8353@aura.veggiechinese.net> On Thu, Sep 25, 2014 at 12:01:01PM -0500, Larry Rosenman wrote: > I run dovecot on FreeBSD and its in ports.. no issues at all and the > maintainer keeps it current. I don't use it very much (mostly read mail locally, and it's a single-user system), but I have no problems with Dovecot (2.2.x, built from ports) on my FreeBSD box. w From trashcan at odo.in-berlin.de Thu Sep 25 17:29:19 2014 From: trashcan at odo.in-berlin.de (Michael Grimm) Date: Thu, 25 Sep 2014 19:29:19 +0200 Subject: Does dovecot work OK on *BSD? In-Reply-To: <20140925121440.18d15686@mydesq2.domain.cxm> References: <20140925121440.18d15686@mydesq2.domain.cxm> Message-ID: On 25.09.2014, at 18:14, Steve Litt wrote: > I'm investigating several 'BSD's: > > FreeBSD One more to confirm that Dovecot and Pigeonhole are running at FreeBSD. > Does anyone know if those OS's have packages for Dovecot, or do I > need to compile it myself? No need to compile, both come as ports. But if you might be interested in testing upcoming versions, it's pretty simple to set up a mercurial repository and compile from scratch, both Dovecot and Pigeonhole. Regards, Michael From remko at FreeBSD.org Thu Sep 25 17:34:28 2014 From: remko at FreeBSD.org (Remko Lodder) Date: Thu, 25 Sep 2014 19:34:28 +0200 Subject: Does dovecot work OK on *BSD? In-Reply-To: <20140925121440.18d15686@mydesq2.domain.cxm> References: <20140925121440.18d15686@mydesq2.domain.cxm> Message-ID: On 25 Sep 2014, at 18:14, Steve Litt wrote: > Hi all, > > I have a dovecot server on my Debian Wheezy desktop computer. My days > with Debian are limited, and I'm investigating several 'BSD's: > > OpenBSD > FreeBSD > PCBSD > NetBSD > DragonflyBSD > etc > > Is there any reason Dovecot wouldn't work on any of those? Does anyone > know if those OS's have packages for Dovecot, or do I need to compile > it myself? > > Thanks, > > SteveT it works just fine for my little company, see my signature on what OS I prefer. Poke me in case you need help .. Cheerio Remko > > Steve Litt * http://www.troubleshooters.com/ > Troubleshooting Training * Human Performance -- /"\ Best regards, | remko at FreeBSD.org \ / Remko Lodder | remko at EFnet X http://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message signed with OpenPGP using GPGMail URL: From slusarz at curecanti.org Thu Sep 25 18:39:11 2014 From: slusarz at curecanti.org (Michael M Slusarz) Date: Thu, 25 Sep 2014 12:39:11 -0600 Subject: Quota Woes In-Reply-To: Message-ID: <20140925123911.Horde.r6BJ1plJFjs4gJ8k8UJ2iw1@bigworm.curecanti.org> Quoting Art Stephens : > Trying to get quota to show up in IMP - Horde 5.x > > Seems it is not working with dovecot > > Escape character is '^]'. > * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE > STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready. This is the pre-authentication capability, so it wouldn't display QUOTA even if it is correctly enabled. You need the post-authentication capability instead. michael From Rainer at krugs.de Thu Sep 25 19:52:44 2014 From: Rainer at krugs.de (Rainer M Krug) Date: Thu, 25 Sep 2014 21:52:44 +0200 Subject: Indexing of mailf fts clucene aborts Message-ID: Hi I am trying lucene to index my email. To create the index, I run the following command and the indexing aborts: ,---- | 09:42:20 ~$ doveadm -Dv index -u rainerkrug 'RMKrugGMAIL.*' | doveadm(rainerkrug): Debug: Loading modules from directory: /usr/local/Cellar/dovecot/2.2.13_1/lib/dovecot | doveadm(rainerkrug): Debug: Module loaded: /usr/local/Cellar/dovecot/2.2.13_1/lib/dovecot/lib20_fts_plugin.so | doveadm(rainerkrug): Debug: Module loaded: /usr/local/Cellar/dovecot/2.2.13_1/lib/dovecot/lib21_fts_lucene_plugin.so | doveadm(rainerkrug): Debug: Loading modules from directory: /usr/local/Cellar/dovecot/2.2.13_1/lib/dovecot/doveadm | doveadm(rainerkrug): Debug: Skipping module doveadm_acl_plugin, because dlopen() failed: dlopen(/usr/local/Cellar/dovecot/2.2.13_1/lib/dovecot/doveadm/lib10_doveadm_acl_plugin.so, 10): Symbol not found: _acl_user_module | Referenced from: /usr/local/Cellar/dovecot/2.2.13_1/lib/dovecot/doveadm/lib10_doveadm_acl_plugin.so | Expected in: flat namespace | in /usr/local/Cellar/dovecot/2.2.13_1/lib/dovecot/doveadm/lib10_doveadm_acl_plugin.so (this is usually intentional, so just ignore this message) | doveadm(rainerkrug): Debug: Skipping module doveadm_expire_plugin, because dlopen() failed: dlopen(/usr/local/Cellar/dovecot/2.2.13_1/lib/dovecot/doveadm/lib10_doveadm_expire_plugin.so, 10): Symbol not found: _expire_set_deinit | Referenced from: /usr/local/Cellar/dovecot/2.2.13_1/lib/dovecot/doveadm/lib10_doveadm_expire_plugin.so | Expected in: flat namespace | in /usr/local/Cellar/dovecot/2.2.13_1/lib/dovecot/doveadm/lib10_doveadm_expire_plugin.so (this is usually intentional, so just ignore this message) | doveadm(rainerkrug): Debug: Skipping module doveadm_quota_plugin, because dlopen() failed: dlopen(/usr/local/Cellar/dovecot/2.2.13_1/lib/dovecot/doveadm/lib10_doveadm_quota_plugin.so, 10): Symbol not found: _quota_user_module | Referenced from: /usr/local/Cellar/dovecot/2.2.13_1/lib/dovecot/doveadm/lib10_doveadm_quota_plugin.so | Expected in: flat namespace | in /usr/local/Cellar/dovecot/2.2.13_1/lib/dovecot/doveadm/lib10_doveadm_quota_plugin.so (this is usually intentional, so just ignore this message) | doveadm(rainerkrug): Debug: Module loaded: /usr/local/Cellar/dovecot/2.2.13_1/lib/dovecot/doveadm/lib20_doveadm_fts_lucene_plugin.so | doveadm(rainerkrug): Debug: Module loaded: /usr/local/Cellar/dovecot/2.2.13_1/lib/dovecot/doveadm/lib20_doveadm_fts_plugin.so | doveadm(rainerkrug): Debug: Effective uid=501, gid=20, home=/Users/rainerkrug | doveadm(rainerkrug): Debug: Namespace inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, subscriptions=yes location=maildir:~/Maildir | doveadm(rainerkrug): Debug: maildir++: root=/Users/rainerkrug/Maildir, index=, indexpvt=, control=, inbox=/Users/rainerkrug/Maildir, alt= | doveadm(rainerkrug): Debug: Ignoring unknown cache field: pop3.order | doveadm(rainerkrug): Debug: Ignoring unknown cache field: binary.parts | doveadm(rainerkrug): Info: RMKrugGMAIL.[Gmail].All Mail: Caching mails seq=2..49011 | 48700/49010Assertion failed: (numDocsInStore*8 == directory->fileLength( (docStoreSegment + "." + IndexFileNames::FIELDS_INDEX_EXTENSION).c_str() )), function closeDocStore, file /tmp/clucene-M0PS6G/src/core/CLucene/index/DocumentsWriter.cpp, line 210. | Abort trap: 6 `---- Any suggestions? I am using dovecot on a Mac, Maverich=ks, installed via homebrew. If you need any further info, please let me know. Thanks, Rainer -- Rainer M. Krug email: Rainerkrugsde PGP: 0x0F52F982 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 494 bytes Desc: not available URL: From jtam.home at gmail.com Fri Sep 26 00:59:29 2014 From: jtam.home at gmail.com (Joseph Tam) Date: Thu, 25 Sep 2014 17:59:29 -0700 (PDT) Subject: Is dovecot vulnerable to the shellshock/CVE-2014-6271 exploit? Message-ID: I'm right now handling this beach-ball sized grenade, and trying to figure out which of our services need to be locked down right away. Since dovecot passes values via environment variables based on user input (e.g. username, password, mailbox?) to auxilliary executables (including possibly bash shell scripts), is dovecot vulnerable to this exploit? (This is not a fault of dovecot, but rather bash's inadequate handling of environment variables.) For example, injection of this sort 1 LOGIN (){x;}exploit-code whatever I guess auth_username_chars would mitigate this particular attempt (assuming it can work), but other values such as mailbox names could also be injected post authentication. Can someone with working knowlegde of dovecot's internals confirm/deny whether this is a something that needs to be addressed? Joseph Tam From mark at ecs.vuw.ac.nz Fri Sep 26 03:03:13 2014 From: mark at ecs.vuw.ac.nz (Mark Davies) Date: Fri, 26 Sep 2014 15:03:13 +1200 Subject: Does dovecot work OK on *BSD? In-Reply-To: <20140925121440.18d15686@mydesq2.domain.cxm> References: <20140925121440.18d15686@mydesq2.domain.cxm> Message-ID: <201409261503.13798.mark@ecs.vuw.ac.nz> dovecot 2.2.13 works very nicely here via pkgsrc on NetBSD. cheers mark From johan+dovecot at huldtgren.com Fri Sep 26 03:10:58 2014 From: johan+dovecot at huldtgren.com (Johan Huldtgren) Date: Thu, 25 Sep 2014 23:10:58 -0400 Subject: Does dovecot work OK on *BSD? In-Reply-To: <20140925121440.18d15686@mydesq2.domain.cxm> References: <20140925121440.18d15686@mydesq2.domain.cxm> Message-ID: <5424D942.6050705@huldtgren.com> > I have a dovecot server on my Debian Wheezy desktop computer. My days > with Debian are limited, and I'm investigating several 'BSD's: > > OpenBSD > FreeBSD > PCBSD > NetBSD > DragonflyBSD > etc > > Is there any reason Dovecot wouldn't work on any of those? Does anyone > know if those OS's have packages for Dovecot, or do I need to compile > it myself? I've successfully run Dovecot on OpenBSD since 2010 and before that for many years on FreeBSD. Never had any issues, runs just fine on both those OSs. .jh From e1c1bac6253dc54a1e89ddc046585792 at posteo.net Fri Sep 26 04:29:20 2014 From: e1c1bac6253dc54a1e89ddc046585792 at posteo.net (Philipp) Date: Fri, 26 Sep 2014 06:29:20 +0200 Subject: Is dovecot vulnerable to the shellshock/CVE-2014-6271 =?UTF-8?Q?exploit=3F?= In-Reply-To: References: Message-ID: <7caf415615b88c024a8acfdf63e87f74@posteo.de> Am 26.09.2014 02:59 schrieb Joseph Tam: > Since dovecot passes values via environment variables based on > user input (e.g. username, password, mailbox?) to auxilliary > executables (including possibly bash shell scripts), is dovecot > vulnerable to this exploit? Given this article about how e.g. PHP could be vulnerable via popen/system: http://lcamtuf.blogspot.de/2014/09/quick-notes-about-bash-bug-its-impact.html I can only think about sieve now, when it constructs mail and pipes that to sendmail_path, but I would be surprised if this is using user-input (e.g. script) in environment variables. I was skimming through Roundcube and didnt find something 'fishy' so far, but that doesnt mean there is nothing ;-). From manu at netbsd.org Fri Sep 26 05:20:46 2014 From: manu at netbsd.org (Emmanuel Dreyfus) Date: Fri, 26 Sep 2014 05:20:46 +0000 Subject: Does dovecot work OK on *BSD? In-Reply-To: <201409261503.13798.mark@ecs.vuw.ac.nz> References: <20140925121440.18d15686@mydesq2.domain.cxm> <201409261503.13798.mark@ecs.vuw.ac.nz> Message-ID: <20140926052046.GX8379@homeworld.netbsd.org> On Fri, Sep 26, 2014 at 03:03:13PM +1200, Mark Davies wrote: > dovecot 2.2.13 works very nicely here via pkgsrc on NetBSD. Same here, works fine on NetBSD. -- Emmanuel Dreyfus manu at netbsd.org From rbthomas at pobox.com Fri Sep 26 07:08:14 2014 From: rbthomas at pobox.com (Rick Thomas) Date: Fri, 26 Sep 2014 00:08:14 -0700 Subject: [Solved] How to configure dovecot imap to listen on multiple ports? In-Reply-To: <0732BD97-524F-45B5-8020-A74203B58145@pobox.com> References: <1B56DA21-CE88-4385-8055-1B4126727252@pobox.com> <53FA5219.1010205@thelounge.net> <4DE34AE0-0D0C-4F73-A4FC-BFC3341241D3@pobox.com> <53FB2D6D.4060602@gedalya.net> <0732BD97-524F-45B5-8020-A74203B58145@pobox.com> Message-ID: I'm running Debian Wheezy with Dovecot version 2.1.7. The following works for me: ------------- /etc/dovecot/local.conf ----------- service imap-login { inet_listener imap { #port = 143 } inet_listener imaps { port = 7993 ssl = yes } inet_listener imaps2 { port = 993 ssl = yes } # Number of connections to handle before starting a new process. Typically # the only useful values are 0 (unlimited) or 1. 1 is more secure, but 0 # is faster. #service_count = 1 # Number of processes to always keep waiting for more connections. #process_min_avail = 0 # If you set service_count=0, you probably need to grow this. #vsz_limit = $default_vsz_limit } ------------- /etc/dovecot/local.conf ----------- Thanks for all the help! Rick From stephan at rename-it.nl Fri Sep 26 08:26:23 2014 From: stephan at rename-it.nl (Stephan Bosch) Date: Fri, 26 Sep 2014 10:26:23 +0200 Subject: Is dovecot vulnerable to the shellshock/CVE-2014-6271 exploit? In-Reply-To: <7caf415615b88c024a8acfdf63e87f74@posteo.de> References: <7caf415615b88c024a8acfdf63e87f74@posteo.de> Message-ID: <5425232F.90308@rename-it.nl> On 9/26/2014 6:29 AM, Philipp wrote: > Am 26.09.2014 02:59 schrieb Joseph Tam: >> Since dovecot passes values via environment variables based on >> user input (e.g. username, password, mailbox?) to auxilliary >> executables (including possibly bash shell scripts), is dovecot >> vulnerable to this exploit? > > Given this article about how e.g. PHP could be vulnerable via > popen/system: > http://lcamtuf.blogspot.de/2014/09/quick-notes-about-bash-bug-its-impact.html > > I can only think about sieve now, when it constructs mail and pipes > that to sendmail_path, > but I would be surprised if this is using user-input (e.g. script) in > environment variables. I don't see much of an attack vector there either. However, there are some people that have wrapped /usr/sbin/sendmail in a shell script to achieve some sort of custom messaging behavior. Those would be vulnerable. Another possibility for trouble would be systems using the Pigeonhole extprograms plugin with shell scripts. Other than that, Pigeonhole doesn't invoke other executables while executing a Sieve script. Regards, Stephan. From jtam.home at gmail.com Fri Sep 26 08:46:56 2014 From: jtam.home at gmail.com (Joseph Tam) Date: Fri, 26 Sep 2014 01:46:56 -0700 (PDT) Subject: Is dovecot vulnerable to the shellshock/CVE-2014-6271 exploit? In-Reply-To: <5425232F.90308@rename-it.nl> References: <7caf415615b88c024a8acfdf63e87f74@posteo.de> <5425232F.90308@rename-it.nl> Message-ID: On Fri, 26 Sep 2014, Stephan Bosch wrote: > I don't see much of an attack vector there either. However, there are > some people that have wrapped /usr/sbin/sendmail in a shell script to > achieve some sort of custom messaging behavior. Those would be vulnerable. > > Another possibility for trouble would be systems using the Pigeonhole > extprograms plugin with shell scripts. Although I don't use it, it's plausible the checkpassword hook is also vulnerable via the MASTER_USER environment variable: http://wiki2.dovecot.org/AuthDatabase/CheckPassword Joseph Tam From tss at iki.fi Fri Sep 26 09:22:38 2014 From: tss at iki.fi (Timo Sirainen) Date: Fri, 26 Sep 2014 12:22:38 +0300 Subject: Is dovecot vulnerable to the shellshock/CVE-2014-6271 exploit? In-Reply-To: References: <7caf415615b88c024a8acfdf63e87f74@posteo.de> <5425232F.90308@rename-it.nl> Message-ID: On 26 Sep 2014, at 11:46, Joseph Tam wrote: > On Fri, 26 Sep 2014, Stephan Bosch wrote: > >> I don't see much of an attack vector there either. However, there are >> some people that have wrapped /usr/sbin/sendmail in a shell script to >> achieve some sort of custom messaging behavior. Those would be vulnerable. >> >> Another possibility for trouble would be systems using the Pigeonhole >> extprograms plugin with shell scripts. > > Although I don't use it, it's plausible the checkpassword hook is also vulnerable > via the MASTER_USER environment variable: > > http://wiki2.dovecot.org/AuthDatabase/CheckPassword This is one possibility, and it's the worst one because it could happen before login. But it requires two things: 1. auth_username_chars setting must include the characters required in the exploit, so "(){;" at least I guess. None of these characters are enabled by default. But I think some people may have set this setting to empty to allow all characters. 2. checkpassword must call bash, which also isn't done by default. Another possibility is is that in some setups the password (%w) may be added to userdb fields, which ends up being exported to environment if post-login scripts are used. Again Dovecot doesn't execute shell automatically, but it may end up being executed by the configuration. So this requires a valid username + password, and ability to change the password to the bash exploit. From klaipedaville at gmail.com Fri Sep 26 11:35:15 2014 From: klaipedaville at gmail.com (Klaipedaville on Google) Date: Fri, 26 Sep 2014 14:35:15 +0300 Subject: Dovecot Sieve and Postfix header_checks Issue Message-ID: Hello List, I tried to subscribe but it's taking forever for the confirmation email to arrive so I thought I would ask away by emailing directly. My apologies in advance should this question appear twice. It may seem real simple to experts but I cannot really figure it out. I'll try to be concise: Dovecot version is 2.1.7. Its dovecot ?n is real short one and follows right after my question. I have my Postfix 2.9.6 properties set like this: header_checks = /etc/path/to/myfile. Then I have Dovecot Sieve also configured and working fine. Now the trouble is that these two cannot be combined together can they? Dovecot Sieve and Postfix's header_checks? If I turn off header_checks in Postfix then Dovecot Sieve is working fine. If I vise versa turn off Dovecot Sieve then Postfix's header-checks are also working fine. However, when I keep them both turned on it also works but only partially and in this case Dovecot Sieve never bounces back any rejected massages remotely, the bounce happens only locally. That is I can see it in my logs that it was rejected locally but the message is never sent back to the sender saying something like, "Spam is rejected here". Thus the reject turns into a silent discard without telling the sender anything at all. Any ideas, help, advices how do I fix that? Would be really grateful for any suggestions / assistance at all. Many thanks in advance! P.S. I would like to use both because Dovecot Sieve is a very powerful and great plugin that uses Spamassassin's added tags and headers based on which I create my rules. Postfix in its turn has a very neat feature of checking the headers via regexp but Postfix does not see / detect Spamassassin's added headers at all because I passed delivery and authentication (which is a way better than Postfix's) to dovecot deliver. # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.6 ext4 auth_mechanisms = plain login cram-md5 scram-sha-1 auth_verbose = yes hostname = WindTalker info_log_path = /var/log/dovecot-sieve.log log_path = /var/log/dovecot-sieve-errors.log mail_location = maildir:/home/mvail/%d/%n 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 passdb { args = /etc/dovecot/passwd driver = passwd-file } plugin { sieve = ~/.dovecot.sieve sieve_default = /etc/dovecot/default.sieve sieve_dir = ~/sieve } pop3_uidl_format = %g postmaster_address = postmaster at example.com protocols = imap pop3 sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } ssl_ca = References: Message-ID: <54255249.70707@integrafin.co.uk> That would most likely be something in your header_checks that is causing the bounce from Sieve to be rejected. There is no reason why you cannot use both. On 26/09/14 12:35, Klaipedaville on Google wrote: > Hello List, > > I tried to subscribe but it's taking forever for the confirmation email to arrive so I thought I would ask away by emailing directly. My apologies in advance should this question appear twice. > > It may seem real simple to experts but I cannot really figure it out. I'll try to be concise: > > Dovecot version is 2.1.7. Its dovecot ?n is real short one and follows right after my question. > > I have my Postfix 2.9.6 properties set like this: header_checks = /etc/path/to/myfile. Then I have Dovecot Sieve also configured and working fine. > > Now the trouble is that these two cannot be combined together can they? Dovecot Sieve and Postfix's header_checks? If I turn off header_checks in Postfix then Dovecot Sieve is working fine. If I vise versa turn off Dovecot Sieve then Postfix's header-checks are also working fine. However, when I keep them both turned on it also works but only partially and in this case Dovecot Sieve never bounces back any rejected massages remotely, the bounce happens only locally. That is I can see it in my logs that it was rejected locally but the message is never sent back to the sender saying something like, "Spam is rejected here". Thus the reject turns into a silent discard without telling the sender anything at all. Any ideas, help, advices how do I fix that? Would be really grateful for any suggestions / assistance at all. Many thanks in advance! > > P.S. I would like to use both because Dovecot Sieve is a very powerful and great plugin that uses Spamassassin's added tags and headers based on which I create my rules. Postfix in its turn has a very neat feature of checking the headers via regexp but Postfix does not see / detect Spamassassin's added headers at all because I passed delivery and authentication (which is a way better than Postfix's) to dovecot deliver. > > # 2.1.7: /etc/dovecot/dovecot.conf > # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.6 ext4 > auth_mechanisms = plain login cram-md5 scram-sha-1 > auth_verbose = yes > hostname = WindTalker > info_log_path = /var/log/dovecot-sieve.log > log_path = /var/log/dovecot-sieve-errors.log > mail_location = maildir:/home/mvail/%d/%n > 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 > passdb { > args = /etc/dovecot/passwd > driver = passwd-file > } > plugin { > sieve = ~/.dovecot.sieve > sieve_default = /etc/dovecot/default.sieve > sieve_dir = ~/sieve > } > pop3_uidl_format = %g > postmaster_address = postmaster at example.com > protocols = imap pop3 sieve > service auth { > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0660 > user = postfix > } > } > ssl_ca = ssl_cert = ssl_key = userdb { > args = uid=vmail gid=vmail home=/home/vmail/%u > driver = static > } > protocol lda { > mail_debug = yes > mail_plugins = sieve > } > > Regards, > Dennis. > -- This message is intended only for the addressee and may contain confidential information. Unless you are that person, you may not disclose its contents or use it in any way and are requested to delete the message along with any attachments and notify us immediately. "Transact" is operated by Integrated Financial Arrangements plc. 29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300. (Registered office: as above; Registered in England and Wales under number: 3727592). Authorised and regulated by the Financial Conduct Authority (entered on the Financial Services Register; no. 190856). From klaipedaville at gmail.com Fri Sep 26 12:00:28 2014 From: klaipedaville at gmail.com (Klaipedaville on Google) Date: Fri, 26 Sep 2014 15:00:28 +0300 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <54255249.70707@integrafin.co.uk> References: <54255249.70707@integrafin.co.uk> Message-ID: <23D946DB1F134A2CB613C8F8E22144BC@Computer> Thank you for your suggestion, Alex. However, my header_checks file has just 5 lines of regexp as follows: /^Subject:.**{5}SPAM*{5}/ REJECT No spammers allowed here. /^Subject:.*\*\*\*\*\*SPAM\*\*\*\*\*/ REJECT No spammers allowed. /\s**{5}SPAM*{5}/ REJECT No spamming hullababballos allowed. /^Subject:(.*)SPAM/ REJECT Spam is not allowed. DISCARD. /^From:.*\@.*\.tw/ REJECT Sorry, Taiwanese mail is not allowed. All the regexp are correct. The first and the third lines actually do the same thing and they are there for testing purposes only. Execution stops at the very first rule matched so there is no problem in having any rules repeated. I can't see how a few the most simplest regular expressions can cause the bounce from Sieve not to go through.. Do you see any problems in these lines above that could possibly be the cause of your suggestion? From: Alex Crow Sent: Friday, September 26, 2014 14:47 To: dovecot at dovecot.org Subject: Re: Dovecot Sieve and Postfix header_checks Issue That would most likely be something in your header_checks that is causing the bounce from Sieve to be rejected. There is no reason why you cannot use both. On 26/09/14 12:35, Klaipedaville on Google wrote: > Hello List, > > I tried to subscribe but it's taking forever for the confirmation email to arrive so I thought I would ask away by emailing directly. My apologies in advance should this question appear twice. > > It may seem real simple to experts but I cannot really figure it out. I'll try to be concise: > > Dovecot version is 2.1.7. Its dovecot ?n is real short one and follows right after my question. > > I have my Postfix 2.9.6 properties set like this: header_checks = /etc/path/to/myfile. Then I have Dovecot Sieve also configured and working fine. > > Now the trouble is that these two cannot be combined together can they? Dovecot Sieve and Postfix's header_checks? If I turn off header_checks in Postfix then Dovecot Sieve is working fine. If I vise versa turn off Dovecot Sieve then Postfix's header-checks are also working fine. However, when I keep them both turned on it also works but only partially and in this case Dovecot Sieve never bounces back any rejected massages remotely, the bounce happens only locally. That is I can see it in my logs that it was rejected locally but the message is never sent back to the sender saying something like, "Spam is rejected here". Thus the reject turns into a silent discard without telling the sender anything at all. Any ideas, help, advices how do I fix that? Would be really grateful for any suggestions / assistance at all. Many thanks in advance! > > P.S. I would like to use both because Dovecot Sieve is a very powerful and great plugin that uses Spamassassin's added tags and headers based on which I create my rules. Postfix in its turn has a very neat feature of checking the headers via regexp but Postfix does not see / detect Spamassassin's added headers at all because I passed delivery and authentication (which is a way better than Postfix's) to dovecot deliver. > > # 2.1.7: /etc/dovecot/dovecot.conf > # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.6 ext4 > auth_mechanisms = plain login cram-md5 scram-sha-1 > auth_verbose = yes > hostname = WindTalker > info_log_path = /var/log/dovecot-sieve.log > log_path = /var/log/dovecot-sieve-errors.log > mail_location = maildir:/home/mvail/%d/%n > 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 > passdb { > args = /etc/dovecot/passwd > driver = passwd-file > } > plugin { > sieve = ~/.dovecot.sieve > sieve_default = /etc/dovecot/default.sieve > sieve_dir = ~/sieve > } > pop3_uidl_format = %g > postmaster_address = postmaster at example.com > protocols = imap pop3 sieve > service auth { > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0660 > user = postfix > } > } > ssl_ca = ssl_cert = ssl_key = userdb { > args = uid=vmail gid=vmail home=/home/vmail/%u > driver = static > } > protocol lda { > mail_debug = yes > mail_plugins = sieve > } > > Regards, > Dennis. > -- This message is intended only for the addressee and may contain confidential information. Unless you are that person, you may not disclose its contents or use it in any way and are requested to delete the message along with any attachments and notify us immediately. "Transact" is operated by Integrated Financial Arrangements plc. 29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300. (Registered office: as above; Registered in England and Wales under number: 3727592). Authorised and regulated by the Financial Conduct Authority (entered on the Financial Services Register; no. 190856). From dovecot at luftivennad.com Fri Sep 26 12:22:04 2014 From: dovecot at luftivennad.com (Ain) Date: Fri, 26 Sep 2014 15:22:04 +0300 Subject: Namespace configuration over SQL In-Reply-To: <09216e6a38304bff56c4d4e71f0adddc.squirrel@webmail.equix.ee> References: <09216e6a38304bff56c4d4e71f0adddc.squirrel@webmail.equix.ee> Message-ID: <65939c762a2101663d7bdbbfcf1120d3.squirrel@webmail.equix.ee> I tried few different dovecot versions. 2.1.16 is working, 2.2.2 is broken. Because I use FreeBSD, in-between versions aren't available (I can use source of course, but ports tree don't include them). Probably some bigger change from 2.1 to 2.2 is affecting SQL output handling, any fix or workaround? Thanks in advance! > Hello! > > I had working setup, where namespace settings (including prefix) was > queried over SQL. Now, after installing new Dovecot to new server (using > same configuration), this is not working anymore. > > Log shows following error: > > """ > Initialization failed: namespace configuration error: list=yes requires > prefix=yes to end with separator > """ > > relevant part from dovecot-sql.conf.ext: > """ > user_query = \ > SELECT \ > 1002 AS uid \ > , 1003 AS gid \ > , CONCAT('/www/home/vmail/domains/', SUBSTRING(d.name, 1, > 1), '/', d.name, '/', u.username) AS home \ > , namespace_prefix AS 'namespace/default/prefix' \ > , 'yes' AS 'namespace/default/inbox' \ > , '%s' AS 'mail_service' \ > FROM vm_domain d \ > INNER JOIN vm_user u ON u.vm_domain_id = d.id \ > WHERE d.name = '%d' AND u.username = '%n' AND u.active = 1 AND > d.active = 1 > """ > > namespace_prefix can be empty or INBOX. > > doveconf -n output: > """ > # 2.2.13: /usr/local/etc/dovecot/dovecot.conf > # OS: FreeBSD 9.3-RELEASE amd64 > auth_debug = yes > auth_verbose = yes > disable_plaintext_auth = no > listen = * > mail_debug = yes > mail_location = maildir:~/Maildir > mmap_disable = yes > namespace default { > inbox = yes > list = yes > location = > prefix = > separator = . > type = private > } > passdb { > args = /usr/local/etc/dovecot/dovecot-sql.conf.ext > driver = sql > } > plugin { > mail_log_events = delete undelete expunge copy mailbox_delete > mailbox_rename flag_change append > mail_log_fields = uid box msgid size > mail_log_group_events = no > } > service imap { > process_limit = 1480 > } > ssl_cert = ssl_key = userdb { > args = /usr/local/etc/dovecot/dovecot-sql.conf.ext > driver = sql > } > verbose_proctitle = yes > protocol imap { > imap_capability = IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE > IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS > THREAD=ORDEREDSUBJECT MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS > LIST-EXTENDED I18NLEVEL=1 ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH > LIST-STATUS SPECIAL-USE > mail_max_userip_connections = 900 > } > protocol pop3 { > mail_max_userip_connections = 300 > } > """ > > Seems like "prefix = " is interpreted as "prefix = yes". > > How I can solve this? > From skdovecot at smail.inf.fh-brs.de Fri Sep 26 13:01:36 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Fri, 26 Sep 2014 15:01:36 +0200 (CEST) Subject: Namespace configuration over SQL In-Reply-To: <09216e6a38304bff56c4d4e71f0adddc.squirrel@webmail.equix.ee> References: <09216e6a38304bff56c4d4e71f0adddc.squirrel@webmail.equix.ee> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 25 Sep 2014, Ain wrote: > I had working setup, where namespace settings (including prefix) was > queried over SQL. Now, after installing new Dovecot to new server (using > same configuration), this is not working anymore. > > Log shows following error: > > """ > Initialization failed: namespace configuration error: list=yes requires > prefix=yes to end with separator > """ > > relevant part from dovecot-sql.conf.ext: > """ > user_query = \ > SELECT \ > 1002 AS uid \ > , 1003 AS gid \ > , CONCAT('/www/home/vmail/domains/', SUBSTRING(d.name, 1, > 1), '/', d.name, '/', u.username) AS home \ > , namespace_prefix AS 'namespace/default/prefix' \ > , 'yes' AS 'namespace/default/inbox' \ > , '%s' AS 'mail_service' \ > FROM vm_domain d \ > INNER JOIN vm_user u ON u.vm_domain_id = d.id \ > WHERE d.name = '%d' AND u.username = '%n' AND u.active = 1 AND > d.active = 1 > """ what do you return as namespace_prefix, NULL vs. '' ? Could you try the other value? > namespace default { > inbox = yes > list = yes > prefix = > separator = . > type = private > } - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBVCVjsXz1H7kL/d9rAQL9GggAuK7ad919SVY/7YV0EDEtiZW6psgHclqs P/oI5o6ycX2C/MkREo9QeDuo68S12jt7H4fvewJ+MgVkUS7FtO8KUeKj5QD6FzKZ bi5mDwnamO8+4fgmO74iGPv2u1pp2E+SS8wPreiVxyZWU/zcM4BrlMJf0JFVk+f7 f5CGrM91hCjWAFr8WSpYlb1m9gY4RG3crogs9c2kntmDY2kwEHcsDvElwf6rwGHk VW1mjxdLUY3wgXXSr8OBEvmWYBIIpTu8XHf3nOh5STbZXRMkdSRWPkftKTzPTmH4 13/xsKzmG6zWuwYHdROinXfCg/hmFg1l+6zsqU/jMAlDiAV6S3B71A== =6ewJ -----END PGP SIGNATURE----- From klaipedaville at gmail.com Fri Sep 26 13:10:40 2014 From: klaipedaville at gmail.com (Klaipedaville on Google) Date: Fri, 26 Sep 2014 16:10:40 +0300 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <23D946DB1F134A2CB613C8F8E22144BC@Computer> References: <54255249.70707@integrafin.co.uk> <23D946DB1F134A2CB613C8F8E22144BC@Computer> Message-ID: <99622F1A0F1241308D93744D9E12D5EF@Computer> Hey! You are right Alex! Many thanks for pointing me to head over to the right direction! It was a clash on rules for some reason. Now, I was also right that these two systems could not be used together because the rules declared in different systems to perform the same action (REJECT) cause the error I was having! The following rule in default.sieve: require ["reject"]; # rule: Reject on "x-spam-flag" header if header :contains "X-Spam-Flag" "YES" { reject "No spamming allowed here."; stop; } and the following Postfix's regexp header_check rules on the subject field: /^Subject:.**{5}SPAM*{5}/ REJECT No spammers allowed here. /^Subject:.*\*\*\*\*\*SPAM\*\*\*\*\*/ REJECT No spammers allowed. /\s**{5}SPAM*{5}/ REJECT No spamming hullababballos allowed. /^Subject:(.*)SPAM/ REJECT Spam is not allowed. DISCARD. were causing the Dovecot Sieve rejection bounce not to go through. The rules blocked the spam all right but rejection was turned into discard for some reason. Now the question is how do I find out which regular expressions will be in conflict with default.sieve scripting rules? Default.sieve is set to block spam on the X-Spam-Flag header and header_checks is set to block spam on the subject field. I am still clueless why didn't these two "cooperate"? Was it just because they were "told" to perform the same action as per my previous guess? But the target to perform this same action on was different... Any more ideas anyone? Alex? Many thanks in advance for any input! From: Klaipedaville on Google Sent: Friday, September 26, 2014 15:00 To: Alex Crow ; dovecot at dovecot.org Subject: Re: Dovecot Sieve and Postfix header_checks Issue Thank you for your suggestion, Alex. However, my header_checks file has just 5 lines of regexp as follows: /^Subject:.**{5}SPAM*{5}/ REJECT No spammers allowed here. /^Subject:.*\*\*\*\*\*SPAM\*\*\*\*\*/ REJECT No spammers allowed. /\s**{5}SPAM*{5}/ REJECT No spamming hullababballos allowed. /^Subject:(.*)SPAM/ REJECT Spam is not allowed. DISCARD. /^From:.*\@.*\.tw/ REJECT Sorry, Taiwanese mail is not allowed. All the regexp are correct. The first and the third lines actually do the same thing and they are there for testing purposes only. Execution stops at the very first rule matched so there is no problem in having any rules repeated. I can't see how a few the most simplest regular expressions can cause the bounce from Sieve not to go through.. Do you see any problems in these lines above that could possibly be the cause of your suggestion? From: Alex Crow Sent: Friday, September 26, 2014 14:47 To: dovecot at dovecot.org Subject: Re: Dovecot Sieve and Postfix header_checks Issue That would most likely be something in your header_checks that is causing the bounce from Sieve to be rejected. There is no reason why you cannot use both. On 26/09/14 12:35, Klaipedaville on Google wrote: > Hello List, > > I tried to subscribe but it's taking forever for the confirmation email to arrive so I thought I would ask away by emailing directly. My apologies in advance should this question appear twice. > > It may seem real simple to experts but I cannot really figure it out. I'll try to be concise: > > Dovecot version is 2.1.7. Its dovecot ?n is real short one and follows right after my question. > > I have my Postfix 2.9.6 properties set like this: header_checks = /etc/path/to/myfile. Then I have Dovecot Sieve also configured and working fine. > > Now the trouble is that these two cannot be combined together can they? Dovecot Sieve and Postfix's header_checks? If I turn off header_checks in Postfix then Dovecot Sieve is working fine. If I vise versa turn off Dovecot Sieve then Postfix's header-checks are also working fine. However, when I keep them both turned on it also works but only partially and in this case Dovecot Sieve never bounces back any rejected massages remotely, the bounce happens only locally. That is I can see it in my logs that it was rejected locally but the message is never sent back to the sender saying something like, "Spam is rejected here". Thus the reject turns into a silent discard without telling the sender anything at all. Any ideas, help, advices how do I fix that? Would be really grateful for any suggestions / assistance at all. Many thanks in advance! > > P.S. I would like to use both because Dovecot Sieve is a very powerful and great plugin that uses Spamassassin's added tags and headers based on which I create my rules. Postfix in its turn has a very neat feature of checking the headers via regexp but Postfix does not see / detect Spamassassin's added headers at all because I passed delivery and authentication (which is a way better than Postfix's) to dovecot deliver. > > # 2.1.7: /etc/dovecot/dovecot.conf > # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.6 ext4 > auth_mechanisms = plain login cram-md5 scram-sha-1 > auth_verbose = yes > hostname = WindTalker > info_log_path = /var/log/dovecot-sieve.log > log_path = /var/log/dovecot-sieve-errors.log > mail_location = maildir:/home/mvail/%d/%n > 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 > passdb { > args = /etc/dovecot/passwd > driver = passwd-file > } > plugin { > sieve = ~/.dovecot.sieve > sieve_default = /etc/dovecot/default.sieve > sieve_dir = ~/sieve > } > pop3_uidl_format = %g > postmaster_address = postmaster at example.com > protocols = imap pop3 sieve > service auth { > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0660 > user = postfix > } > } > ssl_ca = ssl_cert = ssl_key = userdb { > args = uid=vmail gid=vmail home=/home/vmail/%u > driver = static > } > protocol lda { > mail_debug = yes > mail_plugins = sieve > } > > Regards, > Dennis. > -- This message is intended only for the addressee and may contain confidential information. Unless you are that person, you may not disclose its contents or use it in any way and are requested to delete the message along with any attachments and notify us immediately. "Transact" is operated by Integrated Financial Arrangements plc. 29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300. (Registered office: as above; Registered in England and Wales under number: 3727592). Authorised and regulated by the Financial Conduct Authority (entered on the Financial Services Register; no. 190856). From dovecot at luftivennad.com Fri Sep 26 13:21:09 2014 From: dovecot at luftivennad.com (Ain) Date: Fri, 26 Sep 2014 16:21:09 +0300 Subject: Namespace configuration over SQL In-Reply-To: References: <09216e6a38304bff56c4d4e71f0adddc.squirrel@webmail.equix.ee> Message-ID: <5161284e45ed053d53243fb907a496e6.squirrel@webmail.equix.ee> Thanks for reply! Answer below: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thu, 25 Sep 2014, Ain wrote: > >> I had working setup, where namespace settings (including prefix) was >> queried over SQL. Now, after installing new Dovecot to new server (using >> same configuration), this is not working anymore. >> >> Log shows following error: >> >> """ >> Initialization failed: namespace configuration error: list=yes requires >> prefix=yes to end with separator >> """ >> >> relevant part from dovecot-sql.conf.ext: >> """ >> user_query = \ >> SELECT \ >> 1002 AS uid \ >> , 1003 AS gid \ >> , CONCAT('/www/home/vmail/domains/', SUBSTRING(d.name, 1, >> 1), '/', d.name, '/', u.username) AS home \ >> , namespace_prefix AS 'namespace/default/prefix' \ >> , 'yes' AS 'namespace/default/inbox' \ >> , '%s' AS 'mail_service' \ >> FROM vm_domain d \ >> INNER JOIN vm_user u ON u.vm_domain_id = d.id \ >> WHERE d.name = '%d' AND u.username = '%n' AND u.active = 1 AND >> d.active = 1 >> """ > > what do you return as namespace_prefix, NULL vs. '' ? Could you try the > other value? > Empty string, so "". I have even changed this experimentally to this: """ user_query = \ SELECT \ 1002 AS uid \ , 1002 AS gid \ , CONCAT('/www/home/vmail/domains/', SUBSTRING(d.name, 1, 1), '/', d.name, '/', u.username) AS home \ , IF(namespace_prefix="", "", namespace_prefix ) AS 'namespace/default/prefix' \ , 'yes' AS 'namespace/default/inbox' \ , '%s' AS 'mail_service' \ FROM vm_domain d \ INNER JOIN vm_user u ON u.vm_domain_id = d.id \ WHERE d.name = '%d' AND u.username = '%n' AND u.active = 1 AND d.active = 1 """ Result is same, error from log: """ Sep 26 15:12:25 server dovecot: imap(test at foo.local): Error: user test at foo.local: Initialization failed: namespace configuration error: list=yes requires prefix=yes to end with separator Sep 26 15:12:25 server dovecot: imap(test at foo.local): Error: Invalid user settings. Refer to server log for more information. """ With NULL in DB (and using first query version of course) error is same, like above. Thanks! Ain From dovecot at luftivennad.com Fri Sep 26 13:31:36 2014 From: dovecot at luftivennad.com (Ain) Date: Fri, 26 Sep 2014 16:31:36 +0300 Subject: Namespace configuration over SQL In-Reply-To: References: <09216e6a38304bff56c4d4e71f0adddc.squirrel@webmail.equix.ee> Message-ID: <2ed5f4fc8e639556853f312630640ddb.squirrel@webmail.equix.ee> Sorry, using NULL indeed works correctly. My previous test with NULL was little bit flawed. Thanks for help! Ain > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thu, 25 Sep 2014, Ain wrote: > >> I had working setup, where namespace settings (including prefix) was >> queried over SQL. Now, after installing new Dovecot to new server (using >> same configuration), this is not working anymore. >> >> Log shows following error: >> >> """ >> Initialization failed: namespace configuration error: list=yes requires >> prefix=yes to end with separator >> """ >> >> relevant part from dovecot-sql.conf.ext: >> """ >> user_query = \ >> SELECT \ >> 1002 AS uid \ >> , 1003 AS gid \ >> , CONCAT('/www/home/vmail/domains/', SUBSTRING(d.name, 1, >> 1), '/', d.name, '/', u.username) AS home \ >> , namespace_prefix AS 'namespace/default/prefix' \ >> , 'yes' AS 'namespace/default/inbox' \ >> , '%s' AS 'mail_service' \ >> FROM vm_domain d \ >> INNER JOIN vm_user u ON u.vm_domain_id = d.id \ >> WHERE d.name = '%d' AND u.username = '%n' AND u.active = 1 AND >> d.active = 1 >> """ > > what do you return as namespace_prefix, NULL vs. '' ? Could you try the > other value? > >> namespace default { >> inbox = yes >> list = yes >> prefix = >> separator = . >> type = private >> } > > - -- > Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBVCVjsXz1H7kL/d9rAQL9GggAuK7ad919SVY/7YV0EDEtiZW6psgHclqs > P/oI5o6ycX2C/MkREo9QeDuo68S12jt7H4fvewJ+MgVkUS7FtO8KUeKj5QD6FzKZ > bi5mDwnamO8+4fgmO74iGPv2u1pp2E+SS8wPreiVxyZWU/zcM4BrlMJf0JFVk+f7 > f5CGrM91hCjWAFr8WSpYlb1m9gY4RG3crogs9c2kntmDY2kwEHcsDvElwf6rwGHk > VW1mjxdLUY3wgXXSr8OBEvmWYBIIpTu8XHf3nOh5STbZXRMkdSRWPkftKTzPTmH4 > 13/xsKzmG6zWuwYHdROinXfCg/hmFg1l+6zsqU/jMAlDiAV6S3B71A== > =6ewJ > -----END PGP SIGNATURE----- > From acrow at integrafin.co.uk Fri Sep 26 13:34:54 2014 From: acrow at integrafin.co.uk (Alex Crow) Date: Fri, 26 Sep 2014 14:34:54 +0100 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <99622F1A0F1241308D93744D9E12D5EF@Computer> References: <54255249.70707@integrafin.co.uk> <23D946DB1F134A2CB613C8F8E22144BC@Computer> <99622F1A0F1241308D93744D9E12D5EF@Computer> Message-ID: <54256B7E.6060703@integrafin.co.uk> On 26/09/14 14:10, Klaipedaville on Google wrote: > Hey! You are right Alex! Many thanks for pointing me to head over to > the right direction! > It was a clash on rules for some reason. Now, I was also right that > these two systems could not be used together because the rules > declared in different systems to perform the same action (REJECT) > cause the error I was having! > The following rule in default.sieve: > require ["reject"]; > # rule: Reject on "x-spam-flag" header > if header :contains "X-Spam-Flag" "YES" { > reject "No spamming allowed here."; > stop; > } > and the following Postfix's regexp header_check rules on the subject > field: > /^Subject:.**{5}SPAM*{5}/ REJECT No spammers allowed here. > /^Subject:.*\*\*\*\*\*SPAM\*\*\*\*\*/ REJECT No spammers allowed. > /\s**{5}SPAM*{5}/ REJECT No spamming > hullababballos allowed. I think it may be this one above. From the postfix manuals: "By default, matching is case-insensitive, and newlines are not treated as special characters. The behavior is controlled by flags, which are toggled by appending one or more of the following characters after the pattern: *i* (default: on) Toggles the case sensitivity flag. By default, matching is case insensitive." And it looks like * needs escaping there too (if you're trying to match exactly 5 asterisks, you should probably do "\*{5}" not just *{5}. > /^Subject:(.*)SPAM/ REJECT Spam is not allowed. > DISCARD. > were causing the Dovecot Sieve rejection bounce not to go through. The > rules blocked the spam all right but rejection was turned into discard > for some reason. > Now the question is how do I find out which regular expressions will > be in conflict with default.sieve scripting rules? That's just about learning Posix Regex syntax. > Default.sieve is set to block spam on the X-Spam-Flag header and > header_checks is set to block spam on the subject field. I am still > clueless why didn't these two "cooperate"? Was it just because they > were "told" to perform the same action as per my previous guess? I'm almost 100% sure that that regex also matched the bounce from your sieve rules. There is no mysterious interaction between header_checks and sieve rules, it's just your pattern was too liberal in the former. > But the target to perform this same action on was different... Any > more ideas anyone? Alex? Many thanks in advance for any input! I think if you tune that header_checks file correctly you should have no more issues. Thanks Alex -- This message is intended only for the addressee and may contain confidential information. Unless you are that person, you may not disclose its contents or use it in any way and are requested to delete the message along with any attachments and notify us immediately. "Transact" is operated by Integrated Financial Arrangements plc. 29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300. (Registered office: as above; Registered in England and Wales under number: 3727592). Authorised and regulated by the Financial Conduct Authority (entered on the Financial Services Register; no. 190856). From skdovecot at smail.inf.fh-brs.de Fri Sep 26 14:19:10 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Fri, 26 Sep 2014 16:19:10 +0200 (CEST) Subject: Problem to override setting with empty string via userdb In-Reply-To: <2ed5f4fc8e639556853f312630640ddb.squirrel@webmail.equix.ee> References: <09216e6a38304bff56c4d4e71f0adddc.squirrel@webmail.equix.ee> <2ed5f4fc8e639556853f312630640ddb.squirrel@webmail.equix.ee> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Fri, 26 Sep 2014, Ain wrote: There seems to be no way, in order to override a non-empty namespace/default/prefix with an empty value. My test system is Dovecot v2.2.13 (35c3194900b7), the current hg version. See below for an example with SQL. Returning an empty string '' using SQL results into namespace/default/prefix=yes, the boolean string "yes" does replace the empty string returned by SQL. Using a NULL value, you can work around this, but in this the default value must be empty. The applies to LDAP as well, I assume. It definitly applies to userdb_import returned by LDAP, too: http://wiki2.dovecot.org/UserDatabase/ExtraFields?highlight=%28userdb_import%29 The string: namespace/default/prefix=namespace/inbox/prefix sets both namespace/default/prefix and namespace/inbox/prefix to 'yes'. The '=' does not matter. ==== > Sorry, using NULL indeed works correctly. My previous test with NULL was > little bit flawed. > >> On Thu, 25 Sep 2014, Ain wrote: >> >>> I had working setup, where namespace settings (including prefix) was >>> queried over SQL. Now, after installing new Dovecot to new server (using >>> same configuration), this is not working anymore. >>> >>> Log shows following error: >>> >>> """ >>> Initialization failed: namespace configuration error: list=yes requires >>> prefix=yes to end with separator >>> """ >>> >>> relevant part from dovecot-sql.conf.ext: >>> """ >>> user_query = \ >>> SELECT \ >>> 1002 AS uid \ >>> , 1003 AS gid \ >>> , CONCAT('/www/home/vmail/domains/', SUBSTRING(d.name, 1, >>> 1), '/', d.name, '/', u.username) AS home \ >>> , namespace_prefix AS 'namespace/default/prefix' \ >>> , 'yes' AS 'namespace/default/inbox' \ >>> , '%s' AS 'mail_service' \ >>> FROM vm_domain d \ >>> INNER JOIN vm_user u ON u.vm_domain_id = d.id \ >>> WHERE d.name = '%d' AND u.username = '%n' AND u.active = 1 AND >>> d.active = 1 >>> """ >> >> what do you return as namespace_prefix, NULL vs. '' ? Could you try the >> other value? - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBVCV13nz1H7kL/d9rAQLOUwgAneROV2VCx6kbckPo5+pP5VBh2CX6ns7B WD0QVb4/DdP+VcsGCYsKrNmrRA7UA+QMRzjEmpPD4M6UonhfzyrjfatUeTHvQFxC I96+9EPNImCSEujfEp7IvH/S9jebfxYCv23XbY4OQniw+CYHDqVucQ9uV/AEaAe2 OEBJwxP+RPnlVNxo4A9Pt4/GOpNcViCu8FeP74MoyGLyHpWrCqNocse8P1tKRSni gYTB7q2i29UhUfF/WFaaK1pR7sLG0TT1QJ0ZCOLtQMfQPQd8fPwRuxodCsVUDSU4 +IOzWFwQZU7LszSNN4mKetY/jMwW45eVggTIU0ThMuGP8kf4AQWD5w== =L1Qz -----END PGP SIGNATURE----- From klaipedaville at gmail.com Fri Sep 26 14:27:25 2014 From: klaipedaville at gmail.com (Klaipedaville on Google) Date: Fri, 26 Sep 2014 17:27:25 +0300 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <54256B7E.6060703@integrafin.co.uk> References: <54255249.70707@integrafin.co.uk><23D946DB1F134A2CB613C8F8E22144BC@Computer><99622F1A0F1241308D93744D9E12D5EF@Computer> <54256B7E.6060703@integrafin.co.uk> Message-ID: <7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer> > /^Subject:.**{5}SPAM*{5}/ REJECT No spammers allowed here. > /^Subject:.*\*\*\*\*\*SPAM\*\*\*\*\*/ REJECT No spammers allowed. > /\s**{5}SPAM*{5}/ REJECT No spamming > hullababballos allowed. >I think it may be this one above. From the postfix manuals"By default, matching is case-insensitive, and newlines are not treated as special characters. The behavior is controlled by flags, which are toggled by appending one or more of the following characters after the pattern: *i* (default: on) Toggles the case sensitivity flag. By default, matching is case insensitive." Case insensitive is declared by putting this /i at the end of a rule. Postfix has nothing to do with regular expressions (regexp) and regexp is not controlled by postfix. There should be a regexp library available on the server where you are using regexp. It?s like PHP, or tml, or js, or css, it cannot be controlled by postfix. >And it looks like * needs escaping there too (if you're trying to match exactly 5 asterisks, you should probably do "\*{5}" not just *{5}. Yes, the escape character in front \*{5} to match 5 asterisks is the correct one. You are right. I am an expert on regexp and this (incorrect one) was there just for testing purposes because there was a problem with the library on the server so I had this bad rule over there to follow up on error in logs. The library has been fixed by now and as I said earlier execution stops on the first rule matched but does not really do any harm if there is a mistake in the rule, in this 'mistake' case the rule is simply skipped. > /^Subject:(.*)SPAM/ REJECT Spam is not allowed. DISCARD. > were causing the Dovecot Sieve rejection bounce not to go through. The rules blocked the spam all right but rejection was turned into discard for some reason. Now the question is how do I find out which regular >expressions will be in conflict with default.sieve scripting rules? >That's just about learning Posix Regex syntax. All the rules are 100% correct as there is a very simple and useful tool in postfix to check if regexp is correct. The tool can be used even by people who don't have a foggiest idea how regexp work. All you have to do is to type on a command line this postmap -q "Subject: *****SPAM***** blablablabla" regexp:/etc/postfix/header_checks or this postmap -q "X-Spam-Flag: YES" regexp:/etc/postfix/header_checks and it will tell you if your rule is correct or not. It is bullet and fool proof system with 100% guarantee. All these rules have been checked like that despite the fact that I know for a fact that they are correct by my own knowledge and experience. >I'm almost 100% sure that that regex also matched the bounce from your sieve rules. There is no mysterious interaction between header_checks and sieve rules, it's just your pattern was too liberal in the former. No, no. The regex could not have matched the bounce from my own rules because it would be silly to send a test message from the same server that would loop back and block myself by my own rules. I sent test messages from another server's accounts. Plus, there is a difference. Header_checks in Postfix use only customized rules that do not involve any Spamassassin's added headers. Now in my case only Dovecot Sieve goes through Spamassassin headers because as mentioned earlier I passed delivery from Postfix to dovecot LDA in my configuration. That's why everything that has Spamassassin's headers and tags added has to be configured via default.sieve scripting and everything else (that do not get Spamassassin's headers added) may use header_checks of Postfix. I have just figured that out by runnning quite a few different and simple tests. >I think if you tune that header_checks file correctly you should have no more issues. The header_check rules are fine tuned to their best. Anyway, I am thankful for your suggestion as it pointed me to the right direction. Then I picked it up and simply followed onwards by elaborating and building on top which led me to a solved problem Thank you. -------------- next part -------------- A non-text attachment was scrubbed... Name: wlEmoticon-openmouthedsmile[1].png Type: image/png Size: 1053 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: wlEmoticon-smile[1].png Type: image/png Size: 1046 bytes Desc: not available URL: From acrow at integrafin.co.uk Fri Sep 26 14:49:25 2014 From: acrow at integrafin.co.uk (Alex Crow) Date: Fri, 26 Sep 2014 15:49:25 +0100 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer> References: <54255249.70707@integrafin.co.uk><23D946DB1F134A2CB613C8F8E22144BC@Computer><99622F1A0F1241308D93744D9E12D5EF@Computer> <54256B7E.6060703@integrafin.co.uk> <7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer> Message-ID: <54257CF5.8060404@integrafin.co.uk> On 26/09/14 15:27, Klaipedaville on Google wrote: >> /^Subject:.**{5}SPAM*{5}/ REJECT No spammers allowed here. >> /^Subject:.*\*\*\*\*\*SPAM\*\*\*\*\*/ REJECT No spammers allowed. >> /\s**{5}SPAM*{5}/ REJECT No spamming >> hullababballos allowed. >> I think it may be this one above. From the postfix manuals"By default, matching is case-insensitive, and newlines are not treated as special characters. The behavior is controlled by flags, which are toggled by appending one or more of the following characters after the pattern: *i* (default: on) Toggles the case sensitivity flag. By default, matching is case insensitive." > Case insensitive is declared by putting this /i at the end of a rule. > Postfix has nothing to do with regular expressions (regexp) and regexp is not controlled by postfix. There should be a regexp library available on the server where you are using regexp. It?s like PHP, or tml, or js, or css, it cannot be controlled by postfix. So why does it state in man 5 regexp_table that such tables are *case insensitive* by default and the /i actually toggles that? Are you saying that man page is wrong? I'd be surprised as I don't think I've yet come across an occasion where postfix man pages are incorrect! > >> And it looks like * needs escaping there too (if you're trying to match exactly 5 asterisks, you should probably do "\*{5}" not just *{5}. > Yes, the escape character in front \*{5} to match 5 asterisks is the correct one. You are right. I am an expert on regexp and this (incorrect one) was there just for testing purposes because there was a problem with the library on the server so I had this bad rule over there to follow up on error in logs. The library has been fixed by now and as I said earlier execution stops on the first rule matched but does not really do any harm if there is a mistake in the rule, in this 'mistake' case the rule is simply skipped. > >> /^Subject:(.*)SPAM/ REJECT Spam is not allowed. DISCARD. >> were causing the Dovecot Sieve rejection bounce not to go through. The rules blocked the spam all right but rejection was turned into discard for some reason. Now the question is how do I find out which regular >expressions will be in conflict with default.sieve scripting rules? >> That's just about learning Posix Regex syntax. > All the rules are 100% correct as there is a very simple and useful tool in postfix to check if regexp is correct. The tool can be used even by people who don't have a foggiest idea how regexp work. All you have to do is to type on a command line this postmap -q "Subject: *****SPAM***** blablablabla" regexp:/etc/postfix/header_checks or this postmap -q "X-Spam-Flag: YES" regexp:/etc/postfix/header_checks and it will tell you if your rule is correct or not. It is bullet and fool proof system with 100% guarantee. All these rules have been checked like that despite the fact that I know for a fact that they are correct by my own knowledge and experience. > >> I'm almost 100% sure that that regex also matched the bounce from your sieve rules. There is no mysterious interaction between header_checks and sieve rules, it's just your pattern was too liberal in the former. > No, no. The regex could not have matched the bounce from my own rules because it would be silly to send a test message from the same server that would loop back and block myself by my own rules. I sent test messages from another server's accounts. Plus, there is a difference. Header_checks in Postfix use only customized rules that do not involve any Spamassassin's added headers. Now in my case only Dovecot Sieve goes through Spamassassin headers because as mentioned earlier I passed delivery from Postfix to dovecot LDA in my configuration. That's why everything that has Spamassassin's headers and tags added has to be configured via default.sieve scripting and everything else (that do not get Spamassassin's headers added) may use header_checks of Postfix. I have just figured that out by runnning quite a few different and simple tests. > >> I think if you tune that header_checks file correctly you should have no more issues. > The header_check rules are fine tuned to their best. > > Anyway, I am thankful for your suggestion as it pointed me to the right direction. Then I picked it up and simply followed onwards by elaborating and building on top which led me to a solved problem Thank you. > > So if the regexes were all correct, then: a) what was your actual problem once you identified it and b) for the benefit of the list, how did you actually solve it? Alex -- This message is intended only for the addressee and may contain confidential information. Unless you are that person, you may not disclose its contents or use it in any way and are requested to delete the message along with any attachments and notify us immediately. "Transact" is operated by Integrated Financial Arrangements plc. 29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300. (Registered office: as above; Registered in England and Wales under number: 3727592). Authorised and regulated by the Financial Conduct Authority (entered on the Financial Services Register; no. 190856). From noeldude at gmail.com Fri Sep 26 14:51:52 2014 From: noeldude at gmail.com (Noel) Date: Fri, 26 Sep 2014 09:51:52 -0500 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer> References: <54255249.70707@integrafin.co.uk><23D946DB1F134A2CB613C8F8E22144BC@Computer><99622F1A0F1241308D93744D9E12D5EF@Computer> <54256B7E.6060703@integrafin.co.uk> <7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer> Message-ID: <54257D88.1070501@gmail.com> On 9/26/2014 9:27 AM, Klaipedaville on Google wrote: >> /^Subject:.**{5}SPAM*{5}/ REJECT No spammers allowed here. >> /^Subject:.*\*\*\*\*\*SPAM\*\*\*\*\*/ REJECT No spammers allowed. >> /\s**{5}SPAM*{5}/ REJECT No spamming >> hullababballos allowed. >> I think it may be this one above. From the postfix manuals"By default, matching is case-insensitive, and newlines are not treated as special characters. The behavior is controlled by flags, which are toggled by appending one or more of the following characters after the pattern: *i* (default: on) Toggles the case sensitivity flag. By default, matching is case insensitive." > Case insensitive is declared by putting this /i at the end of a rule. > Postfix has nothing to do with regular expressions (regexp) and regexp is not controlled by postfix. Not true. Postfix regexp (and pcre) matches are case insensitive by default, adding the /i flag makes them case sensitive. This should be quite clear in the postfix docs quoted above. This documented default behavior may be different from other software you're familiar with. You're welcome to discuss postfix header checks further on the postfix-users list. -- Noel Jones From klaipedaville at gmail.com Fri Sep 26 15:00:34 2014 From: klaipedaville at gmail.com (Klaipedaville on Google) Date: Fri, 26 Sep 2014 18:00:34 +0300 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <54257CF5.8060404@integrafin.co.uk> References: <54255249.70707@integrafin.co.uk><23D946DB1F134A2CB613C8F8E22144BC@Computer><99622F1A0F1241308D93744D9E12D5EF@Computer> <54256B7E.6060703@integrafin.co.uk><7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer> <54257CF5.8060404@integrafin.co.uk> Message-ID: <8F9EE935A5B5471F88FF0D952C071A49@Computer> >So why does it state in man 5 regexp_table that such tables are *case insensitive* by default and the /i actually toggles that? Are you saying that man page is wrong? I'd be surprised as I don't think I've yet come >across an occasion where postfix man pages are incorrect! I am not saying that the Postfix man is incorrect. It is 100% case insensitive and SPAM (upper case) and spam (lower case) would mean absolutely the same. Therefore my SPAM (upper case) regexp was correct. >So if the regexes were all correct, then: > >a) what was your actual problem once you identified it > >and > >b) for the benefit of the list, how did you actually solve it? > >Alex I explained it all in my previous post. From klaipedaville at gmail.com Fri Sep 26 15:10:55 2014 From: klaipedaville at gmail.com (Klaipedaville on Google) Date: Fri, 26 Sep 2014 18:10:55 +0300 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <54257D88.1070501@gmail.com> References: <54255249.70707@integrafin.co.uk><23D946DB1F134A2CB613C8F8E22144BC@Computer><99622F1A0F1241308D93744D9E12D5EF@Computer> <54256B7E.6060703@integrafin.co.uk><7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer> <54257D88.1070501@gmail.com> Message-ID: >Not true. Postfix regexp (and pcre) matches are case insensitive by default, adding the /i flag makes them case sensitive. This should be quite clear in the postfix docs quoted above. This documented >default behavior may be different from other software you're familiar with. > >You're welcome to discuss postfix header checks further on the postfix-users list. > > -- Noel Jones I am not here to argue on details. It's just getting side tracked. I meant in general. A couple of 100 tests that I ran trying to solve this issue included both case sensitive and case insensitive and all the other possible and impossible options I could think of. Perhaps I missed that little detail, but postfix-user list members and Postfix creator Mr. Wetsie Venema in person said that the regexp were correct. I have discussed it there before as well. From acrow at integrafin.co.uk Fri Sep 26 15:14:47 2014 From: acrow at integrafin.co.uk (Alex Crow) Date: Fri, 26 Sep 2014 16:14:47 +0100 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <8F9EE935A5B5471F88FF0D952C071A49@Computer> References: <54255249.70707@integrafin.co.uk><23D946DB1F134A2CB613C8F8E22144BC@Computer><99622F1A0F1241308D93744D9E12D5EF@Computer> <54256B7E.6060703@integrafin.co.uk><7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer> <54257CF5.8060404@integrafin.co.uk> <8F9EE935A5B5471F88FF0D952C071A49@Computer> Message-ID: <542582E7.1060406@integrafin.co.uk> On 26/09/14 16:00, Klaipedaville on Google wrote: > >So why does it state in man 5 regexp_table that such tables are *case > insensitive* by default and the /i actually toggles that? Are you > saying that man page is wrong? I'd be surprised as I don't think I've > yet come > >across an occasion where postfix man pages are incorrect! > I am not saying that the Postfix man is incorrect. It is 100% case > insensitive and SPAM (upper case) and spam (lower case) would mean > absolutely the same. Therefore my SPAM (upper case) regexp was correct. > > >So if the regexes were all correct, then: > > > >a) what was your actual problem once you identified it > > > >and > > > >b) for the benefit of the list, how did you actually solve it? > > > >Alex > > I explained it all in my previous post. I realise it's probably because of the use of the reject action, which presumably inserts the text "No spamming allowed here." into the subject of the bounce. However what also concerns me is that sending MDN's back to the envelope sender of SPAM messages is very likely to cause your server to be the origin of "Joe-Job" spam. The sieve RFCs state that if using reject (therefore sending MDNs) you should also be able to check for forged envelope senders and in that case do not send bounces. In real life it's considered best to just not bother sending anything back at all, and either discard, or block at the SMTP level using RBLs. Cheers Alex > > -- > This message has been scanned for viruses and > dangerous content by *MailScanner* , and is > believed to be clean. -- This message is intended only for the addressee and may contain confidential information. Unless you are that person, you may not disclose its contents or use it in any way and are requested to delete the message along with any attachments and notify us immediately. "Transact" is operated by Integrated Financial Arrangements plc. 29 Clement's Lane, London EC4N 7AE. Tel: (020) 7608 4900 Fax: (020) 7608 5300. (Registered office: as above; Registered in England and Wales under number: 3727592). Authorised and regulated by the Financial Conduct Authority (entered on the Financial Services Register; no. 190856). From h.reindl at thelounge.net Fri Sep 26 15:17:51 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Fri, 26 Sep 2014 17:17:51 +0200 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <54257CF5.8060404@integrafin.co.uk> References: <54255249.70707@integrafin.co.uk> <23D946DB1F134A2CB613C8F8E22144BC@Computer> <99622F1A0F1241308D93744D9E12D5EF@Computer> <54256B7E.6060703@integrafin.co.uk> <7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer> <54257CF5.8060404@integrafin.co.uk> Message-ID: <5425839F.9000007@thelounge.net> Am 26.09.2014 um 16:49 schrieb Alex Crow: > On 26/09/14 15:27, Klaipedaville on Google wrote: >>> /^Subject:.**{5}SPAM*{5}/ REJECT No spammers allowed here. >>> /^Subject:.*\*\*\*\*\*SPAM\*\*\*\*\*/ REJECT No spammers allowed. >>> /\s**{5}SPAM*{5}/ REJECT No spamming >>> hullababballos allowed. >>> I think it may be this one above. From the postfix manuals"By default, matching is case-insensitive, and >>> newlines are not treated as special characters. The behavior is controlled by flags, which are toggled by >>> appending one or more of the following characters after the pattern: *i* (default: on) Toggles the case >>> sensitivity flag. By default, matching is case insensitive." >> Case insensitive is declared by putting this /i at the end of a rule. >> Postfix has nothing to do with regular expressions (regexp) and regexp is not controlled by postfix. There should >> be a regexp library available on the server where you are using regexp. It?s like PHP, or tml, or js, or css, it >> cannot be controlled by postfix this is just unqualified junk - surely it *has a lot* to do with it because it can and do add the flag as default frankly every script can add i after / as default > So why does it state in man 5 regexp_table that such tables are *case insensitive* by default and the /i actually > toggles that? Are you saying that man page is wrong? I'd be surprised as I don't think I've yet come across an > occasion where postfix man pages are incorrect! they are *not* case-insensitive and it takes 5 seconds to verify that -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From klaipedaville at gmail.com Fri Sep 26 15:44:50 2014 From: klaipedaville at gmail.com (Klaipedaville on Google) Date: Fri, 26 Sep 2014 18:44:50 +0300 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <542582E7.1060406@integrafin.co.uk> References: <54255249.70707@integrafin.co.uk><23D946DB1F134A2CB613C8F8E22144BC@Computer><99622F1A0F1241308D93744D9E12D5EF@Computer> <54256B7E.6060703@integrafin.co.uk><7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer><54257CF5.8060404@integrafin.co.uk><8F9EE935A5B5471F88FF0D952C071A49@Computer> <542582E7.1060406@integrafin.co.uk> Message-ID: <94487CE07C4446C29BA2FAC6C96D17DF@Computer> >I realise it's probably because of the use of the reject action, which presumably inserts the text "No spamming allowed here." into the subject of the bounce. > >However what also concerns me is that sending MDN's back to the envelope sender of SPAM messages is very likely to cause your server to be the origin of "Joe-Job" spam. The sieve RFCs state that if using reject (therefore >sending MDNs) you should also be able to check for forged envelope senders and in that case do not send bounces. In real life it's considered best to just not bother sending anything back at all, and either discard, or block at >the SMTP level using RBLs. > >Cheers > >Alex Whatever's the case the backscatter you're talking about has its own ways and methods to be fought with. There are countries for example Germany where it is prohibited by law to discard any email messages silently. You must reject them so that the senders would be aware what is going on. I was told that by one German admin. I am not sure if this is really true but it has some logic on one hand and it is completely groundless on the other hand because you cannot substitute a live person by a machine. Let's say if the machine (computer / server) confirmed reception of the email it does not necessarily mean that any person on the other end also received and read that email. But this is just demagogy that has very vogue legal / law aspects involved. From h.reindl at thelounge.net Fri Sep 26 15:57:23 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Fri, 26 Sep 2014 17:57:23 +0200 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <94487CE07C4446C29BA2FAC6C96D17DF@Computer> References: <54255249.70707@integrafin.co.uk> <23D946DB1F134A2CB613C8F8E22144BC@Computer> <99622F1A0F1241308D93744D9E12D5EF@Computer> <54256B7E.6060703@integrafin.co.uk> <7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer> <54257CF5.8060404@integrafin.co.uk> <8F9EE935A5B5471F88FF0D952C071A49@Computer> <542582E7.1060406@integrafin.co.uk> <94487CE07C4446C29BA2FAC6C96D17DF@Computer> Message-ID: <54258CE3.9030504@thelounge.net> Am 26.09.2014 um 17:44 schrieb Klaipedaville on Google: > There are countries for example Germany where it is prohibited by law to discard > any email messages silently. You must reject them so that the senders would be > aware what is going on. I was told that by one German admin. I am not sure if > this is really true but it has some logic on one hand it is true and besides the german legal letter below you violate a second law at the same time - that is why you have to run a spamfilter *before queue* and sa-milter exists - in case you reject a message the sending server is responsible for a bounce in case you accept and silently drop it you have a unacceptable configuration - independent of laws - in case of a important and time critical mail i need to know it was rejected and so can call the person by phone or try to remove something which triggered a false positive ____________________________________________________ there are two important rules for mail: a) if you accept it you have to deliver it b) if you can't deliver it you must not accept it if you follow b) you don't become a backscatter http://www.postfix.org/MILTER_README.html ____________________________________________________ ? 303a StGB - Datenver?nderung (1) Wer rechtswidrig Daten (? 202a Abs. 2) l?scht, unterdr?ckt, unbrauchbar macht oder ver?ndert, wird mit Freiheitsstrafe bis zu zwei Jahren oder mit Geldstrafe bestraft -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From jjhoffart at icloud.com Fri Sep 26 15:58:47 2014 From: jjhoffart at icloud.com (jjhoffart) Date: Fri, 26 Sep 2014 09:58:47 -0600 Subject: director In-Reply-To: <5421E105.6020203@gmail.com> References: <797A8820-0AA4-48EF-879D-4E3A81948E49@icloud.com> <5421E105.6020203@gmail.com> Message-ID: Still having some trouble with director. I have copied the var/run/dovecot director along with the /etc/dovecot directory. So I know have /var/run/dovecot-director and dovecot-backend along with /etc/dovecot-director and /etc/dovecot-backend. The base_dir in these corresponds with the named directory in /var/run. The issue I have now is that only one instance will run the other outputs a bunch of errors: root at mail1:~# service dovecot-backend start [....] Starting IMAP/POP3 mail server: dovecot-backendError: service(managesieve-login): listen(*, 4190) failed: Address already in use Error: service(pop3-login): listen(*, 110) failed: Address already in use Error: service(pop3-login): listen(*, 995) failed: Address already in use Error: service(lmtp): Socket already exists: /var/spool/postfix/private/dovecot-lmtp Error: service(lmtp): listen(*, 24) failed: Address already in use Error: service(imap-login): listen(*, 143) failed: Address already in use Error: service(imap-login): listen(*, 993) failed: Address already in use Error: service(auth): Socket already exists: /var/spool/postfix/private/dovecot-auth Fatal: Failed to start listeners i have edited the 10-master.conf file in the backend directory to use different port numbers but still receive the following output above. On Sep 23, 2014, at 3:07 PM, Chris Lasater wrote: > The configuration and run/base_dir directories can be where ever you like. The locations Eduardo stated are the most appropriate for dovecot installed with an RPM. Mine were compiled and set in the home directory, so they are in a slightly different location. As long as you use the -c to point to the correct configuration file you should be good. > For mine I kept my dovecot config file in the default location and put the director one elsewhere and created an alias, so that I can start the director by just typing director. This might make things easier for you to manage, then you can just stop it by running "doveadm -i stop" > > alias director="sudo -E PATH=${PATH} LD_LIBRARY_PATH=${LD_LIBRARY_PATH} /home/user/dovecot/sbin/dovecot -c /home/user/dovecot/etc/dovecot/director.conf" > > > On 09/23/2014 05:00 PM, jjhoffart wrote: >>> Thanks for the replies, >>> I am still fairly new to dovecot and still learning. This is a quick run down of my setup: 3 servers running iRedMail (this is a package that installs dovecot 2.1.7, postfix, and LDAP). All three servers share an NFS backend. The same 3 servers are also sitting behind a load balancer. What I want to do is use these three servers as directors and mail servers. So from the replies I have gotten I understand that I need to create 2 config files 1 for director and 1 for dovecot. Now my next question is do these config files need to be stored in /etc/dovecot or /var/run/dovecot? Also is creating the second config file as simple as copying and renaming the dovecot.conf file? >>> >>> On Sep 23, 2014, at 2:26 PM, Eduardo Ramos wrote: >>> >>>> Hi, >>>> >>>> In fact you don't NEED a director. You can use two dovecot servers sharing a NFS storage with a normal (backend) implementation. It's good to see that page: http://wiki2.dovecot.org/NFS for some good recomendations. >>>> >>>> You must have a base_dir for each instance of dovecot you want to run, and a dovecot.conf as well. One could be director and other backend. I suggest you have two separated configuration directories, /etc/dovecot-director and /etc/dovecot-backend. Each with the respective configuration. Start dovecot with "dovecot -c /etc/dovecot-director/dovecot.conf". Backend is the same. >>>> >>>> In order to help more, provide us more details about your environment and doulbts. >>>> >>>> On 09/23/2014 03:57 PM, jjhoffart wrote: >>>>> Hello, >>>>> I am currently trying to setup a cluster of mail servers. I currently have two servers I am trying to cluster together. These servers will also have a shared NFS backend. I have read on the site that I will need to configure director since I am using NFS. I have read through all of the documentation on director but still need a little guidance to get things up and running. One of the questions I have is about the base_dir on the Multiple Invocations section of the wiki. It states that I will need to change the bas_dir to the new run directory, not sure what needs to happen here, can anyone help me out? From klaipedaville at gmail.com Fri Sep 26 16:18:25 2014 From: klaipedaville at gmail.com (Klaipedaville on Google) Date: Fri, 26 Sep 2014 19:18:25 +0300 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <54258CE3.9030504@thelounge.net> References: <54255249.70707@integrafin.co.uk> <23D946DB1F134A2CB613C8F8E22144BC@Computer> <99622F1A0F1241308D93744D9E12D5EF@Computer> <54256B7E.6060703@integrafin.co.uk> <7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer> <54257CF5.8060404@integrafin.co.uk> <8F9EE935A5B5471F88FF0D952C071A49@Computer> <542582E7.1060406@integrafin.co.uk><94487CE07C4446C29BA2FAC6C96D17DF@Computer> <54258CE3.9030504@thelounge.net> Message-ID: >it is true and besides the german legal letter below you violate a second law at the same time - that is why you have to run a spamfilter *before queue* and sa-milter exists - in case you reject a message >the sending server is responsible for a bounce > >in case you accept and silently drop it you have a unacceptable configuration - independent of laws - in case of a important and time critical mail i need to know it was rejected and so can call the person by phone or try to >remove something which triggered a false positive >____________________________________________________ > >there are two important rules for mail: > >a) if you accept it you have to deliver it >b) if you can't deliver it you must not accept it > >if you follow b) you don't become a backscatter > >http://www.postfix.org/MILTER_README.html Yep, that's correct about point b). Plus, I also personally agree that rejecting is better, than having it silently discarded. Good thing is that I do not reside in Germany so I am safe on that In fact, postfix before-queue content filter has limits in the amount of mail that a site can handle: http://www.postfix.org/SMTPD_PROXY_README.html therefore legal part of this in Germany limits all German people on resources as every single person is forced to run before-queue filters which in my opinion has its own disadvantages on top of everything else and despite the laws as well. -------------- next part -------------- A non-text attachment was scrubbed... Name: wlEmoticon-smile[1].png Type: image/png Size: 1046 bytes Desc: not available URL: From acrow at integrafin.co.uk Fri Sep 26 16:29:33 2014 From: acrow at integrafin.co.uk (Alex Crow) Date: Fri, 26 Sep 2014 17:29:33 +0100 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <94487CE07C4446C29BA2FAC6C96D17DF@Computer> References: <54255249.70707@integrafin.co.uk><23D946DB1F134A2CB613C8F8E22144BC@Computer><99622F1A0F1241308D93744D9E12D5EF@Computer> <54256B7E.6060703@integrafin.co.uk><7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer><54257CF5.8060404@integrafin.co.uk><8F9EE935A5B5471F88FF0D952C071A49@Computer> <542582E7.1060406@integrafin.co.uk> <94487CE07C4446C29BA2FAC6C96D17DF@Computer> Message-ID: <5425946D.70103@integrafin.co.uk> On 26/09/14 16:44, Klaipedaville on Google wrote: > > Whatever's the case the backscatter you're talking about has its own > ways and methods to be fought with. There are countries for example > Germany where it is prohibited by law to discard any email messages > silently. You must reject them so that the senders would be aware what > is going on. I was told that by one German admin. I am not sure if > this is really true but it has some logic on one hand and it is > completely groundless on the other hand because you cannot substitute > a live person by a machine. Let's say if the machine (computer / > server) confirmed reception of the email it does not necessarily mean > that any person on the other end also received and read that email. > But this is just demagogy that has very vogue legal / law aspects > involved. > > One *very* convincing argument not to send an *email* response (reject at SMTP is fine) is that it is very likely indeed you'll end up on an RBL yourself for doing this. It happened to us when we were still bouncing (probably about 8-10 years ago). It was the main reason we stopped. Reindl, I respecfully disagree with (a) at least for the UK. It may be the case in Germany but I'll be damned if I'm going to give up on my Mailscanner - tuned over the years enough that we've never had a legit mail get canned. Anyway, that's enough for me otherwise this is going to turn into a flamewar rather than informational. From h.reindl at thelounge.net Fri Sep 26 16:40:36 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Fri, 26 Sep 2014 18:40:36 +0200 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: References: <54255249.70707@integrafin.co.uk> <23D946DB1F134A2CB613C8F8E22144BC@Computer> <99622F1A0F1241308D93744D9E12D5EF@Computer> <54256B7E.6060703@integrafin.co.uk> <7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer> <54257CF5.8060404@integrafin.co.uk> <8F9EE935A5B5471F88FF0D952C071A49@Computer> <542582E7.1060406@integrafin.co.uk> <94487CE07C4446C29BA2FAC6C96D17DF@Computer> <54258CE3.9030504@thelounge.net> Message-ID: <54259704.8070202@thelounge.net> Am 26.09.2014 um 18:18 schrieb Klaipedaville on Google: >> it is true and besides the german legal letter below you violate a second law at the same time - that is why you have to run a spamfilter *before queue* and sa-milter exists - in case you reject a message >> the sending server is responsible for a bounce >> >> in case you accept and silently drop it you have a unacceptable configuration - independent of laws - in case of a important and time critical mail i need to know it was rejected and so can call the person by phone or try to >remove something which triggered a false positive >> ____________________________________________________ >> >> there are two important rules for mail: >> >> a) if you accept it you have to deliver it >> b) if you can't deliver it you must not accept it >> >> if you follow b) you don't become a backscatter >> >> http://www.postfix.org/MILTER_README.html > > Yep, that's correct about point b). Plus, I also personally agree that rejecting is better, than having it silently discarded. Good thing is that I do not reside in Germany so I am safe on that > > In fact, postfix before-queue content filter has limits in the amount of mail that a site can handle: http://www.postfix.org/SMTPD_PROXY_README.html therefore legal part of this in Germany limits all German people on resources as every single person is forced to run before-queue filters which in my opinion has its own disadvantages on top of everything else and despite the laws as well. that's no problem because with RBL weighting and postscreen you reject 95% of the crap before it ever touchs smtpd or even the contentfilter that stats below are about a maillog starting with Sep 18 19:50:39 for some hundrest domains and currently 2000 valid RCPT, if the contentfilter has to handle most of your incoming flow you made a mistake by not reject earlier with "cheaper" methods ___________________________________________________ that part never touched the contentfilter Invalid User: 3074 Disallowed User: 2 Reject Postscreen: 148451 Reject Postfix: 6225 Blacklist: 144880 Pregreet: 5143 Protocol Error: 1607 Helo: 190 Sender Blocked: 200 Sender Invalid: 229 Sender Spoofed: 847 PTR Missing: 1347 PTR Generic: 319 ___________________________________________________ Connections: 185848 Delivered: 20293 Invalid User: 3074 Disallowed User: 2 Reject Postscreen: 148451 Reject Postfix: 6225 Reject Temporary: 507 Blacklist: 144880 Pregreet: 5143 Protocol Error: 1607 Spamfilter: 2297 Virus: 115 Helo: 190 Subject: 42 Attachment: 0 Sender Blocked: 200 Sender Invalid: 229 Sender Spoofed: 847 PTR Missing: 1347 PTR Generic: 319 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From h.reindl at thelounge.net Fri Sep 26 17:00:09 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Fri, 26 Sep 2014 19:00:09 +0200 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <5425946D.70103@integrafin.co.uk> References: <54255249.70707@integrafin.co.uk> <23D946DB1F134A2CB613C8F8E22144BC@Computer> <99622F1A0F1241308D93744D9E12D5EF@Computer> <54256B7E.6060703@integrafin.co.uk> <7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer> <54257CF5.8060404@integrafin.co.uk> <8F9EE935A5B5471F88FF0D952C071A49@Computer> <542582E7.1060406@integrafin.co.uk> <94487CE07C4446C29BA2FAC6C96D17DF@Computer> <5425946D.70103@integrafin.co.uk> Message-ID: <54259B99.6020505@thelounge.net> Am 26.09.2014 um 18:29 schrieb Alex Crow: > Reindl, > I respecfully disagree with (a) at least for the UK. It may be the case in Germany but I'll be damned if I'm going > to give up on my Mailscanner - tuned over the years enough that we've never had a legit mail get canned. I respecfully disagree - why can't it run before-queue as spamassassin does with sa-milter and in combination with a wise postscreen/postfix setup faces only 5% of all mail sicne the rest got washed away before? > Anyway, that's enough for me otherwise this is going to turn into a flamewar rather than informational well, i would not want to be in danger one of my mails got silently dropped and was a false positive frankly, i was in that situation because using a "Barracuda Spamfirewall" and expecting a sane behavior (reject in case of spam) and it took years to find out it was not the case and needed to be replaced because *in fact* it silently dropped way too much of my own messages as well as from other users too you just don't know about false positives because not every mail is missed by somebody which don't imply it was junk frankly while replace that commercial mails i had mail-discussions where i personally did not miss a few messages until the other side talked about a message in the same thread i never saw -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From eduardo at freedominterface.org Fri Sep 26 17:12:10 2014 From: eduardo at freedominterface.org (Eduardo Ramos) Date: Fri, 26 Sep 2014 14:12:10 -0300 Subject: director In-Reply-To: References: <797A8820-0AA4-48EF-879D-4E3A81948E49@icloud.com> <5421E105.6020203@gmail.com> Message-ID: <54259E6A.8080200@freedominterface.org> Run 'doveadm -i director config' and 'doveadm -i backend config'. Send us the result, please. On 09/26/2014 12:58 PM, jjhoffart wrote: > Still having some trouble with director. I have copied the var/run/dovecot director along with the /etc/dovecot directory. So I know have /var/run/dovecot-director and dovecot-backend along with /etc/dovecot-director and /etc/dovecot-backend. The base_dir in these corresponds with the named directory in /var/run. The issue I have now is that only one instance will run the other outputs a bunch of errors: > > root at mail1:~# service dovecot-backend start > [....] Starting IMAP/POP3 mail server: dovecot-backendError: service(managesieve-login): listen(*, 4190) failed: Address already in use > Error: service(pop3-login): listen(*, 110) failed: Address already in use > Error: service(pop3-login): listen(*, 995) failed: Address already in use > Error: service(lmtp): Socket already exists: /var/spool/postfix/private/dovecot-lmtp > Error: service(lmtp): listen(*, 24) failed: Address already in use > Error: service(imap-login): listen(*, 143) failed: Address already in use > Error: service(imap-login): listen(*, 993) failed: Address already in use > Error: service(auth): Socket already exists: /var/spool/postfix/private/dovecot-auth > Fatal: Failed to start listeners > > i have edited the 10-master.conf file in the backend directory to use different port numbers but still receive the following output above. > > > On Sep 23, 2014, at 3:07 PM, Chris Lasater wrote: > >> The configuration and run/base_dir directories can be where ever you like. The locations Eduardo stated are the most appropriate for dovecot installed with an RPM. Mine were compiled and set in the home directory, so they are in a slightly different location. As long as you use the -c to point to the correct configuration file you should be good. >> For mine I kept my dovecot config file in the default location and put the director one elsewhere and created an alias, so that I can start the director by just typing director. This might make things easier for you to manage, then you can just stop it by running "doveadm -i stop" >> >> alias director="sudo -E PATH=${PATH} LD_LIBRARY_PATH=${LD_LIBRARY_PATH} /home/user/dovecot/sbin/dovecot -c /home/user/dovecot/etc/dovecot/director.conf" >> >> >> On 09/23/2014 05:00 PM, jjhoffart wrote: >>>> Thanks for the replies, >>>> I am still fairly new to dovecot and still learning. This is a quick run down of my setup: 3 servers running iRedMail (this is a package that installs dovecot 2.1.7, postfix, and LDAP). All three servers share an NFS backend. The same 3 servers are also sitting behind a load balancer. What I want to do is use these three servers as directors and mail servers. So from the replies I have gotten I understand that I need to create 2 config files 1 for director and 1 for dovecot. Now my next question is do these config files need to be stored in /etc/dovecot or /var/run/dovecot? Also is creating the second config file as simple as copying and renaming the dovecot.conf file? >>>> >>>> On Sep 23, 2014, at 2:26 PM, Eduardo Ramos wrote: >>>> >>>>> Hi, >>>>> >>>>> In fact you don't NEED a director. You can use two dovecot servers sharing a NFS storage with a normal (backend) implementation. It's good to see that page: http://wiki2.dovecot.org/NFS for some good recomendations. >>>>> >>>>> You must have a base_dir for each instance of dovecot you want to run, and a dovecot.conf as well. One could be director and other backend. I suggest you have two separated configuration directories, /etc/dovecot-director and /etc/dovecot-backend. Each with the respective configuration. Start dovecot with "dovecot -c /etc/dovecot-director/dovecot.conf". Backend is the same. >>>>> >>>>> In order to help more, provide us more details about your environment and doulbts. >>>>> >>>>> On 09/23/2014 03:57 PM, jjhoffart wrote: >>>>>> Hello, >>>>>> I am currently trying to setup a cluster of mail servers. I currently have two servers I am trying to cluster together. These servers will also have a shared NFS backend. I have read on the site that I will need to configure director since I am using NFS. I have read through all of the documentation on director but still need a little guidance to get things up and running. One of the questions I have is about the base_dir on the Multiple Invocations section of the wiki. It states that I will need to change the bas_dir to the new run directory, not sure what needs to happen here, can anyone help me out? From jjhoffart at icloud.com Fri Sep 26 19:28:50 2014 From: jjhoffart at icloud.com (jjhoffart) Date: Fri, 26 Sep 2014 13:28:50 -0600 Subject: director In-Reply-To: <54259E6A.8080200@freedominterface.org> References: <797A8820-0AA4-48EF-879D-4E3A81948E49@icloud.com> <5421E105.6020203@gmail.com> <54259E6A.8080200@freedominterface.org> Message-ID: <5FB2DA15-A93B-473F-ACD8-F1D312A65BFA@icloud.com> Here are the results from the doveadm -r backend config and director config. root at mail1:~# doveadm -i mail1Backend config # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.6 auth_anonymous_username = anonymous auth_cache_negative_ttl = 1 hours auth_cache_size = 0 auth_cache_ttl = 1 hours auth_debug = no auth_debug_passwords = no auth_default_realm = auth_failure_delay = 2 secs auth_first_valid_uid = 500 auth_gssapi_hostname = auth_krb5_keytab = auth_last_valid_uid = 0 auth_master_user_separator = * auth_mechanisms = PLAIN LOGIN auth_proxy_self = auth_realms = auth_socket_path = auth-userdb auth_ssl_require_client_cert = no auth_ssl_username_from_cert = no auth_use_winbind = no auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_username_format = %Lu auth_username_translation = auth_verbose = no auth_verbose_passwords = no auth_winbind_helper_path = /usr/bin/ntlm_auth auth_worker_max_count = 30 base_dir = /var/run/dovecot config_cache_size = 1 M debug_log_path = default_client_limit = 1000 default_idle_kill = 1 mins default_internal_user = dovecot default_login_user = dovenull default_process_limit = 100 default_vsz_limit = 256 M deliver_log_format = msgid=%m: %$ dict { acl = mysql:/etc/dovecot/dovecot-share-folder.conf quotadict = mysql:/etc/dovecot/dovecot-used-quota.conf } dict_db_config = director_doveadm_port = 0 director_mail_servers = director_servers = director_user_expire = 15 mins director_username_hash = %u disable_plaintext_auth = yes dotlock_use_excl = yes doveadm_allowed_commands = doveadm_password = doveadm_proxy_port = 0 doveadm_socket_path = doveadm-server doveadm_worker_count = 0 dsync_alt_char = _ dsync_remote_cmd = ssh -l%{login} %{host} doveadm dsync-server -u%u -l%{lock_timeout} -n%{namespace} first_valid_gid = 1 first_valid_uid = 2000 hostname = imap_capability = imap_client_workarounds = imap_id_log = imap_id_send = imap_idle_notify_interval = 2 mins imap_logout_format = in=%i out=%o imap_max_line_length = 64 k imapc_features = imapc_host = imapc_list_prefix = imapc_master_user = imapc_password = imapc_port = 143 imapc_rawlog_dir = imapc_ssl = no imapc_ssl_ca_dir = imapc_ssl_verify = yes imapc_user = %u import_environment = TZ info_log_path = instance_name = mail1Director last_valid_gid = 0 last_valid_uid = 2000 lda_mailbox_autocreate = no lda_mailbox_autosubscribe = no lda_original_recipient_header = libexec_dir = /usr/lib/dovecot listen = * lmtp_proxy = no lmtp_save_to_detail_mailbox = no lock_method = fcntl log_path = /var/log/dovecot.log log_timestamp = "%b %d %H:%M:%S " login_access_sockets = login_greeting = Dovecot ready. login_log_format = %$: %s login_log_format_elements = user=<%u> method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> login_trusted_networks = mail_access_groups = mail_attachment_dir = mail_attachment_fs = sis posix mail_attachment_hash = %{sha1} mail_attachment_min_size = 128 k mail_cache_fields = flags mail_cache_min_mail_count = 0 mail_chroot = mail_debug = no mail_fsync = optimized mail_full_filesystem_access = no mail_gid = 2000 mail_home = mail_location = maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/ mail_log_prefix = "%s(%u): " mail_max_keyword_length = 50 mail_max_lock_timeout = 0 mail_max_userip_connections = 10 mail_never_cache_fields = imap.envelope mail_nfs_index = no mail_nfs_storage = no mail_plugin_dir = /usr/lib/dovecot/modules mail_plugins = quota mail_prefetch_count = 0 mail_privileged_group = mail_save_crlf = no mail_shared_explicit_inbox = yes mail_temp_dir = /tmp mail_temp_scan_interval = 1 weeks mail_uid = 2000 mailbox_idle_check_interval = 30 secs mailbox_list_index = no maildir_broken_filename_sizes = no maildir_copy_with_hardlinks = yes maildir_stat_dirs = no maildir_very_dirty_syncs = no managesieve_client_workarounds = managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 5 managesieve_max_line_length = 65536 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 master_user_separator = mbox_dirty_syncs = yes mbox_dotlock_change_timeout = 2 mins mbox_lazy_writes = yes mbox_lock_timeout = 5 mins mbox_md5 = apop3d mbox_min_index_size = 0 mbox_read_locks = fcntl mbox_very_dirty_syncs = no mbox_write_locks = dotlock fcntl mdbox_preallocate_space = no mdbox_rotate_interval = 0 mdbox_rotate_size = 2 M mmap_disable = no namespace { hidden = no ignore_on_failure = no inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = no special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / subscriptions = yes type = private } namespace { hidden = no ignore_on_failure = no inbox = no list = children location = maildir:/%%Lh/Maildir/:INDEX=/%%Lh/Maildir/Shared/%%u prefix = Shared/%%u/ separator = / subscriptions = yes type = shared } passdb { args = /etc/dovecot/dovecot-ldap.conf default_fields = deny = no driver = ldap master = no override_fields = pass = no } passdb { args = /etc/dovecot/dovecot-master-users-password default_fields = deny = no driver = passwd-file master = yes override_fields = pass = no } plugin { acl = vfile acl_shared_dict = proxy::acl auth_socket_path = /var/run/dovecot/auth-master quota = dict:user::proxy::quotadict quota_rule = *:storage=1G quota_warning = storage=85%% quota-warning 85 %u quota_warning2 = storage=90%% quota-warning 90 %u quota_warning3 = storage=95%% quota-warning 95 %u sieve = /%Lh/sieve/dovecot.sieve sieve_default = /mail_data/sieve/dovecot.sieve sieve_dir = /%Lh/sieve sieve_global_dir = /mail_data/sieve } pop3_client_workarounds = pop3_enable_last = no pop3_fast_size_lookups = no pop3_lock_session = no pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_no_flag_updates = no pop3_reuse_xuidl = no pop3_save_uidl = no pop3_uidl_duplicates = allow pop3_uidl_format = %08Xu%08Xv pop3c_host = pop3c_password = pop3c_port = 110 pop3c_rawlog_dir = pop3c_ssl = no pop3c_ssl_ca_dir = pop3c_ssl_verify = yes pop3c_user = %u postmaster_address = protocols = pop3 imap sieve lmtp quota_full_tempfail = no recipient_delimiter = + rejection_reason = Your message to <%t> was automatically rejected:%n%r rejection_subject = Rejected: %s replication_full_sync_interval = 12 hours replication_max_conns = 10 replicator_host = replicator replicator_port = 0 sendmail_path = /usr/sbin/sendmail service aggregator { chroot = . client_limit = 0 drop_priv_before_exec = no executable = aggregator extra_groups = fifo_listener replication-notify-fifo { group = mode = 0600 user = } group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener replication-notify { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service anvil { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = anvil extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 1 protocol = service_count = 0 type = anvil unix_listener anvil-auth-penalty { group = mode = 0600 user = } unix_listener anvil { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service auth-worker { chroot = client_limit = 1 drop_priv_before_exec = no executable = auth -w extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 1 type = unix_listener auth-worker { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service auth { chroot = client_limit = 0 drop_priv_before_exec = no executable = auth extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0666 user = postfix } unix_listener auth-client { group = mode = 0600 user = } unix_listener auth-login { group = mode = 0600 user = $default_internal_user } unix_listener auth-master { group = vmail mode = 0666 user = vmail } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } unix_listener login/login { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service config { chroot = client_limit = 0 drop_priv_before_exec = no executable = config extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = config unix_listener config { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service dict { chroot = client_limit = 1 drop_priv_before_exec = no executable = dict extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener dict { group = vmail mode = 0660 user = vmail } user = $default_internal_user vsz_limit = 18446744073709551615 B } service director { chroot = . client_limit = 0 drop_priv_before_exec = no executable = director extra_groups = fifo_listener login/proxy-notify { group = mode = 00 user = } group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener director-admin { group = mode = 0600 user = } unix_listener login/director { group = mode = 00 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service dns_client { chroot = client_limit = 1 drop_priv_before_exec = no executable = dns-client extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener dns-client { group = mode = 0666 user = } unix_listener login/dns-client { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service doveadm { chroot = client_limit = 1 drop_priv_before_exec = no executable = doveadm-server extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 1 type = unix_listener doveadm-server { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service imap-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = imap-login extra_groups = group = idle_kill = 0 inet_listener imap { address = port = 143 ssl = no } inet_listener imaps { address = port = 993 ssl = yes } privileged_group = process_limit = 500 process_min_avail = 0 protocol = imap service_count = 1 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service imap { chroot = client_limit = 1 drop_priv_before_exec = no executable = imap extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1024 process_min_avail = 0 protocol = imap service_count = 1 type = unix_listener login/imap { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service indexer-worker { chroot = client_limit = 1 drop_priv_before_exec = no executable = indexer-worker extra_groups = group = idle_kill = 0 privileged_group = process_limit = 10 process_min_avail = 0 protocol = service_count = 0 type = unix_listener indexer-worker { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service indexer { chroot = client_limit = 0 drop_priv_before_exec = no executable = indexer extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener indexer { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service ipc { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = ipc extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener ipc { group = mode = 0600 user = } unix_listener login/ipc-proxy { group = mode = 0600 user = $default_login_user } user = $default_internal_user vsz_limit = 18446744073709551615 B } service lmtp { chroot = client_limit = 1 drop_priv_before_exec = no executable = lmtp -L extra_groups = group = idle_kill = 0 inet_listener lmtp { address = port = 24 ssl = no } privileged_group = process_limit = 0 process_min_avail = 5 protocol = lmtp service_count = 0 type = unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } unix_listener lmtp { group = mode = 0666 user = } user = vmail vsz_limit = 18446744073709551615 B } service log { chroot = client_limit = 0 drop_priv_before_exec = no executable = log extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = log unix_listener log-errors { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service managesieve-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = managesieve-login extra_groups = group = idle_kill = 0 inet_listener sieve { address = port = 4190 ssl = no } privileged_group = process_limit = 0 process_min_avail = 0 protocol = sieve service_count = 1 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service managesieve { chroot = client_limit = 1 drop_priv_before_exec = no executable = managesieve extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = sieve service_count = 1 type = unix_listener login/sieve { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service pop3-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = pop3-login extra_groups = group = idle_kill = 0 inet_listener pop3 { address = port = 110 ssl = no } inet_listener pop3s { address = port = 995 ssl = yes } privileged_group = process_limit = 0 process_min_avail = 0 protocol = pop3 service_count = 1 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service pop3 { chroot = client_limit = 1 drop_priv_before_exec = no executable = pop3 extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1024 process_min_avail = 0 protocol = pop3 service_count = 1 type = unix_listener login/pop3 { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service quota-warning { chroot = client_limit = 0 drop_priv_before_exec = no executable = script /usr/local/bin/dovecot-quota-warning.sh extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener quota-warning { group = vmail mode = 0660 user = vmail } user = vsz_limit = 18446744073709551615 B } service replicator { chroot = client_limit = 0 drop_priv_before_exec = no executable = replicator extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener replicator { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service ssl-params { chroot = client_limit = 0 drop_priv_before_exec = no executable = ssl-params extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = startup unix_listener login/ssl-params { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service stats { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = stats extra_groups = fifo_listener stats-mail { group = mode = 0600 user = } group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener stats { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } shutdown_clients = yes ssl = required ssl_ca = ssl_cert = method=%m rip=%r lip=%l mpid=%e %c session=<%{session}> login_trusted_networks = mail_access_groups = mail_attachment_dir = mail_attachment_fs = sis posix mail_attachment_hash = %{sha1} mail_attachment_min_size = 128 k mail_cache_fields = flags mail_cache_min_mail_count = 0 mail_chroot = mail_debug = no mail_fsync = optimized mail_full_filesystem_access = no mail_gid = 2000 mail_home = mail_location = maildir:/%Lh/Maildir/:INDEX=/%Lh/Maildir/ mail_log_prefix = "%s(%u): " mail_max_keyword_length = 50 mail_max_lock_timeout = 0 mail_max_userip_connections = 10 mail_never_cache_fields = imap.envelope mail_nfs_index = no mail_nfs_storage = no mail_plugin_dir = /usr/lib/dovecot/modules mail_plugins = quota mail_prefetch_count = 0 mail_privileged_group = mail_save_crlf = no mail_shared_explicit_inbox = yes mail_temp_dir = /tmp mail_temp_scan_interval = 1 weeks mail_uid = 2000 mailbox_idle_check_interval = 30 secs mailbox_list_index = no maildir_broken_filename_sizes = no maildir_copy_with_hardlinks = yes maildir_stat_dirs = no maildir_very_dirty_syncs = no managesieve_client_workarounds = managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_compile_errors = 5 managesieve_max_line_length = 65536 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 master_user_separator = mbox_dirty_syncs = yes mbox_dotlock_change_timeout = 2 mins mbox_lazy_writes = yes mbox_lock_timeout = 5 mins mbox_md5 = apop3d mbox_min_index_size = 0 mbox_read_locks = fcntl mbox_very_dirty_syncs = no mbox_write_locks = dotlock fcntl mdbox_preallocate_space = no mdbox_rotate_interval = 0 mdbox_rotate_size = 2 M mmap_disable = no namespace { hidden = no ignore_on_failure = no inbox = yes list = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { auto = no special_use = \Sent } mailbox Spam { auto = no special_use = \Junk } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / subscriptions = yes type = private } namespace { hidden = no ignore_on_failure = no inbox = no list = children location = maildir:/%%Lh/Maildir/:INDEX=/%%Lh/Maildir/Shared/%%u prefix = Shared/%%u/ separator = / subscriptions = yes type = shared } passdb { args = /etc/dovecot/dovecot-ldap.conf default_fields = deny = no driver = ldap master = no override_fields = pass = no } passdb { args = /etc/dovecot/dovecot-master-users-password default_fields = deny = no driver = passwd-file master = yes override_fields = pass = no } plugin { acl = vfile acl_shared_dict = proxy::acl auth_socket_path = /var/run/dovecot/auth-master quota = dict:user::proxy::quotadict quota_rule = *:storage=1G quota_warning = storage=85%% quota-warning 85 %u quota_warning2 = storage=90%% quota-warning 90 %u quota_warning3 = storage=95%% quota-warning 95 %u sieve = /%Lh/sieve/dovecot.sieve sieve_default = /mail_data/sieve/dovecot.sieve sieve_dir = /%Lh/sieve sieve_global_dir = /mail_data/sieve } pop3_client_workarounds = pop3_enable_last = no pop3_fast_size_lookups = no pop3_lock_session = no pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_no_flag_updates = no pop3_reuse_xuidl = no pop3_save_uidl = no pop3_uidl_duplicates = allow pop3_uidl_format = %08Xu%08Xv pop3c_host = pop3c_password = pop3c_port = 110 pop3c_rawlog_dir = pop3c_ssl = no pop3c_ssl_ca_dir = pop3c_ssl_verify = yes pop3c_user = %u postmaster_address = protocols = pop3 imap sieve lmtp quota_full_tempfail = no recipient_delimiter = + rejection_reason = Your message to <%t> was automatically rejected:%n%r rejection_subject = Rejected: %s replication_full_sync_interval = 12 hours replication_max_conns = 10 replicator_host = replicator replicator_port = 0 sendmail_path = /usr/sbin/sendmail service aggregator { chroot = . client_limit = 0 drop_priv_before_exec = no executable = aggregator extra_groups = fifo_listener replication-notify-fifo { group = mode = 0600 user = } group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener replication-notify { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service anvil { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = anvil extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 1 protocol = service_count = 0 type = anvil unix_listener anvil-auth-penalty { group = mode = 0600 user = } unix_listener anvil { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service auth-worker { chroot = client_limit = 1 drop_priv_before_exec = no executable = auth -w extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 1 type = unix_listener auth-worker { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service auth { chroot = client_limit = 0 drop_priv_before_exec = no executable = auth extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0666 user = postfix } unix_listener auth-client { group = mode = 0600 user = } unix_listener auth-login { group = mode = 0600 user = $default_internal_user } unix_listener auth-master { group = vmail mode = 0666 user = vmail } unix_listener auth-userdb { group = vmail mode = 0660 user = vmail } unix_listener login/login { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service config { chroot = client_limit = 0 drop_priv_before_exec = no executable = config extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = config unix_listener config { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service dict { chroot = client_limit = 1 drop_priv_before_exec = no executable = dict extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener dict { group = vmail mode = 0660 user = vmail } user = $default_internal_user vsz_limit = 18446744073709551615 B } service director { chroot = . client_limit = 0 drop_priv_before_exec = no executable = director extra_groups = fifo_listener login/proxy-notify { group = mode = 00 user = } group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener director-admin { group = mode = 0600 user = } unix_listener login/director { group = mode = 00 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service dns_client { chroot = client_limit = 1 drop_priv_before_exec = no executable = dns-client extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener dns-client { group = mode = 0666 user = } unix_listener login/dns-client { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service doveadm { chroot = client_limit = 1 drop_priv_before_exec = no executable = doveadm-server extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 1 type = unix_listener doveadm-server { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service imap-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = imap-login extra_groups = group = idle_kill = 0 inet_listener imap { address = port = 143 ssl = no } inet_listener imaps { address = port = 993 ssl = yes } privileged_group = process_limit = 500 process_min_avail = 0 protocol = imap service_count = 1 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service imap { chroot = client_limit = 1 drop_priv_before_exec = no executable = imap extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1024 process_min_avail = 0 protocol = imap service_count = 1 type = unix_listener login/imap { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service indexer-worker { chroot = client_limit = 1 drop_priv_before_exec = no executable = indexer-worker extra_groups = group = idle_kill = 0 privileged_group = process_limit = 10 process_min_avail = 0 protocol = service_count = 0 type = unix_listener indexer-worker { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service indexer { chroot = client_limit = 0 drop_priv_before_exec = no executable = indexer extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener indexer { group = mode = 0666 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } service ipc { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = ipc extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener ipc { group = mode = 0600 user = } unix_listener login/ipc-proxy { group = mode = 0600 user = $default_login_user } user = $default_internal_user vsz_limit = 18446744073709551615 B } service lmtp { chroot = client_limit = 1 drop_priv_before_exec = no executable = lmtp -L extra_groups = group = idle_kill = 0 inet_listener lmtp { address = port = 24 ssl = no } privileged_group = process_limit = 0 process_min_avail = 5 protocol = lmtp service_count = 0 type = unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } unix_listener lmtp { group = mode = 0666 user = } user = vmail vsz_limit = 18446744073709551615 B } service log { chroot = client_limit = 0 drop_priv_before_exec = no executable = log extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = log unix_listener log-errors { group = mode = 0600 user = } user = vsz_limit = 18446744073709551615 B } service managesieve-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = managesieve-login extra_groups = group = idle_kill = 0 inet_listener sieve { address = port = 4190 ssl = no } privileged_group = process_limit = 0 process_min_avail = 0 protocol = sieve service_count = 1 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service managesieve { chroot = client_limit = 1 drop_priv_before_exec = no executable = managesieve extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = sieve service_count = 1 type = unix_listener login/sieve { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service pop3-login { chroot = login client_limit = 0 drop_priv_before_exec = no executable = pop3-login extra_groups = group = idle_kill = 0 inet_listener pop3 { address = port = 110 ssl = no } inet_listener pop3s { address = port = 995 ssl = yes } privileged_group = process_limit = 0 process_min_avail = 0 protocol = pop3 service_count = 1 type = login user = $default_login_user vsz_limit = 18446744073709551615 B } service pop3 { chroot = client_limit = 1 drop_priv_before_exec = no executable = pop3 extra_groups = group = idle_kill = 0 privileged_group = process_limit = 1024 process_min_avail = 0 protocol = pop3 service_count = 1 type = unix_listener login/pop3 { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service quota-warning { chroot = client_limit = 0 drop_priv_before_exec = no executable = script /usr/local/bin/dovecot-quota-warning.sh extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = unix_listener quota-warning { group = vmail mode = 0660 user = vmail } user = vsz_limit = 18446744073709551615 B } service replicator { chroot = client_limit = 0 drop_priv_before_exec = no executable = replicator extra_groups = group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener replicator { group = mode = 0600 user = $default_internal_user } user = vsz_limit = 18446744073709551615 B } service ssl-params { chroot = client_limit = 0 drop_priv_before_exec = no executable = ssl-params extra_groups = group = idle_kill = 0 privileged_group = process_limit = 0 process_min_avail = 0 protocol = service_count = 0 type = startup unix_listener login/ssl-params { group = mode = 0666 user = } user = vsz_limit = 18446744073709551615 B } service stats { chroot = empty client_limit = 0 drop_priv_before_exec = no executable = stats extra_groups = fifo_listener stats-mail { group = mode = 0600 user = } group = idle_kill = 4294967295 secs privileged_group = process_limit = 1 process_min_avail = 0 protocol = service_count = 0 type = unix_listener stats { group = mode = 0600 user = } user = $default_internal_user vsz_limit = 18446744073709551615 B } shutdown_clients = yes ssl = required ssl_ca = ssl_cert = wrote: > Run 'doveadm -i director config' and 'doveadm -i backend config'. Send us the result, please. > > On 09/26/2014 12:58 PM, jjhoffart wrote: >> Still having some trouble with director. I have copied the var/run/dovecot director along with the /etc/dovecot directory. So I know have /var/run/dovecot-director and dovecot-backend along with /etc/dovecot-director and /etc/dovecot-backend. The base_dir in these corresponds with the named directory in /var/run. The issue I have now is that only one instance will run the other outputs a bunch of errors: >> >> root at mail1:~# service dovecot-backend start >> [....] Starting IMAP/POP3 mail server: dovecot-backendError: service(managesieve-login): listen(*, 4190) failed: Address already in use >> Error: service(pop3-login): listen(*, 110) failed: Address already in use >> Error: service(pop3-login): listen(*, 995) failed: Address already in use >> Error: service(lmtp): Socket already exists: /var/spool/postfix/private/dovecot-lmtp >> Error: service(lmtp): listen(*, 24) failed: Address already in use >> Error: service(imap-login): listen(*, 143) failed: Address already in use >> Error: service(imap-login): listen(*, 993) failed: Address already in use >> Error: service(auth): Socket already exists: /var/spool/postfix/private/dovecot-auth >> Fatal: Failed to start listeners >> >> i have edited the 10-master.conf file in the backend directory to use different port numbers but still receive the following output above. >> >> >> On Sep 23, 2014, at 3:07 PM, Chris Lasater wrote: >> >>> The configuration and run/base_dir directories can be where ever you like. The locations Eduardo stated are the most appropriate for dovecot installed with an RPM. Mine were compiled and set in the home directory, so they are in a slightly different location. As long as you use the -c to point to the correct configuration file you should be good. >>> For mine I kept my dovecot config file in the default location and put the director one elsewhere and created an alias, so that I can start the director by just typing director. This might make things easier for you to manage, then you can just stop it by running "doveadm -i stop" >>> >>> alias director="sudo -E PATH=${PATH} LD_LIBRARY_PATH=${LD_LIBRARY_PATH} /home/user/dovecot/sbin/dovecot -c /home/user/dovecot/etc/dovecot/director.conf" >>> >>> >>> On 09/23/2014 05:00 PM, jjhoffart wrote: >>>>> Thanks for the replies, >>>>> I am still fairly new to dovecot and still learning. This is a quick run down of my setup: 3 servers running iRedMail (this is a package that installs dovecot 2.1.7, postfix, and LDAP). All three servers share an NFS backend. The same 3 servers are also sitting behind a load balancer. What I want to do is use these three servers as directors and mail servers. So from the replies I have gotten I understand that I need to create 2 config files 1 for director and 1 for dovecot. Now my next question is do these config files need to be stored in /etc/dovecot or /var/run/dovecot? Also is creating the second config file as simple as copying and renaming the dovecot.conf file? >>>>> >>>>> On Sep 23, 2014, at 2:26 PM, Eduardo Ramos wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> In fact you don't NEED a director. You can use two dovecot servers sharing a NFS storage with a normal (backend) implementation. It's good to see that page: http://wiki2.dovecot.org/NFS for some good recomendations. >>>>>> >>>>>> You must have a base_dir for each instance of dovecot you want to run, and a dovecot.conf as well. One could be director and other backend. I suggest you have two separated configuration directories, /etc/dovecot-director and /etc/dovecot-backend. Each with the respective configuration. Start dovecot with "dovecot -c /etc/dovecot-director/dovecot.conf". Backend is the same. >>>>>> >>>>>> In order to help more, provide us more details about your environment and doulbts. >>>>>> >>>>>> On 09/23/2014 03:57 PM, jjhoffart wrote: >>>>>>> Hello, >>>>>>> I am currently trying to setup a cluster of mail servers. I currently have two servers I am trying to cluster together. These servers will also have a shared NFS backend. I have read on the site that I will need to configure director since I am using NFS. I have read through all of the documentation on director but still need a little guidance to get things up and running. One of the questions I have is about the base_dir on the Multiple Invocations section of the wiki. It states that I will need to change the bas_dir to the new run directory, not sure what needs to happen here, can anyone help me out? From ryan at bluemoon.outputservices.com Fri Sep 19 18:57:27 2014 From: ryan at bluemoon.outputservices.com (Dave Ryan) Date: Fri, 19 Sep 2014 12:57:27 -0600 (MDT) Subject: LDAP and dovecot Message-ID: <201409191857.s8JIvRw0000456@bluemoon.outputservices.com> Thank you all for your assistance. I was able to locate another web site that mentioned I needed to compile dovecot with my openldap libraries. I then compiled dovecot in the following manner: CPPFLAGS=-I/usr/local/openldap/include \ LDFLAGS='-L/usr/local/openldap/lib -R/usr/local/openldap/lib' \ ./configure --prefix=/tmp/tocevod --with-ssl=openssl --with-solr --with-zlib --with-bzlib --with-ldap=yes This then included the openldap libraries. I tested access and now it works. ldd on /dovecot/libexec/dovecot/auth showed the openldap libraries. libdovecot.so.0 => /usr/local/tools/dovecot/lib/dovecot/libdovecot.so.0 libpam.so.1 => /usr/lib/libpam.so.1 libldap-2.4.so.2 => /usr/local/openldap/lib/libldap-2.4.so.2 libsasl.so.1 => /usr/lib/libsasl.so.1 libssl.so.0.9.7 => /usr/sfw/lib/libssl.so.0.9.7 libcrypto.so.0.9.7 => /usr/sfw/lib/libcrypto.so.0.9.7 liblber-2.4.so.2 => /usr/local/openldap/lib/liblber-2.4.so.2 libresolv.so.2 => /usr/lib/libresolv.so.2 libgen.so.1 => /usr/lib/libgen.so.1 librt.so.1 => /usr/lib/librt.so.1 libnsl.so.1 => /usr/lib/libnsl.so.1 libsocket.so.1 => /usr/lib/libsocket.so.1 libsendfile.so.1 => /usr/lib/libsendfile.so.1 libc.so.1 => /usr/lib/libc.so.1 libgcc_s.so.1 => /usr/sfw/lib/libgcc_s.so.1 libcmd.so.1 => /usr/lib/libcmd.so.1 libmd.so.1 => /usr/lib/libmd.so.1 libaio.so.1 => /usr/lib/libaio.so.1 libmp.so.2 => /usr/lib/libmp.so.2 libscf.so.1 => /usr/lib/libscf.so.1 libdoor.so.1 => /usr/lib/libdoor.so.1 libuutil.so.1 => /usr/lib/libuutil.so.1 libssl_extra.so.0.9.7 => /usr/sfw/lib/libssl_extra.so.0.9.7 libcrypto_extra.so.0.9.7 => /usr/sfw/lib/libcrypto_extra.so.0.9.7 libm.so.2 => /usr/lib/libm.so.2 Thanks again. From tss at iki.fi Fri Sep 26 21:28:27 2014 From: tss at iki.fi (Timo Sirainen) Date: Sat, 27 Sep 2014 00:28:27 +0300 Subject: doveadm penalty: who is 0.0.0.0? In-Reply-To: <54216809.8060709@heinlein-support.de> References: <54216809.8060709@heinlein-support.de> Message-ID: <2ECB4A61-4DF0-4C6C-8BA3-F97BEF3F45A6@iki.fi> On 23 Sep 2014, at 15:31, Peer Heinlein wrote: > > Using doveadm penalty I just noticed a penalty for 0.0.0.0. > > Is this Postfix querying the auth-socket for his SASL-requests? Most likely. 0.0.0.0 would in any case mean "unknown". It shouldn't show up in penalty though.. From jtam.home at gmail.com Fri Sep 26 23:21:32 2014 From: jtam.home at gmail.com (Joseph Tam) Date: Fri, 26 Sep 2014 16:21:32 -0700 (PDT) Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: References: Message-ID: "Klaipedaville on Google" writes: > However, my header_checks file has just 5 lines of regexp as follows: > ... > /^From:.*\@.*\.tw/ REJECT Sorry, Taiwanese mail is not allowed. Can't speak about the other issues you are having, but is this regexp pattern what you want? Unless Postfix PCRE automatically right-anchors these regexps, aren't you rejecting mail from someone at mail.twinpeaks.org, or even twitter notifications (from *@bounce.twitter.com). Joseph Tam From jtam.home at gmail.com Fri Sep 26 23:30:48 2014 From: jtam.home at gmail.com (Joseph Tam) Date: Fri, 26 Sep 2014 16:30:48 -0700 (PDT) Subject: Is dovecot vulnerable to the shellshock/CVE-2014-6271 exploit? In-Reply-To: References: Message-ID: Timo Sirainen writes: >> Although I don't use it, it's plausible the checkpassword hook is also vulnerable >> via the MASTER_USER environment variable: >> >> http://wiki2.dovecot.org/AuthDatabase/CheckPassword > > This is one possibility, and it's the worst one because it could happen > before login. But it requires two things: > > 1. auth_username_chars setting must include the characters required in > the exploit, so "(){;" at least I guess. None of these characters are > enabled by default. But I think some people may have set this setting > to empty to allow all characters. > > 2. checkpassword must call bash, which also isn't done by default. > > Another possibility is is that in some setups the password (%w) may be > added to userdb fields, which ends up being exported to environment if > post-login scripts are used. Again Dovecot doesn't execute shell > automatically, but it may end up being executed by the configuration. > So this requires a valid username + password, and ability to change the > password to the bash exploit. Thanks for confirming what I suspected, Timo. The latter, if it is at all feasible, appears to be an "inside job" type of exploit, where the exploiter already has an account but can arbitrarily change their password. It's not as serious as the pre-login one, but worth addressing if the narrow circumstances of using post-login bash scripts apply. Joseph Tam From r at sys4.de Sat Sep 27 09:41:58 2014 From: r at sys4.de (Ralf Hildebrandt) Date: Sat, 27 Sep 2014 11:41:58 +0200 Subject: ALT storage question Message-ID: <20140927094158.GA17784@sys4.de> I want to migrate from a non-hashed storage to a hashed storage. So I set this up: mail_location = mdbox:/srv/vmail/%2.256Hu/%Lu/mdbox:ALT=/srv/vmail/%Ld/%Ln/mdbox I rsynced the "old" mdbox-style mailbox from another machine to to /srv/vmail/%Ld/%Ln/mdbox (/srv/vmail/charite.de/ralf.hildebrandt/mdbox in my case) The mail_location /srv/vmail/c5/ralf.hildebrandt at charite.de was non-existing. Then I connected using IMAP and tried to have a look at the INBOX: Sep 27 11:15:15 imap(ralf.hildebrandt at charite.de): Debug: Effective uid=10000, gid=10000, home=/srv/vmail/c5/ralf.hildebrandt at charite.de Sep 27 11:15:15 imap(ralf.hildebrandt at charite.de): Debug: Home dir not found: /srv/vmail/c5/ralf.hildebrandt at charite.de Sep 27 11:15:15 imap(ralf.hildebrandt at charite.de): Debug: Namespace inbox: type=private, prefix=, sep=., inbox=yes, hidden=no, list=yes, subscriptions=yes location=mdbox:/srv/vmail/c5/ralf.hildebrandt at charite.de/mdbox:ALT=/srv/vmail/charite.de/ralf.hildebrandt/mdbox Sep 27 11:15:15 imap(ralf.hildebrandt at charite.de): Debug: fs: root=/srv/vmail/c5/ralf.hildebrandt at charite.de/mdbox, index=, indexpvt=, control=, inbox=, alt=/srv/vmail/charite.de/ralf.hildebrandt/mdbox Sep 27 11:15:15 imap(ralf.hildebrandt at charite.de): Debug: Namespace : /srv/vmail/c5/ralf.hildebrandt at charite.de/mdbox doesn't exist yet, using default permissions Sep 27 11:15:15 imap(ralf.hildebrandt at charite.de): Debug: Namespace : Using permissions from /srv/vmail/c5/ralf.hildebrandt at charite.de/mdbox: mode=0700 gid=default Sep 27 11:15:15 imap(ralf.hildebrandt at charite.de): Debug: Namespace : /srv/vmail/c5/ralf.hildebrandt at charite.de/mdbox/mailboxes/INBOX doesn't exist yet, using default permissions Sep 27 11:15:15 imap(ralf.hildebrandt at charite.de): Debug: Namespace : Using permissions from /srv/vmail/c5/ralf.hildebrandt at charite.de/mdbox: mode=0700 gid=default Sep 27 11:15:15 imap(ralf.hildebrandt at charite.de): Error: Mailbox INBOX has existing files in alt path, rebuilding storage to avoid losing messages Sep 27 11:15:15 imap(ralf.hildebrandt at charite.de): Error: Failed to autocreate mailbox INBOX: Internal error occurred. Refer to server log for more information. [2014-09-27 11:15:15] Sep 27 11:15:15 imap(ralf.hildebrandt at charite.de): Warning: fscking index file /srv/vmail/c5/ralf.hildebrandt at charite.de/mdbox/storage/dovecot.map.index Sep 27 11:15:15 imap(ralf.hildebrandt at charite.de): Info: Disconnected: Logged out in=58 out=623 What is "Mailbox INBOX has existing files in alt path, rebuilding storage to avoid losing messages" referring to? And why is this an error? After all that I reconnect, just to find an empty inbox. WTF? Why is the ALT storage being ignored? The ALT storage contains: total 8 drwxr-xr-x 6 vmail vmail 4096 Aug 18 15:25 mailboxes drwxr-xr-x 2 vmail vmail 4096 Sep 24 00:37 storage and those two directories contain: mailboxes: total 16 drwxr-xr-x 3 vmail vmail 4096 Aug 18 15:25 Drafts drwxr-xr-x 3 vmail vmail 4096 Aug 18 15:25 INBOX drwxr-xr-x 3 vmail vmail 4096 Aug 18 15:25 Sent drwxr-xr-x 3 vmail vmail 4096 Aug 18 15:25 Trash storage: -rw-r--r-- 1 vmail vmail 3552 Sep 25 14:47 dovecot.map.index.log -rw-r--r-- 1 vmail vmail 20015 Sep 25 13:51 m.1 On the other hand, just moving /srv/vmail/charite.de/ralf.hildebrandt/mdbox to /srv/vmail/c5/ralf.hildebrandt at charite.de worked like a charm! -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From klaipedaville at gmail.com Sat Sep 27 09:48:11 2014 From: klaipedaville at gmail.com (Klaipedaville on Google) Date: Sat, 27 Sep 2014 12:48:11 +0300 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <5425946D.70103@integrafin.co.uk> References: <54255249.70707@integrafin.co.uk><23D946DB1F134A2CB613C8F8E22144BC@Computer><99622F1A0F1241308D93744D9E12D5EF@Computer> <54256B7E.6060703@integrafin.co.uk><7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer><54257CF5.8060404@integrafin.co.uk><8F9EE935A5B5471F88FF0D952C071A49@Computer> <542582E7.1060406@integrafin.co.uk> <94487CE07C4446C29BA2FAC6C96D17DF@Computer> <5425946D.70103@integrafin.co.uk> Message-ID: <5BD1A598E6BF4BA6882C640A44ABEDDE@Computer> >Alex: >One *very* convincing argument not to send an *email* response (reject at SMTP is fine) is that it is very likely indeed you'll end up on an RBL yourself for doing this. It happened to us when we were still bouncing (probably >about 8-10 years ago). It was the main reason we stopped. > >Reindl, >I respecfully disagree with (a) at least for the UK. It may be the case in Germany but I'll be damned if I'm going to give up on my Mailscanner - tuned over the years enough that we've never had a legit mail get canned. > >Anyway, that's enough for me otherwise this is going to turn into a flamewar rather than informational. It is really convincing but if you do it right I guess you should be safe . Well, bouncing it all bluntly like shooting from a machine gun absolutely everywhere at random will certainly put you on RBL. How about checking it first if the sender's email address really exists and only then either bounce back (it the address exists) or do not bounce it back if it doesn't. You were the one to tell me in your previous messages to comply with RFC first that is to check for forged envelope senders first. That?s why I have been bouncing it back (rejecting) for the past 4 years and have never ever hit any RBLs at all. From klaipedaville at gmail.com Sat Sep 27 10:01:01 2014 From: klaipedaville at gmail.com (Klaipedaville on Google) Date: Sat, 27 Sep 2014 13:01:01 +0300 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <54259704.8070202@thelounge.net> References: <54255249.70707@integrafin.co.uk> <23D946DB1F134A2CB613C8F8E22144BC@Computer> <99622F1A0F1241308D93744D9E12D5EF@Computer> <54256B7E.6060703@integrafin.co.uk> <7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer> <54257CF5.8060404@integrafin.co.uk> <8F9EE935A5B5471F88FF0D952C071A49@Computer> <542582E7.1060406@integrafin.co.uk> <94487CE07C4446C29BA2FAC6C96D17DF@Computer> <54258CE3.9030504@thelounge.net> <54259704.8070202@thelounge.net> Message-ID: <52E89326163140D1BFE0DDE6A544C3B6@Computer> >Reindl: >that's no problem because with RBL weighting and postscreen you reject 95% of the crap before it ever touchs smtpd or even the contentfilter that stats below are about a maillog starting with Sep 18 19:50:39 >for some hundrest domains and currently 2000 valid RCPT, if the contentfilter has to handle most of your incoming flow you made a mistake by not reject earlier with "cheaper" methods >___________________________________________________ > >that part never touched the contentfilter > >Invalid User: 3074 >Disallowed User: 2 >Reject Postscreen: 148451 >Reject Postfix: 6225 >Blacklist: 144880 >Pregreet: 5143 >Protocol Error: 1607 >Helo: 190 >Sender Blocked: 200 >Sender Invalid: 229 >Sender Spoofed: 847 >PTR Missing: 1347 >PTR Generic: 319 >___________________________________________________ > >Connections: 185848 >Delivered: 20293 >Invalid User: 3074 >Disallowed User: 2 >Reject Postscreen: 148451 >Reject Postfix: 6225 >Reject Temporary: 507 >Blacklist: 144880 >Pregreet: 5143 >Protocol Error: 1607 >Spamfilter: 2297 >Virus: 115 >Helo: 190 >Subject: 42 >Attachment: 0 >Sender Blocked: 200 >Sender Invalid: 229 >Sender Spoofed: 847 >PTR Missing: 1347 >PTR Generic: 319 That sounds interesting. Since you are German and most probably are an expert on before-queue filtering could you advise if it is actually possible to use both before-queue and after-queue filtering? Since it is the Dovecot list I would be curious to know how to do it Dovecot Sieve way. That is my Postfix passes it over to Dovecot for delivery but all the milters work with Postfix directly and my passing delivery over to Dovecot should theoretically simply disable any before-queue filters. I ran a few tests and it did not work for the reason I have just mentioned, because it is piped to dovecot. From klaipedaville at gmail.com Sat Sep 27 10:49:09 2014 From: klaipedaville at gmail.com (Klaipedaville on Google) Date: Sat, 27 Sep 2014 13:49:09 +0300 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: References: Message-ID: >Joseph Tam writes: > > However, my header_checks file has just 5 lines of regexp as follows: > ... > /^From:.*\@.*\.tw/ REJECT Sorry, Taiwanese mail is not allowed. > >Can't speak about the other issues you are having, but is this regexp pattern what you want? Unless Postfix PCRE automatically right-anchors these regexps, aren't you rejecting mail from someone at mail.twinpeaks.org, >or even twitter notifications (from *@bounce.twitter.com). I am not sure I even understand what you were trying to say. It's either because you have no idea how to write any regexp / pcre rules or I did not understand your wording. The rule means: / means a regular expression. Any regular expression is enclosed in forward slashes. For example /Josepsh/ is already the simplest rule in regexp and pcre. ^ it is called caret and indicates the beginning of a line / expression From: is the field I refer to . means any character * matches zero or any number of occurrences of the previous character \ it's called escape that treats any character after it as a regular character (item), not regexp tw means two letters at the end of an email address for example mail at example.tw What it basically does it blocks any email address that ends on .tw Plus, if you refer to the post I wrote it clearly says that running the following on your command line postmap ?q "From: mail at example.tw? regexp:/etc/postfix/header_checks will tell you if the rule is correct or not. This is a bullet / fool proof method. The file called header_checks has to exist of course and it has to contain the rule mentioned above. Plus, I also said in my post that regexp were not the problem in my case at all as it literally takes only 5 seconds and has a couple of dozen various methods to check if the rules are correct or not despite the fact that they come from "stone age" computing like I do myself as well. Honestly speaking it was funny to see how so many people started picking on regexpes in the first place without actually having any clear understanding about how they work. -------------- next part -------------- A non-text attachment was scrubbed... Name: wlEmoticon-smile[1].png Type: image/png Size: 1046 bytes Desc: not available URL: From h.reindl at thelounge.net Sat Sep 27 11:16:40 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Sat, 27 Sep 2014 13:16:40 +0200 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <52E89326163140D1BFE0DDE6A544C3B6@Computer> References: <54255249.70707@integrafin.co.uk> <23D946DB1F134A2CB613C8F8E22144BC@Computer> <99622F1A0F1241308D93744D9E12D5EF@Computer> <54256B7E.6060703@integrafin.co.uk> <7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer> <54257CF5.8060404@integrafin.co.uk> <8F9EE935A5B5471F88FF0D952C071A49@Computer> <542582E7.1060406@integrafin.co.uk> <94487CE07C4446C29BA2FAC6C96D17DF@Computer> <54258CE3.9030504@thelounge.net> <54259704.8070202@thelounge.net> <52E89326163140D1BFE0DDE6A544C3B6@Computer> Message-ID: <54269C98.9090800@thelounge.net> Am 27.09.2014 um 12:01 schrieb Klaipedaville on Google: >> Reindl: >> that's no problem because with RBL weighting and postscreen you reject 95% of the crap before it ever touchs smtpd or even the contentfilter that stats below are about a maillog starting with Sep 18 19:50:39 >> for some hundrest domains and currently 2000 valid RCPT, if the contentfilter has to handle most of your incoming flow you made a mistake by not reject earlier with "cheaper" methods > > That sounds interesting. Since you are German and most probably > are an expert on before-queue filtering could you advise if it > is actually possible to use both before-queue and after-queue > filtering? surely but how does that make sense? > Since it is the Dovecot list I would be curious to know > how to do it Dovecot Sieve way. doing *what*? > That is my Postfix passes it over to Dovecot for delivery but all the milters > work with Postfix directly and my passing delivery over to Dovecot should > theoretically simply disable any before-queue filters that's just impossible you can't control a before-queue filter that way because, well, he is before-queue and has no idea what later happens with that message -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From bart.nogas at gmail.com Sat Sep 27 11:46:44 2014 From: bart.nogas at gmail.com (=?UTF-8?B?QmFydMWCb21pZWogTm9nYcWb?=) Date: Sat, 27 Sep 2014 13:46:44 +0200 Subject: GETMETADATA UTF8 encoding of folder names instead of UTF7 Message-ID: Hello, I have dovecot 2.2.13 instance and I found that (at least for polish language) folder names in GETMETADATA command response are encoded in UTF8. Shouldn't it be converted to UTF7? Both SETMETADATA and GETMETADATA arguments have to be encoded in UTF7, the problem(?) is related only to server response example: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE AUTH=PLAIN AUTH=LOGIN] Dovecot ready. . login user pass . OK [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 METADATA QUOTA ACL RIGHTS=texk] Logged in . GETMETADATA "INBOX/&AVs-olaris" (/private/vendor/kolab/folder-type /shared/vendor/kolab/folder-type) * METADATA {14} INBOX/?olaris (/private/vendor/kolab/folder-type NIL /shared/vendor/kolab/folder-type {4} mail) . OK Getmetadata completed. "INBOX/?olaris" - UTF8 Best Regards, From acrow at integrafin.co.uk Sat Sep 27 12:56:34 2014 From: acrow at integrafin.co.uk (Alex Crow) Date: Sat, 27 Sep 2014 13:56:34 +0100 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: References: Message-ID: <5426B402.8000203@integrafin.co.uk> On 27/09/14 11:49, Klaipedaville on Google wrote: >> Joseph Tam writes: >> >> However, my header_checks file has just 5 lines of regexp as follows: >> ... >> /^From:.*\@.*\.tw/ REJECT Sorry, Taiwanese mail is not allowed. >> >> Can't speak about the other issues you are having, but is this regexp pattern what you want? Unless Postfix PCRE automatically right-anchors these regexps, aren't you rejecting mail from someone at mail.twinpeaks.org, >> or even twitter notifications (from *@bounce.twitter.com). > I am not sure I even understand what you were trying to say. It's either because you have no idea how to write any regexp / pcre rules I don't understand why you seem to think there is some kind of magical interaction between postfix and dovecot. Once postfix passes to the Dovecot LDA that's the end of its responsibility. Likewise dovecot has no inside knowledge of that Postfix does. Certainly in grep that /would/ match ,eg, foo at bar.twister.com because as Joseph said the .tw is not anchored to the end of the pattern. Now whether this applies in headerchecks is not for this list. if it was ^From:.*\@.*\.tw$ it would not. And again according to the man page, $ is usable: "/^(.*)-outgoing@(.*)$/" You seem to think that you are the worlds greatest regexp expert and to be frank it comes off as a bit arrogant. Alex From klaipedaville at gmail.com Sat Sep 27 13:04:09 2014 From: klaipedaville at gmail.com (Klaipedaville on Google) Date: Sat, 27 Sep 2014 16:04:09 +0300 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <54269C98.9090800@thelounge.net> References: <54255249.70707@integrafin.co.uk> <23D946DB1F134A2CB613C8F8E22144BC@Computer> <99622F1A0F1241308D93744D9E12D5EF@Computer> <54256B7E.6060703@integrafin.co.uk> <7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer> <54257CF5.8060404@integrafin.co.uk> <8F9EE935A5B5471F88FF0D952C071A49@Computer> <542582E7.1060406@integrafin.co.uk> <94487CE07C4446C29BA2FAC6C96D17DF@Computer> <54258CE3.9030504@thelounge.net> <54259704.8070202@thelounge.net><52E89326163140D1BFE0DDE6A544C3B6@Computer> <54269C98.9090800@thelounge.net> Message-ID: <1C117C267C9F4534944774D798B2753C@Computer> >...could you advise if it is actually possible to use both before-queue and after-queue filtering? > Reindl >surely but how does that make sense? It makes because it will use two filters, not just one. It will filter before queue first and then anything that may be missed or let through on purpose will be filtered after queue by the second filter. > Since it is the Dovecot list I would be curious to know how to do it Dovecot Sieve way. >doing *what*? Making two filters work together (dovecot after-queue and postfix before-queue). > That is my Postfix passes it over to Dovecot for delivery but all the milters work with Postfix directly and my passing delivery over to Dovecot should theoretically simply disable any before-queue filters >that's just impossible It is technically and theoretically impossible as far as I understand but I thought that I also could be wrong at some point and there were ways to arrange it somehow... that?s why I asked away. >you can't control a before-queue filter that way because, well, he is before-queue and has no idea what later happens with that message. I wouldn?t care what the before-queue would be up to as long as they would "cooperate" together with the after-queue one. That is I would create different rules for "before" and for "after" filters making sure that the rules do not clash, conflict, or contradict with each other in any way. But then again my delivery is done by either Postfix with filters or Dovecot with filters and I am unable to use both. That's actually how my current settings on this server I was setting up work. Postfix uses its regexp header_checks without any filters and it works just fine, then it is passed over to Dovecot for delivery where Spamassassin filters kick in and do their job on top. Thus I have two "spam stoppers" so to speak. The advantage is that I can use both regexp / pcre in Postfix and sieve scripting in Dovecot Sieve. From h.reindl at thelounge.net Sat Sep 27 13:14:24 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Sat, 27 Sep 2014 15:14:24 +0200 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <1C117C267C9F4534944774D798B2753C@Computer> References: <54255249.70707@integrafin.co.uk> <23D946DB1F134A2CB613C8F8E22144BC@Computer> <99622F1A0F1241308D93744D9E12D5EF@Computer> <54256B7E.6060703@integrafin.co.uk> <7D8EB46C4EC24D02B6F8EC3CE8C9C091@Computer> <54257CF5.8060404@integrafin.co.uk> <8F9EE935A5B5471F88FF0D952C071A49@Computer> <542582E7.1060406@integrafin.co.uk> <94487CE07C4446C29BA2FAC6C96D17DF@Computer> <54258CE3.9030504@thelounge.net> <54259704.8070202@thelounge.net> <52E89326163140D1BFE0DDE6A544C3B6@Computer> <54269C98.9090800@thelounge.net> <1C117C267C9F4534944774D798B2753C@Computer> Message-ID: <5426B830.3010003@thelounge.net> Am 27.09.2014 um 15:04 schrieb Klaipedaville on Google: >> ...could you advise if it is actually possible to use both before-queue and after-queue filtering? >> Reindl >> surely but how does that make sense? > > It makes because it will use two filters, not just one. > It will filter before queue first and then anything that may be missed it don't having sa-milter, clamav-milter, postscreen, PTR/HELO checks is all before queue there is not much left.... > or let through on purpose will be filtered after queue by the second filter that's not possible except the milter itself has whitelists which are triggered you need to realize that if a reject before queue was triggered there is nothing happing after because there just exists no queue at all >> Since it is the Dovecot list I would be curious to know how to do it Dovecot Sieve way. > >> doing *what*? > > Making two filters work together (dovecot after-queue and postfix before-queue). it's not the job of dovecot at all >> That is my Postfix passes it over to Dovecot for delivery but all the milters work with Postfix directly and my passing delivery over to Dovecot should theoretically simply disable any before-queue filters > >> that's just impossible > > It is technically and theoretically impossible technically you can't even have a DNSWL before a milter you only can have other thins rejecting on meta-data and stop the milter overhead because a decision is already made >> you can't control a before-queue filter that way because, well, he is before-queue and has no idea what later happens with that message. > > I wouldn?t care what the before-queue would be up to as long as they > would "cooperate" together with the after-queue there is no "cooperate" - if the milter rejects it's rejected if a PTR check rejectes it is rejected no layer after that will get in touch with the message that's the idea of having several layers and try to get the cheaper ones in front - frankly after postscreen if correctly used the layers after only face 5-10% of all incoming mail -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From klaipedaville at gmail.com Sat Sep 27 13:16:22 2014 From: klaipedaville at gmail.com (Klaipedaville on Google) Date: Sat, 27 Sep 2014 16:16:22 +0300 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <5426B402.8000203@integrafin.co.uk> References: <5426B402.8000203@integrafin.co.uk> Message-ID: <3C5DA4DB57B54E9B848DB3C14409438C@Computer> >Alex: >if it was > >^From:.*\@.*\.tw$ >it would not. $ is optional and it only means the end of expression, the rule works either with or without it in the problem I was trying to solve. >And again according to the man page, $ is usable: >"/^(.*)-outgoing@(.*)$/" This is again an option ($), not a must, the rule would be valid either way. >You seem to think that you are the worlds greatest regexp expert and to >be frank it comes off as a bit arrogant. >Alex I am not the world greatest regexp expert but definitely not the worst one. My rules work the way I want and need them to work. Period. I have neither time no desire to prove that 2+2=4. I will not clutter this list speaking off Dovecot issues any more as I feel sorry for time wasted for list readers From h.reindl at thelounge.net Sat Sep 27 13:18:09 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Sat, 27 Sep 2014 15:18:09 +0200 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: References: Message-ID: <5426B911.3090600@thelounge.net> Am 27.09.2014 um 12:49 schrieb Klaipedaville on Google: >> Joseph Tam writes: >> >> However, my header_checks file has just 5 lines of regexp as follows: >> ... >> /^From:.*\@.*\.tw/ REJECT Sorry, Taiwanese mail is not allowed. >> >> Can't speak about the other issues you are having, but is this regexp pattern what you want? Unless Postfix PCRE automatically right-anchors these regexps, aren't you rejecting mail from someone at mail.twinpeaks.org, >> or even twitter notifications (from *@bounce.twitter.com) > > I am not sure I even understand what you were trying to say. > It's either because you have no idea how to write any regexp the only one having no clue are you (bseides wrong mailing-list) /^From:.*\@.*\.tw/ is bullshit and matches twitter.com and so on /^From:.*\@.*\.tw$/ at least would make sure it *ends with* tw frankly your rule matchs *anything* having a @ and .tw -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From h.reindl at thelounge.net Sat Sep 27 13:28:05 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Sat, 27 Sep 2014 15:28:05 +0200 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <3C5DA4DB57B54E9B848DB3C14409438C@Computer> References: <5426B402.8000203@integrafin.co.uk> <3C5DA4DB57B54E9B848DB3C14409438C@Computer> Message-ID: <5426BB65.7080507@thelounge.net> Am 27.09.2014 um 15:16 schrieb Klaipedaville on Google: >> Alex: >> if it was >> >> ^From:.*\@.*\.tw$ >> it would not. > $ is optional and it only means the end of expression, the rule works either with or without it in the problem I was trying to solve. > >> And again according to the man page, $ is usable: > >> "/^(.*)-outgoing@(.*)$/" > > This is again an option ($), not a must, the rule would be valid either way. you are a ignorant fool ____________________________________________________________________________ [root at srv-rhsoft:~]$ postmap -q "From: bla at bla.tw" regexp:/home/harry/Desktop/bla.cf REJECT [root at srv-rhsoft:~]$ postmap -q "From: bla at bla.twitter" regexp:/home/harry/Desktop/bla.cf REJECT [root at srv-rhsoft:~]$ cat /home/harry/Desktop/bla.cf /^From:.*\@.*\.tw/ REJECT ____________________________________________________________________________ [root at srv-rhsoft:~]$ postmap -q "From: bla at bla.tw" regexp:/home/harry/Desktop/bla.cf REJECT [root at srv-rhsoft:~]$ postmap -q "From: bla at bla.twitter" regexp:/home/harry/Desktop/bla.cf [root at srv-rhsoft:~]$ cat /home/harry/Desktop/bla.cf /^From:.*\@.*\.tw$/ REJECT ____________________________________________________________________________ >> You seem to think that you are the worlds greatest regexp expert and to >> be frank it comes off as a bit arrogant. knowledge often comes arrogant to ignorant people > I am not the world greatest regexp expert but definitely not the worst one you are the worst one because you argue instead realize your error > My rules work the way I want and need them to work. Period. no they don't damned > I have neither time no desire to prove that 2+2=4 no, but you telling us it's 5 > I will not clutter this list speaking off Dovecot issues any more as I feel sorry for time wasted for list readers please do so -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From acrow at integrafin.co.uk Sat Sep 27 13:34:57 2014 From: acrow at integrafin.co.uk (Alex Crow) Date: Sat, 27 Sep 2014 14:34:57 +0100 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <5426BB65.7080507@thelounge.net> References: <5426B402.8000203@integrafin.co.uk> <3C5DA4DB57B54E9B848DB3C14409438C@Computer> <5426BB65.7080507@thelounge.net> Message-ID: <5426BD01.3040506@integrafin.co.uk> Wasnt that productive? I'm hoping the hubris will lead to some self-realisation later but I doubt it. Also felt like he was testing us, posting regexes for us to look at and then when we pointed out the errors in them suddenly declaring they were deliberate errors for testing! Alex On 27/09/14 14:28, Reindl Harald wrote: > > Am 27.09.2014 um 15:16 schrieb Klaipedaville on Google: >>> Alex: >>> if it was >>> >>> ^From:.*\@.*\.tw$ >>> it would not. >> $ is optional and it only means the end of expression, the rule works either with or without it in the problem I was trying to solve. >> >>> And again according to the man page, $ is usable: >>> "/^(.*)-outgoing@(.*)$/" >> This is again an option ($), not a must, the rule would be valid either way. > you are a ignorant fool > ____________________________________________________________________________ > > [root at srv-rhsoft:~]$ postmap -q "From: bla at bla.tw" regexp:/home/harry/Desktop/bla.cf > REJECT > > [root at srv-rhsoft:~]$ postmap -q "From: bla at bla.twitter" regexp:/home/harry/Desktop/bla.cf > REJECT > > [root at srv-rhsoft:~]$ cat /home/harry/Desktop/bla.cf > /^From:.*\@.*\.tw/ REJECT > ____________________________________________________________________________ > > [root at srv-rhsoft:~]$ postmap -q "From: bla at bla.tw" regexp:/home/harry/Desktop/bla.cf > REJECT > > [root at srv-rhsoft:~]$ postmap -q "From: bla at bla.twitter" regexp:/home/harry/Desktop/bla.cf > > [root at srv-rhsoft:~]$ cat /home/harry/Desktop/bla.cf > /^From:.*\@.*\.tw$/ REJECT > ____________________________________________________________________________ > >>> You seem to think that you are the worlds greatest regexp expert and to >>> be frank it comes off as a bit arrogant. > knowledge often comes arrogant to ignorant people > >> I am not the world greatest regexp expert but definitely not the worst one > you are the worst one because you argue instead realize your error > >> My rules work the way I want and need them to work. Period. > no they don't damned > >> I have neither time no desire to prove that 2+2=4 > no, but you telling us it's 5 > >> I will not clutter this list speaking off Dovecot issues any more as I feel sorry for time wasted for list readers > please do so > From h.reindl at thelounge.net Sat Sep 27 13:43:47 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Sat, 27 Sep 2014 15:43:47 +0200 Subject: Dovecot Sieve and Postfix header_checks Issue In-Reply-To: <5426BD01.3040506@integrafin.co.uk> References: <5426B402.8000203@integrafin.co.uk> <3C5DA4DB57B54E9B848DB3C14409438C@Computer> <5426BB65.7080507@thelounge.net> <5426BD01.3040506@integrafin.co.uk> Message-ID: <5426BF13.8080805@thelounge.net> Am 27.09.2014 um 15:34 schrieb Alex Crow: > Wasnt that productive? i would call it funny :-) > I'm hoping the hubris will lead to some self-realisation later but I doubt it forget it > Also felt like he was testing us, posting regexes for us to look > at and then when we pointed out the errors in them suddenly > declaring they were deliberate errors for testing! i doubt looking at the subject mixing two complete different layers of a mail system points out clueless from the very beginning and every time i say the truth which is "do not run a mailserver without qualification and real understanding" i am the bad ass everywhere such people are responsible for a lot of spam out there because filter out customer-ranges with potential zombies is easy, but mailservers maintained by people lacking the knowledge how to verify that the configuration does what they think is hard there are two ways to run a mailserver * knowing what you are doing * don't do it > On 27/09/14 14:28, Reindl Harald wrote: >> >> Am 27.09.2014 um 15:16 schrieb Klaipedaville on Google: >>>> Alex: >>>> if it was >>>> >>>> ^From:.*\@.*\.tw$ >>>> it would not. >>> $ is optional and it only means the end of expression, the rule works either with or without it in the problem I >>> was trying to solve. >>> >>>> And again according to the man page, $ is usable: >>>> "/^(.*)-outgoing@(.*)$/" >>> This is again an option ($), not a must, the rule would be valid either way. >> you are a ignorant fool >> ____________________________________________________________________________ >> >> [root at srv-rhsoft:~]$ postmap -q "From: bla at bla.tw" regexp:/home/harry/Desktop/bla.cf >> REJECT >> >> [root at srv-rhsoft:~]$ postmap -q "From: bla at bla.twitter" regexp:/home/harry/Desktop/bla.cf >> REJECT >> >> [root at srv-rhsoft:~]$ cat /home/harry/Desktop/bla.cf >> /^From:.*\@.*\.tw/ REJECT >> ____________________________________________________________________________ >> >> [root at srv-rhsoft:~]$ postmap -q "From: bla at bla.tw" regexp:/home/harry/Desktop/bla.cf >> REJECT >> >> [root at srv-rhsoft:~]$ postmap -q "From: bla at bla.twitter" regexp:/home/harry/Desktop/bla.cf >> >> [root at srv-rhsoft:~]$ cat /home/harry/Desktop/bla.cf >> /^From:.*\@.*\.tw$/ REJECT >> ____________________________________________________________________________ >> >>>> You seem to think that you are the worlds greatest regexp expert and to >>>> be frank it comes off as a bit arrogant. >> knowledge often comes arrogant to ignorant people >> >>> I am not the world greatest regexp expert but definitely not the worst one >> you are the worst one because you argue instead realize your error >> >>> My rules work the way I want and need them to work. Period. >> no they don't damned >> >>> I have neither time no desire to prove that 2+2=4 >> no, but you telling us it's 5 >> >>> I will not clutter this list speaking off Dovecot issues any more as I feel sorry for time wasted for list readers >> please do so -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From tim at bastelfreak.de Sun Sep 28 00:48:25 2014 From: tim at bastelfreak.de (Tim) Date: Sun, 28 Sep 2014 02:48:25 +0200 Subject: Corrupted index cache after migrating from maildir to mdbox Message-ID: <54275AD9.2080900@bastelfreak.de> Hi guys, I'm running dovecot/postfix on my Debian Jessie maschine: # dovecot --version 2.2.13 doveconf -n output: http://p.bastelfreak.de/HsVwS/ today I migrated from maildir(located at /var/vmail) to mdbox with these commands: rsync -av -f"+ */" -f"- *" /var/vmail/ /home/vmail/ rm /home/vmail/*/*/Maildir -rf for i in $(doveadm user \*); do u=$(echo $i | cut -d@ -f1); d=$(echo $i |cut -d@ -f2); dsync -v -u $i mirror mdbox:/home/vmail/$d/$u/mdbox; done Then I changed the mail_location to mdbox:/home/vmail/%d/%n/mdbox and did the following commands: service dovecot restart for i in $(doveadm user \*); do u=$(echo $i | cut -d@ -f1); d=$(echo $i |cut -d@ -f2); dsync -v -u $i mirror maildir:/var/vmail/$d/$u/Mail; done doveadm index -A all INBOX for i in $(doveadm user \*); do doveadm -Dv fts rescan -u $i;done unfortunately I'm getting the following two kinds of error messages for all mail boxes in my mail.log: Error: Corrupted index cache file /home/vmail/%domain/%user/mdbox/mailboxes/%maildir/dbox-Mails/dovecot.index.cache: Broken virtual size for mail UID 2564 and: Error: read(/home/vmail/%domain/%user/mdbox/storage/m.108 ): FETCH BODY[] for mailbox %maildir UID 2564 got too little data: 2417 vs 6319 please let me know if you have any suggestions for fixing this issue or if you need more information. kind regards, Tim From alanm at sics.se Sun Sep 28 13:32:59 2014 From: alanm at sics.se (Alan McGinlay) Date: Sun, 28 Sep 2014 15:32:59 +0200 Subject: dsync mirror does not maintain changes between mailboxes Message-ID: Hi, running: dsync -D -v -o mail_fsync=never mirror -R -f -u user at domain imapc: Where "domain" is a cyrus imap server does not do what the documentation says it does, not even close. After the first run to an empty mailbox on the dovecot 2.2.13 server all the mails (1.1GB) seem to be correctly synced. I send a test email to the dovecot server and it shows up correctly. Second run of the above dsync command, first thing that happens is all mails are deleted from the dovecot mailbox (yet the storage used by output of "du -m" doesn't change) and the sync appears to happen again from scratch however the disk space increases again! Now up to about 2GB and another run will take it up a few hundred mb more! I have tried with multiple different mail storage formats, maildir++, mdbox sdbox, all show the same (except maildir which just complains that INBOX can't be deleted on the second dsync run). This is frustrating beyond belief, please please anyone who has any insight let me know, the dsync debug output is a little huge to sanitize and post to the list but i can send it individually if anyone has any ideas! I am ready to give up totally on dovecot but at the same time I just wish it would work! doveconf -n # 2.2.13 (6bb26098a45c): /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-67-virtual x86_64 Ubuntu 14.04.1 LTS auth_debug = yes auth_master_user_separator = * default_vsz_limit = 512 M disable_plaintext_auth = yes imapc_features = rfc822.size imapc_host = oldmailhost.domain.com imapc_master_user = cyradmin imapc_password = xxxxxxxx imapc_user = %u mail_gid = vmail mail_home = /var/vmail/domains/%d/%1n/%n mail_location = sdbox:~/sdbox mail_plugins = zlib notify quota fts fts_solr mail_prefetch_count = 30 mail_uid = vmail mailbox_list_index = yes managesieve_sieve_capability = fileinto imapflags 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 = separator = / } passdb { args = /etc/dovecot/passwd.masterusers driver = passwd-file master = yes pass = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { fts = solr fts_solr = url=http://localhost:8080/solr/ quota = dirsize:User quota quota_grace = 10%% quota_rule = *:storage=20G sieve = ~/.dovecot.sieve sieve_dir = /var/vmail/sieve/domain/%1d/%d/%1n/%n/ sieve_extensions = imapflags fileinto zlib_save = bz2 zlib_save_level = 5 } protocols = imap pop3 lmtp sieve service auth-worker { user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 user = vmail } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } vsz_limit = 512 M } service imap { process_limit = 1024 vsz_limit = 512 M } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } } ssl_cert = Most documents around there talk abour "dsync", but the modern way is "doveadm backup". This command is not documented in the wiki and there are a few details missing, like how to use it thru SSH. I am currently doing some tests about how to backup my mdbox. I can do tests in local using: $ doveadm backup -u jcea -m proveedores/dovecot mdbox:/tmp/aa/ This will "backup" this mailing list mailbox to "/tmp/aa". Good. Lets try thru SSH: $ doveadm backup -u jcea -m proveedores/dovecot ssh 127.0.0.1 dsync -u jcea mdbox:/tmp/aa/ jcea at 127.0.0.1's password: Fatal: Invalid parameter: mdbox:/tmp/aa/ dsync-local(jcea): Error: read(remote) failed: EOF (version not received) How shoudl I do it?. $ doveadm backup -h backup: invalid option -- 'h' doveadm backup [-u |-A] [-S ] [-dfR] [-l ] [-r ] [-m ] [-n | -N] [-x ] [-s ] I can't find any explanation at all about the different parameters of "doveadm backup". Same thing with "doveadm sync". -- Jes?s Cea Avi?n _/_/ _/_/_/ _/_/_/ jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From jcea at jcea.es Sun Sep 28 22:35:39 2014 From: jcea at jcea.es (Jesus Cea) Date: Mon, 29 Sep 2014 00:35:39 +0200 Subject: dsync full sync In-Reply-To: <5404698A.10605@atifceylan.com> References: <5404698A.10605@atifceylan.com> Message-ID: <54288D3B.1020307@jcea.es> On 01/09/14 14:41, At?f CEYLAN wrote: > Hi all, > I have 2 question. > > First: > I use dovecot (version 2.2.9) with mdbox mail format. When I run dsync > tool with "mirror" or "backup" parameters my source and destination > directory synchronize correctly but if I delete some messages in user > mailbox, deleted messages does not synced to destination. Had you tried running "doveadm purge" in the destination?. -- Jes?s Cea Avi?n _/_/ _/_/_/ _/_/_/ jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From jcea at jcea.es Mon Sep 29 00:15:23 2014 From: jcea at jcea.es (Jesus Cea) Date: Mon, 29 Sep 2014 02:15:23 +0200 Subject: "doveadm backup/sync" are badly documented (SOLVED AND BUG REPORT!) In-Reply-To: <54288323.6040801@jcea.es> References: <54288323.6040801@jcea.es> Message-ID: <5428A49B.3010306@jcea.es> On 28/09/14 23:52, Jesus Cea wrote: [..] > This will "backup" this mailing list mailbox to "/tmp/aa". Good. Lets > try thru SSH: > > $ doveadm backup -u jcea -m proveedores/dovecot ssh 127.0.0.1 dsync -u > jcea mdbox:/tmp/aa/ > jcea at 127.0.0.1's password: > Fatal: Invalid parameter: mdbox:/tmp/aa/ > dsync-local(jcea): Error: read(remote) failed: EOF (version not received) > > How shoudl I do it?. Trying a few things I got here, that works: $ doveadm -o mail_fsync=never -o mdbox_rotate_interval=99d -o mdbox_rotate_size=10M -o mail_attachment_dir=/tmp/aa/attachments -o mail_attachment_min_size=64k -o mail_attachment_hash=%{sha256} -o mail_location=mdbox:/tmp/aa/:DIRNAME=XxX backup -m 'varios/nosotros' -R ssh 127.0.0.1 doveadm dsync-server Two things: 1. I am connecting to myself thru SSH. I want to do a copy of my mdbox with a different configuration. I was not able to transfer that configuration change to thru SSH, so I just reverse the data flow direction (The "-R"): just connect to the regular mailbox_location and bring data here to be stored with a different configuration. This was a kind of enlightment. 2. You must do "ssh 127.0.0.1 doveadm dsync-server" instead of simply "ssh 127.0.0.1" because you would get this error: bash: dsync-server: command not found dsync-local(jcea): Error: read(remote) failed: EOF (version not received) dsync-local(jcea): Error: Remote command returned error 127: ssh 127.0.0.1 dsync-server I guess dovecot is sending the legacy "dsync-server" instead of the current "doveadm dsync-server". LOOKS LIKE THAT IS A BUG!!. > $ doveadm backup -h > backup: invalid option -- 'h' > doveadm backup [-u |-A] [-S ] [-dfR] [-l ] [-r > ] [-m ] [-n | -N] [-x ] [-s > ] > > I can't find any explanation at all about the different parameters of > "doveadm backup". Please, document. > Same thing with "doveadm sync". -- Jes?s Cea Avi?n _/_/ _/_/_/ _/_/_/ jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From jcea at jcea.es Mon Sep 29 02:00:23 2014 From: jcea at jcea.es (Jesus Cea) Date: Mon, 29 Sep 2014 04:00:23 +0200 Subject: "doveadm backup/sync" don't follow message moving even with MDBOX Message-ID: <5428BD37.3020600@jcea.es> Using mdbox as the storage backend, moving a message from a mailbox to another just update a reference. The message is not fisically moved on the disk. I would expect "dsync" to use this fact when source and destination are mdbox. But it doesn't. Anybody else can confirm?. Any plan to implement it?. Thanks!. -- Jes?s Cea Avi?n _/_/ _/_/_/ _/_/_/ jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From bind at enas.net Mon Sep 29 07:32:59 2014 From: bind at enas.net (Urban Loesch) Date: Mon, 29 Sep 2014 09:32:59 +0200 Subject: Imap: Panic: UID 13737 lost unexpectedly from INBOX Message-ID: <54290B2B.5000804@enas.net> Hi, today I got an panic in imap proccess. Details are: Dovecot Version: ii dovecot-core 2:2.2.13-1~auto+74 amd64 secure POP3/IMAP server - core files ii dovecot-dbg 2:2.2.13-1~auto+74 amd64 secure POP3/IMAP server - debug symbols ii dovecot-imapd 2:2.2.13-1~auto+74 amd64 secure POP3/IMAP server - IMAP daemon ii dovecot-lmtpd 2:2.2.13-1~auto+74 amd64 secure POP3/IMAP server - LMTP server ii dovecot-managesieved 2:2.2.13-1~auto+74 amd64 secure POP3/IMAP server - ManageSieve server ii dovecot-mysql 2:2.2.13-1~auto+74 amd64 secure POP3/IMAP server - MySQL support ii dovecot-pop3d 2:2.2.13-1~auto+74 amd64 secure POP3/IMAP server - POP3 daemon ii dovecot-sieve 2:2.2.13-1~auto+74 amd64 secure POP3/IMAP server - Sieve filters support Logs: Sep 29 08:41:16 mailstoreul. dovecot: imap(sys at domain pid:15160 session:<4ccaeS4EYgDD/uGI>): Panic: UID 13737 lost unexpectedly from INBOX Sep 29 08:41:16 mailstoreul. dovecot: imap(sys at domain pid:15160 session:<4ccaeS4EYgDD/uGI>): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x6cc1f) [0x7f14d02aac1f] -> /usr/lib/dovecot/libdovecot.so.0(+0x6cc7e) [0x7f14d02aac7e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f14d026389e] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(+0xa12e) [0x7f14cea4c12e] -> /usr/lib/dovecot/modules/lib20_virtual_plugin.so(virtual_storage_sync_init+0x8db) [0x7f14cea4d07b] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x33) [0x7f14d05982a3] -> dovecot/imap(imap_sync_init+0x7a) [0x41f92a] -> dovecot/imap() [0x41032e] -> dovecot/imap() [0x410531] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xa577e) [0x7f14d05bb77e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0xc6) [0x7f14d02bbfa6] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x93) [0x7f14d02bcd63] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x9) [0x7f14d02bbe09] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f14d02bbe88] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f14d0268d03] -> dovecot/imap(main+0x298) [0x40c238] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd) [0x7f14cfed1eed] -> dovecot/imap() [0x40c39d] Sep 29 08:41:16 mailstoreul. dovecot: imap(sys at domain pid:15160 session:<4ccaeS4EYgDD/uGI>): Fatal: master: service(imap): child 15160 killed with signal 6 (core dumped) The core dump: (gdb) bt full #0 0x00007f14cfee51a5 in raise () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #1 0x00007f14cfee8420 in abort () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #2 0x00007f14d02aac15 in default_fatal_finish (type=, status=status at entry=0) at failures.c:193 backtrace = 0x253b380 "/usr/lib/dovecot/libdovecot.so.0(+0x6cc1f) [0x7f14d02aac1f] -> /usr/lib/dovecot/libdovecot.so.0(+0x6cc7e) [0x7f14d02aac7e] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f14d026389e] -> /usr/lib/d"... #3 0x00007f14d02aac7e in i_internal_fatal_handler (ctx=0x7fff0f69d7f0, format=, args=) at failures.c:657 status = 0 #4 0x00007f14d026389e in i_panic (format=format at entry=0x7f14cea4f528 "UID %u lost unexpectedly from %s") at failures.c:267 ctx = {type = LOG_TYPE_PANIC, exit_status = 0, timestamp = 0x0} args = {{gp_offset = 24, fp_offset = 48, overflow_arg_area = 0x7fff0f69d8e0, reg_save_area = 0x7fff0f69d820}} #5 0x00007f14cea4c12e in virtual_sync_external_flags (vseq=1250, real_uid=13737, bbox=, bbox=, ctx=, ctx=) at virtual-sync.c:67 flags = kw_names = keywords = #6 0x00007f14cea4d07b in virtual_sync_backend_box_sync (sync_flags=, bbox=0x26071f0, ctx=0x261f200) at virtual-sync.c:975 sync_rec = {seq1 = 5, seq2 = 7, type = MAILBOX_SYNC_TYPE_FLAGS} idx1 = 5 vuid = sync_ctx = 0x268a640 sync_status = {sync_delayed_expunges = 1} idx2 = 11 vseq = 1250 #7 virtual_sync_backend_box (bbox=0x26071f0, ctx=0x261f200) at virtual-sync.c:1106 status = {messages = 0, recent = 0, unseen = 3491983296, uidvalidity = 32532, uidnext = 0, first_unseen_seq = 0, first_recent_uid = 3456139202, last_cached_seq = 32532, highest_modseq = 80, highest_pvt_modseq = 140733451983700, keywords = 0x7, permanent_flags = 3495924087, permanent_keywords = 0, allow_new_keywords = 0, nonpermanent_modseqs = 1, no_modseq_tracking = 0, have_guids = 1, have_save_guids = 0, have_only_guid128 = 0} ret = sync_flags = bbox_index_opened = #8 virtual_sync_backend_boxes (ctx=0x261f200) at virtual-sync.c:1444 bboxes = 0x6 i = count = #9 virtual_sync (flags=0, mbox=0x2611de0) at virtual-sync.c:1542 ctx = index_sync_flags = ret = #10 virtual_storage_sync_init (box=0x2611de0, flags=0) at virtual-sync.c:1562 mbox = 0x2611de0 sync_ctx = ret = 0 #11 0x00007f14d05982a3 in mailbox_sync_init (box=box at entry=0x2611de0, flags=flags at entry=0) at mail-storage.c:1678 _data_stack_cur_id = 4 ctx = #12 0x000000000041f92a in imap_sync_init (client=0x2567f40, box=, imap_flags=imap_flags at entry=0, flags=flags at entry=0) at imap-sync.c:230 ctx = 0x25ff630 __FUNCTION__ = "imap_sync_init" #13 0x000000000041032e in idle_sync_now (box=, ctx=0x2568b40) at cmd-idle.c:146 No locals. #14 0x0000000000410531 in idle_callback (box=, ctx=) at cmd-idle.c:158 client = 0x2567f40 #15 0x00007f14d05bb77e in check_timeout (box=0x267d320) at index-mailbox-check.c:51 ibox = file = 0x0 st = {st_dev = 37633, st_ino = 21496482, st_nlink = 1, st_mode = 33152, st_uid = 1001, st_gid = 1001, __pad0 = 0, st_rdev = 0, st_size = 2500, st_blksize = 4096, st_blocks = 8, st_atim = {tv_sec = 1411943094, tv_nsec = 172171250}, st_mtim = {tv_sec = 1411972876, tv_nsec = 150792601}, st_ctim = {tv_sec = 1411972876, tv_nsec = 150792601}, __unused = {0, 0, 0}} notify = true #16 0x00007f14d02bbfa6 in io_loop_handle_timeouts_real (ioloop=0x2543740) at ioloop.c:410 timeout = 0x261bdd0 item = 0x261bdd0 tv = {tv_sec = 0, tv_usec = 0} tv_call = {tv_sec = 1411972876, tv_usec = 171667} t_id = 3 #17 io_loop_handle_timeouts (ioloop=ioloop at entry=0x2543740) at ioloop.c:423 ---Type to continue, or q to quit--- _data_stack_cur_id = 2 #18 0x00007f14d02bcd63 in io_loop_handler_run_internal (ioloop=ioloop at entry=0x2543740) at ioloop-epoll.c:193 ctx = 0x25443d0 events = 0x0 event = 0x11a list = io = tv = {tv_sec = 0, tv_usec = 281628} events_count = 5 msecs = 282 ret = 0 i = call = __FUNCTION__ = "io_loop_handler_run_internal" #19 0x00007f14d02bbe09 in io_loop_handler_run (ioloop=ioloop at entry=0x2543740) at ioloop.c:488 No locals. #20 0x00007f14d02bbe88 in io_loop_run (ioloop=0x2543740) at ioloop.c:465 __FUNCTION__ = "io_loop_run" #21 0x00007f14d0268d03 in master_service_run (service=0x25435d0, callback=callback at entry=0x420cd0 ) at master-service.c:566 No locals. #22 0x000000000040c238 in main (argc=1, argv=0x2543390) at main.c:410 set_roots = {0x428900, 0x0} login_set = {auth_socket_path = 0x253b048 "\001", postlogin_socket_path = 0x0, postlogin_timeout_secs = 60, callback = 0x420b60 , failure_callback = 0x420870 , request_auth_token = 1} service_flags = storage_service_flags = username = 0x0 c = When did the error happened? I was connected with two clients to the same account. - Thunderbird - Horde 5 Webmail I deleted the mail with the UID 13737 within Horde Webmail. Logs for this operation: The email was deleted by the Horde Webmail: Sep 29 08:40:30 mailstoreul. dovecot: imap(sys at domain pid:32487 session:): flag_change: box=INBOX, uid=13737, msgid=<20140928233719.96BAAE842 at bkp-eloma>, size=3613, from=sys at domain (Cron Daemon) Sep 29 08:40:43 mailstoreul. dovecot: imap(sys at domain pid:33205 session:): expunge: box=INBOX, uid=13737, msgid=<20140928233719.96BAAE842 at bkp-eloma>, size=3613, from=sys at domain (Cron Daemon) The still opened session from Thunderbird gots the error and panics (detailed logs see above): Sep 29 08:41:16 mailstoreul. dovecot: imap(sys at domain pid:15160 session:<4ccaeS4EYgDD/uGI>): Panic: UID 13737 lost unexpectedly from INBOX Thanks and regards Urban Loesch From goetz.reinicke at filmakademie.de Mon Sep 29 08:08:41 2014 From: goetz.reinicke at filmakademie.de (=?UTF-8?B?R8O2dHogUmVpbmlja2UgLSBJVCBLb29yZGluYXRvcg==?=) Date: Mon, 29 Sep 2014 10:08:41 +0200 Subject: Master user and invalid credentials dovecot-2.2.13 Message-ID: <54291389.6060605@filmakademie.de> Hi, I followed the docs from the dovecot wiki (http://wiki2.dovecot.org/Authentication/MasterUsers) and still have some problem: 1. uncommented "!include auth-ldap.conf.ext" in 10-auth.conf 2. htpasswd -b -c -s .... to create user/password for a masteruseruser 3. checked auth-master.conf.ext When I try to test the login, I always get an "invalid credentials" in the logs with auth_debug=yes set. dovecot can read /etc/dovecot/master-users The users are in ldap. The example wiki shows the passwords {SHA1}...., in my password file they are {SHA}.... The "master user" posting in september gave some clues what might be wrong, but did not help to solve my problem. Any suggestions are welcome! Thanks and regards. G?tz -- G?tz Reinicke IT-Koordinator Tel. +49 7141 969 82 420 E-Mail goetz.reinicke at filmakademie.de Filmakademie Baden-W?rttemberg GmbH Akademiehof 10 71638 Ludwigsburg www.filmakademie.de Eintragung Amtsgericht Stuttgart HRB 205016 Vorsitzender des Aufsichtsrats: J?rgen Walter MdL Staatssekret?r im Ministerium f?r Wissenschaft, Forschung und Kunst Baden-W?rttemberg Gesch?ftsf?hrer: Prof. Thomas Schadt -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5481 bytes Desc: S/MIME Cryptographic Signature URL: From rs at sys4.de Mon Sep 29 08:19:37 2014 From: rs at sys4.de (Robert Schetterer) Date: Mon, 29 Sep 2014 10:19:37 +0200 Subject: Master user and invalid credentials dovecot-2.2.13 In-Reply-To: <54291389.6060605@filmakademie.de> References: <54291389.6060605@filmakademie.de> Message-ID: <54291619.5000105@sys4.de> Am 29.09.2014 um 10:08 schrieb G?tz Reinicke - IT Koordinator: > Hi, > > I followed the docs from the dovecot wiki > (http://wiki2.dovecot.org/Authentication/MasterUsers) and still have > some problem: > > 1. uncommented "!include auth-ldap.conf.ext" in 10-auth.conf > 2. htpasswd -b -c -s .... to create user/password for a masteruseruser > 3. checked auth-master.conf.ext > > When I try to test the login, I always get an "invalid credentials" in > the logs with auth_debug=yes set. > > dovecot can read /etc/dovecot/master-users > > The users are in ldap. > > The example wiki shows the passwords {SHA1}...., in my password file > they are {SHA}.... > > The "master user" posting in september gave some clues what might be > wrong, but did not help to solve my problem. > > > Any suggestions are welcome! Thanks and regards. G?tz > hm perhaps this helps https://sys4.de/de/blog/2013/02/11/master-user-dovecot-isp-layout-mit-postfixadmin/ but looks like some password problem what do you use plain/login etc ? http://wiki2.dovecot.org/Authentication/Mechanisms http://wiki2.dovecot.org/Authentication/PasswordSchemes Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From michael.wechner at wyona.com Mon Sep 29 12:53:38 2014 From: michael.wechner at wyona.com (Michael Wechner) Date: Mon, 29 Sep 2014 14:53:38 +0200 Subject: No AUTH PLAIN with dovecot 2.0.19 Message-ID: <54295652.6070205@wyona.com> Hi I have installed the package dovecot-postfix on Ubuntu 12.04 LTS: dovecot --version: 2.0.19 postconf -d | grep version: 2.9.6 and receiving email works very fine, but relaying email does not work. I think the problem is that after STARTTLS the authentication is not being executed 250-AUTH PLAIN 250-AUTH=PLAIN which means using telnet returns telnet mx2.wyona.com 587 Trying 50.116.54.197... Connected to node3.wyona.com. Escape character is '^]'. 220 node3.members.linode.com ESMTP Postfix (Ubuntu) EHLO letscallitevil.com 250-node3.members.linode.com 250-PIPELINING 250-SIZE 10240000 250-VRFY 250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN So far I have used dovecot version 1.2.9, which works very fine, but the configuration /etc/dovecot/dovecot.conf seems to be very different in the case of dovecot version 2.0.19. I have checked all kind of tutorials for several days now, like for example https://help.ubuntu.com/10.04/serverguide/postfix.html but nothing helped. Any pointers or help is very much appreciated. Thanks Michael From h.reindl at thelounge.net Mon Sep 29 13:01:08 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Mon, 29 Sep 2014 15:01:08 +0200 Subject: No AUTH PLAIN with dovecot 2.0.19 In-Reply-To: <54295652.6070205@wyona.com> References: <54295652.6070205@wyona.com> Message-ID: <54295814.5060202@thelounge.net> Am 29.09.2014 um 14:53 schrieb Michael Wechner: > I have installed the package dovecot-postfix on Ubuntu 12.04 LTS: > > dovecot --version: 2.0.19 > postconf -d | grep version: 2.9.6 > > and receiving email works very fine, but relaying email does not work. > > I think the problem is that after STARTTLS the authentication is not > being executed > > 250-AUTH PLAIN > 250-AUTH=PLAIN > > which means using telnet returns telnet is worthless because AUTH is likely announced *after STARTTLS* http://www.postfix.org/postconf.5.html#smtp_sasl_security_options > telnet mx2.wyona.com 587 > Trying 50.116.54.197... > Connected to node3.wyona.com. > Escape character is '^]'. > 220 node3.members.linode.com ESMTP Postfix (Ubuntu) oh my god, another server in the linode-zombie network that's bad neigbourhood and you should avoid a PTR ending with "members.linode.com" which is generic and here blocked because i have never seen any legit mail from Linode but 24 hours each day attacks or spam delivery attempts http://www.mxpolice.com/email-security/importance-of-ptr-records-for-reliable-mail-delivery/ > EHLO letscallitevil.com > 250-node3.members.linode.com > 250-PIPELINING > 250-SIZE 10240000 > 250-VRFY > 250-ETRN > 250-STARTTLS > 250-ENHANCEDSTATUSCODES > 250-8BITMIME > 250 DSN -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From clovis at agr.unicamp.br Mon Sep 29 13:04:27 2014 From: clovis at agr.unicamp.br (Clovis Tristao) Date: Mon, 29 Sep 2014 10:04:27 -0300 Subject: Master user and invalid credentials dovecot-2.2.13 In-Reply-To: <54291389.6060605@filmakademie.de> References: <54291389.6060605@filmakademie.de> Message-ID: <542958DB.7060700@agr.unicamp.br> Hi, As you are performing the tests? Would post the debug log? Cheers, Cl?vis Em 29-09-2014 05:08, G?tz Reinicke - IT Koordinator escreveu: > Hi, > > I followed the docs from the dovecot wiki > (http://wiki2.dovecot.org/Authentication/MasterUsers) and still have > some problem: > > 1. uncommented "!include auth-ldap.conf.ext" in 10-auth.conf > 2. htpasswd -b -c -s .... to create user/password for a masteruseruser > 3. checked auth-master.conf.ext > > When I try to test the login, I always get an "invalid credentials" in > the logs with auth_debug=yes set. > > dovecot can read /etc/dovecot/master-users > > The users are in ldap. > > The example wiki shows the passwords {SHA1}...., in my password file > they are {SHA}.... > > The "master user" posting in september gave some clues what might be > wrong, but did not help to solve my problem. > > > Any suggestions are welcome! Thanks and regards. G?tz -- Clovis Tristao - UNICAMP/Faculdade de Engenharia Agricola Administrador de Redes - Secao de Informatica (SINFO) E-mail: clovis at feagri.unicamp.br http://www.feagri.unicamp.br MSN: clovis_tristao33 at hotmail.com Fone: 55(19) 35211031-35211038-35211047-91173116 From h.reindl at thelounge.net Mon Sep 29 13:07:20 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Mon, 29 Sep 2014 15:07:20 +0200 Subject: No AUTH PLAIN with dovecot 2.0.19 In-Reply-To: <54295814.5060202@thelounge.net> References: <54295652.6070205@wyona.com> <54295814.5060202@thelounge.net> Message-ID: <54295988.9090703@thelounge.net> Am 29.09.2014 um 15:01 schrieb Reindl Harald: > Am 29.09.2014 um 14:53 schrieb Michael Wechner: >> which means using telnet returns > > telnet is worthless because AUTH is likely announced *after STARTTLS* > http://www.postfix.org/postconf.5.html#smtp_sasl_security_options > >> telnet mx2.wyona.com 587 >> Trying 50.116.54.197... >> Connected to node3.wyona.com. >> Escape character is '^]'. >> 220 node3.members.linode.com ESMTP Postfix (Ubuntu) > > oh my god, another server in the linode-zombie network > that's bad neigbourhood and you should avoid a PTR > ending with "members.linode.com" which is generic > and here blocked because i have never seen any legit > mail from Linode but 24 hours each day attacks or > spam delivery attempts > > http://www.mxpolice.com/email-security/importance-of-ptr-records-for-reliable-mail-delivery/ errata, with "node" at the begin: luck /^li[0-9]{1,3}[\.\-][0-9]{1,3}\.members\.linode\.com$/ REJECT Generic DNS-Reverse-Lookup >> EHLO letscallitevil.com >> 250-node3.members.linode.com >> 250-PIPELINING >> 250-SIZE 10240000 >> 250-VRFY >> 250-ETRN >> 250-STARTTLS >> 250-ENHANCEDSTATUSCODES >> 250-8BITMIME >> 250 DSN -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From michael.wechner at wyona.com Mon Sep 29 13:21:41 2014 From: michael.wechner at wyona.com (Michael Wechner) Date: Mon, 29 Sep 2014 15:21:41 +0200 Subject: No AUTH PLAIN with dovecot 2.0.19 In-Reply-To: <54295814.5060202@thelounge.net> References: <54295652.6070205@wyona.com> <54295814.5060202@thelounge.net> Message-ID: <54295CE5.5090101@wyona.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi Harald Thanks very much for your quick reply. Please see my answers inline below Am 29.09.14 15:01, schrieb Reindl Harald: > > Am 29.09.2014 um 14:53 schrieb Michael Wechner: >> I have installed the package dovecot-postfix on Ubuntu 12.04 LTS: >> >> dovecot --version: 2.0.19 >> postconf -d | grep version: 2.9.6 >> >> and receiving email works very fine, but relaying email does not work. >> >> I think the problem is that after STARTTLS the authentication is not >> being executed >> >> 250-AUTH PLAIN >> 250-AUTH=PLAIN >> >> which means using telnet returns > > telnet is worthless because AUTH is likely announced *after STARTTLS* > http://www.postfix.org/postconf.5.html#smtp_sasl_security_options right, but when requesting for example mail.wyona.com, then I can see AUTH telnet mail.wyona.com 587 Trying 195.226.6.75... Connected to mx1.wyona.com. Escape character is '^]'. 220 mail.wyona.com ESMTP Postfix (Ubuntu) EHLO wyona.com 250-mail.wyona.com 250-PIPELINING 250-SIZE 10240000 250-VRFY 250-ETRN 250-STARTTLS 250-AUTH PLAIN 250-AUTH=PLAIN 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN quit 221 2.0.0 Bye Connection closed by foreign host. or also when using ngrep T 195.226.6.75:587 -> 10.10.1.102:58990 [AP] 250-mail.wyona.com..250-PIPELINING..250-SIZE 10240000..250-VRFY..250-ETRN..250-STARTTLS..250-AUTH PLAIN..250-AUTH=PLAIN..250-ENHANCEDSTATUSCODES. .250-8BITMIME..250 DSN.. hence I would assume to see it also for the new version of postfix and dovecot, or do I misunderstand something? > > >> telnet mx2.wyona.com 587 >> Trying 50.116.54.197... >> Connected to node3.wyona.com. >> Escape character is '^]'. >> 220 node3.members.linode.com ESMTP Postfix (Ubuntu) > > oh my god, another server in the linode-zombie network > that's bad neigbourhood and you should avoid a PTR > ending with "members.linode.com" which is generic > and here blocked because i have never seen any legit > mail from Linode but 24 hours each day attacks or > spam delivery attempts > > http://www.mxpolice.com/email-security/importance-of-ptr-records-for-reliable-mail-delivery/ thanks for pointing this out. I have set it now according to https://www.linode.com/docs/networking/dns/adding-dns-records/ and it should work within the next 24 hours (at least that's what linode says). Thanks Michael > > >> EHLO letscallitevil.com >> 250-node3.members.linode.com >> 250-PIPELINING >> 250-SIZE 10240000 >> 250-VRFY >> 250-ETRN >> 250-STARTTLS >> 250-ENHANCEDSTATUSCODES >> 250-8BITMIME >> 250 DSN > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUKVzlAAoJECV0ivYw6bPKk+wIAN/Xkj/GfHmEiCE0bTBxGoAU l9opgJT9f/zIX0hSt9NI0Pj+B12dKiseCCO/dA4GiBCmiODNe4IsNqbqgCYpckHD iSkq7X+93jOoHmtdBjyP2Oo1X9OvRy+AcaFFCFABMr3PqNjF9qMSSJMUOToQFuVv uL2ops2zQX5PaUhZ1z/FhHHVHAyyIQgRG+CWr9GNSsZQodF29wu12bQM7Cf9cO0A 49gjymXKkxDtrnSNrjlWD6DF62iA0O1/Z/xAUcySkxUOY9q0ziRxvARynr3iI/Au W9BVlE88/aYb1CUJORnrEMdj2Whad45n7fF4ui/uGocjCAni58R21wJDVYpWlWw= =/0db -----END PGP SIGNATURE----- From h.reindl at thelounge.net Mon Sep 29 13:30:12 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Mon, 29 Sep 2014 15:30:12 +0200 Subject: No AUTH PLAIN with dovecot 2.0.19 In-Reply-To: <54295CE5.5090101@wyona.com> References: <54295652.6070205@wyona.com> <54295814.5060202@thelounge.net> <54295CE5.5090101@wyona.com> Message-ID: <54295EE4.5000906@thelounge.net> Am 29.09.2014 um 15:21 schrieb Michael Wechner: > > Hi Harald > > Thanks very much for your quick reply. Please see my answers inline below > >> telnet is worthless because AUTH is likely announced *after STARTTLS* >> http://www.postfix.org/postconf.5.html#smtp_sasl_security_options > > right, but when requesting for example mail.wyona.com, then I can see AUTH depends on the servers configuration > hence I would assume to see it also for the new version of postfix > and dovecot, or do I misunderstand something? yes, you did not read http://www.postfix.org/postconf.5.html#smtp_sasl_security_options if the server is configured in a way it offers AUTH only over a encrypted channel (recommended) then you need to use STARTTLS before you see the capability and for that telnet is just the wrong tool -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From michael.wechner at wyona.com Mon Sep 29 13:51:41 2014 From: michael.wechner at wyona.com (Michael Wechner) Date: Mon, 29 Sep 2014 15:51:41 +0200 Subject: No AUTH PLAIN with dovecot 2.0.19 In-Reply-To: <54295EE4.5000906@thelounge.net> References: <54295652.6070205@wyona.com> <54295814.5060202@thelounge.net> <54295CE5.5090101@wyona.com> <54295EE4.5000906@thelounge.net> Message-ID: <542963ED.8060204@wyona.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Am 29.09.14 15:30, schrieb Reindl Harald: > > > Am 29.09.2014 um 15:21 schrieb Michael Wechner: >> >> Hi Harald >> >> Thanks very much for your quick reply. Please see my answers inline below >> >>> telnet is worthless because AUTH is likely announced *after STARTTLS* >>> http://www.postfix.org/postconf.5.html#smtp_sasl_security_options >> >> right, but when requesting for example mail.wyona.com, then I can see AUTH > > depends on the servers configuration > >> hence I would assume to see it also for the new version of postfix >> and dovecot, or do I misunderstand something? > > yes, you did not read http://www.postfix.org/postconf.5.html#smtp_sasl_security_options > > if the server is configured in a way it offers AUTH only > over a encrypted channel (recommended) then you need to > use STARTTLS before you see the capability and for that > telnet is just the wrong tool the new server config reads (postfix mail_version = 2.7.0): smtpd_sasl_auth_enable = yes smtpd_sasl_type = dovecot smtpd_sasl_path = private/dovecot-auth smtpd_sasl_authenticated_header = yes smtpd_sasl_security_options = noanonymous smtpd_sasl_local_domain = $myhostname broken_sasl_auth_clients = yes smtpd_recipient_restrictions = reject_unknown_sender_domain, reject_unknown_recipient_domain, reject_unauth_pipelining, permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_sender_restrictions = reject_unknown_sender_domain and the old server config reads: smtpd_sasl_type = dovecot smtpd_sasl_auth_enable = yes smtpd_sasl_security_options = noanonymous smtpd_sasl_path = private/auth broken_sasl_auth_clients = yes smtpd_recipient_restrictions = permit_sasl_authenticated, permit_mynetworks, reject_unknown_recipient_domain, reject_unauth_destination, reject_unauth_pipelining, reject_invalid_hostname, reject_unknown_sender_domain, reject_rbl_client multi.uribl.com, reject_rbl_client bl.spamcop.net, reject_rbl_client opm.blitzed.org, reject_rbl_client cbl.abuseat.org, reject_rbl_client dnsbl.njabl.org which means both configs are using smtpd_sasl_security_options = noanonymous But also when I am not using telnet, but Thunderbird for example, with the new server I never receive a dialog to enter a password as I do with the old server. This is the reason why I started to have the idea that no authentication is being requested in the first place (and hence the relay was rejected). Thanks Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUKWPtAAoJECV0ivYw6bPK/7YIAOPn+52CYWaC8KJsa6FULKSF SzilCnplLC23mRYLhQ1bnvttOMXq2XpASmh/egmkaYC49SDYfpCzawzSUn2Z3IkK KqQbUOU79t9Qc4lTgINKwuRdWrrmx7pB9iH4IggjLfWsaCOM/1yqo6Ir55A+bm0t VWk/U69rWixv0/QBNMqmcp0snJcgjYPh5HtQUHGk1bWZ4LlYwao3wonPJr4pedTo bcwq3SN7rKWCE4V4DBc6luJhqlSudMI37oCYaIw4FYyNZfYEoi4gUMfjeeHVZHrQ VGCaZPusr61GJDF2WxUw4bfoHTBvxsiBqmmaDKy00QrwJGwESI9Mabs9KJS5Mwc= =QGL9 -----END PGP SIGNATURE----- From h.reindl at thelounge.net Mon Sep 29 14:00:59 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Mon, 29 Sep 2014 16:00:59 +0200 Subject: No AUTH PLAIN with dovecot 2.0.19 In-Reply-To: <542963ED.8060204@wyona.com> References: <54295652.6070205@wyona.com> <54295814.5060202@thelounge.net> <54295CE5.5090101@wyona.com> <54295EE4.5000906@thelounge.net> <542963ED.8060204@wyona.com> Message-ID: <5429661B.9020304@thelounge.net> Am 29.09.2014 um 15:51 schrieb Michael Wechner: > Am 29.09.14 15:30, schrieb Reindl Harald: > >> Am 29.09.2014 um 15:21 schrieb Michael Wechner: >>> >>> Hi Harald >>> >>> Thanks very much for your quick reply. Please see my answers inline below >>> >>>> telnet is worthless because AUTH is likely announced *after STARTTLS* >>>> http://www.postfix.org/postconf.5.html#smtp_sasl_security_options >>> >>> right, but when requesting for example mail.wyona.com, then I can see > AUTH > >> depends on the servers configuration > >>> hence I would assume to see it also for the new version of postfix >>> and dovecot, or do I misunderstand something? > >> yes, you did not read > http://www.postfix.org/postconf.5.html#smtp_sasl_security_options > >> if the server is configured in a way it offers AUTH only >> over a encrypted channel (recommended) then you need to >> use STARTTLS before you see the capability and for that >> telnet is just the wrong tool > > the new server config reads (postfix mail_version = 2.7.0): > > smtpd_sasl_auth_enable = yes > smtpd_sasl_type = dovecot > smtpd_sasl_path = private/dovecot-auth > smtpd_sasl_authenticated_header = yes > smtpd_sasl_security_options = noanonymous > smtpd_sasl_local_domain = $myhostname > broken_sasl_auth_clients = yes > smtpd_recipient_restrictions = reject_unknown_sender_domain, > reject_unknown_recipient_domain, reject_unauth_pipelining, > permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination > smtpd_sender_restrictions = reject_unknown_sender_domain * check postfix master.cf for chroot - only explicit "n" disabled it * check configuration of the private/dovecot-auth (permissions and so on) * look at your logs careful ____________________________________________________________________ that is my part in dovecot.conf: service auth { unix_listener /var/spool/postfix/private/auth { mode = 0660 user = postfix group = postfix } } ____________________________________________________________________ that's my part in postfix's main.cf: smtpd_sasl_auth_enable = yes smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth ____________________________________________________________________ well, both are unchanged for a very long time and survived a lot of dist-upgrades (Fedora) as well as Dovecot/Postfix -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From rs at sys4.de Mon Sep 29 14:09:32 2014 From: rs at sys4.de (Robert Schetterer) Date: Mon, 29 Sep 2014 16:09:32 +0200 Subject: No AUTH PLAIN with dovecot 2.0.19 In-Reply-To: <54295652.6070205@wyona.com> References: <54295652.6070205@wyona.com> Message-ID: <5429681C.40702@sys4.de> Am 29.09.2014 um 14:53 schrieb Michael Wechner: > Hi > > I have installed the package dovecot-postfix on Ubuntu 12.04 LTS: > > dovecot --version: 2.0.19 > postconf -d | grep version: 2.9.6 > > and receiving email works very fine, but relaying email does not work. > > I think the problem is that after STARTTLS the authentication is not > being executed > > 250-AUTH PLAIN > 250-AUTH=PLAIN > > which means using telnet returns > > telnet mx2.wyona.com 587 > Trying 50.116.54.197... > Connected to node3.wyona.com. > Escape character is '^]'. > 220 node3.members.linode.com ESMTP Postfix (Ubuntu) > EHLO letscallitevil.com > 250-node3.members.linode.com > 250-PIPELINING > 250-SIZE 10240000 > 250-VRFY > 250-ETRN > 250-STARTTLS > 250-ENHANCEDSTATUSCODES > 250-8BITMIME > 250 DSN > > So far I have used dovecot version 1.2.9, which works very fine, but the > configuration > > /etc/dovecot/dovecot.conf > > seems to be very different in the case of dovecot version 2.0.19. > > I have checked all kind of tutorials for several days now, like for example > > https://help.ubuntu.com/10.04/serverguide/postfix.html > > but nothing helped. > > Any pointers or help is very much appreciated. > > Thanks > > Michael > However you might fix that problem , it would better go Trusty which has more recent version http://packages.ubuntu.com/trusty/dovecot-core 2.2.9 Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From michael.wechner at wyona.com Mon Sep 29 18:45:05 2014 From: michael.wechner at wyona.com (Michael Wechner) Date: Mon, 29 Sep 2014 20:45:05 +0200 Subject: No AUTH PLAIN with dovecot 2.0.19 In-Reply-To: <5429661B.9020304@thelounge.net> References: <54295652.6070205@wyona.com> <54295814.5060202@thelounge.net> <54295CE5.5090101@wyona.com> <54295EE4.5000906@thelounge.net> <542963ED.8060204@wyona.com> <5429661B.9020304@thelounge.net> Message-ID: <5429A8B1.8040608@wyona.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 thanks very much for your configuration. It seems with dovecot 2.0.19 the configuration has changed quite a bit and things have been splitted into several files (http://wiki2.dovecot.org/QuickConfiguration) sudo grep -rl postfix /etc/dovecot/* /etc/dovecot/conf.d/10-master.conf /etc/dovecot/conf.d/01-mail-stack-delivery.conf and included inside dovecot.conf (!include conf.d/*.conf) I finally found that auth_debug is inside /etc/dovecot/conf.d/10-logging.conf I will turn on the logging and hopefully better understand what is happening. Thanks Michael Am 29.09.14 16:00, schrieb Reindl Harald: > > Am 29.09.2014 um 15:51 schrieb Michael Wechner: >> Am 29.09.14 15:30, schrieb Reindl Harald: >> >>> Am 29.09.2014 um 15:21 schrieb Michael Wechner: >>>> >>>> Hi Harald >>>> >>>> Thanks very much for your quick reply. Please see my answers inline below >>>> >>>>> telnet is worthless because AUTH is likely announced *after STARTTLS* >>>>> http://www.postfix.org/postconf.5.html#smtp_sasl_security_options >>>> >>>> right, but when requesting for example mail.wyona.com, then I can see >> AUTH >> >>> depends on the servers configuration >> >>>> hence I would assume to see it also for the new version of postfix >>>> and dovecot, or do I misunderstand something? >> >>> yes, you did not read >> http://www.postfix.org/postconf.5.html#smtp_sasl_security_options >> >>> if the server is configured in a way it offers AUTH only >>> over a encrypted channel (recommended) then you need to >>> use STARTTLS before you see the capability and for that >>> telnet is just the wrong tool >> >> the new server config reads (postfix mail_version = 2.7.0): >> >> smtpd_sasl_auth_enable = yes >> smtpd_sasl_type = dovecot >> smtpd_sasl_path = private/dovecot-auth >> smtpd_sasl_authenticated_header = yes >> smtpd_sasl_security_options = noanonymous >> smtpd_sasl_local_domain = $myhostname >> broken_sasl_auth_clients = yes >> smtpd_recipient_restrictions = reject_unknown_sender_domain, >> reject_unknown_recipient_domain, reject_unauth_pipelining, >> permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination >> smtpd_sender_restrictions = reject_unknown_sender_domain > > * check postfix master.cf for chroot - only explicit "n" disabled it > * check configuration of the private/dovecot-auth (permissions and so on) > * look at your logs careful > ____________________________________________________________________ > > that is my part in dovecot.conf: > > service auth { > unix_listener /var/spool/postfix/private/auth { > mode = 0660 > user = postfix > group = postfix > } > } > ____________________________________________________________________ > > that's my part in postfix's main.cf: > > smtpd_sasl_auth_enable = yes > smtpd_sasl_type = dovecot > smtpd_sasl_path = private/auth > ____________________________________________________________________ > > well, both are unchanged for a very long time and survived > a lot of dist-upgrades (Fedora) as well as Dovecot/Postfix > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUKaixAAoJECV0ivYw6bPKtjAH/AiMIS4I0+8q8vqJYwzs9Pzr LgQfe/O9O6HwtL0u63bkZ8SPslxKUxhpl9dmv6HcodfGxHSkaGdlcVS96o6ynjS4 rcWoco6qQ0PsRiJTT1x2IGqO8mPQgH9ovHmI+6ZKAqjWi4S8iFT6G/D6tdtmikME GqW2p2r0mE4xyn0RwU6IWb+cxEYPq3X/8GuSbQsO3Ux0AcejUBgI1ex9xfHM8xhi vfxPDNY9M1s/l+lwBiEqAjkwe99cOpuBPr9u9Mg6WS3+fGwa+Di642ZeZAy3SB63 /wYtLProbJ7enHar7t0sEb0/WvpqUvchNunlw3R1KRe/RhMSbxKYY0x4t6WLSGo= =MLa2 -----END PGP SIGNATURE----- From user+dovecot at localhost.localdomain.org Mon Sep 29 18:45:44 2014 From: user+dovecot at localhost.localdomain.org (Pascal Volk) Date: Mon, 29 Sep 2014 18:45:44 +0000 Subject: "doveadm backup/sync" are badly documented (SOLVED AND BUG REPORT!) In-Reply-To: <5428A49B.3010306@jcea.es> References: <54288323.6040801@jcea.es> <5428A49B.3010306@jcea.es> Message-ID: <5429A8D8.1050702@localhost.localdomain.org> On 09/29/2014 12:15 AM, Jesus Cea wrote: > ? >> $ doveadm backup -h >> backup: invalid option -- 'h' >> doveadm backup [-u |-A] [-S ] [-dfR] [-l ] [-r >> ] [-m ] [-n | -N] [-x ] [-s >> ] >> >> I can't find any explanation at all about the different parameters of >> "doveadm backup". > > Please, document. > ? That's my task. I hope I'll find the time to write the fine manual until this weekend. Regards, Pascal -- The trapper recommends today: beeffeed.1427220 at localdomain.org From michael.wechner at wyona.com Mon Sep 29 18:47:00 2014 From: michael.wechner at wyona.com (Michael Wechner) Date: Mon, 29 Sep 2014 20:47:00 +0200 Subject: No AUTH PLAIN with dovecot 2.0.19 In-Reply-To: <5429681C.40702@sys4.de> References: <54295652.6070205@wyona.com> <5429681C.40702@sys4.de> Message-ID: <5429A924.2010903@wyona.com> Hi Robert Thank you for your hint! Michael Am 29.09.14 16:09, schrieb Robert Schetterer: > Am 29.09.2014 um 14:53 schrieb Michael Wechner: >> Hi >> >> I have installed the package dovecot-postfix on Ubuntu 12.04 LTS: >> >> dovecot --version: 2.0.19 >> postconf -d | grep version: 2.9.6 >> >> and receiving email works very fine, but relaying email does not work. >> >> I think the problem is that after STARTTLS the authentication is not >> being executed >> >> 250-AUTH PLAIN >> 250-AUTH=PLAIN >> >> which means using telnet returns >> >> telnet mx2.wyona.com 587 >> Trying 50.116.54.197... >> Connected to node3.wyona.com. >> Escape character is '^]'. >> 220 node3.members.linode.com ESMTP Postfix (Ubuntu) >> EHLO letscallitevil.com >> 250-node3.members.linode.com >> 250-PIPELINING >> 250-SIZE 10240000 >> 250-VRFY >> 250-ETRN >> 250-STARTTLS >> 250-ENHANCEDSTATUSCODES >> 250-8BITMIME >> 250 DSN >> >> So far I have used dovecot version 1.2.9, which works very fine, but the >> configuration >> >> /etc/dovecot/dovecot.conf >> >> seems to be very different in the case of dovecot version 2.0.19. >> >> I have checked all kind of tutorials for several days now, like for example >> >> https://help.ubuntu.com/10.04/serverguide/postfix.html >> >> but nothing helped. >> >> Any pointers or help is very much appreciated. >> >> Thanks >> >> Michael >> > However you might fix that problem , it would better go Trusty > which has more recent version > > http://packages.ubuntu.com/trusty/dovecot-core > > 2.2.9 > > > Best Regards > MfG Robert Schetterer > From h.reindl at thelounge.net Mon Sep 29 18:59:57 2014 From: h.reindl at thelounge.net (Reindl Harald) Date: Mon, 29 Sep 2014 20:59:57 +0200 Subject: No AUTH PLAIN with dovecot 2.0.19 In-Reply-To: <5429A8B1.8040608@wyona.com> References: <54295652.6070205@wyona.com> <54295814.5060202@thelounge.net> <54295CE5.5090101@wyona.com> <54295EE4.5000906@thelounge.net> <542963ED.8060204@wyona.com> <5429661B.9020304@thelounge.net> <5429A8B1.8040608@wyona.com> Message-ID: <5429AC2D.4050509@thelounge.net> Am 29.09.2014 um 20:45 schrieb Michael Wechner: > thanks very much for your configuration. It seems with dovecot 2.0.19 > the configuration has changed quite a bit > and things have been splitted into several files it's your choice to have one dovecot.conf containing all settings and is independent of the version frankly my self built RPM deletes all config files before the %files section to have no orphaned / unused crap on the production machines and the one and only configuration is "dovecot.conf" -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 181 bytes Desc: OpenPGP digital signature URL: From jcea at jcea.es Mon Sep 29 23:42:21 2014 From: jcea at jcea.es (Jesus Cea) Date: Tue, 30 Sep 2014 01:42:21 +0200 Subject: "doveadm sync/backup" and SSH should use "ssh-agent" if available Message-ID: <5429EE5D.3060605@jcea.es> I use SSH-AGENT in my system, to cache SSH credentials and avoid typing my key every time I connect to a remoto host. But "doveadm sync/backup", when one of the ends is SSH accessed, doesn't use the available SSH-AGENT and forces me to type my password. -- Jes?s Cea Avi?n _/_/ _/_/_/ _/_/_/ jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From jcea at jcea.es Mon Sep 29 23:57:18 2014 From: jcea at jcea.es (Jesus Cea) Date: Tue, 30 Sep 2014 01:57:18 +0200 Subject: "doveadm sync/backup" should show some kind of progress meter Message-ID: <5429F1DE.4090808@jcea.es> Using "-v" with those commands doesn't nothing, aparently. Using "-D" shows complex debug info only useful for debugging. But this comands take a lot of time and should show some kind of progress meter/feedback like network speed, percent, ETA, etc. -- Jes?s Cea Avi?n _/_/ _/_/_/ _/_/_/ jcea at jcea.es - http://www.jcea.es/ _/_/ _/_/ _/_/ _/_/ _/_/ Twitter: @jcea _/_/ _/_/ _/_/_/_/_/ jabber / xmpp:jcea at jabber.org _/_/ _/_/ _/_/ _/_/ _/_/ "Things are not so easy" _/_/ _/_/ _/_/ _/_/ _/_/ _/_/ "My name is Dump, Core Dump" _/_/_/ _/_/_/ _/_/ _/_/ "El amor es poner tu felicidad en la felicidad de otro" - Leibniz -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From skdovecot at smail.inf.fh-brs.de Tue Sep 30 06:24:38 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Tue, 30 Sep 2014 08:24:38 +0200 (CEST) Subject: STARTTLS test (was Re: No AUTH PLAIN with dovecot 2.0.19) In-Reply-To: <54295EE4.5000906@thelounge.net> References: <54295652.6070205@wyona.com> <54295814.5060202@thelounge.net> <54295CE5.5090101@wyona.com> <54295EE4.5000906@thelounge.net> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 29 Sep 2014, Reindl Harald wrote: >Am 29.09.2014 um 15:21 schrieb Michael Wechner: > >> hence I would assume to see it also for the new version of postfix >> and dovecot, or do I misunderstand something? > if the server is configured in a way it offers AUTH only > over a encrypted channel (recommended) then you need to > use STARTTLS before you see the capability and for that > telnet is just the wrong tool To test STARTTLS try this: a) gnutls-cli -p 587 --starttls smtp STARTTLS ^D The ^D lets gnutls perform the SSL handshake, then you can type again. b) openssl s_client -connect smtp:587 -starttls smtp - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBVCpMpnz1H7kL/d9rAQKMWQgAvT1r7TZpGX6kTPne8P/nrKKbGivJZAqo PoET7l/y7Yf/DW1VC1pgQg6pNYBAbUndTnczJz2nRmLMYNjjO7SV9GBWzMIJzZPj F7A5tN5+LV7y+2KDKM2U49E4jSe7ocm6GGFKTxl4gAegKJZU0S2KMZ3YnA8Wessl rKwgVnL8gau8H3SP7lNdi9V2WvuO4YITXt9l/gmKLlYJqly3JGEOYP714kqY5AcW 2R2h3DO9H61Mr//hlSiNslKOlYAMSkNeqjnntzzUxvcSzBub68Yx0wuP0gYROYJ0 CVbpYiAV3sfUdkK9ZG+c2Lfezrm+FicN7LYiMF88pH3EWQsLcCStjA== =isXw -----END PGP SIGNATURE----- From goetz.reinicke at filmakademie.de Tue Sep 30 07:01:03 2014 From: goetz.reinicke at filmakademie.de (=?UTF-8?B?R8O2dHogUmVpbmlja2UgLSBJVCBLb29yZGluYXRvcg==?=) Date: Tue, 30 Sep 2014 09:01:03 +0200 Subject: Master user and invalid credentials dovecot-2.2.13 In-Reply-To: <542958DB.7060700@agr.unicamp.br> References: <54291389.6060605@filmakademie.de> <542958DB.7060700@agr.unicamp.br> Message-ID: <542A552F.1080408@filmakademie.de> Hi, on the console: telnet localhost 143 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=PLAIN AUTH=LOGIN] Dovecot ready. in the logs: Sep 30 08:56:23 auth: Debug: client in: AUTH 2936 PLAIN service=imap secured session=fOCd4UIEMAB/AAAB lip=127.0.0.1 rip=127.0.0.1 lport=143 rport=54320 resp= Sep 30 08:56:23 auth: Debug: passwd-file(user,127.0.0.1,master,): Master user lookup for login: testma Sep 30 08:56:23 auth: Debug: passwd-file(user,127.0.0.1,master,): lookup: user=user file=/etc/dovecot/master-users Sep 30 08:56:23 auth: Info: passwd-file(user,127.0.0.1,master,): Master user logging in as testma Sep 30 08:56:23 auth: Info: ldap(testma,127.0.0.1,): invalid credentials /G?tz Am 29.09.14 um 15:04 schrieb Clovis Tristao: > Hi, > > As you are performing the tests? > Would post the debug log? > Cheers, > > Cl?vis > > Em 29-09-2014 05:08, G?tz Reinicke - IT Koordinator escreveu: >> Hi, >> >> I followed the docs from the dovecot wiki >> (http://wiki2.dovecot.org/Authentication/MasterUsers) and still have >> some problem: >> >> 1. uncommented "!include auth-ldap.conf.ext" in 10-auth.conf >> 2. htpasswd -b -c -s .... to create user/password for a masteruseruser >> 3. checked auth-master.conf.ext >> >> When I try to test the login, I always get an "invalid credentials" in >> the logs with auth_debug=yes set. >> >> dovecot can read /etc/dovecot/master-users >> >> The users are in ldap. >> >> The example wiki shows the passwords {SHA1}...., in my password file >> they are {SHA}.... >> >> The "master user" posting in september gave some clues what might be >> wrong, but did not help to solve my problem. >> >> >> Any suggestions are welcome! Thanks and regards. G?tz > -- G?tz Reinicke IT-Koordinator Tel. +49 7141 969 82 420 E-Mail goetz.reinicke at filmakademie.de Filmakademie Baden-W?rttemberg GmbH Akademiehof 10 71638 Ludwigsburg www.filmakademie.de Eintragung Amtsgericht Stuttgart HRB 205016 Vorsitzender des Aufsichtsrats: J?rgen Walter MdL Staatssekret?r im Ministerium f?r Wissenschaft, Forschung und Kunst Baden-W?rttemberg Gesch?ftsf?hrer: Prof. Thomas Schadt -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 5481 bytes Desc: S/MIME Cryptographic Signature URL: From tim at bastelfreak.de Tue Sep 30 07:05:10 2014 From: tim at bastelfreak.de (Tim) Date: Tue, 30 Sep 2014 09:05:10 +0200 Subject: Corrupted index cache after migrating from maildir to mdbox In-Reply-To: <54275AD9.2080900@bastelfreak.de> References: <54275AD9.2080900@bastelfreak.de> Message-ID: <542A5626.9090001@bastelfreak.de> Hi guys, does nobody has any thoughts on this error? On 28.09.2014 02:48, Tim wrote: > Hi guys, > > I'm running dovecot/postfix on my Debian Jessie maschine: > > # dovecot --version > 2.2.13 > doveconf -n output: http://p.bastelfreak.de/HsVwS/ > > today I migrated from maildir(located at /var/vmail) to mdbox with these > commands: > rsync -av -f"+ */" -f"- *" /var/vmail/ /home/vmail/ > rm /home/vmail/*/*/Maildir -rf > for i in $(doveadm user \*); do u=$(echo $i | cut -d@ -f1); d=$(echo $i > |cut -d@ -f2); dsync -v -u $i mirror mdbox:/home/vmail/$d/$u/mdbox; done > > Then I changed the mail_location to mdbox:/home/vmail/%d/%n/mdbox and > did the following commands: > > service dovecot restart > for i in $(doveadm user \*); do u=$(echo $i | cut -d@ -f1); d=$(echo $i > |cut -d@ -f2); dsync -v -u $i mirror maildir:/var/vmail/$d/$u/Mail; done > doveadm index -A all INBOX > for i in $(doveadm user \*); do doveadm -Dv fts rescan -u $i;done > > unfortunately I'm getting the following two kinds of error messages for > all mail boxes in my mail.log: > > Error: Corrupted index cache file > /home/vmail/%domain/%user/mdbox/mailboxes/%maildir/dbox-Mails/dovecot.index.cache: > Broken virtual size for mail UID 2564 > > and: > > Error: read(/home/vmail/%domain/%user/mdbox/storage/m.108 > ): FETCH BODY[] for mailbox %maildir UID 2564 got too little data: 2417 > vs 6319 > > please let me know if you have any suggestions for fixing this issue or > if you need more information. > > kind regards, Tim From michael.wechner at wyona.com Tue Sep 30 09:01:39 2014 From: michael.wechner at wyona.com (Michael Wechner) Date: Tue, 30 Sep 2014 11:01:39 +0200 Subject: STARTTLS test (was Re: No AUTH PLAIN with dovecot 2.0.19) In-Reply-To: References: <54295652.6070205@wyona.com> <54295814.5060202@thelounge.net> <54295CE5.5090101@wyona.com> <54295EE4.5000906@thelounge.net> Message-ID: <542A7173.6000502@wyona.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi Steffen Thanks very much for the hint. I will give it a try later today. Michael Am 30.09.14 08:24, schrieb Steffen Kaiser: > On Mon, 29 Sep 2014, Reindl Harald wrote: > > > Am 29.09.2014 um 15:21 schrieb Michael Wechner: > > >> hence I would assume to see it also for the new version of postfix > >> and dovecot, or do I misunderstand something? > > > if the server is configured in a way it offers AUTH only > > over a encrypted channel (recommended) then you need to > > use STARTTLS before you see the capability and for that > > telnet is just the wrong tool > > To test STARTTLS try this: > > a) gnutls-cli -p 587 --starttls smtp > STARTTLS > ^D > > The ^D lets gnutls perform the SSL handshake, then you can type again. > > b) openssl s_client -connect smtp:587 -starttls smtp > > -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUKnFzAAoJECV0ivYw6bPKaRMH/jR/RmgesxicF5zg+o+g6DqI 7fd8sttTeGz3umOrUR8E48frSGOrOdNSxcJEbk8othLhV3qsc0bIMKnOEopF0pIj /oPriGN+vC4bJ2w+iSyYPGdPfLHgc5Cdh/urmhxo4GRZrX5GSedEctP920AQz63B yfnLKRl3wHgFk40uomJLKG2ZLZy1YTxISIfE1pHHGCwDvy+UC2GIT0Cexes7ysTh yQ3S+dhBMknZze8N2dK969hn2TlecqjAK/il0sVlftiW4iYUtuXNA6liwOf/9Y23 aWNcqzTd1l0+EskiNlFlIvv1NVemXoZTnAR37TY+K2GnaKBvsS1j4mDZPw71O28= =fqVr -----END PGP SIGNATURE----- From michael.wechner at wyona.com Tue Sep 30 09:11:02 2014 From: michael.wechner at wyona.com (Michael Wechner) Date: Tue, 30 Sep 2014 11:11:02 +0200 Subject: No AUTH PLAIN with dovecot 2.0.19 In-Reply-To: <5429AC2D.4050509@thelounge.net> References: <54295652.6070205@wyona.com> <54295814.5060202@thelounge.net> <54295CE5.5090101@wyona.com> <54295EE4.5000906@thelounge.net> <542963ED.8060204@wyona.com> <5429661B.9020304@thelounge.net> <5429A8B1.8040608@wyona.com> <5429AC2D.4050509@thelounge.net> Message-ID: <542A73A6.2000905@wyona.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 yes, that makes sense. I also did now doveconf -n > /etc/dovecot/dovecot.conf but I still do not know why the configuration does not work. I have now downgraded to Postfix 2.7.0 Dovecot 1.2.9 also using apt-get install dovecot-postfix but it also did not work with this older version and the corresponding "default" configuration. But I have copied now the old configuration to this "new" setup and it works now. So I would argue there must be something wrong with the "default" configuration when using the package dovecot-postfix. I will try to find out and send a note in case I will find out. Thanks Michael Am 29.09.14 20:59, schrieb Reindl Harald: > > Am 29.09.2014 um 20:45 schrieb Michael Wechner: >> thanks very much for your configuration. It seems with dovecot 2.0.19 >> the configuration has changed quite a bit >> and things have been splitted into several files > > it's your choice to have one dovecot.conf containing > all settings and is independent of the version > > frankly my self built RPM deletes all config files > before the %files section to have no orphaned / unused > crap on the production machines and the one and only > configuration is "dovecot.conf" > -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org iQEcBAEBCgAGBQJUKnOmAAoJECV0ivYw6bPKFb4H/idXFbotox38frbyylVzokLH 8c/vBCjLoSG9mdgJ9/XLrTGUfKSQTU6YRUG1AYBe2thSh6umdpkNWC3Hk4xDX/79 VbFyPeDz3Ad1PAP7uEX1wumzN8DO63RuFDjeIlSaCmoACLrskSrmeF8INiRdZfUR 8Andxp+DVr5aMx0FaJmdRXDLO+H2/3/PzvXz8zpuIYvyd47/0Anfte9P2zv8QZ0n JI9bUCEZtG1hS4CInR7xS7vAD3OPIHQOonjmrLeCTHWTZ3YEYB++rTkQINNlaGNw qF7Az6qt3FzhJjVnwUppWXoVO2CZit+eCSUSYDWjaT4AECX3JxOPdN8B6UG2sUI= =HikP -----END PGP SIGNATURE----- From toni at solu.fi Tue Sep 30 09:24:13 2014 From: toni at solu.fi (Toni Mattila) Date: Tue, 30 Sep 2014 12:24:13 +0300 Subject: Corrupted index cache after migrating from maildir to mdbox In-Reply-To: <542A5626.9090001@bastelfreak.de> References: <54275AD9.2080900@bastelfreak.de> <542A5626.9090001@bastelfreak.de> Message-ID: <542A76BD.7010409@solu.fi> Hi, You have broken maildir files with wrong S= in them. Usually produced by maildrop or courier imap's tools. You can fix them with http://www.dovecot.org/tools/maildir-size-fix.pl If you compare ls -la and S= in the files you will see the difference. Cheers, Toni On 30.9.2014 10:05, Tim wrote: > Hi guys, > > does nobody has any thoughts on this error? > > > On 28.09.2014 02:48, Tim wrote: >> Hi guys, >> >> I'm running dovecot/postfix on my Debian Jessie maschine: >> >> # dovecot --version >> 2.2.13 >> doveconf -n output: http://p.bastelfreak.de/HsVwS/ >> >> today I migrated from maildir(located at /var/vmail) to mdbox with these >> commands: >> rsync -av -f"+ */" -f"- *" /var/vmail/ /home/vmail/ >> rm /home/vmail/*/*/Maildir -rf >> for i in $(doveadm user \*); do u=$(echo $i | cut -d@ -f1); d=$(echo $i >> |cut -d@ -f2); dsync -v -u $i mirror mdbox:/home/vmail/$d/$u/mdbox; done >> >> Then I changed the mail_location to mdbox:/home/vmail/%d/%n/mdbox and >> did the following commands: >> >> service dovecot restart >> for i in $(doveadm user \*); do u=$(echo $i | cut -d@ -f1); d=$(echo $i >> |cut -d@ -f2); dsync -v -u $i mirror maildir:/var/vmail/$d/$u/Mail; done >> doveadm index -A all INBOX >> for i in $(doveadm user \*); do doveadm -Dv fts rescan -u $i;done >> >> unfortunately I'm getting the following two kinds of error messages for >> all mail boxes in my mail.log: >> >> Error: Corrupted index cache file >> /home/vmail/%domain/%user/mdbox/mailboxes/%maildir/dbox-Mails/dovecot.index.cache: >> Broken virtual size for mail UID 2564 >> >> and: >> >> Error: read(/home/vmail/%domain/%user/mdbox/storage/m.108 >> ): FETCH BODY[] for mailbox %maildir UID 2564 got too little data: 2417 >> vs 6319 >> >> please let me know if you have any suggestions for fixing this issue or >> if you need more information. >> >> kind regards, Tim From phil at dovecot.fi Tue Sep 30 12:20:16 2014 From: phil at dovecot.fi (Phil Carmody) Date: Tue, 30 Sep 2014 15:20:16 +0300 Subject: Master user and invalid credentials dovecot-2.2.13 In-Reply-To: <54291389.6060605@filmakademie.de> References: <54291389.6060605@filmakademie.de> Message-ID: <20140930122016.GB20875@phil.dovecot.net> On Mon, Sep 29, 2014 at 10:08:41AM +0200, G??tz Reinicke - IT Koordinator wrote: > The example wiki shows the passwords {SHA1}...., in my password file > they are {SHA}.... You don't need to worry about that part, {SHA} and {SHA1} are aliases that map to the same behaviour: src/auth/password-scheme.c#0805 0805 static const struct password_scheme builtin_schemes[] = { ... 0810 { "SHA", PW_ENCODING_BASE64, SHA1_RESULTLEN, NULL, sha1_generate }, 0811 { "SHA1", PW_ENCODING_BASE64, SHA1_RESULTLEN, NULL, sha1_generate }, Phil From tim at bastelfreak.de Tue Sep 30 13:41:24 2014 From: tim at bastelfreak.de (Tim) Date: Tue, 30 Sep 2014 15:41:24 +0200 Subject: Corrupted index cache after migrating from maildir to mdbox In-Reply-To: <542A76BD.7010409@solu.fi> References: <54275AD9.2080900@bastelfreak.de> <542A5626.9090001@bastelfreak.de> <542A76BD.7010409@solu.fi> Message-ID: <542AB304.8030208@bastelfreak.de> On 30.09.2014 11:24, Toni Mattila wrote: > Hi, > > You have broken maildir files with wrong S= in them. Usually produced > by maildrop or courier imap's tools. You can fix them with > http://www.dovecot.org/tools/maildir-size-fix.pl > I migrated from maildir to mdbox. Seems like the tool only fixes maildir format? possible to fix my mdbox? Also I never noticed any error messages while using maildir. > If you compare ls -la and S= in the files you will see the difference. > > Cheers, > Toni > > On 30.9.2014 10:05, Tim wrote: >> Hi guys, >> >> does nobody has any thoughts on this error? >> >> >> On 28.09.2014 02:48, Tim wrote: >>> Hi guys, >>> >>> I'm running dovecot/postfix on my Debian Jessie maschine: >>> >>> # dovecot --version >>> 2.2.13 >>> doveconf -n output: http://p.bastelfreak.de/HsVwS/ >>> >>> today I migrated from maildir(located at /var/vmail) to mdbox with >>> these >>> commands: >>> rsync -av -f"+ */" -f"- *" /var/vmail/ /home/vmail/ >>> rm /home/vmail/*/*/Maildir -rf >>> for i in $(doveadm user \*); do u=$(echo $i | cut -d@ -f1); d=$(echo $i >>> |cut -d@ -f2); dsync -v -u $i mirror mdbox:/home/vmail/$d/$u/mdbox; >>> done >>> >>> Then I changed the mail_location to mdbox:/home/vmail/%d/%n/mdbox and >>> did the following commands: >>> >>> service dovecot restart >>> for i in $(doveadm user \*); do u=$(echo $i | cut -d@ -f1); d=$(echo $i >>> |cut -d@ -f2); dsync -v -u $i mirror maildir:/var/vmail/$d/$u/Mail; >>> done >>> doveadm index -A all INBOX >>> for i in $(doveadm user \*); do doveadm -Dv fts rescan -u $i;done >>> >>> unfortunately I'm getting the following two kinds of error messages for >>> all mail boxes in my mail.log: >>> >>> Error: Corrupted index cache file >>> /home/vmail/%domain/%user/mdbox/mailboxes/%maildir/dbox-Mails/dovecot.index.cache: >>> >>> Broken virtual size for mail UID 2564 >>> >>> and: >>> >>> Error: read(/home/vmail/%domain/%user/mdbox/storage/m.108 >>> ): FETCH BODY[] for mailbox %maildir UID 2564 got too little data: 2417 >>> vs 6319 >>> >>> please let me know if you have any suggestions for fixing this issue or >>> if you need more information. >>> >>> kind regards, Tim > From r at sys4.de Tue Sep 30 14:29:08 2014 From: r at sys4.de (Ralf Hildebrandt) Date: Tue, 30 Sep 2014 16:29:08 +0200 Subject: home from SQL Message-ID: <20140930142908.GB4001@sys4.de> Currently I'm using user_query = SELECT 1000 AS uid, 1000 AS gid, '/srv/vmail/%2.256Hu/%Lu' AS home, ... so I'm hashing based on %u (basically). But in my SQL db I have a "unique_identifier" field, which never changes, even when the user is changing his/her email address (due to marriage or the like). What I'd really like to do is to use %u to find the value of the unique_identifier field, hash THAT value and use "AS home". But how? That way I can rename users without shuffling directories around the filesystem. -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein From skdovecot at smail.inf.fh-brs.de Tue Sep 30 14:37:48 2014 From: skdovecot at smail.inf.fh-brs.de (Steffen Kaiser) Date: Tue, 30 Sep 2014 16:37:48 +0200 (CEST) Subject: home from SQL In-Reply-To: <20140930142908.GB4001@sys4.de> References: <20140930142908.GB4001@sys4.de> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 30 Sep 2014, Ralf Hildebrandt wrote: > Currently I'm using > user_query = SELECT 1000 AS uid, 1000 AS gid, '/srv/vmail/%2.256Hu/%Lu' AS home, ... > > so I'm hashing based on %u (basically). But in my SQL db I have a > "unique_identifier" field, which never changes, even when the user is > changing his/her email address (due to marriage or the like). > > What I'd really like to do is to use %u to find the value of the > unique_identifier field, hash THAT value and use "AS home". But how? Dovecot cannot help you to hash that value, but if you use a SQL server, you can create a function, which tranforms the unique_identifier into any string you like. Then use user_query = SELECT 1000 AS uid, 1000 AS gid, toHomeDir(unique_identifier) AS home, ... - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBVCrAPXz1H7kL/d9rAQLcGgf/a9ok9TVEscjoyGhuLEpF1RlyG1EhQO+B in5mseexWUPdOhcK/BFkc2FasuAaW8kQ7E+tnRY3h76MQn61c//soATMDI+iJx8X wNVzBRu2YgcISwwfALIQmcVHN3mIbem327Z5nKX+bXYnfoDFvcSAdTohM2YFSw+A xO/oCucW2Kgtv1rQQ1AL88N86VJLTGhx+uowLGrOPTX8Q1zgzH97ii+Ujki+dtnF AWYLaH8lH//DE4jiqmBLQW6flhXM0xeOYa10oAhkLA2WS8I9GVbuBE4TpYc0OiLt IqtmOmRr4ZJkAuKWEIiVOnksAWWK/vLZZeEJGE/E3No/iKE8QA+0DA== =z4O7 -----END PGP SIGNATURE-----