Refer to Administrator Help, we can restrict users from sending mail to a group by editing the reader fields for a Group document.
If user try to send mail to that group, user will receive delivery failure from router. But if user resend the delivery failure, the mail can deliver to all member of group.
Is this a bug ??
Regards,
Joe
Subject: Hey Joe… re: Restrict users from sending mail to a groupis not working !
You at work on your next disc? I’ve been trying to get in touch with you. Scott & Ken from The Crystal Method want to work with you. Have Mick put in a call to 3AM management and work something out. You know that would be a great collaboration.
P.S: didn’t know you were into Domino administration.
Subject: Restrict users from sending mail to a groupis not working !
Have you created the group as a “mulit purpose” group or a “access control list only” group ?You must use the “access control list only” category to avoid mails to the group.
Alexandre
Subject: No, it’s a bug alright…
That’s not the point. The point is to have a group where only certain people can send mail to.It should be a multi-purpose (or mail) group.
I’ve tried it out, and indeed, the first time you get a delivery failure (not authorized …), but if you resend, the message is delivered.
Shouldn’t happen, but I think you could set up a mailrule to catch these ‘second tries’.
Subject: RE: No, it’s a bug alright…
Thanks Tom …I try to catch ‘second tries’ using mailrule and it can working properly.
My mailrule :
“When To or Cc contains All don’t accept message Except when sender contains Admin Notes”
We have groups : All Users, All Branch Users, etc and only Admin Notes can send to these groups.
But if Admin Notes send to one of these groups (for example : All Branch Users), and user who member of All Branch Users group try to “reply to all”, this user still can send to this group but will receive a lot of delivery failure report depend on the number of member of that group.
Hmmm … Do you have an experience too ?
Subject: RE: No, it’s a bug alright…
I didn’t try it out further, but again a workaround could be the mailrule.
I didn’t check the support site, so I don’t know if this is a reported bug, but it may be worth while to launch a support call…
Thanks for the advice, though.
cheers,
Tom
Subject: Why not using Extended ACL?
I think the most appropriate should be to use the extended ACL. Have you considered this? In some cases it might be the good way…
Subject: RE: Why not using Extended ACL?
I’ve already considered this feature, but I never try it because if I refer to Administrator Help, I get the sentence as below:
“Server processes such as the Router task do not enforce extended ACL restrictions. However, in the case of the Router task specifically, you can prevent some users from sending mail to a group by editing the Readers field for the group and including only the names of users you want to allow to send mail to the group. When users omitted from the Readers field attempt to send mail to the group, the Router won’t deliver the mail.”
By the way, thank you for info.