Conference iosg::all-in-1_v30

� I have been a resident at my current site for about nine months.  Since I have 
� been here the SUBSCRIBERS: distribution list doesn't work.   

	Well, then I'd leave if I were you!  8^)  8^)

	Actually, it simply appears that someone has created an alternate
distribution list called SUBSCRIBERS:  All you need to do is to delete this
distribution list from the system, and the default SUBSCRIBERS: (i.e., "All
ALL-IN-1 users on the system") will operate just fine.

	Go to the Administrator's menu and use the MDL (Manage Distribution
Lists) option, select the SUBSCRIBERS: distribution list, and delete it.

	F

Reply .1 gives the correct answer if the bogus "SUBSCRIBERS:" has been created
as a system distribution list.

However, it is also possible that the bogus "SUBSCRIBERS:" is:
    - a personal distribution list in your (presumably the MANAGER) account
    - a profile record
    - a NETWORK record
    - a nickname in your (MANAGER?) account

You'll need to check all these if the suggestion in .1 doesn't fix it.

Scott

I had tried everything the last two notes had suggested before I wrote the note 
into the notes file.

It is not a user, in the profile, a network record, or a personal list created 
by the manager account.  I can't bring it up through ADM MDL to delete it.  
Nothing seems to work.  I can't get rid of it.

Perri

OK, next step:

Do all users see the bogus SUBSCRIBERS:, or only a few, or only one?

What happens if you send a mail to the bogus SUBSCRIBERS: (ie does it get
delivered, and if so who receives it?)

In .3 you don't say whether you've checked your nicknames file...

Also, are you using DDS?  If so, is it an entry in DDS?

Scott

Here is some more additional information for you, we are confused also.

1.  It is not a nickname
2.  It is not listed in DDS
3.  All other users see the same thing
4.  If you send mail to the list nothing happens, it says it has been sent, but 
    it goes to ???
5.  We have tried A1/nocustom, that doesn't work
6.  We tried doing a trace, that show that it works, but nothing 
7.  It does however work on our QA system (the old resident didn't screw that 
    one up)
8.  It is not listed in the network profile
9.  When I create a new distribution list called TEST: and do a GOLD M, and 
    select option SAD, I can select the bogus distribution list.  I can read it 
    but all that is there is SUBSCRIBERS:, no full name, department, phone 
    number or job title.  If you send mail to the bogus subscribers you don't 
    get a memo from the postmaster saying it can't be delivered.


Perri

Is there an entry in OA$DATA:PENDING.DAT for a user called SUBSCRIBERS?

either search the file for SUBSCRIBERS (no :) or read it with DCL using the
key "MAIL SUBSCRIBERS". If there is there then that is where the mail is 
going and ALL-IN-1 thinks that there is a user called SUBSCRIBERS, why it 
may be thinking that if there is no PROFILE entry is a mystery to me.

Of course if there is no PENDING entry then the whole thing is a mystery 8-)

If your customer has a contract call the CSC and a mail specialist will help
you track it down.

HTH

Terry

We finally found it.

There is an entry in PENDING.

We pulled up form profil by doing a <form profil,  when we did a list of 
subscribers there was nothing.  We finally went to the master files and pulled 
up profile that way and found the entry.  I don't know why it would be listed in 
the master profile file but not when you did <form profil.

Thanks for all the suggestions!

perri

    Because the profile filters out dist lists when you are looking at
    users.                                                  
          
    Winton

    
    I have two weird problems:
    
    1.  If I send to SUBSCRIBERS: first_class, the message is sent, if I send
    	the message SECOND_CLASS it goes off and "sends" it, but then I
    	get a message delivery reporting saying that I have no priv to send to
        SUBSCIBERS:.  My account has full priv's enabled
    
    2.	A second user has SUBSCR and SUP set to "Y".  She claims that mail
    	sent to SUBSCRIBERS @A1 @node is working but SUBSCRIBERS: isn't.
    
    Help?
    
    
    "jackin' the house", Bob
    

    
    	I can guess at (1). When you send it SECOND_CLASS, the sender
    	probably checks the wrong account and looks at the ALLIN1 account
    	maybe?
    
    Regards,
    Paul

   First, SUBSCRIBERS: sent First Class go immediately, in the context of
   the sender (I assume you were in the Manager account); anything sent
   Second Class goes in the context of the PostMaster account (Sender if
   your system is running a split Fetcher/Sender setup).  Go to SM MUA and
   select the A1SENDER (or POSTMASTER or whatever you named it) account
   and make sure that the SUBSCR privilege is enabled for this account.

   Secondly, check the Fetcher account on the other node that your user is
   sending to (same reason as above).

   Hthy,

	Ron

    I believe that ROn's solution was the one.  Fetcher and Sender had
    SUBSCR = "N"
    
    Thank you people.
    "jackin' the house", Bob