Re: Question about how to run a deny in access_rules.

Michael Yount <[email protected]> Tue, 13 Oct 2009 15:01:34 -0700
Newsgroups gmane.mail.majordomo.majordomo2.devel
Message-ID <[email protected]>
If the "ackdeny" flag is set for the author, and the 
"ack_attach_original" setting is configured appropriately, the posted 
message will be attached to the denial acknowledgment.

There is no way to attach the posted message to the "inform" notice, but 
you could use the forward action in the access rule, e.g.,
  [email protected], deny, replyfile=myfilename
to forward the message to the owner separately.

(Test these suggestions to make sure they work as you expect.)

Michael

Steven W. Orr wrote:
> On 10/04/09 00:50, quoth Steven W. Orr:
>   
>> On 09/30/09 22:42, quoth Michael Yount:
>>     
>>> Use a rule in the inform configuration setting, e.g.,
>>>  post | fail | inform
>>>
>>> Michael
>>>
>>> Steven W. Orr wrote:
>>>       
>>>> I have a few situations in my lists when I want the person to be
>>>> automatically
>>>> denied, but I would also like to be informed on when it happens.
>>>> Currently, I
>>>> see no way to do this.
>>>>
>>>> For example, I currently have a number of these constructs in my
>>>> access_rules:
>>>>
>>>> post
>>>> deny, replyfile=MultiTo2
>>>> $admin_bothlist2 >= 2
>>>>
>>>> The person who sends the message is getting the rejection, but is
>>>> there some
>>>> way that I as the list owner can get a copy when this happens?
>>>>
>>>> Thanks.
>>>>
>>>>   
>>>>         
>> Ok. One more followup. I'm getting the inform that I wanted but I'd also like
>> to both see the reply contain the content that caused the deny and for the
>> poster to also see it.
>>
>> Doable?
>>
>>
>>     
>
>
> Sorry to be a pain, but this is a piece of functionality that I really need.
> Is there anything that I can do, or even a trick, a hack, a tweak, anything,
> that will cause the replyfile to contain the text that was sent? I reallly
> need to see both the headers and the content. The post | fail| inform got me
> halfway there.
>
>
>