Lampa wrote:
Hello,
MTA is qmail, and there is no problem with it (qmail is stopped for
current user - sticky bit set). Problem is dovecot - and is not
possible to stop dovecot (due to clients)
Well, the "deny passwd file" would be a great solution about now, don't you
think?
http://wiki.do
Hello,
that's not good solution ;( some mailboxes have 1 - 3GB. So need
another solution
Or it can be feature request: disable access when user homedir is sticky ?
2008/4/8, Tolga <[EMAIL PROTECTED]>:
>
>
> Lampa wrote:
>
> > Hello,
> >
> > MTA is qmail, and there is no problem with it (qmail i
Lampa wrote:
Hello,
MTA is qmail, and there is no problem with it (qmail is stopped for
current user - sticky bit set). Problem is dovecot - and is not
possible to stop dovecot (due to clients)
Then copy mailboxes to somewhere else and make backup there.
2008/4/8, Tolga <[EMAIL PROTECTED]
Hello,
MTA is qmail, and there is no problem with it (qmail is stopped for
current user - sticky bit set). Problem is dovecot - and is not
possible to stop dovecot (due to clients)
2008/4/8, Tolga <[EMAIL PROTECTED]>:
>
>
> Lampa wrote:
>
> > Hello,
> >
> > is there some way how to disable tempo
Lampa wrote:
Hello,
is there some way how to disable temporarily account or access to
files. I need to backup with tar, but there is problem when tar is
reading and some file changed (with --ignore-failed-read it continues
but archive is not created and without --ignore-failed-read it fails).
Hello,
is there some way how to disable temporarily account or access to
files. I need to backup with tar, but there is problem when tar is
reading and some file changed (with --ignore-failed-read it continues
but archive is not created and without --ignore-failed-read it fails).
Some accounts are
On Apr 7, 2008, at 4:58 PM, Bill Cole wrote:
Hey folks. One feature I'd really like to see in dovecot is the
ability to point it at a database (with a configurable query) and
have it allow or deny a connection based on looking up the source
IP address in that database.
I run Postfix,
On Apr 7, 2008, at 5:02 PM, Charles Marcus wrote:
Hey folks. One feature I'd really like to see in dovecot is the
ability to point it at a database (with a configurable query) and
have it allow or deny a connection based on looking up the source
IP address in that database.
Is there any rea
> I'm reentering this conversation a little late - but how are you
> delivering mail? Via the Dovecot LDA (in which case Sieve should be
> used)? Or directly via e.g. procmail (in which case Sieve never gets a
> chance to be run)?
I have Exim, which does its usual thing, and the LDA is Dovecot
On Mon, 7 Apr 2008, [EMAIL PROTECTED] wrote:
Unfortunately, this does not seem to be over, yet. I have a script in the
right place now, it is set as Active, but it does not seem to be doing
anything. That is, everything is still going to the INBOX instead of to
the designated directories, and
Unfortunately, this does not seem to be over, yet. I have a script in the
right place now, it is set as Active, but it does not seem to be doing
anything. That is, everything is still going to the INBOX instead of to
the designated directories, and there are no entries in the log files. I
am usi
Charles Marcus wrote:
> On 4/7/2008, Raphael Bittencourt S. Costa ([EMAIL PROTECTED])
> wrote:
>> Using dnotify dovecot's performance was very bad. The system consumes
>> 90% of cpu with just a few imap process running (about 30 process).
>> The performance using --with-notify=none was the same as
On 4/7/2008, Bill Cole ([EMAIL PROTECTED]) wrote:
Hey folks. One feature I'd really like to see in dovecot is the
ability to point it at a database (with a configurable query) and
have it allow or deny a connection based on looking up the source
IP address in that database.
Is there any reaso
At 12:20 PM -0400 4/7/08, Dave McGuire wrote:
Hey folks. One feature I'd really like to see in dovecot is the
ability to point it at a database (with a configurable query) and
have it allow or deny a connection based on looking up the source IP
address in that database.
I run Postfix, an
> sieve_storage = ~/sieve
>
> That means that your script files are inside your home directory in a
> subdirectory called 'sieve'. All scripts must have an extension '.sieve'.
> Meaning that if you put a script called 'ingo' on your server through
> ManageSieve, it is stored in that directory as
[EMAIL PROTECTED] schreef:
OK. I understand all this. Thank you for the reference to the
specification. Apart from the wrong name, I was using PUTSCRIPT instead
of GETSCRIPT. Now, where do I have to put the scripts to GET them? My
home directory does not work, nor do the /var/mail/user/ and
> From what I see here I am not quite sure whether you have understood
> the ManageSieve protocol. The putscript command as specified above
> expects you to provide 2049 bytes of script directly after entering the
> command. It will not accept other commands until it has fully read the
> 2049 byte
(Forgot to CC to the mailinglist)
[EMAIL PROTECTED] schreef:
Here's the latest managesieve session:
OK "Logged in."
CAPABILITY
"IMPLEMENTATION" "dovecot"
"SIEVE" "fileinto reject envelope vacation imapflags notify subaddress
relational comparator-i;ascii-numeric regex"
OK "Capability completed."
On 4/7/2008, Raphael Bittencourt S. Costa ([EMAIL PROTECTED])
wrote:
Using dnotify dovecot's performance was very bad. The system consumes
90% of cpu with just a few imap process running (about 30 process).
The performance using --with-notify=none was the same as using
inotify,
so it could be
On Sat, 2008-04-05 at 14:22 +0300, Uldis Pakuls wrote:
> donotify is more resource expensive - inotify allows monitoring of
> both
> files and directories via a single open fd.
> so before you try --with-notify=none, try --with-notify=dnotify
Using dnotify dovecot's performance was very bad. T
Hey folks. One feature I'd really like to see in dovecot is the
ability to point it at a database (with a configurable query) and
have it allow or deny a connection based on looking up the source IP
address in that database.
I run Postfix, and I've got it configured to use a database
There are no entries in any of the logs related to lda or managesieve.
I did run managesieve again (after creating the relevant logfiles), and
got this:
OK "Logged in."
LISTSCRIPTS
imap(root): Warning: Active sieve script symlink /home/cam/.dovecot.sieve
is no symlink.
OK "Listscripts completed."
> First of all, could you provide us with the output of 'dovecot -n' and,
> since you are talking ManageSieve manually to the server already, a
> listing of a protocol session (i.e. commands and responses)? And, if you
> enable mail_debug for the managesieve protocol, you will get messages in
>
My system is very slow, the Maildir is mounted via NFS, the index is on
a local disk system.
In the config, there is:
max_mail_processes = 3000
login_processes_count = 6
login_max_processes_count = 1500
I can see a large number of processes named "imap", some users have more
than 12 such proc
[EMAIL PROTECTED] wrote:
With all the mess that my email has become, it makes sense for me to try
to make use of Sieve, but I'm having quite the time finding out how to
make it work. I'm running 1.0.13 on a Debian machine. Sieve appears to
be compiled with it. I can access managesieve, and I h
25 matches
Mail list logo
