[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | *OLD* ALL-IN-1 (tm) Support Conference |
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
| Moderator: | IOSG::PYE |
|
| Created: | Thu Jan 30 1992 |
| Last Modified: | Tue Jan 23 1996 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4343 |
| Total number of notes: | 18308 |
3615.0. "SUBSCR and SUP when using DISTRIBUTION lists" by BACHUS::BERVOETS (Luc Bervoets - CSC Brussels alive and kicking) Thu Dec 02 1993 08:11
Hallo,
I have the following problem with the SUBSCR and SUP priv.
When a users doesn't have the SUBSCR priv he can't send to SUBSCRIBERS:
nor he can't send to SUBSCRIBERS:@remote_node.
Normally you need also the SUP priv for sending to REMOT SUBSCRIBERS:.
But when there is SYSTEM Diostribution list ,which contains the following
entries SUBSCRIBERS: and SUBSCRIBERS:@remote_node.
When a user sends now a mail using this distribution list and he doesn't
have the priv SUBSCR, but he has SUP priv.
He receives a message from the postmaster on the local system that he
can't send to SUBSCRIBERS: on the local system. The mail arrives well on
the remote system.
When sending with the same distribution , but now the user doesn't have
SUBSCR nor SUP priv.
He receives the same message from POSTMASTER on local system that he
can't send to the local SUBSCRIBERS: , but the mail stil arrives on the
remote system.
When not using a distribution list , but typing it in manually and you
don't have the priv SUBSCR the system responds immediately that you
don't have the priv for sending to SUBSCRIBERS:
Does anyone have a sollution for this problem/bug or do I have to open a CLD
for it.
Regards,
Luc Bervoets - MCS Belgium.
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3615.5 | Part suggestion/ Part restriction | IOSG::COTTINGHAM | | Fri Dec 03 1993 17:08 | 15 |
| I believe this is a known problem.
I assume the Distribution List is a System Dist List as they should not
be able to create one themselves.
The problem of no instant rejection when expanding the distribution
list is expected behaviour. The problem of The remote not being rejected
(and indeed Second Class) SUBSCRIBER: mail being delivered by the Sender
is a Bug. We are aware of this problem but an IPMT (Severity 3!) report
should be submitted.
I would suggest a workaround is that System Distribution Lists should
not be created to contain SUBSCRIBERS: or SUBSCRIBER:@A1
Regards
Alan
|