Subject: Possible addressbook bug, and some other Qs

From: [email-masked] (Milt Epstein)
Date: 3 Apr 95 21:45:58 GMT

I sent this report to the pine-bugs address, but got back a response
that (among other things) suggested I try the pine newsgroup for a
faster response, so I am posting it here.

I had a problem with an entry in the global address book.  I'm not
sure it's a bug, but I couldn't find any specific problems.

What happened is that I had an entry that had some number of levels of
nested aliases/nicknames (i.e. other address book entries).
Specifically, there was one entry that had six levels, including the
very top and bottom levels, although I'm not sure that's significant.

When I composed a message and gave the top level nickname as the To:,
it was read in OK, but there was a problem with the format.  When I
moved down to the next header line, it indicated a problem with the
contents of the To: line; the message was something like: "Junk at end
of To: line: '> .......'".  Looking back at the To: line, it looked
like an address had been wrapped/split at an inappropriate place (in
the middle of the domain name) and an end-of-line comma inserted there
a bit before the address it seemed to be complaining about.

The same problem occurred when I tried the next highest level
nickname, but things were fine when I moved down another level.  The
problem also disappeared when I changed the order of the
nicknames/names in the second highest level nickname -- the problem
occurred when I had the nickname that continued the long chain listed
first, but things were OK when I moved a regular name (i.e. a regular
username, not a nickname) to the front of the list.

Does this make sense?  Sorry I had to describe it instead of sending
the actual entries, but I'd rather not send those unless absolutely
necessary.

Besides this problem, I had a few other questions related to
addressbook nicknames and how they appear in the To: line.

1. They appear including the "fullname" description of the nickname
(the second field of the addressbook entry).  Is there a way to set it
up so that this does not appear?  For such deeply nested nicknames,
often the "fullname" isn't really meaningful (it's likely just some
arbitrarily chosen grouping name).

2. Sometimes the number of actual addresses in a nickname can be
fairly high, and you end up with a very long To: line.  Is there a way
to set it up so that the addresses are not shown (sort of like a Bcc:,
or "address list suppressed" type of thing), or that only the nickname
(or its corresponding fullname) is shown?

Thanks for your help.

-- 
Milt Epstein
Visiting Research Programmer    National Animal Poison Control Center (NAPCC)
[email-masked]            College of Veterinary Medicine (CVM)
(or [email-masked])      University of Illinois at Urbana-Champaign (UIUC)

---

From: Steve Hubert <[email-masked]>
Date: Fri, 7 Apr 1995 12:25:42 -0700 (PDT)

> a bit before the address it seemed to be complaining about.

Sounds like it might be a bug, all right.  I'm not able to figure out 
what the problem might be without a specific example to work with.  If 
you'd like to send me the addressbook and tell me which nicknames work 
and which don't, I'd be happy to look at it.  Or, if you can cook up a 
fake addressbook with this problem, then you wouldn't have to send the 
real one.
 
> arbitrarily chosen grouping name).

Not in 3.91.  In 3.92 you will be able to have a blank fullname field for 
any entry and then it will do what you want, I think.
 
> (or its corresponding fullname) is shown?

You can use the Bcc line for that.  When you're in the composer, type ^R 
while your cursor is in the headers and then you will see the Bcc line.
 -- 
> (or [email-masked])      University of Illinois at Urbana-Champaign (UIUC)

Thanks,
Steve Hubert <[email-masked]>
Networks and Distributed Computing, Univ. of Washington, Seattle