> I think it was better the first time. The two behaviors are > isomorphic except in returning one different value for one different > input. If it required a backwards-incomptible change in the config > syntax it'd be another matter, but this seems a natural extension to > what the plugin did before which contradicts no other extensions I > can anticipate.
Yes, but it complicates an existing very simple plugin. A compromise is still two files - with an additional argument to the plugins file for DENY or DENYHARD. > It's also fits well with sendmail's /etc/mail/access file, which (though I > dont' care for the conflation in lookup key) enables particular entries to > trigger various failure codes/messages, enable relaying, etc. qpsmtpd != sendmail. It's suddenly not badrcptto if it has the power of access. Not that that functionality is bad, but its scope creep. If thats the functionality you need, then sounds like someone should create a 'sendmailaccess' plugin. > Not crazy about the bang as an errorcode selector, though. If a > line in badrcptto is doing to trigger a DENYHARD, it may as well say > DENYHARD (or DENY or DISCONNECT or whatever) and eliminate the > uncertainty. If using !, I'd put it at the beginning of the line to keep it visible. -R
