[Dovecot] v2.1.16 released
http://dovecot.org/releases/2.1/dovecot-2.1.16.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.16.tar.gz.sig
+ Added quota-status policy service for Postfix
+ Added "doveadm batch" command to run multiple commands before moving
onto the next user (useful only with -A and -u <usermask>)
+ Added forwards compatibility for v2.2 index files
- mdbox: Index rebuilding crashed in some situations
- Fixed a race condition with setting \Recent flags
- Fixed a crash when decoding a specific message (decoding is done
for SEARCH TEXT/BODY and with full text search indexing, so this
couldn't fully DoS a user)Timo Sirainen skrev den 2013-04-04 23:16:
- Added quota-status policy service for Postfix
so now postfix can use dovecot as a qouta policy daemon ? (via check_policy_service)
if so super duper, but i still keep dovecot 1.x for now, will have to redo another server to go with dovecot 2.x, hopefully it will be my first mac mini server not running in an f16 with afterburner :)
On Friday, April 5, 2013 at 5:16 AM, Timo Sirainen wrote:
- Added quota-status policy service for Postfix
Found quota-status related settings in Dovecot-2.2 commit log here: http://hg.dovecot.org/dovecot-2.2/rev/980be1dc80c2
Zhang Huangbin <zhbmaillistonly@gmail.com> wrote:
On Friday, April 5, 2013 at 5:16 AM, Timo Sirainen wrote:
- Added quota-status policy service for Postfix
Found quota-status related settings in Dovecot-2.2 commit log here: http://hg.dovecot.org/dovecot-2.2/rev/980be1dc80c2
yes, great work!
Apr 05 11:26:20 master: Info: Dovecot v2.1.16 starting up (core dumps disabled)
Had to recompile dovecot-2.1-pigeonhole-0.3.1. Everything is fine now.
Andreas
Zhang Huangbin skrev den 2013-04-05 11:00:
On Friday, April 5, 2013 at 5:16 AM, Timo Sirainen wrote:
- Added quota-status policy service for Postfix Found quota-status related settings in Dovecot-2.2 commit log here: http://hg.dovecot.org/dovecot-2.2/rev/980be1dc80c2
neat, it could be done with dovecot qouta dict, and then let postfix sql/ldap query it, but the above is more strong solotion
Hi,
On Friday 05 April 2013 00:16:17 Timo Sirainen wrote:
- Added "doveadm batch" command to run multiple commands before moving onto the next user (useful only with -A and -u <usermask>)
As I understand this new command, it permits to run several doveadm commands in one shot?
If this is correct, could you provide an example showing how to execute those two commands at the same time:
- doveadm quota get -A
- doveadm mailbox status -A -t all '*'
Thanks.
Regards, Gilles.
On Fri, 2013-04-05 at 12:06 +0200, Gilles CHAUVIN wrote:
Hi,
On Friday 05 April 2013 00:16:17 Timo Sirainen wrote:
- Added "doveadm batch" command to run multiple commands before moving onto the next user (useful only with -A and -u <usermask>)
As I understand this new command, it permits to run several doveadm commands in one shot?
If this is correct, could you provide an example showing how to execute those two commands at the same time:
- doveadm quota get -A
- doveadm mailbox status -A -t all '*'
doveadm batch -A : quota get : mailbox status -t all '*'
Except looks like subcommand parameters don't work. Fixed: http://hg.dovecot.org/dovecot-2.2/rev/2918bfacf565
Also those commands crash now because it tries to use "table" formatter.. Giving doveadm -f tab for example fixes the crash. Anyway, it's not really meant for those types of commands, most importantly the idea was to run:
doveadm batch -A : altmove savedbefore 1w : purge
And maybe some expunge commands to delete old mails from Trash/Spam.
On Friday 05 April 2013 14:08:30 Timo Sirainen wrote:
doveadm batch -A : quota get : mailbox status -t all '*'
Except looks like subcommand parameters don't work. Fixed: http://hg.dovecot.org/dovecot-2.2/rev/2918bfacf565
Also those commands crash now because it tries to use "table" formatter.. Giving doveadm -f tab for example fixes the crash. Anyway, it's not really meant for those types of commands, most importantly the idea was to run:
doveadm batch -A : altmove savedbefore 1w : purge
And maybe some expunge commands to delete old mails from Trash/Spam.
Hi Timo,
In fact, I need to run those 2 commands from a Python script once a day (to gather data and make some stats about our mailstore usage).
We are slowly migrating from an old cyrus server and currently, with only ~7500 users, running these commands takes a while. At the end of the migration we'll have ~34000 users using the mailstore... I fear gathering these infos will take a very long time ;).
BTW, thanks for your reply and for the fix ;).
Gilles.
On 5.4.2013, at 14.30, Gilles CHAUVIN <gilles.chauvin@univ-rouen.fr> wrote:
On Friday 05 April 2013 14:08:30 Timo Sirainen wrote:
doveadm batch -A : quota get : mailbox status -t all '*'
Hi Timo,
In fact, I need to run those 2 commands from a Python script once a day (to gather data and make some stats about our mailstore usage).
We are slowly migrating from an old cyrus server and currently, with only ~7500 users, running these commands takes a while. At the end of the migration we'll have ~34000 users using the mailstore... I fear gathering these infos will take a very long time ;).
Try with mailbox_list_index=yes. It should make the status command faster. And if you're using Maildir, set maildir_very_dirty_syncs=yes.
On Friday 05 April 2013 14:36:18 Timo Sirainen wrote:
Try with mailbox_list_index=yes. It should make the status command faster. And if you're using Maildir, set maildir_very_dirty_syncs=yes.
We're using mdbox so I tried mailbox_list_index = yes (wasn't aware of this command) and once activated got a huge amount of these in the logs :-/
2013-04-05T13:54:55.505235+02:00 host dovecot: imap(xxxxxx): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x4636a) [0x7f2dfaab936a] -
/usr/local/lib/dovecot/libdovecot.s o.0(+0x463b6) [0x7f2dfaab93b6] -> /usr/local/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f2dfaa8cc0f] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0xbc3e0) [0x7f2dfadc13e0] -> /usr/loca l/lib/dovecot/libdovecot-storage.so.0(mail_index_sync_begin_to+0x4f) [0x7f2dfadc145f] -> /usr/local/lib/dovecot/libdovecot- storage.so.0(mail_index_sync_begin+0x1e) [0x7f2dfadc14de] -> /usr/l ocal/lib/dovecot/libdovecot-storage.so.0(mailbox_list_index_sync+0xd4) [0x7f2dfad920e4] -> /usr/local/lib/dovecot/libdovecot- storage.so.0(mailbox_list_index_refresh+0x9a) [0x7f2dfad90a7a] -> /usr/local/lib/dovecot/libdovecot- storage.so.0(mailbox_list_index_iter_init+0xf6) [0x7f2dfad90f96] -> /usr/local/lib/dovecot/libdovecot- storage.so.0(mailbox_list_iter_init_multiple+0xf3) [0 x7f2dfad884f3] -> /usr/local/lib/dovecot/libdovecot- storage.so.0(mailbox_list_iter_init+0x19) [0x7f2dfad88c39] -> /usr/local/lib/dovecot/lib01_acl_plugin.so(+0xbd24) [0x7f2df850fd24] -> /usr /local/lib/dovecot/lib01_acl_plugin.so(+0xc65a) [0x7f2df851065a] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_list_index_sync+0x1cd) [0x7f2dfad921dd] -> /usr/local/lib/dovecot/l ibdovecot-storage.so.0(mailbox_list_index_refresh+0x9a) [0x7f2dfad90a7a] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(+0x8c32b) [0x7f2dfad9132b] -> /usr/local/lib/dovecot/libdovecot-sto rage.so.0(+0x8c960) [0x7f2dfad91960] -> /usr/local/lib/dovecot/libdovecot- storage.so.0(mailbox_sync_deinit+0x2a) [0x7f2dfad7fc6a] -> /usr/local/lib/dovecot/libdovecot-storage.so.0(mailbox_sy nc+0x3b) [0x7f2dfad7fd2b] -> dovecot/imap [xxxxxx 10.193.97.50 SELECT] (cmd_select_full+0x16e) [0x40d4fe] -> dovecot/imap xxxxxx 10.193.97.50 SELECT [0x41150d] -> dovec ot/imap xxxxxx 10.193.97.50 SELECT [0x41045e] -> dovecot/imap xxxxxx 10.193.97.50 SELECT [0x41053d] -> dovecot/imap [xxxxxx 10.193.97.50 SELECT] (client_handl
Dovecot was upgraded to v2.1.16 this morning.
Gilles
On 5.4.2013, at 15.01, Gilles CHAUVIN <gilles.chauvin@univ-rouen.fr> wrote:
On Friday 05 April 2013 14:36:18 Timo Sirainen wrote:
Try with mailbox_list_index=yes. It should make the status command faster. And if you're using Maildir, set maildir_very_dirty_syncs=yes.
We're using mdbox so I tried mailbox_list_index = yes (wasn't aware of this command) and once activated got a huge amount of these in the logs :-/
2013-04-05T13:54:55.505235+02:00 host dovecot: imap(xxxxxx): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x4636a) [0x7f2dfaab936a] -> /usr/local/lib/dovecot/libdovecot.s
You're missing the error message before this one, that actually shows where it crashed. Anyway, I was somehow thinking you were using v2.2. mailbox_list_index=yes is somewhat buggy in v2.1, but should work great in v2.2.
On Friday 05 April 2013 15:03:19 Timo Sirainen wrote:
On 5.4.2013, at 15.01, Gilles CHAUVIN <gilles.chauvin@univ-rouen.fr> wrote:
On Friday 05 April 2013 14:36:18 Timo Sirainen wrote:
Try with mailbox_list_index=yes. It should make the status command faster. And if you're using Maildir, set maildir_very_dirty_syncs=yes.
We're using mdbox so I tried mailbox_list_index = yes (wasn't aware of this command) and once activated got a huge amount of these in the logs :-/
2013-04-05T13:54:55.505235+02:00 host dovecot: imap(xxxxxx): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x4636a) [0x7f2dfaab936a] -> /usr/local/lib/dovecot/libdovecot.s You're missing the error message before this one, that actually shows where it crashed. Anyway, I was somehow thinking you were using v2.2. mailbox_list_index=yes is somewhat buggy in v2.1, but should work great in v2.2.
Oops... The 2 lines before says:
2013-04-05T13:54:55.503668+02:00 host dovecot: master: Error: service(imap): child 3825 killed with signal 6 (core dumps disabled) 2013-04-05T13:54:55.504496+02:00 host dovecot: imap(xxxxxx): Panic: file mail- index-sync.c: line 440 (mail_index_sync_begin_to2): assertion failed: (!index-
syncing)
Gilles
On 5.4.2013, at 15.07, Gilles CHAUVIN <gilles.chauvin@univ-rouen.fr> wrote:
You're missing the error message before this one, that actually shows where it crashed. Anyway, I was somehow thinking you were using v2.2. mailbox_list_index=yes is somewhat buggy in v2.1, but should work great in v2.2.
Oops... The 2 lines before says:
2013-04-05T13:54:55.503668+02:00 host dovecot: master: Error: service(imap): child 3825 killed with signal 6 (core dumps disabled) 2013-04-05T13:54:55.504496+02:00 host dovecot: imap(xxxxxx): Panic: file mail-index-sync.c: line 440 (mail_index_sync_begin_to2): assertion failed: (!index->syncing)
Probably too much trouble to fix this in v2.1. v2.2 should have it working though.
Also, with 2.1.16 the metadata plugin by Dennis Schridde now compiles just fine without any modification to Dovecot or the plugin itself. I've updated my documentation on compiling and installing it to reflect these changes. Thanks for adding that small patch Timo I appreciate it. This will give me something to toy with while the native metadata support is hashed out.
Plugin : http://hg.dovecot.org/dovecot-metadata-plugin My install notes (Still partly unfinished) : http://bmts.us/wiki/doku.php?id=article:kolab:dovecot
On Thursday, April 4, 2013 04:16 PM CDT, Timo Sirainen <tss@iki.fi> wrote:
http://dovecot.org/releases/2.1/dovecot-2.1.16.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.16.tar.gz.sig
- Added quota-status policy service for Postfix
- Added "doveadm batch" command to run multiple commands before moving onto the next user (useful only with -A and -u <usermask>)
- Added forwards compatibility for v2.2 index files
- mdbox: Index rebuilding crashed in some situations
- Fixed a race condition with setting \Recent flags
- Fixed a crash when decoding a specific message (decoding is done for SEARCH TEXT/BODY and with full text search indexing, so this couldn't fully DoS a user)
Hello!
Timo Sirainen <tss@iki.fi> wrote:
http://dovecot.org/releases/2.1/dovecot-2.1.16.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.16.tar.gz.sig
- Added quota-status policy service for Postfix
Got a problem with the quota-status. I added it using the howto from Ralf Hildebrand at http://sys4.de/de/blog/2013/04/05/dovecot-quota-mit-postfix-abfragen/
# netstat -pantu |grep 12340 tcp 0 0 127.0.0.1:12340 0.0.0.0:* LISTEN 19666/dovecot
plugin { quota = maildir:User quota quota_grace = 10%% quota_rule = *:storage=500MB quota_rule2 = Trash:storage=+10%%
quota_status_success = DUNNO
quota_status_nouser = DUNNO
quota_status_overquota = 552 5.2.2 Mailbox is full / Mailbox ist voll
autocreate = Trash
autocreate2 = Drafts
autocreate3 = Sent
autosubscribe = Trash
autosubscribe2 = Drafts
autosubscribe3 = Sent}
service quota-status { executable = quota-status -p postfix inet_listener { port = 12340 } client_limit = 1 }
and in der main.cf of postfix warn_if_reject check_policy_service inet:127.0.0.1:12340
I get this in the logfile of postfix: Apr 7 15:52:51 delta postfix/smtpd[19988]: warning: access table inet:127.0.0.1:12340 entry has empty value
What's wrong? Postfis does not seem to get the quota-status from dovecot.
Andreas
Am 07.04.2013 16:07, schrieb Andreas Meyer:
Hello!
Timo Sirainen <tss@iki.fi> wrote:
http://dovecot.org/releases/2.1/dovecot-2.1.16.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.16.tar.gz.sig
- Added quota-status policy service for Postfix
Got a problem with the quota-status. I added it using the howto from Ralf Hildebrand at http://sys4.de/de/blog/2013/04/05/dovecot-quota-mit-postfix-abfragen/
# netstat -pantu |grep 12340 tcp 0 0 127.0.0.1:12340 0.0.0.0:* LISTEN 19666/dovecot
plugin { quota = maildir:User quota quota_grace = 10%% quota_rule = *:storage=500MB quota_rule2 = Trash:storage=+10%%
quota_status_success = DUNNO quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full / Mailbox ist voll autocreate = Trash autocreate2 = Drafts autocreate3 = Sent autosubscribe = Trash autosubscribe2 = Drafts autosubscribe3 = Sent}
service quota-status { executable = quota-status -p postfix inet_listener { port = 12340 } client_limit = 1 }
and in der main.cf of postfix warn_if_reject check_policy_service inet:127.0.0.1:12340
I get this in the logfile of postfix: Apr 7 15:52:51 delta postfix/smtpd[19988]: warning: access table inet:127.0.0.1:12340 entry has empty value
What's wrong? Postfis does not seem to get the quota-status from dovecot.
Andreas
not sure what this means and in hurry ,but i.e try alternate setup
service quota-status { executable = quota-status -p postfix unix_listener /var/spool/postfix/private/quota-status { group = postfix mode = 0660 user = postfix } client_limit = 1 }
smtpd_recipient_restrictions = reject_non_fqdn_recipient, reject_unknown_recipient_domain, permit_mynetworks, ... reject_unauth_destination, check_policy_service unix:private/quota-status
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, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Joerg Heidrich
Robert Schetterer <rs@sys4.de> wrote:
Am 07.04.2013 16:07, schrieb Andreas Meyer:
Hello!
Timo Sirainen <tss@iki.fi> wrote:
http://dovecot.org/releases/2.1/dovecot-2.1.16.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.16.tar.gz.sig
- Added quota-status policy service for Postfix
Got a problem with the quota-status. I added it using the howto from Ralf Hildebrand at http://sys4.de/de/blog/2013/04/05/dovecot-quota-mit-postfix-abfragen/
# netstat -pantu |grep 12340 tcp 0 0 127.0.0.1:12340 0.0.0.0:* LISTEN 19666/dovecot
plugin { quota = maildir:User quota quota_grace = 10%% quota_rule = *:storage=500MB quota_rule2 = Trash:storage=+10%%
quota_status_success = DUNNO quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full / Mailbox ist voll autocreate = Trash autocreate2 = Drafts autocreate3 = Sent autosubscribe = Trash autosubscribe2 = Drafts autosubscribe3 = Sent}
service quota-status { executable = quota-status -p postfix inet_listener { port = 12340 } client_limit = 1 }
and in der main.cf of postfix warn_if_reject check_policy_service inet:127.0.0.1:12340
I get this in the logfile of postfix: Apr 7 15:52:51 delta postfix/smtpd[19988]: warning: access table inet:127.0.0.1:12340 entry has empty value
What's wrong? Postfis does not seem to get the quota-status from dovecot.
Andreas
not sure what this means and in hurry ,but i.e try alternate setup
service quota-status { executable = quota-status -p postfix unix_listener /var/spool/postfix/private/quota-status { group = postfix mode = 0660 user = postfix } client_limit = 1 }
smtpd_recipient_restrictions = reject_non_fqdn_recipient, reject_unknown_recipient_domain, permit_mynetworks, ... reject_unauth_destination, check_policy_service unix:private/quota-status
Tried that already with the same behaviour. Postfix does not get the quota-status.
Andreas
Am 07.04.2013 17:28, schrieb Andreas Meyer:
Robert Schetterer <rs@sys4.de> wrote:
Am 07.04.2013 16:07, schrieb Andreas Meyer:
Hello!
Timo Sirainen <tss@iki.fi> wrote:
http://dovecot.org/releases/2.1/dovecot-2.1.16.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.16.tar.gz.sig
- Added quota-status policy service for Postfix
Got a problem with the quota-status. I added it using the howto from Ralf Hildebrand at http://sys4.de/de/blog/2013/04/05/dovecot-quota-mit-postfix-abfragen/
# netstat -pantu |grep 12340 tcp 0 0 127.0.0.1:12340 0.0.0.0:* LISTEN 19666/dovecot
plugin { quota = maildir:User quota quota_grace = 10%% quota_rule = *:storage=500MB quota_rule2 = Trash:storage=+10%%
quota_status_success = DUNNO quota_status_nouser = DUNNO quota_status_overquota = 552 5.2.2 Mailbox is full / Mailbox ist voll autocreate = Trash autocreate2 = Drafts autocreate3 = Sent autosubscribe = Trash autosubscribe2 = Drafts autosubscribe3 = Sent}
service quota-status { executable = quota-status -p postfix inet_listener { port = 12340 } client_limit = 1 }
and in der main.cf of postfix warn_if_reject check_policy_service inet:127.0.0.1:12340
I get this in the logfile of postfix: Apr 7 15:52:51 delta postfix/smtpd[19988]: warning: access table inet:127.0.0.1:12340 entry has empty value
What's wrong? Postfis does not seem to get the quota-status from dovecot.
Andreas
not sure what this means and in hurry ,but i.e try alternate setup
service quota-status { executable = quota-status -p postfix unix_listener /var/spool/postfix/private/quota-status { group = postfix mode = 0660 user = postfix } client_limit = 1 }
smtpd_recipient_restrictions = reject_non_fqdn_recipient, reject_unknown_recipient_domain, permit_mynetworks, ... reject_unauth_destination, check_policy_service unix:private/quota-status
Tried that already with the same behaviour. Postfix does not get the quota-status.
Andreas
Hi Andreas, i should clean up my eyes the dovecot policy daemon code really is in 2.1.16 but there is no quota_grace Parameter, without this service make small sense i.e if you allready have lmtp quota enabled, cause mostly this will bounce mail before the mailbox gets overquota in real
if you want to test dove quota feature it only make sense if using dove 2.2 ( as written in the blog by Ralf)
speculation , i dont think that Timo will backport quota_grace to 2.1
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, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Joerg Heidrich
Robert Schetterer <rs@sys4.de> wrote:
not sure what this means and in hurry ,but i.e try alternate setup
service quota-status { executable = quota-status -p postfix unix_listener /var/spool/postfix/private/quota-status { group = postfix mode = 0660 user = postfix } client_limit = 1 }
smtpd_recipient_restrictions = reject_non_fqdn_recipient, reject_unknown_recipient_domain, permit_mynetworks, ... reject_unauth_destination, check_policy_service unix:private/quota-status
Tried that already with the same behaviour. Postfix does not get the quota-status.
Hi Andreas, i should clean up my eyes the dovecot policy daemon code really is in 2.1.16 but there is no quota_grace Parameter, without this service make small sense i.e if you allready have lmtp quota enabled, cause mostly this will bounce mail before the mailbox gets overquota in real
Didn't know the thing with the quota_grace. Yes, I use dovecot-lda as transport from postfix. So postfix hands over the mail to the virtual_transport = dovecot and the check with the inet_listener isn't done then? B) I guess dovecot-lda should report the quota-status and do the check.
if you want to test dove quota feature it only make sense if using dove 2.2 ( as written in the blog by Ralf)
I testet this in a productive environment. If I get the time I'll setup a testmachine for 2.2
speculation , i dont think that Timo will backport quota_grace to 2.1
Best Regards MfG Robert Schetterer
Greetings
Andreas
On 7.4.2013, at 17.07, Andreas Meyer <anmeyer@anup.de> wrote:
Got a problem with the quota-status. I added it using the howto from Ralf Hildebrand at http://sys4.de/de/blog/2013/04/05/dovecot-quota-mit-postfix-abfragen/ .. I get this in the logfile of postfix: Apr 7 15:52:51 delta postfix/smtpd[19988]: warning: access table inet:127.0.0.1:12340 entry has empty value
I wonder if that really means that it's getting an empty value or if it's something else. I don't know why it would be getting an empty value. Do you see an anything in Dovecot's error log?
I know there's a bug in 2.1.16 where it crashes if you try to ask quota status for a nonexistent user.. http://hg.dovecot.org/dovecot-2.1/rev/c6b4a639cae1 fixes that.
Hello!
Timo Sirainen <tss@iki.fi> wrote:
On 7.4.2013, at 17.07, Andreas Meyer <anmeyer@anup.de> wrote:
Got a problem with the quota-status. I added it using the howto from Ralf Hildebrand at http://sys4.de/de/blog/2013/04/05/dovecot-quota-mit-postfix-abfragen/ .. I get this in the logfile of postfix: Apr 7 15:52:51 delta postfix/smtpd[19988]: warning: access table inet:127.0.0.1:12340 entry has empty value
I wonder if that really means that it's getting an empty value or if it's something else. I don't know why it would be getting an empty value. Do you see an anything in Dovecot's error log?
Apr 7 19:55:53 delta postfix/smtpd[23362]: connect from dovecot.org[193.210.130.67] Apr 7 19:55:53 delta postfix/smtpd[23362]: warning: access table inet:127.0.0.1:12340 entry has empty value Apr 7 19:55:53 delta postfix/smtpd[23362]: NOQUEUE: client=dovecot.org[193.210.130.67] Apr 7 19:55:54 delta postfix/smtpd[23234]: 727161B31260: client=localhost[127.0.0.1] Apr 7 19:55:54 delta postfix/cleanup[23369]: 727161B31260: message-id=<F5021A00-0B9B-4D1F-8B1A-A133119488E8@iki.fi> Apr 7 19:55:54 delta postfix/smtpd[23234]: disconnect from localhost[127.0.0.1] Apr 7 19:55:54 delta postfix/qmgr[22234]: 727161B31260: from=<dovecot-bounces@dovecot.org>, size=2764, nrcpt=1 (queue active) Apr 7 19:55:54 delta postfix/smtpd[23362]: disconnect from dovecot.org[193.210.130.67] Apr 7 19:55:54 delta postfix/pipe[23370]: 727161B31260: to=<anmeyer@anup.de>, relay=dovecot, delay=0.24, delays=0.07/0/0/0.17, dsn=2.0.0, status=sent (delivered via dovecot service) Apr 7 19:55:54 delta postfix/qmgr[22234]: 727161B31260: removed
I know there's a bug in 2.1.16 where it crashes if you try to ask quota status for a nonexistent user.. http://hg.dovecot.org/dovecot-2.1/rev/c6b4a639cae1 fixes that.
The user exists. This is what I find in the dovecot-lda-errors.log
Apr 07 19:48:13 lda(miles@anup.de): Error: sieve: msgid=<20130407193818.62d8c328@itxnew.bitcorner.intern>: failed to store into mailbox 'INBOX': Quota exceeded (mailbox for user is full) Apr 07 19:48:13 lda(miles@anup.de): Error: sieve: script /var/spool/vhosts/anup.de/miles/.dovecot.sieve failed with unsuccessful implicit keep (user logfile /var/spool/vhosts/anup.de/miles/.dov ecot.sieve.log may reveal additional details)
Nothing special in the dovecot.log Apr 07 19:47:15 imap-login: Info: Login: user=<miles@anup.de>, method=CRAM-MD5, rip=84.179.43.201, lip=213.239.207.165, mpid=23264, session=<X4kr6cjZcgBUsyvJ>
Andreas
Am 07.04.2013 19:58, schrieb Andreas Meyer:
Hello!
Timo Sirainen <tss@iki.fi> wrote:
On 7.4.2013, at 17.07, Andreas Meyer <anmeyer@anup.de> wrote:
Got a problem with the quota-status. I added it using the howto from Ralf Hildebrand at http://sys4.de/de/blog/2013/04/05/dovecot-quota-mit-postfix-abfragen/ .. I get this in the logfile of postfix: Apr 7 15:52:51 delta postfix/smtpd[19988]: warning: access table inet:127.0.0.1:12340 entry has empty value
I wonder if that really means that it's getting an empty value or if it's something else. I don't know why it would be getting an empty value. Do you see an anything in Dovecot's error log?
Apr 7 19:55:53 delta postfix/smtpd[23362]: connect from dovecot.org[193.210.130.67] Apr 7 19:55:53 delta postfix/smtpd[23362]: warning: access table inet:127.0.0.1:12340 entry has empty value Apr 7 19:55:53 delta postfix/smtpd[23362]: NOQUEUE: client=dovecot.org[193.210.130.67] Apr 7 19:55:54 delta postfix/smtpd[23234]: 727161B31260: client=localhost[127.0.0.1] Apr 7 19:55:54 delta postfix/cleanup[23369]: 727161B31260: message-id=<F5021A00-0B9B-4D1F-8B1A-A133119488E8@iki.fi> Apr 7 19:55:54 delta postfix/smtpd[23234]: disconnect from localhost[127.0.0.1] Apr 7 19:55:54 delta postfix/qmgr[22234]: 727161B31260: from=<dovecot-bounces@dovecot.org>, size=2764, nrcpt=1 (queue active) Apr 7 19:55:54 delta postfix/smtpd[23362]: disconnect from dovecot.org[193.210.130.67] Apr 7 19:55:54 delta postfix/pipe[23370]: 727161B31260: to=<anmeyer@anup.de>, relay=dovecot, delay=0.24, delays=0.07/0/0/0.17, dsn=2.0.0, status=sent (delivered via dovecot service) Apr 7 19:55:54 delta postfix/qmgr[22234]: 727161B31260: removed
I know there's a bug in 2.1.16 where it crashes if you try to ask quota status for a nonexistent user.. http://hg.dovecot.org/dovecot-2.1/rev/c6b4a639cae1 fixes that.
The user exists. This is what I find in the dovecot-lda-errors.log
Apr 07 19:48:13 lda(miles@anup.de): Error: sieve: msgid=<20130407193818.62d8c328@itxnew.bitcorner.intern>: failed to store into mailbox 'INBOX': Quota exceeded (mailbox for user is full) Apr 07 19:48:13 lda(miles@anup.de): Error: sieve: script /var/spool/vhosts/anup.de/miles/.dovecot.sieve failed with unsuccessful implicit keep (user logfile /var/spool/vhosts/anup.de/miles/.dov ecot.sieve.log may reveal additional details)
as i wrote, without quota_grace , which not exist in 2.1.16 lda or lmtp will bounce by overquota mailbox, so you mostly never reach a level where the quota policy server is needed however the existing policy code should work ( it did with my last small tests 2.1.15...), but for real testing you need upgrade 2.2
Nothing special in the dovecot.log Apr 07 19:47:15 imap-login: Info: Login: user=<miles@anup.de>, method=CRAM-MD5, rip=84.179.43.201, lip=213.239.207.165, mpid=23264, session=<X4kr6cjZcgBUsyvJ>
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, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Joerg Heidrich
On 7.4.2013, at 20.58, Andreas Meyer <anmeyer@anup.de> wrote:
Apr 7 15:52:51 delta postfix/smtpd[19988]: warning: access table inet:127.0.0.1:12340 entry has empty value
I wonder if that really means that it's getting an empty value or if it's something else. I don't know why it would be getting an empty value. Do you see an anything in Dovecot's error log?
Apr 7 19:55:53 delta postfix/smtpd[23362]: connect from dovecot.org[193.210.130.67] Apr 7 19:55:53 delta postfix/smtpd[23362]: warning: access table inet:127.0.0.1:12340 entry has empty value
Oh, notice the two spaces there between "entry has"? It's looking up an empty key (instead of email@address), so it's getting back an empty value. Although Dovecot's reply should still be DUNNO then. Anyway, looks to me like Postfix config isn't correct somehow.
Timo Sirainen <tss@iki.fi> wrote:
On 7.4.2013, at 20.58, Andreas Meyer <anmeyer@anup.de> wrote:
Apr 7 15:52:51 delta postfix/smtpd[19988]: warning: access table inet:127.0.0.1:12340 entry has empty value
I wonder if that really means that it's getting an empty value or if it's something else. I don't know why it would be getting an empty value. Do you see an anything in Dovecot's error log?
Apr 7 19:55:53 delta postfix/smtpd[23362]: connect from dovecot.org[193.210.130.67] Apr 7 19:55:53 delta postfix/smtpd[23362]: warning: access table inet:127.0.0.1:12340 entry has empty value
Oh, notice the two spaces there between "entry has"? It's looking up an empty key (instead of email@address), so it's getting back an empty value. Although Dovecot's reply should still be DUNNO then. Anyway, looks to me like Postfix config isn't correct somehow.
Yes I saw the space between "entry has". ;). And yes, like posted in my other email, I set the check for the inet_listener to the beginning of the recipient_restrictions in Postfix and the thing worked and the MTA refused to take the mail over.
But thereby got the problem not beeing able to send any email to the mailserver. Don't know why at the moment. Something is wrong with the order of the checks in postfix.
Andreas
participants (7)
-
Andreas Meyer
-
Benny Pedersen
-
Bruce Marriner
-
Gilles CHAUVIN
-
Robert Schetterer
-
Timo Sirainen
-
Zhang Huangbin