Control: reassign -1 spamassassin Control: severity -1 normal Hi Bjørn
On Fri, Sep 07, 2012 at 10:23:09AM +0200, Bjørn Mork wrote:
> Salvatore Bonaccorso <car...@debian.org> writes:
> > On Thu, Sep 06, 2012 at 10:22:57PM +0200, gregor herrmann wrote:
> >> On Thu, 06 Sep 2012 22:11:28 +0200, Salvatore Bonaccorso wrote:
> >>
> >> > Opinions? I would go for reassigning the bug to spamassassin and in
> >> > particular lowering the serverity (spamd is started and error messages
> >> > are missleading).
> >>
> >> Agreed again.
> >>
> >> (It would be nice to hear of Bjørn sees the same, i.e. a running
> >> spamd after the misleading error messages.)
> >
> > Okay, let's wait a few days until defintively reassigning. Bjørn could
> > you confirm that indeed nevertheless these error messages printed out
> > the spamd starts?
>
> Sorry for the delayed response. Yes, I can confirm that spamd starts,
> so the messages are only misleading. Please reassign and update
> priority as you see fit.
>
> Thanks a lot for looking into this.
Thanks for confirming. @Spamassassin-Maintainers, if I was correct
with some debugging of this, spamassassin seems a bit strange on
handling with (but at this I'm not an expert):
113 BEGIN {
114 # redirect __WARN__ and __DIE__
115 # do not trap warnings here based on eval scope; evals are very
116 # common throughout. die()s can be trapped though.
117 $SIG{__WARN__} = sub {
118 log_message("warn", $_[0]);
119 };
120 $SIG{__DIE__} = sub {
121 # see http://use.perl.org/comments.pl?mode=flat&sid=33872 for $^S
122 log_message("error", $_[0]) unless $^S;
123 };
124 }
I reassigned the bugreport from libio-socket-ssl-perl as this should
work correctly here, checking the alternatives and using the ones
found.
Regards,
Salvatore
signature.asc
Description: Digital signature
