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: Pacaging/build issues with AIX and vac (dovecot-2.2.25)
> On October 10, 2016 at 3:57 AM Michael Felt wrote: > > > On 09-Oct-16 22:51, Aki Tuomi wrote: > >> > >> Michael > > > > Does the compiler support C99 standard? > > > > Aki > > Yes. Plus extended features. Key difference with GCC, e.g., are the > flags to the compiler, but autotools general manages those well. > > Key difference with platform (well, of of) is that it is not GNU, and > how shared libraries are built. Again, libtool in particular, handles > this well. We do already support various non-GNU platforms, but our code does expect C99 conforming compiler these days. We also use autotools and libtool. rpcgen should be available, at least according to http://www.ibm.com/support/knowledgecenter/ssw_aix_61/com.ibm.aix.cmds4/rpcgen.htm Does your build end at some particular point? Aki
Re: Pacaging/build issues with AIX and vac (dovecot-2.2.25)
On 09-Oct-16 22:51, Aki Tuomi wrote: Michael Does the compiler support C99 standard? Aki Yes. Plus extended features. Key difference with GCC, e.g., are the flags to the compiler, but autotools general manages those well. Key difference with platform (well, of of) is that it is not GNU, and how shared libraries are built. Again, libtool in particular, handles this well.
Re: Pacaging/build issues with AIX and vac (dovecot-2.2.25)
On 09.10.2016 22:48, Michael Felt wrote: Hi. I finally decided it was really time to stop being lazy and really move away from gmail. After I have a server in my basement using power, etc. So I turned on the imap provided - and did not quite cry - it will have to do for now, but imap2 is wanting. A real server yes, but not Linux. (Using linux would require another server AND I would feel I am being lazy again). So, I downloaded dovecot-2.2.25 and tried to build. Configure (messages to stderr) xlc is /usr/vacpp/bin/xlc + CPPFLAGS="-I/opt/include -I/opt/buildaix/include" CFLAGS="-I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5 -I/opt/buildaix/includes ./configure\ --prefix=/opt \ --sysconfdir=/var/dovecot/etc\ --sharedstatedir=/var/dovecot/com\ --localstatedir=/var/dovecot\ --mandir=/usr/share/man\ --infodir=/opt/share/info/dovecot \ > .buildaix/configure.out xlc_r: 1501-216 (W) command option -dM is not recognized - passed to ld xlc_r: 1501-228 (W) input file c not found 1506-297 (S) Unable to open input file null. No such file or directory. ./configure[25617]: rpcgen: not found messages to stderr by make: I am quite willing to dig and dig - but I want to be know if there will be any interest and/or support for dovecot on AIX. Sincerely, Michael Does the compiler support C99 standard? Aki
Pacaging/build issues with AIX and vac (dovecot-2.2.25)
Hi. I finally decided it was really time to stop being lazy and really move away from gmail. After I have a server in my basement using power, etc. So I turned on the imap provided - and did not quite cry - it will have to do for now, but imap2 is wanting. A real server yes, but not Linux. (Using linux would require another server AND I would feel I am being lazy again). So, I downloaded dovecot-2.2.25 and tried to build. Configure (messages to stderr) xlc is /usr/vacpp/bin/xlc + CPPFLAGS="-I/opt/include -I/opt/buildaix/include" CFLAGS="-I/opt/include -O2 -qmaxmem=-1 -qarch=pwr5 -I/opt/buildaix/includes ./configure\ --prefix=/opt \ --sysconfdir=/var/dovecot/etc\ --sharedstatedir=/var/dovecot/com\ --localstatedir=/var/dovecot\ --mandir=/usr/share/man\ --infodir=/opt/share/info/dovecot \ > .buildaix/configure.out xlc_r: 1501-216 (W) command option -dM is not recognized - passed to ld xlc_r: 1501-228 (W) input file c not found 1506-297 (S) Unable to open input file null. No such file or directory. ./configure[25617]: rpcgen: not found messages to stderr by make: + make > .buildaix/make.out ./update-version.sh[42]: git: not found. "askpass.c", line 59.18: 1506-359 (I) Automatic variable str contains a const member and is not initialized. It will be initia "guid.c", line 113.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will be initiali "iostream-rawlog.c", line 28.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will b "istream-base64-decoder.c", line 42.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It "istream-base64-encoder.c", line 47.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It "istream-jsonstr.c", line 70.26: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will b "mountpoint.c", line 222.39: 1506-068 (W) Operation between types "char*" and "const char*" is not allowed. "istream-decrypt.c", line 68.18: 1506-359 (I) Automatic variable ephemeral_key contains a const member and is not initialized. "istream-decrypt.c", line 276.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will "istream-decrypt.c", line 369.26: 1506-359 (I) Automatic variable peer_key contains a const member and is not initialized. It "istream-decrypt.c", line 745.42: 1506-359 (I) Automatic variable db contains a const member and is not initialized. It will b "ostream-encrypt.c", line 135.65: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will "ostream-encrypt.c", line 454.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will "dcrypt-openssl.c", line 787.36: 1506-359 (I) Automatic variable key contains a const member and is not initialized. It will b "dcrypt-openssl.c", line 1099.33: 1506-359 (I) Automatic variable secret contains a const member and is not initialized. It wi "dcrypt-openssl.c", line 1295.18: 1506-359 (I) Automatic variable tmp contains a const member and is not initialized. It will "dcrypt-openssl.c", line 1365.18: 1506-359 (I) Automatic variable saltbuf contains a const member and is not initialized. It w "istream-decrypt.c", line 68.18: 1506-359 (I) Automatic variable ephemeral_key contains a const member and is not initialized. "istream-decrypt.c", line 276.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will "istream-decrypt.c", line 369.26: 1506-359 (I) Automatic variable peer_key contains a const member and is not initialized. It "istream-decrypt.c", line 745.42: 1506-359 (I) Automatic variable db contains a const member and is not initialized. It will b "ostream-encrypt.c", line 135.65: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will "ostream-encrypt.c", line 454.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will "istream-decrypt.c", line 68.18: 1506-359 (I) Automatic variable ephemeral_key contains a const member and is not initialized. "istream-decrypt.c", line 276.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will "istream-decrypt.c", line 369.26: 1506-359 (I) Automatic variable peer_key contains a const member and is not initialized. It "istream-decrypt.c", line 745.42: 1506-359 (I) Automatic variable db contains a const member and is not initialized. It will b "ostream-encrypt.c", line 135.65: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will "ostream-encrypt.c", line 454.18: 1506-359 (I) Automatic variable buf contains a const member and is not initialized. It will "te
