Re: bouncehandler-unsubscribe shell-hook

Alex Teslik wrote:
> 4) bounces pass a limit, and user is auto-unsubscribed
>>>   
>>>       
>> If delivery is disabled, clearly there won't be bounces.  If a 
>> subscriber takes the trouble to re-enable delivery, why would you 
>> want to count the preceding bounces against that user in the bounce rules?
>>
>>     
>  I don't really have very many options for users who don't add counter-weight rules to
> their over-sensitive spam filtering for lists they've signed up for, other
> than to warn them and then unsubscribe them if it continues.
>   
You could use two bounce rules:  a remove-probe rule that sends a probe 
message (which you could customize) after a certain number of bounces 
have been received, and a remove-noprobe rule which unsubscribes the 
address if the mail continues to be undelivered.

Changing the code to implement a "nomail" bounce rule is problematic for 
reasons I mentioned earlier.

> In my opinion, it would be more
> clear if it were specifically mentioned in the shell-hook help that the
> scripts are not included, they are only called - and will only be executed if
> you put a script there that is named appropriately.
>
>   
The help file says:

 To make use of a shell hook,place a script or program with the
 name of the shell hook in the "scripts" directory where Majordomo is 
installed.


How would you reword that?

Michael