When a user enable vacation in sieve deliver die and the mail lost. I am
using 1.0.3
Thanks
---
in syslog
postfix/pipe[16060]: 8E33017D4: to=<[EMAIL PROTECTED
Am Freitag, 10. August 2007 schrieb Scott Silva:
> Set up a script to move all those marked messages to a "trash" folder
> in each users mailstore. Then you can script another process to delete
> messages in their trash folder older than X days.
Alternatively you could use "find" to simply just de
Michael Weisgerber spake the following on 8/10/2007 11:47 AM:
> Yes, you are right, this will work. Thank you!
> But, as I am never satisfied, ;o) I'd prefer a solution which will not
> delete all marked messages, but keeps, let's say, the last two weeks. Just
> to be able to recover if there had b
Yes, you are right, this will work. Thank you!
But, as I am never satisfied, ;o) I'd prefer a solution which will not
delete all marked messages, but keeps, let's say, the last two weeks. Just
to be able to recover if there had been a faulty deletion decision before.
-Ursprüngliche Nachricht
Hi folks,
I just replaced my mail server's UW-imap with dovecot yesterday. I use
the following folder setting
default_mail_env =
mbox:/asiaa/home/%u/:/asiaa/home/%u/mail/:INBOX=/var/mail/%u:INDEX=/asiaa/home/%u/mail/dovecot_indexes
This is a Scientific linux 4.2 with dovecot 0.99.11-2 .
Now to
I am using Dovecot 1.0.rc15
rc15 is very old... I'd update regardless when you get the chance... and
if I'm not mistaken, there were quite a few updates that affected
Outlook/Outlook Express clients...
together with Outlook (I apologize)
heh...
Now I discovered, that all the old eMails,
On Friday 10 August 2007 10:12:50 Michael Weisgerber wrote:
> Hello 2gether,
>
> I am using Dovecot 1.0.rc15 together with Outlook (I apologize) via IMAPS.
> Now I discovered, that all the old eMails, I marked for deleting, are still
> there, even the veeery old ones. Dovecot is marking the eMails
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 9 Aug 2007, Timo Sirainen wrote:
It should be set if you use userdb passwd. For other userdbs you need to
return it youself. For example with LDAP:
user_attrs = uid=system_user,..etc..
Hmm, that's a bummer! It works with this setting.
I
This is the output of dovecot -n?? or dovecot -a??
I'm sorry; dovecot -a as you advised me, of course.
Release : 1.2.rc15.el5
This is a very old version...
You really should update to at least 1.0 - but best would be the current
version, 1.0.3 - otherwise, you may be chasing a proble
On 8/10/2007, Jordi Espasa Clofent ([EMAIL PROTECTED]) wrote:
My dovecot.conf shows as:
This is the output of dovecot -n?? or dovecot -a??
Release : 1.2.rc15.el5
This is a very old version...
You really should update to at least 1.0 - but best would be the current
version, 1.0.3 - o
dovecot -n is much preferred, as it shows only settings that have been
changed from defaults, as opposed to ALL settings...
You¡ve all the reason. My dovecot.conf shows as:
# /etc/dovecot.conf
base_dir: /var/run/dovecot
log_path: /var/log/dovecot.log
info_log_path:
log_timestamp: %b %d %H:%M:%S
I have a Postfix+Dovecot working in beta/testing; it seems to run very
fine, but one beta-tester user says that kmail informs him about
frequent desconnections.
My dovecot -a shows:
dovecot -n is much preferred, as it shows only settings that have been
changed from defaults, as opposed to AL
Timo Sirainen escribió:
> On Thu, 2007-08-09 at 10:33 +0200, Geert Hendrickx wrote:
>> Timo,
>>
>> is this ok with you? It allows building dovecot-sieve against an installed
>> dovecot package (if --enable-header-install additionally installs liblib.a)
>> including sievec and sieved (needed for py
Hi all,
¿Is there some way/method to monitorize and see what users are working
at same time?
Thanks.
Hi all,
I have a Postfix+Dovecot working in beta/testing; it seems to run very
fine, but one beta-tester user says that kmail informs him about
frequent desconnections.
My dovecot -a shows:
# /etc/dovecot.conf
base_dir: /var/run/dovecot
log_path:
info_log_path:
log_timestamp: %b %d %H:%M:%S
15 matches
Mail list logo