On Wed, 2011-06-01 at 16:59 -0700, Kelsey Cummings wrote:
On Thu, Dec 30, 2010 at 01:52:53PM +0200, Timo Sirainen wrote:
On Tue, 2010-12-21 at 14:55 -0500, David Warden wrote:
But when I try to get my quota on a different local IP using the -S flag
to doveadm:
doveadm quota get
On Thu, Dec 30, 2010 at 01:52:53PM +0200, Timo Sirainen wrote:
On Tue, 2010-12-21 at 14:55 -0500, David Warden wrote:
But when I try to get my quota on a different local IP using the -S flag to
doveadm:
doveadm quota get -u warden -S 137.238.2.244:143
The purpose of -S is
On Tue, 2010-12-21 at 14:55 -0500, David Warden wrote:
But when I try to get my quota on a different local IP using the -S flag to
doveadm:
doveadm quota get -u warden -S 137.238.2.244:143
The purpose of -S is completely different. It's about connecting to
another doveadm instance. There's
I apologize if this is a stupid question but I just compiled 2.0.8 and am
trying to use doveadm to get the quota for a user using the -S socket_path
option because I have different options for the various local IPs that dovecot
listens on.
For example, my default quota is filesystem (NFS
On Dec 21, 2010, at 3:13 PM, Alex Baule wrote:
Its a UNIX Socket , not a TCP socket.
So, it's be a local unix socket, like postgres do.
Ah, in that case it looks like the docs need to be updated because the man
pages and the wiki contain documentation that indicates TCP sockets should