[Alpine-info] LCC displays first member in To: field

[M.RossARR]

> On Thu, 22 Oct 2009, J. O'Connell wrote:



> ... problems with Alpine's 'LCC' address function.


The problem is not new to Alpine, Pine(4.64) suffers the problem, so
it must be a carry through from the old code. I suspect it was not
detected before or dealt with anyway, due to how it seems to happen.
If it is truly a bug as it seems, possibly the Realpine guys will
eventually fix it!


> names having non-Alphanumeric characters (including: periods, commas,

> braces, aphostrophes, dashes; basically non-[0-9a-zA-Z] characters)

> being concatenated with Descriptive member names (note the [.(-)] in the

> Group description and the apostrophe in the membername (O'Neill)).  It

> should also be noted that it happens when the membernames are listed in

> 'Lastname, comma, Firstname' format in the descriptive name field, which

> gets re-arranged by Alpine to the 'Firstname Lastname' format.


I find it happens for any named Group list I use. Neither the Group
list name, nor recipient name, nor punctuation seem to matter. All
Groups I use will trigger the problem, I use no flopped names, I use
no non-alpha characters. I don't see any relationship to that part,
but you may be doing something I never tried.

For me, the problem seems to be triggered by any change made to the
Group list in the Lcc entry while in edit mode.

To quickly demonstrate: load a Group list into the Lcc entry, then
immediately delete one of the Lcc entries (one of the Group list
recipients), then move the cursor off all the Lcc header entries by
hitting enter or cursor keys - move to another header entry; - see
the To header entry picks up the first recipient name of the Group
list, & the To Group list name is updated or changed to the Group
list name if it was different!  To is now a defective entry.

Manual or in Role it does not matter. Only an edit of the Group list
in the Lcc header entry seems to matter.

I use Lcc often as part of using a Role to forward msgs, where the
Role Lcc is loaded with a Group list name, & where the To header
entry is loaded with "undisclosed:  ;"(I do not want the Group list
name in the To header entry, just "undisclosed - because I manually
add Bcc entries as well").

That normally works fine, never does the To header entry corrupt
with Group list name & first receipient name, until I attempt to
make a manual change to the Lcc entry Group list before send. If I
add another name to the Lcc entry I get the same corrupted To, & yet
if I add another name to the Bcc entry all is well. Just the Lcc
header entry being changed triggers this problem for me.

I do not see this problem otherwise!

-- 
The Best To You & Yours,
M. Ross All Rights Reserved
mrossarr at vfemail.net
subj: tellross

---
The word "tyranny" is derived from the Latin "tyrannus," which
translates to "illegitimate ruler." Like AKA Barry Soetoro?
<http://www.wnd.com:80/index.php?fa=PAGE.view&pageId=105764>
Orly Taitz website: <http://www.drorly.blogspot.com/>

---end-of-message---