Spamassassin plugin: Can't call method ... on an undefined value

[markus schnalke]

Hoi,

I'm using qpsmtpd and am quite happy with it. Now I encountered
a problem, when someone sent a message with an (as the sender
said) empty body to me.

This is the relevant part of the logfile:

Thu Jul 21 17:51:45 2016 quagga[18965]: 250 <f...@openmailbox.org>, sender OK - how exciting to get mail from you!
Thu Jul 21 17:51:45 2016 quagga[18965]: dispatching RCPT TO:<b...@marmaro.de>
Thu Jul 21 17:51:45 2016 quagga[18965]: 250 <b...@marmaro.de>, recipient ok
Thu Jul 21 17:51:45 2016 quagga[18965]: dispatching DATA
Thu Jul 21 17:51:45 2016 quagga[18965]: 354 go ahead
Thu Jul 21 17:51:45 2016 quagga[18965]: FATAL PLUGIN ERROR [spamassassin]: Can't call method "as_string" on an undefined value at /usr/share/qpsmtpd/plugins/spamassassin line 163.

Thu Jul 21 17:51:45 2016 quagga[18965]: FATAL PLUGIN ERROR [spamassassin]: Can't call method "get" on an undefined value at /usr/share/qpsmtpd/plugins/spamassassin line 257.

Thu Jul 21 17:51:45 2016 quagga[18965]: FATAL PLUGIN ERROR [spamassassin]: Can't call method "get" on an undefined value at /usr/share/qpsmtpd/plugins/spamassassin line 257.

Thu Jul 21 17:51:45 2016 quagga[18965]: forwarding to localhost:25
Thu Jul 21 17:51:45 2016 quagga[18965]: FATAL PLUGIN ERROR [queue::smtp_2dforward]: Can't call method "as_string" on an undefined value at /usr/share/qpsmtpd/plugins/queue/smtp-forward line 60.

Thu Jul 21 17:51:45 2016 quagga[18965]: 451 Queuing declined or disabled; try again later
Thu Jul 21 17:51:45 2016 quagga[18965]: dispatching QUIT
Thu Jul 21 17:51:45 2016 quagga[18965]: 221 quagga closing connection. Have a wonderful day.


I'm using qpsmtpd from the Debian package version 0.84-9.

The spamassassin line in the plugins file reads:

spamassassin munge_subject_threshold 8 reject_threshold 12 leave_old_headers rename


Is this a known problem? How can I solve it?

Help is appreciated.


meillo


P.S.
Thanks for developing qpsmtpd, which I think is great software!

[markus schnalke]

[2016-08-03 16:38] Charlie Brady <charlieb...@budge.apana.org.au>

> On Wed, 27 Jul 2016, markus schnalke wrote:
> >
> > I'm using qpsmtpd from the Debian package version 0.84-9.
>

> I think you should be reporting your problem to the Debian bug tracker.

Are you implicitly telling me that it's no problem in qpsmtpd
but one in the Debian packaging?

Or are you implicitly telling me that you don't support such
old versions?

Or are you implicitly telling me that others should do the
first-level support?


Could you please clarify.


meillo

[markus schnalke]

Thanks for the reply!

[2016-08-04 11:34] Charlie Brady <charlieb...@budge.apana.org.au>

> On Thu, 4 Aug 2016, markus schnalke wrote:
> > [2016-08-03 16:38] Charlie Brady <charlieb...@budge.apana.org.au>
> > > On Wed, 27 Jul 2016, markus schnalke wrote:
> > > >
> > > > I'm using qpsmtpd from the Debian package version 0.84-9.
> > >
> > > I think you should be reporting your problem to the Debian bug tracker.
> >
> > Are you implicitly telling me that it's no problem in qpsmtpd
>

> I don't know if the problem has been fixed in the upstream qpsmtpd.

Wouldn't it be good to know that?

> > but one in the Debian packaging?
>

> It's definitely in the Debian version, and people maintaining the upstream
> code cannot fix the Debian version.

Of course. I never wanted that. My intention was to hear from you
if you know about this problem and maybe to get help fixing it
myself in the old version I have. You know Perl and qpsmtpd: you
might be able to guess for reasons, if it rather is a general or
a specific problem, and where to look at. (And you might discover
that the new version suffers from it as well ...)

It is unlikly that this problem will get fixed in the Debian
package (because the version is old and qpsmtpd isn't too
widespreadly used in Debian) ... unless I propose a patch myself.
But I wouldn't mind editing the files myself on my system, qpsmtpd
requires doing so, anyway.

As it seems I would have to squashing the bug completely on my
own, this becomes less of an option. The remaining options are:

1) Leave everything as is and accept a message not getting
accepted in long intervals.

2) Remove the Debian package and install the latest version of
qpsmtpd manually.

I tend to go for the former option, because it's less work for
me to do.


meillo

[markus schnalke]

Hoi.

I'm a bit late, but still: Thanks for pointing me on that!
This exactly *was* my problem.


meillo


[2016-08-10 15:33] Charlie Brady <charlieb...@budge.apana.org.au>

> On Wed, 27 Jul 2016, markus schnalke wrote:
> >

> > I'm using qpsmtpd and am quite happy with it. Now I encountered
> > a problem, when someone sent a message with an (as the sender
> > said) empty body to me.
>

> You might want to look at:
>
> http://grokbase.com/t/perl/qpsmtpd/118f562eah/patch-tweak-qps-header-handling-for-messages-with-no-body
>
> "tweak QP's header handling for messages with no body"