Skip Menu |

This queue is for tickets about the Sendmail-PMilter CPAN distribution.

Report information
The Basics
Id: 51058
Status: resolved
Priority: 0/
Queue: Sendmail-PMilter

People
Owner: ZUMMO [...] cpan.org
Requestors: ZUMMO [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Important
Broken in: 0.97
Fixed in: 1.00



Subject: missing data command
SMIC_DATA is not implemented, postfix will fail on this. the following patch partially fixes the bug: --- /usr/share/perl5/Sendmail/PMilter/Context.pm~ 2009-11-03 00:45:28.000000000 +0100 +++ /usr/share/perl5/Sendmail/PMilter/Context.pm 2009-11-03 00:45:28.000000000 +0100 @@ -284,6 +284,8 @@ $this->call_hooks('envrcpt', @$envrcpt); delete $this->{symbols}{&SMFIC_RCPT}; + } elsif ($cmd eq SMFIC_DATA) { + $this->call_hooks('data'); } elsif ($cmd eq SMFIC_QUIT) { last; # that's all, folks!
Would you like to take over maintenance of this distribution?
On Fri Nov 06 04:06:27 2009, DCANTRELL wrote: Show quoted text
> Would you like to take over maintenance of this distribution?
I'm not an expert of the milter protocol but I will gladly help.
On Mon Nov 23 11:51:33 2009, ZUMMO wrote: Show quoted text
> On Fri Nov 06 04:06:27 2009, DCANTRELL wrote:
> > Would you like to take over maintenance of this distribution?
> > I'm not an expert of the milter protocol > but I will gladly help.
(This is a copy/paste form letter) Hello bug submitter to Sendmail::PMilter. As you may or may not be aware Sendmail::Pmilter is effectively orphaned. You've opened an issue against it which the current maintainer (me) doesn't have the time/want to solve. See http://search.cpan.org/~avar/Sendmail-PMilter- 0.98/lib/Sendmail/PMilter.pm#Maintenance for more details. But worry not, you can help solve it yourself if you're interested by patching the module in Git and asking for co-maint permission to upload a new version of the module. Even though your fix may seem trivial to you keep in mind that I'd still need to apply / *TEST* / release it. The testing step would require installing Sendmail and I have no interest in doing so ever again. The reason I'm the maintainer in the first place is that I spotted & patched a problem that needed to be solved and then got maintainer permission because the module was orphaned at the time. It's now orphaned again so if you need fixes to it you're going to have top step up and overtake it.