When I start reading the following news article:
Path:
nntp.uio.no!trane.uninett.no!sunic!EU.net!sun4nl!news.nic.surfnet.nl!highway.LeidenUniv.nl!rulxho!RAAIJMAKERS
From: raaijmakers@rulxho ([EMAIL PROTECTED])
Newsgroups: comp.text.tex
Subject: PicTeX for Windows?
Date: 29 Jun 1994 13:12:49 GMT
Organization: Institute for Dutch Lexicology
Lines: 2
Message-ID: <2urs0h$[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
NNTP-Posting-Host: rulxho.leidenuniv.nl
I'm looking for PicTeX for Windows.
Does it exist?
I get the following backtrace:
Signalling: (error "mail-extr returned \"\" as name")
signal(error ("mail-extr returned \"\" as name"))
error("mail-extr returned \"\" as name")
bbdb-annotate-message-sender("raaijmakers@rulxho ([EMAIL PROTECTED])"
t nil nil)
bbdb/gnus-update-record()
funcall(bbdb/gnus-update-record)
mapcar(funcall (bbdb/gnus-update-record (lambda nil (if ... ...))))
run-hooks(gnus-article-prepare-hook)
gnus-article-prepare(48297 nil)
gnus-summary-display-article(48297)
gnus-summary-next-page(nil)
call-interactively(gnus-summary-next-page)
Looking at the source for bbdb-annotate-message-sender, I find that
the first few lines of the defun are:
(let* ((data (mail-extract-address-components from))
(name (car data))
(net (car (cdr data))))
(if (equal name net) (setq name nil))
(bbdb-debug
(if (equal name "") (error "mail-extr returned \"\" as name"))
(if (equal net "") (error "mail-extr returned \"\" as net")))
So it seems reasonable to guess that mail-extract-address-components
finds out that the "real name" part of the address is a substring of
the mail-address, and thus returns an empty string as the real name,
which makes bbdb-annotate-sender enter debugging mode. (I do not feel
like trying to read and understand the source code of mail-extr,
therefore this is only a guess.)
Addresses like this are, of course, pathological. However, the way the
net is expanding, I think we must assume that they will continue to
crop up once in a while for the foreseeable future.
If my guess is correct: Does someone know a way to make BBDB continue
blithely in a situation like this, or would any such "solution" break
some important piece of functionality.
-- H�vard Fosseng
[EMAIL PROTECTED]
