Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: pop server access?
Date: 20 Oct 1998 19:57:35 +0200	[thread overview]
Message-ID: <m31zo3une8.fsf@sparky.gnus.org> (raw)
In-Reply-To: Norbert Koch's message of "20 Oct 1998 12:53:31 +0200"

Norbert Koch <n.koch@delta-ii.de> writes:

> have you made any changes regarding the pop server access? I can't get
> onto the server after the installation of 0.35.

This patch was applied to make things work under Emacs 20.3:

Index: pop3.el
===================================================================
RCS file: /local/lib/CVSROOT/gnus/lisp/pop3.el,v
retrieving revision 5.1
retrieving revision 5.2
diff -c -r5.1 -r5.2
*** pop3.el	1998/08/29 17:43:28	5.1
--- pop3.el	1998/10/19 22:25:09	5.2
***************
*** 111,124 ****
  Returns the process associated with the connection."
    (let ((process-buffer
  	 (get-buffer-create (format "trace of POP session to %s" mailhost)))
! 	(process))
      (save-excursion
        (set-buffer process-buffer)
!       (erase-buffer)
!       (setq pop3-read-point (point-min))
!       )
      (setq process
  	  (open-network-stream "POP" process-buffer mailhost port))
      (let ((response (pop3-read-response process t)))
        (setq pop3-timestamp
  	    (substring response (or (string-match "<" response) 0)
--- 111,126 ----
  Returns the process associated with the connection."
    (let ((process-buffer
  	 (get-buffer-create (format "trace of POP session to %s" mailhost)))
! 	(process)
!         (coding-system-for-read 'no-conversion)
!         (coding-system-for-write 'no-conversion)
!         )
      (save-excursion
        (set-buffer process-buffer)
!       (erase-buffer))
      (setq process
  	  (open-network-stream "POP" process-buffer mailhost port))
+     (setq pop3-read-point (point-min))
      (let ((response (pop3-read-response process t)))
        (setq pop3-timestamp
  	    (substring response (or (string-match "<" response) 0)

It looks a bit weird to me, now that I think about it.  Why has the
`pop3-read-point' setting moved downwards?  I'll move it back up.

Ratinox, I know you don't like Muletilations of pop3, but it is
necessary it it's going to work in that release.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


  reply	other threads:[~1998-10-20 17:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-10-20 10:53 Norbert Koch
1998-10-20 17:57 ` Lars Magne Ingebrigtsen [this message]
1998-10-22  5:21   ` Norbert Koch
     [not found]     ` <x7yaq8gpp8.fsf@peorth.gweep.net>
1998-10-23  4:39       ` Norbert Koch
     [not found]         ` <x7emry3jcc.fsf@peorth.gweep.net>
1998-10-25 11:54           ` Norbert Koch
     [not found]             ` <x7zpak5fgp.fsf@peorth.gweep.net>
1998-10-26  6:02               ` Norbert Koch
     [not found]                 ` <x7btmyyk3x.fsf@peorth.gweep.net>
1998-10-27 13:18                   ` Norbert Koch
1998-11-04  7:47                   ` Shenghuo ZHU
     [not found]                     ` <x7u30fpi7v.fsf@peorth.gweep.net>
1998-11-04 18:00                       ` Jan Vroonhof
     [not found]   ` <x790ia3thq.fsf@peorth.gweep.net>
1998-10-22  7:14     ` Urban Engberg
1998-10-22  7:22   ` Urban Engberg

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=m31zo3une8.fsf@sparky.gnus.org \
    --to=larsi@gnus.org \
    /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).