On Tue, 16 Oct 2001, Danny Angus wrote: > [so say Oki's attachment stuff was in Forward and it would only be used if > configured to, > and Forward might also contain code forward a copy without ghosting the > original etc etc.]
IMHO, forward + ghosting = forward forward - ghosting = notify (I see, bad math; anyway, I think the semantics is pretty understandable.) > Or, should we be keeping Mailets small and simple, so we have two or three > seperate ForwardXxx classes for slightly different tasks. I like this one better. But ideally, the mailets descend from a common ancestor, so that you'd get consistent configuration elements; ie: do you want it to have "<forwardto>" or "<receivingAddress>"? Is "<sendingAddress>" better than "<from>"? > I only ask 'cos the mailets in the dist. will be bound to be used as > reference examples and I wondered what anyones views of the pros and cons > were. That's why I wanted to have a "contrib" directory in the CVS quite a long ago. Oki --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
