[Mailman-Users] Munged addresses

[Robert Morse]

On 10/18/05 8:12 AM, "Mark Sapiro" <msapiro at value.net> wrote:

> Robert Morse wrote:
> 
>> I have a list running on our server that when you ask for the entire list
>> the firse 25 or so listed are munged. Here's an example
>> 
>>    
>> #PreReg442-1212nstreufert at earthlink.netfrasher
> hsustudent668-1768starif
>> anl
> 
> 
> Is this on the http://www.example.com/mailman/roster/listname page or
> somewhere else? 
I get a list of munged addresses which are not on the hidden.


>What do you see on
> http://www.example.com/mailman/admin/listname/members?
I get the list of munged addresses.

>What do you get
> in reply to an e-mail 'who' command?

Not sure how to do that.
> 
> Is this 'stock' Mailman, or does this list use a custom MemberAdaptor?

Stock as far as I know. Never heard of MemberAdaptor. It's a cpanel instal
of Mailman.
> 
> Are you using a modified roster.html template?

No.
> 
> 
>> You can see that there is an actual email address in there, which when
>> searched on returns a valid address. I would like to get rid of these munged
>> addresses, but when I check the box to unsubscribe them, I get a message
>> back that says the subscriber is not listed. Some are much longer, some ae
>> shorter. Any way I can get rid of these things?
> 
> 
> Based the fact that part of what's there looks like tel #'s,
> student/staff classification, ..., I'm guessing this list uses a
> custom LDAP, MySQL, etc. MemberAdaptor and something in this
> MemberAdaptor's getRegularMemberKeys(() and/or getDigestMemberKeys()
> methods is returning the garbled data.



-- 
Bob Morse
Morse Media
http://www.morsemedia.net
707-444-9566