[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference abbott::teamlinks_windows

Title:TeamLinks for Windows
Notice:Kit and ECO locations: See replies to note 8.o note 8.
Moderator:ORION::chayna.zko.dec.com::tamara::eppesAN
Created:Mon Aug 28 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2238
Total number of notes:9650

1874.0. "TeamLinks users can mail SUBSCRIBERS:!" by WOTVAX::BELL (Martin Bell @BBP) Tue Dec 17 1996 11:19

T.RTitleUserPersonal
Name
DateLines
1874.1MASS10::GERRYOne of those awfully nice AlphaStudio peopleMon Dec 23 1996 09:4810
1874.2XANADU::flymht.zko.dec.com::TAMARA::STJEANBob St.JeanMon Dec 23 1996 15:296
1874.3Any more thoughts or progress?WOTVAX::rasmodem30.reo.dec.com::warbly::bellMartin Bell @BBPTue Mar 25 1997 06:2223
Note: This was QARed as 03266 and PRTed as 11-3-675.

Are there any more thoughts on this problem?

The reply in the PRT database by "jal" didn't seem to offer much
hope!

I don't know the technical details of whether TeamLinks has the
equivalent of the ALL-IN-1 symbol OA$PROFIL_PRVSUB (or whatever),
but it should be able to get the information via AIDA (along with
other details), and check for the SUBSCRIBERS string in addresses
(if ALL-IN-1 is the mail server).

This is a big issue with my customer, as they plan to have 2000
TeamLinks users on a single cluster, so SUBSCRIBERS message will
be _more_ than an inconvenience if they can be sent by "unprivileged"
users, whether by accident or intentionally.

What do other users think?

Cheers,

mb
1874.4WOTVAX::rasmodem3.reo.dec.com::swat01::bellMartin Bell @BBPTue May 20 1997 07:445
Still no more thoughts on this on???

Cheers

Martin Bell @BBP
1874.5XANADU::cascobay.zko.dec.com::TAMARA::STJEANBob St.JeanTue May 20 1997 11:427
Hi Martin,

I will see if we can get a official response on this, both here and
in the PTRs/QARs.

Bob

1874.6XANADU::CUMMINGSJerry Cummings, TeamLinksTue May 20 1997 16:286
    Not an official repsonse, but given our current understanding of the
    problem, it seems like it should be the server enforcing this rule
    rather than the client. I don't think working around this would be a
    simple tweak to TeamLinks, but quite a change.
    
    Jerry