after the latest openssl upgrade it happened again :)
While waiting to see upstream's reaction, could you rebuild the package
against the new version of the library?
PS
I'm reusing this bug because... well, it's the same bug after all, so I
hope it's ok - if it's not just tell me.
Also, since the problem is fixed^W^W goes away rebuilding the package, I
was wondering if there's a more straightforward way to handle this kind
of situation - a "smtpd -n" cronjob on a test machine or something like
that?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org