On Thu, 2007-08-09 at 11:01 -0700, Jeff Ramsey wrote:
> > No, that setting doesn't do anything for IMAP. Also none of those
> > settings affect the "unknown user" error, so maybe 0.99 is somehow
> > lucky
> > in not generating those. Perhaps setting blocking=yes to userdb passwd
> > args would he
On Aug 9, 2007, at 4:58 AM, Timo Sirainen wrote:
On Thu, 2007-08-02 at 12:50 -0700, Jeff Ramsey wrote:
On Aug 1, 2007, at 12:10 PM, Timo Sirainen wrote:
On Wed, 2007-08-01 at 12:05 -0700, Jeff Ramsey wrote:
Aug 1 11:58:51 imap dovecot: auth(default): passwd(QUINAULT-
ileneyoung,:::10.2
On Thu, 2007-08-02 at 12:50 -0700, Jeff Ramsey wrote:
> On Aug 1, 2007, at 12:10 PM, Timo Sirainen wrote:
>
> > On Wed, 2007-08-01 at 12:05 -0700, Jeff Ramsey wrote:
> >> Aug 1 11:58:51 imap dovecot: auth(default): passwd(QUINAULT-
> >> ileneyoung,:::10.200.254.110): lookup
> >> Aug 1 11:58:
On Aug 1, 2007, at 12:10 PM, Timo Sirainen wrote:
On Wed, 2007-08-01 at 12:05 -0700, Jeff Ramsey wrote:
Aug 1 11:58:51 imap dovecot: auth(default): passwd(QUINAULT-
ileneyoung,:::10.200.254.110): lookup
Aug 1 11:58:51 imap dovecot: auth(default): passwd(QUINAULT-
ileneyoung,:::10.200.
On Aug 1, 2007, at 12:10 PM, Timo Sirainen wrote:
I think the problem has to do with NSS. It probably failed with some
error, but since unfortunately getpwnam() interface doesn't support
reporting errors, Dovecot just assumed that the user didn't exist.
I can't think of why this would work any
On Wed, 2007-08-01 at 12:05 -0700, Jeff Ramsey wrote:
> Aug 1 11:58:51 imap dovecot: auth(default): passwd(QUINAULT-
> ileneyoung,:::10.200.254.110): lookup
> Aug 1 11:58:51 imap dovecot: auth(default): passwd(QUINAULT-
> ileneyoung,:::10.200.254.110): unknown user
..
> Perhaps this she
On Aug 1, 2007, at 9:47 AM, Timo Sirainen wrote:
On 1.8.2007, at 18.43, Jeff Ramsey wrote:
Since my initial post, I have noticed this in my log file as well:
Aug 1 08:13:42 imap dovecot: auth(default): userdb
(johnfowler,:::65.174.242.248): user not found from userdb
Aug 1 08:13:42 imap
On 1.8.2007, at 18.43, Jeff Ramsey wrote:
Aug 1 08:09:44 imap dovecot: imap-login: Login: user=,
method=PLAIN, rip=:::10.11.254.52, lip=:::65.174.242.66
Aug 1 08:09:44 imap dovecot: IMAP(jefframsey): Disconnected:
Logged out
I have read that this means that the client was the one
On Aug 1, 2007, at 2:26 AM, Timo Sirainen wrote:
On Tue, 2007-07-31 at 17:12 -0700, Jeff Ramsey wrote:
I am now getting the following message on all Outlook Clients:
"Your IMAP Server closed the connectionthis can occur if the
connection is idle for too long"
What does Dovecot show in lo
version: 1.0.2
imap_client_workarounds = outlook-idle
And I've no problem with OE 6.0. I've been testing with imap since I
read your first post, and there have not been any disconnections.
I don't know about OE2003.
/Bachman
Sergey A. Kobzar skrev:
Hi Jeff,
Did you try play with imap_client_
On Tue, 2007-07-31 at 17:12 -0700, Jeff Ramsey wrote:
> I am now getting the following message on all Outlook Clients:
>
> "Your IMAP Server closed the connectionthis can occur if the
> connection is idle for too long"
What does Dovecot show in logs as the disconnect reason?
This sounds li
Hi Jeff,
Did you try play with imap_client_workarounds options?
I think this must help you:
outlook-idle:
Outlook and Outlook Express never abort IDLE command, so if no mail
arrives in half a hour, Dovecot closes the connection. This is still
fine, except Outlook doesn't connect back so yo
I have been using Dovecot for an IMAP server for a few years now,
with no hitch. Even using Outlook 2K/2K3 as a client.
Yesterday, I had a user experience the 'Negative UIDs' issue spoken
of here: http://wiki.dovecot.org/Clients/NegativeUIDs
I performed all of the steps mentioned in this ar
13 matches
Mail list logo
