Gnus development mailing list
 help / color / mirror / Atom feed
From: Hirotaka Honda <hirotaka@hondalaw.com>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: ding@gnus.org
Subject: Re: (wrong-type-argument number-or-marker-p nil) error at gnus startup
Date: Thu, 03 Jun 2021 08:44:26 +0900	[thread overview]
Message-ID: <m2r1hj96hx.fsf@hondalaw.com> (raw)
In-Reply-To: <m2zgw8bqx8.fsf@hondalaw.com> (Hirotaka Honda's message of "Wed, 02 Jun 2021 17:40:19 +0900")

Dear all

What a cool typo it was. Correct is:
    never happened again.

Hirotaka

Hirotaka Honda <hirotaka@hondalaw.com> writes:

> Dear all
>
> After I commented out gnus-registry as the following, any errors (or the
> same errors) happened again.
>
> ;; (gnus-registry-initialize)
> ;; (setq
> ;;  gnus-registry-split-strategy 'majority
> ;;  gnus-registry-ignored-groups '(
> ;; 								("nntp" t)
> ;; 								("nnrss" t)
> ;; 								("mail.spam" t)
> ;; 								("archive" t)
> ;; 								("Send-Mail" t))
> ;; gnus-registry-track-extra nil
> ;; gnus-registry-max-entries 500000)
>
> ;; (setq spam-log-to-registry t)
>
> Hirotaka Honda
>
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> On 06/01/21 22:30 PM, Hirotaka Honda wrote:
>>> Dear all
>>>
>>> I am not certian what is happening, though the most dubious mail has
>>> the email header like this:
>>>
>>> X-From-Line: - Fri May 28 HH:MM:SS 2021 [I masked the time]
>>> X-Mozilla-Status: 0001
>>> X-Mozilla-Status2: 00000000
>>> ...
>>> From: =?iso-2022-jp?B?[mask]?= <[mask]@outlook.jp>
>>> To: =?utf-8?B?[mask]?=
>>> =?utf-8?B?[mask]?= <[mask]@[mask]>
>>> Cc: =?iso-2022-jp?B?[mask]?=
>>> =?iso-2022-jp?B?[mask]=?= <[mask]@[mask]>,
>>> "[mask]@[mask]" <[mask]@[mask]>
>>> ...
>>> X-Mailer: JavaMail
>>>
>>> Does the Gnus expect that To field and Cc field are coded in different ways?
>>
>> That shouldn't be a problem, the decoding process is called once for
>> each header, and each time it detects the coding over again.
>>
>> My only uncertainty is, should the headers somehow be already decoded at
>> this point (during registry operation), and if so and we're just missing
>> a decode call, why hasn't this become an issue in the past? I suspect we
>> just need to add decoding to the process, but it still makes me suspicious.


  parent reply	other threads:[~2021-06-02 23:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-27  7:58 Julien Cubizolles
2021-05-28  2:36 ` Pankaj Jangid
2021-05-28 17:11   ` Eric Abrahamsen
     [not found]     ` <977D30E3-06DB-46F7-BDC9-933E591A5E78@hondalaw.com>
     [not found]       ` <87tumhsiw6.fsf@ericabrahamsen.net>
2021-06-02  8:40         ` Hirotaka Honda
2021-06-02 16:09           ` Eric Abrahamsen
2021-06-02 23:44           ` Hirotaka Honda [this message]
2021-06-02 23:54             ` Eric Abrahamsen
2021-06-02 21:31     ` Julien Cubizolles

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=m2r1hj96hx.fsf@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).