On Tuesday 20 October 2009 21:49:45 Timo Sirainen wrote:
> On Tue, 2009-10-20 at 17:10 +0200, Michal Hlavinka wrote:
> > On Tuesday 13 October 2009 19:10:15 Timo Sirainen wrote:
> > > On Tue, 2009-10-13 at 17:26 +0200, Michal Hlavinka wrote:
> > > > would it be possible to:
> > > > a) send content
Timo Sirainen wrote:
It currently doesn't even try to group same user's connections to same
process, they'll just go randomly to whichever process manages to accept
it first. Some day perhaps there should be a new service in the middle
that keeps track of existing connections and forwards new one
On Fri, Oct 23, 2009 at 6:14 AM, Timo Sirainen wrote:
> http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha2.tar.gz
> http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha2.tar.gz.sig
>
I have successfully installed it on a few FreeBSD boxes (6.4 and 7.2) with a
few hundred users each, in
I've been looking at various client fixes to add :from, but ultimately the
better solution would be in sieve/managesieve as although I have a single
webmail solution I'm also offering imap access.
A really simple solution (for me) would be for sieve to copy the :address to
:from. I may even implem
Hi list,
I am trying to get rid of the "Error:
file_dotlock_create(~/.dovecot.lda-dupes) failed: No such file or
directory" by adding home directories to my virtual users (ldap).
I want this home dir' to be specified like this:
/var/vmail/$USER/home/
and the sieve scripts to go to:
/var/vmail/
On Thu, Oct 22, 2009 at 07:58:22PM +0200, Marco Nenciarini wrote:
> Timo Sirainen ha scritto:
> >On Thu, 2009-10-22 at 11:44 +0200, Marco Nenciarini wrote:
> >>This morning it happened another time, another time during the daily
> >>cron execution.
> >>
> >>Oct 22 06:26:57 server dovecot: pop3-log
I was glancing at my logwatch report when I noticed:
dovecot: IMAP(robinmail):
fchown(/home/robinmail/mail/.imap/INBOX/dovecot.index.log.newlock, -1,
10(wheel)) failed: Operation not permitted (egid=100(users), group based on
/var/mail/robinmail): 1 Time(s)
dovecot: IMAP(robinmail):
fc
On Sat, 2009-10-24 at 02:38 +0700, Robin Atwood wrote:
> I was glancing at my logwatch report when I noticed:
>
> dovecot: IMAP(robinmail):
> fchown(/home/robinmail/mail/.imap/INBOX/dovecot.index.log.newlock, -1,
> 10(wheel)) failed: Operation not permitted (egid=100(users), group based on
On Saturday 24 October 2009, Timo Sirainen wrote:
> On Sat, 2009-10-24 at 02:38 +0700, Robin Atwood wrote:
> > I was glancing at my logwatch report when I noticed:
> >
> > dovecot: IMAP(robinmail):
> > fchown(/home/robinmail/mail/.imap/INBOX/dovecot.index.log.newlock, -1,
> > 10(wheel)) failed:
Hi,
I am not yet completely happy with the logging behavior of the lmtp. It
logs informative messages like 'lmtp: Info: Connection closed' or 'lmtp:
Info: Disconnected for inactivity'. Hm, which server was connected to
the lmtp? Who was disconnected for inactivity?
I think it would be useful if t
On Sat, 2009-10-24 at 00:02 +0200, Pascal Volk wrote:
> I think it would be useful if the lmtp would also log new connections.
> For example:
> a) TCP connections:
> lmtp: Info: Connection: rip=10.1.2.3, lip=10.1.2.5, cid=12.12345
> b) Socket connections:
> lmtp: Info: Connection: via sock
Using FreeBSD-7.2, I am attempting to configure the system newsyslog
utility to rotate the dovecot.log file. I would prefer to use the
system utility rather than the one described on the dovecot wiki for
rotating the file. Unfortunately, it is not working. This is the error
message that is spawned:
On 10/24/2009 12:34 AM Timo Sirainen wrote:
> On Sat, 2009-10-24 at 00:02 +0200, Pascal Volk wrote:
>> I think it would be useful if the lmtp would also log new connections.
>> For example:
>> a) TCP connections:
>> lmtp: Info: Connection: rip=10.1.2.3, lip=10.1.2.5, cid=12.12345
>> b) Sock
13 matches
Mail list logo