On Thu, 06 Sep 2012 22:11:28 +0200, Salvatore Bonaccorso wrote: > I debugged this a bit further and the problem seems to me more that as > you said spamassassin 'is wrong', as IO::Socket::SSL is checking > correctly his alternatives ...
Wow, impressive! > Here is an output traced running spamd with --ssl, to see first what > happens: Out of curiosity: How did you do this? > It does not seem to be an error of IO::Socket::SSL to me (but I'm not > expert on this), but rather that Spamassassin is handling $^S here in > 'strange' way? Agreed. > 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.) Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe `- NP: Joe Cocker: Marjorine
signature.asc
Description: Digital signature
