Re: imap-parse-fetch: End of file during parsing

[Tassilo Horn <tassilo@member.fsf.org>]

Hi,

since yesterday I cannot fetch mail from one of my POP3 accounts
anymore, too.  I wonder if that is related to my imap problem.

I got those characterp errors with rcirc, too, but I'm not able to
reproduce it.

,----
| Debugger entered--Lisp error: (wrong-type-argument characterp 12269800)
|   re-search-forward("^\\..\n" nil t)
|   pop3-retr(#<process POP> 1 #<buffer  *pop3-retr*>)
|   pop3-movemail("~/.emacs-mail-crash-box")
|   mail-source-fetch-pop((pop :server "pop.gmx.de" :user "tassilo.horn@gmx.de" :password "XXX") #[(file orig-file) "....\n......\n...\"...%..." [file in-group orig-file nnmail-split-incoming nnml-save-mail nil nnmail-get-split-group (pop :server "pop.gmx.de" :user "tassilo.horn@gmx.de" :password "XXX") nnml-active-number] 7])
|   mail-source-fetch((pop :server "pop.gmx.de" :user "tassilo.horn@gmx.de" :password "XXX") #[(file orig-file) "......\n...?........\n...\"...%..." [file in-group orig-file nnmail-split-incoming nnml-save-mail nil nnmail-get-split-group (pop :server "pop.gmx.de" :user "tassilo.horn@gmx.de" :password "XXX") nnml-active-number] 7])
|   nnmail-get-new-mail-1(nnml nnml-save-nov "~/Mail/Popmail" nil nil nil)
|   nnmail-get-new-mail(nnml nnml-save-nov "~/Mail/Popmail" nil)
|   nnml-request-scan(nil "Popmail")
|   gnus-request-scan(nil (nnml "Popmail" (nnml-directory "~/Mail/Popmail") (nnml-active-file "~/Mail/Popmail/active")))
|   gnus-read-active-file-1((nnml "Popmail" (nnml-directory "~/Mail/Popmail") (nnml-active-file "~/Mail/Popmail/active")) nil)
|   gnus-read-active-file()
|   gnus-group-get-new-news(nil)
|   call-interactively(gnus-group-get-new-news nil nil)
`----

Grr.  When I try to send this mail, I get

,----
| Non-printable characters found.  Continue sending? (d, r, i, e, ?): 
| Sending...
| You have lines longer than 79 characters.  Really post? (y or n) 
| The article contains control characters.  Really post? (y or n) 
| [...]
| Message contains characters with unknown encoding.  Really send? (y or n) 
`----

I replied with r to replace the non-printable chars, but it didn't do
so.  Now I replaced them manually to get the mail sent.  Anyone knows
what could cause those spontaneous coding system troubles?

Bye,
Tassilo