Re: ipop3/imap4 login problem

2004-10-05 Thread Mark Crispin
What operating system are you using?
You seem to have obtained a modified distribution, because there is no 
such build option as -D WITH_SSL_AND_PLAINTEXT in the UW distribution.

Have you tried the original UW distribution, on
ftp://ftp.cac.washington.edu/mail/imap.tar.Z
-- Mark --
http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.


Re: locking problem in imap-2002b

2004-10-05 Thread sahil
Quoting Peter Ip <[EMAIL PROTECTED]>:

[...]

> > Just to clarify, user 23048 held the lockfile for user 64763's INBOX?
>
> Yes, that's correct.

Ok. :)  Now, how is that possible if 64763's INBOX is u+rw, with everyone else
(including those in the mailuser group) lacking permission?

[...]

--
Sahil Tandon



Re: locking problem in imap-2002b

2004-10-05 Thread Peter Ip
Hi,
On Tue, 5 Oct 2004 [EMAIL PROTECTED] wrote:
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Tue,  5 Oct 2004 10:11:46 -0400
Subject: Re: locking problem in imap-2002b
Quoting Peter Ip <[EMAIL PROTECTED]>:
[...]
A user using Netscape Messenger couldn't compact his INBOX - imap said
the INBOX was read-only. When I looked on the server, another user
held the lock file in /tmp:
Just to clarify, user 23048 held the lockfile for user 64763's INBOX?

Yes, that's correct.
Peter
_
Peter Ip, PhD
Computing and Network Services, University of Toronto
email: [EMAIL PROTECTED]


Re: locking problem in imap-2002b

2004-10-05 Thread sahil
Quoting Peter Ip <[EMAIL PROTECTED]>:

[...]

> A user using Netscape Messenger couldn't compact his INBOX - imap said
> the INBOX was read-only. When I looked on the server, another user
> held the lock file in /tmp:

Just to clarify, user 23048 held the lockfile for user 64763's INBOX?

[...]

--
Sahil Tandon


Re: locking problem in imap-2002b

2004-10-05 Thread Peter Ip
Hi Frode,
No, we're not using RedHat's RPM's. I've compiled our own.
Thanks
Peter
_
Peter Ip, PhD
Computing and Network Services, University of Toronto
email: [EMAIL PROTECTED]
On Tue, 5 Oct 2004, Frode Nordahl wrote:
From: Frode Nordahl <[EMAIL PROTECTED]>
To: Peter Ip <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Date: Tue, 5 Oct 2004 09:35:00 +0200
Subject: Re: locking problem in imap-2002b
On Oct 4, 2004, at 22:40, Peter Ip wrote:
Hi,
I'm running imap-2002b on RedHat AS3.
Are you running with RedHat's RPM's or have you compiled your own version?
RedHat patches imap-uw, replacing imap-uw's locking functions (using fcntl).
In my experience, this causes things to lock agains eachother everywhere, and 
bypasses IMAP's kiss of death method, since the fcntl syscall is just 
restarted when it recieves the signal.

Mvh,
Frode Nordahl
A user using Netscape Messenger couldn't compact his INBOX - imap said
the INBOX was read-only. When I looked on the server, another user
held the lock file in /tmp:
# ls -li INBOX
7094292 -rw---1 64763mailusr178262 Oct  4 16:31 INBOX
# ls -l /tmp/.*.6c4014
-rw-rw-rw-1 23048mailusr 5 Oct  4 06:52 /tmp/.891.6c4014
User 23048 had an imapd process:
# ps -uawx | grep 23048
#23048   27815  0.0  0.0  4656 1896 ?S06:52   0:00 imapd
root 30656  0.0  0.0  1616  496 pts/1S15:18   0:00 grep 27815
The INBOX for user 23048 had inode number 7094295. Is there a race 
condition that is being tickled? I looked in the RELNOTES for imap-2004a
but couldn't see anything relevant.

Peter
_
Peter Ip, PhD
Computing and Network Services, University of Toronto
email: [EMAIL PROTECTED]
--
--
For information about this mailing list, and its archives, see: 
http://www.washington.edu/imap/c-client-list.html
--



Re: locking problem in imap-2002b

2004-10-05 Thread Frode Nordahl
On Oct 4, 2004, at 22:40, Peter Ip wrote:
Hi,
I'm running imap-2002b on RedHat AS3.
Are you running with RedHat's RPM's or have you compiled your own 
version?

RedHat patches imap-uw, replacing imap-uw's locking functions (using 
fcntl).

In my experience, this causes things to lock agains eachother 
everywhere, and bypasses IMAP's kiss of death method, since the fcntl 
syscall is just restarted when it recieves the signal.

Mvh,
Frode Nordahl
A user using Netscape Messenger couldn't compact his INBOX - imap said
the INBOX was read-only. When I looked on the server, another user
held the lock file in /tmp:
# ls -li INBOX
7094292 -rw---1 64763mailusr178262 Oct  4 16:31 INBOX
# ls -l /tmp/.*.6c4014
-rw-rw-rw-1 23048mailusr 5 Oct  4 06:52 
/tmp/.891.6c4014

User 23048 had an imapd process:
# ps -uawx | grep 23048
#23048   27815  0.0  0.0  4656 1896 ?S06:52   0:00 imapd
root 30656  0.0  0.0  1616  496 pts/1S15:18   0:00 grep 
27815

The INBOX for user 23048 had inode number 7094295. Is there a race 
condition that is being tickled? I looked in the RELNOTES for 
imap-2004a
but couldn't see anything relevant.

Peter
_
Peter Ip, PhD
Computing and Network Services, University of Toronto
email: [EMAIL PROTECTED]
--
--
For information about this mailing list, and its archives, see: 
http://www.washington.edu/imap/c-client-list.html
--