Matt Sergeant escribió:
So the next release I consider to be a fairly major step - we've got
async/smtp-forward and async tls working. That's most of the
showstoppers against using async in production.
So what's missing and what would you like to see before the next release?
(obviously not limited to -async stuff)
Matt.
Proposal 1:
One good thing would be to "organize" the plugins, having some central
repository for them (there is the Wiki, but I'm sure there are a lot of
missing plugins). Also, if they use blocking I/O should be tagged in
some way so that its easy to know if they will work well in async.
I understand that it's not a must-have for a release, and that it can be
done as a side-project, but it would help to reduce the entry level to qp...
Proposal 2:
We have a POP-before-SMTP plugin for qpsmtpd (yeah... the one that
connected via DBI that had problems with the TLS plugin). Don't look bad
at me! I know POP before SMTP is bad, but we need it for compatibility
:p... The thing is that we wanted to add the header that is added when
you use an auth plugin (in SMTP.pm), but it looks like this only attends
to plugins that run in AUTH hooks :(
(smtp-auth username $self->{_auth_user}, mechanism $self->{_auth_mechanism})
I haven't found a decent way to set the parameters necessary for the
$authheader from a plugin that is not called in an AUTH hook? I think
that SMTP.pm needs to be changed to permit this behaviour... because
there are ways of authorizing relay that are not SMTP AUTH (relayclient
file, POP-before-SMTP for example). Maybe just relying on a transaction
note would suffice.
I know you can hook into the recieved_line... and override the
authheader, but it looks more elegant to do it from the SMTP.pm
Proposal 3:
There are a couple of hard-coded references to develooper in the barelf
responses:
$self->respond(421, "See http://smtpd.develooper.com/barelf.html";)
Maybe users should able to configure these responses...
Proposal 4:
I'd like to see a qmail-queue async plugin. I'd put myself to the task,
but by async programming skills tend to null for the moment.
Jose Luis Martinez
[EMAIL PROTECTED]
