From the log:
Oct 6 09:54:10 postamt dovecot: imap(hkunte): Error: quota:
connect(/usr/local/scripts/quota-warning2) failed: Permission denied
From the config:
quota = maildir
quota_rule = INBOX.Trash:storage=+2048M
quota_warning = storage=99%% /usr/local/scripts/quota-warning2 99 %u
Ralf Hildebrandt wrote on 06.10.2010:
From the log:
Oct 6 09:54:10 postamt dovecot: imap(hkunte): Error: quota:
connect(/usr/local/scripts/quota-warning2) failed: Permission denied
From the config:
quota = maildir
quota_rule = INBOX.Trash:storage=+2048M
quota_warning = storage=99%%
* Daniel Luttermann dan...@dlutt.de:
Personally I use this:
service quota-warning {
executable = script /usr/bin/quota-warning.sh
user = vmail
unix_listener quota-warning {
mode = 0660
user = vmail
group = vmail
}
}
What is the meaning of the unix_listener?
Can I
On Wed, 2010-10-06 at 15:33 +0200, Ralf Hildebrandt wrote:
service quota-warning {
executable = script /usr/bin/quota-warning.sh
user = vmail
The process is run as this user.
unix_listener quota-warning {
mode = 0660
user = vmail
group = vmail
This is the socket
* Timo Sirainen t...@iki.fi:
On Wed, 2010-10-06 at 15:33 +0200, Ralf Hildebrandt wrote:
service quota-warning {
executable = script /usr/bin/quota-warning.sh
user = vmail
The process is run as this user.
unix_listener quota-warning {
mode = 0660
user = vmail
On Wed, 2010-10-06 at 16:19 +0200, Ralf Hildebrandt wrote:
Yeah, you can make the service user=root, but give only vmail user
permission to it so only processes running as vmail can connect to it.
Good. The question is: which user will connect to the socket?
dovecot-lda will assume the
* Timo Sirainen t...@iki.fi:
On Wed, 2010-10-06 at 16:19 +0200, Ralf Hildebrandt wrote:
Yeah, you can make the service user=root, but give only vmail user
permission to it so only processes running as vmail can connect to it.
Good. The question is: which user will connect to the
On Wed, 2010-10-06 at 15:29 +0100, Timo Sirainen wrote:
protocol lmtp {
local_ip 127.0.0.1 {
plugin {
quota = maildir:user:noenforcing
}
}
}
Ugh.
You're already using dovecot-lda to deliver the out-of-quota mails? How
do you do this there then?
Oh,
* Timo Sirainen t...@iki.fi:
On Wed, 2010-10-06 at 15:29 +0100, Timo Sirainen wrote:
protocol lmtp {
local_ip 127.0.0.1 {
plugin {
quota = maildir:user:noenforcing
}
}
}
Ugh.
You're already using dovecot-lda to deliver the out-of-quota
On Wed, 2010-10-06 at 16:48 +0200, Ralf Hildebrandt wrote:
Right now I have:
Oct 6 16:38:54 postamt dovecot: lda(ghinrich): save: box=INBOX, uid=993,
msgid=20101006143814.gp19...@charite.de, size=11165930
Oct 6 16:38:54 postamt dovecot: lda(ghinrich): Error: quota:
* Timo Sirainen t...@iki.fi:
On Wed, 2010-10-06 at 16:48 +0200, Ralf Hildebrandt wrote:
Right now I have:
Oct 6 16:38:54 postamt dovecot: lda(ghinrich): save: box=INBOX, uid=993,
msgid=20101006143814.gp19...@charite.de, size=11165930
Oct 6 16:38:54 postamt dovecot: lda(ghinrich):
* Ralf Hildebrandt ralf.hildebra...@charite.de:
Note that above it's trying to connect
to /usr/local/scripts/quota-warning2, which is a completely different
directory. So your quota_warning setting shouldn't have the executable
path, but only quota-warning.
FCK.
Ok, better. Not
* Ralf Hildebrandt ralf.hildebra...@charite.de:
The actual dovecot-lda invocation is:
${BIN_CAT} EOF | /usr/dovecot-2/libexec/dovecot/dovecot-lda -d $USER -o
plugin/quota=maildir:User quota:noenforcing
some text
EOF
dovecot.conf says:
quota = maildir
so should I just use
On Wed, 2010-10-06 at 17:14 +0200, Ralf Hildebrandt wrote:
Oct 6 17:06:24 postamt dovecot: quota-warning: Error: lda: Fatal: Unknown
argument: plugin/quota=maildir:User quota:noenforcing
This looks as if it's missing -o parameter..
The actual dovecot-lda invocation is:
${BIN_CAT} EOF |
* Timo Sirainen t...@iki.fi:
On Wed, 2010-10-06 at 17:14 +0200, Ralf Hildebrandt wrote:
Oct 6 17:06:24 postamt dovecot: quota-warning: Error: lda: Fatal: Unknown
argument: plugin/quota=maildir:User quota:noenforcing
This looks as if it's missing -o parameter..
The actual
15 matches
Mail list logo
