Hello.
I'm reading http://wiki.dovecot.org/Quota/1.1 one last time before my upgrade,
and I have a question about quota_warning option. Which type of script must we
use for this example:
quota_warning = storage=95%% /usr/local/bin/quota-warning.sh 95
What the script must doing? It sends an ema
On Sun, 29 Jun 2008 03:53:54 pm Zhang Huangbin wrote:
> Hi, all.
>
> I just upgrade from 1.0.15 to 1.1.1 in a test box(RHEL 5.2, x86_64).
>
> after upgrade, i got this warning msg:
>
> 8<
> # /etc/init.d/dovecot restart
> Stopping Dovecot Imap: [ OK ]
Hi, all.
I just upgrade from 1.0.15 to 1.1.1 in a test box(RHEL 5.2, x86_64).
after upgrade, i got this warning msg:
8<
# /etc/init.d/dovecot restart
Stopping Dovecot Imap: [ OK ]
Starting Dovecot Imap: Warning: fd limit 1024 is lower than what Dov
On Sat, 2008-06-28 at 10:00 -0700, Michael D Godfrey wrote:
> >
> > On Wed, 2008-06-25 at 09:40 -0700, Michael D. Godfrey wrote:
> >
> >>> > > A guess would be that this is likely due to the endianess of the
> >>> > > multiple architectures that the index is being accessed with. We have
> >>>
On Wed, 2008-06-25 at 09:40 -0700, Michael D. Godfrey wrote:
> > A guess would be that this is likely due to the endianess of the
> > multiple architectures that the index is being accessed with. We have
> > the same issue here across i686/x86_64/sparc. I'm about to post to an
> > older ema
This was starting from a clean index, first opening pine on the NFS
Solaris 9 sparc machine, and then at the same time opening pine on my
Fedora 9 i386 workstation.
Why does it matter where you run Pine? Does it directly execute Dovecot
on the local machine instead of connecting via TCP?
On 6/27/2008 8:27 PM, Jacob Yocom-Piatt wrote:
any clues on how to fix this issue would be welcome.
It will probably be helpful to provide output of dovecot -n so we can
see your config... ?
--
Best regards,
Charles
El Saturday 28 June 2008 07:25:31 Timo Sirainen escribió:
> On Fri, 2008-06-27 at 15:09 +0100, Imobach González Sosa wrote:
> > Hi all,
> >
> > I wanna to set up shared folders for a couple of users and I'd like that
> > everyone could keep the \Seen flag as private. So if user #1 reads some
> > me
El Friday 27 June 2008 21:08:30 Asheesh Laroia escribió:
> On Fri, 27 Jun 2008, Imobach González Sosa wrote:
> > There's no problem in disallowing the users to update the Seen flag.
> > What I want is that every user have their own Seen flags.
>
> Timo and others will know more; but for me, I would
