Matt Sergeant wrote:
If we start adding all this stuff to Plugin.pm it has the possibility of
getting very bloated - there's so much we could just add in there for
convenience. I kind of saw the DSN stuff as a helper class, something
not required but useful, hence the externalisation.
The counter argument being that we *should* be returning the DSN codes
and making it easier for plugin authors to DTRT is a side benefit of
that larger goal.
How about we split change Qpsmtpd::DSN so that any one plugin must load
it, but the methods are added to the Qpsmtpd::Plugin class, rather than
the Qpsmtpd::DSN class? That way, the lean mean spam-eating machine
doesn't need to load it ever, but the ordinary slow and steady MTA gets
the methods in easy to call ways. A true helper class.
John
- Re: Support for RFC 1893 - Enhanced Mail System Status Codes John Peacock
-