Re: Ubuntu Dovecot 2.2.9 several Errors, Transaction log as well as BUG message
Thanks for the advice, sadly the VM hoster uses Qemu with an ancient crappy
kernel and does not offer any way to move upwards to 16.04 with dovecot
2.2.22.
All I could do is try to force the 16.04 packages into the 14.04 system,
which would likely add more problems than solve these :/
Stefan
2017-03-23 9:52 GMT+01:00 Aki Tuomi :
> 2.2.9 is rather old. Updating to a more recent version could help.
>
> Aki
>
>
> On 23.03.2017 10:48, Kein Name wrote:
> > Hello List,
> >
> > I am running an Ubuntu 14.04.5 LTS Server with Dovecot 2.2.9, only local
> > filesystems and authentication done via mysql backend.
> > Server is a Strato Virtual Server running
> > 2.6.32-042stab120.11 #1 SMP Fri Mar 10 16:52:50 MSK 2017 i686 i686 i686
> > GNU/Linux
> >
> > Sometimes I see errors in the log like this for one user:
> >
> > Error: Transaction log /var/vmail/
> > example.net/jena/Maildir/.Archives.2017/dovecot.index.log: duplicate
> > transaction log sequence (2)
> >
> > After seeing these, some time later, (mostly 2h), Dovecot starts to deny
> > login from all clients with messages like this:
> >
> > Mar 23 01:32:27 h2312250 dovecot: auth: Error: BUG: Authentication client
> > sent unknown handshake command:
> > REQUEST?1804861441?19318?1?9ce500129289a0237e4e85a6c880a047?
> session_pid=19323...
> > Mar 23 01:32:27 h2312250 dovecot: imap: Error: Authentication server
> didn't
> > send valid SPID as expected: MECH#011PLAIN#011plaintext
> > Mar 23 01:32:27 h2312250 dovecot: imap: Error: Disconnected from auth
> > server, aborting (client-pid=19318 client-id=1)
> > Mar 23 01:32:27 h2312250 dovecot: imap-login: Internal login failure
> > (pid=19318 id=1) (internal failure, 1 successful auths): user=<
> > u...@example.net>, method=PLAIN, rip=X, lip=X, mpid=19323,
> > session=
> >
> > I do not know if these problems have something to do with each other or
> > not. But it happened several times now (maybe once or twice every month
> or
> > so).
> > When I restart Dovecot, the error seems gone for the moment, until it
> comes
> > back in a month or some weeks.
> >
> >
> > For reference, here is the running config:
> >
> > dovecot.conf
> >
> > # 2.2.9: /etc/dovecot/dovecot.conf
> > # OS: Linux 2.6.32-042stab120.11 i686 Ubuntu 14.04.5 LTS
> > auth_mechanisms = plain login
> > auth_verbose = yes
> > disable_plaintext_auth = no
> > log_timestamp = "%Y-%m-%d %H:%M:%S "
> > 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/dovecot-mysql.conf
> > driver = sql
> > }
> > plugin {
> > quota = maildir:User quota
> > quota_rule = *:bytes=10M
> > sieve = ~/dovecot.sieve
> > }
> > protocols = imap pop3 sieve
> > service auth {
> > unix_listener /var/spool/postfix/private/auth {
> > group = postfix
> > mode = 0660
> > user = postfix
> > }
> > unix_listener auth-master {
> > mode = 0600
> > user = vmail
> > }
> > user = root
> > }
> > ssl_cert = > ssl_key = > userdb {
> > args = /etc/dovecot/dovecot-mysql.conf
> > driver = sql
> > }
> > protocol pop3 {
> > mail_plugins = quota
> > pop3_uidl_format = %08Xu%08Xv
> > }
> > protocol imap {
> > mail_plugins = quota imap_quota
> > }
> > protocol lda {
> > auth_socket_path = /var/run/dovecot/auth-master
> > mail_plugins = sieve quota
> > postmaster_address = postmas...@example.net
> > quota_full_tempfail = yes
> > }
> >
> >
> > dovecot-mysql.conf
> >
> > driver = mysql
> > connect = host=localhost dbname=mail user=user password=XXX
> > default_pass_scheme = CRYPT
> > password_query = SELECT password FROM users WHERE email = '%u'
> > user_query = SELECT
> > CONCAT('/var/vmail/',SUBSTRING_INDEX(email,'@',-1),'/',
> SUBSTRING_INDEX(email,'@',1),'/')
> > AS home,
> > CONCAT('maildir:/var/vmail/',SUBSTRING_INDEX(email,'@',-1),'
> /',SUBSTRING_INDEX(email,'@',1),'/Maildir/')
> > AS mail, 5000 AS uid, 5000 AS gid, concat('*:bytes=', quota) AS
> quota_rule
> > FROM users WHERE email = '%u'
> >
> >
> > Any help is appreciated.
> > Thanks
> > Stefan Koenig
>
Re: Ubuntu Dovecot 2.2.9 several Errors, Transaction log as well as BUG message
2.2.9 is rather old. Updating to a more recent version could help.
Aki
On 23.03.2017 10:48, Kein Name wrote:
> Hello List,
>
> I am running an Ubuntu 14.04.5 LTS Server with Dovecot 2.2.9, only local
> filesystems and authentication done via mysql backend.
> Server is a Strato Virtual Server running
> 2.6.32-042stab120.11 #1 SMP Fri Mar 10 16:52:50 MSK 2017 i686 i686 i686
> GNU/Linux
>
> Sometimes I see errors in the log like this for one user:
>
> Error: Transaction log /var/vmail/
> example.net/jena/Maildir/.Archives.2017/dovecot.index.log: duplicate
> transaction log sequence (2)
>
> After seeing these, some time later, (mostly 2h), Dovecot starts to deny
> login from all clients with messages like this:
>
> Mar 23 01:32:27 h2312250 dovecot: auth: Error: BUG: Authentication client
> sent unknown handshake command:
> REQUEST?1804861441?19318?1?9ce500129289a0237e4e85a6c880a047?session_pid=19323...
> Mar 23 01:32:27 h2312250 dovecot: imap: Error: Authentication server didn't
> send valid SPID as expected: MECH#011PLAIN#011plaintext
> Mar 23 01:32:27 h2312250 dovecot: imap: Error: Disconnected from auth
> server, aborting (client-pid=19318 client-id=1)
> Mar 23 01:32:27 h2312250 dovecot: imap-login: Internal login failure
> (pid=19318 id=1) (internal failure, 1 successful auths): user=<
> u...@example.net>, method=PLAIN, rip=X, lip=X, mpid=19323,
> session=
>
> I do not know if these problems have something to do with each other or
> not. But it happened several times now (maybe once or twice every month or
> so).
> When I restart Dovecot, the error seems gone for the moment, until it comes
> back in a month or some weeks.
>
>
> For reference, here is the running config:
>
> dovecot.conf
>
> # 2.2.9: /etc/dovecot/dovecot.conf
> # OS: Linux 2.6.32-042stab120.11 i686 Ubuntu 14.04.5 LTS
> auth_mechanisms = plain login
> auth_verbose = yes
> disable_plaintext_auth = no
> log_timestamp = "%Y-%m-%d %H:%M:%S "
> 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/dovecot-mysql.conf
> driver = sql
> }
> plugin {
> quota = maildir:User quota
> quota_rule = *:bytes=10M
> sieve = ~/dovecot.sieve
> }
> protocols = imap pop3 sieve
> service auth {
> unix_listener /var/spool/postfix/private/auth {
> group = postfix
> mode = 0660
> user = postfix
> }
> unix_listener auth-master {
> mode = 0600
> user = vmail
> }
> user = root
> }
> ssl_cert = ssl_key = userdb {
> args = /etc/dovecot/dovecot-mysql.conf
> driver = sql
> }
> protocol pop3 {
> mail_plugins = quota
> pop3_uidl_format = %08Xu%08Xv
> }
> protocol imap {
> mail_plugins = quota imap_quota
> }
> protocol lda {
> auth_socket_path = /var/run/dovecot/auth-master
> mail_plugins = sieve quota
> postmaster_address = postmas...@example.net
> quota_full_tempfail = yes
> }
>
>
> dovecot-mysql.conf
>
> driver = mysql
> connect = host=localhost dbname=mail user=user password=XXX
> default_pass_scheme = CRYPT
> password_query = SELECT password FROM users WHERE email = '%u'
> user_query = SELECT
> CONCAT('/var/vmail/',SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1),'/')
> AS home,
> CONCAT('maildir:/var/vmail/',SUBSTRING_INDEX(email,'@',-1),'/',SUBSTRING_INDEX(email,'@',1),'/Maildir/')
> AS mail, 5000 AS uid, 5000 AS gid, concat('*:bytes=', quota) AS quota_rule
> FROM users WHERE email = '%u'
>
>
> Any help is appreciated.
> Thanks
> Stefan Koenig
Ubuntu Dovecot 2.2.9 several Errors, Transaction log as well as BUG message
Hello List,
I am running an Ubuntu 14.04.5 LTS Server with Dovecot 2.2.9, only local
filesystems and authentication done via mysql backend.
Server is a Strato Virtual Server running
2.6.32-042stab120.11 #1 SMP Fri Mar 10 16:52:50 MSK 2017 i686 i686 i686
GNU/Linux
Sometimes I see errors in the log like this for one user:
Error: Transaction log /var/vmail/
example.net/jena/Maildir/.Archives.2017/dovecot.index.log: duplicate
transaction log sequence (2)
After seeing these, some time later, (mostly 2h), Dovecot starts to deny
login from all clients with messages like this:
Mar 23 01:32:27 h2312250 dovecot: auth: Error: BUG: Authentication client
sent unknown handshake command:
REQUEST?1804861441?19318?1?9ce500129289a0237e4e85a6c880a047?session_pid=19323...
Mar 23 01:32:27 h2312250 dovecot: imap: Error: Authentication server didn't
send valid SPID as expected: MECH#011PLAIN#011plaintext
Mar 23 01:32:27 h2312250 dovecot: imap: Error: Disconnected from auth
server, aborting (client-pid=19318 client-id=1)
Mar 23 01:32:27 h2312250 dovecot: imap-login: Internal login failure
(pid=19318 id=1) (internal failure, 1 successful auths): user=<
u...@example.net>, method=PLAIN, rip=X, lip=X, mpid=19323,
session=
I do not know if these problems have something to do with each other or
not. But it happened several times now (maybe once or twice every month or
so).
When I restart Dovecot, the error seems gone for the moment, until it comes
back in a month or some weeks.
For reference, here is the running config:
dovecot.conf
# 2.2.9: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-042stab120.11 i686 Ubuntu 14.04.5 LTS
auth_mechanisms = plain login
auth_verbose = yes
disable_plaintext_auth = no
log_timestamp = "%Y-%m-%d %H:%M:%S "
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/dovecot-mysql.conf
driver = sql
}
plugin {
quota = maildir:User quota
quota_rule = *:bytes=10M
sieve = ~/dovecot.sieve
}
protocols = imap pop3 sieve
service auth {
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
}
unix_listener auth-master {
mode = 0600
user = vmail
}
user = root
}
ssl_cert =
Re: Problem! Dovecot 2.2.9 does not send the information on ending the quota to user
Hi.
I installed the latest version of dovecot (v 2.2.21). But dovecot still doesn't
send the information on ending the quota to user.
# dovecot --version
2.2.21 (5345f22)
2015-12-19 7:27 GMT+03:00 Nick Edwards :
> before reporting an issue, please try a version made this millenium,
> 2.2.9 is older than my gran
> or take it up with your distro, dovecot doesnt make the distro version
> they do
>
> On 12/18/15, Serge Spinoza wrote:
> > Hi.
> >
> > I have Dovecot + Postfix + MySQL.
> > Version of Postix: postfix_2.11.3-1ubuntu1_amd64
> > Version of Dovecot: 2.2.9
> > Operations system is: Ubuntu 15.04 x64
> >
> > Postfix have patched (patch VDA - http://vda.sourceforge.net) for using
> > with quota, it means that file "maildirsize" in mail directory already
> > exists and changed when add/delete mail.
> >
> > Quota for virtual box take in MySQL db.
> >
> > ##
> >
> > Problem:
> >
> > Dovecot does not send the information on ending the quota to user.
> >
> > ##
> >
> >
> > # dovecot -n
> > # 2.2.9: /etc/dovecot/dovecot.conf
> > # OS: Linux 2.6.32-042stab112.15 x86_64 Ubuntu 15.04 ext4
> > auth_debug = yes
> > auth_default_realm = mydomain.ru
> > auth_mechanisms = plain login
> > auth_realms = znak-corp.ru
> > debug_log_path = /var/log/dovecot-debug.log
> > info_log_path = /var/log/dovecot.log
> > lda_mailbox_autocreate = yes
> > lda_mailbox_autosubscribe = yes
> > log_path = /var/log/dovecot.log
> > login_greeting = Welcome to OOO "Corporation ZNAK"
> > mail_gid = 1000
> > mail_location = maildir:/var/vmail/%n@%d
> > mail_plugins = " quota"
> > mail_uid = 1000
> > 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/dovecot-sql.conf.ext
> > driver = sql
> > }
> > plugin {
> > autocreate = INBOX
> > autosubscribe = INBOX
> > quota = maildir:User quota
> > quota_rule = *:storage=10M #(this derective takes from mysql, but i
> wrote
> > it just in case)
> > quota_warning = storage=90%% quota-warning 90 %u
> > quota_warning2 = storage=80%% quota-warning 80 %u
> > }
> > protocols = pop3 imap
> > quota_full_tempfail = yes
> > service auth {
> > unix_listener /var/spool/postfix/private/dovecot-smtp-auth {
> > group = postfix
> > mode = 0666
> > user = postfix
> > }
> > unix_listener auth-userdb {
> > group = vmail
> > mode = 0600
> > user = vmail
> > }
> > }
> > 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
> > }
> > }
> > service quota-status {
> > client_limit = 1
> > executable = /usr/lib/dovecot/quota-status -p postfix
> > inet_listener {
> > port = 12340
> > }
> > }
> > service quota-warning {
> > executable = script /usr/local/bin/quota-warning.sh
> > unix_listener quota-warning {
> > user = vmail
> > }
> > user = vmail
> > }
> > ssl_cert = > ssl_key = > userdb {
> > args = /etc/dovecot/dovecot-sql.conf.ext
> > driver = sql
> > }
> > protocol imap {
> > mail_plugins = " quota imap_quota autocreate"
> > }
> > protocol pop3 {
> > mail_plugins = quota
> > }
> > protocol lda {
> > mail_plugins = " quota autocreate"
> > }
> >
> >
> > #
> > quota-warning.sh
> > #
> >
> > #!/bin/sh
> > PERCENT=$1
> > USER=$2
> > cat << EOF | /usr/lib/dovecot/dovecot-lda -d $USER -o
> > "plugin/quota=maildir:User quota:noenforcing"
> > From: a...@mydomain.ru
> > Subject: Quota warning $PERCENT%
> >
> > Your mailbox is now $PERCENT% full.
> > Please remove unnecessary emails to avoid new mail loosing.
> > EOF
> >
> > #
> > Script has chmod 777
> > #
> >
> > root@mx:~# ls -la /u
Re: Problem! Dovecot 2.2.9 does not send the information on ending the quota to user
before reporting an issue, please try a version made this millenium,
2.2.9 is older than my gran
or take it up with your distro, dovecot doesnt make the distro version they do
On 12/18/15, Serge Spinoza wrote:
> Hi.
>
> I have Dovecot + Postfix + MySQL.
> Version of Postix: postfix_2.11.3-1ubuntu1_amd64
> Version of Dovecot: 2.2.9
> Operations system is: Ubuntu 15.04 x64
>
> Postfix have patched (patch VDA - http://vda.sourceforge.net) for using
> with quota, it means that file "maildirsize" in mail directory already
> exists and changed when add/delete mail.
>
> Quota for virtual box take in MySQL db.
>
> ##
>
> Problem:
>
> Dovecot does not send the information on ending the quota to user.
>
> ##
>
>
> # dovecot -n
> # 2.2.9: /etc/dovecot/dovecot.conf
> # OS: Linux 2.6.32-042stab112.15 x86_64 Ubuntu 15.04 ext4
> auth_debug = yes
> auth_default_realm = mydomain.ru
> auth_mechanisms = plain login
> auth_realms = znak-corp.ru
> debug_log_path = /var/log/dovecot-debug.log
> info_log_path = /var/log/dovecot.log
> lda_mailbox_autocreate = yes
> lda_mailbox_autosubscribe = yes
> log_path = /var/log/dovecot.log
> login_greeting = Welcome to OOO "Corporation ZNAK"
> mail_gid = 1000
> mail_location = maildir:/var/vmail/%n@%d
> mail_plugins = " quota"
> mail_uid = 1000
> 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/dovecot-sql.conf.ext
> driver = sql
> }
> plugin {
> autocreate = INBOX
> autosubscribe = INBOX
> quota = maildir:User quota
> quota_rule = *:storage=10M #(this derective takes from mysql, but i wrote
> it just in case)
> quota_warning = storage=90%% quota-warning 90 %u
> quota_warning2 = storage=80%% quota-warning 80 %u
> }
> protocols = pop3 imap
> quota_full_tempfail = yes
> service auth {
> unix_listener /var/spool/postfix/private/dovecot-smtp-auth {
> group = postfix
> mode = 0666
> user = postfix
> }
> unix_listener auth-userdb {
> group = vmail
> mode = 0600
> user = vmail
> }
> }
> 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
> }
> }
> service quota-status {
> client_limit = 1
> executable = /usr/lib/dovecot/quota-status -p postfix
> inet_listener {
> port = 12340
> }
> }
> service quota-warning {
> executable = script /usr/local/bin/quota-warning.sh
> unix_listener quota-warning {
> user = vmail
> }
> user = vmail
> }
> ssl_cert = ssl_key = userdb {
> args = /etc/dovecot/dovecot-sql.conf.ext
> driver = sql
> }
> protocol imap {
> mail_plugins = " quota imap_quota autocreate"
> }
> protocol pop3 {
> mail_plugins = quota
> }
> protocol lda {
> mail_plugins = " quota autocreate"
> }
>
>
> #
> quota-warning.sh
> #
>
> #!/bin/sh
> PERCENT=$1
> USER=$2
> cat << EOF | /usr/lib/dovecot/dovecot-lda -d $USER -o
> "plugin/quota=maildir:User quota:noenforcing"
> From: a...@mydomain.ru
> Subject: Quota warning $PERCENT%
>
> Your mailbox is now $PERCENT% full.
> Please remove unnecessary emails to avoid new mail loosing.
> EOF
>
> #
> Script has chmod 777
> #
>
> root@mx:~# ls -la /usr/local/bin/quota-warning.sh
> -rwxrwxrwx 1 vmail vmail 285 Dec 17 11:09 /usr/local/bin/quota-warning.sh
>
>
> Check the script this command is successful:
> # /usr/local/bin/quota-warning.sh 82 r...@mydomain.ru
>
> (a letter is sent to r...@mydomain.ru that box is filled to 82%)
>
>
>
> #
> dovecot-sql.conf.ext
> #
>
> driver = mysql
> connect = host=localhost dbname=postfix user=postfix password=xxx
>
> default_pass_scheme = MD5-CRYPT
>
> user_query = SELECT '/var/vmail/%n@%d' as home,
> 'maildir:/var/vmail/%n@%d'as
> mail, 1000 AS uid, 1000 AS gid, concat('*:bytes=', quota) AS quota_rule
> FROM mailbox WHERE username = '%u' AND active = '1'
>
> password_query = SELECT username as user, password, '/var/vmail/%n@%d' as
> userdb_home, 'maildir:/var/vmail/%n@%d' as userdb_mail, 1000 as
Problem! Dovecot 2.2.9 does not send the information on ending the quota to user
Hi.
I have Dovecot + Postfix + MySQL.
Version of Postix: postfix_2.11.3-1ubuntu1_amd64
Version of Dovecot: 2.2.9
Operations system is: Ubuntu 15.04 x64
Postfix have patched (patch VDA - http://vda.sourceforge.net) for using
with quota, it means that file "maildirsize" in mail directory already
exists and changed when add/delete mail.
Quota for virtual box take in MySQL db.
##
Problem:
Dovecot does not send the information on ending the quota to user.
##
# dovecot -n
# 2.2.9: /etc/dovecot/dovecot.conf
# OS: Linux 2.6.32-042stab112.15 x86_64 Ubuntu 15.04 ext4
auth_debug = yes
auth_default_realm = mydomain.ru
auth_mechanisms = plain login
auth_realms = znak-corp.ru
debug_log_path = /var/log/dovecot-debug.log
info_log_path = /var/log/dovecot.log
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
log_path = /var/log/dovecot.log
login_greeting = Welcome to OOO "Corporation ZNAK"
mail_gid = 1000
mail_location = maildir:/var/vmail/%n@%d
mail_plugins = " quota"
mail_uid = 1000
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/dovecot-sql.conf.ext
driver = sql
}
plugin {
autocreate = INBOX
autosubscribe = INBOX
quota = maildir:User quota
quota_rule = *:storage=10M #(this derective takes from mysql, but i wrote
it just in case)
quota_warning = storage=90%% quota-warning 90 %u
quota_warning2 = storage=80%% quota-warning 80 %u
}
protocols = pop3 imap
quota_full_tempfail = yes
service auth {
unix_listener /var/spool/postfix/private/dovecot-smtp-auth {
group = postfix
mode = 0666
user = postfix
}
unix_listener auth-userdb {
group = vmail
mode = 0600
user = vmail
}
}
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
}
}
service quota-status {
client_limit = 1
executable = /usr/lib/dovecot/quota-status -p postfix
inet_listener {
port = 12340
}
}
service quota-warning {
executable = script /usr/local/bin/quota-warning.sh
unix_listener quota-warning {
user = vmail
}
user = vmail
}
ssl_cert =
Re: [PATCH] [dovecot 2.2.9] Quota warnings ignored with FS quotas
On 23 Mar 2015, at 22:32, Michał Giżyński wrote:
>
>
> On 17.02.2015 20:03, Michał Giżyński wrote:
>>
>> On 21.11.2014 20:04, Grzegorz Nosek wrote:
>>> Hi all,
>>>
>>> I noticed that in some circumstances quota warnings are ignored. The bug
>>> arises when both of the following are used:
>>>
>>> 1. percentage-based quota warnings, i.e.:
>>>
>>> quota_warning = storage=1%% quota-warning 1 %u
>>>
>>> 2. filesystem quota backend (and probably others, except for quotas
>>> configured directly in dovecot config)
>>>
>>> Percentage-based quota warnings have rule.bytes_limit recalculated based on
>>> root_set->default_rule.bytes_limit, however this value is zero when FS
>>> quotas are in use. Real quota values (from quotactl) are fetched very late,
>>> in quota_warnings_execute() but at that point no recalculation happens. As
>>> the warning rules have bytes_limit==0, they're effectively ignored.
>>>
>>> The patch below enables quota warnings to be sent when using filesystem
>>> (and possibly maildirsize-based) quotas.
>>>
>>> Based and tested on Ubuntu 14.04's dovecot 2.2.9.
>>>
>>> Best regards,
>>> Grzegorz Nosek
>>>
>>>
>>> diff --git a/src/plugins/quota/quota.c b/src/plugins/quota/quota.c
>>> index adbd70d..8e4d7e0 100644
>>> --- a/src/plugins/quota/quota.c
>>> +++ b/src/plugins/quota/quota.c
>>> @@ -1163,6 +1163,8 @@ static void quota_warnings_execute(struct
>>> quota_transaction_context *ctx,
>>> &count_current, &count_limit) < 0)
>>>return;
>>>
>>> + quota_root_recalculate_relative_rules(root->set, bytes_limit,
>>> count_limit);
>>> +
>>>bytes_before = bytes_current - ctx->bytes_used;
>>>count_before = count_current - ctx->count_used;
>>>for (i = 0; i < count; i++) {
>> Hi,
>> this patch realy fix the bug in quota_warning. Is it possible to add this
>> patch to the next release ?
>>
> Hi,
> I saw that new dovecot was released. Is the quota_warning has been improved ?
That patch is doing a bit too many recalculations, which also always trigger
debug message logging if mail_debug=yes. The attached patch probably fixes the
problem? I'll add it after v2.2.20 is released (because it's affecting so many
different platforms that there's too big of a chance of it breaking one of them
due to some typo).
quota-fs-rules-recalc.diff
Description: Binary data
Re: [PATCH] [dovecot 2.2.9] Quota warnings ignored with FS quotas
On 17.02.2015 20:03, Michał Giżyński wrote:
On 21.11.2014 20:04, Grzegorz Nosek wrote:
Hi all,
I noticed that in some circumstances quota warnings are ignored. The
bug arises when both of the following are used:
1. percentage-based quota warnings, i.e.:
quota_warning = storage=1%% quota-warning 1 %u
2. filesystem quota backend (and probably others, except for quotas
configured directly in dovecot config)
Percentage-based quota warnings have rule.bytes_limit recalculated
based on root_set->default_rule.bytes_limit, however this value is
zero when FS quotas are in use. Real quota values (from quotactl) are
fetched very late, in quota_warnings_execute() but at that point no
recalculation happens. As the warning rules have bytes_limit==0,
they're effectively ignored.
The patch below enables quota warnings to be sent when using
filesystem (and possibly maildirsize-based) quotas.
Based and tested on Ubuntu 14.04's dovecot 2.2.9.
Best regards,
Grzegorz Nosek
diff --git a/src/plugins/quota/quota.c b/src/plugins/quota/quota.c
index adbd70d..8e4d7e0 100644
--- a/src/plugins/quota/quota.c
+++ b/src/plugins/quota/quota.c
@@ -1163,6 +1163,8 @@ static void quota_warnings_execute(struct
quota_transaction_context *ctx,
&count_current, &count_limit) < 0)
return;
+ quota_root_recalculate_relative_rules(root->set, bytes_limit,
count_limit);
+
bytes_before = bytes_current - ctx->bytes_used;
count_before = count_current - ctx->count_used;
for (i = 0; i < count; i++) {
Hi,
this patch realy fix the bug in quota_warning. Is it possible to add
this patch to the next release ?
Hi,
I saw that new dovecot was released. Is the quota_warning has been
improved ?
--
Pozdrawiam / Best Regards
Michał Giżyński
Re: [PATCH] [dovecot 2.2.9] Quota warnings ignored with FS quotas
On 21.11.2014 20:04, Grzegorz Nosek wrote:
Hi all,
I noticed that in some circumstances quota warnings are ignored. The
bug arises when both of the following are used:
1. percentage-based quota warnings, i.e.:
quota_warning = storage=1%% quota-warning 1 %u
2. filesystem quota backend (and probably others, except for quotas
configured directly in dovecot config)
Percentage-based quota warnings have rule.bytes_limit recalculated
based on root_set->default_rule.bytes_limit, however this value is
zero when FS quotas are in use. Real quota values (from quotactl) are
fetched very late, in quota_warnings_execute() but at that point no
recalculation happens. As the warning rules have bytes_limit==0,
they're effectively ignored.
The patch below enables quota warnings to be sent when using
filesystem (and possibly maildirsize-based) quotas.
Based and tested on Ubuntu 14.04's dovecot 2.2.9.
Best regards,
Grzegorz Nosek
diff --git a/src/plugins/quota/quota.c b/src/plugins/quota/quota.c
index adbd70d..8e4d7e0 100644
--- a/src/plugins/quota/quota.c
+++ b/src/plugins/quota/quota.c
@@ -1163,6 +1163,8 @@ static void quota_warnings_execute(struct
quota_transaction_context *ctx,
&count_current, &count_limit) < 0)
return;
+ quota_root_recalculate_relative_rules(root->set, bytes_limit,
count_limit);
+
bytes_before = bytes_current - ctx->bytes_used;
count_before = count_current - ctx->count_used;
for (i = 0; i < count; i++) {
Hi,
this patch realy fix the bug in quota_warning. Is it possible to add
this patch to the next release ?
--
Pozdrawiam / Best Regards
Michał Giżyński
[PATCH] [dovecot 2.2.9] Quota warnings ignored with FS quotas
Hi all,
I noticed that in some circumstances quota warnings are ignored. The bug
arises when both of the following are used:
1. percentage-based quota warnings, i.e.:
quota_warning = storage=1%% quota-warning 1 %u
2. filesystem quota backend (and probably others, except for quotas
configured directly in dovecot config)
Percentage-based quota warnings have rule.bytes_limit recalculated based
on root_set->default_rule.bytes_limit, however this value is zero when
FS quotas are in use. Real quota values (from quotactl) are fetched very
late, in quota_warnings_execute() but at that point no recalculation
happens. As the warning rules have bytes_limit==0, they're effectively
ignored.
The patch below enables quota warnings to be sent when using filesystem
(and possibly maildirsize-based) quotas.
Based and tested on Ubuntu 14.04's dovecot 2.2.9.
Best regards,
Grzegorz Nosek
diff --git a/src/plugins/quota/quota.c b/src/plugins/quota/quota.c
index adbd70d..8e4d7e0 100644
--- a/src/plugins/quota/quota.c
+++ b/src/plugins/quota/quota.c
@@ -1163,6 +1163,8 @@ static void quota_warnings_execute(struct
quota_transaction_context *ctx,
&count_current, &count_limit) < 0)
return;
+ quota_root_recalculate_relative_rules(root->set, bytes_limit,
count_limit);
+
bytes_before = bytes_current - ctx->bytes_used;
count_before = count_current - ctx->count_used;
for (i = 0; i < count; i++) {
]UG] Dovecot 2.2.9 SSL client cert verification fails: openssl verify: OK
Greetings all, I have verified a bug that has long been attributed to lack of knowledge on the part of the user. Dovecot rejects StartSSL client certificates due to reject StartSSL root CA when doing client verification even though the appropriately constructed ca-bundle.pem has been created and applied vi ssl_ca = ca-bundle.pem cat class1-client-crl.pem >>ca-bundle.pem openssl x509 -in startcom-root-ca.pem -subject -issuer >>ca-bundle.pem cat startcom-root-ca-crl.pem >>ca-bundle.pem Furthermore exim, Thunderbird, and Firefox are all perfectly happy with the certificates (and exim has no problem verifying the client certificates). Further, there are many more messages regarding issues with users of dovecot having issues with StartCom client certificates who have reported following all the steps than with Cyrus or Courier. Oh, and client verification of server-side certificate works fine with server-side certificate bundle (cat server.pem startcom-intermediate.pem startcom-root-ca.pem >dovecot.pem) Relevant dovecot -n included below: auth_debug = yes auth_mechanisms = plain login digest-md5 cram-md5 otp auth_ssl_require_client_cert = yes auth_verbose = yes ssl = required ssl_ca = signature.asc Description: OpenPGP digital signature
Re: Trouble getting listescape plugin to work with "$" separator (as demonstrated in Wiki) in Dovecot 2.2.9
On 10/02/2014 05:23 PM, Ben Johnson wrote:
> Now, the only problem I see is that when I attempt to create a new
> folder beneath the Inbox (whether it contains a "." or not), the folder
> appears at the root-level of the IMAP account, at the same level as the
> Inbox itself. The folder name is "INBOX.My Folder".
>
> Also, if I try to select the folder and view its contents, I receive the
> error, "Mailbox doesn't exist: INBOX.My Folder". But this may simply be
> a product of a misconfiguration on my part.
Namespace configuration can be a bit difficult. I urge you to read the wiki
page on namespaces carefully and test which
configuration works with your mail clients. It might be as easy, as renaming
the namespace you have now to inbox, eg:
namespace INBOX {
inbox = yes
location =
prefix =
separator = $
type = private
}
If that is not what you meant, or does not work for your clients, try with
several namespaces and setting the "prefix" in them.
br,
Teemu Huovila
Re: Trouble getting listescape plugin to work with "$" separator (as demonstrated in Wiki) in Dovecot 2.2.9
On 10/2/2014 9:57 AM, Teemu Huovila wrote: > On 10/01/2014 09:43 PM, Ben Johnson wrote: >> Ultimately, I have two questions: >> >> 1.) Is the nesting structure that I've employed correct? The Wiki 2 page >> is not clear with regard to the nesting; is it correct to put the >> "namespace" block inside the "protocol imap" block, as I demonstrated above? > I think it would be better, if you put the namespace configuration at the top > level. See > http://master.wiki2.dovecot.org/Namespaces or 10-mail.conf and > 15-mailboxes.conf, that are located in the > doc/example-config/conf.d/ directory of the Dovecot sources, for more > examples. > >> 2.) Is it possible to escape the dollar sign so that it can be used as >> the separator? > There was a mistake in the wiki. You should quote the $ like this: "$". > > br, > Teemu Huovila > Teemu, Thank you!!! Quoting the "$" fixed the syntax issue. And I moved the namespace to the root level of the configuration, per your advice. Now, the only problem I see is that when I attempt to create a new folder beneath the Inbox (whether it contains a "." or not), the folder appears at the root-level of the IMAP account, at the same level as the Inbox itself. The folder name is "INBOX.My Folder". Also, if I try to select the folder and view its contents, I receive the error, "Mailbox doesn't exist: INBOX.My Folder". But this may simply be a product of a misconfiguration on my part. For what it's worth, this seems to happen regardless of the separator that I define in the namespace. Do I need to change something else in the Dovecot config for this to work the way that I'm intending? Thanks again for your invaluable assistance, -Ben
Re: Trouble getting listescape plugin to work with "$" separator (as demonstrated in Wiki) in Dovecot 2.2.9
On 10/01/2014 09:43 PM, Ben Johnson wrote: > Ultimately, I have two questions: > > 1.) Is the nesting structure that I've employed correct? The Wiki 2 page > is not clear with regard to the nesting; is it correct to put the > "namespace" block inside the "protocol imap" block, as I demonstrated above? I think it would be better, if you put the namespace configuration at the top level. See http://master.wiki2.dovecot.org/Namespaces or 10-mail.conf and 15-mailboxes.conf, that are located in the doc/example-config/conf.d/ directory of the Dovecot sources, for more examples. > 2.) Is it possible to escape the dollar sign so that it can be used as > the separator? There was a mistake in the wiki. You should quote the $ like this: "$". br, Teemu Huovila
Trouble getting listescape plugin to work with "$" separator (as demonstrated in Wiki) in Dovecot 2.2.9
Hello,
I'm attempting to install the listescape plugin so that IMAP users are
able to include periods (.) and forward slashes (/) in IMAP directory names.
I'm following the instructions at
http://wiki2.dovecot.org/Plugins/Listescape , which imply that this can
be accomplished by enabling the listescape plugin and using the dollar
sign ($) as the separator.
With regard to my dovecot configuration, first, I changed
protocol imap {
mail_plugins = quota imap_quota antispam
}
to
protocol imap {
mail_plugins = quota imap_quota antispam listescape
namespace private {
separator = $
inbox = yes
}
}
When I start dovecot, I receive the following error:
doveconf: Warning: NOTE: You can get a new clean config file with:
doveconf -n > dovecot-new.conf
doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:102:
namespace private {} has been replaced by namespace { type=private }
Pretty straightforward; I made the required change to yield
protocol imap {
mail_plugins = quota imap_quota antispam listescape
namespace {
type = private
separator = $
inbox = yes
}
}
But now, when I attempt to start dovecot, I receive the following error:
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf
line 104: Unknown variable: $
doveconf: Error: managesieve-login: dump-capability process returned 89
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf
line 104: Unknown variable: $
Is it possible that the instructions at the Wiki 2 URL cited above are
out-of-date?
If I try to escape the $ with any other character (I'm just shooting in
the dark regarding possible escape characters, as I cannot find
definitive documentation that pertains to escaping $ in the dovecot
configuration), I receive yet another error:
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf:
Namespace '': Hierarchy separator must be only one character long
doveconf: Error: managesieve-login: dump-capability process returned 89
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf:
Namespace '': Hierarchy separator must be only one character long
Ultimately, I have two questions:
1.) Is the nesting structure that I've employed correct? The Wiki 2 page
is not clear with regard to the nesting; is it correct to put the
"namespace" block inside the "protocol imap" block, as I demonstrated above?
2.) Is it possible to escape the dollar sign so that it can be used as
the separator?
Full "doveconf -n" output is included below.
Thanks for any assistance,
-Ben
# doveconf -n
# 2.2.9: /etc/dovecot/dovecot.conf
doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf
line 104: Unknown variable: $
doveconf: Error: managesieve-login: dump-capability process returned 89
# OS: Linux 3.13.0-34-generic x86_64 Ubuntu 14.04.1 LTS
auth_mechanisms = plain login
disable_plaintext_auth = no
listen = *,[::]
log_timestamp = "%Y-%m-%d %H:%M:%S "
mail_debug = yes
mail_privileged_group = vmail
passdb {
args = /etc/dovecot/dovecot-sql.conf
driver = sql
}
plugin {
antispam_backend = pipe
antispam_debug_target = syslog
antispam_pipe_program = /bin/bash
antispam_pipe_program_args = /usr/local/bin/sa-learn-pipe.sh
antispam_pipe_program_notspam_arg = --ham
antispam_pipe_program_spam_arg = --spam
antispam_pipe_tmpdir = /tmp
antispam_spam_pattern_ignorecase = SPAM;JUNK
antispam_trash_pattern_ignorecase = trash;Deleted *
antispam_verbose_debug = 1
quota = dict:user::file:/var/vmail/%d/%n/.quotausage
quota_rule2 = Trash:storage=+100M
quota_rule3 = Junk:ignore
quota_rule4 = INBOX:storage=+100M
quota_warning = storage=100%% quota-reached 100 %u %d
quota_warning2 = storage=95%% quota-warning 95 %u %d
quota_warning3 = storage=80%% quota-warning 80 %u %d
quota_warning4 = -storage=100%% quota-below below %u %d
sieve = /var/vmail/%d/%n/.sieve
}
postmaster_address = postmas...@localhost.com
protocols = imap pop3 sieve
service auth {
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
}
unix_listener auth-userdb {
group = vmail
mode = 0600
user = vmail
}
user = root
}
service config {
unix_listener config {
group = vmail
mode = 0600
user = vmail
}
}
service imap-login {
client_limit = 1000
process_limit = 500
}
service quota-below {
executable = script /usr/local/bin/quota-below.sh
unix_listener quota-below {
group = vmail
mode = 0666
user = vmail
}
user = vmail
}
service quota-reached {
executable = script /usr/local/bin/quota-reached.sh
unix_listener quota-reached {
group = vmail
mode = 0666
user = vmail
}
user = vmail
}
service quota-warning {
executable = script /usr/local/bin/quota-warning.sh
unix_listener quota-warning {
group = vmail
mode = 0666
user = vmail
}
user = vmail
}
ssl_cert =
Re: Segfault dovecot 2.2.9
Simon Gareste wrote: > This outdated version is the one packaged in Ubuntu LTS 14.04.1, > which I believe I'm not the only one using. Updating the dovecot packages > provided by Ubuntu would certainly help. If Ubuntu packages segfault, you should file a bug report at Ubuntu Launchpad: https://help.ubuntu.com/community/ReportingBugs Regards Daniel
Re: Segfault dovecot 2.2.9
Am 28.07.2014 12:33, schrieb Simon Gareste: > Le 28/07/2014 12:14, Reindl Harald a écrit : >> Am 28.07.2014 09:44, schrieb Simon Gareste: >>> When trying to set up dovecot, I somehow managed to get a segfault. Trying >>> to launch dovecot from command line >>> (simply execute 'dovecot') results in the error message: >>> Segmentation fault (core dumped) >>> >>> Trying dovecot -n results in pretty much the same: >>> # 2.2.9: /etc/dovecot/dovecot.conf >>> Segmentation fault (core dumped) >>> >>> Looking at syslog, I see >>> doveconf[3676]: segfault at 200 ip 7fbb93c4fcb3 sp 7fff005b4c10 >>> error 4 in >>> libc-2.19.so[7fbb93c04000+1bc000] >> current is 2.2.13 >> >> so don't report problems with a outdated version instead >> just upgrade - there where bugfixes between 2.2.9 and >> 2.2.13 in context of segfaults here and there >> > Thank you. This outdated version is the one packaged in Ubuntu > LTS 14.04.1, which I believe I'm not the only one using that's the problem with all that LTS packages nobody knows what fixes they may have backported and what are missing, so the version number no longer says anything which makes it also impossible for the upstream developer to know the patchlevel that's why i build packages for server software the last 7 years on my own infrastructure from upstream sources Updating the dovecot packages provided by Ubuntu would certainly help. I understand that the version I'm > using is roughly 9 months old, but then the LTS was released 3 months ago, > why doesn't it include the 2.2.11 or > 2.2.12? > > And I found the solution in the end, the problem comes from > auth_debug_passwords=yes being the right thing, and > auth_debug_passwords=plain being source of segfault. I don't know where I got > the "plain" value in the first place, > but I certainly should have read more carefully some docs. I also don't know > if this was fixed later, but shouldn't > there be a verification on some values of some variables, when there are > limited values to which they can be defined? http://comments.gmane.org/gmane.mail.imap.dovecot/76231 signature.asc Description: OpenPGP digital signature
Re: Segfault dovecot 2.2.9
Le 28/07/2014 12:14, Reindl Harald a écrit : Am 28.07.2014 09:44, schrieb Simon Gareste: When trying to set up dovecot, I somehow managed to get a segfault. Trying to launch dovecot from command line (simply execute 'dovecot') results in the error message: Segmentation fault (core dumped) Trying dovecot -n results in pretty much the same: # 2.2.9: /etc/dovecot/dovecot.conf Segmentation fault (core dumped) Looking at syslog, I see doveconf[3676]: segfault at 200 ip 7fbb93c4fcb3 sp 7fff005b4c10 error 4 in libc-2.19.so[7fbb93c04000+1bc000] current is 2.2.13 so don't report problems with a outdated version instead just upgrade - there where bugfixes between 2.2.9 and 2.2.13 in context of segfaults here and there Thank you. This outdated version is the one packaged in Ubuntu LTS 14.04.1, which I believe I'm not the only one using. Updating the dovecot packages provided by Ubuntu would certainly help. I understand that the version I'm using is roughly 9 months old, but then the LTS was released 3 months ago, why doesn't it include the 2.2.11 or 2.2.12? And I found the solution in the end, the problem comes from auth_debug_passwords=yes being the right thing, and auth_debug_passwords=plain being source of segfault. I don't know where I got the "plain" value in the first place, but I certainly should have read more carefully some docs. I also don't know if this was fixed later, but shouldn't there be a verification on some values of some variables, when there are limited values to which they can be defined? Anyway, dovecot is running, all my apologizes for the unwanted spam. Simon
Re: Segfault dovecot 2.2.9
Am 28.07.2014 09:44, schrieb Simon Gareste: > One difference I noticed between the two servers is that on the failing one, > there is > no /var/run/dovecot. I presume this folder and its files are created once > dovecot is > launched, so that's why it's not present, and is only a symptom of the > failure, > not a cause? no, it is supposed to be created by package install and on modern systems where /var/run is a symlink to /run which is a tmpfs everytime at boot [root@mail:~]$ cat /usr/lib/tmpfiles.d/dovecot.conf d /run/dovecot 0755 root dovecot - signature.asc Description: OpenPGP digital signature
Re: Segfault dovecot 2.2.9
Am 28.07.2014 09:44, schrieb Simon Gareste: > When trying to set up dovecot, I somehow managed to get a segfault. Trying to > launch dovecot from command line > (simply execute 'dovecot') results in the error message: > Segmentation fault (core dumped) > > Trying dovecot -n results in pretty much the same: > # 2.2.9: /etc/dovecot/dovecot.conf > Segmentation fault (core dumped) > > Looking at syslog, I see > doveconf[3676]: segfault at 200 ip 7fbb93c4fcb3 sp 7fff005b4c10 error > 4 in libc-2.19.so[7fbb93c04000+1bc000] current is 2.2.13 so don't report problems with a outdated version instead just upgrade - there where bugfixes between 2.2.9 and 2.2.13 in context of segfaults here and there signature.asc Description: OpenPGP digital signature
Segfault dovecot 2.2.9
Hi all, When trying to set up dovecot, I somehow managed to get a segfault. Trying to launch dovecot from command line (simply execute 'dovecot') results in the error message: Segmentation fault (core dumped) Trying dovecot -n results in pretty much the same: # 2.2.9: /etc/dovecot/dovecot.conf Segmentation fault (core dumped) Looking at syslog, I see doveconf[3676]: segfault at 200 ip 7fbb93c4fcb3 sp 7fff005b4c10 error 4 in libc-2.19.so[7fbb93c04000+1bc000] I tried but couldn't find the core dump anywhere on the server. Any help on this would be appreciated too. I (trying to ) run it with postfix, on an Ubuntu 14.04 (Linux mail2.arturia.com 3.13.0-32-generic #57-Ubuntu SMP Tue Jul 15 03:51:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux), brand new server. What troubles me even more is that I just set up successfully another mail server a week ago, with the same configuration (diffing the conf folders) except for log or mailbox paths (driver and stuff are the same). In the google search I've done, I saw some stuff about openssl: both servers are running 1.0.1f, since one is running fine, I guess this is not the culprit. One difference I noticed between the two servers is that on the failing one, there is no /var/run/dovecot. I presume this folder and its files are created once dovecot is launched, so that's why it's not present, and is only a symptom of the failure, not a cause? Thanks for your help, and please tell me what other information I could provide to help. Simon
Re: [Dovecot] dovecot 2.2.9 - ssl_cert and ssl_key ignored
On 5/11/2014 5:14 AM, Alexandru Bostina wrote: Nevermind, I think I found the problem. It seems that Ubuntu's default settings for Dovecot are wrong, they lack the "<" character before the certificate/key path. So either of the following works: ssl_cert_file = /dat/etc/ssl/certs/server.crt ssl_key_file = /dat/etc/ssl/private/server.key or ssl_cert = ssl_key = The latter is what was showing in the config you posted in the OP? -- Best regards, Charles
Re: [Dovecot] dovecot 2.2.9 - ssl_cert and ssl_key ignored
Nevermind, I think I found the problem. It seems that Ubuntu's default settings for Dovecot are wrong, they lack the "<" character before the certificate/key path. So either of the following works: ssl_cert_file = /dat/etc/ssl/certs/server.crt ssl_key_file = /dat/etc/ssl/private/server.key or ssl_cert = mailto:a...@alnio.ro> *Sent:* Sunday, May 11, 2014 12:04PM *To:* Peter Chiochetti <mailto:p...@myzel.net>, Dovecot <mailto:dovecot@dovecot.org> *Subject:* Re: [Dovecot] dovecot 2.2.9 - ssl_cert and ssl_key ignored Yes, it does. But I mentioned that just using the old settings (ssl_key_file) works (with the same certificate and key). *From:* Peter Chiochetti<mailto:p...@myzel.net> *Sent:* Sunday, May 11, 2014 11:58AM *To:* Alexandru Bostina<mailto:a...@alnio.ro>, Dovecot <mailto:dovecot@dovecot.org> *Subject:* Re: [Dovecot] dovecot 2.2.9 - ssl_cert and ssl_key ignored > Am 2014-05-11 10:16, schrieb Alexandru Bostina: > > Hello, > > > > It seems that Dovecot ignores the new /ssl_cert and ssl_key /settings. > > > > Using them in the dovecot configuration results in the error: > > Fatal: Couldn't parse private ssl_key: error:0906D06C:PEM > > routines:PEM_read_bio:no start line: Expecting: ANY PRIVATE KEY] > > > > Does the file read something like this in the first line? > > > -BEGIN RSA PRIVATE KEY- >
Re: [Dovecot] dovecot 2.2.9 - ssl_cert and ssl_key ignored
Yes, it does. But I mentioned that just using the old settings (ssl_key_file) works (with the same certificate and key). *From:* Peter Chiochetti <mailto:p...@myzel.net> *Sent:* Sunday, May 11, 2014 11:58AM *To:* Alexandru Bostina <mailto:a...@alnio.ro>, Dovecot <mailto:dovecot@dovecot.org> *Subject:* Re: [Dovecot] dovecot 2.2.9 - ssl_cert and ssl_key ignored Am 2014-05-11 10:16, schrieb Alexandru Bostina: > Hello, > > It seems that Dovecot ignores the new /ssl_cert and ssl_key /settings. > > Using them in the dovecot configuration results in the error: > Fatal: Couldn't parse private ssl_key: error:0906D06C:PEM > routines:PEM_read_bio:no start line: Expecting: ANY PRIVATE KEY] > Does the file read something like this in the first line? > -BEGIN RSA PRIVATE KEY-
Re: [Dovecot] dovecot 2.2.9 - ssl_cert and ssl_key ignored
Am 2014-05-11 10:16, schrieb Alexandru Bostina: Hello, It seems that Dovecot ignores the new /ssl_cert and ssl_key /settings. Using them in the dovecot configuration results in the error: Fatal: Couldn't parse private ssl_key: error:0906D06C:PEM routines:PEM_read_bio:no start line: Expecting: ANY PRIVATE KEY] Does the file read something like this in the first line? -BEGIN RSA PRIVATE KEY- -- peter
[Dovecot] dovecot 2.2.9 - ssl_cert and ssl_key ignored
Hello, It seems that Dovecot ignores the new /ssl_cert and ssl_key /settings. Using them in the dovecot configuration results in the error: Fatal: Couldn't parse private ssl_key: error:0906D06C:PEM routines:PEM_read_bio:no start line: Expecting: ANY PRIVATE KEY] Using the old /ssl_//cert//_file/ and /ssl_key_file/ results in their being obsolete warning but no fatal error. # 2.2.9: /etc/dovecot/dovecot.conf doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:107: ssl_cert_file has been replaced by ssl_cert =
Re: [Dovecot] dovecot 2.2.9 replication
On 3/12/2014 9:00 AM, Костырев Александр Алексеевич wrote: Good afternoon, I have a problem with replication is configured in Dovecot, I have two servers, they are version 2.2.9. Here is their configuration /root@mx1:/etc/dovecot# dovecot -n// //# 2.2.9: /etc/dovecot/dovecot.conf// What's with all those extraneous slashes?? -- Best regards, Charles
Re: [Dovecot] dovecot 2.2.9 replication
I didn't get it.
What's wrong ?
What's not working?
-Original Message-
From: dovecot [mailto:dovecot-boun...@dovecot.org] On Behalf Of Франчук Олег
Sent: Wednesday, March 12, 2014 10:37 PM
To: dovecot@dovecot.org
Subject: [Dovecot] dovecot 2.2.9 replication
Good afternoon, I have a problem with replication is configured in
Dovecot, I have two servers, they are version 2.2.9. Here is their
configuration
/root@mx1:/etc/dovecot# dovecot -n//
//# 2.2.9: /etc/dovecot/dovecot.conf//
//# OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4 ext4//
//auth_debug = yes//
//auth_debug_passwords = yes//
//auth_mechanisms = plain login//
//auth_socket_path = /var/run/dovecot/auth-master//
//base_dir = /var/run/dovecot///
//disable_plaintext_auth = no//
//dsync_remote_cmd = /usr/bin/ssh -l Debian-exim %{host}
/usr/bin/doveadm dsync-server -u//%u//-l%{lock_timeout} -n%{namespace}//
//first_valid_gid = 103//
//first_valid_uid = 101//
//listen = *//
//mail_access_groups = mail,Debian-exim,dovecot//
//mail_debug = yes//
//mail_full_filesystem_access = yes//
//mail_gid = 103//
//mail_location = maildir:/var/vmail/%d/%n//
//mail_plugins = " notify replication"//
//mail_uid = 101//
//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//
//namespace inbox {//
// inbox = yes//
// location
=
//
// prefix
=
//
//}
//
//passdb
{
//
// args =
/etc/dovecot/dovecot-ldap.conf
//
// driver =
ldap
//
//}
//
//plugin {//
// autocreate = Trash//
// autocreate2 = Sent//
// autocreate3 = Drafts//
// autocreate4 = Junk//
// autosubscribe = Trash//
// autosubscribe2 = Sent//
// autosubscribe3 = Drafts//
// autosubscribe4 = Junk//
// mail_replica = remote:Debian-exim at 10.0.1.2//
// sieve = /var/vmail/%d/%n/currently-active-script.sieve//
// sieve_dir = /var/vmail/%d/%n/sieve//
//}//
//protocols = imap sieve pop3//
//service aggregator {//
// fifo_listener replication-notify-fifo {//
//mode = 0777//
//user = Debian-exim//
// }//
// unix_listener replication-notify {//
//mode = 0777//
//user = Debian-exim//
// }//
//}//
//service auth {//
// unix_listener auth-client {//
//group = Debian-exim//
//mode = 0666//
//user = Debian-exim//
// }//
// unix_listener auth-master {//
//group = Debian-exim//
//mode = 0666//
//user = Debian-exim//
// }//
// user = root//
//}//
//service config {//
// unix_listener config {//
//mode = 0777//
//user = Debian-exim//
// }//
//}//
//service doveadm {//
// user = Debian-exim//
//}//
//service imap-login {//
// inet_listener imap {//
//address = 127.0.0.1,209.51.169.117,10.0.1.1//
//port = 143//
// }//
//}//
//service managesieve-login {//
// executable = /usr/lib/dovecot/managesieve-login//
// inet_listener sieve {//
//address = 127.0.0.1,209.51.169.117,10.0.1.1//
//port = 2000//
// }//
// process_min_avail = 1//
// service_count = 1//
// vsz_limit = 64 M//
//}//
//service managesieve {//
// executable = /usr/lib/dovecot/managesieve//
// process_limit = 10//
//}//
//service pop3-login {//
// inet_listener pop3 {//
//address = 127.0.0.1,209.51.169.117,10.0.1.1//
//port = 110//
// }//
//}//
//service replicator {//
// process_min_avail = 1//
// unix_listener replicator-doveadm {//
//mode = 0777//
//user = Debian-exim//
// }//
// unix_listener replicator {//
//mode = 0777//
//user = Debian-exim//
// }//
//}//
//ssl = no//
//userdb {//
// args = /etc/dovecot/dovecot-ldap.conf//
// driver = ldap//
//}//
//protocol lda {//
//
[Dovecot] dovecot 2.2.9 replication
<>
[Dovecot] [Dovecot 2.2.9] mail-filter plugin don't load
Hello, I'm trying to load the mail-filter plugin (dovecot-2.2.9) with the following option in 10-mail.conf : mail_plugins = $mail_plugins mail_filter But I've got the following error when restarting dovecot : dovecot: imap: Fatal: Plugin 'mail_filter' not found from directory /usr/local/lib/dovecot I reinstalled dovecot-2.2.9 from sources (freeBSD ports) but it did not install the mail-filter library in /usr/local/lib/dovecot Thank you for your help. - Stanislas SABATIER s.sabat...@pobox.com ---
Re: [Dovecot] No Dovecot 2.2.9 on OpenBSD 5.4 amd64
On 7.12.2013, at 6.35, Philippe Lelédy wrote: > doveconf -n > # 2.2.9: /etc/dovecot/dovecot.conf > doveconf: Fatal: pool_system_realloc(536870912): Out of memory Maybe this shows where it’s failing: DEBUG_OUTOFMEM=1 gdb —args doveconf -n bt full
[Dovecot] No Dovecot 2.2.9 on OpenBSD 5.4 amd64
Hi, First I have this warning when configuring: configure: WARNING: sys/ucred.h: present but cannot be compiled configure: WARNING: sys/ucred.h: check for missing prerequisite headers? configure: WARNING: sys/ucred.h: see the Autoconf documentation configure: WARNING: sys/ucred.h: section "Present But Cannot Be Compiled" configure: WARNING: sys/ucred.h: proceeding with the compiler's result configure: WARNING: ## -- ## configure: WARNING: ## Report this to dovecot@dovecot.org ## configure: WARNING: ## -- ## So I do ! Second, make builds fine, but doveconf not: doveconf -n # 2.2.9: /etc/dovecot/dovecot.conf doveconf: Fatal: pool_system_realloc(536870912): Out of memory Because I can't run doveconf, I give the only information I can get dovecot --version 2.2.9 and dovecot --build-options Build options: ioloop=kqueue notify=kqueue ipv6 openssl io_block_size=8192 Mail storages: shared mdbox sdbox maildir mbox cydir imapc pop3c raw fail SQL drivers: Passdb: bsdauth checkpassword passwd passwd-file Userdb: checkpassword passwd prefetch passwd-file Install prefix . : /usr/local File offsets ... : 64bit I/O polling : kqueue I/O notifys : kqueue SSL : yes (OpenSSL) GSSAPI . : no passdbs : static passwd passwd-file checkpassword bsdauth : -shadow -pam -sia -ldap -sql -vpopmail userdbs : static prefetch passwd passwd-file checkpassword : -ldap -sql -vpopmail -nss SQL drivers : : -pgsql -mysql -sqlite Full text search : squat : -lucene -solr Ph. Le.
Re: [Dovecot] 2.2.9
On 11/24/13, Eugene wrote: > Hi all, > > In recent years I use dovecot installed from FreeBSD ports. Interestingly, I > > feel that they follow the dovecot releases rather well but with some lag, > e.g. currently it is at 2.2.6. I don't know if that is 'by design' or caused > > by lack of manpower, but it works pretty well in that problems usually get > fixed before the update =) > (And then again, nobody says you should install a new version on the release > > day). > > Also, I am not sure RCs as such would do much good, since most of the test > systems are not likely to reproduce the volume and diversity of production > workloads. > you dont do any testing for software do you? :) I do for one very popular bit of software, although we can not test for every configuration, loading and stress testing is very common on all configurations we do check :)
Re: [Dovecot] 2.2.9
On 11/24/13, Luuk wrote: > On 23-11-2013 18:44, Andreas Kasenides wrote: >> On 23-11-2013 3:47, Noel Butler wrote: >>> These would be found if Timo reverted back to issuing RC's before any >>> official release, to iron out the niggly off-putting bugs, like most > > >> I second this and offer my services for two, three different system > > What is the difference between a 'RC' and a new version? > > One should TEST this new version ALWAYS before using it in production > (it does not matter if there was a 'RC' before it...) > this is why most softwares have a group of people testing them, so when you "test it" you hopefully dont find any. > 2 cents > > ;) > > > >
Re: [Dovecot] 2.2.9
On 11/24/13, Andreas Kasenides wrote: > On 23-11-2013 3:47, Noel Butler wrote: >> On Fri, 2013-11-22 at 10:14 +0100, Ralf Hildebrandt wrote: >> >>> * Thomas Leuxner : >>> > * Ralf Hildebrandt 2013.11.22 09:44: >>> > >>> > > Which patch? >>> > >>> > http://www.dovecot.org/list/dovecot/2013-November/093654.html >>> > >>> > Pigeonhole related patches. >>> >>> Damn. Those are biting me as well :/ >>> >> >> >> These would be found if Timo reverted back to issuing RC's before any >> official release, to iron out the niggly off-putting bugs, like most >> software does, or gets his devs and a community of official testers >> each >> with wildly different configurations and set ups, ASF have an excellent >> model that could be followed, bunch of devs and testers who each report >> on different distros and configs, why? because no single dev can >> imagine >> and test every possible configuration. it might just save dovecot's >> good name, I recall a lot of damage was done to that in the circles I'm >> in when 2.0 was released with patches nearly every few days and weeks, >> I >> know a few ISP's and businesses that went back to courier or Wu's >> because major bugs were getting in often, though it has been a lot >> better since 2.1 series, until this release that is :) > > I second this and offer my services for two, three different system > configs from Dovecot's plain old simple config with MAILDIR to slightly > more complicated > configurations with proxying/LDAP/dsync/mySQL etc based on > virtualization with KVM. > > I also propose that upon employing above strategy that Timo should come > up with a > release cycles (long term, short term) with announced targets. Patches > should be released as patches strictly as needed, not releases, and > should be announced on a low traffic list like he is already doing with > releases. OR something along these lines. > careful, or the suckups will go you next :) > I know these are growing pains but essential. Email systems are CRITICAL > for most of us. > dovecot is over 10 years, most softwares overcome these in the first couple of years > Andreas >
Re: [Dovecot] 2.2.9
I wonder if you have the balls to send to that him so he can see it, he did say he unsubscribed all to often I see heros like you, you're like the bitchy kid who waits for someone to walk out the room then bitch about them. On 11/23/13, Rick Romero wrote: > Noel, > > I include you in the gang of three, and I only read half the posts on this > list. I have no specific reason to, but it isn't a good association. > > A decade ago I was active on the Pegasus mail and Mercury lists, and names > stood out after a while. Unfortunately on this list, the names stand out for > a completely different reason - and its not positive. > > Just chill, everyone. You never know who's going to interview you in a > year. > > Rick
Re: [Dovecot] error while compiling dovecot 2.2.9
On 25-11-2013 20:38, Reindl Harald wrote:
Am 25.11.2013 20:31, schrieb Luuk:
On 25-11-2013 20:04, Timo Sirainen wrote:
On 25.11.2013, at 19.36, Luuk wrote:
while doing 'sudo make install',
its complaining about the existance of ‘/usr/local/lib/dovecot/auth’
Don’t use the same directory for libexecdir and moduledir.
Configured with: ../configure --prefix=/usr
i doubt that this would end in /usr/local/ at all
They seem to be different:
libexecdir='${exec_prefix}/lib'
moduledir='${exec_prefix}/lib/dovecot'
normally you would have /usr/local/lib/dovecot and /usr/local/libexec/dovecot
or for a x86_64 OS /usr/lib64/ like below
[harry@rh:~]$ rpm -q --filesbypkg dovecot | grep dovecot/auth
dovecot /usr/lib64/dovecot/auth
dovecot /usr/lib64/dovecot/auth/libauthdb_imap.so
dovecot /usr/lib64/dovecot/auth/libdriver_mysql.so
dovecot /usr/libexec/dovecot/auth
i started with configure:
./configure --with-sql=yes --with-mysql --with-sqlite
./configure --help
ok, i changed it to:
./configure --with-sql=yes --with-mysql --with-sqlite
--libexecdir=/usr/local/libexec/dovecot
--with-moduledir=/usr/local/lib/dovecot
and now 'make install' worked.
tomorrow i'll start with configuring... ;)
Re: [Dovecot] error while compiling dovecot 2.2.9
Am 25.11.2013 20:31, schrieb Luuk:
> On 25-11-2013 20:04, Timo Sirainen wrote:
>> On 25.11.2013, at 19.36, Luuk wrote:
>>
>>> while doing 'sudo make install',
>>> its complaining about the existance of ‘/usr/local/lib/dovecot/auth’
>>
>> Don’t use the same directory for libexecdir and moduledir.
>
> Configured with: ../configure --prefix=/usr
i doubt that this would end in /usr/local/ at all
> They seem to be different:
> libexecdir='${exec_prefix}/lib'
> moduledir='${exec_prefix}/lib/dovecot'
normally you would have /usr/local/lib/dovecot and /usr/local/libexec/dovecot
or for a x86_64 OS /usr/lib64/ like below
[harry@rh:~]$ rpm -q --filesbypkg dovecot | grep dovecot/auth
dovecot /usr/lib64/dovecot/auth
dovecot /usr/lib64/dovecot/auth/libauthdb_imap.so
dovecot /usr/lib64/dovecot/auth/libdriver_mysql.so
dovecot /usr/libexec/dovecot/auth
> i started with configure:
> ./configure --with-sql=yes --with-mysql --with-sqlite
./configure --help
signature.asc
Description: OpenPGP digital signature
Re: [Dovecot] error while compiling dovecot 2.2.9
On 25-11-2013 19:54, Oscar del Rio wrote: On 11/25/13 01:40 PM, Luuk wrote: On 25-11-2013 19:36, Luuk wrote: while doing 'sudo make install', its complaining about the existance of ‘/usr/local/lib/dovecot/auth’ . /usr/bin/mkdir -p '/usr/local/lib/dovecot/auth' /usr/bin/mkdir: cannot create directory ‘/usr/local/lib/dovecot/auth’: File exists any tips on what i did wrong? i'm able to provide more info, if only i knew what info is needed ;) ls -ld /usr/local/lib/dovecot/auth luuk@asus:~/source/dovecot-2.2.9> ls -ld /usr/local/lib/dovecot/auth -rwxr-xr-x 1 root root 1356716 Nov 25 19:36 /usr/local/lib/dovecot/auth luuk@asus:~/source/dovecot-2.2.9>
Re: [Dovecot] error while compiling dovecot 2.2.9
On 25-11-2013 20:04, Timo Sirainen wrote:
On 25.11.2013, at 19.36, Luuk wrote:
while doing 'sudo make install',
its complaining about the existance of ‘/usr/local/lib/dovecot/auth’
Don’t use the same directory for libexecdir and moduledir.
luuk@asus:~/source/dovecot-2.2.9> grep -ir libexecdir config.log
| # If user did not specify libexecdir, set the correct target:
| if test "$libexecdir" = '${exec_prefix}/libexec' ; then
| libexecdir='${exec_prefix}/lib'
Configured with: ../configure --prefix=/usr --infodir=/usr/share/info
--mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib
--enable-languages=c,c++,objc,fortran,obj-c++,java,ada
--enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.7
--enable-ssp --disable-libssp --disable-libitm --disable-plugin
--with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux'
--disable-libgcj --disable-libmudflap --with-slibdir=/lib
--with-system-zlib --enable-__cxa_atexit
--enable-libstdcxx-allocator=new --disable-libstdcxx-pch
--enable-version-specific-runtime-libs --enable-linker-build-id
--program-suffix=-4.7 --enable-linux-futex --without-system-libunwind
--with-arch-32=i586 --with-tune=generic --build=i586-suse-linux
Configured with: ../configure --prefix=/usr --infodir=/usr/share/info
--mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib
--enable-languages=c,c++,objc,fortran,obj-c++,java,ada
--enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.7
--enable-ssp --disable-libssp --disable-libitm --disable-plugin
--with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux'
--disable-libgcj --disable-libmudflap --with-slibdir=/lib
--with-system-zlib --enable-__cxa_atexit
--enable-libstdcxx-allocator=new --disable-libstdcxx-pch
--enable-version-specific-runtime-libs --enable-linker-build-id
--program-suffix=-4.7 --enable-linux-futex --without-system-libunwind
--with-arch-32=i586 --with-tune=generic --build=i586-suse-linux
Configured with: ../configure --prefix=/usr --infodir=/usr/share/info
--mandir=/usr/share/man --libdir=/usr/lib --libexecdir=/usr/lib
--enable-languages=c,c++,objc,fortran,obj-c++,java,ada
--enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.7
--enable-ssp --disable-libssp --disable-libitm --disable-plugin
--with-bugurl=http://bugs.opensuse.org/ --with-pkgversion='SUSE Linux'
--disable-libgcj --disable-libmudflap --with-slibdir=/lib
--with-system-zlib --enable-__cxa_atexit
--enable-libstdcxx-allocator=new --disable-libstdcxx-pch
--enable-version-specific-runtime-libs --enable-linker-build-id
--program-suffix=-4.7 --enable-linux-futex --without-system-libunwind
--with-arch-32=i586 --with-tune=generic --build=i586-suse-linux
libexecdir='${exec_prefix}/lib'
luuk@asus:~/source/dovecot-2.2.9> grep -ir moduledir config.log
moduledir='${exec_prefix}/lib/dovecot'
luuk@asus:~/source/dovecot-2.2.9>
They seem to be different:
libexecdir='${exec_prefix}/lib'
moduledir='${exec_prefix}/lib/dovecot'
i started with configure:
./configure --with-sql=yes --with-mysql --with-sqlite
Re: [Dovecot] error while compiling dovecot 2.2.9
On 25.11.2013, at 19.36, Luuk wrote: > while doing 'sudo make install', > its complaining about the existance of ‘/usr/local/lib/dovecot/auth’ Don’t use the same directory for libexecdir and moduledir.
Re: [Dovecot] error while compiling dovecot 2.2.9
On 11/25/13 01:40 PM, Luuk wrote: On 25-11-2013 19:36, Luuk wrote: while doing 'sudo make install', its complaining about the existance of ‘/usr/local/lib/dovecot/auth’ . /usr/bin/mkdir -p '/usr/local/lib/dovecot/auth' /usr/bin/mkdir: cannot create directory ‘/usr/local/lib/dovecot/auth’: File exists any tips on what i did wrong? i'm able to provide more info, if only i knew what info is needed ;) ls -ld /usr/local/lib/dovecot/auth
Re: [Dovecot] error while compiling dovecot 2.2.9
On 25-11-2013 19:36, Luuk wrote: while doing 'sudo make install', its complaining about the existance of ‘/usr/local/lib/dovecot/auth’ . make[3]: Entering directory `/home/luuk/source/dovecot-2.2.9/src/anvil' /usr/bin/mkdir -p '/usr/local/lib/dovecot' /bin/sh ../../libtool --mode=install /usr/bin/install -c anvil '/usr/local/lib/dovecot' libtool: install: /usr/bin/install -c .libs/anvil /usr/local/lib/dovecot/anvil make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/home/luuk/source/dovecot-2.2.9/src/anvil' make[2]: Leaving directory `/home/luuk/source/dovecot-2.2.9/src/anvil' Making install in auth make[2]: Entering directory `/home/luuk/source/dovecot-2.2.9/src/auth' make[3]: Entering directory `/home/luuk/source/dovecot-2.2.9/src/auth' /usr/bin/mkdir -p '/usr/local/lib/dovecot' /bin/sh ../../libtool --mode=install /usr/bin/install -c auth checkpassword-reply '/usr/local/lib/dovecot' libtool: install: /usr/bin/install -c .libs/auth /usr/local/lib/dovecot/auth libtool: install: /usr/bin/install -c .libs/checkpassword-reply /usr/local/lib/dovecot/checkpassword-reply /usr/bin/mkdir -p '/usr/local/lib/dovecot/auth' /usr/bin/mkdir: cannot create directory ‘/usr/local/lib/dovecot/auth’: File exists make[3]: *** [install-auth_moduleLTLIBRARIES] Error 1 make[3]: Leaving directory `/home/luuk/source/dovecot-2.2.9/src/auth' make[2]: *** [install-am] Error 2 make[2]: Leaving directory `/home/luuk/source/dovecot-2.2.9/src/auth' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/home/luuk/source/dovecot-2.2.9/src' make: *** [install-recursive] Error 1 luuk@asus:~/source/dovecot-2.2.9> any tips on what i did wrong? i'm able to provide more info, if only i knew what info is needed ;) it's a new install from the downloaded sources: -rw-r--r-- 1 luuk users 4540858 Nov 25 19:05 dovecot-2.2.9.tar.gz luuk@asus:~/source/dovecot-2.2.9> cat /etc/os-release NAME=openSUSE VERSION="12.3 (Dartmouth)" VERSION_ID="12.3" PRETTY_NAME="openSUSE 12.3 (Dartmouth) (i586)" ID=opensuse ANSI_COLOR="0;32" CPE_NAME="cpe:/o:opensuse:opensuse:12.3" luuk@asus:~/source/dovecot-2.2.9>
[Dovecot] error while compiling dovecot 2.2.9
while doing 'sudo make install', its complaining about the existance of ‘/usr/local/lib/dovecot/auth’ . make[3]: Entering directory `/home/luuk/source/dovecot-2.2.9/src/anvil' /usr/bin/mkdir -p '/usr/local/lib/dovecot' /bin/sh ../../libtool --mode=install /usr/bin/install -c anvil '/usr/local/lib/dovecot' libtool: install: /usr/bin/install -c .libs/anvil /usr/local/lib/dovecot/anvil make[3]: Nothing to be done for `install-data-am'. make[3]: Leaving directory `/home/luuk/source/dovecot-2.2.9/src/anvil' make[2]: Leaving directory `/home/luuk/source/dovecot-2.2.9/src/anvil' Making install in auth make[2]: Entering directory `/home/luuk/source/dovecot-2.2.9/src/auth' make[3]: Entering directory `/home/luuk/source/dovecot-2.2.9/src/auth' /usr/bin/mkdir -p '/usr/local/lib/dovecot' /bin/sh ../../libtool --mode=install /usr/bin/install -c auth checkpassword-reply '/usr/local/lib/dovecot' libtool: install: /usr/bin/install -c .libs/auth /usr/local/lib/dovecot/auth libtool: install: /usr/bin/install -c .libs/checkpassword-reply /usr/local/lib/dovecot/checkpassword-reply /usr/bin/mkdir -p '/usr/local/lib/dovecot/auth' /usr/bin/mkdir: cannot create directory ‘/usr/local/lib/dovecot/auth’: File exists make[3]: *** [install-auth_moduleLTLIBRARIES] Error 1 make[3]: Leaving directory `/home/luuk/source/dovecot-2.2.9/src/auth' make[2]: *** [install-am] Error 2 make[2]: Leaving directory `/home/luuk/source/dovecot-2.2.9/src/auth' make[1]: *** [install-recursive] Error 1 make[1]: Leaving directory `/home/luuk/source/dovecot-2.2.9/src' make: *** [install-recursive] Error 1 luuk@asus:~/source/dovecot-2.2.9> any tips on what i did wrong?
Re: [Dovecot] 2.2.9
Am 23.11.2013 20:08, schrieb Eugene: > In recent years I use dovecot installed from FreeBSD ports. Interestingly, I > feel that they follow the dovecot > releases rather well but with some lag, e.g. currently it is at 2.2.6. I > don't know if that is 'by design' or > caused by lack of manpower, but it works pretty well in that problems usually > get fixed before the update =) > (And then again, nobody says you should install a new version on the release > day). > > Also, I am not sure RCs as such would do much good, since most of the test > systems are not likely to reproduce the > volume and diversity of production workloads. in general RCs are doing good for several reasons * confirm bugs in whatever patches flying around are confirmed to fix * verify that there are no show-stoppers * verify that patches flying around have no obvious regressions don't know what release exactly it was, but one of the last year simply broke TLS/SSL using dovecot as proxy in front of imap/pop3 * i saw the relase announce * built the RPM * installed it on my testserver * first connection-> segfault that are basics which should not happen in any release of whatever software well, that is why you should have test-setups for them before call yourself sysadmin and you do not need the production load to verify "thats broken" that there maybe other bugs only visible under load is a different story but bugs which are catched with a trivial test should not be in a release so yes, RCs are fine because they prevent a majority of users get hit by a regeression from a random patch solving whatever border case in the CVS which may make only a few people happy and bite most others that is why every serious software is using Beta/RC/Release they give people the chance to make tests *before* the release without need to compile each day the current CVS state signature.asc Description: OpenPGP digital signature
Re: [Dovecot] 2.2.9
On 2013-11-23 19:08, Eugene wrote: Also, I am not sure RCs as such would do much good, since most of the test systems are not likely to reproduce the volume and diversity of production workloads. Perhaps, then, a simple 'click for thumbs up' approach on the web site, to say "I have installed this version and it is working for me." It requires more input from the user base, but for the people who wait to make sure others find the bugs first, it would give confidence that this has happened. Simon. -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
Re: [Dovecot] 2.2.9
Hi all, In recent years I use dovecot installed from FreeBSD ports. Interestingly, I feel that they follow the dovecot releases rather well but with some lag, e.g. currently it is at 2.2.6. I don't know if that is 'by design' or caused by lack of manpower, but it works pretty well in that problems usually get fixed before the update =) (And then again, nobody says you should install a new version on the release day). Also, I am not sure RCs as such would do much good, since most of the test systems are not likely to reproduce the volume and diversity of production workloads. Best wishes Eugene -Original Message- From: Andreas Kasenides Sent: Saturday, November 23, 2013 10:24 PM To: dovecot@dovecot.org Subject: Re: [Dovecot] 2.2.9 On 23-11-2013 19:56, Luuk wrote: On 23-11-2013 18:44, Andreas Kasenides wrote: On 23-11-2013 3:47, Noel Butler wrote: These would be found if Timo reverted back to issuing RC's before any official release, to iron out the niggly off-putting bugs, like most I second this and offer my services for two, three different system What is the difference between a 'RC' and a new version? One should TEST this new version ALWAYS before using it in production (it does not matter if there was a 'RC' before it...) 2 cents ;) RC means exactly what is says Release Client :) NOT a release. So if you get bitten by it then do not come here complaining. Most software go through several RCs before issuing a normal release. Most administrators have test systems that can test RCs for basic functionality and report here of any problems to be fixed. Some though jump into a new release when one is available. An RC should at least show the red flag raised. Andreas
Re: [Dovecot] 2.2.9
On Nov 23, 2013, at 12:24 PM, Andreas Kasenides wrote: > RC means exactly what is says Release Client :) NOT a release. Release Candidate, not Client. A candidate to be the final release unless a late bug is found. -- Larry Stone lston...@stonejongleux.com http://www.stonejongleux.com/ smime.p7s Description: S/MIME cryptographic signature
Re: [Dovecot] 2.2.9
On 23-11-2013 19:56, Luuk wrote: On 23-11-2013 18:44, Andreas Kasenides wrote: On 23-11-2013 3:47, Noel Butler wrote: These would be found if Timo reverted back to issuing RC's before any official release, to iron out the niggly off-putting bugs, like most I second this and offer my services for two, three different system What is the difference between a 'RC' and a new version? One should TEST this new version ALWAYS before using it in production (it does not matter if there was a 'RC' before it...) 2 cents ;) RC means exactly what is says Release Client :) NOT a release. So if you get bitten by it then do not come here complaining. Most software go through several RCs before issuing a normal release. Most administrators have test systems that can test RCs for basic functionality and report here of any problems to be fixed. Some though jump into a new release when one is available. An RC should at least show the red flag raised. Andreas
Re: [Dovecot] 2.2.9
On 23-11-2013 18:44, Andreas Kasenides wrote: On 23-11-2013 3:47, Noel Butler wrote: These would be found if Timo reverted back to issuing RC's before any official release, to iron out the niggly off-putting bugs, like most I second this and offer my services for two, three different system What is the difference between a 'RC' and a new version? One should TEST this new version ALWAYS before using it in production (it does not matter if there was a 'RC' before it...) 2 cents ;)
Re: [Dovecot] 2.2.9
On 23-11-2013 3:47, Noel Butler wrote: On Fri, 2013-11-22 at 10:14 +0100, Ralf Hildebrandt wrote: * Thomas Leuxner : > * Ralf Hildebrandt 2013.11.22 09:44: > > > Which patch? > > http://www.dovecot.org/list/dovecot/2013-November/093654.html > > Pigeonhole related patches. Damn. Those are biting me as well :/ These would be found if Timo reverted back to issuing RC's before any official release, to iron out the niggly off-putting bugs, like most software does, or gets his devs and a community of official testers each with wildly different configurations and set ups, ASF have an excellent model that could be followed, bunch of devs and testers who each report on different distros and configs, why? because no single dev can imagine and test every possible configuration. it might just save dovecot's good name, I recall a lot of damage was done to that in the circles I'm in when 2.0 was released with patches nearly every few days and weeks, I know a few ISP's and businesses that went back to courier or Wu's because major bugs were getting in often, though it has been a lot better since 2.1 series, until this release that is :) I second this and offer my services for two, three different system configs from Dovecot's plain old simple config with MAILDIR to slightly more complicated configurations with proxying/LDAP/dsync/mySQL etc based on virtualization with KVM. I also propose that upon employing above strategy that Timo should come up with a release cycles (long term, short term) with announced targets. Patches should be released as patches strictly as needed, not releases, and should be announced on a low traffic list like he is already doing with releases. OR something along these lines. I know these are growing pains but essential. Email systems are CRITICAL for most of us. Andreas
Re: [Dovecot] 2.2.9
On Sat, Nov 23, 2013 at 01:10:04AM -0700, Eric Broch wrote: > On 11/22/2013 7:06 PM, Timo Sirainen wrote: > > > > (And as for the original question: I’ll make v2.2.9 this weekend. And as > > for bugs, as I already once mentioned, I’m planning on implementing > > significantly more comprehensive testing for Dovecot during the next year.) > > > Thanks for the great software, Timo. I agree. It's very good software, and I appreciate all the hard work you put in, Timo. Simon. -- The Wellcome Trust Sanger Institute is operated by Genome Research Limited, a charity registered in England with number 1021457 and a company registered in England with number 2742969, whose registered office is 215 Euston Road, London, NW1 2BE.
Re: [Dovecot] 2.2.9
On 11/22/2013 7:06 PM, Timo Sirainen wrote: > Everyone replying to this thread really should just shut up. I (and likely > just about nobody else) don’t care who is more wrong or more right or a > better or worse person or whatever, but any mails that have nothing to do > with Dovecot don’t belong to this list. I have no interest in being some kind > of a kindergarten teacher telling people how to behave, but there are about 3 > of you who nowadays constantly seem to be wasting my time on thinking about > it. > > (And as for the original question: I’ll make v2.2.9 this weekend. And as for > bugs, as I already once mentioned, I’m planning on implementing significantly > more comprehensive testing for Dovecot during the next year.) > Thanks for the great software, Timo.
Re: [Dovecot] 2.2.9
Noel, I include you in the gang of three, and I only read half the posts on this list. I have no specific reason to, but it isn't a good association. A decade ago I was active on the Pegasus mail and Mercury lists, and names stood out after a while. Unfortunately on this list, the names stand out for a completely different reason - and its not positive. Just chill, everyone. You never know who's going to interview you in a year. Rick
Re: [Dovecot] 2.2.9
On Sat, 2013-11-23 at 04:06 +0200, Timo Sirainen In-Reply-To: <1385170783.4058.5.camel@tardis> wrote: > but there are about 3 of you who nowadays constantly seem to be wasting my > time on thinking about it. > no doubt, despite my one single post to "them" in long time, but being informed that my name has been dragged into their shit fight a few times, you of course include me in this gang of 3, frankly, I've had a gutfull of your lengthy vendetta, it is after all why I rarely waste my time here and the those I've helped have mostly been via private anyway, now, my time for lists is being more rare these days, I have far more important activities to worry about in life, so it is with much pleasure I inform you that you will need to find some other poor sucker to blame for the trolls and idiots, I am removing myself from the dovecot "community" forthwith, well, in 3 minutes, enough time for this message to make it through mailman before I confirm unsub :) oh before I go, ya know, if you reigned in the regular offenders like other lists, nobody else would have needed to. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] 2.2.9
Thanks for providing and maintaining a great piece of software. Rick
Re: [Dovecot] 2.2.9
Everyone replying to this thread really should just shut up. I (and likely just about nobody else) don’t care who is more wrong or more right or a better or worse person or whatever, but any mails that have nothing to do with Dovecot don’t belong to this list. I have no interest in being some kind of a kindergarten teacher telling people how to behave, but there are about 3 of you who nowadays constantly seem to be wasting my time on thinking about it. (And as for the original question: I’ll make v2.2.9 this weekend. And as for bugs, as I already once mentioned, I’m planning on implementing significantly more comprehensive testing for Dovecot during the next year.)
Re: [Dovecot] 2.2.9
On Fri, 2013-11-22 at 10:14 +0100, Ralf Hildebrandt wrote: > * Thomas Leuxner : > > * Ralf Hildebrandt 2013.11.22 09:44: > > > > > Which patch? > > > > http://www.dovecot.org/list/dovecot/2013-November/093654.html > > > > Pigeonhole related patches. > > Damn. Those are biting me as well :/ > These would be found if Timo reverted back to issuing RC's before any official release, to iron out the niggly off-putting bugs, like most software does, or gets his devs and a community of official testers each with wildly different configurations and set ups, ASF have an excellent model that could be followed, bunch of devs and testers who each report on different distros and configs, why? because no single dev can imagine and test every possible configuration. it might just save dovecot's good name, I recall a lot of damage was done to that in the circles I'm in when 2.0 was released with patches nearly every few days and weeks, I know a few ISP's and businesses that went back to courier or Wu's because major bugs were getting in often, though it has been a lot better since 2.1 series, until this release that is :) <> signature.asc Description: This is a digitally signed message part
Re: [Dovecot] 2.2.9
Am 23.11.2013 02:29, schrieb Benny Pedersen: > Nick Edwards skrev den 2013-11-22 17:17: > >> I need a drink > > if you can find some to drink with, all problems with dovecot will comeback > tomorrow :=) so why are you subscribed here? you permanently attack dovecot itself on the dovecot list > i just made another sieve rule now makes you not smarter, it only shows why i told you to shut up days ago resulting in attacks of Noel and Nick because i am the bad guy would you have quoted fair maybe even Noel would have realized it was deserved because you stripped out quoting your trolling signature.asc Description: OpenPGP digital signature
Re: [Dovecot] 2.2.9
On Sat, 2013-11-23 at 02:29 +0100, Benny Pedersen wrote: > Nick Edwards skrev den 2013-11-22 17:17: > > > I need a drink > > if you can find some to drink with, all problems with dovecot will > comeback tomorrow :=) > > i just made another sieve rule now > > What has this to do with dovecot? Take your trolling off list please. I'm starting to regret defending you against Harald, perhaps its YOU who should be booted and not him Nicks right about one thing though, you seem to have not taken your medicated lately Benny. (although you dont blindly go around abusing people on every list, and in CC's and private, so we wont blacklist you :) ) <> signature.asc Description: This is a digitally signed message part
Re: [Dovecot] 2.2.9
Nick Edwards skrev den 2013-11-22 17:17: I need a drink if you can find some to drink with, all problems with dovecot will comeback tomorrow :=) i just made another sieve rule now
Re: [Dovecot] 2.2.9
Am 22.11.2013 17:17, schrieb Nick Edwards: > what the fuck are you rambling about now? jesus christ, shut the fuck > up and stop popping your dumb comments in when you have no fucking > clue, this has nothing to do with 1 v 2 or some crap that your dumb > arse delusional trolling mouth spills out > > and what the fuck does that have to do with it... christ, go take your > drugs idiot and stop commenting on threads that are obvoiously above > your intelligence grade > > I need a drink if i would post this summary to Benny the hell would freeze over while he has deserved it more than once. i wonder why people come up with blacklists and what else to judge one is allowed to say this, one is not because personal dislikes and whatever instead grow up and take rough answers like a man signature.asc Description: OpenPGP digital signature
Re: [Dovecot] 2.2.9
Am 22.11.2013 17:17, schrieb Nick Edwards: > On 11/22/13, Benny Pedersen wrote: >> Nick Edwards skrev den 2013-11-22 07:20: >>> Timo (since he is the only one that maters here), >> >> so it should have being private mail ? > > No Timo made it clear all dovecot stuff must go by list > >> that sayed i keep dovecot 1.x as the most recent stable version, and 2.x >> as the unstable development version that works for some but not all > > what the fuck are you rambling about now? jesus christ, shut the fuck > up and stop popping your dumb comments in when you have no fucking > clue, this has nothing to do with 1 v 2 or some crap that your dumb > arse delusional trolling mouth spills out ah - now you also woke up why i classified Benny as troll and told him to shut up leading in Noel Butler only see my reponse line quoted and start again his personal fight against me and people like you enter the train with "cool blacklist, i use it too"? well, you most likely will not see this response until someone else quotes it, but more i can not do to make people realize that there is a difference between pure Trolls and people not always nice enough for everybody and his brother signature.asc Description: OpenPGP digital signature
Re: [Dovecot] 2.2.9
On 11/22/13, Benny Pedersen wrote: > Nick Edwards skrev den 2013-11-22 07:20: >> Timo (since he is the only one that maters here), > > so it should have being private mail ? > No Timo made it clear all dovecot stuff must go by list > that sayed i keep dovecot 1.x as the most recent stable version, and 2.x > as the unstable development version that works for some but not all > what the fuck are you rambling about now? jesus christ, shut the fuck up and stop popping your dumb comments in when you have no fucking clue, this has nothing to do with 1 v 2 or some crap that your dumb arse delusional trolling mouth spills out > still have kernel 3.11.6 on gentoo, no problem with that, hmm :=) > and what the fuck does that have to do with it... christ, go take your drugs idiot and stop commenting on threads that are obvoiously above your intelligence grade > living on edge can be fun sometimes I need a drink
Re: [Dovecot] 2.2.9
Reuben Farrelly skrev den 2013-11-22 09:37: its a free world, any one can provide a patch if wanted to fix something, but if it aint broke, dont fix it i have my silly choices, but seems from maillist here its good choices of keep 1.x still, and lucky i have a distro where its posible
Re: [Dovecot] 2.2.9
* Thomas Leuxner : > * Ralf Hildebrandt 2013.11.22 09:44: > > > Which patch? > > http://www.dovecot.org/list/dovecot/2013-November/093654.html > > Pigeonhole related patches. Damn. Those are biting me as well :/ -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebra...@charite.de | http://www.charite.de
Re: [Dovecot] 2.2.9
* Ralf Hildebrandt 2013.11.22 09:44: > Which patch? http://www.dovecot.org/list/dovecot/2013-November/093654.html Pigeonhole related patches. signature.asc Description: Digital signature
