9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Gordon Hogan <dhog@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] I still dont understand...
Date: Mon, 16 Jul 2001 15:53:30 -0400	[thread overview]
Message-ID: <20010716195334.36D2F19A32@mail.cse.psu.edu> (raw)

There are some bugs in the upas/fs plaintext POP implementation, which
probably weren't detected because upas/fs insists on APOP if the server
supports it.  Here's a patch for them.  Note that there is another bug -- upas/fs
will die if your POP mbox has 0 messages.  I haven't got around to fixing that.

/n/dump/2001/0716/sys/src/cmd/upas/fs/pop3.c:132,133 c /n/dump/2001/0705/sys/src/cmd/upas/fs/pop3.c:132,133
< 		sprint(buf, "/mnt/auth/pop/%s/%s", pop->host, pop->user);
< 		if((fd = open(buf, OREAD)) < 0)
---
> 		sprint(buf, "/mnt/auth/pop3/%s/%s", pop->host, pop->user);
> 		if((fd = open(buf, ORDWR)) < 0)
/n/dump/2001/0716/sys/src/cmd/upas/fs/pop3.c:469 c /n/dump/2001/0705/sys/src/cmd/upas/fs/pop3.c:469
< 	int nf, ppop;
---
> 	int nf;
/n/dump/2001/0716/sys/src/cmd/upas/fs/pop3.c:472,473 c /n/dump/2001/0705/sys/src/cmd/upas/fs/pop3.c:472
< 	ppop = strncmp(path, "/pop/", 5) == 0;
< 	if(!ppop && strncmp(path, "/apop/", 6) != 0)
---
> 	if(strncmp(path, "/pop/", 5) != 0 && strncmp(path, "/apop/", 6) != 0)
/n/dump/2001/0716/sys/src/cmd/upas/fs/pop3.c:491 c /n/dump/2001/0705/sys/src/cmd/upas/fs/pop3.c:490,491
< 	pop->ppop = ppop;
---
> 	if(strncmp(path, "/pop/", 5) == 0)
> 		pop->ppop = 1;



             reply	other threads:[~2001-07-16 19:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-16 19:53 David Gordon Hogan [this message]
2001-07-16 19:58 ` Michael Grunditz
2001-07-16 20:02   ` Michael Grunditz
2001-07-16 20:04 ` Boyd Roberts
2001-07-16 20:00   ` Michael Grunditz
  -- strict thread matches above, loose matches on Subject: below --
2001-07-16 20:39 David Gordon Hogan
2001-07-17  0:55 ` Boyd Roberts
2001-07-16 20:33 David Gordon Hogan
2001-07-16 19:33 Michael Grunditz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010716195334.36D2F19A32@mail.cse.psu.edu \
    --to=dhog@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).