the proxy and director sub-commands intended to be separate and
distinct in their operation? If so, then this makes sense, as a proxy
isn't necessarily a director.
Are there any plans for a proxy kick equivalent that would work
across directors?
--
Tom Pawlowski
OIT-CSS Syste
hanks for taking a look!
* Timo Sirainen [2012-05-17 00:35:49 +0300]:
> On 17.5.2012, at 0.20, Tom Pawlowski wrote:
>
> > dovecot: imap(user1): Error:
> > readdir(/u1/user1/Maildir/.AUTO-DELETED-SPAM/new) failed: Too many levels
> > of symbolic links
> ..
> >
would think the bug
would have been evident before then. I'm also curious as to why dovecot
is getting an ELOOP error code from it.
Any ideas or pointers would be appreciated, sorry for the length. :)
--
Tom Pawlowski
OIT-CSS System Administrator office: Hill 145
email: tom...@jl
n - but as someone on this list pointed
> out recently, that doesn't apply if they try X attempts on the same
> connection. Although, I don't think that was case here - maybe I
> should update my dovecot jail with that illegal chars line. But, be
> that as it may - all these attempts failed because the user didn't
> exist. What if the user exists though? Does this illegal chars make
> a hole for them to enter through?
>
> Simon
>
--
Tom Pawlowski
OIT-CSS System Administrator office: Hill 147
email: tom...@jla.rutgers.edu phone: (732) 445-2634
iving a test
> email (to check if it would show up in the inbox) from another user. Has
> anyone heard of such a thing?
>
> Here's a dump of my dovecot configuration.
>
--
Tom Pawlowski
OIT-CSS System Administrator office: Hill 147
email: tom...@jla.rutgers.edu phone: (732) 445-2634
irst attempt to call it works, subsequent attempts
fail.
I've attached a strace log of it in action.
--
Tom Pawlowski
OIT-CSS System Administrator office: Hill 147
email: tom...@jla.rutgers.edu phone: (732) 445-2634
execve("/usr/bin/doveadm", ["doveadm&
), the ipc
service has a client_limit of 0 by default, so we shouldn't be hitting a
ceiling anyway, correct?
So are these false warnings or something to be concerned about?
--
Tom Pawlowski
OIT-CSS System Administrator office: Hill 147
email: tom...@jla.rutgers.edu ph