bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug in Gnus v5.9.0 collecting mail via pop3 with incorrect Date head


From: Kevin Rodgers
Subject: Re: Bug in Gnus v5.9.0 collecting mail via pop3 with incorrect Date header
Date: Mon, 26 Jan 2004 13:13:15 -0700
User-agent: Mozilla/5.0 (X11; U; SunOS i86pc; en-US; rv:0.9.4.1) Gecko/20020406 Netscape6/6.2.2

Gareth Owen wrote:

This is the backtrace:

Debugger entered--Lisp error: (error "Cannot get new mail")
  signal(error ("Cannot get new mail"))
  error("Cannot get new mail")
  byte-code("ÁÂÃ\"!"
  mail-source-fetch((pop :server "pop.freeserve.net" :user "myusername" :password 
"notactuallymy password") (lambda (file orig-file) (nnmail-split-incoming file (quote 
nnml-save-mail) (quote nil) (if ... nil ...) (quote nnml-active-number))))
  nnmail-get-new-mail(nnml nnml-save-nov "/home/gowen/Mail/gnus/" "alex")
  nnml-request-scan("alex" "private")
  gnus-request-scan("nnml+private:alex" (nnml "private"))
  gnus-activate-group("nnml+private:alex" scan)
  gnus-get-unread-articles(nil)
  gnus-group-get-new-news(nil)
  call-interactively(gnus-group-get-new-news)

This is the mail on the server that causes the error.
Note the Date header :
X-From_: nfRSVSU@libero.it Mon Jan 26 16:40:17 2004
Return-path: <nfRSVSU@libero.it>
Envelope-to: test@gwowen.freeserve.co.uk
Delivery-date: Mon, 26 Jan 2004 16:40:17 +0000
Received: from client-200.106.25.156.speedy.net.pe (unknown [200.106.25.156])
        by mwinf3004.me.freeserve.com (SMTP Server) with SMTP id 158A61803325
        for <test@gwowen.freeserve.co.uk>; Mon, 26 Jan 2004 16:17:32 +0100 (CET)
From: <nfRSVSU@libero.it>
To: <test@gwowen.freeserve.co.uk>
Subject: help
Date: MIME-Version: 1.0
Content-Type: multipart/related;
     type="multipart/alternative";
     boundary="Y38fIi16xj683T1Ia44AD5tRaU5jN051"
X-Mailer: AOL 7.0 for Windows UK sub 52
Message-Id: <20040126151732.158A61803325@mwinf3004.me.freeserve.com>

Point taken, that Emacs should not fail to retrieve such a message
(whether from a server regardless of the protocol, or from a spool file).
But note that RFC 2822 does require the Date header to be present, and
its contents to be both syntactically and semantically valid.

--
Kevin Rodgers





reply via email to

[Prev in Thread] Current Thread [Next in Thread]