Gnus development mailing list
 help / color / mirror / Atom feed
From: Hirotaka Honda <hirotaka@hondalaw.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>, ding@gnus.org
Subject: Re: Mail source failed, wrong-type-argument integer-or-marker-p nil
Date: Fri, 28 May 2021 01:49:27 +0900	[thread overview]
Message-ID: <67b31f60-16fa-16f7-ee0c-3e97785c2dba@hondalaw.com> (raw)
In-Reply-To: <87wnrkw4kl.fsf@ericabrahamsen.net>

Dear all

I moved nnmail.elc and el.gz and put condition-case-unless-debug into
nnmail.el.
Somehow debugger window did not open.

I found this line in *Messages"
>Processing mail from ~/.emacs-mail-crash-box...

Does it suggest email crashed, I forgot it, and some files (.newsrc,
.newsrc.eld, newsrc-dribble, and .gnus.registry.eieio) left collapsed?

Hirotaka Honda

On 2021/05/28 0:59, Eric Abrahamsen wrote:
> Hirotaka Honda <hirotaka@hondalaw.com> writes:
>
>> Dear all
>>
>> Mail source (pop :server hondalaw.sakura.ne.jp :user
>> hirotaka@hondalaw.com :leave 64 :port 995 :authentication apop)
>> failed: (wrong-type-argument integer-or-marker-p nil)
> That error is coming from somewhere in the code below, which could
> actually be quite a bit of code since it is calling out to
> `nnmail-split-incoming' which is a fairly large function. Have you
> changed anything configuration related to mail splitting recently?
>
> One thing you can try, to get a better traceback, is find this code in
> the source file (nnmail.el:1828) and change the `condition-case' to
> `condition-case-unless-debug'. Then M-x toggle-debug-on-error, and run
> the code again, and paste the traceback you get from that.
>
> (condition-case cond
>     (mail-source-fetch
>      source
>      (let ((smsym (intern (format "%s-save-mail" method)))
> 	   (ansym (intern (format "%s-active-number" method)))
> 	   (src source))
>        (lambda (file orig-file)
> 	 (nnmail-split-incoming
> 	  file smsym
> 	  spool-func
> 	  (or in-group
> 	      (if (equal file orig-file)
> 		  nil
> 		(nnmail-get-split-group orig-file
> 					src)))
> 	  ansym))))
>   ((error quit)
>    (message "Mail source %s failed: %s" source cond)
>    0))
>
>



  reply	other threads:[~2021-05-27 16:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21 16:15 spam-split of spam.el with bsfilter Hirotaka Honda
2020-09-22  1:55 ` 黃炳熙
2020-09-22  2:09   ` Emanuel Berg
2020-09-23  0:48     ` 黃炳熙
2020-09-23  1:01       ` Emanuel Berg
2020-09-23  2:30         ` 黃炳熙
2021-04-10 10:50 ` Hirotaka Honda
2021-04-10 13:30   ` Emanuel Berg
2021-04-11 11:10     ` Hirotaka Honda
2021-04-11 11:16       ` Emanuel Berg
2021-05-27 13:48       ` Mail source failed, wrong-type-argument integer-or-marker-p nil Hirotaka Honda
2021-05-27 15:59         ` Eric Abrahamsen
2021-05-27 16:49           ` Hirotaka Honda [this message]
2021-05-27 16:53             ` Eric Abrahamsen
2021-05-27 21:30               ` Hirotaka Honda
2021-05-28 17:29                 ` Eric Abrahamsen
2021-05-28  2:40           ` Pankaj Jangid
2021-05-28 23:05             ` Andy Moreton

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=67b31f60-16fa-16f7-ee0c-3e97785c2dba@hondalaw.com \
    --to=hirotaka@hondalaw.com \
    --cc=ding@gnus.org \
    --cc=eric@ericabrahamsen.net \
    /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).