> -----Messaggio originale----- > Da: Stefano Bagnara [mailto:[EMAIL PROTECTED] > Inviato: martedì 8 maggio 2007 20.02 > A: James Users List > Oggetto: Re: QUIT command > > Marcello Marangio ha scritto: > > Hi all > > > > As you probably already know, James performs a user lock processing the > PASS > > command and releases the processing the QUIT command. > > An user lock? Isn't this a custom patch you did to your own James > Server? IIRC we (official JAMES Server distribution) never supported > user locking (and this is a known bug, but not the bug you're reporting > now). > > Please check if the lock is in your custom code or please point us to > the code locking the user.
Yes, you're right: I was looking at some old code I made to fix the lock bug for a single instance, and I thought it was some original james code... > > > So if after a PASS a QUIT is not issued, the user gets stuck. > > > > The question is: if a client chooses the USER and PASS sequence to get > the > > authentication (instead of APOP), is the QUIT command mandatory? > > Anyway, the question is the same, even if is more rfc1939 related rather than james: is QUIT command the ONLY way to pass from the AUTHENTICATION state to the UPDATE state? > > If not, it is quite of a bug. ... of mine. Thanks Marcello --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
