I have a few subscribes on some of our lists whose ISPs use
Securence.com. It seems that mail they send is routed through
Securence, given an ID then continued to the destination. The problem
is that Listserv is interpreting the Securence ID embedded in the
header as the originating address and rejects them as not subscribed.

[log in to unmask]

Anyone have experience with this type of problem. I'm sure the problem
lies with Securence, not Listserv.


------------
Regards,
Randy Klumph
[log in to unmask]
The National Consortium on Deaf-Blindness
The Teaching Research Institute
345 N Monmouth Ave
Monmouth, OR 97361