> > Perhaps for consistency with header related matchers and mailets your > > classes should be named SetAttribute, HasAttribute etc. instead of > > SetMailAttribute, HasMailAttribute etc, as it is clear that a <mailet> > > entry deals with Mail objects. > > > > What do you think? > > The reason for this naming convention is, that I was afraid users > could think > that a SetAttribute would set the attribute on the Mailet instance (the > MailetContext) and not on the Mail instance, mainly because > MailetContext has > had attributes longer.
You are right. Vincenzo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
