Re: Quota-status service on Director
Did you solve this problem of quota status? I am in the same situation right now, i would appreciate you let me know any helpfull information Sent with Aqua Mail for Android https://www.mobisystems.com/aqua-mail
Re: Quota-status service on Director
It is possible it will be supported in future, but for now it's not
supported.
Aki
On 27.09.2017 11:33, Dimos Alevizos wrote:
> Hi,
>
> is quota-status still not supported in proxy configuration ?
> Any chance it will be in the future ?
>
> Dimos
>
> On 10/10/2016 09:06 πμ, Aki Tuomi wrote:
>> Hi!
>>
>> quota-status is not supported in proxy configuration. You should use
>> quota_warning and quota_over_flag scripts instead.
>>
>> Aki
>>
>> On 08.10.2016 03:51, Michael Kliewe wrote:
>>> Hello,
>>> any news on this topic? I tried it again with Dovecot 2.2.25, but it's
>>> still not possible to run the quota-status services on the directors.
>>> They try to access the mailbox of the user, which they obviously
>>> cannot. I'm not sure why Dovecot tries to open the mailbox, I would
>>> have expected just a dict-query (SQL) to check the quota. If the
>>> mailbox has to be opened, it has to be done on the correct backend
>>> Dovecot of the user.
>>> Is there any chance to fix this problem? Or am I doing something wrong
>>> here?
>>> Kind regards
>>> Michael
>>>
>>> Am 23.02.2015 um 03:09 schrieb Michael Kliewe:
Hello,
I'm trying to configure the quota-status service, but it seems I'm
not successful with my director setup (2.2.9). I activate the
quota-status service like this on my director server:
$ cat 91-quota-status.conf
##
## Quota-Status configuration.
##
# Load Module quota-status and listen on TCP/IP Port for connections.
service quota-status {
executable = quota-status -p postfix
inet_listener {
address = 10.0.1.44
port = 12340
}
client_limit = 1
}
# Plugin configuration.
# Return messages for requests by quota status: success, nouser and
overquota.
plugin {
quota_status_success = DUNNO
quota_status_nouser = DUNNO
quota_status_overquota = "552 5.2.2 Mailbox is over quota"
}
After restarting the director service I try to query the quota status
service:
printf "recipient=u...@domain.de\nsize=10\n\n" | nc 10.0.1.44 12340
The output is:
action=DEFER_IF_PERMIT Invalid user settings. Refer to server log for
more information.
In the debug log of the director I see this:
Feb 23 03:03:09 director01 dovecot: auth: Debug: userdb out: USER
1 u...@domain.de
mail=mdbox:/mnt/data01/domain.de/user/maildir
home=/mnt/data01/domain.de/user proxy=Y master=
pass= uid=5000gid=1
quota_rule=*:storage=60593 quota_rule2=*:messages=10
Feb 23 03:03:09 director01 dovecot: quota-status(u...@domain.de):
Error: user u...@domain.de: Initialization failed: Namespace '':
mkdir(/mnt/data01/domain.de/user/maildir/mailboxes) failed:
Permission denied (euid=5000(vmail) egid=1(daemon) missing +w perm:
/mnt, dir owned by 0:0 mode=0755)
So the quota status service tries to access the mailbox of the user
ON THE DIRECTOR. But the director has not mounted the mailboxes of
the users, that's what the backend dovecots are for (proxy=Y). So the
quota-status query is not proxied to the dovecot backend server I
would assume.
Does that mean I have to start the quota-status service on the
dovecot backend servers and access it from the Postfix server
directly? Currently the Postfixes can only reach the directors, not
the backend servers.
Is it possible to use the quota-status service on the director?
Thanks for any hints and help
Michael
>
Re: Quota-status service on Director
Hi,
is quota-status still not supported in proxy configuration ?
Any chance it will be in the future ?
Dimos
On 10/10/2016 09:06 πμ, Aki Tuomi wrote:
> Hi!
>
> quota-status is not supported in proxy configuration. You should use
> quota_warning and quota_over_flag scripts instead.
>
> Aki
>
> On 08.10.2016 03:51, Michael Kliewe wrote:
>> Hello,
>> any news on this topic? I tried it again with Dovecot 2.2.25, but it's
>> still not possible to run the quota-status services on the directors.
>> They try to access the mailbox of the user, which they obviously
>> cannot. I'm not sure why Dovecot tries to open the mailbox, I would
>> have expected just a dict-query (SQL) to check the quota. If the
>> mailbox has to be opened, it has to be done on the correct backend
>> Dovecot of the user.
>> Is there any chance to fix this problem? Or am I doing something wrong
>> here?
>> Kind regards
>> Michael
>>
>> Am 23.02.2015 um 03:09 schrieb Michael Kliewe:
>>> Hello,
>>>
>>> I'm trying to configure the quota-status service, but it seems I'm
>>> not successful with my director setup (2.2.9). I activate the
>>> quota-status service like this on my director server:
>>>
>>> $ cat 91-quota-status.conf
>>> ##
>>> ## Quota-Status configuration.
>>> ##
>>> # Load Module quota-status and listen on TCP/IP Port for connections.
>>> service quota-status {
>>>executable = quota-status -p postfix
>>>inet_listener {
>>> address = 10.0.1.44
>>> port = 12340
>>>}
>>>client_limit = 1
>>> }
>>> # Plugin configuration.
>>> # Return messages for requests by quota status: success, nouser and
>>> overquota.
>>> plugin {
>>>quota_status_success = DUNNO
>>>quota_status_nouser = DUNNO
>>>quota_status_overquota = "552 5.2.2 Mailbox is over quota"
>>> }
>>>
>>> After restarting the director service I try to query the quota status
>>> service:
>>>
>>> printf "recipient=u...@domain.de\nsize=10\n\n" | nc 10.0.1.44 12340
>>>
>>> The output is:
>>>
>>> action=DEFER_IF_PERMIT Invalid user settings. Refer to server log for
>>> more information.
>>>
>>> In the debug log of the director I see this:
>>>
>>> Feb 23 03:03:09 director01 dovecot: auth: Debug: userdb out: USER
>>> 1 u...@domain.de
>>> mail=mdbox:/mnt/data01/domain.de/user/maildir
>>> home=/mnt/data01/domain.de/user proxy=Y master=
>>> pass= uid=5000gid=1
>>> quota_rule=*:storage=60593 quota_rule2=*:messages=10
>>> Feb 23 03:03:09 director01 dovecot: quota-status(u...@domain.de):
>>> Error: user u...@domain.de: Initialization failed: Namespace '':
>>> mkdir(/mnt/data01/domain.de/user/maildir/mailboxes) failed:
>>> Permission denied (euid=5000(vmail) egid=1(daemon) missing +w perm:
>>> /mnt, dir owned by 0:0 mode=0755)
>>>
>>> So the quota status service tries to access the mailbox of the user
>>> ON THE DIRECTOR. But the director has not mounted the mailboxes of
>>> the users, that's what the backend dovecots are for (proxy=Y). So the
>>> quota-status query is not proxied to the dovecot backend server I
>>> would assume.
>>>
>>> Does that mean I have to start the quota-status service on the
>>> dovecot backend servers and access it from the Postfix server
>>> directly? Currently the Postfixes can only reach the directors, not
>>> the backend servers.
>>>
>>> Is it possible to use the quota-status service on the director?
>>>
>>> Thanks for any hints and help
>>> Michael
Re: Quota-status service on Director
Hi!
quota-status is not supported in proxy configuration. You should use
quota_warning and quota_over_flag scripts instead.
Aki
On 08.10.2016 03:51, Michael Kliewe wrote:
> Hello,
> any news on this topic? I tried it again with Dovecot 2.2.25, but it's
> still not possible to run the quota-status services on the directors.
> They try to access the mailbox of the user, which they obviously
> cannot. I'm not sure why Dovecot tries to open the mailbox, I would
> have expected just a dict-query (SQL) to check the quota. If the
> mailbox has to be opened, it has to be done on the correct backend
> Dovecot of the user.
> Is there any chance to fix this problem? Or am I doing something wrong
> here?
> Kind regards
> Michael
>
> Am 23.02.2015 um 03:09 schrieb Michael Kliewe:
>> Hello,
>>
>> I'm trying to configure the quota-status service, but it seems I'm
>> not successful with my director setup (2.2.9). I activate the
>> quota-status service like this on my director server:
>>
>> $ cat 91-quota-status.conf
>> ##
>> ## Quota-Status configuration.
>> ##
>> # Load Module quota-status and listen on TCP/IP Port for connections.
>> service quota-status {
>>executable = quota-status -p postfix
>>inet_listener {
>> address = 10.0.1.44
>> port = 12340
>>}
>>client_limit = 1
>> }
>> # Plugin configuration.
>> # Return messages for requests by quota status: success, nouser and
>> overquota.
>> plugin {
>>quota_status_success = DUNNO
>>quota_status_nouser = DUNNO
>>quota_status_overquota = "552 5.2.2 Mailbox is over quota"
>> }
>>
>> After restarting the director service I try to query the quota status
>> service:
>>
>> printf "recipient=u...@domain.de\nsize=10\n\n" | nc 10.0.1.44 12340
>>
>> The output is:
>>
>> action=DEFER_IF_PERMIT Invalid user settings. Refer to server log for
>> more information.
>>
>> In the debug log of the director I see this:
>>
>> Feb 23 03:03:09 director01 dovecot: auth: Debug: userdb out: USER
>> 1 u...@domain.de
>> mail=mdbox:/mnt/data01/domain.de/user/maildir
>> home=/mnt/data01/domain.de/user proxy=Y master=
>> pass= uid=5000gid=1
>> quota_rule=*:storage=60593 quota_rule2=*:messages=10
>> Feb 23 03:03:09 director01 dovecot: quota-status(u...@domain.de):
>> Error: user u...@domain.de: Initialization failed: Namespace '':
>> mkdir(/mnt/data01/domain.de/user/maildir/mailboxes) failed:
>> Permission denied (euid=5000(vmail) egid=1(daemon) missing +w perm:
>> /mnt, dir owned by 0:0 mode=0755)
>>
>> So the quota status service tries to access the mailbox of the user
>> ON THE DIRECTOR. But the director has not mounted the mailboxes of
>> the users, that's what the backend dovecots are for (proxy=Y). So the
>> quota-status query is not proxied to the dovecot backend server I
>> would assume.
>>
>> Does that mean I have to start the quota-status service on the
>> dovecot backend servers and access it from the Postfix server
>> directly? Currently the Postfixes can only reach the directors, not
>> the backend servers.
>>
>> Is it possible to use the quota-status service on the director?
>>
>> Thanks for any hints and help
>> Michael
Re: Quota-status service on Director
Hello,
any news on this topic? I tried it again with Dovecot 2.2.25, but it's
still not possible to run the quota-status services on the directors.
They try to access the mailbox of the user, which they obviously cannot.
I'm not sure why Dovecot tries to open the mailbox, I would have
expected just a dict-query (SQL) to check the quota. If the mailbox has
to be opened, it has to be done on the correct backend Dovecot of the user.
Is there any chance to fix this problem? Or am I doing something wrong here?
Kind regards
Michael
Am 23.02.2015 um 03:09 schrieb Michael Kliewe:
Hello,
I'm trying to configure the quota-status service, but it seems I'm not
successful with my director setup (2.2.9). I activate the quota-status service
like this on my director server:
$ cat 91-quota-status.conf
##
## Quota-Status configuration.
##
# Load Module quota-status and listen on TCP/IP Port for connections.
service quota-status {
executable = quota-status -p postfix
inet_listener {
address = 10.0.1.44
port = 12340
}
client_limit = 1
}
# Plugin configuration.
# Return messages for requests by quota status: success, nouser and overquota.
plugin {
quota_status_success = DUNNO
quota_status_nouser = DUNNO
quota_status_overquota = "552 5.2.2 Mailbox is over quota"
}
After restarting the director service I try to query the quota status service:
printf "recipient=u...@domain.de\nsize=10\n\n" | nc 10.0.1.44 12340
The output is:
action=DEFER_IF_PERMIT Invalid user settings. Refer to server log for more
information.
In the debug log of the director I see this:
Feb 23 03:03:09 director01 dovecot: auth: Debug: userdb out: USER 1 u...@domain.de
mail=mdbox:/mnt/data01/domain.de/user/maildirhome=/mnt/data01/domain.de/user
proxy=Y master= pass= uid=5000gid=1
quota_rule=*:storage=60593 quota_rule2=*:messages=10
Feb 23 03:03:09 director01 dovecot: quota-status(u...@domain.de): Error: user
u...@domain.de: Initialization failed: Namespace '':
mkdir(/mnt/data01/domain.de/user/maildir/mailboxes) failed: Permission denied
(euid=5000(vmail) egid=1(daemon) missing +w perm: /mnt, dir owned by 0:0
mode=0755)
So the quota status service tries to access the mailbox of the user ON THE
DIRECTOR. But the director has not mounted the mailboxes of the users, that's
what the backend dovecots are for (proxy=Y). So the quota-status query is not
proxied to the dovecot backend server I would assume.
Does that mean I have to start the quota-status service on the dovecot backend
servers and access it from the Postfix server directly? Currently the Postfixes
can only reach the directors, not the backend servers.
Is it possible to use the quota-status service on the director?
Thanks for any hints and help
Michael
RE: quota-status service
> > The way I understand it is, this Quota service was built specifically > for postfix. (I only have postfix, have not used any other MTA) > The "quota-status" executable is in you libexec directory. ( I compiled > my dovecot instance, hence is is not in "regular" directory) Thanks. I also responded to Aki, but to close the loop: evidently quota-status is newer than the version of dovecot on my Ubuntu 12.04 machine. So I'll need to upgrade. > The "quota_status_*" are responses to postifx. AFAIK, these are the only > 3 possible options. > > Please see ( > https://sys4.de/en/blog/2013/04/08/postfix-dovecot-mailbox-quota/ ) for > a detailed info on this > > When Postfix MTA is "inline" with the sender, and if you have correctly > configured the quota service, it will check if the recipient's mailbox > can accept mails. If the recipient is able to accept mail dovecot > responds with "DUNNO" (as configured in "quota_status_success" ) to let > postifx continue with its sender checks. if the recipient's mail box is > unable to accept mails, the dovecot responds with "552 5.2.2 Mailbox is > full" (as configured in "quota_status_overquota"), this will prevent > postfix from accepting mail and will respond with 552 status . All this > is documented in that blog. > Thanks. I saw the link to Hildebrandt's blog on the wiki. (BTW, his Postfix book is still great!) And I understood the example. But it didn't cover the answers to my questions. Aki covered most of them. Thanks again, Michael
Re: quota-status service
Michael,
See my responses inline
On 07/02/2016 06:25 AM, Michael Fox wrote:
???
From: Michael Fox [mailto:n...@mefox.org]
Sent: Thursday, June 30, 2016 1:59 PM
To: Dovecot Mailing List (dovecot@dovecot.org)
Subject: quota-status service
I'm trying to understand the quota-status service, but I can't find complete
documentation.
The quota-status service is mentioned here: http://wiki.dovecot.org/Quota
And an example configuration is shown:
service quota-status {
executable = quota-status -p postfix
inet_listener {
port = 12340
# You can choose any port you want
}
client_limit = 1
}
This is how I have configured it.
But I can't find any information on quota-status.
"man quota-status" returns nothing.
I am unable to find a "quota-status" file on my machine. Where is the
executable located?
What does the "-p postfix" option do?
Are there any other command line options?
The above wiki page shows three quota_status_* options in use:
quota_status_success = DUNNO
quota_status_nouser = DUNNO
quota_status_overquota = "552 5.2.2 Mailbox is full"
The way I understand it is, this Quota service was built specifically
for postfix. (I only have postfix, have not used any other MTA)
The "quota-status" executable is in you libexec directory. ( I compiled
my dovecot instance, hence is is not in "regular" directory)
The "quota_status_*" are responses to postifx. AFAIK, these are the only
3 possible options.
Please see (
https://sys4.de/en/blog/2013/04/08/postfix-dovecot-mailbox-quota/ ) for
a detailed info on this
When Postfix MTA is "inline" with the sender, and if you have correctly
configured the quota service, it will check if the recipient's mailbox
can accept mails. If the recipient is able to accept mail dovecot
responds with "DUNNO" (as configured in "quota_status_success" ) to let
postifx continue with its sender checks. if the recipient's mail box is
unable to accept mails, the dovecot responds with "552 5.2.2 Mailbox is
full" (as configured in "quota_status_overquota"), this will prevent
postfix from accepting mail and will respond with 552 status . All this
is documented in that blog.
Please also see: http://www.postfix.org/SMTPD_ACCESS_README.html
Where are their meanings documented?
What are the allowed values?
Are there other quota_status_* options?
Thanks in advance.
Thanks,
Michael
Hope this was helpful
-Thanks
Vijay
RE: quota-status service
???
From: Michael Fox [mailto:n...@mefox.org]
Sent: Thursday, June 30, 2016 1:59 PM
To: Dovecot Mailing List (dovecot@dovecot.org)
Subject: quota-status service
I'm trying to understand the quota-status service, but I can't find complete
documentation.
The quota-status service is mentioned here: http://wiki.dovecot.org/Quota
And an example configuration is shown:
service quota-status {
executable = quota-status -p postfix
inet_listener {
port = 12340
# You can choose any port you want
}
client_limit = 1
}
But I can't find any information on quota-status.
"man quota-status" returns nothing.
I am unable to find a "quota-status" file on my machine. Where is the
executable located?
What does the "-p postfix" option do?
Are there any other command line options?
The above wiki page shows three quota_status_* options in use:
quota_status_success = DUNNO
quota_status_nouser = DUNNO
quota_status_overquota = "552 5.2.2 Mailbox is full"
Where are their meanings documented?
What are the allowed values?
Are there other quota_status_* options?
Thanks in advance.
Thanks,
Michael
