Thank you Sam,
In fact, since my Centos update, I also had an issue with Roudcube, I could not
send email. So I took back the previous version of Roundcube and there was no
bug anymore on my VPS.
So cool!
It was nice to help me :-)
Bye, Lenawaii
> Le 1 avr. 2020 à 15:12, Sam Clippinger via spa
H looks like a bug, but because spamdyke is compiled C, there's almost
no way to tell how it happened. If you updated your OS but didn't update
spamdyke, I'd suggest making sure you're on the latest version of spamdyke and
recompiling it on your updated OS. If you still see crashes, th
Well, dang! I'll keep hunting for more bugs, but if you have a way to trigger
these crashes reliably, I'd really love to work with you to get access so I can
test directly. If the version of gcc is new enough, I'd want to try
recompiling spamdyke with the -fsanitize=address flag, which will pr
Unfortunately after about four hours I'm seeing segfaults in my logs
again. :( I found it strange that it didn't happened right away after
installing a new spamdyke version.
...
Apr 13 11:31:11 mail kernel: spamdyke[26755]: segfault at 11 ip
7fbe85b03828 sp 7fff69e76990 error 4 in
lib
LOL. I think it even has a graphic installer in our days. Which I never
used actually. :) If you need a test environment I can always make one
for you.
Your patch is working, I think. I don't see kernel general protection
errors in logs anymore. So I assume that problem in my case is fixed.
Wow Gentoo, really? Every time I consider Gentoo, I start getting flashbacks of installing Slackware 1.2 from floppy disks back in the elder days. Nevertheless, I tried installing Gentoo to try to duplicate your environment and gave up about halfway through the install guide... I can't remember h
Hi Everyone,
On Apr 7, 2015, at 5:44 PM, Dirk via spamdyke-users
wrote:
Dear Sam,
at first thank you for glorious work with spamdyke! I'm using it
since
several years and it's very helpful to me.
At 30th march 2015 I've done an upgrade to version 5 (previous: last
4
version). Since then I o
If spamdyke was compiled on this server, I doubt the problem is glibc... it's
more likely the messages are showing a location within glibc because the fault
occurs within a library function. From those log entries, I think the most
likely clues are the ones mentioning a double free or corrupt m