Re: bouncehandler-unsubscribe shell-hook
"Alex Teslik" <[email protected]> Fri, 3 Nov 2006 19:52:28 -0800
| Newsgroups | gmane.mail.majordomo.majordomo2.devel |
|---|---|
| Message-ID | <[email protected]> |
Hi Michael, Thanks for the reply. I think you may have misunderstood what I meant. The scenario I am trying to create is: 1) user subscribes to receive messages 2) messages to subscribed user bounce 3) bounces hit a limit and shell-hook sets the user to "no messages" and issues a warning to user to fix the bounce problem with their account 4) bounces pass a limit, and user is auto-unsubscribed remove-consult involves consult, which is undesirable. I'm confused about the shell hooks being included. The help says that majordomo uses them, but if they aren't included I guess mj does not use them? In any event, is there an example shell-hook somewhere that could get me started? Thanks! Alex On Fri, 03 Nov 2006 13:46:48 -0800, Michael Yount wrote > Alex Teslik wrote: > > Hello, > > > > I wanted to create a shell hook named bouncehandler-nomessagesandwarn, and I > > was hoping to start by copying and then hacking bouncehandler-unsubscribe... > > but I can't find it. > Shell hooks are intended to be site-specific, so there aren't any > included with Mj2. > > > P.S.- if there is a non-shell hook way to do a bouncehandler-nomessagesandwarn > > (where the users settings are set to "no messages" and they are warned that > > they will soon be unsubscribed) please feel free to push me in the right > > direction. Thanks! > If a subscriber's delivery class is set to "nomail," any > unsubscription will need to be done by the list administrators. How > will the administrators be able to distinguish subscribers whose > delivery was suspended due to bounces from subscribers who have > chosen to suspend delivery? > > Why is the remove-consult bounce rules action inadequate for your needs? > > Michael